Instructions sheet is attached
1 CSC 237 – Advanced C# Final Project Requirements OVERVIEW You are required to complete a final project for your final exam. The project will consist of the design, development, test, debug, and presentation of an ASP.NET Core MVC web application of your choice. This is a good opportunity to solve a problem of interest to you, to be creative, and to show your programming skills. The project can be anything you like, but it must have the required design documents and ASP.NET Core MVC programming concepts. Listed below are the program requirements section and their details. Be creative and have fun! After completing this final project, you will have a good introduction to the way large web applications are actually created. You will go through a lot of planning items before you actually code. You will realize that going through this planning process will allow your programming tasks to go much smoother by minimizing bugs or errors in programming logic. INSTRUCTIONS Getting Started Today, most new applications that are created, are done so as a web application. Rarely are new desktop applications created. There are myriad reasons why this is occurring, but the most frequent reason is deployment. Once a web application is created, it can be deployed quickly via the internet or intranet. Furthermore, updates to that application can be instantaneous. This is why many companies are switch to cloud-based web applications to support their business. Think of an interesting problem to solve using an ASP.NET Core MVC application. For example, a game, a data management system, or a form that computes the price of a car. Students in the past have created things like a grocery shopping list, a car dealership program for their family business, or a program to handle inventory for a jewelry business they were starting. It can be anything you like. Once you have selected an idea, notify the instructor by submitting the final project you will be writing for approval. Final Project Research – Before diving into any development project, it is always important to perform some extensive market research first. The reason here is two-fold. First, you should know what other companies are doing something similar to what you are thinking about doing. Chances are that when you think you have something unique, most times you will find that it is not. In doing so, you can begin thinking about how to differentiate your site from your competitors. Secondly, there is no sense in reinventing the wheel. Customers that use the sites of your competitors are used to information being presented in a particular way. For example, sites like Groupon and LivingSocial present customers with deals on their homepage. Therefore, it wouldn’t make sense for you to develop a similar website that requires users to perform multiple clicks to get your deals. Therefore, researching your competitors will help in the design and flow of your website. 2 Minimal Viable Product (MVP) – When creating a new piece of software, developers normally create what is known as a Minimal Viable Product or MVP. An MVP is a scaled-down version of the application we wish to bring to market. It contains the minimum functionalities that would still entice users to want to use or buy our application. Often times, we have big dreams for our application. However, all of the functionality we are wanting is not necessary right now. We just want to have something completed, that works and gives decent functionality to our user. An MVP is what you will be developing for your final project. To begin identifying your MVP, list all of the functionalities you would like to have in your application. Then try to eliminate those “nice to have” features. Important Things to Remember Your instructor may be able to provide you with some additional warnings about completing your project. Understand that plagiarism is a SERIOUS offense. This final project has been a standard for this course for several semesters. Your instructor has access to all previously submitted final projects. Your program must be written by you. Although you may obtain ideas from the internet or other students, your code must be your own. There have been at least one or two students each semester that attempted to test the system. In these cases, because the final is worth 500 points, the zero they obtained on the final resulted in them failing the course. What you must concern yourself with is that you must make sure that no other student has turned in the exact same code you did. The program can be the same but the code must not. As each semester passes, trying to find a project to copy the code and submit it as your own becomes harder and harder. IMPORTANT: Please understand that should plagiarism be discovered in your final program, all previous assignments for the final in which you may have previously received credit will also receive a zero. Should you feel the need to contest receiving a zero on your final, you must arrange an in-person meeting with the instructor within 1 week after final grades are posted. To submit your project for approval, create a Microsoft Word document that contains your name, class, and the name of your program. Then submit a one to two paragraph summary about what your program does. This summary should be detailed enough so that your instructor can identify most of the programming concepts needed to complete the application. Think of this document as your 90 second elevator pitch that you would give someone you wanted to sell your program to. IMPORTANT: When submitting this document to the Dropbox, please remember to at least include your name and a title for your program. Also, DO NOT DOUBLE-SPACE OR INDENT YOUR PARAGRAPHS!! You can use this document as a representation of how it should be organized. Your Required Tasks in Order of Completion 1. Complete Software Specification Document (SSD) 2. Complete user stories document 3. Project Wireframes 4. Submit application with completion of User Story 1 5. Submit application with completion of User Story 2 6. Submit application with completion of User Story 3 7. Submit your final program Task 1: Software Design Document (SDD) A Software Design Document or SDD is a written description of a software product that a software designer writes in order to give a software development team overall guidance to the architecture and design of the software application. This is a document that you will most likely come across many times 3 in your development career. It will allow you to take a deep-dive into determining what application you are actually building. Your task in this portion of your final is to write a simple but thorough SDD. A template has been attached to the SDD Dropbox as a starting point. Please use this document for the completion of this portion of the final. Please note that your thoroughness and your writing capabilities will be evaluated in this assignment. Therefore, please make sure you proof your work before submitting. Also, if I should have questions about your application further along in development, I should be able to refer to this document for answers. At a minimum, your SDD should define in detail your site’s CRUD operations. CRUD stands for CREATE, READ, UPDATE, and DELETE, which are the basic functions of data manage. Nearly all applications allow users to create or add new entries, to read or view those entries, to update or change those entries, and to delete or remove those entries. There most likely will be instances where some applications may have more of a particular CRUD operation than others. Also, many sites also have static pages that do not involve communicating with a database, which you will need to think about as well. You use these operations as a basis for your milestones if you’d like. The Dropbox for this assignment contains a template to begin preparing this document. This template contains instructions that will guide you through the completion of the document. If you have any questions concerning this document, please contact your instructor for more clarification. Lastly, please note that this will not be a document that you can complete in a day. It takes a lot of thought process to complete an SDD. Therefore, please allot enough time for you to do your research on your application. Task 2: User Stories With this final, you will be required to create user stories to aid in the identification of the requirements for your application. These user stories must specifically describe the main functionalities or your application and must be prioritized before submitting. If you need information on creating user stories, you may view the Creating Effective User Stories course on Pluralsight at the following link: https://app.pluralsight.com/library/courses/creating-effective- user-stories/table-of-contents. (Please note that I will be more critical about your user stories here than I have been in previous courses.) Below is an example of how you would create these user stories. Note, that you should create at least 5 user stories for your application. However, most likely, your application will require many more, so I would expect to see enough user stories to complete your MVP. Suppose that a customer has requested a sales tracking system. The first step in an agile process, like any other development method, would be to define the system requirements. The customer begins by meeting with programmers and providing user stories. A user story is a short, simple requirements definition. Programmers review user stories to determine the project’s requirements, priorities, and scope. Here are three user story examples: • As the sales manager, I want to identify fast or slow-moving items so I can manage our inventory more effectively. • As a store manager, I need enough lead time to replenish my stock so I don’t run out of hot items. 4 • As a