Interactive App Development Team
Project
PROG10065 Winter 2024
Summary
The PROG10065 Interactive App Development Team Project is a group project where 2-3
students collaborate equally to create an object-oriented program using principles, best
practices and technologies learnt in the course. Projects must incorporate the principles,
concepts and techniques covered in class as well as something new which will need a
certain level of research and experimentation.
Requirements
Content
1. UI presentation tier: at least 2-3 pages/views (one per team member) that are
significant for interactivity with the user.
2. Business logic tier: at least 4-6 significant classes (two classes per team member)
other than the user interface classes developed to support the presentation tier.
3. A data tier using files to persist data and application settings.
Technology
1. XAML and C#
2. Appropriate data structures (e.g. dynamic Lists)
3. Files for storing data (e.g. text, CSV, JSON)
Principles and Best Practices
1. Object-Oriented Programming design. Includes e]ective use of encapsulation,
polymorphism, inheritance, abstraction, loose coupling, separation of concerns,
and simple, cohesive classes and methods.
2. UML modelling diagrams to illustrate:
a. Significant classes and their relationships with one-another.
b. Significant workflows using sequence diagrams.
3. Source Code Version Control. E]ective use of Git and GitHub for the collaborative
development of source code. Comments with commit to Git repositories must be
useful and reflect changes made to code. The professor will require access to the
remote repository on GitHub at the end of the project.
4. Appropriate coding conventions and best practices in writing code. This includes
appropriate, descriptive names for variables and classes, as well as adhering to
proper naming conventions in C#.
5. Code Commenting.
a. Each class shall have a header with the principal author of the code and a
short description of what the code is for
b. Each method and field shall be commented with XAML style comments and
include a brief description of the purpose of method and field.
c. Comments should be included in any aspect of the code that reflects
significant design decisions.
Project Plan
1. Each C# class shall have only one author from the team. Each team member must
take ownership and responsibility of his/her contribution to the project’s code. You
will be graded individually based on your contribution.
2. The author shall be clearly documented in each source file.
3. Work assignments shall be clearly documented through an up-to-date project plan
that is to be delivered with the project.
Presentation
1. Present the purpose of the applica<on.
2. Present the applica<on’s project plan
3. Demo the applica<on func<onality. Each student in the group shall demo the
func<onality he/she worked on
4. Iden<fy how the project completed meets the requirements iden<fied in this document:
a. Content requirements
b. Technology requirements
c. Principles and Best Prac<ces
5. Presenta<on may be done in class (if <me permits) or may be a video recording.
Deliverables
1. Visual Studio project with complete source code and any assets necessary to
execute the project.
2. Access to the GitHub account hosting the project.
3. Presentation materials
4. Final project report consisting of the updated proposal document with what was
completed and with the di]erences between the initial proposal and the actual
outcome highlighted. The Project Plan section should clearly identify the detailed
responsibilities that each team member had in the completion of the project.
All the project deliverables shall be archived and submitted via SLATE.
如有需要，請(qǐng)加QQ：99515681 或WX：codehelp