Unit 6: Network Diagram View - Subjective Questions

Network Diagram view is a graphical representation of the tasks in a project and the logical relationships between them. Each task is displayed as a node or box, while connecting lines represent dependencies.

Its primary purposes are:

• To show the sequence in which project activities must occur.
• To identify predecessor and successor relationships.
• To understand the logical flow of the project.
• To locate tasks that may affect the project schedule.
• To analyze summary tasks and their subordinate activities.

The view helps a project manager understand the project structure more clearly than a simple task list.

To examine a Network Diagram, the project manager studies both the task nodes and the connecting link lines.

Important information includes:

• Nodes: Usually display the task name, task identification number, duration, start date, finish date, or other selected fields.
• Link lines: Show dependencies between tasks.
• Direction of links: Indicates which task must occur before another task.
• Summary nodes: Represent groups of related subtasks.
• Node formatting: May identify task status, task type, or critical activities.
• Relationship indicators: Show whether the dependency is Finish-to-Start, Start-to-Start, Finish-to-Finish, or Start-to-Finish.

By following the diagram from the beginning to the end, the project manager can understand the workflow and detect missing or incorrect relationships.

A summary task is a higher-level task that groups several related subtasks under one heading. In Network Diagram view, it may be displayed as a separate summary node containing information about the group of activities.

Summary tasks are useful because they:

• Organize a complex project into manageable phases.
• Provide an overview of a group of activities.
• Show the overall start and finish period of the grouped tasks.
• Help analyze relationships between project phases.
• Make the diagram easier to read by reducing unnecessary detail.

The summary task does not usually represent one independent physical activity. Instead, it summarizes the schedule characteristics of its subordinate tasks.

A regular task node represents one specific project activity, whereas a summary task node represents a collection of related subtasks.

Summary nodes are valuable for overview and organization, while regular nodes provide the detailed schedule information needed for execution.

The general procedure for changing to Network Diagram view is as follows:

1. Open the required project file.
2. Select the View tab or view-selection control.
3. Locate the group containing task views.
4. Select Network Diagram.
5. Wait for the project tasks and relationships to be displayed as nodes and link lines.
6. Adjust the zoom or layout if the entire diagram is not visible.

The exact command names may vary slightly between project management applications, but the objective is to select the view that displays tasks as connected network nodes.

Zooming changes the scale at which the Network Diagram is displayed. It is especially useful when a project contains many tasks and relationships.

To view the whole project:

• Open the zoom control in Network Diagram view.
• Reduce the zoom percentage or choose a Fit to Window or Entire Project option.
• Check that the first and last major tasks are visible.
• Increase the zoom again when detailed editing is required.

A lower zoom level provides an overall view of the project flow, while a higher zoom level makes task names, dates, and relationship details easier to read. Zooming changes only the display scale and does not change task data.

A node can generally be opened for editing by using either of the following methods:

• Double-click method: Double-click the required task node. A task information or formatting dialog box opens, allowing the task properties to be edited.
• Context-menu method: Right-click the node and select an appropriate command such as Task Information, Edit Task, or Format Node.

After editing, the user should confirm the changes using OK, Apply, or an equivalent command. The diagram may then be refreshed so that the updated task information and relationships are shown correctly.

Direct editing allows selected task information to be changed without opening a separate task information dialog.

A typical procedure is:

1. Select the required node.
2. Click the task name or editable field inside the node.
3. Type the new value or modify the existing text.
4. Press Enter or click outside the node to confirm.
5. Review the resulting network relationships and layout.

Advantages include:

• Faster correction of task names or visible values.
• Less interruption to the scheduling workflow.
• Convenient editing while examining task dependencies.
• Immediate visual confirmation of the change.

Direct editing should be used carefully because changing task information may affect the schedule and connected activities.

Laying out the boxes means arranging task nodes and their link lines in a readable and logical position within the Network Diagram.

A good layout is important because it:

• Makes the sequence of activities easy to follow.
• Reduces crossing link lines.
• Prevents nodes from overlapping.
• Separates different project phases clearly.
• Helps users identify predecessors and successors quickly.
• Improves the presentation of summary tasks.

Automatic layout tools can arrange the diagram according to the dependency structure. Manual adjustments may still be necessary when the automatically generated layout is crowded or difficult to interpret.

Layout controls determine how nodes are arranged and how much information is displayed in the diagram. Common controls include:

• Automatic layout: Arranges nodes based on their relationships.
• Flow direction: Places tasks from left to right, right to left, top to bottom, or bottom to top.
• Spacing: Controls the horizontal and vertical distance between nodes.
• Alignment: Aligns nodes along common rows or columns.
• Level or hierarchy settings: Organize tasks according to dependency levels.
• Display options: Control whether summary tasks, link labels, or task details are visible.
• Layout refresh or reflow: Recalculates positions after changes are made.

These controls help produce a diagram that is both structurally accurate and visually understandable.

To move a node manually:

1. Place the pointer over the task node.
2. Select and hold the node.
3. Drag it to the desired position.
4. Release the pointer when the node is correctly placed.
5. Check that the link lines still connect clearly to the node.

Precautions include:

