The scenario planning phase is the first step you take in IEPD development.
In scenario planning, the IEPD stakeholders decide and agree on what will go into the package. This phase can take a long time to accomplish. The more thought and analysis you put into defining your requirements typically results in better schemas and support documents.
Develop a high level scope and goal of the intended exchange. Decide what information needs to be a part of it. Interview stakeholders to gain an understanding of the information exchange environment. Stakeholders can include the organizations with whom you are exchanging information, community stakeholders in the same mission space, and practitioners from your organization.
Ask questions such as the following:
Consider complicating factors:
An existing, small, simple exchange requires fewer exchange development resources than a new, big, poorly documented one.
An effective scenario is informative, strategic, and comprehensive. A model is a graphical representation of information exchange requirements and is essential to depict the scenario that will ultimately drive the building of the information exchange. Use diagrams to create business scenarios as an effective first step to accomplish this. Recommended diagram types include the following:
A use case diagram graphically represents the functionality of a particular information exchange as perceived by an external observer. It has the following components:
|Actor||Depicts system interactions; a role that a human, device, or system “plays” within the diagram.|
|Use Case||Depicts system functionality such as main or sub functionality, a user goal, or an activity system.|
|Relationship||Depicts the relationships actors have with use cases and each other.|
|System||Contains all functionality and limits scope of the diagram.|
A business process diagram shows the graphical and sequential activities involved in an exchange. It is similar to a workflow diagram and has the following components:
|Stakeholder||Any person, organization, or system directly or indirectly involved in the information exchange.|
|Actvity||Correlates the data being exchanged with any activity that drives it.|
|Gateway-Event Based||Activities that force a decision upon a stakeholder.|
|Flow||Connects business processes and events to show the direction of activities in the diagram.|
|Start Event/Stop Event||Acts as an activity trigger or represents the result or completion of an activity.|
A sequence diagram shows how applications or systems operate with one another. It displays the sequential order of operational processes or messages between applications as horizontal arrows between the parallel, vertical lines that are used for applications. This allows the specification of simple runtime scenarios in a graphical manner. A typical sequence diagram should include the following elements:
|Applications||Any application involved in sending messages within the information exchange.|
|Messages||Any message being sent between applications within the information exchange.|
This sub-process of the traveler processing system has three interacting applications:
When you have answers to the questions and complications discussed earlier, and one or more detailed diagrams, you can proceed to the next phase, Analyze Requirements.