Software engineering system modeling and architectural view

Context models

used to illustrate the operational context of a system - they show what lies outside the system boundaries

Class diagrams

used when developing an object-oriented system model to show the classes in a system and the associations between these classes.

dynamic model

the organization of the system when it is executing

Types of UML Diagrams

Activity, use Case, sequence, class, and State diagrams

Use case modelling

Each use case represents a discrete task that involves external interaction with a system. Actors in a use case may be people or other systems.

Generalization

Generalized view of class system and displaying the inheritance hierarchy

Architectural models

Show the system and its relationship with other systems

Data stimuli

Some data arrives that has to be processed by the system.

Event Stimuli

Some event happens that triggers system processing. Events may have associated data, although this is not always the case.

System modeling

the process of developing abstract models of a system, with each model presenting a different view or perspective of that system

UML

Unified Modeling Language

Structural Models

display the organization of a system in terms of the components that make up that system and their relationships.

Existing system models

help clarify what the existing system does and can be used as a basis for discussing its strengths and weaknesses. These then lead to requirements for the new system.

New system models

help explain the proposed requirements to other system stakeholders. Engineers use these models to discuss design proposals and to document the system for implementation.

Interaction models

helps to identify user requirements. Typically use case and sequence diagrams

In a model-driven engineering process...

it is possible to generate a complete or partial system implementation from the system model

Behavior models

models of the dynamic behavior of a system as it is executing. They show what happens or what is supposed to happen when a system responds to a stimulus from its environment.

State Machine Models

show system states as nodes and events as arcs between these nodes. When an event occurs, the system moves from one state to another.

Data driven models

show the sequence of actions involved in processing input data and generating an associated output.

Event driven modeling

shows how a system responds to external and internal events.

Class aggregation model

shows how classes that are collections are composed of other classes

Sequence diagrams

shows the sequence of interactions that take place during a particular use case or use case instance

Static model

shows the structure of the system design

Modality

specifies the necessities of relationship to exist

Cardinality

specifies the number of occurrences of entities

External perspective

where you model the context or environment of the system

behavioral perspective

where you model the dynamic behavior of the system and how it is processed by the system.

interaction perspective

where you model the interactions between a system and its environment, or between the components of a system.

structural perspective

where you model the organization of a system or the structure of the data that is processed by the system