Business Analysis Session4

7/31/2019 Business Analysis Session4

1/27

BUSINESS ANALYSIS

DAY-4

Vamsi Mohan V


2/27

AGENDA

(DAY-4) Data Modeling

Process Modeling

Software Development Process Models

Waterfall model

-

Agile Development Processes

eXtreme Programming (XP)

Test Driven Development (TDD) Agile Methods

Classic Vs Agile processes


3/27

Data Modeling Data Modeling

The purpose of a data model is to describe the concepts relevant toa domain, the relationships between those concepts, and informationassociated with them. A data model usually takes the form of adiagram supported by textual descriptions. It visually represents the

, ,

business, attributes associated with them and the significantbusiness relationships among them.

Data models are often supported by a Data Dictionary and Glossary

and Business Rules analysis.

The two most widely used types of data model are the entity-relationship diagram (ERD) and the class diagram


4/27

Elements Logical data models describe the information relevant to an

organization. High-level logical data models may focus solely ondescribing the entities, attributes and relationships of most

importance. Physical data models describe how data is stored andmanaged in a software application.

1. Concept:

Logical data models describe the information relevant to an organization. High-levellogical data models may focus solely on describing the entities, attributes andrelationships of most importance. Physical data models describe how data is storedand managed in a software application. Each type of concept should have a uniqueidentifier (a type of attribute) that differentiates between actual instances of the

concept. Concepts are referred to as entities in ERDs and as classes in classdiagrams.


5/27

2. Attributes:

An attribute defines a particular piece of information associated witha concepthow much information can be captured in it, allowablevalues, and the type of information it represents.

Name: a unique name for the attribute. Other names used bystakeholders may be captured as aliases.

Values/Meanings: a list of acceptable values for the attribute. Thismay be expressed as an enumerated list or as a description ofallowed formats for the data (including information such as thenumber of characters). If the values are abbreviated this will includean explanation of the meaning.

Description: the definition of the attribute in the context of thesolution.


6/27

3. Relationship:

Relationships are significant business associations between concepts.The example shows the relationships between Business Analyst andRequirement as an annotated line. The labels explain the nature of therelationship from the perspective of each entity.

Relationships define how information is used in the operation of thebusiness, and indicate the important linkages that need to be managedand maintained in the solution. Relationshi s ma also indicate the

cardinality or multiplicity of the relationship (i.e. the number ofrelationships allowed or required).

4. Metadata

Metadata is defined as data about data. Metadata describes thecontext, use, and validity of business information and is generally usedto determine when and why information stored in a system waschanged.


7/27

Data Model - Usage Considerations Data Model Advantages:

Data models offer the flexibility of different levels of description. Theyprovide a consistent modeling approach that supports the transition

through planning, analysis, design and implementation.

Because they have a strong basis in mathematical concepts, datamodels are supported by rigorous rules for correctness and

.

models.

Disadvantages:

Data models can be complex, and they deal with concepts that maybe unfamiliar to people without a background in InformationTechnology. If not properly presented, they can be difficult for usersto understand and relate to. Terms and definitions may vary in use indifferent organizational units or domains.


8/27

Process Modeling A process describes how multiple people or groups collaborate over a period

of time to perform work. Processes involve a number of activities that arelinked by a sequence flow. A process is repeatable and may have multiple

paths to completion. A process is initiated by an event in the business domain, such as a sale of a

product to a customer, a request for information by a senior executive, or afailure to complete a transaction. Events may be actions taken by a person,

,

time. The process model may involve manual activities, be completelyautomated, or a combination thereof. The process is complete when theobjective or the goal of the process is completed.

A process model is a visual representation of the sequential flow and control

logic of a set of related activities or actions. Process modeling is used toobtain a graphical representation of a current or future process within anorganization. A model may be used at its highest level to obtain a generalunderstanding of a process or at a lower level as a basis for simulation sothat the process can be made as efficient as possible.


9/27

Elements There are many different notations in use to depict process models. Process

models typically contain some or all of the following key elements:

1. Notation Elements:

Activities: The individual steps or pieces of work that must be completed inorder to execute the business process. An activity may be a single task ormay be further decomposed into a subprocess (with its own activities, flow,and other process elements).

Decisions: Forks where the flow of work roceeds in two or more flows and

optionally, where separate flows merge together. A decision may createmutually exclusive or parallel flows.

Events: Events occur outside the scope of a process and may be the resultof actions taken, messages received, or the passage of time. Events maycreate, interrupt, or terminate processes.

Flow: Indicate the direction of the step-by-step sequence of the workflow. Ingeneral, diagrams are drawn from top to bottom or in the direction of readingto show the passage of time. The process flow may split to allow for activitiesto occur simultaneously and later merge.


10/27

Roles: Roles represent a type of person or group. Role definitions typicallymatch those in the organization model.

Swimlanes and Pools: Swimlanes are horizontal or vertical sections of

a process model that show which activities are performed by a particularrole. When the flow of work crosses the boundary of a swimlane,responsibility for that work then passes to another person or groupwithin the organization.

A pool represents an organizational boundary. It may include a numberof swimlanes. Commonly, a process will include one pool for thecustomer and a second pool for the organization, although it is possiblefor a process to include any number of pools.

Terminal Points: Terminal points represent the beginning or end of aprocess or process flow. A terminal point generally represents some kindof event that is visible to the organization or outside of it.


11/27

2. Process Improvement:

There are a number of frameworks and methodologies that focus on processimprovement methods, such as Six Sigma, Lean, and a large number ofproprietary BPM approaches. Methods for process improvement include value

stream mapping, statistical analysis and control, process simulation,benchmarking, process frameworks, and others. Common changes to processesin order to improve them include:

Analysis of a process to identify and remove activities that do not add value to a, .

Reduction of the time required to complete a process (by reducing the time toperform a task or the wait time between tasks).

Improving interfaces or handoffs between roles and organizational units to

remove errors.

Reduction or elimination of bottlenecks and backlogs.


12/27

Process Modeling Components


13/27

Modeling


14/27

Development process models Static process models

Waterfall model

V-model

Incremental process model

Iterative/Incremental process model

eXtreme Programming

Prototypic development

Test Driven Development (TDD)


15/27

Waterfall model


16/27

V-Model


17/27

Agile Development Processes


18/27

eXtreme Programming (XP)


19/27

Planning in XP


20/27

Methods in XP


21/27

Software Prototypes


22/27

Test Driven Development (TDD)


23/27

TDD Process


24/27

Advantages of TDD


25/27

Agile Methods


26/27

Classic Vs Agile processes


27/27

Session Review:

Questions?

I would like to hear from you: please send us your queries [email protected]

Documents

Business Analysis Session4