CS 425/625 Software Engineering System Models Based on Chapter 7 of the textbook [Somm00] Ian Sommerville, Software Engineering, 6th Ed., Addison-Wesley, 2000 and on Ch7 PowerPoint presentation available at the book’s web-site: www.comp.lancs.ac.uk/computing/resources/IanS/SE6/Slides/index.html September 29, 2003

Outline System Models Contextual Models Behavioral Models Data Models Object Models

Introduction. System models are used to specify the system to be built in a more detailed way Typically, system models are graphical descriptions of the system, its services and its constraints Various perspectives for system modeling: Context Behavior Structure

.Introduction The production of system models is usually guided by methods, e.g., SSA (Structured Systems Analysis), SADT (Structured Analysis and Design Technique), OMT (Object Modeling Technique), etc. In practice, various models, not bound to methods, could be combined to describe the system and its requirements Main types of system models: Data Processing Models Composition Models Architectural Models Classification Models Stimulus-Response Models

Context Models… Contextual models show the system and its environment Ideally, the boundaries between the system and its environment are identified clearly Dependencies between the computer-based system and systems from the environment are highlighted

.Context Models.. Various models can be used for context modeling: Very simple, high level architectural models show the system and its connections with environmental components High level process models indicate main process activities High-level data-flow diagrams depict data transformations and data transfers

..Context Models. Example of architectural model for system context specification: an ATM system and its environment [Fig. 7.1, Somm00]

…Context Models Example of process model for system context specification: an equipment procurement system [Fig. 7.2, Somm00]

Behavioral Models……. Behavioral models specify the overall behavior of the system: Data-flow models (or data-flow diagrams, DFD) are suitable for data-driven systems State machine models (or stimulus-response models) are appropriate for event-driven systems

.Behavioral Models…... Data-flow models show the system in terms of: Data stores [graphical representation: rectangles] Data transformations (data processing operations) [graphical representation: rounded rectangles] Data movements (data transfers) [graphical representation: directed lines]

..Behavioral Models….. State machine models describe system behavior using two main modeling elements: States [represented using rounded rectangles] Transitions [shown as directed links between states]

…Behavioral Models.... A DFD example: an order processing system [Fig. 7.3, Somm00]

….Behavioral Models… State machine diagrams depict the behavior of the system in terms of responses to events Real-time systems are essentially event-driven systems The system is assumed to be in one of its possible states at any given moment of time. A transition to another state is triggered by the occurrence of an event David Harel’s statecharts are included in the UML (Unified Modeling Language); DFDs are not part of UML

…..Behavioral Models.. Example of state machine diagram: A microwave oven controller [Fig. 7.5, Somm00]

…...Behavioral Models. The statecharts notation used in UML allows: Specification of composite states (states that have sub-states), thus supporting model decomposition Description of actions performed while in a state: Entry actions State actions (activities) Exit actions Description of transitions: Events that trigger the transition Conditions under which transitions occur Actions on transitions, if any

…....Behavioral Models Example of composite state: microwave oven [Fig. 7.7, Somm00]

Semantic Data Models… Data models describe the logical structure of data processed by the system The Entity-Relationship-Attribute model, ERA (also known as Entity-Relationship model, ER) shows: Entities in the system Relationships between entities Attributes of entities and relationships Cardinality constraints (e.g., “one” or “many”)

.Semantic Data Models.. Data dictionaries are repositories of information pertaining to the elements of the system models. They are useful to manage the namespace of the system models as well as to supply a cross-reference tool for analysis, design, implementation, and evolution.

..Semantic Data Models. An ERA example: a software design description [Fig. 7.8, Somm00]

…Semantic Data Models Data dictionary: examples of data entries [Fig. 7.9, Somm00]

Object Models…….. Objected-oriented modeling is centered around the concepts of object and class An object is an entity described in terms of attributes (data) and operations (functionality) A class is a template for objects that have similar features (attributes and operations). More exactly, the objects that belong to the same class have the same structure and behavior, e.g., davidsAlarmClock is an object (instantiation) of the class AlarmClock

.Object Models……. The distinguishing principles of object-oriented (OO) technology are: Encapsulation Inheritance Polymorphism

..Object Models…… Objects provide more natural ways to model real-life entities Both structure (class diagrams) and behavior (e.g., interaction diagrams and state diagrams) can be described A class diagram shows: Classes Relationships between classes Constraints Annotations

…Object Models….. The value of OO comes from: Greater modeling power Increased reusability and extensibility Improved control of complexity

….Object Models…. Example of class hierarchy: a library system [Fig. 7.10, Somm00]

…..Object Models… Another example of class hierarchy: Library users [Fig. 7.11, Somm00]

……Object Models.. Example of multiple inheritance [Fig. 7.12, Somm00]

…….Object Models. Example of class structure with aggregation [Fig. 7.13, Somm00]

……..Object Models Example of sequence diagram [Fig. 7.14, Somm00]