Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: THEend8_
CSC 648/848-04
Milestone 1: Use cases, High Level Requirements and Specifications Announce: 06/10/2021 Due: 06/22/2021 Objective: The objective of Milestone 1 is to develop: a) initial high-level personas and use cases; b) from use cases develop high level functional requirements for the application, c) list high level architecture, frameworks and tools to be used (generally the same as in M0), and c) get the teamwork going. Note that these are only high-level requirements and specs with the idea to get early feedback and iterate before investing in developing more detailed specs and first prototype in Milestone 2. Future designs can deviate from Milestone 1 in the spirit of iterative SW design and development. Initial input for your work is the instructor guidance, class slides on the topics as well as your SW and tool selection for M0. For use cases and functional specs, feel free to also use your own ideas, research similar applications that already exist, talk to your friends etc. Please consult class material on Use Cases, Requirements and Specs. This is the first team milestone. The whole student team submits one milestone document for each Milestone 1 – 5, submission details are below. You will discuss ongoing work on Milestone 1 during team session in each class, and you can also send e-mail to instructors with questions. Expected size of this document is at least 10 pages. Document formatting (page numbers, table of contents, each section starts in a new page….) is really important when you submit technical documentation like the one in M1. Content and structure for Milestone 1 document for review: In the document for Milestone 1 (M1) you must have ALL of the following subsections in exact order as below (have a separate numbered section for each) in one PDF file. I require that each subsection starts on the new page: 0. Title page MUST include –“SW Engineering CSC648/848 Summer 2021” Project/application title and name (you can use the name you chose for your application) –Team number –Names of students (team lead first) with e-mail of team lead. Please mark those who are team lead, front end, back end leads and Github master –“Milestone 1” –Date –History table (revisions) (Note: you will update this document based on instructors’ feedback so this is important) 1. Executive Summary: Short description of the final product/application and its key advantages, novelty, value (up to 1 page). Make it as an executive summary – think of answering the question of why we should fund this project. We suggest you assign a name to your project for easier reference and good “marketing”. This summary should be readable to a general manger/executive that is not a CS specialist and is used to explain and also to advertise/promote your project. Typical outline is: one paragraph on the motivation and importance of the application you are developing, followed by a paragraph on what your application will be doing and how it helps the users (high level only, no jargon) and optionally what is unique and special in your design. 2. Main Use Cases: Summarize key categories of users/actors for your application – their general characteristics, goals, skills, pain points related to the application you are developing. About 1/3 of a page per actor – see class notes. (Note: in key categories you stay general, in use cases you say how actors/users will use your app (at high level)). Then provide 5-10 main use cases (one paragraphs for each use case) - see class notes on more detailed format for requirements. Focus only on main use cases. For each Use Case you develop, first create it in text format, and then describe it using a Use Case diagram. Don’t forget to add in your user cases possible situations where the user or/and your app/actors do not perform actions as expected.