bluuebunny/crossref_metadata_2025_split huggingface dataset:
8.5.2 Systems Engineering Heuristics – Is there a need to innovate, integrate and invigorate?
Authors: Mar Brian W. , Morais Bernard G. 
Published: November 2014

AbstractThis paper reports the results of a survey to evaluate the current systems engineering heuristics and determine if there is a need to innovate, integrate and invigorate the existing set. By identifying the trends and needs of systems engineering heuristics, a research agenda for SECOE can be improved. This paper uses the Pragmatic Principles (DeFoe, 1993) as a bench mark for systems engineering heuristics and the INCOSE 2000 proceedings as the state of the art of engineering practice to identify the heuristics many systems engineers support. The results of this investigation indicates that there are heuristics that are generic for both product and product development systems (process), and others that are focused on product not process, but there is not complete agreement on any heuristic. The FRAT concept (Mar, 1991) is used as a framework to organize and simplify these heuristics.
2.6.4 Active Co‐operation Networks – Key to a Competitive Advantage in a Global Marketplace ?
Authors: Wieser Michael , Schulz Armin , Vollerthun Andreas 
Published: November 2014

AbstractIn recent years rapid developments in information technology have dramatically changed the availability of information. It is now almost possible to get any information at any place in the world at any time. The economy has adapted to these changes and will continue to do so in the future. To keep up with competitors strategic alliances can be observed in many markets. Virtual enterprises and communities are the consequence. Due to the globalisation of markets the economy is getting increasingly networked and consequently complex. It will be significant in future to analyse and model these processes and it must be clarified to what extent systems engineering methods/tools can be used to handle this complexity.The strategy how to initiate and scale modern networking is described on the basis of two projects in the European satellite business.
7.6.2 Completeness of Conceptual Models Developed using the Integrated System Conceptual Model (ISCM) Development Process
Authors: Gonzales Regina M. 
Published: November 2014

AbstractThere exists a semantic gap between developers and users of systems. Requirements engineering is addressing this gap by introducing requirements methods, techniques, and processes that facilitate greater understanding of the customers and users needs. Many of these methods and techniques rely on the analyst or developer to model the product domain. With the complexity of systems developed today, this can be a formidable task. These systems have multiple users with diverse needs and require the integration of multiple domains in order to develop them.Customers, users and developers are the stakeholders for a system. Increasing the communication and decreasing the semantic gap between diverse stakeholders are the aims of the Integrated System Conceptual Model (ISCM) Development Process. This process uses a combination of elicitation methods and techniques. However, the stakeholders create the initial models for the system based on their own mental models of a proposed system. This paper focuses on completeness indicators proposed in order to regulate the ISCM process.
7.6.4 Capability Dynamics: An approach to Capability Planning and Development in Large Organisations
Authors: Flint Shayne R , Boughton Clive V 
Published: November 2014

AbstractThis paper describes Capability Dynamics, a synthesis of system dynamics, control, agent based simulation and distributed systems techniques, which aims to increase the likelihood that decisions made throughout and at all levels of an organisation contribute in a coordinated way to satisfying the organisation's requirements and those of its stakeholders.The focus of Capability Dynamics is on the identification of systems that need to be developed, modified and retired within a whole‐of‐capability, and whole‐of‐life context of required capabilities and evaluation criteria. It is left to other research and existing systems engineering practice to improve individual systems within this context.
8.6.1 Project Kookaburra: Educating Systems Engineers Using Design of Unmanned Aerial Vehicles
Authors: Smith E. Price , Bollino Kevin , Rogers Anthony J. , DiSebastian John D. 
Published: November 2014

AbstractThis paper presents the results of an educational initiative to bring aircraft systems design into the systems engineering curriculum at the United States Air Force Institute of Technology. The project spans preliminary design, mission analysis, aircraft modification, test planning, flight testing and system analyses for a small multi‐mission unmanned aerial vehicle system. Educational and mission outcomes are presented.
1.7.2 System Approach of Electric Utility Restructuring in Developing Countries: An Outlook in Asia
Authors: Leeprechanon N. , Moorthy S.S. , David A.K. 
Published: November 2014

