|Service Operation idea built into EPF? [message #573861]
||Sat, 02 December 2006 04:52
| Charles Edwards
Registered: July 2009
Where I work, we have been defining the terminology of how we specify |
business services generally. See attached JPEG (readable at 100%) for
reference to this questions terminology.
We want to be able to use our concept of 'Services' with their public facing
'Service Operations' to describe what we do in our department and how people
from external departments can call on our departments services. We then want
to build these into an EPF process web and publish it to the organisation so
thay can see what we do and how they can use our services. The idea is they
would only need to look at the Service Operation to see how to engage with
us (what Input Work Products, engagement Communication protocols, Output
Work Products, etc.)
As far as I can see
o The Capability Pattern is a collaboration and that would match our
overall description of Capability in our model.
o The Activities and Tasks (how) would define the Internal workings of what
we do in our department, along with the Roles (who) and Work Products
What I am not sure of is How would one show a "Service Operation" in EPF?
(think of it as an interface into the Servce - The Public facing call on a
I would suggest it would be another type like Role, Tasks, Work Products,
Guidance called Service Operation?
So the questions are:
o Is it worth defining something like this in EPF?
o Is there a better way of achieveing what we are trying to do?
o Is there a meta-model for EPF anywhere in UML so we can see where to
extend it and how things inter-relate?
Here is a made up example:
Department's Internal (Private) Service:
Capability: Assess Impact of a New Project on the existing Architecture
Role<<primary>> : Enterprise Architect
Activity: 1) Assess Proposed Project Architecture
Task: 1.1) Identify Proposed Project Architecture (select ViewPoints)
Task: 1.2) Map to Existing Architecture framework
Activity: 2) Identify Impacts on Enterprise Architecture
Task: 2.1) Assess Impact (Issues and Risks) on the Architecture
Task: 2.2) Identify Dispensations for Tactical over Strategic direction
Activity: 3) Refine Enterprise Architectural Model
Task: 3.1) Update Enterprise Architectural Roadmaps Model
Task: 3.2) Update Issues & Risk List
Task: 3.3) Update Dispensations List
Work Products: Introductory Software Architecture Description, Enterprise
Architecture Framework, Risk List, EA RoadMap Model, etc.
Department's External (Public) Service operation:
Service Operation: Assess Architecture for new Project
Roles: Project Solution Architect, Project Manager
Protocol Behaviour: (imagine a sequence diagram here)
1. Notification of New Project (arrives from Project Office to EA)
2. Architectural engagement on the Project (between Solution Architect
and Enterprise Architect)
3. Workshop to resolve all Issues (between Solution Architect and
4. [optional: Dispensations allowed (from EA to Project)]
5. Updated SAD delivered (from EA to Project)
Input Work Products: Project Inception Document
Output Work Products: Introductory Software Architecture Description,
[optional: Project Architectural Dispensations]
Powered by FUDForum
. Page generated in 0.05770 seconds