bluuebunny/crossref_metadata_2025_split huggingface dataset:
An Interface Control Approach to Land‐Use Management
Authors: Carson Ronald S. 
Published: November 2014

ABSTRACTAn interface control approach is formulated for land‐use management that relies on establishing and maintaining interface conditions rather than defining the content of the activity on the land. This is analogous to the system engineering concept of constraining the interface boundary conditions rather than specifying the detailed design. An application to regulating wetlands is examined. This approach has the possibility of producing relatively more stable land‐use regulations by eliciting the intent behind a regulation.
Development Of Laboratory Capabilities For The Integration Of Global Positioning Satellite (GPS) System Onto The F‐14 Aircraft
Authors: Chan Hin K. , Hugh Robert , Krinsley Brian 
Published: November 2014

ABSTRACTThis paper discusses the systems approach used in the design and development of laboratory test capabilities used to integrate GPS capabilities onto the F‐14 aircraft. Modifications made to the existing simulation/stimulation capabilities, radar target generators and airframe wiring will be discussed as well as the installation and alignment of a three axis tilt table, the design of a stand‐alone workstation, and the use of COTS test tools.
System Modeling and Possible Applications for the Social Sciences
Authors: Koehler Andrew , Pelmulder Susan , Stone Adam 
Published: November 2014

ABSTRACTSystem Engineering tools have been used extensively to model the technical characteristics of large systems or processes. However, little use of these tools has been made in the social sciences, and the modeling of the social factors that contribute to design choices—in the case of systems that involve political processes—remains relatively crude. This paper discusses the efforts of the Center for Nuclear and Toxic Waste Management, University of California, Berkeley to employ system design tools as part of social science research into US surplus plutonium disposition options.
Overcoming Problems in the Development of an Automated Car Park System by Introducing Systems Engineering Methods
Authors: Harzenetter Florian , Beutler Jörg , Negele Herbert , Fricke Ernst 
Published: November 2014

ABSTRACTSince 1992 Maurer Söhne is developing an automated car park system and now has built a prototype for the City of Augsburg, 60 km west from Munich. During this project problems arose, especially with respect to changes. Therefore, Maurer Söhne started to implement systems engineering methods to overcome those problems in the planned serial production of the automated car park system. This paper is not a glorification of a development process, instead it describes the problems and their causes, what we called “management by Beckenbauer”, during the development phase. Furthermore, the paper shows how Maurer Söhne started to solve one of the main problems, i.e. to manage changes, by implementing special systems engineering methods.
The Science of Railway Systems Engineering?
Authors: Williams John S , Allan Jeff , Jin Jenny Q 
Published: November 2014

ABSTRACTIt is described how a scientific approach to railway systems engineering is needed to lead to a modelling development plan coupled closely to the system development and test programme. This coupling is best achieved using databased information which is sourced both from the design process and from the tests and trials conducted during implementation. The final models and databases need to be not just a record of the project development, but to form the basis for the planning of future operations and railway updates.
MODELING AND SIMULATION BASED SYSTEM INTEGRATION APPROACH
Authors: Huang Paul , Kar Pradip , Kennedy Alan , Kato Hiroko 
Published: November 2014

ABSTRACTThis paper describes a modeling and simulation (M&S) based approach to provide life cycle support for the Bradley Fighting Vehicle (BFV) M2A3. The BFV A3 is being developed under an Engineering and Manufacturing Development (EMD) program at United Defense LP (UDLP). The BFV A3 Upgrade program incorporates lessons learned in the Desert Storm Operation. Upgrades are primarily in the area of fire control, electronics and software.
ENGINEERING OF INTELLIGENT, COMPLEX ADAPTIVE SYSTEMS USING AN AGENT‐BASED ARCHITECTURE
Authors: Clymer John R. 
Published: November 2014

ABSTRACTA methodology for bringing intelligent, Complex Adaptive Systems (CAS) into being is discussed, and the requirements for such intelligent systems are summarized. An agent‐based system architecture is proposed that will satisfy the requirements for such an intelligent system. A facilitator agent that manages communication, coordination, and collaboration is proposed as a part of this architecture. A goal‐directed behavior process is included as part of the facilitator agent to satisfy many of the intelligent system requirements.
Spreadsheet Aided System Engineering and Optimization
Authors: Mincer Tom R. , Hooper David M. 
Published: November 2014

