Skip to content

tektechnologies/Software-Development-Capstone

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Millennial Resort Manager (MRM, Inc.)


Product Owner

Craig Barkley - GitHub Profile

Database Administrator

Jared Greenfield

Scrum Leaders

Francis
Dani
Austin B.
Dalton

Scrum Teams

Scrum Team One

Francis
James
Ramesh
Eric
Matt H.

Scrum Team Two

Dani
Matt L.
Richard
Caitlin
Kevin

Scrum Team Three

Austin B.
Phillip
Eduardo
Austin D.
Wes

Scrum Team Four

Dalton
Carlos
Alisa
Jacob
Gunardi

What is Definition of a Done Increment?

What is done?

  • Must compile without errors: Daily build rule.

  • Tested: Unit tested + Logic Layer, Stored Procedure Approved + Pair program with someone else.

  • Standard Documentation: UML automation.

  • Exception Handling (Try-Catch): Properly validated + Validation object class for presentation.

  • Documentation updates.

  • NOT DONE UNIT SUBMITTED! - Resolved Git issue conflicts + Rerun unit test and recompile

  • Logic Layer / Data Access made with Interfaces: i.e ( iRoomManager ).

  • User Interface needs to look good and have human readable values

  • Lookup Table procedures.

  • Must follow naming conventions.

C# Coding Standards and Naming Conventions

Object Name Notation Length Plural Prefix Suffix Abbreviation Char Mask Underscores
Class name PascalCase 128 No No Yes No [A-z][0-9] No
Constructor name PascalCase 128 No No Yes No [A-z][0-9] No
Method name PascalCase 128 Yes No No No [A-z][0-9] No
Method arguments camelCase 128 Yes No No Yes [A-z][0-9] No
Local variables camelCase 50 Yes No No Yes [A-z][0-9] No
Constants name PascalCase 50 No No No No [A-z][0-9] No
Field name camelCase 50 Yes No No Yes [A-z][0-9] Yes
Properties name PascalCase 50 Yes No No Yes [A-z][0-9] No
Delegate name PascalCase 128 No No Yes Yes [A-z] No
Enum type name PascalCase 128 Yes No No No [A-z] No

Add to READ.me below.

3. Development Tools

1. Visual Studio 2017 Enterprise; .Net Build Target 4.6.1 (NOT CORE)
2. Database: SQL Server version 2012 Express
3. WPF + ASP.NET MVC
4. Better Controls - ? - XCEED Community Edition Control Set
5. Entity Framework, Most Stable JSLibrary through NuGet Package Manager (DO NOT USE BETA)
6. Discord, Trello, Github

4. DataBase Naming Conventions

1. Obey C# naming conventions//forever.
2. Descriptive is better.
3. DataAccess - Create, Retrieve, update, deactivate, purge.
4. Logic Layer - Add, Edit, Retrieve, Delete.
5. DataBase - (snake case) - Insert, Select, Update, Delete.
6. Presentation(Hungarian) - btn, lst, tst, cbo, pwd.

5.

6.

7.

8.

9.

10.

11.

12.

13.

14.

15.

Offical Reference

  1. MSDN General Naming Conventions
  2. DoFactory C# Coding Standards and Naming Conventions
  3. MSDN Naming Guidelines
  4. MSDN Framework Design Guidelines
  5. ktaranov/naming-convention

About

Final Project Code for Kirkwood Project

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published