


Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
Bugs and Errors Bugs and Errors
Typology: Lecture notes
1 / 4
This page cannot be seen from the preview
Don't miss anything!
Chapter 4: Requirements Engineering Your name: Answer all questions. 1 mark per question
What is the software requirements document?
What is the distinction between the termsʼ shallʼ and ʻshouldʼ in a user requirements document, which is written in natural language?
What are the main advantages of using a standard format to specify requirements?
What are the principal stages of the requirements engineering process? The official document that defines the requirements that should be implemented by the system developers. All requirements have the same format so are easier to read, The definition of form fields mean that writers are less likely to forget to include information Some automated processing is possible.
Requirements elicitation and analysis
Requirements specification
Requirements validation ʻ Shall ʼ normally indicates a mandatory requirement ʻ Should ʼ indicates a desirable but not essential requirement.
What checks should be applied during requirements validation?
List three requirements validation techniques?
What is requirements management?
What are the stages in the requirements change management process?
Validity checks
Consistency checks
Completeness checks
Realism checks
The verifiability of the requirements should be assessed.
Requirements reviews
Prototyping
Test-case generation The process of managing changes to requirements during requirements specification and after the system has gone into use. a. Problem analysis and change specification b. Change analysis and costing c. Change implementation