CSCI 183 Lecture Notes - Lecture 8: Block Diagram, Sequence Diagram, Use Case
Document Summary
Lecture, reading/chapter/novel/article during class, power point, movies (if need to collect info. ) Architectural design: once interactions between software system and environment have been defined, make architectural design. Object class id: identifying object classes in oo systems, use a grammatical analysis of a natural language description of the system to be constructed. As each scenario is analyzed, the team responsible for the analysis must identify the required objects, attributes, and operations. Reuse: reuse of functions and objects in language libraries, the abstraction level: don"t reuse software directly but rather use knowledge of successful abstractions in the design of your software. Need to adapt and extend the component by adding some code of your own. Involves some kind of configuration of these systems. Integrating from different providers is conflicting and expensive. Design models: show the objects or their classes in a system, show the associations and relationships between these entities, a bridge between the system requirements and the implementation of a system.