19149265
Descripción
Fichas por Mikael Caselitz, actualizado hace más de 1 año
|
Creado por Mikael Caselitz
hace alrededor de 5 años
|
|
| Pregunta | Respuesta |
| Requirements elicitation | purpose of a system |
| Requirements analysis |
- create a model of the system, which is correct, complete, consistent and verifiable
Image:
Image (binary/octet-stream)
|
| Functional vs. object oriented decomposition | Functional decomposition: -System decomposed into functions -Functions into smaller functions Object oriented decomposition: -System decomposed into classes -Classes into smaller classes |
| UML use case diagram: elements |
Image:
Image (binary/octet-stream)
|
| Abbot technique |
From problem statement of the customer
Image:
Image (binary/octet-stream)
|
| Knowlege sources | Application 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 |
| Typical software developement activities |
Image:
Image (binary/octet-stream)
|
| Types of requirements: Functional requirements | -Functionality: what is the software supposed to do -External interfaces: interaction with people, hardware, software |
| Types of requirements: Non-functional requirements | Quality requirements: URPS -Usability (steps required to get somewhere) -Reliability (Robustness, Safety) -Performance (Response t., Availability...) -Supportability (Adaptabiliy, Maintanence, Portability) (Constraints : Operation enviroments...) |
| Scenario build | 1) Name: 2) Participating actors: 3) Flow of events: - Mit konkreten Namen etc. |
| Textual use case description | 1) Name 2) Participating actors 3) Entry condition 4) Flow of events 5) Exit condition 6) Special requirements |
| From Uml class diagrams to UML communication diagrams |
Image:
Image (binary/octet-stream)
|
¿Quieres crear tus propias Fichas gratiscon GoConqr? Más información.