©GoldSim Technology Group LLC., 2015 Designing Well-Structured and Scalable Models April 2015 Webinar.

Slides:



Advertisements
Similar presentations
HL7 V2 Implementation Guide Authoring Tool Proposal
Advertisements

Chapter 11 Designing the User Interface
Key-word Driven Automation Framework Shiva Kumar Soumya Dalvi May 25, 2007.
GoldSim Technology Group LLC, 2007 Slide 1 GoldSim User Conference San Francisco, CA October 25-26, 2007 GoldSim Tutorial and Discussion: Techniques for.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Requirements and Design
Analysis Modeling Over view of today’s lesson T he analysis model is the first technical representation of a system. Analysis modeling uses a combination.
Chapter 2 Succeeding as a Systems Analyst
Input Validation For Free Text Fields ADD Project Members: Hagar Offer & Ran Mor Academic Advisor: Dr Gera Weiss Technical Advisors: Raffi Lipkin & Nadav.
About the Presentations The presentations cover the objectives found in the opening of each chapter. All chapter objectives are listed in the beginning.
Chapter 4 Sec. 4.1, 4.2, 4.4 Procedures (User-defined)
User Interface Design Chapter 11. Objectives  Understand several fundamental user interface (UI) design principles.  Understand the process of UI design.
GoldSim Technology Group LLC, 2007 Slide 1 GoldSim User Conference San Francisco, CA October 25-26, 2007 GoldSim Tutorial: Model Building Tips for Organizations.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
TIBCO Designer TIBCO BusinessWorks is a scalable, extensible, and easy to use integration platform that allows you to develop, deploy, and run integration.
staffs.ac.uk Process Model. staffs.ac.uk Contents Provide definitions Explain the components and representations Introduce a step.
1 Analytical Tools, Data & Scenarios Workshop July 29, 2004 California Water Plan Update 2004.
CHAPTER 3: DEVELOPING LITERATURE REVIEW SKILLS
BIS310: Structured Analysis and Design Introduction and Systems Planning Week 1.
Managing the development and purchase of information systems (Part 1)
Software Engineering 2003 Jyrki Nummenmaa 1 REQUIREMENT SPECIFICATION Today: Requirements Specification Requirements tell us what the system should.
Requirements Analysis
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
Web Designing By Bhupendra Ratha, Lecturer School of Library & Information Science D.A.V.V., Indore.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa REQUIREMENT SPECIFICATION Today: Requirements Specification.
<Idea Title> Students : XXX, YYY (University)
Generic Instrument Processing Facility Interface Specifications A. BuongiornoFrascati 12 /10/2012 ESA EOP-GS 1.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
Enterprise Architecture [Product Name] [Enterprise Architect] [Discipline and Names] To-Be Powerpoint Presentation v
Structured Analysis.
I Power Higher Computing Software Development The Software Development Process.
Ad Hoc Graphical Reports Ad Hoc Graphical Reports Copyright © Team #4 CSCI 6838 Spring CSCI Research Project and Seminar Team# 4 (
Program Planning and Design. What is Program Planning and Design? Program planning and design is simply knowing what you want to do and how you want to.
OHTO -01 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it.
Chapter 9 & 10 Database Planning, Design and Administration Database Application Lifecycle DBMS Selection Database Administration.
MODELING AND ANALYSIS Pertemuan-4
Enterprise Architecture Aligning IT and Business during Integration Antonio Rios April 2008.
©GoldSim Technology Group LLC., 2012 Dashboards August 2012 Webinar By Jason Lillywhite.
July 2012 Webinar.  The conceptual model  Containers ◦ Localization ◦ Exposing output ◦ Cloning  Submodels  Dashboards.
Modern Systems Analysis and Design Third Edition Chapter 2 Succeeding as a Systems Analyst 2.1.
CSC480 Software Engineering Lecture 7 September 16, 2002.
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
Software Engineering Lecture 10: System Engineering.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Data Flow Diagram : Developed By Larry Constantine as a way of expressing system requirements in graphical Form: Data Flow Models (DFMs) are easy to understand.
 Problem Analysis  Coding  Debugging  Testing.
 System Requirement Specification and System Planning.
Version 0.1 Draft – For Review Murali Mohan Murthy
5th Shire River Basin Conference 22 February 2017 Shire River Basin Management Project Shire Basin Planning Tool Sub-Component A1 Development of a.
Software Testing.
An Overview of Requirements Engineering Tools and Methodologies*
Data Flow Diagrams.
Designing Well-Structured and Scalable Models
GUIDE FOR AN EFFECTIVE POSTER
System Programming and administration
Modern Systems Analysis and Design Third Edition
System Design.
Web Engineering.
Dev Test on Windows Azure Solution in a Box
Software Requirements Specification Document
Scenario Modeling in GoldSim
Georg Umgiesser and Natalja Čerkasova
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Members: Keshava Shiva Sanjeeve Kareena
MECH 3550 : Simulation & Visualization
THE ECE 554 XILINX DESIGN PROCESS
Joint Application Development (JAD)
THE ECE 554 XILINX DESIGN PROCESS
Modern Systems Analysis and Design Third Edition
Programming Logic and Design Eighth Edition
Presentation transcript:

