bluuebunny/crossref_metadata_2025_split huggingface dataset:
THE CREATION OF SYSTEMS AND SOFTWARE STANDARDS BY AN EVOLUTIONARY PROCESS
Authors: Brook Peter , Arnold Stuart , Barnes Derek , Stevens Richard 
Published: November 2014

AbstractImproving the efficiency of the development of software and systems is essential to all modern companies. For one UK organisation, this has led to a concerted effort in developing and applying standards, training, pilot projects, promotional activities, and setting up centres of expertise. The results for both software and systems have been almost totally positive. A relatively small investment has made systems and software developments more professional, and this approach is being extended across the whole organization.A continuous process improvement approach has been adopted, with the initial effort focused on achieving ISO 9001 certification for software. The second iteration has used experience gained to enhance the original standards. The goals for Phase 2 were to cover large systems, to improve metrics, and to cover feasibility work. The systems process was itself used to define a coherent architecture for the standards, along with the training and organisational implementation. The wider professional community has been involved in the standards process, including the DERA's customers and associates, industry, as well as members of the UK INCOSE Chapter. This paper records the experience in evolving the standards.
USE OF PROCESS MODELS TO ESTIMATE A PROJECT'S DEVELOPMENT COSTS
Authors: Langston Dale G. 
Published: November 2014

AbstractCurrent cost models were developed based on the assumption that complexity of the product was the dominant predictor of cost. This paper describes a cost model developed around process capability that eliminates the dependency on complexity. This paper describes the development of the model, results from execution of the model, and future work to be undertaken to extend to model.
IMPLEMENTING RECALL: A CASE‐BASED REASONING SYSTEM FOR THE ACCESS AND REUSE OF LESSONS LEARNED
Authors: Sary Charisse , Mackey William 
Published: November 2014

AbstractThis paper discusses the activities of an ongoing project to develop and field the Reusable Experience with Case‐Based Reasoning for Automating Lessons Learned (RECALL) system. RECALL captures and reuses lessons learned at the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center's Mission Operations and Data Systems Directorate (MO&DSD). Primarily, systems and software engineering lessons learned are captured. Lessons learned describe positive experiences and successes that need to be reinforced, as well as problems faced and ways to avoid them in the future. We believe that lessons learned would be reused more often if others confronted with similar problems could locate them quickly and easily.Therefore, the case‐based reasoning (CBR) approach is being tried as an alternative to more conventional or other intelligent software methods. A proof‐of‐concept prototype was developed and demonstrated to evaluate the applicability of CBR to this problem. This paper describes subsequent work, which includes making RECALL operational and fielding the system on the World Wide Web to facilitate user access. Because the system will be available to a diverse set of users, a process for incorporating lessons into the database has been defined. This paper describes the process and the actual execution of this process during RECALL implementation.
MEASUREMENT TOOLS FOR RAPID DEVELOPMENT
Authors: Goldense Bradford L. 
Published: November 2014

ABSTRACTThe state of measurement of product development in the 1990s is still largely historical and reactive, but at least measurements are now being made. Measurement is central to improvement. For the past twenty‐five years there has been relatively little improvement in product development productivity. Now the first emergence of predictive and/or proactive metrics are changing fundamental thinking towards the use of measurements to drive product development change, not just to record results. This trend in product development is analogous to the evolution of measurement during the 1980s in the manufacturing‐based functions. Also analogous, is that the product development focus is on measuring processes and not just the resultant product. Comprehensive approaches require metrics for ten to fifteen separable but interrelated business and/or technical processes that comprise product development. Case studies from medical, process control, instrument, and semiconductor companies illustrate measurement approaches and applications of specific metric tools and techniques. Product development metrics will evolve over time to a now unforseen science once a great number of companies cut their cycle time in half. Metrics and measurement tools deployed today will ultimately be considered rudimentary two decades from now.
SOFTWARE QUALITY METRICS FOR LARGE SCALE SYSTEMS DEVELOPMENT
Authors: Toth Kalman C. , John Robert , Stewart Ronald 
Published: November 2014

AbstractMetrics are widely viewed as critical to the execution of large scale software development and systems integration projects. To attain high levels of maturity as defined by the Software Engineering Institute's Capability Maturity Model [Humphrey 1989], it is clear that in addition to effective project management and change controls, metrics processes need to be integrated into the activities of development projects and institutionalized within the business itself. This paper outlines how Hughes Aircraft of Canada Limited, Systems Division (HCSD) has established divisional and program‐specific metrics processes support the production of high quality, maintainable systems. The metrics activities for the Canadian Automated Air Traffic System (CAATS) are used to illustrate many of the ground‐breaking accomplishments achieved at HCSD
IMPLEMENTING A SUCCESSFUL METRICS PROGRAM
Authors: Ramchandani Chander , Buford Carolyn 
Published: November 2014

