AP233 OMG And A Concept Model for Systems Engineering, - PowerPoint PPT Presentation

1 / 16
About This Presentation
Title:

AP233 OMG And A Concept Model for Systems Engineering,

Description:

Fabrication. Vendor. Assembly. Vendor. Package Data. Supplier. Requirements ... Describes product data throughout the lifecycle of a product and through the ... – PowerPoint PPT presentation

Number of Views:64
Avg rating:3.0/5.0
Slides: 17
Provided by: davidw56
Category:

less

Transcript and Presenter's Notes

Title: AP233 OMG And A Concept Model for Systems Engineering,


1
AP233 - OMG And A Concept Model for Systems
Engineering,
David W. OliverModel Based Systems, Inc.173
Iacuele Drive, Wakefield RI 02879doliver106_at_cox.n
et
11/06/02
2
What is the context of Systems Engineering?
Commercial
Govt
User/Owner/Operator
User/Owner/Operator
Management
Marketing
Acquisition Authority
Systems Engineering
UML ISO SC7
Engineering Disciplines
3
Circuit Board Supplier Network Standard Protocols
Facilitate Data Use
System Engineer
Package Data Supplier
Simulation Model Supplier
Requirements
Design Team
Assembly Vendor
Configuration Managed Corporate Data Interface
Process
ECAD
MCAD
Device Supplier
Fabrication Vendor
A Standard Data Model
4
Scope of STEP
Describes product data throughout the lifecycle
of a product and through the supplier chain.
5
Some Existing Application Protocols
AP201 Explicit Draughting AP202 Associative
Draughting AP203 Configuration Controlled 3D
Designs of Mechanical Parts and Assemblies
AP204 Mechanical Design using boundary
representation AP205 Mechanical Design using
Surface Representation AP207 Sheet Metal Die
Planning and Design AP209 Composite Metallic
Analysis Related Design AP210 Electronic
Assembly, Interconnect and Packaging Design
AP212 Electrotechnical Design and Installation
AP213 Numerical Control (NC) Process Plans for
Machined Parts AP214 Core Data for Automotive
Mechanical Design Processes AP215-218 Ship
Arrangement, Moulded Forms, Piping, Structures
AP220 PCA Process Planning AP221 Functional
Data and their Schematic Representation for
Process Plant AP222 Design to Manufacturing for
Composite Structures AP223 Exchange of Design
and Manufacturing Product Information for Cast
Parts AP224 Mechanical Product Definition for
Process Planning Using Machining Features AP225
Building Elements Using Explicit Shape
Representation AP226 Ship Mechanical Systems
AP227 Plant Spatial Configuration AP231
Process Design and Process Specifications of
Major Equipment AP232 Technical Data Packaging
Core Information and Exchange AP233 Systems
Engineering Data Representation AP239 Maintenance
(also called PLCS)
indicate at DIS, FDIS or IS
6
now
later
May 2000
over
INCOSE Requirements
PDM Modules
PLCS Modules
Baseline
(Program Life Cycle Support)
AP233 Successive Releases
Ist, Text Requirements
2nd, Structure
3rd, Funct Behavior
4th, State Behavior
7th, Organ., Roles, People
5th, Configuration Management
6th Change Control
8th, WBS Scheduling
7
Benefits of AP233
  • A quantitative standard that supports
    information transfer
  • - Like the standard meter and watt, not like
    1220 and 632
  • International standard XML tags for requirements
    information
  • Information transfer through the supply chain
    and across tools
  • Basis for a UML Profile for Systems Engineering
  • - Bridge the information chasm to Software
    Engineering
  • - Align System/Software Semantics
  • - An accepted language for Systems Engineering
  • Dollar value to companies of rigorous
    requirements
  • information transfer is millions to billions!

8
STEP in Data Exchange
Exchange standard
SE Tool STEP Interface
Encoding formats
Process model (AAM)
Information model (ARM)
File


Reusable parts (STEP Libraries IR, AIC,
Modules..)
Database
Information model (AIM)
9
Dictionary Rules
1. Definitions tell what of all things are
included by the definition and what are
excluded. 2. Definitions tell how a thing
already defined decomposes into other
defined things 3. Definitions tell how things
already defined are classified 4. Definitions
tell how things already defined are related 5.
Definitions have a distinct order. There is a
root that starts the system of definitions.
Definitions may use terms already defined and
terms that appear in a standard dictionary.
10
(3)
Domain of Interest
(2)
Category
(5)
categorizes
System View
(1)
(6)
(7)
has view
Stakeholder
SE_Thing
Environment
exhibits
has
(4)
(8)
Interacts with
Stakeholder Need
satisfied by
System
(9)
(11)
allocated to
Property Reference
System Requirement
Property
represented by
statement of
reference for
(10)
derived from
(12)
(13)
(14)
Physical Property
Structure
Behavior
Top Level Concept Model, Figure 1.
allocated to
budgeted to
11
(14)
Structure
(19)
(17)
(15)
Interface Specification
Part
described by
Port
1
1
Interconnection (18)
(16)
Link
System Static Structure, Figure 2.
12
(1)
Light blue background means this entity comes
from Figure 1.
(12)
Behavior
(20)
(21)
(22)
generate and consume
Function Ordering
orders
Function
I/O
(4)
(24)
(23)
(6)
External Function
Internal Function
System
allocated to
Environment
allocated to
1
2
generates and consumes
Behavior, Figure 3.
13
Systems Engineering
Element
Category, exhaustive exclusive
Software Engineering
Matter
Energy
Information
Knowledge about elements in an interpretable langu
age
Obey Conservation Laws
Has mass, unit mass Occupies volume, unit
length3
Ability to do work units masslength2/time2
14
Systems Engineering
Software Engineering
Properties calculated with engineering
equations from Properties
Whole
Whole
all
Part 1
Part 2
Part 1
Part 2
Unary decomposition MAY not be all of the parts
N-airy decomposition GAURANTEES all the parts
Properties and Behavior are result interaction of
parts calculated with laws of science
15
Systems Engineering
Software Engineering
  • Components in the
  • decomposition tree have
  • physical properties with
  • - Values
  • - Variance
  • - Units
  • - Probability distribution
  • The values exist and are versioned
  • - As specified
  • - As designed
  • - As manufactured
  • - By serial number
  • - As maintained
  • - As disposed of
  • Classes have attributes
  • Instances have attribute
  • values

16
Systems Engineering
Software Engineering
Super-class Attribute a_1 Method m_1
Exhaustive Non-exhaustive
Exclusive Inclusive
Sub-Category 3 Selection Criteria
Sub-Category 2 Selection Criteria
Sub-class 2 Attribute a_3 Method m_3
Elements belong in a category if their Properties
and Behaviors match the Selection Criteria. The
properties and behaviors result from their
composition
Subclasses inherit attributes and methods of
super-class. Code not repeated compiler creates
message links
Write a Comment
User Comments (0)
About PowerShow.com