| { |
| "paper_id": "X96-1045", |
| "header": { |
| "generated_with": "S2ORC 1.0.0", |
| "date_generated": "2023-01-19T15:05:18.644058Z" |
| }, |
| "title": "TIPSTER Text Phase II Configuration Management Plan", |
| "authors": [], |
| "year": "", |
| "venue": null, |
| "identifiers": {}, |
| "abstract": "This document presents the TIPSTER Text Phase II Configuration Management (CM) Plan for identifying, controlling, and auditing the TIPSTER Architecture status and configuration definition. 1.1 Configuration Management Goals The CM process will support the following TIPSTER goals: use of API's, modular substitution, and conformance to applicable standards. The CM process will document the conformance of each TIPSTER application to the Architecture Design Document and with any applicable APIs. The most important affect of the CM process will be to promote modular substitution, software re-use, and reduced risk of project planning. This will allow for the orderly upgrading of installed systems as technology improves in the future. It will also facilitate the sharing of developed software between Government agencies and offices.", |
| "pdf_parse": { |
| "paper_id": "X96-1045", |
| "_pdf_hash": "", |
| "abstract": [ |
| { |
| "text": "This document presents the TIPSTER Text Phase II Configuration Management (CM) Plan for identifying, controlling, and auditing the TIPSTER Architecture status and configuration definition. 1.1 Configuration Management Goals The CM process will support the following TIPSTER goals: use of API's, modular substitution, and conformance to applicable standards. The CM process will document the conformance of each TIPSTER application to the Architecture Design Document and with any applicable APIs. The most important affect of the CM process will be to promote modular substitution, software re-use, and reduced risk of project planning. This will allow for the orderly upgrading of installed systems as technology improves in the future. It will also facilitate the sharing of developed software between Government agencies and offices.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Abstract", |
| "sec_num": null |
| } |
| ], |
| "body_text": [ |
| { |
| "text": "The CM review process, described in detail below, will result in a document which details the ways in which an application or vendor product conforms to the Architecture Design Document and is in agreement with the TIPSTER Architecture design. This document is a TIPSTER Application Conformance Assessment Document (TACAD).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TIPSTER Application Conformance Assessment Document", |
| "sec_num": "1.2" |
| }, |
| { |
| "text": "In order for an application or vendor product to successfully acquire a TACAD, the following conditions must be met:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TIPSTER Application Conformance Assessment Document", |
| "sec_num": "1.2" |
| }, |
| { |
| "text": "For TIPSTER Application development:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "TIPSTER Application Conformance Assessment Document", |
| "sec_num": "1.2" |
| }, |
| { |
| "text": "The TIPSTER Application development complies with the TIPSTER CM process, the details which are contained in this document. In short, the TIPSTER Application must undergo a Preliminary Design Review (PDR) and a Final Operating Capability (FOC) review. At these reviews, any discrepancy or deviation from the TIPSTER Architecture must be documented and justified/explained.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "\u2022", |
| "sec_num": null |
| }, |
| { |
| "text": "Any new code or capabilities for the TIPSTER Application must be developed in accordance with the TIPSTER Architecture. Failure to do so will be documented and justified in the TACAD.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "\u2022", |
| "sec_num": null |
| }, |
| { |
| "text": "\u2022 To the extent possible and in the Government's best interest, existing code and capability to be incorporated into the TIPSTER Application will be re-engineered in accordance with the TIPSTER Architecture. Failure to do so will be documented and justified in the TACAD.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "\u2022", |
| "sec_num": null |
| }, |
| { |
| "text": "For Vendor Products:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "\u2022", |
| "sec_num": null |
| }, |
| { |
| "text": "\u2022 If the vendor's product is used in a TIPSTER Application, the criteria stated above in \"For TIPSTER Application development\" will apply.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "\u2022", |
| "sec_num": null |
| }, |
| { |
| "text": "\u2022 A vendor's product may be determined to be TIPSTER compliant with the use of a TACAD independent of actually being part of a TIPSTER Application. To support the development of this TACAD, the vendor will demonstrate, by inspection, module-by-module compliance with the TIPSTER Architecture.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "\u2022", |
| "sec_num": null |
| }, |
| { |
| "text": "On the basis of the TACAD, the Configurations Control Board (CCB) will determine that a TIPSTER Application is conformant or non-conformant, if it exhibits sufficient overlap with the Architecture Design Document.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "\u2022", |
| "sec_num": null |
| }, |
| { |
| "text": "The extent of TIPSTER Conformance will be determined on a \"per module\" basis and documented in the TACAD. As a result of the TIPSTER Application reviews (described in section 1.2, below) a summary matrix will be available as shown in Appendix A, Figure A -I, below.", |
| "cite_spans": [], |
| "ref_spans": [ |
| { |
| "start": 246, |
| "end": 254, |
| "text": "Figure A", |
| "ref_id": null |
| } |
| ], |
| "eq_spans": [], |
| "section": "\u2022", |
| "sec_num": null |
| }, |
| { |
| "text": "The TACAD may be used by Vendors to facilitate teaming with other Vendors or insertions of new capability into existing TIPSTER systems.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "\u2022", |
| "sec_num": null |
| }, |
| { |
| "text": "The TIPSTER CM process imposes two control gates, PDR and FOC, on the TIPSTER Application development lifecycle, as shown in Figure 1 -2. In preparation for these control gates, it is expected that the developing contractor and the SE/CM will work together to prepare the documentation and to identify any discrepancies between the Architecture Design and the TIPSTER Application's design. This cooperation will be in the form of an Engineering Review Board (ERB).", |
| "cite_spans": [], |
| "ref_spans": [ |
| { |
| "start": 125, |
| "end": 133, |
| "text": "Figure 1", |
| "ref_id": "FIGREF0" |
| } |
| ], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "At the PDR control gate, the following TIPSTER Application documentation is expected to be put in the TACAD and under TIPSTER CM control:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "\u2022 1. TIPSTER Application Design Documentation.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "\u2022 2. Documentation detailing any design discrepancy or deviations from the TIPSTER Architecture on a per-module basis. This document will also justify or explain the discrepancy or deviations found.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "\u2022 3. Any Requests For Change (RFC) to the TIPSTER Architecture to cover the discrepancy or deviations in the TACAD.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "At the FOC control gate, the following are expected to be put in the TACAD and under TIPSTER CM control:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "\u2022 1. TIPSTER Application As-Built Documentation.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "\u2022 2. Documentation detailing any as-built discrepancy or deviations from the TIPSTER Architecture. This document will also explain the discrepancy or deviations.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "\u2022 3. Any Requests For Change (RFC) to the TIPSTER Architecture to cover the discrepancy or deviations.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "It is expected that TIPSTER Applications will require control gates at the time of design and at the time of final delivery. The TIPSTER PDR and FOC control gates will 'piggy-back' on the projects control gates, to the maximum extent possible. The Architecture Committee will determine whether a TIPSTER Application has successfully passed a PDR and FOC control gate ERBs. In practice, the Architecture Committee will appoint a small group of people to sit on the Configuration Control Board (CCB) to examine, in detail, the documentation and justifications provided at the PDR and FOC control gates. The CCB will then make a recommendation to the Architecture Committee as to whether or not the control gate has been satisfied. The specifics of how to run the CCB and the control gates are given in Section 3.0, below.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "The CCB will assign and use an Engineering Review Board (ERB) to compile the documentation necessary for the CCB's review. The ERB will be comprised of the SE/CM and the developing contractor's representatives. The specifics of how to run the ERB are given in Section 3.0, below.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "Discrepancies will originate from the ERB and will primarily be presented by the developing contractor's representatives. The discrepancies will be submitted to the CCB for disposition, which can be one of the following:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "\u2022 An RFC can be initiated to incorporate the discrepancy as a change to the Architecture Design Document.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "\u2022 The discrepancy can be \"Noted and Documented\". This would assume that it is in the best interest of the Government to deviate from the Architecture in this particular case.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "\u2022 The discrepancy can be sent back to the developing contractor and the Government Contracting Officer's Technical Representative (COTR) with a request that the discrepancy be cleared up.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "2.0 BACKGROUND", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management in a TIPSTER Application LifeCycle", |
| "sec_num": "1.3" |
| }, |
| { |
| "text": "Phase I of the TIPSTER Text Program, including the Text Retrieval Conference (TREC) and Message Understanding Conference (MUC) activities, produced a variety of advanced methods for text handling. However, incorporating the various algorithms and methods into usable applications under one TIPSTER Architecture requires close control and documentation of the constituent parts that comprise the TIPSTER II Architecture. This assumption is based on the following points:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Need for TIPSTER Configuration Management", |
| "sec_num": "2.1" |
| }, |
| { |
| "text": "\u2022 The detection and extraction systems were not developed to work together, although many important text processing tasks require interaction between detection and extraction technologies.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Need for TIPSTER Configuration Management", |
| "sec_num": "2.1" |
| }, |
| { |
| "text": "\u2022 Applications produced under Phase I have not been tested against the variety of tasks and natural languages that must be handled. The Government cannot treat every application requirement for natural language processing as a separate system; deployable systems must be flexible enough to handle a variety of tasks and languages with only minor modifications.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Need for TIPSTER Configuration Management", |
| "sec_num": "2.1" |
| }, |
| { |
| "text": "\u2022 Existing systems at both a component and module level implement similar functionality very differently. Standardizing on the Architecture and interfaces of a core set of such components and modules, so that they can be reused in many applications on many platforms, is the purpose of the TIPSTER Text Phase II Program. Specialized functions can have standard interfaces to operate with these core functions. This functional modularization will support the interoperability and flexibility that the Government believes is necessary to handle the variety and breadth of its text processing tasks. It will also reduce acquisition and maintenance costs and allow for the orderly expansion of an application's capability once deployed. Finally, functional modularization will support and advance the research community by making available a standardized, basic text handling architecture; no longer will an architecture have to be invented for every new experiment.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Need for TIPSTER Configuration Management", |
| "sec_num": "2.1" |
| }, |
| { |
| "text": "The TIPSTER II SE/CM effort involves supporting the Government in overseeing the development of an open architecture and integration of components and modules for comprehensive text handling capabilities. This will allow processing of character streams and text databases from many disparate sources through content detection and data base or knowledge base update. In addition, tools and interfaces for configuring architecture components to particular applications must be integrated and managed.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "2,2 SE/CM Role Within the Overall TIPSTER Framework", |
| "sec_num": null |
| }, |
| { |
| "text": "Key issues in the development of the architecture requirements are defining the functions to be performed, the specific requirements of components and modules to perform each such function, particularly their input, output, and interface specifications, and also specifying an open architecture for integrating all components and modules. Key issues in the development of the Architecture itself are standardizing, documenting, and disseminating the module functional and interface specifications.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "2,2 SE/CM Role Within the Overall TIPSTER Framework", |
| "sec_num": null |
| }, |
| { |
| "text": "The role of the SE/CM contractor is best understood within the context of the overall TIPSTER framework. This framework includes three separate but interrelated set of activities: the SE/CM effort; the Architecture efforts; and the Demonstration Activities. Figure 2 -1 depicts the respective functions of each activity set, and their interrelationships. The figure highlights the communications between SE/CM and the other activities, which will typically be in the form of architecture component requirements or description documents, and completed software modules.", |
| "cite_spans": [], |
| "ref_spans": [ |
| { |
| "start": 258, |
| "end": 266, |
| "text": "Figure 2", |
| "ref_id": null |
| } |
| ], |
| "eq_spans": [], |
| "section": "2,2 SE/CM Role Within the Overall TIPSTER Framework", |
| "sec_num": null |
| }, |
| { |
| "text": "\u2022 rchitecture Rqmts\"~ Definition ..) . B -- SE/CM m./f V&V Common~'~-~\"~ .... fArchitecture Rqmts'~ ~ Modules* J I I=.TTOr'[ Definition J *If Applicable (\"-C M Common~ L Module,~. J _ Demonstration Demonstration Prototype Implementation ,..)-- Activities Figure 2-1 SE/CM Activities Related to Overall TIPSTER Framework", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "2,2 SE/CM Role Within the Overall TIPSTER Framework", |
| "sec_num": null |
| }, |
| { |
| "text": "Initially, the architecture requirements will be defined from the existing TIPSTER I requirements, with the addition of requirements for integrating the most promising algorithms from that effort. The SE/CM will assist the Government in evaluating architectures proposed by TIPSTER II contractors. Later, as demonstration prototypes are initiated, their requirements must be analyzed to determine the adequacy of the existing architecture, and to define necessary or desirable enhancements.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "2,2 SE/CM Role Within the Overall TIPSTER Framework", |
| "sec_num": null |
| }, |
| { |
| "text": "Throughout this iterative process, the SE/CM will perform configuration identification activities including configuration definition, establishment of the Architecture baseline, review of applicable documentation and processing of Architectural changes. These activities will occur throughout the refinement effort and life of the Architecture. The SE/CM will work with the senior technical designers and engineers from all of the TIPSTER II teams to identify the Configuration Items (CIs). CM is responsible for gathering, storing, and presenting the current status of each configuration item.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "2,2 SE/CM Role Within the Overall TIPSTER Framework", |
| "sec_num": null |
| }, |
| { |
| "text": "The purpose of this plan is to establish guidelines, responsibilities, methods and procedures for CM for the TIPSTER Text Phase II Architecture. Specific procedures for CM are in related Configuration Management Procedures (CMPs). CM is intended to provide a stable and consistent definition of the TIPSTER Architecture.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Purpose of the CM Plan", |
| "sec_num": "2.3" |
| }, |
| { |
| "text": "The scope of this plan encompasses anything related to the TIPSTER Architecture. As such, CM will be in effect during the life of the Architecture and will be primarily concerned with the documentation which describes the Architecture. It will not be applied to the software produced by the developers; CM for that software is the responsibility of the individual contractor.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Scope of the CM Plan", |
| "sec_num": "2.4" |
| }, |
| { |
| "text": "The CM process is expected to become active at such time as the first Architecture baseline is established and CM will remain active throughout the life of the Architecture.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Scope of the CM Plan", |
| "sec_num": "2.4" |
| }, |
| { |
| "text": "The CM process will monitor and control changes to the Architecture. Normally, changes to the baseline will be initiated when an TIPSTER Application has been designed and the PDR identifies potential deficiencies in the Architecture.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Scope of the CM Plan", |
| "sec_num": "2.4" |
| }, |
| { |
| "text": "Request For Changes (RFC) will go through the CM process and ultimately be approved by the Architecture Committee.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Scope of the CM Plan", |
| "sec_num": "2.4" |
| }, |
| { |
| "text": "It is expected that the TIPSTER Architecture will continuously be undergoing growth and change. It is therefore vital that the CM process be able to reconstruct the exact state of the TIPSTER Architecture at any given date in the past.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Scope of the CM Plan", |
| "sec_num": "2.4" |
| }, |
| { |
| "text": "Changes are categorized as either Class I, which is a change to the current Architecture baseline, or Class II, which is all other changes, such as correction of document typographical errors, resolution of ambiguities, and changes that clearly do not qualify as a Class I. Deviations are defined as discrepancies wherein an application does not conform to the particular Architectural standard.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Scope of the CM Plan", |
| "sec_num": "2.4" |
| }, |
| { |
| "text": "In addition to what was already noted in Section 1.2, this CM Plan defines the configuration management activities and philosophy required to support the TIPSTER Text Phase II Architecture throughout its entire life cycle. CM provides a means to identify, control, audit, and report on the configuration and status of the TIPSTER Architecture.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "CM Plan Synopsis", |
| "sec_num": "2.5" |
| }, |
| { |
| "text": "The remaining sections of this document provide information to effect quality change and release controls for TIPSTER II:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "CM Plan Synopsis", |
| "sec_num": "2.5" |
| }, |
| { |
| "text": "\u2022 Section 2.0 lists the referenced documents and the documents under CM which in turn define the Architecture at any time.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "CM Plan Synopsis", |
| "sec_num": "2.5" |
| }, |
| { |
| "text": "\u2022 Section 3.0 describes the relevant SE/CM configuration organizations for TIPSTER II. It also describes the CM roles and responsibilities of other program entities.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "CM Plan Synopsis", |
| "sec_num": "2.5" |
| }, |
| { |
| "text": "\u2022 Section 4.0 describes the general approach to CM, CM responsibilities, and CM Phasing and Milestones.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "CM Plan Synopsis", |
| "sec_num": "2.5" |
| }, |
| { |
| "text": "\u2022 Section 5.0 has a glossary of all acronyms and abbreviations used in this CM Plan.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "CM Plan Synopsis", |
| "sec_num": "2.5" |
| }, |
| { |
| "text": "The following documents were referenced in preparing this document. ", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Referenced and CM Documents", |
| "sec_num": "2.6" |
| }, |
| { |
| "text": "The TIPSTER II SE/CM project employs a Configuration Management organization to establish CM procedures, oversee the application of these procedures by all team members and provide all necessary reports and support for the CM function. The overall TIPSTER Text Phase II program organization, depicted in Figure 3 -1, identifies the relationship of the SE/CM support function with other TIPSTER components. This complex structure consists of the multi-agency Executive Committee and Architecture Committee, architecture contractors, demonstration and prototype development contractors, COTRs and the SE/CM contractor. Figure 3- ", |
| "cite_spans": [], |
| "ref_spans": [ |
| { |
| "start": 304, |
| "end": 312, |
| "text": "Figure 3", |
| "ref_id": "FIGREF4" |
| }, |
| { |
| "start": 617, |
| "end": 626, |
| "text": "Figure 3-", |
| "ref_id": "FIGREF4" |
| } |
| ], |
| "eq_spans": [], |
| "section": "Organizational Structure", |
| "sec_num": "3.1" |
| }, |
| { |
| "text": "N \\ [ Working Group I Integrated D \u1ebd ~'~/~\"~'~...~J~] W\u00b0rk~\"~ '~\"/~\"-L~J~'--M- t r~--t ....... ~ \" 1 1 ~ Draft ; * *r--~u'q~ '~---~L~n~Jd [R&D", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Organizational Structure", |
| "sec_num": "3.1" |
| }, |
| { |
| "text": "The following paragraphs describe the roles and responsibilities of each project element involved in the CM function. Figure 3 -3 illustrates the organizational structure of the SE/CM organization. ", |
| "cite_spans": [], |
| "ref_spans": [ |
| { |
| "start": 118, |
| "end": 126, |
| "text": "Figure 3", |
| "ref_id": "FIGREF4" |
| } |
| ], |
| "eq_spans": [], |
| "section": "Roles and Responsibilities", |
| "sec_num": "3.2" |
| }, |
| { |
| "text": "The Program Manager (PM) assists the Chair of the Architecture Committee in meeting the objectives of the TIPSTER Architecture and Demonstration programs, with respect to requirements definition, coordination of disparate contractors and approaches, and supervision of the configuration management and verification/validation efforts. Compliance with the guidelines and procedures specified in this plan is the primary responsibility of the program manager along with the CM Manager (CMM). The PM is responsible for approving the tailoring of CM policies, practices, and procedures to ensure that adequate methods are implemented for identification and control of the TIPSTER Architecture.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SE/CM Program Manager", |
| "sec_num": "3.2.1" |
| }, |
| { |
| "text": "The Program Manager ensures that:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SE/CM Program Manager", |
| "sec_num": "3.2.1" |
| }, |
| { |
| "text": "\u2022 Adequate CM resources, including CM tools, are made available.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SE/CM Program Manager", |
| "sec_num": "3.2.1" |
| }, |
| { |
| "text": "\u2022 CM plans and procedures are approved by the Architecture Committee Chair.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SE/CM Program Manager", |
| "sec_num": "3.2.1" |
| }, |
| { |
| "text": "\u2022 Documented and approved CM practices and procedures are followed by all team members.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SE/CM Program Manager", |
| "sec_num": "3.2.1" |
| }, |
| { |
| "text": "\u2022 CM personnel are trained in the objectives, procedures, and methods for performing their assigned CM activities.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SE/CM Program Manager", |
| "sec_num": "3.2.1" |
| }, |
| { |
| "text": "\u2022 CM requirements, processes, and practices are conveyed to all TIPSTER team members for compliance.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SE/CM Program Manager", |
| "sec_num": "3.2.1" |
| }, |
| { |
| "text": "The CM Manager (CMM) will report to the TIPSTER SE/CM Program Manager. The CMM is responsible for (a) implementing a CM system which is tailored for the unique features of the TIPSTER Text Phase II Program and (b) developing CM procedures to assure control of documentation. To support the preparation of configuration status reports, the CMM maintains a database containing the change status of all Architecture elements and changes.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management Manager", |
| "sec_num": "3.2.2" |
| }, |
| { |
| "text": "To assure the integrity of all items placed within CM control, the CMM establishes and maintains both electronic and hard copy libraries with access limited to CM personnel. The CMM acts as the point of contact for receiving and processing information from external organizations. Incoming and outgoing shipments of CM controlled items will be handled by the CMM. The CMM is also responsible for performing and supporting both formal and informal audits conducted at appropriate milestones during the Architecture life cycle.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management Manager", |
| "sec_num": "3.2.2" |
| }, |
| { |
| "text": "The CMM is a regular participant in all ERB and CCB meetings. The role of the CMM is to schedule these meetings, provide an agenda, record and disseminate minutes, and track action items.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management Manager", |
| "sec_num": "3.2.2" |
| }, |
| { |
| "text": "The CMM, in performing the foregoing responsibilities, will have the independence and authority to coordinate and communicate CM functions with management and technical personnel involved in the Architecture effort. All management and technical personnel are required to be familiar with and comply with the provisions of this CM plan, as well as being responsible for certain configuration activities in support of CM functions. The following ", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Management Manager", |
| "sec_num": "3.2.2" |
| }, |
| { |
| "text": "A software architecture engineer will assist the Architecture Committee Chair by performing certain CM tasks. These tasks consist of reviewing/analyzing problem reports and change requests, and preparing recommendations to effect proposed changes or preparing a statement why the proposed change should not be made to the Architecture.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Software Architecture Engineer", |
| "sec_num": "3.2.3" |
| }, |
| { |
| "text": "The Verification and Validation (V&V) Testing Engineer will develop and implement tests to determine if modules in TIPSTER Applications are consistent with the Architecture Design Document by ensuring that they conform to the specifics in the Architecture Design Document.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Verification and Validation Testing Engineer", |
| "sec_num": "3.2.4" |
| }, |
| { |
| "text": "Additionally, if necessary, the V&V Test Engineer will determine that shared components and modules interface as required, both in isolation and in combination with the other components and modules. Specifically, the interfaces must be as described in the TIPSTER Interface Control Document. Internal component processing capabilities do not come under the scope of V& V Testing. (See V&V Test Plan). The V&V Testing Engineer controls formal CSCI test procedure development prior to those components being placed under formal CM control, reports problems identified during formal CSCI testing to CM, and actively participates in ERB and CCB meetings.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Verification and Validation Testing Engineer", |
| "sec_num": "3.2.4" |
| }, |
| { |
| "text": "The CCB is the Government review and action board comprised of key personnel from the Architecture Committee, SE/CM, and the appropriate contractors. The CCB provides a central point of coordination of changes to the baseline Architecture. The CCB is the focal point and the source of direction for implementation of Class I changes to the TIPSTER II Architecture.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Control Board (CCB)", |
| "sec_num": "3.2.5" |
| }, |
| { |
| "text": "The CCB reviews each Class I change and makes a decision as to the disposition with the options of (a) approve the change, (b) disapprove the change, or (c) defer the proposed change. Each board member is allowed to state his/her official position on the proposed change. However, the CCB is a non-voting board. Thus, the CCB Chairman shall render the final decision as to the course of action to the taken. The CCB's decision is recorded as a Change Directive.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Control Board (CCB)", |
| "sec_num": "3.2.5" |
| }, |
| { |
| "text": "The CCB's major responsibilities are:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Control Board (CCB)", |
| "sec_num": "3.2.5" |
| }, |
| { |
| "text": "\u2022 Review all proposed change requests.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Control Board (CCB)", |
| "sec_num": "3.2.5" |
| }, |
| { |
| "text": "\u2022 Assess change impacts.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Control Board (CCB)", |
| "sec_num": "3.2.5" |
| }, |
| { |
| "text": "\u2022 Provide a statement that the application development which initiated a change is in compliance with the Architecture or represents a deviation from the Architecture.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Control Board (CCB)", |
| "sec_num": "3.2.5" |
| }, |
| { |
| "text": "\u2022 Review modifications to all documentation.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Control Board (CCB)", |
| "sec_num": "3.2.5" |
| }, |
| { |
| "text": "\u2022 The results of any actions taken by the CCB are reported to the Architecture Committee.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Control Board (CCB)", |
| "sec_num": "3.2.5" |
| }, |
| { |
| "text": "The membership of the CCB is: Other key personnel will be assigned to the CCB as the Chair may deem necessary to resolve particular issues. The CCB Chair will conduct the meeting and render the final decision to the course of action to be taken.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Control Board (CCB)", |
| "sec_num": "3.2.5" |
| }, |
| { |
| "text": "The above members form the core of the CCB. If a member is unable to attend a meeting, he/she must designate a representative to attend in his/her place. The representative must have full authority to act on behalf of the missing member. Additional individuals are invited to participate, as appropriate, when their technical expertise is required.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Configuration Control Board (CCB)", |
| "sec_num": "3.2.5" |
| }, |
| { |
| "text": "The ERB is an internal TIPSTER II Architecture review and action panel comprised of personnel from all project groups. Membership of the ERB is: The objectives of the ERB are disposition of problems, classification of proposed changes, and disposition of Class II changes. Upon receipt and disposition of a problem, the ERB will analyze it for type of problem, priority, and verification of the proposed solution. When the problem is fixed, the ERB will determine the implementation schedule of the fix into the affected baselines. Upon review of a change request, the ERB first determines the classification as either a Class I or Class II type of change. For Class I changes, the ERB assigns preparation of a Request For Change (RFC) to the responsible groups for submittal to the CCB for their review and disposition. Class II changes are within the scope of authority of the ERB for disposition. The ERB reviews each Class II change and then takes appropriate action for its disposition. Each panel member is allowed to state his/her position on the change. However, the ERB is a non-voting board. Thus, the ERB chairman shall render final decision as to the course of action to be taken. ERB decisions are recorded on Change Directives, a copy of which is sent to the CCB for information only.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Engineering Review Board (ERB)", |
| "sec_num": "3.2.6" |
| }, |
| { |
| "text": "\u2022 SE/CM", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Engineering Review Board (ERB)", |
| "sec_num": "3.2.6" |
| }, |
| { |
| "text": "The Architecture Committee has final authority over the TIPSTER Architecture and in this role can accept or reject any Change Directive reported by the CCB.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Architecture Committee", |
| "sec_num": "3.2.7" |
| }, |
| { |
| "text": "The Architecture Committee appoints the members of the CCB. ", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Architecture Committee", |
| "sec_num": "3.2.7" |
| }, |
| { |
| "text": "Since the CM function does not start until the Architecture baseline has been released by the Architecture Working Group (AWG), it will have no CM responsibility.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Architecture Working Group (AWG)", |
| "sec_num": "3.2.8" |
| }, |
| { |
| "text": "The TIPSTER Phase II evaluation working group (EWG) is tasked with designing, implementing, and coordinating evaluations intended to demonstrate the effectiveness of TIPSTER architectural approaches; thus, the EWG will be a user of the results of the CM process by using the appropriate Architectural version in their evaluations. ", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Evaluation Working Group", |
| "sec_num": "3.2.9" |
| }, |
| { |
| "text": "The SE/CM has five major goals with respect to the RFC process for the TIPSTER Architecture. follows:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "The Goal", |
| "sec_num": "4.4.1" |
| }, |
| { |
| "text": "Submissions of RFCs can come from any source. developers, the CAWG, or the SE/CM.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Overview -Submitter/Reviewer", |
| "sec_num": "4.4.2" |
| }, |
| { |
| "text": "Submissions from applications developers will be They are as Provide for consistency in the development of the Architecture.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Application Developer Submission", |
| "sec_num": "4.4.2.1" |
| }, |
| { |
| "text": "Allow for changes, proposed on the basis of different versions of the Architecture, to be combined into a single change.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Application Developer Submission", |
| "sec_num": "4.4.2.1" |
| }, |
| { |
| "text": "Provide for consideration of changes proposed by any interested party.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Application Developer Submission", |
| "sec_num": "4.4.2.1" |
| }, |
| { |
| "text": "Encourage changes to the Architecture from anyone who has done an implementation.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Application Developer Submission", |
| "sec_num": "4.4.2.1" |
| }, |
| { |
| "text": "Provide for independent submission and review of proposed changes.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Application Developer Submission", |
| "sec_num": "4.4.2.1" |
| }, |
| { |
| "text": "It is expected that submissions will be made by application reviewed by the SE/CM and approved/disapproved by the Architecture Committee. As reviewer, the SE/CM will recommend minor modifications to the RFC to maintain a level of consistency in names and methods. If major modifications are necessary, the SE/CM may submit an entirely new RFC. The Architecture Committee will then have both RFCs to approve/disapprove. The CAWG will be able to evaluate the proposed changes and make suggestions to the SE/CM or the Architecture Committee. Any comments/recommendations by the CAWG will be an addendum to the formal RFC.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Application Developer Submission", |
| "sec_num": "4.4.2.1" |
| }, |
| { |
| "text": "As a minimum, the CAWG will receive the RFC when it is formally submitted to the SE/CM. Under normal circumstances, however, the SE/CM will be aware that changes are likely to be forthcoming from an application under development. In such cases, the SE/CM will keep the CAWG informed of the issue under discussion. In this way, the CAWG may be able to provide timely input to the application developer as to previously debated issues or 'known' work-arounds for the difficulty encountered.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Application Developer Submission", |
| "sec_num": "4.4.2.1" |
| }, |
| { |
| "text": "Submissions from the CAWG will be reviewed by the SE/CM and approved/disapproved by the Architecture Committee. As reviewer, the SE/CM may recommend minor modifications to the RFC to maintain a level of consistency in names and methods.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "CAWG Submission", |
| "sec_num": "4.4.2.2" |
| }, |
| { |
| "text": "On rare occasions, submissions may come from the SE/CM and will be reviewed by the CAWG or other person(s) as designated by the Architecture Committee and approved/disapproved by the Architecture Committee. The reviewer may recommend minor modifications to the RFC to maintain a level of consistency in names and methods.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SE/CM Submission", |
| "sec_num": "4.4.2.3" |
| }, |
| { |
| "text": "If the reviewer is not the CAWG, the SE/CM will keep the CAWG informed of the issue under discussion. In this way, the CAWG will be able to provide comments and recommendations to the Architecture Committee.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SE/CM Submission", |
| "sec_num": "4.4.2.3" |
| }, |
| { |
| "text": "RFCs will be formally tracked by their RFC number. The RFC will contain the following: ", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "Tracking of RFCs", |
| "sec_num": "4.4.3" |
| }, |
| { |
| "text": "The CM activities described in this CM Plan are initiated and completed in accordance with the Program Master Schedule.Table 4-1 is a list of major events/milestones and specifies the CM activities conducted and the planned dates for initiation and completion of each event/milestone.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "", |
| "sec_num": null |
| } |
| ], |
| "back_matter": [], |
| "bib_entries": {}, |
| "ref_entries": { |
| "FIGREF0": { |
| "text": "2 TIPSTER Application LifeCycle with Configuration Management Gates", |
| "type_str": "figure", |
| "uris": null, |
| "num": null |
| }, |
| "FIGREF1": { |
| "text": "Figure 3-2 Configuration Management Functional Structure", |
| "type_str": "figure", |
| "uris": null, |
| "num": null |
| }, |
| "FIGREF2": { |
| "text": "Organizational Structure of TIPSTER II SE/CM Support", |
| "type_str": "figure", |
| "uris": null, |
| "num": null |
| }, |
| "FIGREF4": { |
| "text": "Figure 3-4 CM Organization", |
| "type_str": "figure", |
| "uris": null, |
| "num": null |
| }, |
| "FIGREF5": { |
| "text": "Such as Email TrafficThe RFCs will be available on the internet on the TIPSTER web page5.0 GLOSSARY AND LIST OF ABBREVIATIONSThe terms and abbreviations listed below are used within this CM Plan. Their meanings are provided for the reader'", |
| "type_str": "figure", |
| "uris": null, |
| "num": null |
| }, |
| "TABREF1": { |
| "type_str": "table", |
| "text": "The structure, roles and responsibilities of the Configuration Management organization are defined in the paragraphs below.", |
| "num": null, |
| "html": null, |
| "content": "<table><tr><td colspan=\"2\">3.0 ORGANIZATION</td></tr><tr><td colspan=\"2\">The documents which will be placed under CM are:</td></tr><tr><td>\u2022</td><td>TIPSTER Requirements Document</td></tr><tr><td>\u2022</td><td>TIPSTER Architecture Design Document</td></tr><tr><td>\u2022</td><td>TIPSTER Architecture Interface Control Document</td></tr><tr><td>\u2022</td><td>TIPSTER Architecture Concept</td></tr><tr><td>\u2022</td><td>TIPSTER CM Plan</td></tr><tr><td>\u2022</td><td>TIPSTER Validation and Verification Plan</td></tr><tr><td>\u2022</td><td>TACAD</td></tr></table>" |
| }, |
| "TABREF3": { |
| "type_str": "table", |
| "text": "", |
| "num": null, |
| "html": null, |
| "content": "<table><tr><td/><td/><td/><td>cM I Manager</td></tr><tr><td>Identify Configuration Items</td><td colspan=\"4\">[ I Documentation Control Configuation Changes I I I \u00b0 are I I'n'or 'll For a' I ii sta' us' [ Report on Changes Conduct & Support Audits i I I I</td><td>I CCB & ERB</td><td>i</td></tr><tr><td colspan=\"2\">Project 7</td><td>~J</td><td>Architecture</td><td>Architecture</td></tr><tr><td colspan=\"2\">i R&D Project~-</td><td>t~===~lates</td><td>~ ~</td><td>L~._.l-~ates</td></tr><tr><td colspan=\"5\">I~,o ~ro~ec~ \u00b0r ,~o V ,,~o I~'\u00b0 Figure 3-1 TIPSTER Text Phase II Organization , Lo hero</td><td>\"%\u00b0o</td></tr></table>" |
| }, |
| "TABREF5": { |
| "type_str": "table", |
| "text": "-1, CM Responsibilities and Relationships, is a matrix of the major CM functions and responsibilities of various management and technical personnel.", |
| "num": null, |
| "html": null, |
| "content": "<table><tr><td/><td/><td/><td colspan=\"3\">Site Responsibilities</td><td/></tr><tr><td>Program Configuration</td><td>Client</td><td>PM</td><td>Technical</td><td>CMM</td><td>Technical</td><td>Subcontractors</td></tr><tr><td>Managment Functions/</td><td>Program</td><td/><td>Manager</td><td/><td>Staff</td><td/></tr><tr><td>Responsibilities</td><td>Office (PO)</td><td/><td/><td/><td/><td/></tr><tr><td>Baselines: Functional</td><td>Approve,</td><td>Monitor</td><td>Comply</td><td>Administer!</td><td>Comply</td><td>Comply</td></tr><tr><td/><td>Control &</td><td/><td/><td/><td/><td/></tr><tr><td/><td>Review</td><td/><td/><td/><td/><td/></tr><tr><td>Allocated</td><td>Approve,</td><td>Monitor</td><td>Comply</td><td>Administer</td><td>Comply</td><td>Comply</td></tr><tr><td/><td>Control &</td><td/><td/><td/><td/><td/></tr><tr><td/><td>Review</td><td/><td/><td/><td/><td/></tr><tr><td>Development</td><td>Approve &</td><td>Establish &</td><td>Comply</td><td>Administer</td><td>Comply</td><td>Comply</td></tr><tr><td/><td>Review</td><td>Manage</td><td/><td/><td/><td/></tr><tr><td>Product</td><td>Approve,</td><td>Monitor</td><td>Comply</td><td>Administer</td><td>Comply</td><td>Comply</td></tr><tr><td/><td>Control &</td><td/><td/><td/><td/><td/></tr><tr><td/><td>Review</td><td/><td/><td/><td/><td/></tr><tr><td>Configuration Identification</td><td>Control</td><td>Submit to</td><td>Review</td><td>Perform</td><td>Provide</td><td>Provide</td></tr><tr><td/><td/><td>Client PO</td><td>Inputs</td><td/><td>Inputs</td><td>Inputs</td></tr><tr><td>Change Requests</td><td>Control</td><td>Submit to</td><td>Originate</td><td>Administer</td><td>Provide</td><td>Provide</td></tr><tr><td/><td/><td>Client PO</td><td/><td/><td>Inputs</td><td>Inputs</td></tr><tr><td>Implement Approved</td><td>Control</td><td colspan=\"2\">Manage Perform</td><td>Support</td><td>Perform</td><td>Perform</td></tr><tr><td>Changes</td><td/><td/><td/><td/><td>I</td><td/></tr><tr><td>Program Change Control</td><td>Review</td><td>Chair</td><td colspan=\"2\">Member : Administer</td><td>Attend !</td><td>Attend</td></tr><tr><td>Panel</td><td/><td/><td>i</td><td/><td/><td/></tr><tr><td>Configuration Library</td><td>Review</td><td>Review</td><td>Support</td><td>Manage</td><td>Support</td><td>Support</td></tr><tr><td>Documents/Deliverables</td><td>Review &</td><td>Submit to</td><td>Review</td><td>Administer</td><td>Prepare</td><td>Prepare</td></tr><tr><td/><td>Approve</td><td>Client PO</td><td/><td/><td>Documents</td><td>Documents</td></tr><tr><td>Status Accounting</td><td>Review</td><td>Review</td><td>Review</td><td>Manage</td><td>Provide</td><td>Provide</td></tr><tr><td/><td/><td>Reports</td><td>Reports</td><td/><td>Inputs</td><td>Inputs</td></tr><tr><td>Configuration Reviews &</td><td>Review</td><td>' Chair</td><td colspan=\"2\">Prepare Administer</td><td>Provide</td><td>Provide</td></tr><tr><td>Audits</td><td/><td/><td/><td/><td>Inputs</td><td>Inputs</td></tr><tr><td/><td colspan=\"5\">Table 3-1 CM Responsibilities and Relationships</td><td/></tr></table>" |
| }, |
| "TABREF8": { |
| "type_str": "table", |
| "text": "The membership of the EWG is composed of the following core personnel:", |
| "num": null, |
| "html": null, |
| "content": "<table><tr><td colspan=\"2\">Events/Milestones</td><td>CM Activities</td><td>Start Date</td><td>Finish Date</td></tr><tr><td colspan=\"2\">Requirements</td><td>Initiate status accounting for action items,</td><td>00/00/00</td><td>00/00/00</td></tr><tr><td>Definition</td><td/><td>Establish project files</td><td/></tr><tr><td>Commence</td><td/><td>Establish Architecture Baseline, Initiate change</td><td/></tr><tr><td colspan=\"2\">Configuration</td><td>control, Initiate \"Version Description Document\"</td><td/></tr><tr><td>Management</td><td/><td>Initiate status accounting for changes, and continue</td><td/></tr><tr><td/><td/><td>Action Items Maintain project files</td><td/></tr><tr><td>CM Setup</td><td/><td>Identify Configuration Items, Continue change</td><td/></tr><tr><td/><td/><td>control, Continue status accounting for changes and</td><td/></tr><tr><td/><td/><td>action items, Maintain project files, Deliver</td><td/></tr><tr><td/><td/><td>architecture documents</td><td/></tr><tr><td>Preliminary</td><td>Design</td><td>Process changes, identify Architectural Deviations,</td><td/></tr><tr><td colspan=\"2\">Review (PDR)</td><td>Continue change control, Update \"Version</td><td/></tr><tr><td/><td/><td>Description Document\", Continue status accounting</td><td/></tr><tr><td/><td/><td>for changes and Action Items, Maintain project files</td><td/></tr><tr><td>Final</td><td>Operating</td><td>Issue Architecture Deviation Document Continue</td><td/></tr><tr><td colspan=\"2\">Capability (FOC)</td><td>change control, Update \"Version Description</td><td/></tr><tr><td/><td/><td>Document\", Continue status accounting for changes</td><td/></tr><tr><td/><td/><td>and action items, Maintain project files,</td><td/></tr><tr><td colspan=\"2\">\u2022 Chairperson</td><td/><td/></tr><tr><td>\u2022</td><td colspan=\"2\">SE/CM Representative</td><td/></tr><tr><td>\u2022</td><td colspan=\"2\">2 NSA Representatives</td><td/></tr></table>" |
| } |
| } |
| } |
| } |