AbstractIn today's highly competitive business environment, with its tight budgets and pressure for continuous improvement and reengineering, qualitative improvements are no longer adequate for an organization to be competitive in the marketplace. Improvements need to be measurable, which requires the availability of quantified baselines and metrics to support the quantification. This paper describes a framework for collection and utilization of metrics within an organization involved in the engineering, development, and deployment of complex systems; the types of metrics that are needed to measure the effectiveness of an organization's processes; and a proposed framework for their utilization at the tactical and strategic levels, including their roles in process improvement and reengineering. This paper also discusses commonly encountered pitfalls and guidelines for implementing a successful metrics program.
ROCKWELL COLLINS AIR TRANSPORT METRICS
Authors: Philpott Ian W. 
Published: November 2014

AbstractTo continue as a world class avionics company, Collins Air Transport Division is adding engineering metrics to well‐planned Systems, Hardware and Software Processes. We ask much of our engineers, requesting them to follow new and unfamiliar processes, while measuring their work. The paper reviews the objectives of the metrics program and how we are carrying out those objectives. The paper also reviews our staff's concerns introduced by the metrics program.
Supplier Selection Using Capability Maturity Model
Authors: Reichner Albert 
Published: November 2014

AbstractThe Systems Engineering Capability Maturity Model (SE‐CMM) is designed to help organizations improve their practice of systems engineering through self assessment. Although version 1.0 of the SE‐CMM is not intended to be used for supplier selection, the characteristics of a systems engineering organization that indicate mature processes in a self assessment are similarly desirable in assessment for purposes of supplier selection. The existing appraisal method, on the other hand, needs modification for application to supplier selection. The author was a member of a team that used the SE‐CMM with a modified appraisal method to assess the systems engineering capability of four companies for the purpose of supplier selection. As the assessment progressed, the appraisal method was tuned to account for differences between supplier selection and self assessment. In the end the appraisal team successfully accomplished their goal of advising the customer as to the relative and absolute systems engineering capabilities of each candidate supplier.
A Second Systems Engineering Process Assessment at the Westinghouse Hanford Company
Authors: Widmann E. R. , Brenchley D. L. , Andrews B. A. , Worl J. 
Published: November 2014

AbstractIn September 1995, a second systems engineering process assessment (SEPA) was conducted at the Westinghouse Hanford Company (WHC) using the INCOSE Systems Engineering Capability Assessment Model (SECAM) and supporting documents. This SEPA, like the first at WHC in February 1995, was facilitated by the INCOSE CAWG, which developed the INCOSE SECAM and supporting documents (assessment method). The Capability Assessment Working Group (CAWG) is one of four working groups that comprise the Measurement Technical Committee of the Technical Board of the International Council on Systems Engineering (INCOSE).This paper presents detailed information about the SEPA with emphasis on: (1) background events leading up to the SEPA; (2) planning undertaken to ensure the success of the SEPA, including tailoring of the INCOSE SECAM and supporting documents; (3) conduct of the SEPA; (4) post‐SEPA activities, including observations on the ability to mature using the INCOSE SECAM as a vector for growth; and (5) observations from the SEPA, including lessons learned and recommendations for improvement and subsequent impact on the INCOSE SECAM and supporting documents. The SEPA is noteworthy since it is the first time that a complex model developed for measuring systems engineering capability was applied twice to the same organization. This offers the potential of beginning the validation of the model.
A Synopsis of Metrics and Observations from Systems Engineering Process Assessments Conducted Using the INCOSE SECAM
Authors: Andrews B. A. , Widmann E.R. 
Published: November 2014

AbstractThe INCOSE Systems Engineering Capability Assessment Model (SECAM) was developed by the Capability Assessment Working Group (CAWG) to assess systems engineering capability. Eleven systems engineering process assessments (SEPAs) have been conducted using the SECAM and the proto‐models from which it was developed. Three more SEPAs are planned for the near future. This paper characterizes and contrasts the assessment techniques and metrics from each SEPA. Insights from these SEPAs are also summarized to assist potential users of the INCOSE SECAM understand how to prepare for the assessment process.
CONTROLLING THE CHAOS: AN INTEGRATED APPROACH TO MANAGING A SYSTEM DEVELOPMENT PROGRAM
Authors: Adamsen Paul B. 
Published: November 2014

