The purpose of this section is to document some examples of the requirements for the proposed system. The requirements checklist communicates what the system is expected to do and how it is to perform. For purposes of this business case, the requirements checklist will include five (5) requirements, each one stated as one complete sentence, for each of the following areas:
- Functional requirements â€“ what the system will do. Roberto, Julian
- Data requirements â€“ requirements for handling input, output & storage of data. (this is the only thing I need answered )
- Technical requirements â€“ system performance specifications.
- Security requirements â€“ covering various aspects of system, data, and transaction security.
The result will be a list of 20 requirements statements, separated into the categories above.
Approach to Developing this Section
To gain and understanding of what constitutes well written requirements, read the “Writing Good Requirements” document in the Course Content and Section 4.3 of http://www.math.uaa.alaska.edu/~afkjm/cs401/IEEE83…
As outlined in that resource, the statement of each requirement should be correct, unambiguous, complete, and consistent. With those characteristics, they will also be verifiable, modifiable and traceable. The area that requires the most careful consideration is determining into which category the requirement should be placed. Almost all requirements are “functional” – but those which have to do with security or system performance or directly with data should be put into those categories. “Functional” has to do what the system processing needs to do for the user.
Use information from the case study to develop the functional and data requirements. Technical and security requirements may come from team members’ previous experience or learning, or from research. Each requirement must specifically tie to the case study and the proposed solution. Five well-written requirements are to be developed for each category: functional, data, technical and security requirements, for a total of 20 requirements. An introduction to the Requirements Checklist should precede the list.
You should understand that, although it is beyond the scope of this business case (and should not be included), to be able to trace requirements through the system development process, additional information is normally provided in the Requirements Checklist, including: Category, Number, Statement of Requirement, Source of the Requirement, Where it is implemented in the system, how it is to be tested, and a place to indicate that each requirement has been implemented in the system. In a total list of requirements for a system, there would also be many more requirements than this, but just listing the 20 requirements statements is enough to demonstrate the ability to identify and write requirements in the various categories.
The software me and my group are using is Qfloors