PROJECT WORK (BUSINESS ANALYST)

-THERE ARE FOUR ATTACHMENTS WITH SAMPLE WORK. 

Save Time On Research and Writing
Hire a Pro to Write You a 100% Plagiarism-Free Paper.
Get My Paper

– EXCEL WORK 

– NEED PLAGIARISM REPORT

– ALL THE REQUIREMENTS ARE ATTACHED BELOW. 

– SHOULD STRICTLY FOLLOW THE INSTRUCTIONS. 

Save Time On Research and Writing
Hire a Pro to Write You a 100% Plagiarism-Free Paper.
Get My Paper

WB

S

OUTLINE 2.1 UML Design For Interface 2.1.1 Create Outline of UML 2.1.2 Derived Requirements Artifacts 2.2 System/Software Design 2.2.1 Design Software Components 2.2.2 P

eer Review 2.3 Approve Design

2.

3.1 Derive Component Level Requirements

2.

3.2 Unit test

2.

3.3 System and Enterprise Test 2.3.4 Derive sell-off Acceptance Criteria 2.3.

5 Peer review

3.1

Approve Content S/W Component

Design

3.1.1 Provide Design Crafts

3.1.2

Derive sell-off Acceptance Criteria

3.1.2

Peer Review

3.2

Code and

Unit Test 3.2.1 Code Test Software 3.2.2 Unit Test

Software

3.3

Function Test 3.3.1 Check the Function 4.1 Design Test Artifacts 4.1.1 Derive System Level Test Cases 4.1.2 Derive Enterprise Level Test Cases 4.1.3

Peer Review

4.2 Perform Environment Level Tests 4.2.1 Execute Test Cases 4.3 Approve Test Services 4.3.1 Quality Check 4.3.2 Design Review 4.3.3 Pre-Ship Review 4.4 Run Test on Live Environment 4.4.1

Quality Check

4.4.2 Final Acceptance Test 4.5 Deploy to Operational Environment 4.5.1 Work with Customer facility

WBS

Astin Martin LLC

2.1.1 Create Outline of UML

2.1.2 Derived Requirements Artifacts

2.2 System/Software Design

2.2.1 Design Software Components

2.2.2 Peer Review

2.3 Approve Design

2.3.1

Derive Component Level Requirements

2.3.2

Unit test

2.3.3

System and Enterprise Test

2.3.4 Derive sell-off Acceptance Criteria

2.3.5

Peer review

3.1

Approve Content S/W Component Design

3.1.1 Provide Design Crafts

3.1.2 Derive sell-off Acceptance Criteria

3.1.2 Peer Review

3.2

Code and Unit Test

3.2.1 Code Test Software

3.2.2

Unit Test Software

3.3 Function Test

3.3.1 Check the Function

4.1 Design Test Artifacts

4.1.1 Derive System Level Test Cases

4.1.2 Derive Enterprise Level Test Cases

4.1.3 Peer Review

4.2 Perform Environment Level Tests

4.2.1 Execute Test Cases

4.3 Approve Test Services

4.3.1 Quality Check

4.3.2 Design Review

4.3.3 Pre-Ship Review

4.4 Run Test on Live Environment

4.4.1 Quality Check

4.4.2 Final Acceptance Test

4.5 Deploy to Operational Environment

4.5.1 Work with Customer facility

2.1UML Design For Interface

RAM

2.1 UML Design For Interface

2.1.1

P S P S S S

2.1.2

P P S S

2.2 System/Software Design
2.2.1 Design Software Components S P S S S
2.2.2 Peer Review S P P S S
2.3 Approve Design
2.3.1 Derive Component Level Requirements S P P S S
2.3.2 Unit Test P S S
2.3.3 System and Enterprise Test P S S
2.3.4 Derive sell-off Acceptance Criteria P P S
2.3.5 Peer Review S P S P P P
3.1 Approve Content S/W Component
3.1.1

S S P S

3.1.2 Derive sell-off Acceptance Criteria S P S

Peer Review S P S P S

3.2 Code and Unit Test
3.2.1 Code Test Software S S S P P S
3.2.2

S P P S

3.3 Function Test
3.3.1

S S P S

4.1 Design Test Artifacts
4.1.1 Derive System Level Test Cases S P S P P P S
4.1.2 Derive Enterprise Level Test Cases S S S P S P S S
4.1.3 Peer Review S S S S P P
4.2

