Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Systems Engineering CORE ® - A Model Based Approach January, 2004 Jody H. Fluhr Vitech Corporation 502.995.8895.

Similar presentations


Presentation on theme: "1 Systems Engineering CORE ® - A Model Based Approach January, 2004 Jody H. Fluhr Vitech Corporation 502.995.8895."— Presentation transcript:

1 1 Systems Engineering CORE ® - A Model Based Approach January, 2004 Jody H. Fluhr Vitech Corporation

2 2 Providers of Systems Engineering Solutions –Consulting –Training –Systems Engineering Technology and Tools Developers of the CORE Systems Engineering Tool Suite Founded in August 1992 First commercial shipment of CORE in March 1993 Headquarters in Tysons Corner, Virginia US Sales Offices throughout the US International Resellers around the world

3 3 Over 250 Clients in 14 Countries DoD –US Army, US Air Force, US Navy, USMC Intelligence Agencies –CIA, NIMA, NSA, NGIC Dept. of Energy –Sandia, Los Alamos, Idaho Falls, Savannah River, Hanford NASA Lockheed Martin Boeing Raytheon FedEx MITRE Booz-Allen & Hamilton SAIC Sprint Bearing Point UDLP Northrop Grumman Orbital Sciences Battelle TRW TASC Canadian Defense Research (DRDC) General Atomics/Burns and Roe NOKIA Telecommunications Motorola USAA De Beers Diamond Mines (SA) Peugeot/PSA Citroen Israeli Aircraft Industries Litton/PRC

4 4 The Systems Engineering Dilemma: Complexity and Synchronization Preliminary System Concepts And Existing Interfaces InputsInputs NeedsAndRequirements Operational System OutputsOutputs Supporting Documentation The Design Churn Electrical Engineering Electrical Engineering Manufacturing Test and Verification Mechanical Engineering Mechanical Engineering Systems Engineering Systems Engineering Software Engineering Software Engineering Quality Engineering Quality Engineering Safety Engineering Safety Engineering Procurement External Teams External Teams People with Specialty Skills With Their Perspective With Their Tools and Processes Producing Their Designs and Work Products Design Team

5 5 Major Challenge of Systems Engineering Managing the complexity to achieve a harmonious solution. –Many different types of efforts and information must be successfully managed/executed to achieve project success Engineering Elements (Requirements, Functionality, Architecture, System Resources, etc.) Project Elements (WBS, Activities/Tasks, Products, Reviews, Processes, Budgets, Schedules, etc.) Interconnectivity: Elements are related to and affect one another Complexity creates Challenges –Integration Challenge How to keep team efforts integrated? –Consistency Challenge How to keep engineering (information, design, documentation, etc.) consistent across the board? –Availability Challenge How to keep the latest engineering accessible to the whole team? How to prevent engineering/decisions based on obsolete/dated information?

6 6 CORE Overview CORE – A Systems Engineering Technology –Developed to support the People who implement the Systems Engineering Methodology Analyze, Decompose and Allocate System Requirements –Validate Requirements –Requirements Management Requirements Engineering Define System Behavior –Functionality –Operations Define System Architecture –Internal and External Interfaces –Subsystems/Assemblies/Components Define System Verification and Validation –Verification Requirements –Verification Planning (Events and Resources) –Designed to meet the Systems Engineers Challenges

7 7 CORERepository System Engineering Process Source Requirements Domain Architecture Domain Behavior Domain V&V Domain verified by Originating requirements trace to behavior Originating requirements trace to physical components Behavior is allocated to physical components verified by

8 8 An Iterative System Engineering Process Primary Concurrent Engineering Activities At Each Layer Source Documents Layer 1 (Draft 1) Layer 2 (Draft 2) Layer n (Final Specs) and Behavior Analysis Synthesis/ Architecture Design V & V System Design Database Specification & Report Generation Iterate as Required When Layer Completed Iterate as Required When Layer Completed Originating Requirements Analysis Behavior Analysis Synthesis/ Architecture Design V & V System Design DatabaseSpecification & Report Generation Behavior Analysis Synthesis/ Architecture Design V & V System Design DatabaseSpecification & Report Generation Initial Requirements for this layer are embodied in the model passed from the prior layer CORE supports a disciplined, iterative approach to systems definition.