©GoldSim Technology Group LLC., 2015 Designing Well-Structured and Scalable Models April 2015 Webinar

©GoldSim Technology Group LLC., 2015 Overview Design Implementation Documentation Validation and review Presentation

©GoldSim Technology Group LLC., 2015 Types of Models A model to answer a specific question A tool to answer on- going questions

©GoldSim Technology Group LLC., 2015 Design: Model Requirements Before design Basis for level of effort What does the model do and not do? Specific requirements –Interface and Reporting –Data –Functional requirements –Performance –Delivery & Maintainability

©GoldSim Technology Group LLC., 2015 Design: Formulate Conceptual Model How to fulfill requirements? Schematic diagrams Top down approach

©GoldSim Technology Group LLC., 2015 Design: Model Framework Input/output Performance Interface

©GoldSim Technology Group LLC., 2015 Design: Top Down Approach Start with “Here is the problem I’m solving…” Formulate problem using diagrams and logical statements Diversion <= 4 m3/d How big should new pond be? Can water quality be improved? How can we maximize supplies? Expenses < $5M Supplies >= 100 ML

©GoldSim Technology Group LLC., 2015 Design: Draw a System Schematic Upstream Pond 1 Pond 3 Pond 2 Return Flow Overflow Supply A A A Supply B S S Downstream A A Return Flow

©GoldSim Technology Group LLC., 2015 Document the Design Include requirements Criteria and assumptions Diagrams Basis for model documentation

©GoldSim Technology Group LLC., 2015 Implementation Build using “top-down” approach Testing Documentation and graphical design User interface Standards Versioning and file management

©GoldSim Technology Group LLC., 2015 Implementation: System Components

©GoldSim Technology Group LLC., 2015 Keep it DRY Don’t Repeat Yourself Local containers provide local scope Cloned containers Maintain libraries

©GoldSim Technology Group LLC., 2015 Group Elements with Common Purpose Scenario data Data controlled by dashboard External data sources Logic flow and/or physical flows Results that export

©GoldSim Technology Group LLC., 2015 Simulation Settings Assume the settings will change Don’t structure expressions on single time setting

©GoldSim Technology Group LLC., 2015 Implementation: Build Data Model Global inputs Avoid embedding data in expression fields Main outputs Import/export

©GoldSim Technology Group LLC., 2015 Generic Objects Localized containers with local scope Switch out “chunks” of the model Concise names

©GoldSim Technology Group LLC., 2015 Standardize Naming conventions Influence lines Documentation File Management Versioning

©GoldSim Technology Group LLC., 2015 Model Framework Example

©GoldSim Technology Group LLC., 2015 Model Framework Example

©GoldSim Technology Group LLC., 2015 Model Framework Example

©GoldSim Technology Group LLC., 2015 System Representation

©GoldSim Technology Group LLC., 2015 System Representation

©GoldSim Technology Group LLC., 2015 System Representation

©GoldSim Technology Group LLC., 2015 System Representation

©GoldSim Technology Group LLC., 2015 System Representation

©GoldSim Technology Group LLC., 2015 System Representation

©GoldSim Technology Group LLC., 2015 Model Documentation Focus on needs of audience Text Graphic objects Hyperlinks

©GoldSim Technology Group LLC., 2015 What Prevents Good Documentation? Insufficient funds It is difficult and time consuming to translate model logic and formulation to written descriptions The person writing the logic might not have the patience or ability to assist with documentation Lacking a good example to draw from

©GoldSim Technology Group LLC., 2015 Components of Documentation Abstract/Introduction/Background The underlying methodology (theory) Model limitations (and capabilities) Data requirements Input specifications (how is data put into the model?) Summary of model output and any processing of results Example application of the model

©GoldSim Technology Group LLC., 2015 Versioning

©GoldSim Technology Group LLC., 2015 Validation Independent models or algorithms Excel – note difference in time stepping! Reporting periods High-resolution results

©GoldSim Technology Group LLC., 2015 Independent Review Documentation is the basis Markup the model

©GoldSim Technology Group LLC., 2015 Presentation High level access to important results Low level access to all other results Consistency Muted colors Dashboards –Light background for Windows controls

©GoldSim Technology Group LLC., 2015

Thank you!