AbstractWhy so much chaos so quickly on many development programs? Typically during the proposal phase the Management Volume is generated in isolation from the Technical Volume and vise versa. After the program is awarded this discontinuity becomes a major fissure embedded in the foundation upon which the program is built. Often chaos in varying degrees results. Symptoms of this condition include: difficulty in measuring progress which impairs visibility afforded to management; key requirements are not communicated to all impacted areas; and critical issues do not get surfaced to management in a timely fashion. Thus the chaos level of the system rises which, in turn, causes the technical, cost, and schedule risk to increase since risk increases proportionately with the chaos level of the system. This paper suggests two ways of minimizing program chaos: first, to implement semi‐autonomous Integrated Product Teams (IPT) and organize them according to the logic of the System Development Process (SDP) (see Adamsen, 1995); second, to integrate the responsibilities of management and technical development under each IPT, fitting each to function semi‐autonomously. The IPT then becomes the mechanism for integrating not only the technical activities, but also the management activities. This environment fosters an atmosphere of camaraderie which facilitates communication across all disciplines of activity. In addition, the development of meaningful metrics tracked with honest inputs occurs since naturally adversarial relationships have been alleviated. Open and honest communication to management is encouraged since all are on the same team and win or lose together, and management of the configuration is facilitated because all the stakeholders are involved in the development. With this approach, the typical discontinuity between the management team and the technical development team, and the ensuing chaos, can be effectively mitigated.
REQUIREMENTS CONSISTENCY ‐A BASIS FOR DESIGN QUALITY‐
Authors: Van Dewerker F. Scott , Booth Stuart T. 
Published: November 2014

AbstractLarge design projects have a significant challenge to maintain consistent quality specifications throughout the development life cycle. The cost of maintaining such specifications and ensuring their consistency is high, and if not performed adequately can pose a significant risk to the program by inducing errors into the design. This paper presents methods for automation in concert with a process that will effectively reduce the inconsistencies in specifications.
Observations on the Measurement of Systems Engineering Capability
Authors: Widmann E. R. , Dragavon E. J. , Schuster J. J. , Richman G. , Bradley D. W. 
Published: November 2014

AbstractIn the past few years, several models have been developed to measure systems engineering process maturity. Two of these models have gained a great deal of attention: the INCOSE SECAM and the EPIC (formerly Industrial Collaboration) SE‐CMM. This paper describes the conduct of a dual systems engineering process assessment that applied both of these well known models to the same organization using the EPIC SE‐CMM Appraisal Method, rather than the shorter duration INCOSE SECAM Assessment Method. The assessment was conducted at Hughes Aircraft Company (HAC), Electro‐Optical Systems (EOS). The assessment is noteworthy since it is the first time both models have been applied concurrently. This paper provides a synopsis of both models along with a description of the dual assessment. Issues observed from the assessment regarding the models and the Appraisal Method are described; their resolution is important for the conduct of future assessments. Impacts upon the two models and application methods are discussed based upon the experiences gained from the dual assessment.
Model Driven System Design Working Group: FOUNDATIONAL CONCEPTS FOR MODEL DRIVEN SYSTEM DESIGN
Authors: Baker Loyd , Clemente Paul , Cohen Bob , Permenter Larry , Purves Byron , Salmon Pete 
Published: November 2014

AbstractThis paper presents an initial viewpoint on an emerging technology: Model Driven System Design (MDSD). In contrast, the current state of practice has been characterized as document centered. Practitioners of system design are well aware of the technical and organizational difficulties of implementing current approaches. By modeling multiple aspects of a system throughout its life cycle, this new view of system design offers dramatic gains in productivity and product quality.
TOOLS INTEGRATION INTEREST GROUP REPORT: SCENARIOS LEADING TOWARDS A CONCEPT OF OPERATIONS FOR AN INTEGRATED SYSTEMS ENGINEERING ENVIRONMENT
Authors: Schier James , Nallon John , Walker John , Kolberg David 
Published: November 2014

ABSTRACTThe Tools Integration Interest Group (TIIG) is developing a Specification for an Integrated Systems Engineering Environment (ISEE) in response to the Corporate Advisory Board. To develop a system specification, one must understand the context in which the system will operate. Consequently, the TIIG is developing, in parallel, the Concepts of Operations for the Integrated Systems Engineering Environment. Initial efforts leading toward the development of the full Concepts of Operations document are defined in terms of two types of scenarios: tool‐oriented scenarios dealing with implementation issues and operation‐oriented scenarios dealing with the envisioned ISEE and how it enables systems engineers to work. This paper collects the initial seven scenarios which have been developed by members of the Tools Integration Interest Group. Five scenarios are tool‐oriented and deal with typical tool‐to‐tool data transfer procedures commonly used. Two scenarios are operations‐oriented and deal with user navigation within an integrated program database for systems engineers and the change control process for managing requirements and assessing the impact of requirements changes.
INCOSE Tools Database Working Group Status Report
Authors: Case Randy , Findley Beth , McMullen William , Sampson Mark E. 
Published: November 2014

