5.7.2 The Data Standard AP‐233: An Invigorator for Global Systems Engineering

Self Cite

Abstract. SysML is a new standard language for system modeling, built on top of the new version of the popular UML and tailored for the specific needs of systems engineers. In this paper we present a brief overview of the SysML along with observations on the language and some challenges facing the systems engineering and tool vendor community.The purpose of the paper is not to criticize the outcome of the SysML standard but to evaluate its strengths and weaknesses and identify areas for future improvement.

Section: Product Data In the Enterprisementioning

confidence: 99%

2.3.1 SysML – an Assessment

Herzog¹,

Pandikow²

2005

Self Cite

“…More detail to the model, philosophy and evolution of the AP-233 design can be found in (Johnson, 1999;Johnson et al, 1999;Johnson et al, 2000;Pandikow et al, 2000;Johnson & Herzog, 2001;Herzog & Torne 2001). Scott et al (2002) have shown that AP-233 is well suited as a generic format for holding systems and software requirements and transferring them between dissimilar tools.…”

Section: Ap 233mentioning

confidence: 99%

4.3.3 An Architecture for an Intelligent Requirements Elicitation and Assessment Assistant

Scott

Cook

2003

Requirements engineering is crucial to the success of the system engineering process. Unfortunately, while current generation tools provide good support to requirements capture, they offer only modest assistance for cognitive tasks such as requirements assessment. This paper opens by introducing the attributes needed to define a requirement and the qualities of good requirements and requirements sets. An argument is then presented for the inclusion of artificial intelligence to perform requirements analysis and this is followed by a review of intelligent requirement analysis tools identifying the need for enhancements. From this basis, the paper describes the architecture of an intelligent requirements elicitation and assessment assistant that is currently under construction.

“…In the authors view the projects were successful in components 1-3 in the sense that it was demonstrated that the information model along with supporting STEP parts could be used to exchange information between a number of commercial and proprietary tools (Johnson, 2001). The validation scenarios executed included data exchange between tools used in the same phase in the engineering process (Statemate ↔ Teamwork), and tools used throughout the engineering process (Labsys, StP, Demanda, with Doors used as a PDM system).…”

Section: Introductionmentioning

confidence: 99%

6.3.3 A PS covering Functional Architecture support in SEDRES developed drafts of AP‐233

Herzog

2004

Self Cite

Abstract. This paper takes a data exchange perspective on the multitude of methods proposed for capture of system functional architecture. The particular focus of the paper is the different approaches proposed for representing the control flow view of a model. We show that an extended Petri-net notation can be used to capture control flow for methods like FFBD, behaviour diagram and also UML activity diagrams. An example is used to illustrate how the SEDRES developed drafts of AP-233 can represent FFBD control flow. The paper also contains a general discussion on AP-233 and the underlying non-functional requirements for a data exchange standard.