°


Conceptual Design using

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 seamless
development approach²from 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 Diagrams
ëIncorporates the capacity to model both business and system design
in an integrated environment
°


è
| 


Identify the actors and model the business process:

ëÿngage 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.
°






è|

ëèusiness sign-off and ownership of final business process

ëShared understanding of business process
ëÿmergence 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
ëÿxposure of touch points between users and the systems
supporting the business process
°


è|
 

 

| 

  

| 
  !   

| 


 

è

  è

 
°


| 



˜re an extension of the UML Use Case forming the hub of the functional
requirements and include the following content:
ë˜ 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
ë˜ series of dialogues or usage scenarios describing the interaction
between 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 other
events both before and after the process step is executed
°



 
è

"



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 can
be signed off by business
and subsequently built by
the development team.
°


è


 è

"



ëåunctional requirements are expressed in µèusiness

Context¶ with system responsibilities defined as a series of
interactions between participants (˜ctors as Human or
System) within a business process
ëThe system design is approached from both a user and
business perspective
ëThe conceptual design evolves in a transparent and flexible
manner
ëÿach use case consists of a build able and testable unit of
work leading to a potentially iterative development process
°






#
 

rocess_ iagrams

  
 1..*
functional_Requirement

 
 


Initiated_ rocess_ tep

*
rocess_ tep
  


1..*

This diagram displays Notified_Actor
1..* 1..* 1..* # 





Functional_Requirements
«describes»

the relationships tructure_ iagram 

Navigation_ iagram
0..1

between the artefacts (


 
$$ 
%%  
 0..1
$$ %%  
 

included in a standard creen_tructure_

1
iagram
1


Navigation_Bar rules
_ iagram

Holocentric analysis «describes»

screens
ocuments 1..*

model. ÿxternal 1..*



 Help_Text
1


 
*
 
%%
artefacts such as $$ 

µscreen shots¶ are

1..*

Fields
ÿnumeration
ocuments * I_ÿdit_Rules
ocument_Rule
included as required , 

*

$$#
 %%
0..1
* *

Field_Rules 1

#

using links to the 1..*




1..*

relevant object. ÿnumeration Fields


+
 +     essages
*
Rules
1..*
 
& 
 '
 




)# 
  




+ 
°


è

 
 


ë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 èusiness Change which
incorporates all products to support the users experience
ë˜pproach the business and IT design from the users
perspective
ëDesign artefacts (e.g. èusiness ules & ˜ctors) can be
reused and shared both within and outside the organisation
ëPowerful scripting language allows tool customisation
°



 
 

Holocentric Website: www.holocentric.com
(Trial version of the software available for download)

˜CT Sales Manager :

Ian ÿxcel ± Phone: 4 4 987 3

Implementation Manager:
èen Clohesy ± Phone: 4 5 3 876