Computer Science Question

Assignment #2 – Writing Requirements DefinitionsGood Requirements Definitions can mean the success or failure of a project! “A good requirement
states something that is necessary, verifiable, and attainable. Even if it is verifiable and attainable, and
eloquently written, if it is not necessary, it is not a good requirement. To be verifiable, the requirement
must state something that can be verified by examination, analysis, test, or demonstration. Statements
that are subjective, or that contain subjective words, such as “easy”, are not verifiable. If a requirement
is not attainable, there is little point in writing it. A good requirement should be clearly stated.” [1]
[1] Ivy Hooks, “Writing Good Requirements.” Proceedings of the Third International Symposium of the NCOSE. Volume 2, 1993
What will we do?
Define at least 10 unique functional or nonfunctional requirements for an app on a phone. You can use
any existing app as a reference to generate the requirements (please include the app name and/or
description of the app). At least five of the requirements are to be well-defined functional or
nonfunctional requirements. At least five of the requirements are to be poorly defined functional or
nonfunctional requirements. Then, critique each of the poorly defined requirements in terms of a
question you would ask to elicit a better written requirement.
Why are we doing this?
Most people write poor requirements because they have no training or experience in writing good
requirements. This assignment will allow you to explore writing good requirements, and critically
think through how you might extract more information from stakeholders when you have identified
problematic requirements.
Learning Objectives
This assignment makes use of multiple course objectives
• Describe Systems Engineering Standards and Best Practices
• Structure key steps in the SE processes from stakeholder analysis to transition of systems to
operations