conveyer belt project parts 1 and 2
1.0 Conveyer Belt Project
1.1 Hardware
1.1.1 Hardware Specifications
1.1.2 Hardware Design
1.1.3 Hardware Documentation
1.1.4 Prototypes
1.1.5 Order Circuit Boards
1.1.6 Assemble Preproduction Models
1.2 Operating System
1.2.1 Kernel Specifications
1.2.2 Drivers
1.2.2.1 Disk Drivers
1.2.2.2 Serial I/O Drivers
1.2.3 Memory Management
1.2.4 Operating System Documentation
1.2.5 Network Interface
1.3 Utilities
1.3.1 Utilities Specifications
1.3.2 Routine Utilities
1.3.3 Complex Utilities
1.3.4 Utilities Documentation
1.3.5 Shell
1.4 System Integration
1.4.1 Architectural Decisions
1.4.2 Integration First Phase
1.4.3 System Hardware/Software Test
1.4.4 Project Documentation
1.4.5 Integration Acceptance Testing
The work breakdown structure essentially is a decomposition of the work to be completed by the project team in order to successfully accomplish the project objectives and deliverables. It’s a very practical tool to visualise the work that needs to be done, however that is about all it’s useful for. The information provided by the work breakdown structure is not enough to allow the project team to identify any milestones or points of significance in the project. At this stage each element of the project has only been identified, none of them have been time scheduled, cost estimated or placed in a definitive chronological order, making it difficult to identify any significant milestones.
Network scheduling refers to the graphical representation of activities that define the sequence of work in a project. It is an important tool used to visualise the chronological order of activities needed to be completed in order to meet the project deliverables and objectives. The project team decided to use Microsoft project to develop the network schedule for the conveyer belt project. However before a network schedule could be produced it was necessary to enter some important information into Microsoft project. Firstly the work calendar had to be
1.1 Hardware
1.1.1 Hardware Specifications
1.1.2 Hardware Design
1.1.3 Hardware Documentation
1.1.4 Prototypes
1.1.5 Order Circuit Boards
1.1.6 Assemble Preproduction Models
1.2 Operating System
1.2.1 Kernel Specifications
1.2.2 Drivers
1.2.2.1 Disk Drivers
1.2.2.2 Serial I/O Drivers
1.2.3 Memory Management
1.2.4 Operating System Documentation
1.2.5 Network Interface
1.3 Utilities
1.3.1 Utilities Specifications
1.3.2 Routine Utilities
1.3.3 Complex Utilities
1.3.4 Utilities Documentation
1.3.5 Shell
1.4 System Integration
1.4.1 Architectural Decisions
1.4.2 Integration First Phase
1.4.3 System Hardware/Software Test
1.4.4 Project Documentation
1.4.5 Integration Acceptance Testing
The work breakdown structure essentially is a decomposition of the work to be completed by the project team in order to successfully accomplish the project objectives and deliverables. It’s a very practical tool to visualise the work that needs to be done, however that is about all it’s useful for. The information provided by the work breakdown structure is not enough to allow the project team to identify any milestones or points of significance in the project. At this stage each element of the project has only been identified, none of them have been time scheduled, cost estimated or placed in a definitive chronological order, making it difficult to identify any significant milestones.
Network scheduling refers to the graphical representation of activities that define the sequence of work in a project. It is an important tool used to visualise the chronological order of activities needed to be completed in order to meet the project deliverables and objectives. The project team decided to use Microsoft project to develop the network schedule for the conveyer belt project. However before a network schedule could be produced it was necessary to enter some important information into Microsoft project. Firstly the work calendar had to be