![]() |
![]() |
![]() |
|
| 4.3 Elementary Method "Bar Chart" (BAR) |
4.3 Elementarmethode "Balkenplan" (BALK)
1 Identification/Definition of the Method
2 Brief Characteristic of the Method
The Bar Chart (BAR) or GANTT diagram is a method applied for the scheduling and control of projects. It is used to illustrate duration and time sequence of the activities in a project.
Means of Representation
Begin, end, and duration of the project activities are entered into a calender in form of a bar. Depending on the objective of the bar chart, they might be differently grouped and represented so e. g. an allocation to staff members is included. The grid of the calender adheres to the level of refinement or the planning and to the size and complexity of the project; normally it is structured into months or weeks.
The control of actual and planned value is realized by differentiating between actual and planned bars in the representation (e. g. color, shade). Deviations from the planned status can easily be detected by means of the calender entries.
3 Limits of the Methods Application
The interpretations of the bar chart mentioned below schedule, milestone, personnel, and resource plan depend on each other. Changing a target date in one of the plans usually results in modifications in one or several other plans. In planning activities, the highest priority should be given to the factor limiting most.
4 Specification of the Methods Allocation
| No. | Activity | Description |
|---|---|---|
| 4.1 |
PM1.5 Generation of Preliminary Plan |
The Bar Chart will be applied under different aspects:
In the schedule plan, the activity-related effort planning and time scheduling will be documented (subproducts in question: Project Plan.Deadlines (Planned and Actual) for SD/QA/CM/PM Activities, Project Plan.Delivery and Supply Deadlines). The milestone plan includes the documentation of the scheduling for important project states (subproduct in question: Project Plan.Milestone Plan). The personnel plan documents the staff-member-related deadline effort planning and time scheduling (subproduct in question: Project Plan.Staff). The resource plan documents the resource planning of hardware, software, equipment, and infrastructure (subproduct in question: Project Plan.Resources).
|
| 4.2 |
PM4 Detailed Planning |
The information listed under 4.1 goes for the "Detailed Planning" too. In PM1.5 - Generation of Preliminary Plan, BAR is applied with regard to the main activities of the project; in PM4 - Detailed Planning, BAR is applied with regard to the subactivities, up to the lowest level.
BAR is applied in the sense of a
|
| 4.3 |
PM8 Project Control |
Here the method BAR will be applied for an actual/planning control. It is realized by comparing the actually occurred deadlines and the actually utilized resources with the values planned in the bar chart. The result is entered into the report documents. Therefore it is not possible in this case to talk about the coverage of the product.
Activity PM8 - Project Control is covered by the supplementary application of the methods EVT - Earned Value Method and TRDA - Trend Analysis which both make information about the actual/planned status possible under various aspects. In this connection, BAR produces the information about the actual situation of the project as compared to the planned deadlines. |
| 4.4 |
QA1.2 Generation the Assessment Plan |
Method BAR is applied in the sense of a scheduling plan (compare 4.1 [1]) and also in the sense of a resource plan (compare 4.1 [4]). In both case, BAR is sufficient for covering the subproduct Assessment Plan.Time Schedule. |
| 4.5 |
SD2.6 Specification of System Integration |
Method BAR is applied within the scope of the SD activities in the sense of a scheduling plan (compare 4.1 [1]). BAR thus meets the requirements for the subproduct Integration Plan.Integration Network Plan. |
| 4.6 |
SD1.8 Generation of Software Maintenance and Modification Concept |
Method BAR is applied within the scope of this activity in the sense of a scheduling plan (compare 4.1 [1]). BAR thus meets the requirements for the subproduct SWMM Concept.Transition to Utilization with regard to the chronological plan of the transition process. |
5 Interfaces
| No. | Interface | Observation | Information in Annex 1 |
|---|---|---|---|
| 5.1 | BAR-NPT |
The results generated for the activity list within the scope of the structural analysis of the NPT - Network Planning Technique are used as the basis for a Bar Chart.
When converting the bar chart into a framework for the network plan, the content and subject of the work packages, the effort and duration as well as the begin and the end deadlines, the allocation of the work packages to the projects, personnel, etc. will be used. When converting the network plan into a bar chart, the content and subject of the work packages, the effort and duration as well as the begin and the end deadlines of the work packages will be used. |
4.2 Interface BAR-NPT |
6 Literature
7 Functional Tool Requirements
![]() |
![]() |
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
![]() |