Posted: March 11th, 2022
Create User Story Included my proposal Building on your proposal from the first assignment, you’ll break down the functional requirements of each component of your project in a project specification
Create User Story Included my proposalBuilding on your proposal from the first assignment, you’ll break down the functional requirements of each component of your project in a project specification document. ScheduleIntroductionTue, Sep 15, 2020Discussion/Lab Class PeriodTue, Sep 22, 2020Office hoursBy appointmentAssignment DueThu, Oct 1, 2020 Requirements for the AssignmentYour specification should define the scope of the course-connected portion of your project and should contain a number of user stories that each identify the who, what, and why of each piece of functionality.User StoriesA user story is a requirement statement that identifies the basic characteristics of a piece of functionality: the role of a user with an activity or goal in mind, the desired action they would like to take, and their motivation for using that functionality.A user story usually initially takes the formAs a _________________ (who: user role)I want to _________________ (what: capability/activity/goal)so that I can _________________ (why: motivation).Once you’ve written a number of user stories, you can collect them into groups to identify the different user roles your application should support, the major types of activity your application should support, and the different types of motivations users bring to your application. You can add these categories to each of your user stories in order to identify themes you can focus on independently while working on the application. This will help you to focus your efforts and complete working software in small increments.You can capture these user stories and organize them in many different ways, but often the easiest method is to write each story on a 3”x5” index card with a marker or thick pen. This way, you can easily read what’s on the card, and can easily shuffle them and re-shuffle them into categories and themes, noting their categorizations and themes with annotations in the margins or on the backs of the cards.Prioritization and the MVAOnce you’ve developed your collection of user stories and identified the categories and themes among them, you will want to prioritize those themes and decide which of them need to be part of your minimum viable application (MVA). You may decide that some themes can easily be split into multiple phases of implementation, allowing you to prioritize a portion of that theme for early development and other portions of that theme later.Once prioritized, identify among the highest prioritized themes those that are important to include in the minimum viable application. Then, for those themes, identify whether each user story involves creating new capabilities in the browser-based client application, in the server application that supports it, or in both. If there are portions of the same user story that involve creating new capabilities in both applications, you will need to make a note on the story of what portion of the functionality belongs in the server and what portion belongs in the client.These MVA-relevant themes and their user stories should then be captured in a project board in your project Github repository. You can find the project board feature under the Projects tab of your project repo. For more information on project boards, see the Github documentation here.Your project board will serve as a guide for you during development of the next three assignments, so it’s very important that you create the relevant cards there.The Specification DocumentOnce all that is done, you will need to write a specification document identifying the goal and synopsis of the project based on your proposal and discussion with the instructor, the major user roles, themes, and other categorizations identified, and the portion of the work identified for the MVA with reasons for that prioritization.Your specification document should reference your project board and should contain a link to the project repostory within the document. SubmissionThe project board must be completed in your project Github repository.Your proposal document can be written in whatever software you wish, but must be submitted as a PDF format document.
Place an order in 3 easy steps. Takes less than 5 mins.