摘要:

AbstractIn an Integrated Product Team environment, the systems engineering focus can be diluted unless specific steps are taken to focus the key people working on each team, and to improve their understanding and teamwork. Team Launches and Team Workshops have been created to educate teams just coming under contract and ongoing teams, respectively. The workshops teach team techniques in a structured, facilitated setting, over a two‐ to four‐day period, during which teams concentrate on establishing system and project goals, roles, responsibilities, and plans. This paper describes the agendas and processes involved in producing Team Launches and Team Worksh

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1995.tb01835.x

年代:1995

数据来源: WILEY

摘要:

AbstractTheory is one thing; practicality is another. Selling a requirements tool is one thing; using it is another. Here actual experiences in requirement management using three automated toolsets–the Simple Tested Available Requirement Tracer (START), Teamwork and the Cowen Utilities, and R‐Trace and Utilities‐are described in some detail. These toolsets range from table‐document referencing systems to a full centralized database requirement text system. All were used through one or more revisions to top level requirements and all were successful to a degree.Topics include training; requirement identification/marking, allocation, and flowdown verification; responsibility segmentation; and spec and analysis document generation and control.Brief comments are also given on experience with eight other t

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1995.tb01836.x

年代:1995

数据来源: WILEY

摘要:

AbstractIn the DOD, eighty percent of the life‐cycle cost of a software‐intensive system is for maintenance, and the cost of fixing software increases by an order of magnitude as it is passed from developer to maintainer. Much of the requisite knowledge about the system's mission, software structure, and maintenance tool set and procedures resides with the developers of a software‐intensive system. While some of this knowledge may actually be documented, it is seldom readily accessible and software maintainers must painstakingly rediscover it. To reduce the learning curve among software maintainers and the associated life‐cycle costs for specific systems, new software documentation approaches must be developed.This paper describes the HAC/RMPE Software Maintenance Tutor, a multimedia prototype which has proved effective in capturing system‐specific developer knowledge in a form that is useful to the maintainers. The tutor was built for the Higher Authority Communication/Rapid Message Processing Element (HAC/RMPE) and has been in use since September 1993 as a means of familiarizing new personnel with the HAC/RMPE software. New materials are continually being added. The tutor combines elements of a training system and an on‐line performance aid, and represents a unique approach for supplementing the software maintenance training process.The HAC/RMPE Tutor shows promise for filling a critical gap in the training of software maintainers and thereby reducing the overall system life‐cycle cost. It also represents a generic form of multimedia documentation which has applications in many

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1995.tb01837.x

年代:1995

数据来源: WILEY

摘要:

AbstractSustaining a competitive advantage in the global marketplace is a continuous challenge. Fast paced changes in technology, re‐engineered processes, revolutionary acquisition reforms, and highly sophisticated enabling techniques and toolsets are impacting our business. Without a proactive approach, it is easy to fall behind or “get off track”. Well‐defined roadmaps are needed to guide growth and change. While many businesses today develop business and technology strategies, these are not enough. ASystems Engineering Core Competency Strategyis equally essential to engineering organizations who will remain competitive in the next decade. This paper presents the key elements of this strategy, including recommendations for its development and use, and lessons learned based on a decade of exp

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1995.tb01838.x

年代:1995

数据来源: WILEY

摘要:

AbstractThis paper describes an architecture study for a system with the objective of developing a corporation's core competence in Systems Engineering. The study focuses on people as the key resource to be leveraged upon in order to achieve this objective. A system called thePeople Systemis postulated and defined by applying a tailored version of the Systems Engineering process.

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1995.tb01839.x

年代:1995

数据来源: WILEY

摘要:

AbstractThe Systems Engineering (SE) department at Space Systems Division of Rockwell is responsible for providing qualified Systems Engineers to all of the division's programs. Our training program addresses both immediate and long term skill needs. Immediate skill needs are developed with just‐in‐time in‐house training and on‐the‐job training. Our long term SE training program is integrated with SE career planning so individuals can identify specific types of training they need to achieve their long term career objectives. In addition, we monitor the effectiveness of the SE training to continuously improve it. Our training program consists of four basic elements: (1) an internal SE How‐To course to teach basic principles, (2) SE tools training, (3) on‐the‐job‐training (experience), and (4) formal degree SE programs from l

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1995.tb01840.x

年代:1995

数据来源: WILEY

摘要:

AbstractThe Aerospace Corporation sponsors in‐house research to enhance and extend the corporation's core competencies. The objective of one Aerospace Sponsored Research (ASR) was to develop new concepts for systems engineering, consistent with Integrated Weapon System Management (IWSM)/ Integrated Product Development (IPD) environments, by addressing methodology, guidance and training, and computer‐aided tools. The ASR had five primary objectives including defining an Systems engineering/ Configuration Management (SE/CM) methodology, developing guidance and training, investigating computer‐aided SE/CM tools, maintaining Aerospace role introducing SE/CM concepts to the Space and Missile Systems Center (SMC), and ensuring cross‐information flow of lessons learned between SMC System Program Offices (SPOs) and external customers. Significant accomplishments were made toward satisfying each of the stated objectives, especially achieving the opening of an operational SMC IPD

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1995.tb01841.x

年代:1995

数据来源: WILEY

摘要:

AbstractSome basic lessons learned, some “heresies,” and some causes of requirement denial are presented with the goal of providing information and food for thought for persons interested in designing requirement management systems. These are based upon practical experience of the author and others.One of the major lessons learned is the advantage of the use of a limited number of analysis documents to control derived, implied, or budgeted requirements. A layered schema made up of alternating specification (hardware/software/process/test) layers and analysis layers has proved ideal for handling all types of requirements.The heresies are some challenges to current strongly held beliefs. Sample heresy is “Just because we can't test it doesn't mean it's not a requirement.”Requirement denial is something like, “That's not a requirement that's just an algorithm we're going to use to meet a requirement.” (The other side of the argument is “If you gotta do it, it's a

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1995.tb01842.x

年代:1995

数据来源: WILEY

摘要:

AbstractThe Department of Defense Systems Management College uses the Stored Energy Ground Vehicle Simulation (“Mousetrap”) to train future program managers in the application and power of concurrent engineering and the systems engineering process. The simulation has evolved over the past seven years into what we believe to be a world class concurrent engineering simulation, which additionally provides the military officers and DoD civilians a critically important industry perspective.Each student integrated product team performs the role of a defense contractor competing against other student “companies” in their quest for the single follow‐on production contract to be awarded after completion of the acquisition development cycle and a government supervised competitive “run‐off”. They respond to a government request for proposal, negotiate a contract and spend time over 14 weeks developing a life cycle balanced system, expending and accounting for labor and actual government funds for materials. They must conduct three acquisition phase based technical design reviews presented to an integrated government program office, and subsequently build and field a compet

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1995.tb01843.x

年代:1995

数据来源: WILEY

摘要:

AbstractThis paper clarifies the value of using state‐of‐the‐art systems engineering tools (SETs) in the classroom, both at the undergraduate and graduate level. The goals for using SETs in the classroom as well as the lessons I have learned from trial and error experiences while trying to use them effectively. These lessons learned are based upon my experiences using DesignIDEF (Meta Software), RDD‐100 (Ascent Logic), and CORE (Vitech Corporation) over the past four years in the classroom and on research projects with students. I conclude that the benefits of this activity far exceed the costs (which are not inconsiderable) and that each SET must be approached uniquely in designing classroom act

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1995.tb01844.x

年代:1995

数据来源: WILEY