|Home | Copyright Notice and Legal Disclaimers | Navigation Help | Tour! | Downloads | Contact Us | Site Index | Search|
|Methodology | Legends | Conventions Used in EIDX Documentation | EIDX's Use of UML Class Diagrams | Procedures and Templates|
On this Page:
Understanding EIDX Business Models
There are a number of ways of representing a business process graphically. Many organizations are adopting the Unified Modeling Language (UML) for representing business processes. The most commonly used are:
The EIDX community is made up of both business and technical constituents, and, as mentioned earlier, EIDX models are conceptual. EIDX is using some UML, as described here.
Traditional EIDX Representation (Use Case)
Although UML notation is not used, the traditional EIDX representation is still considered to be very understandable to business people, and it serves the same function as a UML Use Case, i.e. to illustrate the scope of a process, the players, and the basic activities.
The base activity diagram for a component model or scenario represents our best attempt at a standards-neutral, technology-neutral view. As mentioned before, technology-specific or standards-specific views may also be presented.
EIDX uses the term "context diagram" for lack of a better term -- be aware that some people use the term differently. EIDX uses the term for a diagram that represents best-practice relationships between the component and scenario models.
Each context diagram is from the perspective of one component or scenario model.
Last updated 06 February 2003