"Software Modeling and Design" Study Notes (1) - Introduction
Introduction
1. In use case modeling , the functional requirements of the system are defined in terms of use cases and actors
Static Modeling : Provides a structured view of the system. Classes are defined in terms of seven attributes and relationships to other classes.
Dynamic modeling provides a behavioral view of the system. Use cases are realized through interactions between objects. Object interaction diagrams are used to show how objects communicate to achieve a use case. The state-related aspects of the system are defined using state diagrams.
2. Software architecture : separate the overall structure of the system from the internal details of each structure. The emphasis on components and their connections is sometimes called global programming , while the detailed design of individual components is called local programming .
Description at different levels of detail:
At a high level of detail, it is possible to describe how a software system can be decomposed into subsystems.
At a lower level of detail, it is possible to describe how a subsystem is decomposed into modules or components.
The software quality attributes of the system should be considered when designing the software architecture. These attributes relate to how the architecture satisfies important non-functional requirements.
Software architecture is sometimes called high-level design. Software architecture can be described from different views, and it is important to ensure that the architecture satisfies both functional and non-functional software requirements. The software architecture is also the starting point for detailed design and implementation.
3. Terms related to software design
Software Design Notation : A method of describing a software design graphically, textually, or both.
Software design thinking : It is a fundamental thinking that can be used to design a system.
Software design strategy : It is an overall planning and directional guidance for design.
Software Structural Organization Guidelines : Heuristic rules or guidelines used to help designers organize software systems into components.
Software Design Methodology : A systematic approach that describes the sequence of steps used to create a design based on the given application system software requirements.
4. COMET : A UML-based software application modeling and design method.
is an iterative, use-case-driven and object-oriented approach to software development. , covering the requirements, analysis, and design modeling phases of the software development life cycle.
5. The UML model can be a platform-independent model (PIM) or a platform-related model (PSM).
PIM is an accurate model that describes the software architecture before the decision to adopt a specific platform is made.
6. Different software architecture modeling views in UML.
Use case view : It is a functional requirement view, which is the input of software architecture design. Each use case describes a sequence of interactions between one or more actors and the system.
Static View : Describes the architecture in terms of classes and the relationships between classes, where the relationships include association, whole/part (composition or aggregation), generalization/specialization relationships. Represented as a UML class diagram.
Dynamic interaction view : describes the architecture through objects and message communication between objects. This view can also be used to describe the execution sequence of a particular scenario. Represented as a UML communication diagram.
Dynamic state machine view : The internal control and sequencing of a control component can be described by a state machine. Represented as a UML state diagram.
Structural component view : components are used to describe the software architecture, components are interconnected through ports, and the description of supply interfaces and request interfaces is supported. Represented as a UML structured class diagram.
Dynamic Concurrency View : Describes software architecture as concurrent components executing on distributed nodes and communicating via messages. Represented as a UML concurrent communication diagram.
Deployment View : A specific configuration that describes how components in a distributed architecture are allocated to different hardware nodes. Represented as a UML deployment diagram.
7. Concurrent design method of real-time system : Combining early concurrent design, real-time design and early object-oriented design method, emphasizing the construction of information hiding module and concurrent task construction.
Summarize
Introduces object-oriented methods and notation, software architecture design, and UML. It also briefly describes the development history of software design methods, object-oriented analysis and design methods, and concurrent, distributed, and real-time design methods.
practise
(1) What is software modeling - designing software applications before coding
(2) What is the Unified Modeling Language - a standardized graphical language and representation for describing object-oriented models
**(3)**What is software architecture - the overall structure of a software system
**(4)**What is software design notation - graphical or textual description of software
(5) What is software design thinking—a fundamental thought that can be applied to software system design
(6) What is a software design strategy—the overall plan and guidance for developing a design
(7) What are the principles of software structure organization - guidelines to help organize a software system as a set of components
**(8)**What is a software design method - a systematic method for producing a design
(9) What is the Platform Independent Model (PIM) - a precise software architecture model before making a commitment to a specific platform
(10) What is a platform-dependent model (PSM) - an accurate software architecture model mapped to a specific platform