Reference no: EM132992324
Activity of Lesson - 6
Review Questions
1. What is a requirement? What is requirements engineering?
2. Briefly explain the different types of requirements?
3. How to distinguish the user requirement definition and the system requirement definition? Explain with examples.
4. What are functional requirements? Give examples.
5. What are non-functional requirements? Give examples (Use the types of non-functional requirements).
6. What is requirements imprecision?
7. Why completeness of the requirements is important in software engineering?
8. List and briefly explain metrics for non-functional requirements.
9. What are the domain requirements? Explain briefly.
10. List the explain he different users of requirements document.
11. List and explain the structure if the requirement specification.
12. What is a structured specification?
13. What is a tabular specification?
14. Explain the spiral view of the requirements engineering process.
15. List and explain the problems of requirements analysis.
16. Explain the requirements elicitation and analysis process.
17. What are the principles of the agile methods? Briefly explain each.
18. What is ethnography?
19. Explain the steps of ethnography and prototyping for requirements analysis.
20. List and explain what you ae checking in requirements.
21. What are the requirements validation techniques?
22. What is requirements evolution?
Practice Problems (Submit only Practice problems)
P.6.1. Discover ambiguities or omissions in the following statement of requirements for part of a ticket-issuing system: "An automated ticket-issuing system sells rail tickets. Users select their destination and input a credit card and a personal identification number. The rail ticket is issued and their credit card account charged. When the user presses the start button, a menu display of potential destinations is activated, along with a message to the user to select a destination. Once a destination has been selected, users are requested to input their credit card. Its validity is checked and the user is then requested to input a personal identifier. When the credit transaction has been validated, the ticket is issued."
P.6.2. Write a set of non-functional requirements for the ticket-issuing system, setting out its expected reliability and response time.
P.6.3. Suggest how an engineer responsible for drawing up a system requirements specification might keep track of the relationships between functional and non-functional requirements.
P.6.4. Using your knowledge of how an ATM is used, develop a set of use cases that could serve as a basis for understanding the requirements for an ATM system.
P.6.5. When emergency changes have to be made to systems, the system software may have to be modified before changes to the requirements have been approved. Suggest a model of a process for making these modifications that will ensure that the requirements document and the system implementation do not become inconsistent.
Attachment:- Week 6 Tutorial.rar