UMLTM for Systems Engineering RFP
RFP:
Refer to Chapter 6 and Appendix A.2 of
the RFP for specific information on UML for SE. The other sections of the
RFP provide general information for submitters.
UML for Systems
Engineering RFP - ad/03-03-41 (28 March, 2003)
Objectives of This Request For Proposal (RFP):
This Request for Proposal solicits submissions that specify
a customization of UML™ for Systems Engineering (SE). The customization of
UML for systems engineering is intended to support modeling of a broad range
of systems, which may include hardware, software, data, personnel,
procedures, and facilities.
The customization of UML for SE should support the analysis,
specification, design, and verification of complex systems by:
·
capturing the systems information in a precise and efficient
manner that enables it to be integrated and reused in a wider context
·
analyzing and evaluating the system being specified, to
identify and resolve system requirements and design issues, and to support
trade-offs
·
communicating systems information correctly and consistently
among various stakeholders and participants
A UML-based language for modeling systems will support the
exchange of analysis, specification, design, and verification information
using standardized notations and semantics that are understood in precise
and consistent ways. This will improve communication among people who
participate in the systems development process and promote interoperability
among tools that support this process. The language may also establish a
common modeling framework that can be further customized to meet specific
needs. The use of UML as a base language will extend the user skills, tools,
and knowledge that currently exists to additional users.
The customization of UML for systems engineering is being
closely coordinated with a related ISO STEP effort known as AP-233, which is
defining a data interchange standard for systems engineering. The
combination of these two efforts is expected to provide a comprehensive
framework for the exchange of systems information using standardized
notations and semantics.
To the degree that schedules permit, UML for SE should be
based on adoption in progress for a UML 2.0 specification.
The following are the references referred to in Section
6 of the RFP:
6.3 Relationship
to Existing OMG Specifications
6.3.1
Unified Modeling Language (UML™)
·
Unified Modeling Language (UML™), Version 1.4
(formal/01-09-67)
·
Unified Modeling Language (UML™), Version 1.5 (ptc/02-09-02)
(This version of UML is currently being finalized and includes the
specification for Action Semantics.)
6.3.2
Meta Object Facility (MOF™)
·
Meta Object Facility (MOF™), version 1.4 (formal/2002-04-03)
·
XMI Metadata Interchange (XMI®),
version 1.2 (formal/2002-01-01)
·
XMI Metadata Interchange (XMI®),
version 2.0 (ptc/02-06-03)
·
UML Human-Usable Textual Notation (HUTN) (ptc/02-12-01)
(This specification is currently being finalized, and provides additional
capabilities for text-based interchange of UML and MOF models.)
6.3.3
UML 2.0 Requests for Proposal
·
UML 2.0 Infrastructure RFP (ad/00-09-01)
·
UML 2.0 Superstructure RFP (ad/00-09-02)
·
UML 2.0 OCL RFP (ad/00-09-03)
·
UML 2.0 Diagram Interchange RFP (ad/01-02-39)
·
MOF 2.0 Core RFP (ad/01-11-14)
·
MOF 2.0 XMI Mapping RFP (ad/01-11-13)
·
MOF 2.0 Query / Views / Transformations RFP (ad/02-04-10)
6.3.4
UML Profiles and Metamodels
·
UML Profile for Schedulability, Performance, and Time (ptc/2002-03-02)
·
UML Profile for Modeling QoS and FT Characteristics and
Mechanisms RFP (ad/02-01-07)
·
UML Profile for Enterprise Distributed Object Computing
(ptc/02-02-05)
·
SPEM Software Process Engineering Metamodel (SPEM), Version
1.0
(formal/2002-11-14)
·
UML Testing Profile RFP (ad/01-07-08)
·
Business Process Definition Metamodel RFP (bei/03-01-06)
·
Business Rules in Models RFI (ad/02-09-13)
6.2 Related
Activities, Documents and Standards
OMG Systems Engineering
Domain Special Interest Group (SE DSIG),
6.2.1
International Council on Systems
Engineering (INCOSE)
INCOSE is an international not-for-profit membership
organization that develops and promotes the system engineering approach to
multi-disciplinary product development. It worked with OMG to help launch
the SE DSIG initiative, which held its kickoff meeting in September, 2001,
and is helping to coordinate UML for SE-related activities with ISO and
other groups. It also helps to develop, maintain awareness, and provide
review for model-driven approaches within the systems engineering community.
6.2.2
ISO STEP AP-233 Effort
The SE DSIG effort is closely aligned with the on-going ISO
AP-233 standard activity. AP-233 is focused on developing a data interchange
standard for systems engineering, which is intended to provide a neutral
data format to exchange systems engineering information among tools. The
AP-233 project is a working group of ISO TC-184 (Technical Committee on
Industrial Automation Systems
and Integration), SC4 (Subcommittee on Industrial Data Standards), and is
part of the larger STEP effort, which provides standardized models and
infrastructure for the exchange of product model data. The result of this
effort will be part of the existing ISO 10303 standard that will provide an
“Application Protocol” for Systems Engineering. One of the joint SE DSIG and
AP-233 tasks is the development of the Systems Engineering Conceptual Model,
which is intended to help align the requirements for UML for SE and the
AP-233 data interchange standard.
6.2.3
Requirements Analysis for UML for SE
This document (Version 0.4 dated November 12, 2002) was used
as a basis for analyzing the various sources of requirements for UML for SE,
for identifying perceived issues regarding gaps in UML 1.x related to
systems engineering, and for exploring potential solutions for UML for SE.
6.2.4
SE Terms and Definitions
The UML for SE Definitions List provides a self-consistent
set of systems engineering terms and definitions that are referenced in the
requirements section of this RFP. This list defines many of the specialized
systems engineering terms used in this RFP and appears under the SE Terms
and Definitions heading on the UML for SE RFP page. A core subset of these
definitions is included in the glossary in Appendix A.2. In addition, the
UML for SE RFP page identifies other sources of definitions, including
industry standard definitions, the definitions in the semantic dictionary
that accompanies the SE Conceptual Model, and definitions from the UML
specification. It is recognized that continued effort is required to fully
harmonize all of these terms and definitions with each of their sources,
including definitions used by the systems engineering user community and
definitions used in the UML specification.
6.2.5
SE
Conceptual Model and Semantic Dictionary
The SE Conceptual Model and Semantic Dictionary is a joint
effort between INCOSE, AP-233, and the OMG SE DSIG to develop a top-level
information model to characterize basic systems engineering concepts. Early
versions were developed as part of the Systems Engineering Data
Representation and Exchange Standardisation (SEDRES) project, a European
consortium project that led to the formation of ISO AP-233.
6.2.6
Responses to UML for SE Request for Information (RFI)
The SE DSIG issued an OMG Request for Information (RFI) in
February 2002 to collect input on existing experience and to gather
requirements on the use of UML for SE. There were thirteen responses to this
RFI, which were reviewed at the June and September 2002 meetings of the SE
DSIG. The complete set of RFI responses and presentations regarding these
responses are available on the UML for SE RFP page. In addition, there were
two RFI responses to the UML 2.0 RFI in 1999 that addressed the application
of UML for SE, and which are also identified on below.
6.2.7 Reference
Papers
Several papers have been written on the use of UML for
systems engineering, some of which provided some excellent insights to
validate the requirements, and which also offer potential solutions. In
addition, there are some reference papers for non-UML based systems
engineering approaches that may assist in assessing how UML for SE might
support or contrast with these approaches. Some of these papers are
available from the “Reference Papers” link of the UML for SE RFP page.
6.2.8
Systems
Engineering Process Standards
The SE DSIG
effort is focused on establishing standards for system modeling. System
modeling should be an integral part of the activities and techniques defined
by a systems engineering process and methodology. There are several
standards for systems engineering processes, including ANSI/EIA 632, IEEE
1220-1998, and ISO/IEC 15288. Each
of these process standards defines a set of primary activities that must be
performed to implement systems engineering. There are also a variety of
methodologies for implementing the systems engineering process, which
include both structured and object-oriented methodologies. Some examples of
systems engineering methodologies are referenced in the UML for SE RFI
Responses, and many others can be found in the INCOSE systems engineering
papers, journals, and handbook, as well as a broad array of systems
engineering texts. These process standards and methodologies help to provide
additional context on the variety of roles that a systems modeling language
might fill.
Other
6.7.1 Sample Problem Description:
Submissions shall include models of one or more sample
problems to demonstrate how their customization of UML for SE addresses the
requirements of this RFP. The submitter may select one or more sample
problems of their choosing, or apply their proposed solution to the sample
problem descriptions included below. The compliance matrix referred to in
Section 6.5 of the RFP, must include a reference to the portion of the
sample problem, which demonstrates how each requirement is being addressed.
Return to SE DSIG
|
