Karteikarten
Requirements analysis
Karten in diesem Stapel (12)
- 1Requirements elicitationpurpose of a system
- 2Requirements analysis- create a model of the system, which is correct, complete, consistent and verifiable
- 3Functional vs. object oriented decompositionFunctional decomposition:
-System decomposed into functions
-Functions into smaller functions
Object oriented decomposition:
-System decomposed into classes
-Classes into smaller classes - 4UML use case diagram: elements
- 5Abbot techniqueFrom problem statement of the customer
- 6Knowlege sourcesApplication knowledge: end user/application domain know abstraction for application domain
General word knowledge: generic knowledge and intuition
Solution domain: S. d. experts know abstractions in solution domain - 7Typical software developement activities
- 8Types of requirements: Functional requirements-Functionality: what is the software supposed to do
-External interfaces: interaction with people, hardware, software - 9Types of requirements: Non-functional requirementsQuality requirements: URPS
-Usability (steps required to get somewhere)
-Reliability (Robustness, Safety)
-Performance (Response t., Availability...)
-Supportability (Adaptabiliy, Maintanence, Portability)
(Constraints : Operation enviroments...) - 10Scenario build1) Name:
2) Participating actors:
3) Flow of events:
- Mit konkreten Namen etc. - 11Textual use case description1) Name
2) Participating actors
3) Entry condition
4) Flow of events
5) Exit condition
6) Special requirements - 12From Uml class diagrams to UML communication diagrams
Informationen
- Beschreibung
- Der Nutzer hat seine Fachbereichs-Information gelöscht. Karteikarten am Requirements analysis, erstellt von Gelöschter Nutzer am 15/09/2019.
- Erstellt von
- Gelöschter Nutzer
- Aufrufe
- 26
- Verlauf
-
- Erstellt von Mikael Caselitz · 2 Sep 2019
- Kopiert von Mikael Caselitz · 15 Sep 2019
- Bewertung