Scribd
Upload
14 views5 pages

UML vs Flowchart Assignment

The document compares UML (Unified Modeling Language) and flowcharts, highlighting their distinct purposes, complexities, and usage in software development. UML is a comprehensive modeling language for designing software systems, while flowcharts are simpler diagrams for visualizing processes. It also provides a brief history of UML's development and examples of basic UML diagrams related to turning on a light.

Uploaded by

abdullahiyahaya584
Copyright
© © All Rights Reserved
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
14 views5 pages

UML vs Flowchart Assignment

The document compares UML (Unified Modeling Language) and flowcharts, highlighting their distinct purposes, complexities, and usage in software development. UML is a comprehensive modeling language for designing software systems, while flowcharts are simpler diagrams for visualizing processes. It also provides a brief history of UML's development and examples of basic UML diagrams related to turning on a light.

Uploaded by

abdullahiyahaya584
Copyright
© © All Rights Reserved
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/ 5

UML vs Flowchart Assignment

Assignment

1. Differentiate Between UML and Flowchart

Think of UML and flowcharts as tools for visual communication in software and systems, but they serve

different purposes and have different levels of complexity.

Definition and Purpose:

- UML (Unified Modeling Language):

- A standardized modeling language used to design, visualize, and document software systems.

- Acts as a blueprint for software development.

- Useful throughout the entire software development lifecycle.

- Flowchart:

- A simple diagram used to represent the flow of steps in a process or algorithm.

- Best for visualizing logical operations or decision-making in code or business processes.

Comparison Table:

Feature | UML | Flowchart

------------------|---------------------------------------|---------------------------------------------

Purpose | Modeling complete software systems | Illustrating algorithms or processes

Complexity | More complex with multiple diagram types | Simple with basic symbols

Scope | System-wide (structure, behavior, interaction) | Specific to one process or function


UML vs Flowchart Assignment

Usage | Full software development lifecycle | Algorithm design and process documentation

Expressiveness | Very expressive; supports detailed modeling | Less expressive; best for simple logic

2. Summary of the History of UML

Before the 1990s, developers used different object-oriented modeling techniques, such as:

- Booch Method - by Grady Booch

- Object Modeling Technique (OMT) - by James Rumbaugh

- Object-Oriented Software Engineering (OOSE) - by Ivar Jacobson

These methods had varying notations, causing inconsistency. Recognizing the need for a unified standard,

the three experts-nicknamed the "Three Amigos"-collaborated at Rational Software Corporation to create a

single modeling language.

Key Historical Milestones:

- 1995: UML 0.9 released (initial draft)

- 1997: UML 1.0 released - the first official version

- 2005: UML 2.0 released - a major update that added more diagrams and improved modeling for complex

and embedded systems

- 2005 to Present: Several minor revisions (UML 2.1 to UML 2.5) to fix issues and refine the language

Today, UML is managed by the Object Management Group (OMG) and remains an essential tool for

modeling software, especially in large-scale or object-oriented systems, even alongside agile methodologies.

3. Simple UML Diagrams (Example: Turning On a Light)


UML vs Flowchart Assignment

Below are three basic UML diagrams illustrating how a light can be turned on using a switch.

A. Class Diagram

+---------+ +--------+

| Switch | ----> | Light |

+---------+ +--------+

| - isOn: Boolean | - isOn: Boolean |

| + turnOn(): void| + illuminate(): void |

| + turnOff(): void| + extinguish(): void|

+---------+ +--------+

Explanation:

- Two classes: Switch and Light

- Both have an isOn attribute and methods to control the light.

- The arrow shows association-the switch controls the light.

B. Use Case Diagram

+--------+

| User |

+--------+

/\

/ \
UML vs Flowchart Assignment

+----------+ +----------+

| Turn On | | Turn Off |

| Light | | Light |

+----------+ +----------+

Explanation:

- Actor: User

- Use Cases: Turn On Light, Turn Off Light

- Shows what the user can do in the system.

C. Activity Diagram

+----------+

| Start |

+----------+

+------------------+

| Flip the Switch |

+------------------+

+------------------+

| [Switch is ON] |

+------------------+
UML vs Flowchart Assignment

+------------------+

| Light Turns ON |

+------------------+

+----------+

| End |

+----------+

Explanation:

- Flow of actions to turn on a light.

- Includes a decision: if switch is ON, then light turns on.

- Ends after the light is turned on.

You might also like