4.2.1 Execute Test Cases S P S P S P P S
4.3 Approve Test Services
4.3.1 Quality Check S S P S P P
4.3.2 Design Review S P S P
4.3.3 Pre-Ship Review S P P
4.4

4.4.1

S P S S P

4.4.2 Final Acceptance Test S S P S S P P
4.5 Deploy to Operational Environment
4.5.1

S S P P

Project manager Chief Engineer System Engineer | System Engineer || System Engineer ||| Lead System Engineer Software Engineer | Software Engineer || Software Engineer ||| Lead Software Engineer System Test Engineer | System Test Engineer || System Test Engineer ||| Lead System Test Engineer Quality Engineer | Quality Engineer || Quality Engineer ||| Lead Quality Engineer
WBS Item Work Item
Create UML Outline
Derive Requirement Artifacts
Provide Design Artifacts
3.1.3
Unit Test Software
Check The Function
Perform Environmental Tests
Run Test On Live Environment
Quality Checks
Work with Customer Facility

ACTIVITY COST

Activity Cost and Activity Duration Schedule MAY JUNE JULY August September October November Task Employee Work Days Labor Rate Labor Cost OH (

15

.95%) Total

Employee Work Days Labor Rate

labor Cost OH(15.55%)

Total Employee Work Days Labor Rate Labor Cost OH(15.55%) Total Employee Work Days Labor Rate Labor Cost OH(15.55%) Total Employee Work Days Labor Rate Labor Cost OH(15.55%) Total Employee Work Days Labor Rate Labor Cost OH(15.55%) Total Employee Work Days Labor Rate Labor Cost OH(15.55%) Total

2.1 UML Design For Interface

2.1.1 Create Outline of UML

CE

5

75.41 3016.4 481.1158 3497.5158 LSE 10 56.91 4552.8 726.1716 5278.9716 SE3

10

51.17 4093.6 652.9292 4746.5292 SW3

5

51.01 20

40.4 3

25

.4438 2365.8438 QE3

5

52.01 2080.4 331.8238 2412.2238 2.1.2 Derived Requirements Artifacts

SE2

15

47.37 5684.4 906.6618 6591.0618 SE1

15

41.15 4938 787.611 5725.611 SW2

10

47.62 3809.6 607.6312 4417.2312 QE2

10 52.01

4160.8 663.6476 4824.4476 2.2

System/Software Design 2.2.1 Design Software Components SE2 10 47.37

3789.6 604.4412 4394.0412

SE1 15 41.15 4938 787.611 5725.611

SW1

15

42.38 5085.6 811.1532 5896.7532 QE1

5

40.38 1615.2 257.6244 1872.8244 2.2.2 Peer review LSE 10 56.91 4552.8

707.9604 5260.7604 SE2 15 47.37 5684.4

883.9242 6568.3242 SE1 15 41.15 4938

767.859 5705.859 SW1 15 42.38 5085.6

790.8108 5876.4108 QE1 10 40.38

3230.4 502.3272 3732.7272 2.3

Approve Design 2.3.1 Derive Component Level Requirements LSE 5 56.91

2276.4 353.9802 2630.3802 SE3 15 51.17

6140.4 954.8322 7095.2322 SE2 20 47.37

7579.2 1178.5656 8757.7656 SW3 20 51.01

8161.6 1269.1288 9430.7288 QE3 15 52.01

6241.2 970.5066 7211.7066 2.3.2 Unit Test SE1 10 41.15

3292 511.906 3803.906

SW1 15 42.38 5085.6 790.8108 5876.4108
QE1 10 40.38 3230.4 502.3272 3732.7272

2.3.3 System and Enterprise Test SE2 10 47.37 3789.6

589.2828 4378.8828 SW2 15 47.62

5714.4 888.5892 6602.9892 QE2 10

47.55 3804 591.522 4395.522 2.3.4 Derive sell-off Acceptance Criteria

LSTE

10

55.25 4420 687.31 5107.31 STE3

20

49.25 7880 1225.34 9105.34 QE3 15 52.01 6241.2 970.5066 7211.7066
2.3.5 Peer Review SE3 15 51.17 6140.4 954.8322 7095.2322
SE2 15 47.37 5684.4 883.9242 6568.3242
SW3 10 51.01