9 9 CORERepository CORE Overview - System Engineering Capabilities Requirements Analysis and Management Verification and Validation Design and Implementation Requirements Capture Requirements Analysis Requirements Traceability Requirements Issues and Risks Physical Architectural Modeling Functional Modeling Operational Scenarios Interfaces – External and Internal System Integration System Issues and Risks Verification Requirements Development Verification Planning and Status Test Procedure Development Test Configuration Development Verification Issues and Risks Document Generation System Specifications Interface Control Documents RFP Responses and Proposals Requirements Traceability Reports

10 10 CORE Overview – The CORE Repository Centralized repository or database Accessible to engineering team Comprised of classes of elements and elements themselves Elements have attributes Elements can have relationships with other elements Data in repository can be viewed and manipulated in various ways Database Editor CORE Repository

11 11 Systems Engineering CLASSES Relationships Attributes Element Document System Components Functions Interfaces Constraints Requirements Risks Issues Etc. This Database Editor view allows browsing of all system elements, Relationships, and attributes. CORE Overview – The CORE Repository

12 12 CORE Overview – Engineering Element Example Element Name Other Element Attributes ElementRelationships This element, ATC Draft Specs , documents these six requirement elements. Element Editor

13 13 Example: System Requirements Model Children (decomposed) Requirements Traced to Functionality Allocated to System components Original Requirements

14 14 CORERepository CORE Overview - System Engineering Capabilities Requirements Analysis and Management Verification and Validation Design and Implementation Requirements Capture Requirements Analysis Requirements Traceability Requirements Issues and Risks Physical Architectural Modeling Functional Modeling Operational Scenarios Interfaces – External and Internal System Integration System Issues and Risks Verification Requirements Development Verification Planning and Status Test Procedure Development Test Configuration Development Verification Issues and Risks Document Generation System Specifications Interface Control Documents RFP Responses and Proposals Requirements Traceability Reports

15 15 CORE Overview – Functional/Operational Modeling CORE provides Functional Flow Block Diagrams (FFBDs) to capture system functionality or operations. Each Function is an element in the Repository.

16 16 CORE Overview – Functional Interfaces Enhanced Functional Flow Block Diagram N 2 Diagram CORE provides Enhanced Functional Flow Block Diagrams and N 2 Diagrams to capture Functional Interfaces.

17 17 System behavior model defines architecture of simulation model CORE Overview – Functional/Operational Modeling and Discrete Event Simulation CORE executes FFBDs in its Discrete Event Simulator allowing dynamic analysis of functional models and requirements.

18 18 CORE Overview – System/Architecture Modeling The System Architecture or System Hierarchy view shows the breakdown of the system. See Next Slide.

19 19 CORE Overview – System/Architecture Modeling Attributes of this system component. Relationships to other elements. A different view of the same element – its attributes and relationships to other elements in the system model.

20 20 CORE Overview – System Interfaces See Next Slide. This Interface or Physical Block Diagram is automatically generated by CORE based on the data in the repository. The Open Circle on the interface indicates that the interface connects through the Top-Level System to a subsystem.

21 21 CORE Overview – System Interfaces Interface Name Interface Description Interface Connectivity All things that appear on any diagram are elements in the Repository.

22 22 CORE Overview – System Interfaces Data (Secondary) Interface

23 23 CORERepository CORE Overview - System Engineering Capabilities Requirements Analysis and Management Verification and Validation Design and Implementation Requirements Capture Requirements Analysis Requirements Traceability Requirements Issues and Risks Physical Architectural Modeling Functional Modeling Operational Scenarios Interfaces – External and Internal System Integration System Issues and Risks Verification Requirements Development Verification Planning and Status Test Procedure Development Test Configuration Development Verification Issues and Risks Document Generation System Specifications Interface Control Documents RFP Responses and Proposals Requirements Traceability Reports

24 24 CORE Overview: Verification & Validation Planning Verification Requirement Verification Event Test Configuration Test Procedure Requirement Source Source Requirement Design/Implementation Traceability

25 25 Program and Project Management Organizational Model Work Breakdown Structure Project Functional Flow Model COREs Systems Engineering Methodology and Capabilities can be applied to project engineering. Refer to ECS Case Study

