Austin Martin Electronic Project

1

BUSA 428

Spring 2021

Project
Management

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

BUSA 428 Course
Project

2

COURSE PROJECT GOAL (IE)

Identification of Problems/Tasks:

– Understand the problems presented
– Provide appropriate information with associated objective evidence

Analysis:

– Evaluate and provide relevant impact of the problems presented
– Provide responses using information from quantitative measures as derived from

software tool results

Solutions and Recommendations:

– Provide solution to task/problems presented along with any associated action
plans

PROJECT INSTRUCTIONS

Use the project response Word document posted in doc sharing and begin to respond to all

questions

Be sure and address each question/request in detail providing emphasis on project objectives

All graphs/charts/tables are to be produced in the native format (excel, project, etc.) and

then copied into the response area of the Management Word document

Major Submission Requirement: Post BOTH the Management Word document with all

responses/graphs/charts/tables AND the objective evidence (the native documents from where

you copied the charts/graphs/tables)

Project Due Date: 21 April 2021

GRADING CRITERIA

Cover all points in the response. Use the Word document posted as the template for all

responses and task work. The Word document will be the formal response back to Astin

Martin Electronics. All tables, graphics, and figures created by other tools should be

copied and pasted in the Word document maintaining a professional appearance with

3

appropriate labeling of all figures, diagrams, tables, artifacts pasted. As this is a

professional document, do not leave template examples in your submission.

Where applicable, provide clear documentation, graphics, diagrams, and tables that

help clarify any responses.

STATEMENT OF WORK SUMMARY

Software Project Team (YOU): JBB Software

Customer: Astin Martin Electronics LLC

RFP awarded for specific message services which will be incorporated into an

electronic instrument company (Astin Martin Electronics LLC) interface to electronic

gauges. Topical level requirements for the software were provided. Deliverable products

include:

– Systems Engineering to provide appropriate requirements decomposition
– Software Engineering to provide design/development/unit test of software
– System Test Engineering to provide component and enterprise level testing
– Quality Engineering to provide quality control through the entire development life

cycle
– Management functions to include all primary functions (project management,

finance, planning & scheduling, Overhead support (contracts, engineering matrix,
etc.)

Award date of May 15 and required completion date (deliverables provided) of

November 15.

Astin Martin Electronics request of planned deliverables, acceptance criteria, quality

plan, and work breakdown structure. These items need to be provided in an acceptable

time for Astin Martin to review and approve.

Astin Martin Electronics further requests other deliverables to include final software

(source and binary) which meets all approved acceptance criteria, associated design

documents (system and development level)

All project questions or request for project scope changes should be directed to the

Astin Martin Electronics designee (course instructor).

There is no requirement relative to project tools used to generate the required data.

Topical requirements include:

– System Engineering: UML design artifacts for graphic widgets to display
aeronautical expanse gauges for interface testing within the technical specs
guidelines for twenty-five different visual aspects. Include appropriate level of
peer review. Design should include graphical mock-up of gauges.

4

– 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: Provide appropriate level design artifacts from System
Engineering UML design artifacts. Include appropriate level of peer review.

– Software Engineering: Code and Unit Test software modules that execute the
software which meets all topical and derived requirements

– System Test Engineering: Derive sell-off acceptance criteria. Include appropriate
peer review (including System Engineering) and customer approval.

– System Test Engineering: Derive System and Enterprise Level Test Cases.
Include appropriate level of peer review.

– System Test Engineering: Execute test cases as software modules become
available

– Quality Engineering: Provide 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), and Final Acceptance Test (software
demonstration at customer facility showing software meets all requirements as
installed)

Approved labor rates ($/hr.) as follows:

– System Engineer I: 42.15
– System Engineer II: 46.37
– System Engineer III: 50.17
– Lead System Engineer: 55.93
– Software Engineer I: 42.38
– Software Engineer II: 46.61
– Software Engineer III: 52.01
– Lead Software Engineer: 58.76
– System Test Engineer I: 42.76
– System Test Engineer II: 41.62
– System Test Engineer III: 47.25
– Lead System Test Engineer: 53.21
– Quality Engineer I: 41.38
– Quality Engineer II: 46.54
– Quality Engineer III: 53.11
– Lead Quality Engineer: 59.89
– Project Manager: 95.52 (LOE – Level of Effort)
– Chief Engineer: 74.41 (LOE – Level of Effort)

Approved overhead rates as follows:

– : 6.4% of total hours
– Planning & Scheduling: 5.1% of total hours

5

– Management (Contracts/Senior Management): 2.2% of total hours
– Facility: 1.9% of total hours
– HR/Staffing: 0.62% of total hours

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.

6

Quality Engineering: Provide quality checks.

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. (* Minimum of 12 tasks)

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

7

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).

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

*** Add more WBS activities as required or you deem necessary ***

Example: May want to add WBS level for Quality Engineering for derived tasks or those

tasks could be incorporated in the WBS items noted above.

NOTIONAL ACTIVITY DURATION
SCHEDULE

Notional Activity estimated Duration

The estimated total elapsed time for how long an activity will take from starts

to finish, including associated waiting time. Also referred to as activity

resource estimated or estimated activity resources.

Example only: Does not reflect tasks of this assignment. Be sure and remove any

examples in your management response document.

8

PROJECT QUESTIONS & TASKS

1. Provide a project objective associated with the Astin Martin Electronics project.
Include a list of assumptions about the project.

2. What is a work breakdown structure? What is a responsibility matrix? Using the Astin
Martin Astin Martin Electronics project activity list and activity duration schedule,
create a WBS and RAM.

Work Breakdown Structure (Should provide hierarchical graph)

???

Responsibility Assignment Matrix

??? (Example RAM Template: From different requirements.
Be sure and remove any examples in your management response
document.)

TaskDate 15-May 25-May 5-Jun 15-Jun 25-Jun 5-Jul 15-Jul 25-Jul 5-Aug 15-Aug 25-Aug 5-Sep 15-Sep 25-Sep 5-Oct 15-Oct 25-Oct 5-Nov 15-Nov

Select Layout

Design Graphics

Approve Design

Write Content

Approve Content

Insert content into page

Set up test web service

Perform tests

Approve web service

Go live

Plan Duration Actual Start % Complete (beyond plan)

Baseline Schedule

9

10

3. (Major) List all activity costs. From the project activity list and activity duration
schedule, estimate the cost of each activity. Then, determine the Total Budgeted Cost
(TBC) for the Astin Martin Electronics project. Provide the information in table format
by month. Objective evidence of derived costs is required for credit. Use labor and
overhead rates as provided in your derived calculations.

(Example Template: Does not reflect tasks associated with this assignment. Be
sure and remove any examples in your management response document.)

4. Provide a cumulative budgeted cost curve and monthly budget curve for the Astin
Martin Electronics project. Provide in appropriate graph format. This should
represent both monthly budget and TBC over the period of performance of the
project.

5. Astin Martin Electronics wants to know if you plan to use a management reserve for
their project. Explain what the term reserve means and why you will use contingency
reserve in the project or not. Be sure and consider the implications of using or not
using the reserve. Provide appropriate detail in your response.

6. Astin Martin Electronics wants to know how JBB Software plans to employ cost
management and earned value (EV) in their project. Explain to Astin Martin
Electronics why it is necessary to calculate the earned value of work performed and
how you plan to execute this task.

7. Astin Martin Electronics is concerned about how JBB Software will manage risks.
Describe what JBB Software plans to do in order to manage risk on the Astin Martin
Electronics project and if a risk assessment matrix will be employed and why.
Provide appropriate level of detail in your response.