Sections 10-11 Flashcards
Types of stakeholders in requirements engineering
Project (testers, business analysists, project manager, devs etc)
Business (project sponsor, product owner, end users, sme’s)
* Note placement of project manager vs owner
Types of requirements
- General (business constraints, business policies, business continuity, legal)
- Technical (hardware, software, interface (interoperability), internet)
- Functional (data entry, data maintenance, procedural, data retrieval)
- Non-Functional (performance, security, access, backup, recovery, archiving, retention, robustness, availability, usability, accessibility, capacity, scalability)
1 and 2 are business requirements, 3 and 4 are solution requirements
What model guides the requirements of the project
OSCAR (Objectives, Scope, Constraints, Authority, Resources) helps create the Terms of Reference or Project Initiation Doc or a clear statement of project intent
Four types of knowledge
- Tacit individual
- Tacit corporate
- Explicit individual
- Tacit corporate
Techniques to get explicit knowledge
Workshops, interviews, doc analysis
Techniques to get tacit knowledge
Protocol analysis, Business activity Model, value stream diagram
What language should be kept out of requirements
Moscow (must should). Shall is ok to have
Two categories of business rules when analysing requirements
- Constraints
- Operational Guidance
Five part framework for requirements establishing
- Elicitation
- Analysis
- Validation
- Documentation
- Management
How to structure class diagrams
Class name on top (Upper case for fist letter)
Attributes in middle (first lower, second capital)
Operations (same spelling as attributes)
What type of requirements are user stories useful for?
Functional requirements
Types of models for showing functional and data requirements
- Use case diagram
- Class models