ABSTRACTThe Excel™ spreadsheet has become a valuable, powerful engineering tool that now provides strategic capabilities to:
create graphical user interfaces (GUIs)
command other languages like FORTRAN and C through Dynamic Link Libraries (DLLs)
control an integrated object oriented programming language called Visual Basic Applications (VBA)
command databasesThe GUI capability of Excel allows the system engineer to create windows like applications (icon driven) with minimum effort. This GUI capability enhances system information presentation and provides the means to manage system information flow efficiently. Excel allows a design team to redefine the “back of the envelope calculation.” This is accomplished by interfacing with other languages such as FORTRAN and C, its own programming language VBA, and an optimization tool called Solver. With the modular, platform nature of Excel, engineers can now apply the system engineering process and develop unique applications devoted to their project team needs.
HOW DO YOU MODEL A SYSTEM ?
Authors: Plastow Ian 
Published: November 2014

ABSTRACTIn answering the question How do you model a system? this paper considers the requirements for modelling of a system in the context of the systems development lifecycle. It examines the issues that have to be resolved for a systems model particularly those related to integration (both horizontal and vertical). A means of satisfying the wide ranging requirements of a systems model is proposed. Neither the proposed requirements nor the means of satisfying them are intended as definitive but are anticipated and intended to stimulate further discussion.
A Framework for Research Into Model‐Driven System Design
Authors: Lykins Howard 
Published: November 2014

ABSTRACTThere is a pressing need for research into the use of machine interrogable models for requirements analysis, design, integration, testing, and management at all levels of systems and software engineering. This paper describes a candidate framework for research into model‐driven systems engineering. The framework is a recently published process for integrated systems and software‐level engineering of software‐intensive systems, described in terms of management and development activities and associated information. To show how the process can serve as a research framework, this paper selects a subset of the activities and information flows, discusses how modeling relates to them, and raises some example issues.
Systems Engineering Specification Techniques
Authors: Ghahramani Bahador 
Published: November 2014

ABSTRACTThe primary purpose of the Specifications Techniques Supported by CASE Tools (STCT) is to improve the effectiveness of Systems Engineer's (SE) efforts in design and development processes. These techniques help SE's by guiding them through the system's design and development (D&D), architecture, documentation, requirements, and verifications phases. This practice is a practical and efficient alternative to the traditional procedures of developing specifications, in which the specifications developed do not necessarily follow modern engineering approaches. STCT applies to both systems and software specifications as well as firmware and high‐level hardware requirements.
An Effective Approach To System Integration: A Comprehensive Checklist
Authors: Hyer Scott A. 
Published: November 2014

ABSTRACTSystem integration is one of many ambiguous terms used in high technology system development communities which needs to be better understood and recognized. Its definition often depends on one's point of view and purpose. However, it must be recognized that system integration is an idea which must drive the development process from start to finish. The influence of system integration must carry significant weight at the beginning during requirements development and system design as well as through the detailed design, build, and test activities as more traditionally recognized. This paper attempts to treat system integration as a more universal activity by first defining it from different aspects and then by presenting an approach which can be effective in a wide variety of situations. The approach is offered in the form of a checklist, which tends to be more easily visualized, understood, and incorporated into a plan of action. This paper also attempts to remain independent of particular technology applications and business areas to maximize its applicability.
REDESIGN COST AVOIDANCE USING SYSTEM ENGINEERING
Authors: Helm Jim , Cantrell R. T. 
Published: November 2014

ABSTRACTA system engineering approach was used for development of the Motorola space‐based cellular network called IRIDIUM1. Significant cost reductions were realized using requirements analysis and management along with system engineering team processes. Statistics show a 40 to 1 reduction in development engineering time due to team requirements inspections. Due to their general nature, these system engineering processes are easily transportable to any project with a development phase.
The Vortex Principle: Systems Engineering with a Twist
Authors: Jorgensen Raymond W. 
Published: November 2014

ABSTRACTMany models have been used to describe the processes that engineers should be following to provide effective engineering solutions for today's problems. Each model has drawn attention to the fact that engineering requires a disciplined approach to problem resolution. However, these models are failing to capture the concepts of information abstraction as it applies toward effective system decomposition. Appropriate application of abstract reasoning, however, is necessary for effective communication of a system definition. This paper presents an engineering process model that depicts the iterative flow of requirements and design along a vortex that follows an appropriate breakdown of abstracted system components.
Considerations in Developing Originating Requirements
Authors: Buede Dennis M. , Charbonneau Steven 
Published: November 2014

ABSTRACTThis paper addresses the issue of what types of analysis might be best for analyzing the interaction the system under question with relation to its external systems during the requirements development process. We examine process or functional modeling as well as behavioral or state modeling. The effort employs academic case studies and a survey of practicing systems engineers.
Report on Development of ISO Standard 15288 System Life Cycle Processes
Authors: Lake Jerome G. 
Published: November 2014

