COMP2007-Sw Modelling Flashcards
0
Q
Sw modelling why bother
A
Commercial impact Impact on economy, Security, Safety Certification
1
Q
Software modelling
A
Sw model= Description textual or visual Aspects of software system; Requirements Architecture Behaviour Deployment. Development process model Requirements model Concurrency model Sw modelling=practice of creating and analysing sw models!
2
Q
Sw modelling-who uses it
A
Can be uses by different peeps to; Document important decisions Communicate about software Validate software Generare software
3
Q
Sw modelling-problems
A
Incompleteness Inconsistency Inadequacy Ambiguity Lack of traveability Uninteligibility Un-measurability Poor structure Over specification Noise
4
Q
Sw modelling-perspecrives
A
Different models present system from different perspectives External; shows system's context or environment Process; Shows system dev process + activities supported by it Behavioural; Showing beh of system Structural; Showing system data or architecture
5
Q
Sw modelling challenges
A
Modelling Non funct reqs v diff Modelling is diff fm methodology May producte too much docum Sys models too detailed and diff for users to understand Maintainability still a major issue
6
Q
Modelling-up front remarks
A
Trial and error process Process not same as outcome Interaction btwn; Requirements engineering Architecting and Design Iterative process
7
Q
Modelling principles
A
Abstraction:
Focus on main properties and manage complexity
Modularity, coupling & cohesion
Limit complexity (complex systems, simple models!)
Hierarchical structure and model decomposition
8
Q
Which model is right
A
Commercial needs;
Size od cust base
Who pays
Intellectual property issues
- are there patents
- does employer rely on IPR (trade or sell)
How much documentation to make prog useful
How much support:
Mean vs. Variance
9
Q
System modelling techniques
A
Classic;
- entity-relationship modelling
- finite state machines
- data flow diagrams
OO modelling-variety of UML diagrams
Formal modelling methods
