SEG 3102 Study Guide - Midterm Guide: Common Object Request Broker Architecture, Component Object Model, Information Hiding

• School: University of Ottawa
• Department: Software Engineering
• Course: SEG 3102
• Professor: Stephane Some

Document Summary

Physical: use case view: show requirements (model: uml uc, uml interaction diagrams, text, logical view: 1. support requirements; 2. include key abstractions from the domain model and mechanisms; 3. Software developers & project manager; 4. model: uml component, uml package diagrams: physical view: 1. Physical topology and deployment of system over processing nodes; 2. address availability, reliability (fault-tolerance), performance (throughput) and scalability; 3. System engineers; 4. model: uml deployment diagrams: architecture degradation: 1. Architectural erosion: violate: prescriptive architecture: designed arch. Supporting s-d: module definition: sub-division of the system unit of code or data (ex. function/procedure, class, component, subsystem, layer), modules" properties: 1. Replaceable within its environment; 3. has interfaces and depends (uses) interfaces; 4. can be composed of other components; 5. several components can be composed based on interfaces match: component models: 1. Microsoft component object model (com/dcom), . net model; 2.