5. Process and working structure Flashcards
1
Q
Process
A
A set of interrelated activities performed in a given order to process information or materials
2
Q
The RE process
A
- shapes the information flaw
- communication model between participants
- defines the RE work products to be used or produced
- provides a framework in which RE elicit, document, validate and manage requirements
3
Q
Overall process fit
A
- process might require wp that the RE process must deliver
- terminology in the RE should be aligned
4
Q
Influencing factors
A
- overall process fit
- development context
- stakeholder availability and capability (exploitative, continuous)
- shared understanding (the more the more light weight)
- complexity and criticality
- constraints (customer or regulator)
- time and budget available
- validity of requirements (likely to change)
- experience of requirements engineer
5
Q
Development context
A
- customer-supplier-user relationship
- development type
- contract
- trust
6
Q
Development type
A
- a supplier specifies and develops a system for a specific customer
- an organization develops a system with the intention to sell it as a product or service to many customers in a certain market segment
- a supplier configures a system for a customer from a set of ready-made components
- a vendor enhances and evolves an existing product
7
Q
Contract
A
- is there a contract or similar agreement that formal defines deliverables, costs, deadlines, responsibilities …
- fixed or iterative functionality …
8
Q
Process facets
A
- custom-specific vs market oriented (development type)
- prescriptive vs exploratory (deals with purpose and role of requirements)
- linear vs iterative
9
Q
Linear RE process
A
- requirements are specified up front in a single phase
- mostly heavyweight
- produce comprehensive requirements specification that requires no or only little adaptation or few changes during the design and implementation of the system
10
Q
Criteria for choosing a linear RE process
A
- Dev process is plan driven and linear
- Stakeholders are available, know their requirements and can specify them up front
- a comprehensive requirements is required as a contractural basis for outsourcing or tendering the design and implementation of the system
- regulatory authorities require a comprehensive formally released requirements specification at an early stage of the development
11
Q
An iterative RE process
A
- specified incrementally starting from initial goals
- interwine the specification of the requirements with the design and implementation of the system
- lightweight process
12
Q
Criteria for choosing an iterative RE process
A
- Dev process is iterative and agile
- many requirements are not known up front but will emerge and evolve during the development of the system
- stakeholders are available such that short feedback loops can be established as a means of mitigating the risk of developing the wrong system
- the duration of development allows more than one iteration
- ability to change requirements easy is important
13
Q
Prescriptive
A
- requirements constitute a contract: all requirements are binding and must be implemented.
- create a requirements specification that can be implemented with no or little interaction between stakeholder and developer
14
Q
Explorative RE
A
- goals are not know a priory, concrete requirement have to be elicited => have to be explored
15
Q
Criteria for choosing a prescriptive RE process
A
- customer requires a fixed contract for system development, often with fixed functionality, scope, price and deadline
- functionality and scope take precedence over cost and deadlines
- development of the specified system may be tender or outsourced