In this phase, we model the current business system, electronic or manual, focusing on the primary product, the triggering event(s), inputs to the system, secondary products, and activity flow. This is also the first time we identify the objects that are intrinsic to the business in this system.
The participants in this phase include the core facilitation team and the extended team identified in the Preliminary Planning phase. The core facilitation team is responsible for facilitating the meetings, and keeping notes that will provide the textual information for the diagrams and a record of facts that will be required in later phases.
As an integral part of facilitation, diagrams must be developed during the meetings using a public medium that all participants can see. This keeps the team focused, draws input from the rest of the team, and helps to keep communication open and accurate. (Reminder: If the meeting location is not equipped with a built-in, large-scale medium, such as a blackboard or whiteboard, you may want to bring static sheets and markers.)
|
Business Process Model
This model shows the triggering event, the primary and secondary outputs, and the inputs. It can be created using Visio templates available on the M drive.
Note: If you do not have Visio on your machine, the template will be displayed as gibberish. If this happens, use the PC in the hallway where Visio is installed. |
 
|
|
Business Process Document
The Business Process Document is a Word document that describes the business process, and includes the Business Process Model, as well as the descriptive text.
Click on the Sample button to see an example of a Business Process Document. Click on the Template button to save the template on your C drive, where you can use it to open a new Business Process document in Word. Click here for complete instructions for using a template in Word. |
|
|
Entity Object Model
This model shows the entity objects and their relationships for the current business process. It will be updated as needed to reflect the business process as it is developed in the System Analysis and subsequent phases. The model is created and updated in Visio. |
|
|
Object Life Cycle Model
This model shows the life cycle changes in an object. A life cycle model should be developed for each entity that has significant life cycle changes in the business process. These models are created and updated in Visio. |
|
|
Information Event Map
This is a matrix developed to test for the completeness of the entity life cycle analysis. There is no template available at this time. |
|
|
Business Event Map
This is a matrix developed to test for the completeness of the business analysis. There is no template available at this time. |
|
|
Proposed Solution Statement
This is a brief explanation of the most likely solution to the business problem. If this information is not already in the Initiation Plan, the plan should be updated to include the information in the relevant sections. At this time, there is no sample using the Initiation Plan template. |
|
|
Methodology Compliance Form
This form is used to document that the project conforms to the methodology for this phase. It must be completed in Word and sent with the rest of the documentation packet for approval.
There is no sample available at this time. |
|
|
Recommendation Form
This form contains the recommendation of the project team on whether the project should go forward as planned. It must be completed in Word and sent with the rest of the documentation packet.
There is no sample available at this time. |
|
Distribute the project plan and business context model to all team members.
The team meets to discuss the current business process and develop a common understanding of what is happening now. If the team includes members who are not familiar with the methodology, the core team (or a DMS representative on the core team) explains the objective of this phase, and the methods that will be used to accomplish it.
To facilitate the business analysis discussion, develop a Business Process Model for each major process within the scope of the project, using a medium visible to all participants (public medium). Then for each business process, draw one or more Activity Flow diagrams.
TIP: The Business Process Model shows the borders of the system, or its external pieces, whereas the Activity Flow diagram shows the internal pieces, or activities, within the process.
For validation questions, see page 3D-15 of the OOA&D class materials.
The scribe enters the textual information about the business processes using the Process template, and distributes the results to the team.
A member of the core facilitation team creates an electronic version of the Business Process Model(s) and Activity Flow diagram(s), using the tool provided for that purpose. (The tool has not been provided yet. Until it is, you can either draw the models free-hand and distribute hardcopy, or use Visio to make electronic copy. The templates use Visio, which must be installed on the machine you are using to access them from Netscape.)
One or two members of the core facilitation team perform Direct Observation of the business processes, and note differences and/or omissions on the Business Process Model(s) and Activity Flow diagram(s).
The core facilitation team meets to create a first draft of the Entity Object Model, again using the whiteboard to facilitate and focus the discussion. This initial Entity Object Model shows objects with major attributes and major operations, and all simple relationships. For validation questions, see page 3B-20 of the OOA&D class materials.
Verify the Entity Object Model with client input. This can be done with the extended team, or with a subset of client participants.
The extended team considers all objects, and creates the Object Life Cycle models for each object with significant state and data maintenance changes, to show the events that control the changes. For a validation checklist, see page 3C-9 of the OOA&D class materials.
A member of the core team creates the Information Event Map and the Business Event map. These are a test for completeness, and provide cross-reference information. If anything is shown by these maps to be missing, the core team meets to re-examine the models and find the missing pieces.
The extended team reviews the models and documentation produced in this phase, making any changes that seem necessary.
The models and documentation are forwarded to the methodology unit representative with the compliance form (use the Compform template), and a methodology walkthrough is scheduled with the core team and the methodology representative. Before the walkthrough, the methodology representative reviews the documentation packet, and completes the compliance form (or a draft version of the form).
At the walkthrough, the methodology representative can ask any questions and raise any issues about compliance with the methodology, or suggestions for improvement. If any changes are required, the team must complete the required step(s) and schedule a follow-up walkthrough with the methodology representative. When the walkthrough is completed successfully, the project continues with the next step.
The methodology representative completes the compliance form and returns the documentation packet to the project team.
The team discusses and identifies possible solutions to the business problem, and selects the solution they deem most appropriate.
The team draws up a proposed solution statement that includes:
- The technical plan--How are you going to get the project done? What are the phases? This should be explained in the Development Approach section of the Initiation Plan.
- The resource plan--What skill sets are needed? What does each skill set provide? Particularly important is the definition of the extended team for the next phase.
- The quality plan--How do we know when we're done? The success criteria should be explained in the Goals and Objectives section of the Initiation Plan, including measures that test for existence, quality, and quantity. Specification or requirements documents should provide this in greater detail.
The core team writes a recommendation on whether or not to proceed. Use the Recomend template, which includes space for the actual recommendation, and for the pros and cons associated with the recommendation.
The recommendation is forwarded to the project sponsor with the proposed solution statement for review, and the project sponsor decides whether or not the project is to go forward.