Systems Analysis - Functional and non-functional requirements
Related learning outcomes from the unit outline:
- Demonstrate evidence of the knowledge set and skill set required by the systems analyst.
- Apply structured techniques to the analysis of current systems and modelling of future systems.
Background: Finding or eliciting the functional (FRs) and non-functional requirements (NFRs) of a system is a critical skill for a systems analyst. For each of the following items, decide if each is a FR or NFR by seeing if it conforms to the definitions given in the lecture (a FR is what is system is supposed to do whilst an NFR is how to do it or a system constraint).
Tasks:
1. Split yourselves into groups of four. Decide if the following items are functional requirements, non-functional requirements or something else then provide reasons for your choice.
2. Discuss if the requirements are well-specified or not.
3. Re-write as necessary, using the following popular format: 1) the user; 2) the capability; 3) the object; and 4) the qualifier. For example: The warehouse manager (user) must be able to create (capability) the incoming stock records (object) anytime within standard business hours (qualifier).
a. The system shall allow users to see all of their invoices for the past 30 days.
b. The system must authenticate users.
c. The system must have an easy to use user interface.
d. The database will be MySQL.
e. All code must be stored in an SVN repository.
f. The system shall charge users' credit cards for purchases.
g. The system shall store user information, specifically name, DOB and address, in an Oracle database.
h. The system shall process all mouse clicks very fast to ensure that users do not have to wait.
i. The system must encode all transactions with 1024 bit RSA keys.
j. The system shall debit a user's account upon withdrawal of funds.