REQUIREMENTS GATHERING USING OBJECT-

ORIENTED MODELS
UML –Unified Modeling Language–
Mario Castillo
Requirements Gathering using Object-
Oriented Models
■ Requirements Gathering: Meet the client requirements through an elicitation
process and using different techniques.
■ Object-Oriented: Refers to a programming language, system or software
methodology that is built on the concepts of logical objects.
■ It works through the creation, utilization and manipulation of reusable objects to
perform a specific task, process or objective.
■ The Unified Modeling Language (UML) is a general-purpose, developmental,
modeling language in the field of software engineering, that is intended to provide a
standard way to visualize the design of a system.

■ UML has been evolving since the second half of the 1990s and has its roots in the
object-oriented methods developed in the late 1980s and early 1990s

■ http://www.uml.org
 What is a Modeling Language ?

■ A modeling language is any artificial language that can be used to express

information or knowledge or systems in a structure that is defined by a consistent
set of rules. The rules are used for interpretation of the meaning of components in
the structure.

■ A modeling language can be graphical or textual.

■ UML is a graphical modeling language

Then,

■ UML is a general purpose modelling language. The main aim of UML is define a
standard way to visualize the way a system has been design.
■ UML is not a programming language, it is rather a visual language.
 UML Design:

■ UML offers a way to visualize a system's architecture in a diagram, including

elements such as:
– any activities (jobs);
– individual components of the system;
■ and how they can interact with other software components;
– how the system will run;
– how entities interact with others (components and interfaces);
– external user interface.
 Assignment # 5_Part 1
■ In an office word:
■ 1. After checking the first slides and using your own words explain what Unified
Modeling Language is. (Please don’t copy & paste)
 UML Design:
■ Software development methods
– UML is not a development method by itself; however, it was designed to be compatible
with the leading object-oriented software development methods or models.

■ Modeling
– UML diagrams represent two different views of a system model:
■ Static (or structural) view: emphasizes the static structure of the system using objects,
attributes, operations and relationships. It includes class diagrams, composite structure
diagrams and other diagrams.
■ Dynamic (or behavioral) view: emphasizes the dynamic behavior of the system by
showing collaborations among objects and changes to the internal states of objects. This
view includes sequence diagrams, activity diagrams, state machine diagrams and other
diagrams.
 Assignment # 5_Part 1

■ 2. Go to Omnivox. In the section Documents you can find a document called Types
of UML Diagrams. In that document you will find six Static or Structural Diagrams
and seven Dynamic or Behavioral Diagrams. Using your own words, explain each one
of them in four or five lines. (Please don’t copy & paste)
Static View of UML: Class Diagram

A class diagram describes the

structure of a system by
showing the system's classes,
their attributes, operations (or
methods), and the relationships
among objects.
Class Diagram
 Assignment # 5_Part 1

■ 3. Class Diagram Exercise: Following the last two examples given in the slides:
■ Person: Student / Lecturer and
■ BankAccount: CheckingAccount / SavingsAccount
Make a simple Class Diagram with the following information:
■ College: Student / Teacher