Please enable JavaScript.
Coggle requires JavaScript to display documents.
Software Engineering Y2 (Software Lifecycle (Waterfall (Separate phases…
Software Engineering Y2
Software Lifecycle
Activities - Specification, Design, Validation and Evolution
-
-
Waterfall
-
- Requirements analysis - What services are required, feasibility study etc. Outputs: Feasibility report, System models, Requirements
- System and software design - Design the system to match the specification. Outputs: Specification designs
- Implementation and unit testing - Create executable code and test each part of the system.
- Integration and system testing - Testing system as a whole. Acceptance tests - Getting the client to test it.
- Operation and maintenance - Final documentations etc.
Incremental Development - Development is broken down and delivered as increments, with the important parts of the system first. Lower risk of failure, important parts of the system get the most testing, client feedback is available earlier.
Spiral Development - No backtracking. Loops are not fixed, so can be whatever the system needs at the time. Sections: Objective, Risk assessment, Development and validation, Planning for next phase
-
Static UML Diagrams
Use Case
Have user's (actors) of the system and tasks they must undertake. Then define relationships between these
-
-
-
-
Class Diagram
-
Properties - Class name, attributes and methods. + means public. # means private. Eg. #title - String
-
Data Driven Design - Identity all of the data, then divide into classes. Nouns are candidate classes. Verbs are candidate operations
-
Relationships - bidirectional (straight line), unidirectional (open arrow), composition (filled diamond), aggregation (open diamond), Inherits (open triangle arrow)
-
-
-
Component Diagram
-
Each component has data/methods it requires to complete and data that it produces. They can get glued together as lollipops and socket
-
Deployment Diagram
Has nodes which are software/hardware components, which are associated together with lines.
Dynamic UML Diagrams
Sequence Diagram
Describe the objects and messages they pass between each other, in time order
-
Conditional boxes such as opt, if, while etc. Has guards
-
State Diagram
Describes the different states an object can be in, and the different ways they transfer between them. Eg. a book can have states: on shelf, on loan, reserved, damaged etc.
-
-