Share the diagrams with others in the organization in seeking their view of who and what is involved. Once you have drafted your context diagram, it's essential to validate your analysis. Incoming relationship flows trigger the start of an internal activity within your organization. Then label the flows with what interactions are taking place and whether they are incoming or outgoing. Using the right angles for the relationship flows simplifies the diagram and enables greater area to label the flows. As you identify and place the external entities onto your diagram, begin to connect the relationships that occur between each external entity and your organization by drawing one directional arrow either coming or leaving the organization. Not having control essentially means having to work within the constraints and constrictions imposed by their entity, such as legislation, regulations, industry and international standards. You may need them to adapt to your needs, for instance, having them use a template supplied by your organization or complying with secure electronic bank standards. An example of influence may be the ability to negotiate an agreement. Remember, a box is used to represent entities where your organization only has influence over. Throughout the analysis, you'll become aware of more external entities. Each box will represent a single entity that interacts with the organization. As they are external to your organization, you will place them in a box. From your research and discussions, begin to add all the external stakeholders around the outside of the circle. Remembering a circle is used to indicate what you have control over, what and how things happen within the organization. All interactions with the external entities will stem in and out from the circle. Start with the main entity that you wish to provide the context for by drawing a circle in the middle of the page with its name inside the circle. If you find your page needs to be really big to fit everything in, then you're probably overcomplicating it and need to pull yourself back out of the detail. There's a tendency to dive into the detail and try and fit in too much information. Why? Well, having a single page forces you to keep your diagram at the highest level. As a rule of thumb, you should start with a single page. We need to keep it simple and high level. The important thing is to remember that this is the start of our business process modeling. In my experience, all of the above are great ways to begin building your knowledge and validate your context diagram. You can research the organization on the intranet, ask colleagues a lot of questions, or run a series of workshops with key people with business knowledge. There are a few easy steps to creating a good context diagram, but before you can begin to piece together how the organization fits in the big picture, you first need to do some research. But not enough detail, people will start to worry you missed something. Too much detail, and people won't engage. As with any diagram, making complex things simple is the aim of the game.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |