The bare essentials 2 Flashcards
What is requirements engineering (Jarke et al)
Capture, share, represent analyze and prioritize requirements that will be the basis of the design of a project
-> Change to design requirements because of the creation of systems
What are the steps in the RE process?
- Discovery of requirements
(with stakeholders) - Requirement specification
Making the document with the specificaiton / the document itself - Requirement validation and verification
What is requirement validation?
Do the requirements reflect the intentions of the stakeholder?
Am I building the right product?
What is requirement verification?
Degree to which the requirements conform to technical standards of requirement quality
Am I building the product right?
What are the 4 requirement principles proposed by Jarke?
- Intertwine requirements with organizational context
- Evolve designs and ecologies
- Manage through architecture
- Recognize and mitigate against design complexity
What is meant by intertwine requirements with organizational context?
Organizational objectives, forces, cultures influence what they want now and what they want in the future.
-> Will the system tackle emerging goals as well?
What is meant by evolve designs and ecologies?
they mean evolution of requirements
Designs evolve over time, just like requirements. Take that into account and allow for requirement changes. Focus on customer’s preferences
What is meant by manage through architecture?
The architecture of an IT infrastructure of a business is stable. Use this stability as an anchor for design focus.
This will aid stability, scalability and control
The variation points in a system allow for evoluation
What is meant by recognizing and mitigating against design complexity?
Complexity is inherent to a system. Requirements by customers and their behaviour is also difficult to predict.
If it is really complex -> small changes can change the whole system.
-> Use strategic decision making for generating requirements;
-> Constantly try to match stability with the rate of change
What is often used in the beginning of the requirement process?
Use cases. They are behavioural and focus on the functionalities that a system should offer.
-> Functional requirements
What are functional requirements?
Actions that a system should perform
- Assigned to specific components
What are non-functional requirements?
General properties a system should have
system should be adequately protected against….
What ar econstraints?
Contextual conditions
-> System will be used by non-experienced users
What is the principal agent theory?
Asymmetry in information between designers and customers
How do you adress complexity and how not?
- Have a loosely coupled architecture to prevent dependencies;
- Centralization -> entities linked to central entity, not to all entities;
- Standardization
- Re-use of modules
- Buy instead of build
Do NOT add extra man at the last phases.
