1 Flashcards
Vad är en Requirement engineering mål när man jobbar:
To understand the customers goal and needs regarding future software system.
Reasons why software systems evolves over time:
Changes with:
-law, regulations (abroad),
-policies/ rules (in organizations)
Emergence of:
-technology, innovation, new competing software solutions
När software system evolevs, 4 challenges appear from stakeholders:
- System complexity increase - quality, functions after costumers needs
- Pressure to reduce cost - companies want lower product prices to reduce their cost and system and the system must be developed and produced at lower cost.
- Shorter development time - increasing competitions, and the customer want a faster and innovated system functions in a short time.
- Higher quality demands: need to have high quality demands for the company.
Sum: higher level of quality, shorter time frame and lower cost.
Sucessfactors for planning a project:
1.Good requirements
2. user involved
3. Good planing
4. Small milestones
5. educated people
failure factors in a project:
1.Changing requirments
2. Incomplete requirments
3.Lack of planning
4. Lack of resources
Problem and consequenses with bad RE
- some features might work but not all in the system
- customer get something else than expected
- Lack of prioritering of the requirments, problem to design the system
- postpone relese date, money waste etc.
The reeingenering frameworks of concept:
- Requirment
- Stakeholder
- Requirment documentation
- RE activites
- What is Requirment (IT definition):
- What is the main types of Requirment
- What is requirement in IT?
Describe a condition (capability)that the system must meet. - Main types of system requirements are: (FQL)
-functional requirement : task of what the system should achieve
-Quality requirement: Defines a quality property/attribute of the entire system or of a system
component , service , or function .
-Constraints/limits requirement: limited the way the system should be developed.
- What is a stakeholder?
-(System) stakeholders are the persons or the organizations that have an interest in the system to be developed. they commonly have requirements for the system.
- Requirments document
What is :
3.1 Requirement document
3.2 Requirment document descirbes (5 things)
3.1 A formal documentation to stakeholders of requirments for the system.
3.2 FQLIB
-Functions for the system
- The quality and limits for the system
- Business goal that system should support
- Integrate with other system
- Requirment acitivtes
Name 3 core activities from requirements engineering:
Name 2 sectional acitivites that supports these 3 core
- Elicitation: improve the understanding of requirements. (interview)
- Documentation: specify requirments, (brainstorming)
- Negotiation: approved/change requirements from diffrent stakeholders needs.
Sectional activites:
- Validation: prirites the requirments and sort them
- mangement: change and work with the requirments.
Methods: For RE
What is:
-Planned driven development?
- Agile development?
- PDL: well formulated document for each activite and step by step process (predicteable projects)
- Agile: Interactive activites and tight communication with customer over the development cycle. rapid and flexible response to changes through development.