4080.8 634.5644 4715.3644 SW2 10 47.62 3809.6

592.3928 4401.9928 STE3 15 49.25

5910 919.005 6829.005

QE3 15 52.01 6241.2 970.5066 7211.7066

3.1 Approve Content S/W Component Design
3.1.1 Provide Design Artifacts

LSW

10

58.83 4706.4 731.8452 5438.2452 SW3 20 51.01 8161.6 1269.1288 9430.7288
SE3 10 51.17 4093.6

636.5548 4730.1548 QE2 10 47.55 3804 591.522 4395.522
3.1.2 Derive sell-off Acceptance Criteria

STE2

20

43.62 6979.2 1085.2656 8064.4656 STE1

20

41.78 6684.8 1039.4864 7724.2864 QE1 15 40.38

4845.6 753.4908 5599.0908 3.1.3 Peer Review SW3 20 51.01 8161.6 1269.1288 9430.7288
SE3 20 51.17

8187.2 1273.1096 9460.3096 STE2 15 43.62

5234.4 813.9492 6048.3492 STE1 10 41.78

3342.4 519.7432 3862.1432 QE1 10 40.38 3230.4 502.3272 3732.7272

3.2 Code and Unit Test

3.2.1 Code Test Software LSW 15

58.38 7005.6 1089.3708 8094.9708 SW3 25 51.01

10202 1586.411 11788.411 SW2 25 47.62

9524 1480.982 11004.982 SW1 25 42.38

8476 1318.018 9794.018 SE3 20 51.17 8187.2 1273.1096 9460.3096
QE3 15 52.01 6241.2 970.5066 7211.7066
3.2.2 Unit Test Software SW1 25 42.38 8476 1318.018 9794.018
SE1 25 41.15

8230 1279.765 9509.765 SE2 25 47.37

9474 1473.207 10947.207 QE1 20 40.38

6460.8 1004.6544 7465.4544

3.3 Function Test

3.3.1 Check the Function SW3 20 51.01 8161.6 1269.1288 9430.7288
SW1 20 42.38

6780.8 1054.4144 7835.2144 SE3 15 51.17 6140.4 954.8322 7095.2322

QE3 15 52.01 6241.2 970.5066 7211.7066
4.1 Design Test Artifacts

4.1.1 Derive System Level Test Cases LSTE 10 55.25 4420 687.31 5107.31
STE3 15 49.25 5910 919.005 6829.005
SE3 10 51.17 4093.6 636.5548 4730.1548
SE2 15 47.37 5684.4 883.9242 6568.3242
SW3 10 51.01 4080.8 634.5644 4715.3644
SW1 15 42.38 5085.6 790.8108 5876.4108
QE2 10 47.55 3804 591.522 4395.522
4.1.2 Derive Enterprise Level Test Cases STE3 15 49.25 5910 919.005 6829.005
STE1 20 41.78 6684.8 1039.4864 7724.2864
SE2 15 47.37 5684.4 883.9242 6568.3242
SE1 20 41.15

6584 1023.812 7607.812 SW2 15 47.62 5714.4 888.5892 6602.9892
SW1 20 42.38 6780.8 1054.4144 7835.2144
QE2 10 47.55 3804 591.522 4395.522
QE1 10 40.38 3230.4 502.3272 3732.7272
4.1.3 Peer Review LSTE 10 55.25 4420 687.31 5107.31
STE3 15 49.25 5910 919.005 6829.005
STE2 15 43.62 5234.4 813.9492 6048.3492
STE1 15 41.78

5013.6 779.6148 5793.2148 SE1 10 41.15 3292 511.906 3803.906
SW1 10 42.38

3390.4 527.2072 3917.6072 4.2 Perform Environment Level Tests
4.2.1 Execute Test Cases SE3 20 51.17 8187.2 1273.1096 9460.3096
SE2 20 47.37 7579.2 1178.5656 8757.7656

SW2 15 47.62 5714.4 888.5892 6602.9892

SW1 15 42.38 5085.6 790.8108 5876.4108
LSTE 10 55.25 4420 687.31 5107.31
STE3 20 49.25 7880 1225.34 9105.34
STE2 20 43.62 6979.2 1085.2656 8064.4656
QE3 15 52.01 6241.2 970.5066 7211.7066

4.3 Approve Test Services

