Operational Concept Description (OCD)Version HistoryTable of ContentsTable of TablesTable of FiguresIntroductionPurpose of the OCDStatus of the OCDShared VisionSuccess-Critical StakeholdersSystem Capability DescriptionExpected BenefitsBenefits ChainSystem Boundary and EnvironmentSystem TransformationInformation on Current SystemInfrastructureArtifactsCurrent Business WorkflowSystem Objectives, Constraints and PrioritiesCapability GoalsLevel of Service GoalsOrganizational GoalsConstraintsRelation to Current SystemProposed New Operational ConceptElement Relationship DiagramBusiness WorkflowsOrganizational and Operational ImplicationsOrganizational TransformationsOperational TransformationsOperational Concept Description (OCD)Mission Science Information and Data Management SystemTeam 06Team member RolesCelia Kung Project Manager Planning and Control EngineerHardik Shah Feasibility Analyst Requirements EngineerBrian Anderson Operational Concept Engineer Project ManagerYujie Chen Prototyper System ArchitectZhenlu Sun Requirements Engineer Operational Concept EngineerKathleen Barrera Quality Focal Point System Requirement EngineerWei Tan System Architect PrototyperOperational Concept Description (OCD) for NDI/ NCS Version 1.310/24/2011Version Date: 10/24/11 iiOperational Concept Description (OCD) for NDI/ NCS Version 1.3Version HistoryDate Author Version Changes made Rationale09/23/11 Zhenlu Sun&Yujie Chen1.0- Initial version of OCD - Using with Operational Concept Description (OCD) for NDI/ NCS template Version 1.010/10/11 Brian Anderson1.1- Updated the team roles table on coverpage- The Benefits Chain Analysis- Expanded the OCD status section (section 1.2)- Updated section 2.3 Expected Benefits - The Benefits Chain Analysis has changed after our winwin negotiations meeting.- The benefits were more accurately defined after the winwin meetings and the resulted in the need to updatethe corresponding sections.10/14/11 Brian Anderson1.2- Updated section 2.5 System and Boundary- Updated section 3.2.1 Capability Goals- Updated section 3.3.1 Element Relationship Diagram- Updated the Benefits Chain Analysis- Diagram was wrong (Student Workers were on the wrong side)- OC-3 needed clarification- Diagram was missing- Benefits Chain Analysis was misrepresenting the system10/22/11 Brian Anderson1.3- Updated section 3.3.1 Element Relationship Diagram- Updated the Benefits Chain Analysis- Diagram was not accurate- Benefits Chain Analysis was misrepresenting the systemVersion Date: 10/24/11 iiiOperational Concept Description (OCD) for NDI/ NCS Version 1.3Table of ContentsOperational Concept Description (OCD) iVersion History iiTable of Contents iiiTable of Tables ivTable of Figures v1. Introduction 11.1 Purpose of the OCD 11.2 Status of the OCD 12. Shared Vision 22.1 Success-Critical Stakeholders 22.2 System Capability Description 22.3 Expected Benefits 32.4 Benefits Chain 42.5 System Boundary and Environment 53. System Transformation 63.1 Information on Current System 63.2 System Objectives, Constraints and Priorities 83.3 Proposed New Operational Concept 103.4 Organizational and Operational Implications 12Version Date: 10/24/11 ivOperational Concept Description (OCD) for NDI/ NCS Version 1.3Table of TablesTable 1: Success-Critical Stakeholders..........................................................................................................................2Table 2: Capability Goals...............................................................................................................................................8Table 3: Relation to Current System...............................................................................................................................9v Version Date: 10/24/11Operational Concept Description (OCD) for NDI/ NCS Version no 1.3Table of FiguresFigure 1 Benefit Chain...................................................................................................................................................4Figure 2: System Boundary and Environment Diagram................................................................................................5Figure 3: Current Business Workflow for Inventory Control.........................................................................................7Figure 4: Business Workflow Diagram for student participation in program...............................................................8Figure 5: Entity Relationship Diagram........................................................................................................................11Figure 6: Business Workflow........................................................................................................................................11Figure 7: Business Workflow Diagram of Information and Database System.............................................................12Version Date: 10/24/11 viOperational Concept Description (OCD) for NDI/ NCS Version 1.3IntroductionPurpose of the OCD To describe the success-critical stakeholders' shared vision of the project being undertaken. The requirements are still being gathered and the design of the proposed system is being developed. This document provides, in detail, the shared visions and goals of the stakeholders of the Information and Database Management System for the Mission Science. The success-critical stakeholders of the project are Darin Gray, as the project owner; the Mission Science student workers and Darin Gray, as users; Darin Gray, as the maintainer.Status of the OCD The status of the OCD has been reviewed by all team members and class staff. This document has been changed to include the agreed upon benefits following the two winwin negotiation meetings. The updates in the benefits were the basis for a new benefits chain analysis to be accomplished. Brian Anderson has been assigned as the primary Operational Concept Engineer.Version Date: 10/24/111Operational Concept Description (OCD) for NDI/ NCS Version 1.3Shared VisionThe system needs to be a more robust integrated database that stores and tracks Students demographics, Inventory and Costs, Lesson plans, and Applicable Standards .Success-Critical StakeholdersTable 1: Success-Critical StakeholdersStakeholder AuthorizedRepresentativesOrganization Relation to Benefits ChainClientDarin Gray Mission Science - Provide information and feedback to the development team. - Use the system.- Provide training to the future user.
View Full Document
Unlocking...