AbstractThe design of a suitable power market is a major concern, particularly for the deregulation of the electricity supply industry (ESI) in Western countries. This has led to a realization of the need for reform and competition in developing countries also. However, there are fundamental differences between the two groups of economies in the maturity of the ESI structure, economic priorities and the role of the state in development. This paper, therefore, synthesises a model of reform which is sensitive to these realities. Consequently, the outlook is different from the prevailing tendency to simply transpose experience from elsewhere. The core issue that we identify is the approach to the transmission system. The case of the Electricity Generating Authority of Thailand (EGAT) is used as the main reference point due to its medium size and orientation towards restructuring. In addition, short sections on Sri Lanka and China are included to broaden the relevance of the discussion.
3.7.1 Creating High Value Future Architectures
Authors: Parnell Gregory S. 
Published: November 2014

AbstractGovernment and commercial organizations have realized that system architectures (complex large‐scale systems of systems) are critical to their future success. Architecting involves many decision‐makers and stakeholders; significant future uncertainties; and complex value trade‐offs. System architects, systems engineers, and systems analysts must develop and use objective, credible, and traceable methodologies to create high value future architectures. This paper provides a process to develop a system architecting methodology to meet this need.
3.7.2 Discovering the Architecture for Product X
Authors: Ring Jack 
Published: November 2014

AbstractThis paper describes how the architecture for a high tech product was discovered by a work group of diverse individuals who had little prior grounding in systems engineering principles or methods. This report provides a running account of the iterative hypotheses and tests that enabled the traverse from problem situation to solution specification. The resulting architecture and rationale were understood and supported by all project members. The architecture differed significantly from pre‐project concepts but clearly simplified both the product and the product realization process. A companion infrastructure was defined, as well. A post‐project survey indicated that the client felt the effort was worth both the time and expense and saved them from several “bad ideas.”
3.7.3 The Architecture View Set in Action
Authors: Morgan Tara , Frank Rodger 
Published: November 2014

AbstractArchitecture Based Design™ (ABD™) is a system engineering design process being used at Lockheed Martin Management & Data Systems (LM M&DS). This process is based on the use of an Architecture View Set (AVS) to capture the executing architecture of a system This paper provides a case study of the use of the ABD™ process and the AVS to design and develop a system on a current program. These experiences are presented through a series of observations and conclusions about the impact of this methodology and its relationship to the following topics:

Incremental Development Cycle
Use of Composite Views
Power of the Meta‐CASE Tool
Customer Presentations
Requirement Traceability
Documentation Methods
Relationships between the Views
Executing vs. Construction Aspects
Test Program
3.7.4 Validating a Commercial Product Architecture
Authors: Adifon Leandre , Lentz V. A. , Lerner Bruce , Marvin Daryl J. 
Published: November 2014

AbstractCommercial products in existing industries have an architecture. The functional architecture is implicit from the domain, as envisioned by the founder of the company. The only representation of the functional architecture may be enveloped in the physical architecture. The physical architecture has evolved over time to keep up with innovation and changes in the marketplace. As technology is investigated and sometimes subsequently inserted, the occasion arises to more formally reassess the functional architecture and validate the evolved Physical architecture in regard to expanded functionality and new technology. Today, independent modifications in the various pieces of the product drive substantial changes in the physical architecture. This paper addresses the journey of one commercial company to validate the architecture of the flagship product. The methods and approach will subsequently be used with the other product lines. The goal is a modular architecture with standardized interfaces to enable significant decreases in time to market, and reduction in the cost of production and support. The paper addresses 1) the business drivers for taking the time and resources to do the validation, 2) the methods employed and 3) the plan for evolving the engineering and operations within the company to realize the advantages sought when starting the effort.
4.7.2 Getting to Requirements: The W5H Challenge
Authors: van Gaasbeek James R , Martin James N 
Published: November 2014

AbstractMost systems engineers have a clear idea on how to transform a set of top‐level requirements into detailed requirements that drive subsystem design and development. However, very few know an effective manner of “discovering” these top‐level requirements themselves. It is often assumed that they will “appear” from somewhere. This paper describes a generic W5H technique that works well in extracting the true requirements from various stakeholders. W5H is shorthand for What, Who, Where, When, Why and How. The W5H technique is a handy mental framework to assist the engineer in transforming the needs, wants, and expectations of various stakeholders into a cohesive and complete set of top‐level requirements.
6.7.3 Towards Modelling and Analysis of Internet Open Trading Protocol Transactions using Coloured Petri Nets
Authors: Ouyang Chun , Kristensen Lars Michael , Billington Jonathan 
Published: November 2014