4.3.1 Quality Checks STE3 20 49.25 7880 1225.34 9105.34
STE2 20 43.62 6979.2 1085.2656 8064.4656
STE1 15 41.78 5013.6 779.6148 5793.2148
QE3 10 52.01 4160.8

647.0044 4807.8044 QE2 15 47.55

5706 887.283 6593.283 QE1 10 40.38 3230.4 502.3272 3732.7272
4.3.2 Design Review QE3 20 52.01

8321.6 1294.0088 9615.6088 QE2 20 47.55

7608 1183.044 8791.044 STE3 15 49.25 5910 919.005 6829.005
STE2 15 43.62 5234.4 813.9492 6048.3492
4.3.3 Pre-Ship Review QE3 15 52.01 6241.2 970.5066 7211.7066

QE2 15 47.55 5706 887.283 6593.283

QE1 15 40.38 4845.6 753.4908 5599.0908
4.4 Run Test on Live Environment
4.4.1 Quality Checks QE3 10 52.01 4160.8 647.0044 4807.8044
QE2 10 47.55 3804 591.522 4395.522

QE1 15 40.38 4845.6 753.4908 5599.0908

STE3 10 49.25

3940 612.67 4552.67 STE2 10 43.62

3489.6 542.6328 4032.2328 4.4.2 Final Acceptance Test

LQE

10

59.83 4786.4 744.2852 5530.6852 QE3 15 52.01 6241.2 970.5066 7211.7066
QE2 15 47.55 5706 887.283 6593.283
QE1 10 40.38 3230.4 502.3272 3732.7272
STE3 10 49.25 3940 612.67 4552.67
STE2 10 43.62 3489.6 542.6328 4032.2328
STE1 10 41.78 3342.4 519.7432 3862.1432

4.5 Deploy to Operational Environment

4.5.1 Work with Customer Facility LSTE 5 55.25

2210 343.655 2553.655 STE3 5 49.25

1970 306.335 2276.335 STE2 5 43.62

1744.8 271.3164 2016.1164 STE1 5 41.78

1671.2 259.8716 1931.0716 May Total 57748.6656 June Total 91060.333 July Total 136162.7334 August Total 164865.8156 September Total 142981.57 October Total 112172.2424 Novemeber Total 44292.626

Total

Budget

Cost

749283.986 Task MAY JUNE JULY

AUG

UST SEP

TEMBER OCT

OBER NOV

EMBER 2.1

Create UML Outline and Derive requirement artifacts 39859.4358 2.2 System/Software Design

17889.2298 27144.0816 2.3 Approve Design

63916.2514 58245.9818 3.1 Approve Content S/W Component

77916.7516 3.2

Code/Unit Test 95070.8424 3.3 Function Test

31572.882 4.1 Design Test Artifacts

38222.0912 82795.2726 4.2

Perform Envirnomental Test 60186.2974 4.3 Approve Test Services

88784.9224 4.4 Run Test on Live Environment

23387.33 35515.448 4.5 Deploy to Operational Environment

8777.178 Total Budget Cost

57748.6656 91060.333 136162.7334 164865.8156 142981.57

112172.2524

44292.626

Graph

Month

TBC CBC MAY 57748.6656 57748.6656
JUNE 91060.333

148808.9986 JULY 136162.7334

284971.732 AUG 164865.8156

449837.5476 SEP 142981.57

592819.1176 OCT 112172.2524

704991.37 NOV 44292.626

749283.996

Cummulitive Budget Curve

TBC MAY JUNE JULY AUG SEP OCT NOV 57748.6656 91060.332999999999 136162.7334 164865.8156 142981.57 112172.2524 44292.625999999997 CBC MAY JUNE JULY AUG SEP OCT NOV 57748.6656 148808.99859999999 284971.73199999996 449837.54759999993 592819.1176 704991.37 749283.99600000004

Month

Budget

BUSA 428

Spring 2021

Project Management

Management Response Document

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

BUSA 428 Course Project

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 this sample before you submit your response to management.)

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 this sample before you submit your response to management.)

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.

10

1

BUSA 42

8

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:

– Finance: 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.)

Task\Date 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.

BU

S

A

428

F

a

l

l 2020

P

r

o

j

e

c

t

Ma

n

a

g

e

m

ent

Management Re

s

ponse Doc

u

ment

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

