Tutorial 2
1. During ‘Elicitation and Analysis Process’ activities, eliciting and understanding
requirements from system stakeholders is a difficult process. Explain TWO (2) reasons and
give example for each of them based on this case study?
The reasons is stakeholders don’t know what they really want. Based on case
study , the stakeholder don’t either they want to track the inventory or handle the sales.
The reason is stakeholders express requirements in their own terms. Based on
case study, the stakeholder state the requirement they want in their own terms and its will
confuse the software engineer.
2. From the given user requirement “the system shall able to track inventory and provide
related report every month”. Please construct TWO (2) possible system requirement related
to that user requirement.
1.1 On the last working day of each month. A summary of sales, remains inventory of stock
shall be generated.
1.2 A report shall be created for each store and shall list the individual toys name, the toys
inventory.
3.Describe THREE (3) requirements validation techniques and give example for each of
them based on this case study? Which technique that you think the most suitable to validate
the requirement from the case study? Justify your answer.
First, requirements reviews. Based on case study, we can do a manual analysis of the
requirement of the company to know what they want.
Second, prototyping. Based on case study, we can use an executable model of the
system to check the requirement of the company can function or not.
Third, test-care generation. We can developing some test based on the requirement
to check testability of the software.
I think that prototyping is the most suitable because the time given is short. So we can
find a prototype model of the software and customized it.
4. Non-functional requirements often constrain the system being developed and the
development being used. Give TWO (2) types of non-functional requirements. Write ONE
(1) non-functional requirements statement for each type that has been mentioned for the
proposed system
Firstly, performance requirements. The shutdown time must not excceed than 20
seconds.
Second, security requirements. Only the staff of toy store can log in into the system.