Software Project Team (YOU): JBB SoftwareCustomer: Astin Martin Electronics LLCRFP awarded for specificmessageservices which will be incorporated into anelectronic instrumentcompany (Astin MartinElectronicsLLC)interface to electronicgauges. Topical level requirements for the software were provided. Deliverable productsinclude:–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 lifecycle–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)ofNovember 15.Astin MartinElectronicsrequest of planned deliverables, acceptance criteria, qualityplan, and work breakdown structure. These items need to be provided in an acceptabletime for Astin Martin to review and approve.Astin MartinElectronicsfurther requests other deliverables to include final software(source and binary) which meets all approved acceptance criteria, associated designdocuments (system and development level)All project questions or request for project scope changes shouldbe directed to theAstin MartinElectronicsdesignee (course instructor).There is no requirement relative to project tools used to generate the required data.Topical requirementsinclude:–System Engineering: UML designartifactsforgraphic widgets to displayaeronautical expanse gaugesfor interface testingwithin the technical specsguidelines for twenty–five different visual aspects. Include appropriate level ofpeer review. Design should include graphical mock–up of gauges.
4–System Engineering: Derivecomponent level requirements for SoftwareEngineering to design, code, and unit test and System Test can provide Systemand Enterprise level testing–Software Engineering: Provide appropriate level design artifacts from SystemEngineering UML design artifacts. Include appropriate level of peer review.–Software Engineering: Code and Unit Test software modules that execute thesoftware which meets all topical and derived requirements–System Test Engineering: Derive sell–off acceptance criteria. Include appropriatepeer 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 modulesbecomeavailable–Quality Engineering: Provide quality checks during the processes described forSystem Engineering, Software Engineering, and System Test Engineering asappropriate–Include the following customer related reviews: Design Review (after SystemEngineering completes design artifacts), Pre–Ship Review (provided prior to AstinMartinElectronicsacceptance of software), and Final Acceptance Test (softwaredemonstration at customer facility showing software meets all requirements asinstalled)Approved labor rates as follows:–System Engineer I: 41.15–System Engineer II: 47.37–System Engineer III: 51.17–Lead System Engineer: 56.91–Software Engineer I: 42.38–Software Engineer II: 47.62–Software Engineer III: 51.01–Lead Software Engineer: 58.83–System Test Engineer I: 41.78–System Test Engineer II: 43.62–System Test Engineer III: 49.25–Lead System Test Engineer: 55.25–Quality Engineer I: 40.38–Quality Engineer II: 47.55–Quality Engineer III: 52.01–Lead Quality Engineer: 59.83–Project Manager: 91.55(LOELevel of Effort)–Chief Engineer: 75.41 (LOELevel of Effort)Approvedoverheadrates as follows:–Finance:6.2% of total hours–Planning & Scheduling:5.5% of total hours
5–Management (Contracts/Senior Management): 2.1% of total hours–Facility: 1.2% of total hours–HR/Staffing: 0.55% of total hoursACTIVITY / TASK LIST BY LOWEST WBS LEVEL LEG2.1Systems Engineering: UML Designfor InterfaceSystem Engineering: Create outline of UMLand derived requirements artifacts.Software Engineering: Assist system engineering.Quality Engineering: Provide quality checks2.2Systems Engineering:System/Software DesignSystem Engineering: Design appropriatesoftware componentsto display aeronauticalexpanse gauges within the technical specs guidelines for twenty–five different visualaspects. Include appropriate level of peer review.Software Engineering: Assist system engineering.Quality Engineering: Provide quality checks.2.3Systems Engineering:Approve designSystem Engineering: Derive component level requirements for Software Engineering todesign, code, and unit test and System Test can provide System and Enterprise leveltesting.Software Engineering: Assist system engineeringSystem Test Engineering: Derive sell–off acceptance criteria. Include appropriate peerreview (including System Engineering) and customer approval.Quality Engineering: Provide quality checks.3.1Software Engineering:ApproveContentS/W Component DesignSystem Engineering: Assist softwareengineeringSoftware Engineering: Provide appropriate level design artifacts from SystemEngineering UML design artifacts. Include appropriate level of peer review.System Test Engineering: Derive sell–off acceptance criteria. Include appropriate peerreview (including System Engineering) and customer approval.
6Quality Engineering: Provide quality checks.3.2Software Engineering: Code and Unit TestSystem Engineering: Assist software engineeringSoftware Engineering: Code and Unit Test softwaremodules that execute the softwarewhich meets all topical and derived requirements.Quality Engineering: Provide quality checks.3.3Software Engineering: Function Test (with actual gauges)System Engineering: Assist software engineeringSoftware Engineering: Check the functionQuality Engineering: Provide quality checks.4.1Test Engineering: Design Test ArtifactsSystem Engineering:Supportwith other engineers for opinionSoftware Engineering:Supportwith other engineers for opinionSystem Test Engineering: Derive System and Enterprise Level Test Cases. Includeappropriate level of peer review.Quality Engineering: Provide quality checks.4.2Test Engineering:PerformEnvironment Level TestsSystem Engineering:Supportwith other engineers for opinionSoftware Engineering:Supportwith other engineers for opinionSystem Test Engineering: Execute test cases as software modules become availableQuality Engineering: Provide quality checks.4.3Test Engineering:ApproveTest Services (with CustomerAcceptanceCriteria)System Test Engineering: Assist Quality EngineeringQuality Engineering: Quality checks during the processes described for SystemEngineering, Software Engineering, and System Test Engineering as appropriate
7Include the following customer related reviews: Design Review (after SystemEngineering completes design artifacts), Pre–Ship Review (provided prior to Astin MartinElectronicsacceptance of software).4.4Test Engineering: Run Test on LiveEnvironment (Customer Facility)System Test Engineering: Assist Quality engineeringQuality Engineering: quality checks, and Final Acceptance Test (software demonstrationat customer facility showing software meets all requirements as installed) installed)4.5System Test Engineering: Deploy to Operational Environment (Customer Facility)System Test Engineering:work with customer facility team for full deploymentUse approved installation instructions to deploy software into operational environmentwith 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 thosetasks could be incorporated in the WBS items noted above.NOTIONALACTIVITY DURATIONSCHEDULENotionalActivity estimated DurationThe estimated total elapsed time for how long an activity will take from startsto finish, including associated waiting time. Also referred to as activityresource estimated orestimated activity resources.Example only:Does not reflect tasks of this assignment.
8PROJECT QUESTIONS & TASKS1.Provide aproject objectiveassociated with theAstin Martin Electronicsproject.Include a list ofassumptionsabout the project.2.What is a work breakdown structure? What is a responsibility matrix?Using the AstinMartinAstin MartinElectronicsprojectactivity list and activity duration schedule,create a WBS and RAM.Work Breakdown Structure(Should providehierarchical graph)???Responsibility Assignment Matrix???(Example
“Order a similar paper and get 30% discount on your first order with us. Use the following coupon“SUPER50”