BUSA 428

C

ourse Project

PROJ

E

C

T

Q

UESTIONS & TASKS

 

1. Prov

i

d

e a project objective associated

w

it

h

the Astin Martin Electronics project. Include a list o

f

assumptions about the project.

JBB software will provide all the planned deliverables that meet all the requirements as stated in the Statement of Work to Astin Martin Electronics. JBB software will provide all required deliverables in a qualit

y

manner within the agreed contract budget and schedule.

A list of assumptions about the project is:

· System Engineer will provide appropriate requirements decomposition.

· Software Engineer will design, develop and perform the unit test of software.

· System Test engineer will provide component and perform enterprise level testing.

· Quality Engineer will provide quality checks through the entire project performance.

· Work break down structure is provided to show the work of all Engineers.

· All of the employee is ready to handle for any upcoming risks.

· Peer review to know the opinion from Seniors.

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.

A work breakdown structure is hierarchical graph that describes the project and divides the work into smaller group to achieve the project goals.

Responsibility assignment matrix is used to describe the works that need to be completed and the team members of the project. In the other word, RAM chart shows the roles and responsibilities of all the employees.

(Major)

L

ist all activity costs. From the project activity list and activity duration schedule, estimate the cost of each activity. Then, determine the Total

Budget

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

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

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

JBB Software is planning to use contingency reserve in this project. The term reserve means the budget or fund that we are planning to use on this project. Risk might occur in future. It might be identified or unidentified. The reason we are planning to use contingency reserve in this project is we can use for both know and unknown risk. It is an estimation reserve based on a number of risk assessment strategies. Contingency reserve is estimated by the project manager and handle them as they occur.

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

Cost management is important to everyone participating in this project. It shows how the project budget is prepared and handled. It helps to control and minimize the project’s

Chances of running beyond the budget. In this project, we have created the activity cost schedule which shows the task and labor cost for each month. We have also created the total budget cost schedule.

We are also calculating the earned value in this project. Earned value is a method of calculating and tracking the amount of project work performed against the schedule. It shows whether the work is behind the schedule or over the project budget. It is calculated by multiplying the percentage of work completed by the project total budget. It is necessary to calculate the earned value of work performed because project manager can see the work performance of employees and the cost. Also, it provide project manager to ensures consistent coordination of the tasks involved which increases the efficiency and control of the project.

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

JBB software is well prepared and trained to deal with any potential risk that could arise in the project. In order to manage the risk on this project, we will employ risk assessment matrix. Risk assessment matrix is calculated to minimize the possibility of major risk to maximize project efficiency. It helps to identify the risk in the initial phase. When we identify the risk, we will evaluate them as soon as possible. We will give priority to the level of risk and build techniques to reduce its effects.

Astin Martin LLC

2.1.1 Create Outline of UML

2.1.2 Derived Requirements Artifacts

2.2 System/Software Design

2.2.1 Design Software Components

2.2.2 Peer Review

2.3 Approve Design

2.3.1 Derive Component Level Requirements

2.3.2 Unit test

2.3.3 System and Enterprise Test

2.3.4 Derive sell-off Acceptance Criteria

2.4.5 Peer review

3.1 Approve Content S/W Component Design

3.1.1 Provide Design Crafts

3.1.2 Derive sell-off Acceptance Criteria

3.1.2 Peer Review

3.2 Code and Unit Test

3.2.1 Code Test Software

3.2.2 Unit Test Software

3.3 Function Test

3.3.1 Check the Function

4.1 Design Test Artifacts

4.1.1 Derive System Level Test Cases

4.1.2 Derive Enterprise Level Test Cases

4.1.3 Peer Review

4.2 Perform Environment Level Tests

4.2.1 Execute Test Cases

4.3 Approve Test Services

4.3.1 Quality Check

4.3.2 Design Review

4.3.3 Pre-Ship Review

4.4 Run Test on Live Environment

4.4.1 Quality Check

4.4.2 Final Acceptance Test

4.5 Deploy to Operational Environment

4.5.1 Work with Customer facility

2.1UML Design For Interface

Cummulitive Budget Curve

TBC MAY JUNE JULY AUG SEP OCT NOV 57748.6656 9

10

