The document discusses system modeling, which provides a framework for understanding system components and their functionalities. It covers various perspectives, including context, behavioral, and data architecture, and details the creation and importance of data flow diagrams and state transition diagrams. Additionally, it explains data and object modeling, highlighting the relationships and attributes of data objects within a system.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
4 views
SE-ch2
The document discusses system modeling, which provides a framework for understanding system components and their functionalities. It covers various perspectives, including context, behavioral, and data architecture, and details the creation and importance of data flow diagrams and state transition diagrams. Additionally, it explains data and object modeling, highlighting the relationships and attributes of data objects within a system.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17
SYSTEM MODEL
BY – ER. SURAJ AWAL
SYSTEM MODELLING
• System model provides a model of system components that
sets foundation for further development. • Helps the analyst to understand the functionality of the system. • Provides a medium to communicate with the customers. SYSTEM MODELLING
• The model can represent different perspective:
1. System context or environment (external perspective) 2. Behavior of the system (Behavioral perspective) 3. System or data architecture (Structural perspective) CONTEXT MODEL
• A model that establishes the information boundary between the
system being implemented and the environment in which the system is to operate. • It defines all external producers of information used by the system, all external consumers of the information created by the system and all entities that communicate through the interface. DATA FLOW DIAGRAM
• Graphical representation that depicts information flow and the
transforms that are applied as data move from input to output • Used to represent a system at any level of abstraction • Partitioned into levels that represent increasing information flow and functional detail DATA FLOW DIAGRAM (LEVEL 0)
• Also known as context diagram
• Represents the entire system element as a single entity with input and output indicated by incoming and outgoing arrows respectively DATA FLOW DIAGRAM (LEVEL 1 AND LEVEL 2)
• The overall system entity is partitioned into additional
processes to reveal more detail • Each process in level 1 DFD is a sub function of the overall system • For level 2 DFD, the process in level 1 is further partitioned into additional sub processes DATA FLOW DIAGRAM (THINGS TO CONSIDER)
• Information flow continuity must be maintained
• Input and output to each refinement must remain the same in all the levels • This concept is known as DFD balancing • Important for development of consistent models CREATING DATA FLOW DIAGRAM (DFD)
• The level 0 DFD should depict the system as a single entity
• Primary input and output should be carefully noted • Refinement should begin by isolating candidate processes, data to be represented at the next level • All arrows and entity should be labeled with meaningful names • Information flow continuity should be maintained • One entity should be refined at a time BEHAVIORAL MODELLING
• Represents the operational principle for all requirements analysis
methods • Models the dynamic behavior of the system as it is executing • Shows what happens or what is supposed to happen when a system responds to a stimuli • One of the most important behavioral modelling technique is state transition diagram STATE TRANSITION DIAGRAM
• State transition diagram depicts the behavior of system by indicating
the state change of the system on occurrence of particular action • Represents event driven modelling • Assumption : System has finite number of states and events may cause a transition from one state to another • A state is any observable mode of behavior STATE TRANSITION DIAGRAM (MICROWAVE OVEN) DATA AND OBJECT MODEL
• Depicts the data objects to be processed by the system
• Indicates the composition of each data object and attributes that describe the object • Indicates the location of the data objects within the system and also the relationships between the objects and the processes that transform them DATA AND OBJECT MODEL
• Consists of three information – data object, attributes and
relationship • Data object is a representation of any composite information (Eg: person, car) • Attributes define the properties of a data object (Eg: attributes of person object would be name, address, age; attributes of car object would be model, make, color, body type) DATA AND OBJECT MODEL
• Relationships indicates the way by which data objects are
interlinked to one another (Eg: person object owns car object) • ERD (Entity Relationship Diagram) is one of the data modelling technique ENTITY RELATIONSHIP DIAGRAM THANK YOU!