business requirements modelling holocentric

8/8/2019 Business Requirements Modelling Holocentric

1/12

Presented by:

Shane Rice

Software Development Quality and Productivity

ATO

Conceptual Design usingHolocentric Modeler

Holocentric


2/12

What is Holocentric Modeler

a tool that captures, organizes, integrates and presents models,

specifications and code for developing object-oriented software and

systems.

Integrates object-oriented methods and languages into a seamlessdevelopment approachfrom early analysis and design concepts

through to detailed class code and back again

supports a number of popular object-oriented methods and notations,

which cover Class, Object Interaction, Use Case diagrams as well as

General DiagramsIncorporates the capacity to model both business and system design

in an integrated environment

Holocentric


3/12

Business Process Model

Identify the actors and model the business process:

Engage business representatives and arrange workshops to model

with them model current business process, if necessary, then future

business processes fulfilling the intent of the required change

Document the internal and external users/actors involved in the

system

Model the business process - begin at a high level and gradually

increase the granularity i.e determine the scope of the business then

the major processing areas, then the processes within those areas.

Holocentric


4/12

The benefits of the BPM include:

Business sign-off and ownership of final business process

Shared understanding of business process

Emergence of products and services that support the users

experience of the business process

Identification and clarification of business rules impacting on

the process

Understanding of responsibilities and capabilities

Exposure of touch points between users and the systems

supporting the business process

Holocentric


5/12

BPM in Holocentric

Proce re - 1 to M n

Proce i gr - 1 to M n

Mo el co e

Base

ctor Base

ctor

Process

te

Holocentric


6/12

Process Steps

Are an extension of the UML Use Case forming the hub of the functional

requirements and include the following content:

A description of the work to be carried out within the process step and

how that piece of work will satisfy the needs of the stakeholders and fulfil

the business intent

A series of dialogues or usage scenarios describing the interactionbetween the actors (Human and system) within the process. This

consists of a normal course describing the main success scenario and a

series of alternate courses detailing other scenarios which may be either

successful or unsuccessful.

Pre and Post Conditions detailing the expected state of systems or otherevents both before and after the process step is executed

Holocentric


7/12

Modellin the Business Requirements

B

se

tor B

se

tor

ro ess

te The requirements model

reaches maturity through

linking artefacts to their

relevant use cases as they

reach completion.

The final result is a

complete section of the

business process that canbe signed off by business

and subsequently built by

the development team.

Holocentric


8/12

Benefits of a Modellin Business Requirements

Functional requirements are expressed in Business

Context with system responsibilities defined as a series of

interactions between participants (Actors as Human or

System) within a business processThe system design is approached from both a user and

business perspective

The conceptual design evolves in a transparent and flexible

mannerEach use case consists of a build able and testable unit of

work leading to a potentially iterative development process

Holocentric


9/12

Holocentric Artefacts

This diagram displays

the relationships

between the artefacts

included in a standard

Holocentric analysis

model. External

artefacts such as

screen shots are

included as requiredusing links to the

relevant object.

rocess

te

rocess Area

rocess

ia

ra

le

le Facet

ia

ra

Actor

Bsiness

ject

o

el

>

Glossar!

ia

ra

creen

!

ste

Featres

Fnctional

e

"

ire

ent

Non F

nctional

e"

ire

ent

essa

e

Hel

#

ext

ecification Class

ia

ra

Concet

al Class

ia

ra

En

eration

1..*

screens

$ocument_Rule

0..1

1..*

$ocuments

0..1

%

tructure_$

iagram0..1

Navigation_$

iagram

Notified_Actor

1..*

1..*

Initiated_&rocess_

%

tep

rules

*

1..*

Functional_Requirements

Rules

1..*

1..*

$ocuments

1..*

&rocess_

%

tep

&rocess_

$iagrams

1..*

describes

describes

'essages*

*

Fields

1..*

Fields

Help_Text

1

1Navigation_Bar

_$ iagram

*

(

I_Edit_Rules

1%

creen_%

tructure_$

iagram

1..*

Enumeration

Enumeration

*

1Field_Rules

functional_Requirement

*

Holocentric


10/12

Benefits of usin Holocentric Modeler

Standardised approach to business and application design

Centralised repository of project information

Traceability from original business requirements to

implementation of code

Simulation of the entire Business Change which

incorporates all products to support the users experience

Approach the business and IT design from the users

perspective

Design artefacts (e.g. Business ules & Actors) can bereused and shared both within and outside the organisation

Powerful scripting language allows tool customisation

Holocentric


11/12

Contact Details for Holocentric

Holocentric Website: www.holocentric.com

(Trial version of the software available for download)

ACT Sales Manager :

Ian Excel Phone: 4 4 987 3

Implementation Manager:Ben Clohesy Phone: 4 5 3 876

Holocentric


12/12

business requirements modelling holocentric

Documents