In: Operations Management
Using the Astin Martin Astin Martin Electronics project activity list, create a WBS.
ACTIVITY / TASK LIST BY LOWEST WBS LEVEL LEG
2.1 Systems Engineering: UML Design for Interface
System Engineering: Create outline of UML and derived requirements
artifacts. Software Engineering: Assist system engineering.
Quality Engineering: Provide quality checks
2.2 Systems Engineering: System/Software Design
System Engineering: Design appropriate software components to display aeronautical expanse gauges within the technical specs guidelines for twenty-five different visual aspects. Include appropriate level of peer review.
Software Engineering: Assist system engineering. Quality Engineering: Provide quality checks.
2.3 Systems Engineering: Approve design
System Engineering: Derive component level requirements for Software Engineering to design, code, and unit test and System Test can provide System and Enterprise level testing.
Software Engineering: Assist system engineering
System Test Engineering: Derive sell-off acceptance criteria. Include appropriate peer review (including System Engineering) and customer approval.
Quality Engineering: Provide quality checks.
3.1 Software Engineering: Approve Content S/W Component Design System Engineering: Assist software engineering
Software Engineering: Provide appropriate level design artifacts from System Engineering UML design artifacts. Include appropriate level of peer review.
System Test Engineering: Derive sell-off acceptance criteria. Include appropriate peer review (including System Engineering) and customer approval.
Quality Engineering: Provide quality checks.
5
3.2 Software Engineering: Code and Unit Test System Engineering: Assist software engineering
Software Engineering: Code and Unit Test software modules that execute the software which meets all topical and derived requirements.
Quality Engineering: Provide quality checks.
3.3 Software Engineering: Function Test (with actual gauges)
System Engineering: Assist software engineering
Software Engineering: Check the function
Quality Engineering: Provide quality checks.
4.1 Test Engineering: Design Test Artifacts
System Engineering: Support with other engineers for opinion
Software Engineering: Support with other engineers for opinion
System Test Engineering: Derive System and Enterprise Level Test Cases. Include appropriate level of peer review.
Quality Engineering: Provide quality checks.
4.2 Test Engineering: Perform Environment Level Tests
System Engineering: Support with other engineers for opinion
Software Engineering: Support with other engineers for
opinion
System Test Engineering: Execute test cases as software modules
become available Quality Engineering: Provide quality checks.
4.3 Test Engineering: Approve Test Services (with Customer Acceptance Criteria) System Test Engineering: Assist Quality Engineering
Quality Engineering: Quality checks during the processes described for System Engineering, Software Engineering, and System Test Engineering as appropriate
Include the following customer related reviews: Design Review (after System Engineering completes design artifacts), Pre-Ship Review (provided prior to Astin Martin Electronics acceptance of software).
6
4.4 Test Engineering: Run Test on Live Environment (Customer Facility) System Test Engineering: Assist Quality engineering
Quality Engineering: quality checks, and Final Acceptance Test (software demonstration at customer facility showing software meets all requirements as installed) installed)
4.5 System Test Engineering: Deploy to Operational Environment (Customer Facility) System Test Engineering: work with customer facility team for full deployment
Use approved installation instructions to deploy software into operational environment with support from customer facility team
Assumptions are a series of events which are expected to occur/happen during a Project Life Cycle. This mostly happens without any proof.
As there never exist a complete certainty within a project plan, we can’t emphasize on the change & risk management involved.
1. A Work Breakdown Structure (WBS) in project management and systems engineering, is a deliverable oriented breakdown of a project into smaller components. A work breakdown structure is a key project deliverable that organizes the team's work into manageable sections.