610 likes | 945 Views
Systems Engineering Solution. OPCAT 3.0. Agenda. Background What is Systems Engineering? OPCAT Solution The Methodology. Company Profile. OPCAT 3.0. Mission Statement. Become the worldwide preferred model-driven system engineering solution, dramatically reducing development-cost.
E N D
Systems Engineering Solution OPCAT 3.0
Agenda • Background • What is Systems Engineering? • OPCAT Solution • The Methodology
Company Profile OPCAT 3.0
Mission Statement Become the worldwide preferred model-driven system engineering solution, dramatically reducing development-cost
Company Background • OPCAT solution is based on 13 years of research at the Technion and MIT. • OPCAT Inc. was founded by the Technion and Prof. Dov Dori during 2005 to commercialize the technology. • OPCAT benefits from continuous infusion of knowledge from leading academic institutes.
What is Systems Engineering? • Systems Engineering is a first, crucial phase in the development of any complex, multidisciplinary system. • The quality of the system design resulting from this mission-critical phase will impact the cost and value of the entire project.
Systems Engineering Defined “The top level process of engineering a system to meet overall requirements.” www.tso.co.uk/demo/itil2/cd/content/ss/ss_apdx_a_02.htm “The application of engineering to solutions of a complete problem in its full environment by systematic assembly and matching of parts in the context of the lifetime use of the system.”www.ichnet.org/glossary.htm
Software Design Mechanics Design Electronics Design Systems Engineering Role System Development Stages SYSTEM ENGINEERING DETAILED DESIGN PRODUCTION INTEGRATION TEST • Systems Engineering encompasses: • System Architecture • Requirements Engineering • Subsystem Integration Design • System Testing Design • Project Oversight & Management Accounts for ~15% of the Development Budget
Risk Time Risk Time Traditional Design SYSTEM DESIGN DETAILED DESIGN PRODUCTION INTEGRATION TEST Saved Time/Cost “System Thinking” Design Source: INCOSE, 2005
Success in this mission-critical phase cannot be achieved using just Partial solutions geared for software design: UML Administration tools that focus on workflow andauthorization Elementary tools Like Word or Visio A comprehensive model-driven systems Engineering solution is a must!
Requirements and specification documents of large, complex systems that rely on text suffer from: • Indigestible volume • Inconsistencies and incompleteness • Lack of verification and simulation capabilities • Ambiguity and different interpretations
Unambiguous communication language. • Comprehensive • Amenable to simulation and debug at design level • Allows common language and better management control
OPCAT Architecture Smooth, fast, and consistent transition across the system lifecycle stages Editor Designing the system by using Object Process Methodology (OPM) graphical and textual language Advisor Smart algorithms identify design patterns and helps implement organization’s best practices on-the-fly. Simulator Simulation and conceptual debugging at the design level • Interaction Layer • Requirements • Production Information • Frameworks and Policies Engage requirements, production information (PLM) & standards- related-information into the SE design Integration tests are planed as a consistent layer on top of the system design Integration Test Planner Business Intelligence Gather and analyze design data in order to estimate quality, risk, reusability and cost
OPCAT Main Outputs Detailed Design The design is transmitted by XML to detailed design tools such as UML, BPEL, MATLAB and CAD, enabling smooth transition to the next phases of design. Project Management Skeleton Development tasks are automatically exported to the organizational project management software where resources, cost and timetable can be added. Product Lifecycle Management Systems Basic physical component list (Bill of Materials - BOM) carrying SKU is exported to the organizational PLM systems for further handling Knowledge Management Systems OPM blueprints provide a common ground for system development and reference. Embedded model-based test design serve as reference for the later system integration testing.
Main Advantages • A comprehensible model of the system throughout the entire system lifecycle, resulting in dramatic overall development cost reduction. • Preservation of actionable knowledge for effective maintenance and future generations development via OPCAT’s built-in evolution mechanism.
is a is a affects The basic idea behindObject-Process Modeling conceived reality modeled reality Bus Is modeled by Vehicle Car Is modeled by Objects Gas Filling Is modeled by Process Expressing real things – objects and processes – and relations among them as concepts in a model
Modeling objects • An object can represent: • A class – a template for a group of potentially existing things with the same set of attributes (structure) and operations (behavior) • An instance – an entity that actually exists, with is own attribute values Object:Racecar Attribute:Color Operation:Racing Object: Racecar Attribute: Color Attribute Value: yellow
Modeling processes • An process can represent: • A class – a template for an occurrence of a transformation (generation, consumption, or state change) of one or more objects • An instance – an actual occurrence of object transformation with is own attribute values Process:Wheel Replacing Process Attribute:Duration Process Attribute:Tools required Process:Wheel Replacing Process Attribute:Wheel Position Value: front left Process Attribute:Race Location Value: Daytona, OH
What is Object-Process Methodology? • A comprehensive conceptual modeling paradigm for Systems Engineering that enables: • Communicating • Documenting • Engineering (simulation, testing, traceability…) • Lifecycle support of complex, multi-disciplinary systems • Based on symmetry between structure (objects) and behavior (processes)
The basic OPM things: Objects and Processes Object-Process Diagram object process Object-Process Language
Two major OPM features: • Unification in a single model of the two crucial and complementary system aspects: • Structure – What? (objects) • Behavior – How? (processes) • Bi-modal expression of the model engaging the two sides of the brain: • Intuitive yet formal graphics, and • Equivalent naturallanguage
Objects and Processes • Objects and processes are two types of equally important things (entities) required to describe a system in a single, unifying model. • At any point in time, each object is at some state. • Objects are transformed through processes: generated, consumed, or change their state.
The object-process symmetry • Objects and processes are of equal importance in the system model • A system cannot be faithfully modeled without any one of those things • Objects and processes complement each other in representing knowledge about the system • There is no supremacy of one type of thing over the other – each can be above or below the other in the importance hierarchy
State • A situation that an object can be in at some point during its lifecycle • The only OPM entity beside things (object and process)
Cake Making Animated Simulation Example
OPM Elements: Entities and Links • Entity types: • Object: A thing that exists for some time • State: A situation at which an object can be • Process: A thing that transforms an object • Link types: • Structural link: A link denoting a persistent relation between objects • Procedural link: A link between a process and the object it transforms or a state of that object
OPM model of the carbon cycle Object-Process Diagram (OPD) Object-Process Language (OPL) paragraph
Carbon cycle: The OPL script Object-Process Language (OPL) paragraph
Complexity Management Complexity is controlled through recursive and selective scaling (zooming) of objects and/or processes to any desired level of details.
Complexity Management • The ability to trade off clarity and completeness: • Clarity is the ability to clearly present and see the system’s structure and behavior • Completeness is the extent to which all the details of the system are specified • These two model attributes necessarily contradict each other
Scrrenshot of the Product Lifecycle Engineering system Object-Process Diagram (OPD) OPD hierarchy view Object-Process Language (OPL) paragraph
Product Lifecycle Engineering system: The automatically generated text Productis physical.Productcan beapproved, distributed, used, pre-tested, rejected, stored, sold, orretired.pre-testedis initial.retiredis final. Product is made of Raw Material.Product benefits User.Manufactureris physical.Manufacturer makes & supports Product.Environmentis environmental and physical.Environmentconsists ofUser, Market Demand, Raw Material, Technology, andCompetition.Useris environmental and physical.Market Demandis environmental.Raw Materialis environmental and physical.Technologyis environmental.Competitionis environmental.Product Lifecycle Engineeringis physical.Product Lifecycle EngineeringrequiresEnvironment.Product Lifecycle EngineeringaffectsProduct, User, andManufacturer.