Software Project Team (YOU): JBB Software Customer: Astin Martin Electronics LLC RFP awarded for specific message services which will be incorporated into a n 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 provid e 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 de velopment 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 Electroni cs 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 di splay 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 artifac ts. 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 appropr iate 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 Engineeri.

1. Software Project Team (YOU): JBB Software
Customer: Astin Martin Electronics LLC
RFP awarded for specific
message
services which will be incorporated into a
n
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 provid
e appropriate requirements decomposition

2. -
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 de
velopment 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.

3. 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
Electroni
cs
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

4. generate the required data.
Topical requirements
include:
-
System Engineering: UML design
artifacts
for
graphic widgets to di
splay
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.

5. 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 artifac
ts. 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
-

6. off acceptance criteria. Include appropr
iate
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

7. (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)
Appr
oved labor rates as follows:
-
System Engineer I: 4
1
.15
-
System Engineer II: 4
7

8. .37
-
System Engineer III: 51.17
-
Lead System Engineer: 5
6
.91
-
Software Engineer I: 4
2
.38
-
Software Engineer II: 47.62
-
Software Engineer III: 51.01
-
Lead Software Engineer: 5
8

9. .83
-
System Test Engineer I: 4
1
.78
-
System Test Engineer II: 43.
62
-
System Test Engineer III: 49.25
-
Lead System Test Engineer: 5
5
.25
-
Quality Engineer I: 40.38
-
Quality Engineer II: 47.55

10. -
Quality Engineer III: 5
2
.01
-
Lead Quality Engineer: 59.83
-
Project Manager: 91.
5
5
(LOE
–
Level of Effort
)
-
Chief Engineer: 7
5
.41 (LOE

11. –
Level of Effort
)
Approved
overhead
rates as follows:
-
Finance:
6
.
2
% of total hours
-
Planning & Scheduling:
5
.
5
% of total hours

12. 5
-
Management (Contracts/Senior Management): 2.
1
% of total hours
-
Facility: 1.
2
% of total hours
-
HR/Staffing: 0.5
5
% of total hours
ACTIVITY / TASK LIST BY LOWEST WBS LEVEL LEG
2.1
Systems Engineering
: UML Design

13. 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 techn
ical specs guidelines for twenty
-
five different visual
aspects. Include appropriate level of peer review.

14. Software Engineering: Assist system engineering.
Quality Engineering: Provide quality checks.
2.3
Systems Engineering:
Approve design
System Enginee
ring: 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 acce
ptance criteria. Include appropriate peer
review (including System Engineering) and customer approval.
Quality Engineering: Provide quality checks.
3.

15. 1
Software Engineering:
Approve
C
ontent
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
revi
ew (including System Engineering) and customer approval.
6
Quality Engineering: Provide quality checks.

16. 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 Engineer
ing: Check the function
Quality Engineering: Provide quality checks.
4.1
Test Engineering: Design Test Artifacts
System Engineering:
Support

17. with other engineers for opinion
Software Engineering:
Support
with other engineers for opinion
System Test Engine
ering: 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

18. 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 appropriat
e
7
Include the following customer related reviews: Design Review
(after System

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

20. operational environment
with s
upport 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:

21. Does not reflect tasks of this assignment
.
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 resp
onsibility matrix?
Using the Astin
Martin

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