SOFTWARE REQUIREMENTS

ENGINEERING
BUSINESS MODELING

 A business model is an abstraction of how a business functions

 A business model typically is described from the point of view of the

business.

 The business model is described in the words and thoughts of the persons
that execute it and those that participate in it.
BUSINESS MODELING

 Business modeling is a problem analysis technique especially suitable for

the Information System (IS) environment

 Business environment (Subject World) is complex

 We need to understand
 some of this complexity before even attempting to define a specific problem
worth solving
 the broader context in which the application (solution system) operates.
THE PURPOSE OF BUSINESS MODELING

 To understand the structure and dynamics of the organization

 To ensure that customers, end users, and developers have a common

understanding of the organization
 Business modeling is a technique to help answer critical questions, such as:
 How do you know you have identified all system use cases?
 What do the workers (users) do before using our system?
 What business value does the system bring?

 A good understanding of business processes helps you to build the right systems.
 We need to answer following questions from solution perspective
 Why build a system at all?
 Where should it be located?
 How can we determine what functionality is optimum (best possible) to
locate on a particular system?
 When should we use manual-processing steps or workarounds (a method for
overcoming a problem)?
 When should we consider restructuring the organization itself in order to
solve the problem?
BUSINESS MODELLING AND VIEWS

 In order to properly describe the business problem in simple and easy-to-

understand terms, and yet not lose the complexity, we look at the
business problem from different perspectives, or views.

 Within each of these views, different UML diagrams may be used in

order to properly describe the view.
FUNCTIONAL VIEW

 The functional view describes the functions that are performed in the
business.
 Functions(drawn as use cases) are typically executed by an actor, who takes
responsibility for the successful execution of the function.
 Use case diagrams may be organized within package structures. Package
diagrams may also be used to describe dependencies between the parts of the
business.
 Functions defined in the functional view typically refers to the "What"
that is being done in the business and the "Who" who performs it.
STRUCTURAL VIEW

 The structural view identifies all of the business entities (business

entities are formed to sell a product or a service) that come into play and
how these entities are related to each other.

 The business entities typically represents the “with what" entities that are
used by, or is affected by the functions described in the functional view .
BEHAVIOURAL VIEW

 The behavioural view is used to describe the flow of activities that are
executed in order to successfully achieve the function's outcome, or
workflow across the functions.
 The behavioural view describes "How" things are done.
 The behavioural view often also describes how the business entities are
referenced, or used, as part of the activities.
MODELING NOTATION IN UML

Create Project
Customer Project Manager Customer
R&D Dept Order
Organization Business Business
Business Business Use Case
Unit Entity
Actor Worker
 BUSINESS MODELING WORKFLOW

Capture a Common Find Business Structure the

Vocabulary Actors and Business
Use Cases Use Case Model
Business Business
Process Model
Analyst Reviewer

Describe Review
a Business Business
Use Case Describe a Use-Case Model
Business Worker
Find
Business Business Workers
Designer and Entities Review
Business
Object Model
Describe a
Business Entity
WORKERS
 Business-process analyst
 leads and coordinates business use-case modeling by outlining and delimiting (Defining) the
organization being modeled.
 E.g., the business-process analyst establishes which business actors and business use cases exist and how they
interact. (B Actor and B Use Case, Interaction between them)
 The business designer
 details the specification of a part of the organization by describing the workflow of one or several
business use cases. (Workflow of one or more B Use case)
 specifies the business workers and business entities needed to realize a business use case to these
business entities. (B Workers and B Entities to realize the B Use case)
 defines the responsibilities, operation, attributes, and relationships of one or several business workers
and business entities. (Relationship between B Workers and B Entities)
 Stakeholders
 who represent various parts of the organization and provide input and review

 The business reviewer

 who reviews the resulting artifacts
ARTIFACTS

 A business use-case Model

 a model of the business's intended functions.
 It is used as an essential input to identify roles and deliverables in the organization.

 A business object model

 an object model describing the of business use cases

 Supplementary business specifications

 This document presents any necessary definitions of the business not included in the
business use-case model or the business object model.
 A glossary defines important terms used in the business.
BUC (BUSINESS USE CASE) MODEL (WHAT
PART)

 The business use-case model provides the big picture from a business actor's
perspective.
 Describes business processes (functions of business)
 These processes are documented as a sequence of actions that provide observable value
to a business actor.
 Used to identify roles and deliverables in the organization

 It consists of one or more use-case diagrams that contain one or more business
use cases.
 is independent of the concrete (actual) possibilities and requirements for its (IT-
related) implementation
A BUC MODEL
A BUSINESS OBJECT
MODEL
A BUC MODEL OF AN ORDER
MANAGEMENT
ORGANIZATION

RFQ->RFP->ORDER PROCESS
Q& A