01 Software and UML Flashcards
1
Q
software engineering approaches
A
- water fall
- incremental
- evolved
2
Q
waterfall model flow
A
- communication
- planning
- modeling
- construction
- deployment
3
Q
when should we use waterfall model
A
- well defined requirements
- adequate resources
- good team expertise
- not too large project
- no urgent need
4
Q
Incremental model flow
A
- communication
- planning
- construction
- deployment
- incremental 1
5
Q
when should we use incremental model
A
- requirements reasonably defined
- quick prototype
- new technology involved
- team is not very skilled
6
Q
evolutionary process models
A
- designed to accommodate software product changing over time
- combination of iterative and incremental
- breakdown work into smaller chunks, prioritise chunks
- spiral model, prototyping model
7
Q
prototyping model flow
A
- communication
- quick plan
- model quick design
- prototype construction
- deployment, evaluation and feedback
8
Q
when should we use prototyping model
A
- small, low cost system
- unclear, incomplete requirement
- active customer involvement
- lack of experience
9
Q
spiral model
A
- communication
- planning
- modeling
- construction
- deployment
each phase has a milestone
10
Q
when should we use spiral model
A
- unclear requirements
- able to tolerate high risk
- large scale and complex
- frequent releases
11
Q
what is UML modeling
A
represent system using graphical notation
12
Q
UML models
A
structure model - class diagram
behavior model
- use case diagram
- activity diagram
- sequence diagram
- state diagram
13
Q
structure models
A
display organization of components making up the system and their relationship
14
Q
behavioral model
A
show dynamic behaviour of a system, how it respond to stimulus
stimulus types
- data: to be processed by system
- events: triggers the system
15
Q
data driven modeling
A
shows entire sequence of actions from initial input to corresponding output
