The goal is to practice defining non-functional requirement, assign importance and priority to functional requirements, and conduct a risk analysis.
Non-Functional Requirements, Prioritization, and Risk Analysis
Your manager asked you to complete the ABC Distance Learning Software System specification document by adding non-functional requirements, classifying importance and prioritization to functional requirements, and to analyze and assign risk rating and impact areas to functional requirements. The list of the features (functional requirements) for this system is listed in the template under section 2.2.
Project 3
Software Requirements Specification
Non-Functional Requirements, Prioritization, and Risk Analysis
Mission:
Your manager asked you to complete the ABC Distance Learning Software System specification document by adding non-functional requirements, classifying importance and prioritization to functional requirements, and to analyze and assign risk rating and impact areas to functional requirements. The list of the features (functional requirements) for this system is listed in the template under section 2.2.
Objectives:
The goal is to practice defining non-functional requirement, assign importance and priority to functional requirements, and conduct a risk analysis.
Steps:
You are to use the project3-specification-template.doc which specifies the sections and information you need to provide. It already lists the functional requirements for which you are to assign importance, prioritize, and perform risk analysis. For non-functional requirements, think of the LEO system or any other virtual classroom you have used in the past and make up some relevant non-functional requirements that you think this type of system should have based on the given features. Try to come up with as many different types of non-functional requirements as you can and make sure to make them measurable and as specific as possible.
Resources:
Review related book chapters, power points charts, and class discussions for week 7 and 8.
Review SRS-RPS Game-Requirements – FullExample.docx sections 5, 6, and 7 to help with this project.
Deliverables:
Your deliverable must be the specification document submitted as Microsoft Word file named YourName-Project3-Specification.doc or YourName-Project3-specification.docx.
Grading Rubric:
- 5% The document meets graduate level
criteria with no issues with grammar, punctuation, spelling, etc. APA style
guide is used for providing any citations and references. Background
information is filled out correctly and completely
- 5% Project was submitted to TurnItIn
- 15%The document identifies significant
number of appropriate non-functional requirements’ categories and requirements
for this product that are measurable and explained clearly and completely.
- 10% The
document explains fully and clearly the overall approach to classifying the
importance level for each functional requirement
- 15% Each
requirement is given an importance level classification (L, M, or H) along with
explanation of rationale for the classification. Note: Importance classification determines how important each
requirement is to be implemented. High requirements are critical and low
requirements may have a work-around and could de not implemented or implemented
at a later time.
- 10% The
document explains fully and clearly the overall approach to prioritizing the
requirements (what technique is being used) and how the priority is determined
(based on what criteria).
- 15%All requirements are prioritized
based on the technique used within their importance level. The requirements are
sorted from highest priority to lowest within their importance group. There is
a rationale for the prioritization of each requirement. Note: Priority determines the order of implementing the
requirements. Rationale should explain why one requirement should be
implemented earlier than other one.
- 10% The
document explains fully and clearly the approach to assigning risk to each
requirement for each risk type and then how the overall risk for each
requirement is determined.
- 15%For each requirement there are different types of risks identified along with their rating of that risk. There is an explanation for each rating. Then there is an overall risk calculated for each requirement. The requirements are sorted in the order of highest overall risk requirement to lowest one. Note: The risks represent what is the likelihood that the particular type of risk will happen to the product when this particular requirement is added. For example, what are the chances that implementing this particular requirement will impact the performance of the overall product.
Total 100%
