Project Work Breakdown Structure WBS
7.4.1 Project Work Breakdown Structure WBS
The Project Work Breakdown Structure WBS is a tool that allows project managers to define task sets, milestones and deliverables. It is a systematic analysis approach of depicting a project as a set of discrete pieces of work. The tasks and milestones can be used in a project to track development or maintenance. Two methods are used in defining the work breakdown structure, namely, the Work Breakdown Analysis and WBS Top-down Decomposition and Bottom-up Integration. Work Breakdown Analysis The Work Breakdown Analysis consists of the following steps: 1. Break the project into blocks of related activities. 2. Arrange the blocks into a logical hierarchy. • Analysis starts by identifying the major phases and the major deliverables that each produces. • For each activity, break them to define sub-activities and the work products produced by these sub-activities. • Continue to subdivide an activity until you get to an activity that cannot be subdivided anymore. This atomic activity is called the work unit or package. 3. Define the Work Unit or Package. The work unit or package is the responsibility of one person. It should be executed until it finishes without any interruption. Its duration and cost can be measured, and requires the continuous use of a resource group. WBS Top-down Decomposition and Bottom-up Integration Process This method defines two major activities as specified in its name, specifically, the top- down decomposition and bottom-up integration. 1. Top-down Decomposition • Identify 4-7 major components of work. Do not worry about the sequence. • Identify intermediate and final deliverables for each grouping. • Perform functional decomposition until a task has one owner, clear deliverables, credible estimates and can be tracked. • Use verb-object at lowest task level. Recommended number of levels is four 4. • Multiple iterations are required. 2. Bottom-up Integration • Brainstorm all possible tasks. • Organize task into 4-7 major groupings reflecting how the project will be managed. Software Engineering 313 J.E.D.I7.4.2 Work Breakdown Schedule Format
Parts
» | Komputasi | Suatu Permulaan
» Quality Focus Process Method Tools
» What is quality? How do we define quality?
» Software Quality Characteristics of a Well-engineered Software
» Software Quality Assurance Activities Formal Technical Reviews
» Types of Software Process Models
» Understanding Systems | Komputasi | Suatu Permulaan
» End-users Understanding People in the Development Effort
» What is documentation? Criteria for Measuring Usability of Documents
» Abstraction Encapsulation Review of Object-oriented Concepts
» Modularity Hierarchy Review of Object-oriented Concepts
» Project Assignment Object-oriented Process Model
» Modeling Activity Unified Modeling Language UML
» UML Baseline Diagrams Unified Modeling Language UML
» Requirements Engineering Concepts | Komputasi | Suatu Permulaan
» Inception Requirements Engineering Tasks
» Elaboration Negotiation Requirements Engineering Tasks
» Specification Validation Requirements Engineering Tasks
» Management Requirements Engineering Tasks
» Scenario Modeling Requirements Analysis and Model
» Requirements Model Validation Checklist
» InvoiceNumber : Numeric Here, an attribute named InvoiceNumber contains a numeric value.
» Ternary association which is a relationship of three or more objects of
» The Analysis Model Analysis Model Validation Checklist
» Requirements Traceability Matrix RTM
» Requirements Metrics | Komputasi | Suatu Permulaan
» The Design Model Design Engineering Concepts
» Describing the Package Diagram Developing the Architectural Design
» Software Architecture Validation Checklist
» Developing the Data Design Model
» Report Design Interface Design
» Forms Design Interface Design
» Basic Component Design Principles Component-level Design Guidelines
» Component Diagram Developing the Software Component
» Project Assignment Design Model Validation Checklist
» Mapping the Design Deliverables to the Requirements Traceability Matrix Design Metrics
» Creating the Data Design Model Creating the Interface Design Creating the Control Design
» Project Assignment Programming Standards and Procedures
» Using Pseudocodes Control Structure Guidelines Documentation Guidelines
» Implementing Packages | Komputasi | Suatu Permulaan
» Abstract Classes Implementing Controllers
» Interfaces Why do we use Interfaces?
» Interface vs. Abstract Class Interface vs. Class Creating Interfaces
» Relationship of an Interface to a Class Inheritance among Interfaces
» Implementing Java Database Connectivity JDBC
» AWT GUI Components Implementing the Graphical User Interface
» Layout Managers Implementing the Graphical User Interface
» Controlling the Version of the Software
» Introduction to Software Testing
» White-Box Testing Techniques Software Test Case Design Methods
» Black-Box Testing Techniques Software Test Case Design Methods
» Testing your Programs | Komputasi | Suatu Permulaan
» Test-driven Development Steps Test-driven Development Methodology
» Testing Java Classes with JUnit
» Testing the System | Komputasi | Suatu Permulaan
» Mapping the Software Testing Deliverable to the RTM Test Metrics
» Project Assignment Software Project Management
» Problem Identification and Definition
» The Project Team Structure Project Responsibility Chart
» Project Work Breakdown Structure WBS
» Work Breakdown Schedule Format
» Size-oriented Metrics- Lines of Codes LOC Function-Oriented Metrics: Function Points FP
» Project Estimations | Komputasi | Suatu Permulaan
» The Risk Table Risk Management
» Risk Identification Checklist Risk Management
» Baseline Software Configuration Tasks
» Writing the Project Plan Project Assignment Case Tools
Show more