Flashcards
Requirements
Cards in this deck (14)
- 1Requirements elicitation is difficult due to (4 reasons)...1. Stakeholders not knowing what they want from a computer system
2. Stakeholders expressing requirements in their own terms/jargon
3. Different stakeholders expressing requirements differently
4. Political factors (preserve stakeholder's self importance) - 2The Requirements Elicitation and Analysis process is cyclical and consists of the following four steps ...1. Discovery
2. Classification and Organisation
3. Prioritisation and Negotiation
4. Specification - 3Requirements can be classified according to the ... criteria, and give a description of each categoryMoSCoW
Must - minimal usable subset of requirements, project deemed failure if these not met
Should - Physical workaround possible but causes large inconvenience/pain
Could - same as Should but with less inconvenience/pain
Would - desired but not delivered now, help to clarify scope and manage expectations - 4Requirements Validation is concerned with ... and is formed of the following checks (VCCRV)concerned with 'have we got requirements right'
Validity - reflect real needs of users
Consistency - no conflicts in requirements
Completeness - all functions/constraints as intended by users
Realism - implementable within budget/schedule
Verifiability - in order to reduce potential for disputes - 5A Software Process is ... and consists of (SDIVE) ...A Software process is a set of structured activities to develop a software system
Consists of Specification, Design, Implementation, Validation and Evaluation - 6Requirements Engineering establishes .. Process is ...what services are required and what the constraints on system operation and development
Feasibility Study -> Requirements Elicitation and Analysis -> Specification -> Validation - 7User Stories (for Agile) are used to decide ... and consist of ..... what functionality is required
consist of Card, Conversation and Confirmation - 8A good user story is (INVEST) ...Independent
Negotiable
Valuable to Users
Estimable
Small
Testable - 9User Requirements are ...1. High Level
2. written in Natural Language, accompanied by Diagrams
3. Written for customers - 10System Requirements are ...1. Detailed/low-level
2. Formed in structured document with detailed descriptions of system functions, services and operational constraints
3. Defines what should be implemented
4. Read by end users and technical staff - 11The problems with Natural Language specification are that its ...1. ambiguous
2. overly-flexible
3. lacks modularisation - 12Functional Requirements are ...1. Statement of services system should provide
2. How system should react to a particular input
3. How System should behave - 13Non-Functional Requirements are ...1. Constrainst (such as timing, constraints on development process, standards etc.)
2. Refer to the qualities of the software, which need to be specific, quantifiable and testable - 14—
Information
- Description
- Bachelors Degree Systems and Software Analysis (Unit 6 - Requirements and Use Case Diagrams) Flashcards on Requirements, created by Jorden Allcock on 06/03/2016.
- Created by
- Jorden Allcock
- Views
- 0
- Rating