Project Requirements 1. The project shall consist of: a. At least 6-12 forms (two to three forms per team member). b. A database of at least 2-8 tables (at least one per team member) linked / related to each other. c. At least 6-12 classes (at least two classes per team member) other than the Windows / Web Forms classes. These classes are to handle the business logic. Please note that: d. The project should be complex enough based on the number of team members. e. It does not make sense that a team of four members create a very simple project, which simply does CRUD operations. 2. Project shall make use of the following technologies/techniques: a. Windows forms or Web forms. b. ADO.NET, for database connectivity (preferably DataSets and offline connectivity). c. Commenting. The code shall be commented according to the following requirements: i. Each class shall have a header with the principal author of the code and a short description of what the code in the file is for. ii. Each method and field shall be commented with XML style comments and include a brief description of the purpose of method and field. If the Author of the method is different than the author of the class, the author name shall also be included in method headers. iii. The code (inside functions) shall be commented to explain WHY the code is there (not how, not what) wherever necessary. d. Coding conventions: i. Forms and controls naming conventions. ii. Scope prefixes conventions (e.g. use of _ prefix for any field). iii. Naming conventions: names start with capital letters for classes, methods and properties, and start with a small letter for variables and fields. 3. Quality of the design and code will have a significant role when grading the project: a. Simple, cohesive classes and methods. b. Descriptive names for classes, methods and variables. c. Coding conventions (naming conventions, indentation, code organization). d. Comments (both XML style comments and regular code comments). Web Services using .NET and C# Programming Winter 2017 2 Web Services using .NET and C# Programming 4. Work assignments: a. Each C# class shall have only one author out of the group. "We all worked on it together" is not acceptable, as that would never happen in a professional team project. As a team, you collaborate but each team member must take ownership and responsibility of a piece of the code. You will be graded individually based on your contribution. b. The author shall be clearly documented in each source file. Again, multiple authors in a single file not acceptable. c. The work assignments must be consistent with the original project proposal even if minor difference exist AND they must be updated in the project completion document. 5. Project Presentation: a. I'll visit each group one-by-one to see the functionality of the application. (You do not need to prepare slideshow and present in front of the class.) b. Present the purpose of the application to me. c. Present a high-level overview of the application. d. Demo the application functionality. Each student in the group shall demo the functionality he/she worked on. e. Present briefly the technologies used in the application (follow the list of requirements given in point 2. f. Every member of the group should be present for the project presentation. g. Every member will be graded individually, not as a group.