Business Architecture - Advice Please!

[Stoppy]

Hi All,

Just looking for some advice with my packaging in EA. The reason being my core skills are BPMN and Business Analysis/software development and the way things are I am quickly ascending into the Enterprise Architecture space and dancing across all domains. Look Out!  

My current task I have built the following package structure in my current state:

Level 1 - Function Model
Level 2 - Business Services, Contracts, Service Qualities
Level 2 - Process, Events, Controls, Products
Level 2 - Functions

There may be a level 3 under some Level 2.

So, I have populated these packages with our organsiational functions, services and products.

I have then created a package called "View Model" and then another package called "Business Product, Service, Function View" and dragged the functions, services and products from the above packages onto my diagram to build a view for my stakeholders.

I have a couple of questions:

1. Is this best practice what I doing?
2. Should I use this respository of elements to build other diagrams and stakeholder views?
3. Am I over complicating things and is there a better way to do this?
4. I am using manage baselines to help version control the package through the stakeholder iterations, should I beware of anything with this function?

Thanks in advance,

Stoppy

[Helmut Ortmann]

Hello Stoppy,

to find the right way to model you have to write down what you want to archieve with modeling. There is no best way. Only your way. You have to find your modeling method.

Your package structure is a starting point. Usually you need some time to establish a stabile package structure. The package structure should be complient to your modeling method and your modeling process.

Different views for different stakeholders is always a good idea. So reuse model elements in different diagrams.

Baselines rely on disciplined working. If you and your team are disciplined than it will work. Personally I prefer Version Control if I need controlled changes. But there are also some drawbacks. It's also a good idea to start with Version Control after you have established a stabile package structure.

Helmut

[Stoppy]

G'day Helmut,

Your package structure is a starting point

I am using TOGAF, so it is pretty prescribed, managing the elements will be my challenge.

Guess the main reason for my post is this a new package in a new domain for me and didn't want to make a rod for my own back, but as your reply indicated the package will evolve and mature over time which I need to be open minded too.  

Baselines rely on disciplined working. If you and your team are disciplined than it will work.

It's just me, hence the elevation from Business Analyst to Enterprise Architect.  

Regards,

Stoppy

[Stoppy]

Hi All,

I stumbled accross this document when googling and researching yesterday. Page 7 is definately where my thread is pitching at and how I am shaping my packages: http://www.in2grateit.com/pdf/Sparx%20EA%20for%20TOGAF%209%20Architects.pdf

Regards,

Stoppy  

[Stoppy]

Just thought I would provide a update to my journey on this item, as googling has not provided any real world public practical examples to benchmark against.

So Basically I have built a very high level view of our products and services and functions which demonstrates their support to deliver to our customer.

From here I have now built a second layer package for the functions which models the core activities.

From here I have built a "third layer" for the Activities and "second layer" for the Products and Services which breakdown into four packages:

1. Business, Application and Technology package - Provides a view of the itegration of Actors and Roles, Business Services, Business Processes, Application Services, Application Components and Infrastructure
2. Business Process Package - Provides detailed BPMN models for the Activity
3. Policy and Procedure Package - Provides links to relevant artefacts stored in our organisation for the Activity
4. Reporting Package - Provides links to relevant artefacts to metrics and measures such as balanced scorecards for the Activity
5. Requirements Package - Provides the ability to capture and model business requirements for the Activity

So far, I must say the management of the linkages from various packages and the redundancy of elements as the models mature has been challenging.

If anyone has some feedback or words of wisdom, happy to hear from you.

Regards,

Stoppy