Eng Large Software Systems

Eng Large Software Systems

1. Metrics

   • Non-trivial
   • Intended for release
   • Benefits from proper practices
     • e.g. UML
   • Not difficult to use with standard development tool
     • e.g. IDE

2. Reverse Engineering

   • Produce a class diagram from source code
     • Class Diagram represents the static view of software and can be used as a base for other UML diagrams such as sequence diagrams. Useful to show how changes can effect classes through dependencies and how you can reduce coupling through interfaces.
   • Used to increase longevity of the system
   • Re-documentation
   • Design Discovery

3. Sequence Diagrams

   • How objects collaborate to complete a task
   • Elaborate use case diagrams
     • Bridges gap between high level view and more technical formal view that programmers need.
   • Guide for implementation
   • Test whether implementation is feasible
   • Interaction Frames
     • alt:Alternative  opt:Optional par:Parallel loop neg:Negative region:Critical Region ref:Reference sd:Sequence Diagram