NO1 Popular kala jadu karne wale ka contact number kala jadu karne wale baba ...
UML Practical.pptx System Analysis and Design
1. UML Practical Class
Software Engineering
Lecturer in Charge: DR. OLADEJO BOLANLE
Handled by: IGWAGU Nzubechukwu & BELLO Taofeeq
(BS, MS Computer Science)
2. UML- Unified Modeling Language
It is use to describe the language of an
applications with some common notation
3. UML: Use Case Diagram
•It is used to gather the requirements
•It includes internal and external influences
4. UML: Use Case Diagram - Notation
System
Use case
Actor
Association
Include
Extends
Dependency
Generalization
6. UML: Class Diagram - Basics
•Represents the static view of a software system.
•Shows Objects and their relationships.
7. UML: Class Diagram – Key Elements
•Classes: Blueprint for objects.
•Attributes: Characteristics of classes.
•Functions/Methods: Action classes can perform.
8. UML: Class Diagram – Relationships
•Association: Connections between classes.
•Inheritance/Generalization: How classes inherit
properties.
•Aggregation/Composition: Whole part relationships.
9. UML: Class Diagram – Benefits
•Helps visualize software.
•Guide implementation.
•Enhances communication among teams.
12. FLOW CHART
Graphical representation of an algorithm, process or workflow
Flowchart Components:
• Processes: Represent actions or steps in a process.
• Decisions: Indicate branching based on conditions.
• Connectors: Show the flow direction.
• Input/Output: Represent data input and output points.
13. FLOW CHART : Practical Example
Draw a flow chart of a simple authentication
system
15. Data Flow Diagram 1: Context
Diagram
•A high-level view of a system's interactions.
•The scope of the system and its relationship
to the environment
16. Data Flow Diagram 1: Context Diagram - Key
Components
1. Main System: Central focus of the diagram.
• Central Box: Represents the core of the
system.
• Interactions: Show how the system interacts
with external entities.
MAIN SYSTEM
17. Data Flow Diagram 1: Context Diagram - Key
Components
2. External Entities: Entities interacting with the
system.
• Entities outside the system boundary.
• Examples: Customers, suppliers, external
systems.
EXTERNAL ENTITIES
18. Data Flow Diagram 1: Context Diagram - Key
Components
3. Data Flows: Represent data exchanged between entities and
the system.
• Paths for data entering or leaving the system.
• Labeling: Naming data flows for clarity.
• Direction: Indicating data flow direction (inward or outward).
DATA FLOW
19. Data Flow Diagram 1: Context Diagram Benefits
• Simplifies complex systems for easy understanding.
• Identifies external interfaces clearly.
• Serves as a starting point for creating detailed DFDs.
20. Data Flow Diagram 1:
Context Diagram - Practical Example:
Draw a Context diagram of a Food Ordering
System
22. Data Flow Diagram II: Level 1 Diagram
•Level 1 DFD is an expansion of the context diagram.
•Subprocesses: Processes from the context diagram
are detailed.
•Identifying subprocesses and data flows.
23. Data Flow Diagram II: Level 1 Diagram -
Components
• Processes: Breakdown of the main system into subprocesses.
• Data Stores: Where data is stored within the system.
• Data Flows: Connections between processes and data stores.
• External Entities: Entities interacting with the system.
Sub
Processes
DATA FLOW
DATA STORES
EXTERNAL ENTITIES
24. Data Flow Diagram II: Level 1 Diagram - Benefits
•Detailed insight into system functionality.
•Basis for further decomposition into Level 2 DFDs.
•Facilitates system analysis and design.
25. Data Flow Diagram II:
Level 1 Diagram - Exercise 2:
Four separate processes of the food-ordering system
27. Entity-Relationship Diagram
• Shows how entities such as people, objects relate with each other in
a system
• Practical Example: Draw the inventory system for the food ordering
system.
28. BUSINESS CASE
• An INVOICE includes one or more INVOICE ITEMs, each of which
corresponds to an INVENTORY ITEM.
• Each PRODUCT is associated with INVENTORY ITEMs.
• A SALE indicates that Hoosier Burger sells one or more ITEM
SALEs, each of which corresponds to a PRODUCT.
• An ITEM SALE cannot exist without an associated SALE, and over
time the result will be zero-to-many ITEM SALEs for a PRODUCT
