Business Objectives & Success Criteria

[apetosa]

Greetings.

What is the recommended best practice for representing business objectives and success criteria in EA as first class objects (using v9.0, build 908)?

Presently, I modeled the business objectives as a set of Requirement Elements, which are first class objects in EA. I chose this approach for traceability purposes. However, in principle, a business objective (e.g., release v1.0 of Application X by date Y) is too broad in my opinion to be represented as a requirement. Also, it is not a feature, which is a logical representation of some capability to which one or more requirements will map.

Are there other first class objects in EA better suited to modeling business objectives?

Thank you.


Regards,

Anthony

[OpenIT Solutions]

Version 9 introduces "Strategic Diagrams", the Strategy Map has vison and mission elements (classes with stereotypes). Your approach of using a requirment sounds fine to me - you could create an explicit "business objective" stereotype (and place it into a UML Profile).

Either way you can use UML relationships to model the relationship between a business objective and the requirments that are associated with the objective.

Any help?

Jon Ridgway.

[apetosa]

Jon,

Thank you, sir. I will take a look. Much appreciated.


Regards,

Anthony