Recent Question/Assignment
Requirements Document
The key to design is a good understanding of the requirements of the system. The requirements document captures the functional and non--functional requirements of the system we will eventually develop. When I read your document I am looking to get an understanding of how the system will work. For example, how will the system look on startup. How will the user create a new album? How will the user add a photo to an album? And so on.
The Requirements Document should address the system requirements and should not include design issues. At a minimum your requirements document must contain:
• Document Title
• Date
• Introduction
• Glossary
• User Requirements Definition o Functional Requirements
o Fully--elaborated Use Cases and Scenarios o Non--functional Requirements
• Requirements prototyping o Screen Layout/Screenshots
• Risk Analysis
Note:
Use--cases are a great way to address requirements. The use--case diagram (stick-men and bubbles) is only the starting point for your UML diagrams. Fully elaborated use--cases are a very powerful way to analyze requirements. For example, suppose we have a use--case called -Add photo to album-. What is the purpose of this use-case? What are the pre--conditions? Must the album already be selected or is this part of the use--case? What happens during the use--case? What are the post-conditions? Is their exception flow in addition to normal flow?
Requirement prototyping can help refine and further elaborate your requirements. Creating screenshots of the use cases or requirements can help user visualize the system and helps identify underlying requirements. You can include screenshots within the body of the use case or you can place all screenshots in an appendix and refer to them from the use--cases. You will normally have at least one use case for each functional requirement ---- this is just a general notion ---- but it's a good place to start.
There are many Requirements Document Templates available online. If you already
have a template that you have used in the past, please feel free to use it in this course as long as it covers the areas listed above.
Grading Rubric:
• Introduction, including title and date – 10 points
• Glossary – 10 points (based on completeness of terms)
• User Requirements Definition -- 45 points (based on accuracy and completeness of elaboration)
• User Interaction – 25 points (based on completeness and reflection of requirements)
• Risk Analysis – 10 points
The key to design is a good understanding of the requirements of the system. The requirements document captures the functional and non--functional requirements of the system we will eventually develop. When I read your document I am looking to get an understanding of how the system will work. For example, how will the system look on startup. How will the user create a new album? How will the user add a photo to an album? And so on.
The Requirements Document should address the system requirements and should not include design issues. At a minimum your requirements document must contain:
• Document Title
• Date
• Introduction
• Glossary
• User Requirements Definition o Functional Requirements
o Fully--elaborated Use Cases and Scenarios o Non--functional Requirements
• Requirements prototyping o Screen Layout/Screenshots
• Risk Analysis
Note:
Use--cases are a great way to address requirements. The use--case diagram (stick-men and bubbles) is only the starting point for your UML diagrams. Fully elaborated use--cases are a very powerful way to analyze requirements. For example, suppose we have a use--case called -Add photo to album-. What is the purpose of this use-case? What are the pre--conditions? Must the album already be selected or is this part of the use--case? What happens during the use--case? What are the post-conditions? Is their exception flow in addition to normal flow?
Requirement prototyping can help refine and further elaborate your requirements. Creating screenshots of the use cases or requirements can help user visualize the system and helps identify underlying requirements. You can include screenshots within the body of the use case or you can place all screenshots in an appendix and refer to them from the use--cases. You will normally have at least one use case for each functional requirement ---- this is just a general notion ---- but it's a good place to start.
There are many Requirements Document Templates available online. If you already
have a template that you have used in the past, please feel free to use it in this course as long as it covers the areas listed above.
Grading Rubric:
• Introduction, including title and date – 10 points
• Glossary – 10 points (based on completeness of terms)
• User Requirements Definition -- 45 points (based on accuracy and completeness of elaboration)
• User Interaction – 25 points (based on completeness and reflection of requirements)
• Risk Analysis – 10 points
Looking for answers ?
Recent Questions
Word limit: 1500 - 2000Objectives:The purpose of this assignment is to:1. Familiarise yourself with best practice in engineering sustainability in a particular field by conducting a thorough literature...Module code: BMA4005-20Module title: Professional PracticeAssignment: A1. Digital PosterWord count: 500Contribution to module mark: 40% of overall gradeAssessment type: IndividualWeight 40%Submission deadline:...Assessment Criteria for Written Report (20%)• Submission of a minimum 1500 to maximum 1800-words written report due from week 9. You will submit your written report one week after you have undertaken the...Assessment 2: (20%) Case Study Presentation Due Date weeks 10This assessment builds on your theoretical knowledge and tests your ability to apply this knowledge to practice.you are required to formulate...Assessment 2Assessment 2Report: 30%Word count: 1400 – 1600 wordsDue date: Sunday of Week 8DescriptionYou are playing the role of a community service worker supporting a young adult son who is 18 years...1500-1800 wordsInstructions From TutorPlease download the eTask3 spreadsheet from Canvas and save the eTask spread as an Excel file. The main content of the force method is taught in Lectures 6,7&8.eTask3.1 is a...Show All Questions