60.332999999999 136162.7334 164865.8156 142981.57 112172.2524 44292.625999999997 CBC MAY JUNE JULY AUG SEP OCT NOV 57748.6656 148808.99859999999 284971.73199999996 449837.54759999993 592819.1176 704991.37 749283.99600000004

Month

Budget

10

2.1 UML Design For Interface
2.1.1 Create UML Outline P S P S S S
2.1.2 Derive Requirement Artifacts P P S S
2.2 System/Software Design

2.2.1 Design Software Components S P S S S
2.2.2 Peer Review S P P S S
2.3 Approve Design

2.3.1 Derive Component Level Requirements S P P S S
2.3.2 Unit Test P S S
2.3.3 System and Enterprise Test P S S
2.3.4 Derive sell-off Acceptance Criteria P P S
2.3.5 Peer Review S P S P P P
3.1 Approve Content S/W Component

3.1.1 Provide Design Artifacts S S P S
3.1.2 Derive sell-off Acceptance Criteria S P S
3.1.3 Peer Review S P S P S
3.2 Code and Unit Test

3.2.1 Code Test Software S S S P P S
3.2.2 Unit Test Software S P P S
3.3 Function Test

3.3.1 Check The Function S S P S
4.1 Design Test Artifacts

4.1.1 Derive System Level Test Cases S P S P P P S
4.1.2 Derive Enterprise Level Test Cases S S S P S P S S
4.1.3 Peer Review S S S S P P
4.2 Perform Environmental Tests

4.2.1 Execute Test Cases S P S P S P P S
4.3 Approve Test Services

4.3.1 Quality Check S S P S P P
4.3.2 Design Review S P S P
4.3.3 Pre-Ship Review S P P
4.4 Run Test On Live Environment

4.4.1 Quality Checks S P S S P
4.4.2 Final Acceptance Test S S P S S P P
4.5 Deploy to Operational Environment

4.5.1 Work with Customer Facility S S P P

Q
u

al
it

y
En

gi
n

ee

r

|

|

Q
u

al
it

y
En

gi
n

ee
r

||

|

Le
ad

Q
u

al
it

y
En

gi
n

ee
r

So
ft

w
ar

e
En

gi
n

ee
r

|

So
ft

w
ar

e
En

gi
n

ee
r

||

So
ft

w
ar

e
En

gi
n

ee
r

||
|

Le
ad

S
o

ft
w

ar
e

E

n
gi

n
ee

r

Sy
st

em
T

es
t

En
gi

n
ee

r
|

Sy
st

em
T

es
t

En
gi

n
ee

r
||

WBS Item Work Item Sy
st

em
T

es
t

En
gi

n
ee

r
||

|

Le
ad

S
ys

te
m

T
es

t
En

gi
n

ee
r

Q
u

al
it

y
En

gi
n

ee
r

|

Pr
o

je
ct

m
an

ag
er

Ch
ie

f

E
n

gi
n

ee
r

Sy
st

em
E

n
gi

n
ee

r
|

Sy
st

em
E

n
gi

n
ee

r
||

Sy
st

em
E

n
gi

n
ee

r
||

|

Le
ad

S
ys

te
m

E
n

gi
n

ee
r

2.1UML Design For Interface

2.1.1Create UML Outline P SPS S S

2.1.2Derive Requirement Artifacts PP S S

2.2System/Software Design

2.2.1Design Software Components SPS S S

2.2.2Peer Review SP PS S

2.3Approve Design

2.3.1Derive Component Level Requirements SPP S S

2.3.2Unit Test P S S

2.3.3System and Enterprise Test P S S

2.3.4Derive sell-off Acceptance Criteria PP S

2.3.5Peer Review SP SP P P

3.1Approve Content S/W Component

3.1.1Provide Design Artifacts S SP S

3.1.2Derive sell-off Acceptance Criteria SP S

3.1.3Peer Review S P SP S

3.2Code and Unit Test

3.2.1Code Test Software S SSPP S

3.2.2 Unit Test Software SP P S

3.3Function Test

3.3.1Check The Function S S P S

4.1Design Test Artifacts

4.1.1Derive System Level Test Cases SP S P PP S

4.1.2Derive Enterprise Level Test Cases SS SP S P SS

4.1.3Peer Review S S SSPP

4.2Perform Environmental Tests

4.2.1Execute Test Cases SP SP SPP S

4.3Approve Test Services

4.3.1Quality Check SSP SPP