26 26 CORERepository CORE Overview - System Engineering Capabilities Requirements Analysis and Management Verification and Validation Design and Implementation Requirements Capture Requirements Analysis Requirements Traceability Requirements Issues and Risks Physical Architectural Modeling Functional Modeling Operational Scenarios Interfaces – External and Internal System Integration System Issues and Risks Verification Requirements Development Verification Planning and Status Test Procedure Development Test Configuration Development Verification Issues and Risks Document Generation System Specifications Interface Control Documents RFP Responses and Proposals Requirements Traceability Reports

27 27 The content of documents are automatically generated by CORE based on the data in the repository. CORE Overview – Document Generation

28 28 COREscript and API Scripting language provided in CORE –Object Oriented Query Language –Document/Report Generation MS Word compatible (Rich Text Format) MS Excel compatible HTML Text Over 30 open-source reports (System Specifications, Interface Specifications, etc.) are provided –Query and Analysis Application Program Interface –Provides access to Engineering Repository information by external applications –Automation of information exchange with applications such as PDM, DOORS, etc.

29 29 The Total Process and Synchronization ORD.1Intelligence Information System Source Requirements Date: August 3, 1996 Author: System Engineer Number:Name: documents incorporates generatescauses constrained by ORD.1 Intelligence Information System Source Require... Document OR.1 Specific Requirements OriginatingRequir... OR.1.1 Accept Requests OriginatingRequir... I.1 Media of Requests Issue OR.1.2 Retain Inventory OriginatingRequir... OR.1.3 Control Multiple Sensors OriginatingRequir... OR.1.4 Maximum Staff OriginatingRequir... R.1 Staffing Per Shift Risk OR.2 Continuous Support OriginatingRequir... SYS.1 Intelligence Information System System C.1 Continuous Operation Constraint Date: August 4, 1996 Author: System Engineer Number: C.0 Name: Universe built from C.0 Universe External System C.1 Customers External System C.2 Collectors External System SYS.1 Intelligence Information System System Architecture Domain Requirements trace to behavior Requirements trace to physical components Source Requirements Domain Process Domain Source Requirement s Analysis Behavior Analysis Architecture Analysis Design V & V V&V Domain Function/ Behavior Domain Behavior is allocated to physical components verified by

30 30 CORE Deployment Options Workstation Integrated application for small teams or on- site modeling/review Updates Segments Enterprise Collaborative environment at the product, project, or enterprise level CORE2net Internet Intranet Web browser access enabling collaboration at the enterprise level and beyond

31 31 Backup

32 32 CORE Workstation –Fully functional, single-user version of CORE Self-Contained Database Management System Executes on standalone computer workstation –Databases can be exported and imported –Operates in conjunction with CORESim Product CORESim provides Discrete-Event Simulation capability –System Requirements Windows 95/98/Me or Windows NT/2000/XP 300 MHz processor or higher 128 MB RAM 80 MB available hard disk space CORE Deployment Options – Workstation

33 33 CORE Enterprise –Client-Server Version of CORE –Provides scalability for project teams –Provides access to engineering repository from clients on local- area network –Enterprise Server System Requirements Windows NT/2000/XP (Professional or Server Additions) 10BaseT Network (or better) 128 MB RAM 300 MHz CPU or higher –Enterprise Client System Requirements Windows 95/98/Me or Windows NT/2000/XP 300 MHz processor or higher 128 MB RAM 80 MB disk free space TCP/IP protocol LAN access to Enterprise Server CORE Deployment Options – Enterprise

34 34 COREsim –Adds Discrete Event Simulation capability to CORE –Dynamically interprets behavior models (FFBDs) –Utilized to identify timing, resource utilization and model inconsistencies –System Requirements No additional resources required CORE Deployment Options – COREsim

35 35 CORE2net Enterprise Web Server –Allows any workstation with a web browser and internet access to Engineering Repository on Enterprise Web Server –Operates in Enterprise Configuration Only –Requires user name and password (same as Workstation and Enterprise) –Web-based html interfaces Predefined views and queries Customizable html interfaces can be developed and deployed CORE Deployment Options – CORE2net Web Server

36 36 CORE2net allows users to access the CORE Engineering Repository on the Enterprise Server using the Internet Provides browsing capability Authorized users can change element information Execute queries or generate views (see next slide) CORE Deployment Options – CORE2net

37 37

38 38 Thank You for Attending. Jody H. Fluhr Vitech Corporation Phone:


Download ppt "1 Systems Engineering CORE ® - A Model Based Approach January, 2004 Jody H. Fluhr Vitech Corporation 502.995.8895."

Similar presentations


Ads by Google