Business Analysis

C.
Essential Skills for Business
Analysis

LL
Zaran Tech
ch Puja
Te
What is Data Modeling?
Peter Chen first introduced entity/relationship modeling in 1976 . It was a brilliant
idea that has revolutionized the way we represent data. It was a first version only,
an

however, and many people since then have tried to improve on it. A veritable
plethora of data modeling techniques have been developed.
Things became more complicated in the late 1980’s with the advent of a variation on
this theme called "object modeling". The net effect of all this was that there were
now even more ways to model the structure of data. This was mitigated somewhat
in the mid-1990's, with the introduction of the UML, a modeling technique
intended to replace at least all the "object modeling" ones.
r

 The purpose of a data model is to describe the concepts relevant to a domain, the
relationships between those concepts, and information associated with them.
 A data model is a simply a diagram that describes the most important “things” in
Za

your business environment from a data-centric point of view.

1
Other Types of Data Model

Conceptual Data Modeling - identifies the highest-level

relationships between different entities.

C.
Logical Data Modeling - illustrates the specific entities, attributes
and relationships involved in a business function. Serves as the basis for the
creation of the physical data model.

LL
Physical Data Modeling - represents an application and database-
specific implementation of a logical data model.

ch
Te
Types of Data Model : ERD
Entity-relationship diagram (ERD)
an

Preferred when the model will be used as the basis for a relational database. ERD
is a specialized graphic that illustrates the interrelationships between entities
in a database. ERD’s often use symbols to represent three different types of
information. Boxes are commonly used to represent entities. Diamonds are
normally used to represent relationships and ovals are used to represent
attributes.
r
Za

2
 Process flow diagram
Commonly used in engineering to indicate the general flow of plant processes and
equipment. The PFD displays the relationship between major equipment of a
plant facility and does not show minor details such as piping details and
designations. Another commonly-used term for a PFD is a flowchart.

C.
LL
ch
Te

Data flow diagram

Graphical representation of the "flow" of data through an information system.
an

DFDs can also be used for the visualization of data processing (structured
design). On a DFD, data items flow from an external data source or an
internal data store to an internal data store or an external data sink, via an
internal process.
r
Za

3
 Popular Data Modeling Tools

 There are a number of data modeling tool:

C.
LL
ch
Te
History of UML
•Unified Modeling Language
an

•UML is a modeling language which puts together several diagrammatic views

which can be used for any stage of the software development life cycle.
•UML has its nine kinds of modeling diagrams

The development of UML began in late 1994 when Grady Booch and Jim Rumbaugh of Rational
Software Corporation began their work on unifying the Booch and OMT (Object Modeling
r

Technique) methods.

While Rational was bringing UML together, efforts were being made on achieving the broader goal of
Za

an industry standard modeling language.

Rational established the UML Partners consortium with several organizations (Digital Equipment
Corp., HP, i-Logix, IntelliCorp, IBM, ICON Computing, MCI Systemhouse, Microsoft, Oracle,
Rational Software, TI, and Unisys ) willing to dedicate resources to work toward a strong UML 1.0
definition.

This collaboration produced UML 1.0, a modeling language that was well defined, expressive,
powerful, and generally applicable.

“UML is an industry standard modeling language with a rich graphical notation, and
comprehensive set of diagrams and elements.”

4
UML Diagrams
1. Use Case Diagrams
2. Activity Diagrams

C.
3. Sequence Diagrams
4. Collaboration Diagrams
5. Class Diagrams
Component Diagrams

LL
6.
7. Deployment Diagrams
8. Decomposition Diagram
9. State Diagram
http://www.msoffice.us/Visio/Visio_2007_UML_Modeling_Part_1.htm

Zaran Tech
ch Puja
Te
Use Case Diagram
an

 Type of behavioral diagram defined by and created from a Use-case analysis.

 Its purpose is to present a graphical overview of the functionality provided by a
system in terms of actors, their goals (represented as use cases), and any
dependencies between those use cases.
 The main purpose of a use case diagram is to show what system functions are
performed for which actor. Roles of the actors in the system can be depicted.
r
Za

5
 Use Case Diagram Rules
 The only valid relationship between an actor and another is “generalization”. A “User” can Run
Applications. A “Super User” can Install & Run applications.
 Use the “Include” relationship to show that the behavior of one use case is wholly and unconditionally
used in another use case.
 Use the “Generalization” relationship to show that a use case is a specialization of another use case.
 Use the “Extend Relationship to show that one use case conditionally augments (or extends) the
behavior of another use case.

C.
LL
the extend relationship

ch
Te
Use Case Diagram: Medical Clinic
Software
r an
Za

6
 Activity Diagram
Shows the business process flow and makes use of the use
cases similar to data flow diagrams
Simple Activity Diagram Cross Functional Activity Diagram

C.
LL
Zaran Tech
ch Puja
Te
Sequence Diagrams
Are used to display the orderly sequence of message transfer
between entities of the system
r an
Za

Zaran Tech Puja

7
 Collaboration Diagrams
The collaboration diagram illustrates messages being sent between
classes and objects (instances).

C.
LL
Purchasing a Bus Ticket
ch
Te
Class Diagram
 Gives an overview of a system by showing its classes and the relationships
among them. Class diagrams are static -- they display what interacts but not
an

what happens when they do interact.

r
Za

Zaran Tech Puja

8
 Component Diagrams
Shows the component types and their dependencies in the
architecture of the system as a whole

C.
LL
Zaran Tech
ch Puja
Te
Decomposition Diagram
 Used to show functional decomposition into processes (high-level
an

function), process, organization or data subject area.

r
Za

9
 Deployment Diagrams
Shows the physical architecture and the deployment components.

C.
LL
Zaran Tech
ch Puja
Te
State Chart Diagram
State Chart diagram describes the flow of control from one state to another state. States are
defined as a condition in which an object exists and it changes when some event is
an

triggered. So the most important purpose of State Chart diagram is to model life time of
an object from creation to termination.
r
Za

10
Tools for UML Diagrams

C.
 Rational Rose

http://www.screencast.com/users/PujaM/folders/Jing/media/f7224a99-5a05-4ca3-bc40-
91e024280c3a

LL
 MS Visio
 Visual Paradigm
 Enterprise Architect

ch
Te
r an
Za

Zaran Tech Puja

11