4.3.2Design Review SP SP

4.3.3Pre-Ship Review SPP

4.4Run Test On Live Environment

4.4.1Quality Checks SP SSP

4.4.2Final Acceptance Test SSP SSPP

4.5Deploy to Operational Environment

4.5.1Work with Customer Facility SSPP

Q
u
a
l
i
t
y

E
n
g
i
n
e
e
r

|
|
Q
u
a
l
i
t
y

E
n
g
i
n
e
e
r

|
|
|
L
e
a
d

Q
u
a
l
i
t
y

E
n
g
i
n
e
e
r

S
o
f
t
w
a
r
e

E
n
g
i
n
e
e
r

|
S
o
f
t
w
a
r
e

E
n
g
i
n
e
e
r

|
|
S
o
f
t
w
a
r
e

E
n
g
i
n
e
e
r

|
|
|
L
e
a
d

S
o
f
t
w
a
r
e

E
n
g
i
n
e
e
r

S
y
s
t
e
m

T
e
s
t

E
n
g
i
n
e
e
r

|
S
y
s
t
e
m

T
e
s
t

E
n
g
i
n
e
e
r

|
|

WBS ItemWork Item S

y
s
t
e
m

T
e
s
t

E
n
g
i
n
e
e
r

|
|
|
L
e
a
d

S
y
s
t
e
m

T
e
s
t

E
n
g
i
n
e
e
r
Q
u
a
l
i
t
y

E
n
g
i
n
e
e
r

|
P
r
o
j
e
c
t

m
a
n
a
g
e
r
C
h
i
e
f

E
n
g
i
n
e
e
r
S
y
s
t
e
m

E
n
g
i
n
e
e
r

|
S
y
s
t
e
m

E
n
g
i
n
e
e
r

|
|
S
y
s
t
e
m

E
n
g
i
n
e
e
r

|
|
|
L
e
a
d

S
y
s
t
e
m

E
n
g
i
n
e
e
r

MAY JUNE JULY AUGUST SEPTEMBER OCTOBER NOVEMBER
2.1 Create UML Outline and Derive requirement artifacts 39859.4358
2.2 System/Software Design 17889.2298 27144.0816
2.3 Approve Design 63916.2514 58245.9818
3.1 Approve Content S/W Component 77916.7516
3.2 Code/Unit Test 95070.8424
3.3 Function Test 31572.882
4.1 Design Test Artifacts 38222.0912 82795.2726
4.2 Perform Envirnomental Test 60186.2974
4.3 Approve Test Services 88784.9224
4.4 Run Test on Live Environment 23387.33 35515.448
4.5 Deploy to Operational Environment 8777.178

Total Budget Cost 57748.6656 91060.333 136162.733 164865.816 142981.57 112172.252 44292.626

Task

MAYJUNEJULYAUGUSTSEPTEMBEROCTOBERNOVEMBER

2.1Create UML Outline and Derive requirement artifacts39859.4358

2.2System/Software Design 17889.229827144.0816

2.3Approve Design 63916.251458245.9818

3.1Approve Content S/W Component 77916.7516

3.2Code/Unit Test 95070.8424

3.3Function Test 31572.882

4.1Design Test Artifacts 38222.091282795.2726

4.2Perform Envirnomental Test 60186.2974

4.3Approve Test Services 88784.9224

4.4Run Test on Live Environment 23387.3335515.448

4.5Deploy to Operational Environment 8777.178

Total Budget Cost 57748.665691060.333136162.733164865.816142981.57112172.25244292.626

Task

Calculate your order
Pages (275 words)
Standard price: $0.00
Client Reviews
4.9
Sitejabber
4.6
Trustpilot
4.8
Our Guarantees
100% Confidentiality
Information about customers is confidential and never disclosed to third parties.
Original Writing
We complete all papers from scratch. You can get a plagiarism report.
Timely Delivery
No missed deadlines – 97% of assignments are completed in time.
Money Back
If you're confident that a writer didn't follow your order details, ask for a refund.

Calculate the price of your order

You will get a personal manager and a discount.
We'll send you the first draft for approval by at
Total price:
$0.00
Power up Your Academic Success with the
Team of Professionals. We’ve Got Your Back.
Power up Your Study Success with Experts We’ve Got Your Back.

Order your essay today and save 30% with the discount code ESSAYHELP