Mission Critical System Development: Design Views and Their Integration--Version 2.0.

Hoang, Ngocdung; Karangelen, Nicholas E.; Howell, Steven L.

doi:10.21236/ada310022

Cited by 4 publications

(1 citation statement)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The ECS effort has identified five initial design capture views for specifying computerbased system design as summarized in Table 1: Informational, Functional, Behavioral, Environmental, and Implementation [2]. Three of these views-Informational, Functional, and Behavioral-are based on traditional specification and design methodologies.…”

Section: Setis Information Model Semanticsmentioning

confidence: 99%

Applying the system engineering environment to the reengineering process

Krasovec

Howell

1995

Journal of Systems Integration

Self Cite

View full text Add to dashboard Cite

Abstract. There is increasing motivation in both government and commercial enterprises to make the tools, methods, and information models common to modern system engineering environments available to support the reverse engineering and re-design of complex, computer-based systems. This paper reports on recent efforts to develop and validate a comprehensive system engineering environment which adequately supports both forward and reverse engineering processes. A key component of this engineering environment is the System Engineering Technology Interface Standard (SETIS). SETIS is composed of standardized engineering information models, data interchange mechanisms, and data access methods by which engineering and analysis tools in the Navy's Engineering Complex Systems (ECS) project are being integrated.We contend that SETIS is a viable pathway which can be exploited to enhance and bring added value to the reverse engineering process. In this paper we examine the content and granularity of the information models embodied in SETIS along with the information needs, capabilities, and products of ECS tools which are applicable to reverse engineering problems. Next, we evaluate two current reverse engineering activities relative to their compatibility with a SETIS-based engineering environment. Our evaluation has revealed that there is a design information abstraction threshold which must be reached before the data by-products of reverse engineering can be successfully encoded in SETIS design models and analyzed by the ECS toolkit. One of the case studies involves the translation of reai-time Ada software to an equivalent Elementary Statement Language encoding and the fabrication of abstracted software units. The other case study examines a system level reengineering methodology being applied to existing segments of a Naval command and control system. Both of these reengineering processes provide adequately abstracted design information from the legacy system which will support the use of models and analysis methods in the ECS engineering environment. Compatibility with system engineering environments such as ECS can be achieved by ensuring that the design extraction process from legacy systems yield process or program level functional, behavioral, and interface descriptions.

show abstract

Section: Setis Information Model Semanticsmentioning

confidence: 99%

Applying the system engineering environment to the reengineering process

Krasovec

Howell

1995

Journal of Systems Integration

Self Cite

View full text Add to dashboard Cite

show abstract

VERDICT: A distributed virtual environment for system engineering

Kuchinski

2000

Syst. Engin.

View full text Add to dashboard Cite

Abstract1 . This paper proposes a framework for the development of a distributed virtual interface (called VERDICT) for a system engineering development environment that (1) focuses on the role of the human in the system being designed, (2) focuses on the cognitive needs of the engineers using the development environment, and (3) facilitates the intended universality of the environment by relying on technologies that allow architecture independence.

show abstract

3.3.3 VERDICT: A Distributed Virtual Environment for System Engineering

Kuchinski

1998

INCOSE International Symp

View full text Add to dashboard Cite

Abstract1 This paper proposes a framework for the development of a distributed virtual interface (called VERDICT) for a system engineering development environment that (1) focuses on the role of the human in the system being designed, (2) focuses on the cognitive needs of the engineers using the development environment, and (3) facilitates the intended universality of the environment by relying on technologies that allow architecture independence. VERDICT stands for Virtual Environment for Remote Design Integration and Configuration Testing. Its purpose is to provide a distributed virtual interface to a system engineering environment for the design of complex systems. Principal among its goals is the organization of information through the development of a taxonomy of the types of knowledge representations, or cognitive media, used in system design. Related to this goal is the determination of how these cognitive media are best represented by physical media (text, graphics, animation, sound, etc.). Another goal is implementation transparency, through the utilization of enabling technologies such as Java and CORBA.

show abstract

Mission Critical System Development: Design Views and Their Integration--Version 2.0.

Cited by 4 publications

References 0 publications

Applying the system engineering environment to the reengineering process

Applying the system engineering environment to the reengineering process

VERDICT: A distributed virtual environment for system engineering

3.3.3 VERDICT: A Distributed Virtual Environment for System Engineering

Contact Info

Product

Resources

About