AbstractElectronic Commerce (E‐Commerce) is a rapidly growing area with new companies entering the market place and existing companies moving their commercial operations onto the Internet. The Internet Open Trading Protocol (IOTP) is a standard being developed by the Internet Engineering Task Force aiming at providing an interoperable framework for E‐Commerce over the Internet. In this paper we use Coloured Petri Nets (CP‐nets or CPNs) to construct an executable model of the IOTP Deposit Transaction. Due to the formal semantics of CP‐nets, this CPN model constitutes an unambiguous specification of the Deposit Transaction and allows us to conduct a formal analysis of the Deposit Transaction. This initial analysis has already revealed minor deficiencies in the Deposit Transaction procedures demonstrating the benefit of applying formal methods for the specification and development of complex communication protocols.
7.7.4 A System Approach to the Conceptual Design of an Upgrade Mission Payload for Maritime Helicopters
Authors: Kusumo Raden , Sinha Arvind K. , Scott Murray L. 
Published: November 2014

AbstractThe global budget climate has laid restrictions on the design and development of new military aircraft to meet the demands of additional mission capabilities. To enhance mission capabilities, mid‐life upgrade of in‐service aircraft, involving placement of advanced technology mission systems onboard, is acknowledged as a cost‐effective option. To facilitate the mid‐life upgrade process, a “Decision Support System” is required to identify the state‐of‐the‐art mission systems that will provide the required mission capabilities. An “Integrated Decision Support System” (IDSS) that analyses the mission requirements holistically, to identify mission systems that enhance the capability of the aircraft is presented in this paper. A brief outline of the IDSS framework developed by a systems approach is presented initially, followed by a detailed discussion of the ‘Mission Payload Design’ (MPD) sub‐model. The MPD sub‐model prioritises the identified mission systems based on their relative dependence and degree of contribution in mission accomplishment, to formulate mission payload alternatives for aircraft upgrade.
9.1.1 An Experiential Approach for the Training of Systems Engineers
Authors: Fisher Jack , Terry Kathleen 
Published: November 2014

AbstractFor the last five years, the California Institute of Technology Industrial Relations Center has provided systems engineering training for engineers from the Northrop Grumman Corporation. The program has evolved over this period and is recognized by the participants and Northrop Grumman management as an effective means of training prospective systems engineers. The course includes seven class meetings over a period of six months with an instructor‐defined class exercise. The class of typically 24–28 students is divided into two teams. The exercise requires each team to develop a system with a number of pre‐defined steps that are described by the instructor tutorials. The exercise originates with an instructor‐written Operational Requirements Document and culminates with a student‐prepared Preliminary Design Review and life cycle cost estimate. The tutorial material prepares the students for each step in the system development process. Each 8‐hour, monthly class meeting involves a tutorial by the faculty as well as student team reports on their progress with the exercise.
9.1.2 Legacy Software Testing – A Current Methodology
Authors: Gibson Ralph D. , Chapman Michael D. 
Published: November 2014

AbstractIn the simulation world, software upgrade is more common than new development. Thus it is extremly important to ensure proper operation of of the simulation model as it is enhanced. The big question is how does one keep the current model operating correctly while adding new capabilities? The Model Development Team at the Air Combat Environment Test and Evaluation Facility, Patuxent River Naval Air Station, Maryland, has developed an approach that is useful in making sure that the current simulation model keeps its current capabilities operating correctly as well as testing any new capability that is added. The purpose of this paper is to present the approach used by the Model Development Team to answer the question put forth. This paper discusses the software development and maintenance criteria used as the overarching guide for testing. The testing process used and how this process ensures that the model meets the criteria is then given. Specific test examples and expected output are provided as a model testing approach. Finally, the future of development testing for the Model Development Team is presented.
9.1.4 Comparison of Residential Broadband Systems and Services
Authors: McNeill Ronald P. 
Published: November 2014

AbstractThis paper provides a high‐level overview of residential broadband technologies. First, the paper describes the two main broadband technologies currently offered in the consumer market: DSL (digital subscriber line) and the cable modem. Next, the paper provides a view on some of the factors that are generating demand for residential broadband. This includes bundled services, interactive television, HDTV, and telecommuting. Lastly, the paper touches on future residential broadband technologies such as fixed wireless services and fiber optics. The paper demonstrates that there will be a significant increase in demand for home broadband services over the next several years. As costs continue to decrease, new and better technologies will continually be developed and home broadband use will become ingrained in our daily lives.
9.1.6 Generation of a Service Language for the Resource Reservation Protocol Using Formal Methods
Authors: Villapol María E. , Billington Jonathan 
Published: November 2014

