INSY 4051 Business Applications Development: Group Project - Phase II
INSY 4051 – Group Project – Phase II
The group project is aimed at helping students use the topics covered in the course to solve a business problem. The focus of this project is to promote problem solving rather than mindless application of best practices to a problem. Unlike best practices which change over time, problem solving is a timeless skill.
To increase the chance of transferable learned lessons across different groups at the end of the semester, all groups will work on developing a program that delivers a similar functionality, but in different contexts. Particularly, this semester we will focus on creating a Console application that allows users to make appointments or reservations. This functionality is useful in a variety of contexts such as hotel reservation, doctor’s appointment, and rental electric scooters (and many more). More details about the technical requirements of the project (e.g., authentication, user interface, etc.) will be available for Phase II.
In Phase II, groups will implement the information system they proposed in Phase I. Below, you see a list of requirements for Phase II. If you have any questions about the project, please ask as early as possible.
Phase II Requirements
-
Phase II document. In this document:
1.1. Explain the subset of functionalities you chose to develop and why you chose them. [about 1⁄2 -1 page] 1.2. Provide screenshots (or a video) along with brief descriptions showing how your app works.
1.3. If the app does not work, explain why (in this case, you should provide screenshots (or a video) of theparts that work properly).
-
Link to Project’s GitHub Repository. The project’s GitHub repository must contain:
2.1. The entire solution (including the .sln file, the project file, and all .cs files).
2.2. A complete history of the project (i.e., all commits and changes that led to the final repository).1 2.3. Proper comments in all .cs files.2
Note 1: To have a complete history of the project, the team members must use Git and GitHub to commit their changes to the project throughout the time they work on the project. For more information, follow the instructions in our in-class group project sessions.
Note 2: Proper comment means that a C# programmer who is not involved in your project should be able to understand the code by reading the comments.