ABSTRACTSince the late 1980s there has been a focused effort to produce standards, guides, and models that will enhance the development of systems. With the deemphasis of military standards within the US Department of Defense, these efforts by US and international standard bodies have been further stimulated.In 1994 the US published interim standard EIA/IS 632, Systems Engineering, and IEEE 1220 Trial‐Use Standard, Application and Management of the Systems Engineering Process. The International Organization for Standardization (ISO) has also been creating a series of standards and guides. ISO/IEC 12207, Software Life Cycle Processes, is one such standard published in 1995. Additional ISO guides and national implementations standards pertaining to 12207 are under preparation. Also in 1995, the same ISO working group that developed 12207 has undertaken the development of a system standard to be known as 15288, System Life Cycle Processes. And in 1996, the United Kingdom Defence Evaluation and Research Agency (DERA) prepared a draft guide with a system model that provides an excellent framework for engineering a system.This paper puts these and other efforts into perspective. The focus is on the 15288 development.
A Business System Engineering Model Architecture
Authors: Tronstad Yngvar D. , Peterson Jan 
Published: November 2014

ABSTRACTThis paper describes a Business System Engineering (BSE) approach to Information System Reengineering which can be applied to the Year 2000 problem as well as the more strategic migration from legacy computer systems to client server environments. The BSE is founded on proven System Engineering (SE) principles where changes in Information Systems (ISs) are driven by business requirements.
Development and Implementation of a Systems Engineering Process
Authors: White Paul , Tufts Robert , Treadwell Terry , Schier Jim , Reynolds Patti , Nolte Jerry , Newbern Dave 
Published: November 2014

ABSTRACTWe have developed a standard systems engineering process for TASC, and have begun implementing that process on systems engineering projects. We have found the standard systems engineering process to be a very useful tool in executing our work.
Applying Programmatic Risk Assessment to Nuclear Materials Stabilization R&D Planning
Authors: Kenley C. Robert , Hoozer S. Alenka Brown‐Van 
Published: November 2014

ABSTRACTA systems engineering approach to programmatic risk assessment, derived from the aerospace industry, was applied to various stabilization technologies to assess their relative maturity and availability for use in stabilizing nuclear materials. The assessment provided valuable information for trading off available technologies and identified the at‐risk technologies that will require close tracking by the Department of Energy (DOE) to mitigate programmatic risks.
Risk Management Implementation in a Product Team Environment
Authors: Elam Rudy , Kohrs Bob 
Published: November 2014

