|
Outline:
|
Structure of the tutorial
|
|
|
Requirements Engineering : Outline
|
|
Goals:
|
What we want learn?
|
|
|
|
Problem:
|
Application of the theory to a problem from the real world
|
|
|
Requirements Engineering: Problem and Solution
|
|
Theory:
|
|
|
Introduction:
|
Structuring the knowledge until now
|
|
|
RAD, Levels of descriptions
|
|
Essence:
|
Explaining the concept
|
|
|
Process for ARENA,Requirements Elicitation activities
|
|
Demo:
|
Showing how it works
|
|
|
REQuest : Live demonstration
|
|
Exceptions:
|
What shall we do if something goes wrong?
|
|
|
REQuest: Guidelines
|
|
Summary:
|
Repeating the key points
|
|
|
Putting all together, Next steps
|
|
Next Steps:
|
- Meet with your development team as soon as possible
- Login to REQuest with your Lotus Notes account
- Add actors, use cases and services
- Discuss, negotiate and resolve questions
- Write one complete scenario per team (that is one possible example of the system in use)
|
|
|
Further readings:
|
-
Bruegge B., Dutoit A.: Object-Oriented Software Engineering: Conquering Complex and Changing Systems, Prentice Hall, 2000
|
|
|
Glossary
|
Glossary for Requirements Engineering Tutorial
|
|
|
|
|
