MOWLES Team Update Omar AbuRealh (SE), Systems Engineering, Reporting and Presenting Robert Collier (OR), Customer Liaison and Team Lead Joseph Pack (SE),

Slides:



Advertisements
Similar presentations
Integration of MBSE and Virtual Engineering for Detailed Design
Advertisements

10 Software Engineering Foundations of Computer Science ã Cengage Learning.
Alternate Software Development Methodologies
Object-Oriented Analysis and Design
Introduction To System Analysis and Design
Lecture 11: Chapter 22 Topics –Object Oriented Modeling –UML –Use case.
Systems Development Life Cycle
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Permanent Magnet Motor Modeling Software Evaluation Kaila Krieser, EE Dan Montgomery, EE Craig Christofferson, EE Mark Wisted, EE Dr. Mani Mina, Advisor.
S/W Project Management
Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Mihir Daptardar Software Engineering 577b Center for Systems and Software Engineering (CSSE) Viterbi School of Engineering 1.
Chapter 14 Information System Development
1 Systems Engineering Process Review Mark E. Sampson EMIS 8340 Systems Engineering Tool—applying tools to engineering systems.
Acquiring Information Systems and Applications
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
Introduction To System Analysis and Design
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
SE: CHAPTER 7 Writing The Program
Systems Analysis and Design in a Changing World, 3rd Edition
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
Software Engineering Emphasis for Engineering Computing Courses William Hankley Computing & Information Sciences Kansas State University.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
Model Based Systems Engineering Visualization Steven Corns Missouri University of Science & Technology.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Chapter 5 – System Modeling
Systems Development Life Cycle
IBM Rational Rhapsody Advanced Systems Training v7.5
CompSci 280 S Introduction to Software Development
Chapter 1 The Systems Development Environment
UML(Unified Modeling Language)
UML Diagrams By Daniel Damaris Novarianto S..
Component and Deployment Diagrams
Chapter 5 System modeling
Chapter 5 – System Modeling
INCOSE Usability Working Group
Object-Oriented Analysis and Design
Program Management Portal: Request Management, PCRs and the Client
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN
Unified Modeling Language
Chapter 1 The Systems Development Environment
UML Diagrams Jung Woo.
System Modeling Chapter 4
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
CH#3 Software Designing (Object Oriented Design)
An Introduction to Visual Basic .NET and Program Design
Software Engineering (CSI 321)
Outbrief MBSE Workshop Breakout Session 31 January 2011
CS310 Software Engineering Dr.Doaa Sami
Software Design Lecture : 15.
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
The Software Development Process
Systems Development Life Cycle
Chapter 4 System Modeling.
Chapter 1 The Systems Development Environment
MBSE for PLM: Part of the Digital Systems Life Cycle
UML  UML stands for Unified Modeling Language. It is a standard which is mainly used for creating object- oriented, meaningful documentation models for.
Decision Support System (DSS) for MOWLES
Presentation transcript:

MOWLES Team Update Omar AbuRealh (SE), Systems Engineering, Reporting and Presenting Robert Collier (OR), Customer Liaison and Team Lead Joseph Pack (SE), Evaluation Developer Tool

Overview Client Meeting Tool Design MBSE Design Moving Forward ACRONYMS Note: Acronyms used in this presentation are general systems engineering acronyms and not specific to this particular task: BDD - Block Definition Diagram DSS - Decision Support System GPU - Graphics Processing Unit IBD - Internal Block Diagram MBSE - Model-Based Systems Engineering MOE - Measure of Effectiveness MOP - Measure of Performance USB - Universal Serial Bus

Client Meeting: Overview Met with customer on Friday Clarified “requirements”/desires Clarified George Mason team’s project scope and expected contribution to long-term effort Discussed scope of input parameters Discussed expectations for final deliverables (MBSE ‘static’ models and decisions support system (DSS) tool to enable analysis) We discussed the exact design and of the vehicle being designed as well as our current options for visual tools. Additionally, the complete problem space and nature of the behavior of the visual tools was explained and possible solutions were proposed to resolve them. Finally we discussed the Parameters with which we wish to measure

Client Meeting: Lessons Learned Sensor discussion dominated technical conversation Three basic sensors were identified Photogrammetry: Works in Low Detail environments, ie cleanly made tunnels and buildings Light Coding: Works better in high detail environments Time of Flight: works better in high detail environments

Tool Design: The Use Cases Three Use Cases for DSS operation were identified User Runs Analysis: Run an analysis of the behavior of the system in the field User Adds a Component: adds a component to the available component to be analyzed Add a Platform Add Software Add Sensor Add Component Parameters User Changes Parameter Value: User changes a parameter for an attribute Generated Activity Diagrams from each use case

Tool Design: Creating the Use Cases Note that execution of the tool allows for adding different components (platform, sensor, software) via parameter values. Adding new parameters would involve the MBSE products.

Tool Design: Activity Diagram for ‘Run Analysis’ Initial activity diagrams are ‘living models’ and will change as more detailed functionality in the DSS is identified and more complex analytical processes are defined.

MBSE: Current Products Overview Current Model Based Systems Engineering (MBSE) products include a package diagram and a block definition diagram (BDD) The Package Diagram Describes the individual components within the system and the external actors to the system The Block Definition Diagram describes the way that the components within the system interact with each other and with the outside system. Here the BDD shows the internal system of the DSS and the MOWLES itself and how the interact with regard to the operator ‘Next step’ products include the internal block diagram (IBD) and parametric diagram Generated a ‘cheat sheet’ guide for the clients to aid in understanding language and form factor of MBSE deliverables

MBSE: Package Diagram

MBSE: Block Definition Diagram The BDD identifies which parameters from which physical objects are likely to be considered within the DSS. To change what parameters are considered, users would need to modify the BDD, IBD, and parametric diagrams to determine how to modify the DSS.

Moving Forward Continue meeting with the customer and explore avenues with which to make advancements in the problem and solution spaces Develop initial measures of effectiveness (MOE) (DSS outputs) Get review of initial measures of performance (MOP) and object parameters (DSS inputs) Deliver MBSE ‘cheat sheet’ to orient clients with expected architecture deliverables Tool Development: Continue definition of final tool use/implementation Develop approach for implementing calculations/logic presented in parametric models (from MBSE) MBSE: Develop initial IBD products to enable parametric diagram modeling Solicit for review/feedback of MBSE data (not necessarily directly on the products) from the client The most efficient approach seems to be proposing or ‘asserting’ each object’s MOPs and the total system’s MOEs, then pushing those MOPs/MOEs to the client for review.

Questions?