vault backup: 2023-09-27 16:56:46
This commit is contained in:
parent
9929ef7d48
commit
f3366c9db8
3 changed files with 107 additions and 26 deletions
|
@ -21,3 +21,31 @@ Requirements engineering seeks to ensure the three following objectives:
|
|||
|
||||
|
||||
## Activities
|
||||
Process Scheme: [[process.excalidraw]]
|
||||
|
||||
### 1. Inception
|
||||
- Initiation of the process, based on some necessity or business expectation.
|
||||
- At the end, the requirements engineer should be able to describe what is the client vision and return on investment.
|
||||
- One must also evaluate if what the client needs is already available in the market.
|
||||
|
||||
### 2. Elicitation
|
||||
- This activity handles how requirements should be captured.
|
||||
- The requirements elicitation techniques must:
|
||||
1. identify the sources of requirements;
|
||||
2. aid the various stakeholders to correctly describe the requirements;
|
||||
- This activity is inherently communicational, since it requires an in-depth interaction with the stakeholders.
|
||||
- Requirements elicitation techniques:
|
||||
1. Interview
|
||||
2. Survey
|
||||
3. Introspection
|
||||
4. Ethnography
|
||||
5. focus group
|
||||
6. cooperative work
|
||||
7. domain analysis
|
||||
8. object-orientation
|
||||
9. prototyping
|
||||
10. scenario
|
||||
11. goal modelling
|
||||
12. persona
|
||||
|
||||
### 3. Elaboration
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue