Lab 5 CPIT 250 System Analysis and Design

Outline System Development Life Cycle System Design Phase –UML Overview Diagrams UML Class diagram CPIT 250 System Analysis and Design

System Analysis and Design Different phases of system development life cycle: CPIT 250 System Analysis and Design

System Design Phase During the Design Phase, the system is designed to satisfy the requirements identified in the previous phases. The requirements identified in the Requirements Analysis Phase are transformed into a System Design Document that accurately describes the design of the system And that can be used as an input to system development in the next phase. CPIT 250 System Analysis and Design

System Design Phase The output of the design phase is the system specification. The system specification is like a set of blueprints that the consultants follow when developing your system. And just as it is very difficult, inefficient, and costly to build a house without blueprints, it is also very difficult, inefficient, and costly to build a software system without a system specification. CPIT 250 System Analysis and Design

System Design Phase During design phase, the developers will develop several parts of your system –Develop and model a program design. During this part of the design phase, the developers break down the system into pieces that can be programmed. Breaking down the system into manageable modules also makes changes easier to implement. –It should translate all the requirements and information that specify in the analysis phase CPIT 250 System Analysis and Design

UML Overview What is UML diagram ? –It stands for Unified Modeling Language –Used for specifying, visualizing, constructing, and documenting the software systems. –It is not a programming language but tools can be used to model the software system using UML diagrams. –After that, we can generate code in various languages. CPIT 250 System Analysis and Design

UML Diagrams UML includes the following nine diagrams –Class diagram –Object diagram –Deployment diagram –Component diagram –Activity diagram –Use case diagram –Collaboration diagram –Sequence diagram –Package diagram CPIT 250 System Analysis and Design Structural Modeling Behavioral Modeling Architectural Modeling

Class Diagram Definition: –The class diagram is a static diagram, it represents the features of an application. –Class diagram is not only used for visualizing, describing and documenting the system. –But also for constructing executable code of the software application. –It shows a collection of classes and describes the attributes and operations of that class. –It is also known as a structural diagram. CPIT 250 System Analysis and Design

Class Diagram Notations: CPIT 250 System Analysis and Design

Class Diagram Relationship Aggregation: –The contained classes are not strongly dependent on the life cycle of the container. –It’s form by drawing a line from the parent class to the child class with a diamond shape near the parent class. Composition: –It’s like the aggregation with different in the contained class will be obliterated (finish) when the container class is destroyed. –It’s form by drawing a line from the parent class to the child class with a filled shape near the parent class. CPIT 250 System Analysis and Design

Class Diagram How to draw Class Diagram? –The following points should be remembered while drawing a class diagram: The name of the class diagram should be meaningful to describe the aspect of the system. Each element and their relationships should be identified in advance. Attributes and Methods of each class should be clearly identified. For each class minimum number of properties should be specified. Because unnecessary properties will make the diagram complicated. Use notes when required to describe some parts of the diagram. Because at the end of the drawing it should be understandable to the developer/coder. CPIT 250 System Analysis and Design

Class Diagram Example CPIT 250 System Analysis and Design