Page 1 of 13 COMP 2139 – ASP.NET Web Application Development Due Date: Friday, February 25th, XXXXXXXXXX:59 pm) Team Size: 2 – 4 Team Members. Project Name: GBCSporting_ Problem Synopsis: Having...

Web Application (Model-View-Controller)


Page 1 of 13 COMP 2139 – ASP.NET Web Application Development Due Date: Friday, February 25th, 2022 (11:59 pm) Team Size: 2 – 4 Team Members. Project Name: GBCSporting_ Problem Synopsis: Having graduated from George Brown College, you have recently been offered and accepted a position at a lucrative start-up company. The company consists of a number of experienced engineers and developers, who believe that hiring a new graduate, such as you, will result in an abundance of new and innovative ideas to the organization. The company is situated in the Sporting sector, and the IT Director has identified the need to develop an application designed for the technical support department of a hypothetical software company that develops software for sports leagues. The purpose of the website is to track technical support service calls (referred to as incidents) in a database that also stores information about the company’s customers, software products, and technicians To kick-off phase I of the project, your manager has the initial task of assembling a team capable of constructing the first phase of the project. As such, the IT Director, Management team and Architects all agree, that utilizing ASP.NET (Visual Studio), C#, IIS (IIS Express) and SQL Server (SQL Express), .NET6.0 are a mandatory requirement. The architects envision the solution should be delivered in two separate releases, specifically, phase I (assignment 1) and phase II (assignment 2 – to follow later in the course). Your manager recalls during the interview, that you had highlighted your familiarity of ASP.NET, C# and web application development. Giving your experience of these technologies, you immediately appeal as an ideal candidate to be added to the project team. Additionally, by selecting you as part of the project initiative, your manager will conveniently be presented with the opportunity to evaluate your performance, gauging how you may possibly fit into future projects within the organization. The phase I project deliverables have been scoped-out for by the Business Analysts. Wireframes have been constructed and serve to clarify the project deliverables that the solution must contain at a minimum. Page 2 of 13 Project Brief The GBC Sporting Technical Support website consists of web pages that support two types of users. First, it lets administrators manage the products, technicians, customers, incidents, and product registrations that are in the database. Second, it lets technicians update incidents that have been assigned to them. The Database The database for the application stores the data that’s needed to track technical support incidents. You may build the database up incrementally, but ideally for the completed web application, the database should include tables for storing data about the company’s products, technicians, customers, incidents, and registrations (you do not need all these tables for assignment 1, the recommendation is you develop only the elements of the schema you need for assignment 1, and defer the remaining tables/relationships for the final assignment, assignment 2). The Table Entity Relationships The Incidents table contains one row for each technical support incident. Each row in the Incidents table is related to one row in the Customers table, which contains data about the company’s customers; one row in the Products table, which contains data about the company’s products; and one row in the Technicians table, which contains data about the company’s technical support staff. In addition, each row in the Customers table is related to one row in the Countries table, which stores a list of available countries. The Registrations table, on the other hand, is a linking table (join table) that creates a many-to- many relationship between the Customers and Products tables. As a result, each row relates one customer to one product. This allows one customer to register many products, and it allows one product to be registered by many customers. The Assignment The description of the assignment includes one or more screen captures (wireframes) that conveys how the pages should conceptually appear when they’re completed as well as specifications for how the assignment should be coded. Please note however, the design of each page, and the overall application however, is ultimately left up to each team. A level of creativity and originality is much appreciated. This information is detailed enough for you to complete the assignment. However, you’ll need to use your best judgment on how to code many of the details. To do that, write the code in the way that you think is best. For some requirements, the assignment’s specifications will require your team to perform a certain amount of research. For example, some requirements will require the study of technologies/enhancements related to the course material, but may perhaps have yet to be formally covered in the course lectures. Page 3 of 13 Home Page The GBC Sports Application requires a Home Page. The Home Page includes a navigation bar and some menu options for alter assignments The Business Analysts have provided a wireframe mockup of a potential home login page below: Home Page - Specifications • Create an application that based on the MVC (Model-View-Design) pattern. • Create a home page like the one shown above • Use a Razor layout to store elements that are common to all pages, such as the navigation bar and footer • The recommendation is to use bootstrap for styling, but the design is left open to each individual group. • Mark all navigation bar items as active. Page 4 of 13 Manage Products The GBC Sports Pro application requires a Products page that allows admin users (and only admin users) to view, edit and delete existing products. The Business Analysts have provided a wireframe mockup of a potential Products page below: The Product Manager Page - Specifications • When the user clicks on the Manage Products link on the Home Page, or the Products link in the navbar, the application should display the Product Manager page. • When the user clicks the Add Product button, the application should display the Add/Edit Product page with blank Code and Name fields but with the current date in the Release Date field. • When the user clicks the Edit button for a product, the application displays the Add/Edit Product page with the current data for the product. • When the user clicks the Delete button for a product, the application should display a Delete Product page that confirms the deletion. Page 5 of 13 The Add/Edit Product Page The Business Analysts have provided a wireframe mockup of a potential Add/Edit page below: The Add/Edit Page - Specifications • The application should display the Product Manager page when the user completes or cancels an add, edit, or delete operation. • Validate the data the user enters in the Add/Edit Product page to be sure that the user enters a product code, name, and price. If this data isn’t provided, the app should display a summary of the validation errors above the form. • Use lowercase URLs with a trailing slash. • Since they are so similar, use the same Razor view file to add and edit a product. Page 6 of 13 Manage Technicians The Business Analysts have provided a wireframe mockup of a potential Manage Technicians page below: The Manage Technician Page - Specifications • When the user clicks the Manage Technicians link on the Home page or the Technicians link in the navbar, the application should display the Technician Manager page. • When the user clicks the Add Technician button, the application should display the Add/Edit Technician page with blank fields. • When the user clicks the Edit button for a product, the application should display the Add/Edit Technician page with the current data for the technician. • When the user clicks the Delete button for a technician, the application should display a Delete Technician page that confirms the deletion. Page 7 of 13 The Add/Edit Technician The Business Analysts have provided a wireframe mockup of a potential Add/Edit Technicians page below: The Add/Edit Technician Page - Specifications • The application should display the Technician Manager page when the user completes or cancels an operation that adds, edits, or deletes a technician. • Validate the data the user enters in the Add/Edit Technician page to be sure that the user enters values for all fields. If this data isn’t provided, the application should display a summary of the validation errors above the form. • Use lowercase URLs with a trailing slash. • Use the same Razor view file to add and edit a technician. Page 8 of 13 Manage Customers The Business Analysts have provided a wireframe mockup of a potential Manage Customers page below: The Manage Customers Page - Specifications • When the user clicks the Manage Customers link from the Home page or the Customers link from the navbar, the application should display the Customer Manager page. • When the user clicks the Add Customer button, the application should display the Add/Edit Customer page with blank fields. • When the user clicks the Edit button for a customer, the application displays the Add/Edit Customer page with the data for the selected customer. • When the user clicks the Delete button for a customer, the application should display a Delete Customer page that confirms the deletion. Page 9 of 13 The Add/Edit Customer Page The Business Analysts have also provided a wireframe mockup of a potential Add/Edit Customer page below: The Add/Edit Customers Page - Specifications • The application should display the Customer Manager page when the user completes or cancels an operation for adding, editing, or deleting a customer. • Validate the data the user enters in the Add/Edit Customer page. To be valid… o The user must select a country from the drop-down list of countries. o The Email and Phone fields are optional. o All other fields are required. • Use the same Razor view file to add and edit a customer. • In the Country drop-down list, display all countries that are available from the database (add some countries to your database). • When the application displays the Edit Customer page, make sure to select the correct country for the specified customer. Page 10 of 13 The Manage Incident Page