AbstractThe Resource Reservation Protocol (RSVP) is a signalling protocol, which transports and maintains Quality of Service (QoS) information along the path of a data flow. It is being modelled and analysed using a verification methodology proposed by (Billington et al 1986). The methodology includes a service and protocol specification. This paper is focused on the definition, modelling, and analysis of the RSVP service specification. A service language including all the possible service primitives sequences was also generated. It is being used as part of the verification process of RSVP. Also, this service specification will allow other resource reservation protocols to be developed that satisfy this service.
9.1.7 Prediction of SAP based ERP Systems Capacity Using Stochastic Processes and Spectrum Analysis
Authors: Zuniga Roberto B. 
Published: November 2014

AbstractThis paper presents an innovative approach to predict system resources consumption within an ERP production environment running SAP R/3 applications. It combines ‘Discrete Event’ modeling technologies with Digital Signal Processing (DSP) methodologies for analysis of stochastic (random variable described) phenomena. The approach consists in considering the samples collected by system monitoring tools as discrete stochastic signals representing system resources behavior. These signals are filtered and processed by Time – Frequency transformation algorithms to extract a set of sinusoidal mathematical sequences that characterize the periodicity of each signal. These set of discrete frequency components uniquely identifies system resources (CPU, Disk IO, etc) behavior as effected by the transaction been executed.
5.2.4 FRAT – A BASIC FRAMEWORK FOR SYSTEMS ENGINEERING
Authors: Mar Brian W. , Morais Bernard G. 
Published: November 2014

AbstractSystems engineering can be difficult to implement if the words and framework are not clearly understood by all parties involved. INCOSE has adopted a definition of systems engineering; yet a debate continues over what systems engineering is and how to do it. The authors have developed over a period of many years the FRAT framework for describing the process used to implement systems engineering for any task, the name for which is derived by the first letters of the series of words function, requirement, answer, and test. FRAT is based on the hypothesis that four views of a system are needed to completely define any system. These views are what it does (functions), how well the functions are performed (requirements), a physical or actual description of the system (answers), and verification and validation of the system when completed (tests). The FRAT framework has been validated by reviewing all the papers published at INCOSE proceedings. It is important to recognize that the system of interest (a product) is produced by another system (a production system). Both of these systems can be described by the four FRAT views when developing a shared vision of the development process as well as the product that is developed.
2.1.4 Use Case Development Integrated in a Systems Engineering Environment
Authors: Smith Darold K. 
Published: November 2014

AbstractThe ability to capture stakeholder interests early in a system's evolution is critical to successful deployment of the system over its lifecycle. The concept of capturing user functionality as use cases is beginning to be used in systems engineering. Most use case content development consists of the manual process of documenting use case information as text in a CASE tool or in a word processor.This paper describes one approach to integrating use case development in the systems engineering environment. Each element of the user‐defined use case template is an object in the SLATE1 database. The benefits include: capturing relations among user needs, use cases, requirements, architecture, implementation, product lifecycle, affected parties, and external CASE tools.The collaborative environment assures that all users work with current data. Custom reports and metrics allow tracking use case progress, issues, etc.
1.1.3 Heuristics in Planning for Advancing Technologies: a Comparison of Heuristics Used on the X‐33 Program vs. the Heuristics Used on the Apollo Program
Authors: Spurlock D. M. 
Published: November 2014

AbstractProjects in advancing technologies require planning like any project in any other field. Unlike most projects, those in advancing technologies will benefit from using architectures that are open and evolvable. By comparing the planning of the Apollo lunar landing and the X‐33 projects, certain heuristics can be identified to aid future project's planning. A basic set of heuristics can be identified to be used by projects that are part of an advancing technological field. This paper looks at heuristics from Apollo and X‐33 planning. This paper also presents results from a survey of current engineering planning and how the heuristics identified in the main body of this paper are or are not used in current engineering planning.
2.1.3 Applying Systems Engineering to Clinical Trials
Authors: Bamdad Julie A. 
Published: November 2014

AbstractThe clinical trials industry has remained largely untouched by the application of systems engineering principles, perhaps due to the intangible nature of its product. This complex and growing industry could benefit greatly from a more widespread application of systems engineering. Work in clinical trials Data Coordinating Centers (DCCs) includes managing unique tasks and complicated flows of communication, processes that systems engineering can improve. The focus narrows on one study group as a case study, as some systems engineering principles are explored and suggested applications of them are made that could improve workflow and alleviate problems.