1. Requirements Management
Needs statements to User Requirements
Instructor Slides
Exercise Module Number: RM10
This course material was developed with NSF – TUES award #

2. SMART Requirments S – Specific M - Measurable
A – Attainable or Action-oriented
R - Realistic
T – Traceable or Time-based

3. Some Terminology Needs Statement: SRS: Use Case: ? Decision Tree: ?
Also known as problem statement, need statement, or needs assessment
Statement of need establishes the focus and rationale of the requirement
The statement of need is a concise and coherent statement
SRS:
Is a description of a software system to be developed. It lays out functional and non-functional requirements, and may include a set of use cases that describe user interactions that the software must provide.
Use Case: ?
Decision Tree: ?
Truth Table: ?

4. Some Terminology: Use Case
In software and systems engineering, a use case is a list of steps, Typically defining interactions between a role (known in Unified Modeling Language (UML) as an "actor") and a system, to achieve a goal. The actor can be a human, an external system, or time.
Source:

5. Some Terminology: Use Case
A UML Use Case Diagram for the interaction of a client (the actor) and a restaurant (the system)
Source:

6. Use Case: Manage Backpack
ID: UCS
Actors: Player
Preconditions:
Game play is paused
Backpack contents are visible
Flow of Events:
Use case starts when player selects a backpack item
If player selects “remove” item”
2.1 System deletes selected item from backpack display
If player selects “add item”
3.1 Systems places new item in backpack display below the selected item
Postconditions:
Backpack display is updated
1/15/2019

7. Use Cases
Scenarios that describe how the product will be used in specific situations.
Written narratives that describe the role of an actor (user or device) as it interacts with the system.
Use-cases designed from the actor's point of view.
Not all actors can be identified during the first iteration of requirements elicitation, but it is important to identify the primary actors before developing the use-cases.

8. User Profile - Example Full Control (Administrator)
Read/Write/Modify All (Manager)
Read/Write/Modify Own (Inspector)
Read Only (General Public)

9. Use Case Example - 1 Read Only Users Read/Write/Modify Own Users
The read-only users will only read the database and cannot insert, delete or modify any records.
Read/Write/Modify Own Users
This level of users will be able to insert new inspection details, facility information and generate letters. They will be also able to modify the entries they made in the past.

10. Use Case Example - 2 Read/Write/Modify All Users Full Control Users
This level of users will be able to do all the record maintenance tasks. They will be able to modify any records created by any users.
Full Control Users
This is the system administrative level which will be able to change any application settings, as well as maintaining user profiles.

14. Some Terminology: Decision Tree
A decision tree is a decision support tool that uses a tree-like graph or model of decisions and their possible consequences, including chance event outcomes, resource costs, and utility. It is one way to display an algorithm.
Source:

15. Some Terminology: Decision Tree
Source:

16. Decision Table
Rules
Condition 1 2
Actions

17. Condition
N not numeric T F
N <= 1 -
N legal
N prime
Action
Print “N prime” X
Print “N not prime”
Print error message
Print “Good bye”
Input new value for N
Stop

18. Presentation Graphics
Event Table
Mode
Event1
Event2
Event3
Event4
Presentation Graphics
Action1
Action8 O X
Architecture
Drawing
A2 then A3
A5 & A6
Programming A4
A1, A2 & A3 A7
X = no action defined for event
O = no state change and no action

19. Task
Discuss how each of the expressed "needs" statement may be developed into a Use Case description for analysis and requirements specification.
Could a Decision Tree be used?
Could a Decision Table (Truth Table) be used?
Could a Use Case be used?

20. Needs Statement 1
To order the pizza online, the customer should be able to conveniently specify size and various combinations for the choice of toppings. But certain toppings, with price discount would be offered only for the large pizza.
What do the students say?

21. Needs Statement 1
To order the pizza online, the customer should be able to conveniently specify size and various combinations for the choice of toppings. But certain toppings, with price discount would be offered only for the large pizza.
We need to analyze all the different cases possible with an order. A decision tree or table will be a good tool to do that. The Use Case description will verify that our analysis is correct.
Instructor: This can become very complicated depending on the number of different cases that need to be dealt with differently. It will be a good study case for the use of decision tree.

22. Needs Statement 2
For regular pain medicine, the nurse may write in the prescription, but nurse must also send a request to one of the available doctors and anyone of them may then review the patient record and endorse the prescription.
What do the students say?

23. Needs Statement 2
For regular pain medicine, the nurse may write in the prescription, but nurse must also send a request to one of the available doctors and anyone of them may then review of the patient record and endorse the prescription.
The parties involved are (1) nurse, (2) doctors. The interaction sequence of events need to be sorted out. The completed use case cover end- to-end from the nurse initiating till the work flow terminates with a doctor endorsing, or nurse rescinds the prescription.
Instructor: The work flow of how the document (prescription written by the nurse) goes through different states needs to be analyzed and understood to see how the interactive sequence between the parties work in concert.

24. Needs Statement 3
Upon receipt of the student's registration request to enroll, the system will check to make sure that the student has paid all outstanding fees. Otherwise, the request will be put on hold or denied.
What do the students say?

25. Needs Statement 3
Upon receipt of the student's registration request to enroll, the system will check to make sure that the student has paid all outstanding fees. Otherwise, the request will be put on hold or denied.
Upon receipt of the student's enroll request, the "system" will follow a sequence of interactive with various other sub-systems, checking for appropriate information and/or status. The interaction terminates with the request being approved, put on hold, or denied.
Instructor: The requirements need to be analyzed to sort out all the necessary conditions to approve the request to enroll, as well as when to hold and when to deny. A decision table may be a helpful tool.

26. Needs Statement 4
To allow the customer check out, the cashier must scan every item, apply the coupons - some may be applicable, and some may not - and then allow different forms of payment for the purchase.
What do the students say?

27. Needs Statement 4
To allow the customer check out, the cashier must scan every item, apply the coupons - some may be applicable, and some may not - and then allow different forms of payment for the purchase.
The use case should illustrate the sequence of interaction between the cashier and the register system: following the scanning to identify each item, then coupons, then form of payment. The end-to-end sequence must cover all possible paths.
Instructor: The detailed specification needs to analyze all the sales conditions such as discounts, applicability of coupons, etc, as well as various combinations of payment methods.

28. Needs Statement 5
When the inventory level is too low, the stored procedure should also check the product overage which may be scrapped for calculating the quantity to be ordered; the order should be reviewed by the responsible manager before sending it out.
What do the students say?

29. Needs Statement 5
When the inventory level is too low, the stored procedure should also check the product overage which may be scrapped for calculating the quantity to be ordered; the order should be reviewed by the responsible manager before sending it out.
The low inventory level triggers an event (a database stored procedure). The procedure should check availability of scrap from previous overage production to determine the quantity to re-order. Then the prepared order goes to the manager's inbox to await approval.
Instructor: Technical terms in manufacturing planning may need to be explained: inventory level, production overage, scrap, etc. The concept of database trigger built by stored procedure also needs some explanation.

30. Questions