ABSTRACTThe implementation of a project‐wide risk management effort, in a project environment which uses product teams as the principal organization structure, requires a special management approach for effective results. Discussed herein are the practical experiences encountered in applying risk management to a two billion dollar wind tunnel design and construction project with a multiple set of project teams differentiated by technology specialties, corporate cultures and widely dispersed geographical locations. Lessons learned are summarized for use in future applications of risk management in a complex multidimensional project matrix environment.
Enhancing Teamwork with Cross‐Product Teams (CPT's)
Authors: Martin James N. 
Published: November 2014

ABSTRACTIntegrated Product Teams (IPTs) are all the rage now. However, teamwork can be more effectively implemented on development projects if Cross‐Product Teams (CPTs) are also used. The Systems Engineering Process cannot be performed well in a vacuum. It requires the right people, the right organization for those people, and the right functional design disciplines involved (e.g., software, mechanical, circuit card, logistics, ASIC/FPGA, microwave, interconnect assemblies, and test equipment). It also requires the proper timing with regard to when the different “levels” of the system architecture are defined and when the related functional design disciplines are brought to bear. This paper describes the programmatic framework within which the Systems Engineering Process should be performed. This framework involves the system breakdown structure (or product hierarchy), the organizational breakdown structure (or project teaming chart), and the project schedule.
A Sixth Discipline For Future Awareness
Authors: Hall Elaine , Gorsuch Thomas 
Published: November 2014

ABSTRACTWhat are the disciplines required to successfully manage and develop software systems in today's fast‐paced world? This paper describes a sixth discipline for future awareness—reasoning about possibilities. The current model of software development is based on an adaptation of the Deming model of process optimization. This adaptation is lacking a known discipline that is essential to software‐systems engineering. We develop the sixth discipline that extends the Deming model by adding the ability to discover risk and opportunity. To demonstrate the utility of the six‐discipline model, we describe the distribution of risk‐management practices to the six disciplines. Future awareness improves the current model of software‐system development by providing the capability to manage a future full of change and uncertainty.
Development Of A “Systems Engineering” Organization
Authors: Jackson William N. 
Published: November 2014

ABSTRACTOrganizations develop and cultures change over time. For an organization to be successful over the course of many years, strong foundations must be established. A properly defined and implemented Strategic Plan can provide a strong foundation. A prime example of a solid foundation is the Constitution of the United States. It provides guidance to a large diverse populace, permits modifications, is continuously being monitored and has been fairly successful for over 200 years. The US Constitution could be considered a “Strategic Plan”, developed by the first US Systems Engineers, our founding fathers!
SYSTEM INTEGRATION AND TEST IN INTEGRATED PRODUCT AND PROCESS DEVELOPMENT (IPPD): ENGINEERING OUT THE SURPRISES{PRIVATE}
Authors: Roe Charles L. 
Published: November 2014

ABSTRACTSystem integration is the process of assembling and evaluating a product after component design and development has been completed. This consists of interfacing and integrating the subassemblies and verifying that they perform according to the top‐level specifications. Since system integration is where the system comes together, its significance and importance should be readily apparent to the systems engineer, who must work the interfaces diligently during component development and establish lines of communication among the development teams to ensure that the finished product works as planned when tested against the system requirements.
Joint Development Teams in Action: Government and Industry Perspectives
Authors: Kollmorgen Leland S. , Terry William S. 
Published: November 2014

ABSTRACTMany organizations are embracing development of new systems or products through the use of integrated teams. Although clearly the direction of the future, there are some challenges along the way particularly when the new organizational ideas are inserted into development programs which are already in progress. This paper describes an integrated team environment which is currently being used to develop a complex new weapon system for the U.S. Navy. The implementation of this team environment can be used as a useful case study for others embarking on similar undertakings as both positive and negative aspects of the program team environment are discussed as well as a summary of lessons learned. This paper examines the team approach from both the position of the government and that of the prime contractor.
Important Skills and Knowledge to Include in Corporate Systems Engineering Training Programs
Authors: Watts Jerry G. , Mar Brian W. 
Published: November 2014

ABSTRACTThis study identifies the skills and knowledge that companies consider important for systems engineers to have and determines the amount of training offered by the companies to develop the same skills and knowledge. A survey of companies with training programs for systems engineers was administered and identified critical skills and knowledge to be basic problem solving, development and management of requirements, teamwork and communication, and system optimization. The amount of training offered to develop these skills and knowledge varies considerably from company to company and does not correlate with the emphasis the company places on the same skills and knowledge.
Systems Engineering Process Help Window
Authors: Grady Jeffrey O. 
Published: November 2014

ABSTRACTTraining accomplished closest to the need best serves that need. Most systems engineering training opportunities, where they do occur, are too far removed in time from the need for that training. Commonly, good external training opportunities cost more than we can afford to spend and are not scheduled for our convenience but rather for broader market demands. The combination of these factors act to make it very difficult to progress rapidly in improving one's skills and knowledge in this field. This paper offers a system engineering organization a way to parlay a prior investment in networking and systems engineering process definition into an affordable solution for this problem. The solution offered also permits the use of a simple generic enterprise systems engineering process manual by providing the detailed how‐ to information in the form of just‐in‐time training materials linked to the process manual.
Covert SE: Teaching SE in a Disciplinary Context
Authors: Maier Mark W. 
Published: November 2014

ABSTRACTMost INCOSE members agree, systems engineering is not just for systems engineers. But if systems engineering belongs in the disciplinary engineers toolkit, how should it be taught? This paper describes the authors observations in teaching systems engineering within a disciplinary context, and in particular in trying to make it a normal part of that disciplinary practice. Thus “covert SE” refers to the use and teaching of systems engineering methods without calling them by that name. In the authors experience systems methods apply to disciplinary engineering, but their teaching and application is not simple and is not without problems. The persistent nature of some of the problems suggests that the remedy is only partially in better materials, but also partially in rethinking the value of certain methods.
A Case Study for Teaching System Requirements Analysis
Authors: Gonzales Regina M. , Johnson Eric 
Published: November 2014

ABSTRACTThis paper presents an analysis of a semester course in System Requirements Analysis taught at the Klipsh School of Electrical and Computer Engineering at New Mexico State University. A real‐world model for product development was used with a life‐sized project. Methods and theory for product development were taught on an as needed basis. The lessons learned and insights gathered are presented.