Unmanned Control & Tracking System (UCATS) Project ...



Unmanned Control & Tracking System (UCATS) Project Management PlanIntroductionThis plan describes the organization, tasking, schedule and processes used to develop the anization and ResponsibilitiesThe Naval Surface Warfare Center Dahlgren Division (NSWCDD) SYST-798 Team DJ3K team will use the organization shown in Figure 1 to develop the system architecture for the UCATS. The NSWCDD SYST-798 Team DJ3K team consists of the following members:Kurt Chewning Jennifer Greene Dave ManleyJeanette SmithJohn SmithProgram ManagerDave ManleySystems EngineerJennifer GreeneFunctional Architect LeadJeanette SmithSystems Problem LeadJohn SmithInstantiated Architect LeadKurt ChewningFigure 1: NSWCDD Team DJ3K OrganizationUCATS TaskingTable 1 summarizes the UCATS tasking, due date, the Team DJ3K member (Point of Contact (POC)) responsible for coordinating the development of the deliverable, and whether this is a formal project deliverable of a systems engineering product used to develop the system. This POC is not necessarily responsible for generating the entire deliverable, but instead will collect and consolidate all the deliverables from the team.WBSDatesPOCs#NameStartFinishChewning, Kurt Greene, Jennifer Manley, DaveSmith, Jeanette Smith, John1.Project Management31-Aug18-Dec???Lead?1.1Organize Team31-Aug31-AugAllAllAllAllAll1.2Select Concept1-Sep4-SepAllAllAllAllAll1.3Generate Project Proposal5-Sep14-Sep???Lead?1.3.1Project Proposal Presentation4-Sep13-SepSME????1.3.2Project Proposal Summary4-Sep13-Sep????SME1.3.3Proposal Scoped and Approved14-Sep14-SepAllAllAllAllAll1.4Project Management Plan5-Sep12-Sep??SME??1.5Networked Schedule13-Sep20-Sep??SME??1.6System Business Concept15-Sep23-Sep??SME??1.7Stakeholder Value Mapping15-Sep23-SepSME1.8SOW15-Sep23-Sep???SME?1.9Reporting17-Oct18-Dec???Lead?1.9.1Final Presentation17-Oct18-DecSME????1.9.1.1Rough Draft Presentation17-Oct13-NovSME????1.9.1.2Final Draft Presentation14-Nov18-DecSME????1.9.2Final Report17-Oct18-Dec?SME???1.9.2.1Rough Draft Report17-Oct13-Nov?SME???1.9.2.2Final Draft Report14-Nov18-Dec?SME???2.0Systems Engineering Management15-Sep18-Dec?Lead???2.1Systems Engineering Tools Selection15-Sep15-SepAllAllAllAllAll2.2CM15-Sep18-Dec?SME???2.3Systems Engineering Management Plan (SEMP)15-Sep5-Oct?SME???2.4Risk Management Plan (RMP)15-Sep5-Oct?SME???2.5Product Assurance Plan (PAP)15-Sep5-Oct?SME???3.0System Design15-Sep16-OctAllAllAllAllAll3.1Define System Level Problem15-Sep26-Sep????Lead3.1.1Develop Concept of Operations15-Sep16-Sep?SME???3.1.2Develop Use Cases15-Sep23-Sep??SME??3.1.3Develop External Systems Activity Diagram15-Sep23-Sep??SME??3.1.4Develop External Systems Diagram15-Sep16-Sep????SME3.1.5Develop Systems Objectives Hierarchy15-Sep16-Sep??SME??3.1.6Develop Analyze and Refine Requirements17-Sep25-Sep???SMESME3.1.7Obtain Approval for Requirements25-Sep25-SepAllAllAllAllAll3.1.8Document Final Requirements26-Sep26-Sep????SME3.2Develop System Functional Architecture27-Sep3-Oct??Lead??3.2.1Create Simple Functional Concept27-Sep27-Sep??SME??3.2.2Draft and Evaluate Functional Model28-Sep30-Sep??SME??3.2.2.1Conduct Functional decomposition Brainstorming28-Sep28-SepAllAllAllAllAll3.2.2.2Conduct Functional Decomposition Trade Study29-Sep29-Sep??SME??3.2.2.3Select Functional Decomposition30-Sep30-SepAllAllAllAllAll3.2.3Complete Functional and Data Models1-Oct1-Oct?SME???3.2.3.1Generate Initial Functional Models1-Oct1-Oct?SME???3.2.3.2Generate System Activity Diagrams1-Oct1-Oct??SME??3.2.3.3Identify / Draft Sub-System Interface Requirements1-Oct1-Oct?SMESME??3.2.4Trace Input / Output Requirements2-Oct2-Oct?SME???3.2.4.1Complete Draft IDEF A0 & A1 Diagrams2-Oct2-Oct?SME???3.2.4.2Complete Draft IDEF A2 Diagrams2-Oct2-Oct??SMESMESME3.2.5Obtain Approval for Functional Architecture3-Oct3-OctAllAllAllAllAll3.2.6Document Final Functional Architecture3-Oct3-Oct?SMESMESMESME3.3Develop System Instantiated Architecture4-Oct16-OctLead????3.3.1Develop Generic Architecture4-Oct6-OctAllAllAllAllAll3.3.1.1Brainstorm Architecture4-Oct4-OctAllAllAllAllAll3.3.1.2Generate Trade-Offs5-Oct5-OctSMESMESMESMESME3.3.1.3Down-Select Generic Architecture6-Oct6-OctAllAllAllAllAll3.3.2Develop Instantiated Architecture7-Oct15-OctAllAllAllAllAll3.3.2.1Brainstorm Instantiated Architecture Components7-Oct7-OctAllAllAllAllAll3.3.2.2Generate Morphological Box - Instantiated Sys Arch Sub-Sys8-Oct9-OctSMESMESMESMESME3.3.2.3Conduct Sub-System Trade-Off Analysis10-Oct12-OctSMESMESMESMESME3.3.2.4Down Select Instantiated Architecture13-Oct13-OctAllAllAllAllAll3.3.2.5Finalize Sub-System Interface Requirements14-Oct14-OctSMESMESMESMESME3.3.2.6Document Instantiated Draft Design15-Oct15-OctSMESMESMESMESME3.3.3Obtain Approval for Instantiated Architecture15-Oct15-OctAllAllAllAllAll3.3.4Final Instantiated Design16-Oct16-OctAllAllAllAllAll4.0Refine / Update Design17-Oct15-DecAllAllAllAllAll4.1System Requirements17-Oct15-Dec????Lead4.2Functional Design17-Oct15-Dec??Lead??4.3Instantiated Design17-Oct15-DecLead????Table 1: Task ListProject Management:The project management tasking includes the generation of the project plan, providing progress briefings and reports, and providing the final briefing and report.Systems Engineering ManagementThe systems engineering tasking includes selecting the systems engineering tools NSWCDD Team DJ3K will use on the project and providing Configuration Management (CM) Functions.Systems Design:The systems design tasking includes defining the system level problem, generating a functional architecture, and generating a physical architecture.ScheduleFigure 2 summarizes the draft Collaborative UAV Schedule. NSWCDD Team DJ3K will deliver a networked schedule as a deliverable for this project.ProcessesNSWCDD Team DJ3K will develop the Collaborative UAV System Design by assigning one person to coordinate the development of a specific task or deliverable (See Table 1). This POC will not necessarily be responsible for developing the item, but they will be responsible for coordinating and consolidating all inputs. Team DJ3K will ensure the quality of the deliverable by using a peer review process. After the POC has developed a final draft of the task or deliverable, they will email it to the team for a peer review. The POC will be responsible for setting a peer review due date for inputs and coordinating the update of the deliverable and resolution of all team comments.Figure 2: UCATS Schedule ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download