Upload
joseph-kasser
View
194
Download
1
Tags:
Embed Size (px)
DESCRIPTION
This paper provides an overview of a number of research areas that include investigating the nature of systems engineering and its underlying concepts, defining the properties of object-oriented requirements, producing prototype object-oriented tools for systems engineering, and applying of systems engineering to various domains.
Citation preview
© University of South Australia, 2003 1
A Program of Researchinto Systems Engineering
Joseph E. Kasser DSc CEng CM MIEE, Stephen C. Cook PhDFIEE FIEAust
Systems Engineering and Evaluation CentreUniversity of South Australia
School of Electrical and Information EngineeringMawson Lakes Campus, South Australia 5095
Telephone: +61 (08) 8302 3941, Fax: +61 (08) 8302 4723Emails: [email protected], [email protected]
© University of South Australia, 2003 2
Topics The elements of a framework for the
engineering of complex systems; Object-oriented systems engineering; Research into prototype object-
oriented tools for systemsengineering; The application of systems
engineering to various domains.
© University of South Australia, 2003 3
Systems Engineering
Academia isteaching it
Industry ispracticing it
INCOSE is trying toimprove it
Tower of SystemsEngineering
© University of South Australia, 2003 4
Tower of SystemsEngineering
Systems Engineering
But nobody knowswhat it is
No agreeddefinition
Academic debateabout degrees in thesubject
© University of South Australia, 2003 5
Product/sub-systemEngineering
Project SystemEngineering
Business SystemEngineering
Industry SystemEngineering
Socio-EconomicSystems Engineering
The 5-Layer Systems EngineeringModel
Government Regulation and Control.Economic, legal and political influences.
National Wealth Creation, the Nation’sEngine. (Japan operates at this level)
Industrial Wealth Creation. ManyBusinesses make an industry
Corporate Wealth Creation. (The Westoperates at this level.)
Technology Artefacts. To some the only“real” systems engineering. Many Products(can) make a system
Time Derek Hitchins, SETE 2000
© University of South Australia, 2003 6
ISO/IEC 15288 Road Map
Project PlanningProcess
Project AssessmentProcess
Project ControlProcess
Decision-makingProcess
Risk ManagementProcess
ConfigurationManagement ProcessAgreement Processes
Acquisition Process
Supply Process
InformationManagement Process
Enterprise EnvironmentManagement Process
Investment ManagementProcess
System Life CycleManagement Process
Resource ManagementProcess
Quality ManagementProcess
Enterprise ProcessesStakeholder Requirements
Definition ProcessRequirements Analysis Process
Architectural Design Process
Implementation Process
Maintenance Process
Disposal Process
Operation Process
Validation Process
Verification Process
Transition Process
Integration Process
Technical ProcessesProjectProcesses
© University of South Australia, 2003 7
Elements for Area of Research The Area of Concern (A),
• which might be a particular problem in a discipline (area ofstudy), a real-world problem situation, or a system of interest.
A particular linked Framework of Ideas (F) in whichthe knowledge about the area of concern is expressed.• includes current theories, bodies of knowledge, heuristics, etc
as documented in the literature as well as tacit knowledge.
The Methodology (M) in which the framework isembodied• incorporates methods, tools, and techniques in a manner
appropriate to the discipline that uses them to investigate thearea of concern.
© University of South Australia, 2003 8
Relationships Between F,M&A
Elements relevant to any piece of research(Checkland and Holwell, 1998: p 13).
© University of South Australia, 2003 9
Broad Areas of Concern A designed physical system
• (that also contains human components). A human activity system
• (engineering organisation).
Each span many disciplines and require pluralistic approaches thatnot only invoke multiple methodologies but ones that rest on quitedistinctly different frameworks of ideas.
They are of fundamentally different types and hence will probablyhave to be approached with different methodologies.
As such we now understand why:• Many systems engineers cannot clearly articulate the functions and
benefits of systems engineering (Kasser and Shoshany 2001).• It has been extremely difficult to establish a systems engineering
body of knowledge (SEBOK) for the diverse activities that areknown by the term “systems engineering.” (Kasser and Massie,2001).
© University of South Australia, 2003 10
Topics
The elements of a framework for theengineering of complex systems; Object-oriented systems engineering; Research into prototype object-
oriented tools for systems engineering; The application of systems
engineering to various domains.
© University of South Australia, 2003 11
Object-Oriented SE has a Gap
Concept ofoperations
(Use Cases)
Systems (objects)
Object-orientedsoftware
Object-orientedhardware
© University of South Australia, 2003 12
What is a Requirement? It is a means of communication
It is a representation of a need• Traditionally text based
Requirements are crucial todelivering the right system andproducing it in the most effectivemanner (optimal costs)
© University of South Australia, 2003 13
What is a Good Requirement? Describes something (“what”) about
the system to be implemented• Product dimension
Facilitates the process of implementingthe system• Process dimension
It’s a real requirement• Well-written but useless
© University of South Australia, 2003 14
The Real RequirementDesignRequirement Test
Acceptancecriteria
(property of a requirement)
© University of South Australia, 2003 15
Research Questions Can an object-oriented approach provide
traceability from the highest level needstatement to the lowest level ofimplementation? Can a conversion to object-oriented
requirements bypass or resolve today’sproblem of poor requirements?
What are the properties of object-oriented requirements?• Product dimension• Process dimension
© University of South Australia, 2003 16
Topics The elements of a framework for the engineering
of complex systems;
Object-oriented systems engineering;
Research into prototype object-orientedtools for systems engineering;• OCH
• CREAP
• PETS
The application of systems engineering to variousdomains.
© University of South Australia, 2003 17
The Operational ConceptHarbinger
Takes a holistic approach through greaterparticipation of stakeholders in a form thatallows them to contribute meaningfully
Helps to elicit (complete the set of)requirements
Reduces poorly articulated requirements
Minimizes undocumented requirements
Minimizes immeasurable requirements
© University of South Australia, 2003 18
OCH Evolutionary Sequence -Summary
Combined Operations Concept andRequirements information
Added• Measures of effectiveness• Multi-media and diagrammatic
information• Non-sequential access to, and display of,
information• Parallel display (views) of information
© University of South Australia, 2003 19
The Place of the OCH in the SDLC
© University of South Australia, 2003 20
Structure of the OCH Frame-based
Underlying sequential State Machine
Use Case scenarios
UML swim lane format
Activity sequence (PERT like) relationships
© University of South Australia, 2003 21
Scenario Formats UML, basic and enhanced with graphics
• the current way of working. Static workflow diagrams
• adding user perspective, Dynamic workflow diagrams
• animated diagrams showing sequences. Audio files
• containing verbal descriptions such as environmental conditions for the deployed system, or user
concerns.
Video files• showing scenarios
animated or filmed.
Simulations• of all or part of the system.
Text mode• for those people who still think in terms of “requirements”
© University of South Australia, 2003 22
Example
© University of South Australia, 2003 23
Server
LAN/Internet
CONTROL
S1 S2 Sn
Physical View of OCH
© University of South Australia, 2003 24
A Practical OCH
© University of South Australia, 2003 25
Advantages of the OCH
Bypasses today’s problems due to “poorrequirements”
Connects development effort more directly tothe user needs
Visual representation of “needs”• Improves the requirements elicitation process
by providing an interactive facility for exploring the capabilitiesof the customer’s needs.
• leads to inherited non-functional “needs”which reduces the quantity of “missing requirements”
Helps bridge the gap between soft and hardsystems
© University of South Australia, 2003 26
The Purpose of the CommunicationsRequirements Evaluation & AssessmentPrototype (CREAP)
To determine if Requirements Engineering tools couldbe extended to:• Constrain writers of requirements to feasible specifications• Generates a list of feasible implementation options consistent
with a defined inventory
To determine if• User selected combinations of equipment from inventory list• Would provide the needed communications capability• For a specific category of serviceAntennasReceiversTransmittersModems
© University of South Australia, 2003 27
Communications coverage
© University of South Australia, 2003 28
Elements of the CREAP
The frames• General purpose so that the contents of the frames
can be replaced by a set of frames for a differentscenario allowing the tool to be used in anotherscenario potentially with no additionalprogramming.
The user interface template• Provides the template for the information to be
displayed on the GUI.
The frame interpreter• A state machine, which interprets the contents of the
frames.
© University of South Australia, 2003 29
CREAP
© University of South Australia, 2003 30
Prototype Educational Tools forSystem and Software Engineering
(PETS)
© University of South Australia, 2003 31
Prototype Educational Tools forSystem and Software Engineering
(PETS)
© University of South Australia, 2003 32
Prototype Educational Tools forSystem and Software Engineering
(PETS)
© University of South Australia, 2003 33
Prototype Educational Tools forSystem and Software Engineering
(PETS)
© University of South Australia, 2003 34
Prototype Educational Tools forSystem and Software Engineering
(PETS)
© University of South Australia, 2003 35
Prototype Educational Tools forSystem and Software Engineering
(PETS)
© University of South Australia, 2003 36
Prototype Educational Tools forSystem and Software Engineering
(PETS)
© University of South Australia, 2003 37
Topics
The elements of a framework for theengineering of complex systems;
Object-oriented systems engineering;
Research into prototype object-oriented tools for systems engineering;
The application of systems engineeringto various domains.
© University of South Australia, 2003 38
Research areas An Acquisition Methodology for the Procurement and
Integration of a Network Enabled Warfare System ofSystems
A Systems Approach to the Evaluation of Complex, Real-Time Information Systems: Determining theEffectiveness of Command and Control Organisations
Developing methodologies to make efficient use ofCommercial Off The Shelf software products in Research
How the audio interface for short range infrared guidedair-to-air missiles can be improved
Measures of Effectiveness: The Standards for Success
Strategic Planning and Capability Engineering
© University of South Australia, 2003 39
Systems Engineering GlossaryProject
Student summer project• One iteration through the Development Life Cycle
Initial announcement on Discuss Reflector
Prototype (limited vocabulary) in test
SECOE project
© University of South Australia, 2003 40
Conclusions A research program into systems engineering covers a
broad range of activities The incorporation of process elements into the
requirement object has shown to be a promising approachfor increasing the effectiveness of the systems engineeringprocess and providing customers with a product that meetstheir needs.
The reductionist approach to solving the problem of poorrequirements is the time-phased parallel process ofbuilding a suite of tools for performing specific tasks.
While the reductionist approach may not be applicable tosolving all complex problems, in these applications theresults have been promising. FRED, CREAP, TIGER, theremaining PETS and the OCH provide capability thatshows that parts of the problem of poor requirements canbe alleviated by applying the appropriate technology.
© University of South Australia, 2003 41
Summary
The elements of a framework for theengineering of complex systems;
Object-oriented systems engineering;
Research into prototype object-oriented tools for systems engineering;
The application of systems engineeringto various domains.
© University of South Australia, 2003 42
Questions ?