《wbs313systemarchitectureworkscopeplanningsheet》由会员分享，可在线阅读，更多相关《wbs313systemarchitectureworkscopeplanningsheet（6页珍藏版）》请在金锄头文库上搜索。
1、Keck Next Generation Adaptive OpticsUpdated 6/27/2018 at 9:32 下午 by Author-1-NGAO System Design Phase: Work Scope Planning Sheet v2.0WBS Element Title:NGAO System Architecture Definition WBS Element Number:3.1.3 Work Package Lead:Richard Dekany Work Package Participants:Bauman, Gavel, Flicker, Neyma
2、n, Velur, WizinowichWork ScopeWBS Dictionary Entry: Produce Baseline NGAO System Architecture and Program Scope in consideration of input from the system/science requirements, performance budgets and trade studies, and iterate with these efforts. Provide top-level guidance on architectural choices t
3、hat meet the requirements, in order to allow the designs of the major systems (AO system, LGS facility, science operations and science instruments) to proceed. Document the system architecture considerations, trade-offs and decisionsin support of the system design manual.Inputs:System Requirements D
4、ocument Rev 2.0 Detailed NGAO Observing Scenario Use Cases The set of WBS 3.1.1 Performance Budget Tools and Reports Numerous WBS 3.1.2 Trade Study Reports Draft Operational Requirements Functional Requirements Science Instrument Priorities (updated from 6/06 proposal ranking) On-going Science Team
5、Feedback (via in particular Claire)Products:Documentation of the architecture selection process and selection criteria System Design Manual v1.0 Functional Requirements Document v1.0 for the AO and laser systems Initial subsystem cost estimates Technical risk analysis v1.0Methodology:This work packa
6、ge will be executed by a small team (6 persons) working on a regular Monday afternoon meeting cadence (2-3 hour Wednesday meeting followed by 10 hrs of additional work per person per week.)All meetings will be by video, with as frequent collection of team members in one location as possible (suggest
7、 Wednesday face-to-face meetings for Bauman, Dekany, Gavel, Velur when possible)Work Plan:May 24, 2007Review WBS 3.1.3 PlanReview Constraints from SRD KI support Science instrument priorities (updated from 6/06 proposal ranking)Review potential top-down architectures Keck 1 upgrades Large FoV Relay,
8、 instruments, d-IFU Small FoV Relay(s), instrument d-IFU AM2 / no AM2Title DateUpdated 6/27/2018 at 9:32 下午 by Author 2May 30, 2007Develop subsystem selection process and selection criteria Examples: Cost, cost risk, schedule risk, reliability, maintainability, vendor options, and system expandabili
9、tyDiscuss and adopt relevant list of system functions (see Table 1 for an example starting point) The definition of system functions should follow the System Requirements Document and the collection of NGAO Observing Scenario Use Cases. Assign functions to team members, who will suggest, develop, an
10、d later rank candidate subsystems (resources include KAON library, literature, experience)Schedule flow-down interviews with subsystem assigneesTuesday, June 5, 2007 (Velur traveling)First batch candidate subsystems described by assignees Includes initial evaluation against selection criteria Identi
11、fy constraints and conditions on subsystem candidates that justify this ranking Example: Subsystem A is only preferred under conditions B, C, and D. (Could be other subsystem choices or certain risk mitigation successes.)Assign development of subsystem cost estimate basis template (for later ease of
12、 estimation)June 13, 2007 (Velur and Dekany traveling)Second batch candidate subsystems described by assignees Includes initial evaluation against selection criteria Includes cost estimate basisJune 20, 2007 No Meeting (OSA conflict)June 27, 2007Review and adopt subsystem candidate rankings Address
13、questions raised during initial evaluationsDefine architecture evaluation criteria Examples: Cost, cost risk, schedule risk, performance, reliability, maintainability, vendor options, and system expandabilityTitle DateUpdated 6/27/2018 at 9:32 下午 by Author 3July 9-13, 2007 Architecture RetreatPropos
14、e candidate architectures as combinations of subsystems having top ranking determined above. Include original top-down architectures Brainstorm on new subsystem combinationsDevelop architecture system-level cost estimation (parametric)Assign and begin drafting initial Subsystems Functional Requireme
15、nts DocumentsJuly 25, 2007Discuss and generate initial rank order candidate architectures in terms of architecture selection criteria.Identify and assign key outstanding architecture issues to addressAug 1, 2007Review resolution of key issues, collect into Risk RegisterSolicit external input as appr
16、opriate (e.g. latest guidance from Advancement Office)Aug 8, 2007Review external considerationsCollect architecture elements into prioritized, initial cost estimated program; input into SDM v1.0Formally adopt baseline architecture and program scopeAssign SDM v1.0 writing assignmentsAug 15, 2007Initial draft sections of SDM v1.0 due to SDM EditorAug 22, 2007Final SDM section input, editorial reviewAug 29, 2007Initial release of SDM v1.0 (WBS 3.6.1) Initial