• Move the complete node rather than editing its text accidentally.
• Avoid placing the node over another node.
• Keep the direction of the workflow understandable.
• Do not assume that moving a node changes task dependencies; it changes only the visual position.
• Reapply automatic layout if manual positioning makes the diagram confusing.

Copying a node can be used when a new task is similar to an existing task.

A typical procedure is:

1. Select the existing task node.
2. Use the Copy command or the corresponding keyboard shortcut.
3. Paste the node into the required location.
4. Change the copied task name and other properties so that it represents a distinct activity.
5. Create the required dependency by dragging from the predecessor or successor connector, or by using a task-link command.
6. Verify the resulting dates and relationships.

The copied node must receive a unique task identity. Copying the visual appearance alone does not necessarily create a valid schedule relationship. Adding a link may change the timing of the copied task and all dependent tasks, so the schedule should be recalculated and reviewed.

Node content determines which task fields are visible inside each box. Common fields include:

• Task identification number.
• Task name.
• Duration.
• Start and finish dates.
• Resource names.
• Completion percentage.
• Task status.
• Constraint information.
• Critical-path or slack information.

Changing node content improves analysis by displaying the information most relevant to the current task. For example, a planning review may require dates and durations, while progress monitoring may require status and percentage complete. Showing too many fields can make the diagram crowded, so the content should be selected according to the purpose of the analysis.

To change a node border:

1. Select the required node or group of nodes.
2. Open the formatting or node-style settings.
3. Select the border color.
4. Select a border style, such as solid, dashed, or dotted, and choose a suitable width if available.
5. Apply the changes and review the diagram.

Formatting can be useful for visual classification. For example:

• A distinct border can identify critical tasks.
• A different style can distinguish summary tasks from regular tasks.
• Color can highlight milestones, delayed activities, or completed tasks.
• Consistent formatting can improve readability across project phases.

Formatting should remain consistent and should not be used as a substitute for accurate task data.

The display of a summary task can usually be changed through its node-formatting or layout settings. Possible changes include:

• Showing or hiding the summary node.
• Displaying the summary task as a single consolidated box.
• Showing its subordinate tasks in an expanded form.
• Changing the fields shown inside the summary node.
• Applying a distinct border, color, or shape.
• Controlling whether links connect to the summary task or to its subtasks.

The selected style should depend on the purpose of the diagram. A consolidated summary node is useful for high-level reporting, while an expanded display is better for detailed planning and dependency analysis. The display must accurately communicate the relationship between the summary task and its subtasks.

The four standard dependency types are:

• Finish-to-Start (FS): The predecessor must finish before the successor can start. This is the most commonly used relationship.
• Start-to-Start (SS): The successor cannot start until the predecessor starts.
• Finish-to-Finish (FF): The successor cannot finish until the predecessor finishes.
• Start-to-Finish (SF): The successor cannot finish until the predecessor starts. This relationship is less common.

The relationship type describes the logical condition between two tasks. It is different from the physical appearance or position of the connecting line in the diagram.

To view a relationship type:

1. Select the link line between the predecessor and successor nodes.
2. Open the link properties, task dependency details, or equivalent context-menu command.
3. Examine the displayed dependency type and any lead or lag value.
4. Close the properties after reviewing or confirming the relationship.

This information is important because the same two tasks can have different scheduling meanings. A Finish-to-Start link indicates sequential work, while a Start-to-Start link permits overlapping work after the predecessor begins. Incorrectly identifying the relationship can produce unrealistic dates, excessive delays, or unsafe parallel activities.

To change a relationship type:

1. Select the link line connecting the two task nodes.
2. Open the dependency or link-properties dialog.
3. Select the required relationship, such as FS, SS, FF, or SF.
4. Specify lead or lag if the project requires it.
5. Confirm the change.
6. Review the task dates and downstream activities after the schedule recalculates.

Afterward, check:

• Whether the new dependency represents the real work sequence.
• Whether the successor date changed as expected.
• Whether any constraints or deadlines are violated.
• Whether critical-path or slack information changed.
• Whether the link is still connected to the intended tasks.

To remove a link line:

1. Select the link line between the two task nodes.
2. Use the Delete, Remove Link, or equivalent command.
3. Confirm the action if prompted.
4. Review the task relationships and schedule dates.

Removing a link deletes the logical dependency between the tasks. The successor may then be scheduled earlier or may become disconnected from the intended workflow. Risks include:

• Creating an unrealistic task sequence.
• Allowing work to start before required information is available.
• Changing the critical path.
• Producing incorrect project completion dates.
• Losing an important scheduling rule.

The link should be removed only when the real project process no longer requires that dependency.

To manually add a link line:

1. Select the predecessor task node.
2. Use its dependency connector or linking command.
3. Drag the connector to the successor task node, or select the successor through a dependency dialog.
4. Release the pointer or confirm the command.
5. Open the link properties to verify the relationship type.
6. Check for any required lead or lag.
7. Review the recalculated schedule.

Validation should confirm that:

• The link connects the intended predecessor and successor.
• The relationship type is correct.
• No circular dependency has been created.
• The task dates remain realistic.
• The new link does not accidentally remove or replace another dependency.
• The diagram remains readable.