General

	Purpose of this Diagrams Set is to collect Planning related Diagrams.
	Scope: There are Planning related diagrams in the section above. The Planning Diagrams are served as a reminder tools during the Planning processes.
	Status: Draft release.

Warning: If you think that you have discovered any copyright violation on page, please notify me immediately by e-mail: This e-mail address is being protected from spam bots, you need JavaScript enabled to view it . Thank you.

Glossary and Abbreviations

• IT - Information Technologies
• IS - Information Systems

Planning

There is a lot of books and articles related to Planning which repeats same information again and again. Here are some rare diagrams placed to pay attention to or to use them as a tools.

Planning:: Planning at Startup

Figure 1 shows processes which should be started at the startup of the project. Roles should be defined and documented as well.

Fig.1: Planning:: Planning at a Startup

Planning:: Planning at Startup:: Steering committee meetings

Steering committee meetings are used as a forum for creating a common understanding of the project progress. This in turn lays the foundation for coordinating the work within development and across the different functional areas.

Planning:: Planning at Startup:: Requirements clarification

Requirements clarification is as follows:

1. Splitting compound requirements into several requirements
2. Adding definitions of terms (glossary) and using them consistently
3. Using a common sentence structure and the teem "shall"
4. Adding details
5. Quantifying statements when possible
6. Defining attributes for each requirement, e.g., assigning a requirement to a software component, classifying its priority, estimating its efforts, or associating it with another requirement it depends on

Only two roles (persons) are working on the Product Requirements refining and clarification cycle: Customer (or Customer Proxy) and Project Manager. All the team members are working to produce the Schedule.

Planning: Plan Components

Figure 2 shows Plan Components and their relationship.

Fig.2: Planning:: Plan Components 

Planning:: Information Technologies Hierarchy

It is important keep in mind Information Technology Hierarchy shown on Figure 3 for the period of the planning of new system.

Fig.3: Planning:: Information Technologies Hierarchy

During the process of the System Development it is necessary to bear in mind that hardware platform should be decided on the later Stage, when all higher level planning is done. Time line on the Fig. 3 goes from top to bottom (i.e. before Application Software Stage will be decided it is necessary to have good understanding of the Business Transactions it should serve).

Width of the pyramid at the given Stage level is proportional to the amount of the people involved in the Stage (e.g. to make proper Strategic Planning team should be not more than 3-5 people, and on the later stages more people should be involved).

Downloads

	Diagrams from the above Diagram Set could be downloaded in Zip format here:
	planning_dia.zip
	Diagrams are created in Dia format. For Unix/Linux users it is a standard diagram drawing software. Windows users can obtain legal GPL-ed copy of Dia from http://dia-installer.de/index_en.html

Your Comments

It could be really great if you find time to submit your comments, corrections, and other feedback to This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

Regards,
 
Sergei