AbstractThe Tools Database Working Group is delivering the second release of the Systems Engineering Tools Database at the 1996 INCOSE Symposium. This update is focused on Systems Architecture Tools and includes an update on Requirements Management Tools. The information contained within the database comes direct and unedited from the tool suppliers. It is our wish that this information will save INCOSE members (those looking for information and those providing it) time as well as provide a common framework of reference for these important tools for Systems Engineers.
METRICS WORKING GROUP 1996 REPORT
Authors: Miller William D. , Rhodes Donna H. 
Published: November 2014

AbstractThe INCOSE Metrics Working Group (MWG) mission is to promote shared understanding of systems engineering metrics and measurement practices, and advance the state‐of‐the‐art of metrics collection and utilization. The paper covers:
History and Progress
Meeting Activity
Strategic Goals
MWG Workproducts
Collaboration with CAWG
INCOSE Measurement Technical Committee Paper: Moving Towards an Integrated Set of Products for Measuring Systems Engineering
Authors: Widmann E. R. , Miller W. D. 
Published: November 2014

AbstractThis paper provides information on the INCOSE Measurement Technical Committee and its four working groups. The charter and goals are presented along with objectives for development and support of measurement products. Significant milestone events for both products and product support services are provided – the only products to receive approval, or interim approval, of the INCOSE Technical Board were developed within the Measurement Technical Committee. A description of each of the measurement products developed to date is furnished. A synopsis of the past year's activities is provided along with planned future activities. An integrated approach to development of measurement products is being pursued to permit more effective measurement and improvement of systems engineering activities. The products developed by the Measurement Technical Committee are available to become an integral part of the strategic planning activities of both industry and government.
2 A “Systems of Systems” Perspective of the Year 2000 Problem
Authors: Walker Loren Mark 
Published: November 2014

ABSTRACTA “System of Systems” perspective of the Year 2000 (Y2K) problem is crucial for any organization that owns or operates computer‐based systems that interface with other systems, especially large multi‐computer system programs. This paper focuses on the requirements, multiple systems and interfaces, functional analysis, threads, testing, and multi‐organizational Y2K coordination issues inherent in all large Y2K certification programs. In addition, the positive long‐term benefits of reengineering and documenting the program's functionality, physical architecture and products are also discussed. Special emphasis is placed on the importance of “System Threads”, key to capturing the essence of very complex system interface issues and the prioritization of resource allocations and organizational activities.The importance of preparing for, identifying and fixing problems that remain after January 1, 2000 are also examined. Addressing these topics is essential to assure that, through end‐to‐end operation, large programs consisting of many computer‐based systems, will have a reasonably high level of confidence that: 1) the systems will operate, 2) no corruption of data will occur within the systems, and 3) output products will continue to meet customer expectations.This paper is based on the author's application of the topics discussed to a large multi computer based program, consisting of 100s of unique computer systems located at several locations. The concepts discussed were initiated in 1998 and are proving to be highly effective in meeting the program's Y2K certification needs.
2 Designing Standards for Open Simulation Environments in the Chemical Industries: A Computer‐Supported Use‐Case Approach
Authors: Jarke M. , Becks A. , Köller J. , Tresp C. , Braunschweig B. , Aachen RWTH 
Published: November 2014

AbstractUnder the double pressures of global competition and increasing environmental awareness, the importance of high‐performance simulation tools in the process industries (food, chemicals, oil, …) is rapidly growing. However, traditional simulation environments are closed monolithic systems which are extensible only by a small group of market‐leading vendors. The resulting bottlenecks in interoperability, reuse and innovationled to the CAPE‐OPEN project, in which the chemical and oil industries are defining standards for a component‐based approach to process simulation, in order to open up the market to smaller vendors and to facilitate rapid industrial uptake of academic research prototypes. For general systems engineering, the CAPE‐OPEN standardising process has at least two interesting features: (a) it has experimented on a large scale with a distributed use case approach, following a variant of the UML (Unified Modelling Language) approach for modelling, but also linking down to programming standards based on CORBA (Common Object Request Broker Architecture) and COM (Common Object Model); (b) the management of this world‐wide distributed effort has been facilitated by the use of an Internet‐based workspace co‐operation environment, augmented by advanced structuring and analysis methods from software engineering and computational intelligence.
3 Managing Future ‐ Methodology to Evaluate and Fund Innovative Ideas
Authors: Vollerthun A. , Fricke E. , Schärtl H. 
Published: November 2014

AbstractA three‐phased approach for governmental as well as internal company centers is suggested to stepwise improve and evaluate proposed concepts for innovations.The objective of this concept was to have a transparent, structured, and reproducible process to select the right innovative project in terms of political, economical, and technical objectives for funding by e.g. a governmental agency. A stepwise process and related methods, that cover technical as well as economical aspects (and related sensitivities) to come to a tentative decision which project to fund are proposed.Before discussing critical aspects of the proposed process, aerospace‐related examples will be presented to show how the process has been applied, and how different concepts were evaluated.