TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY TRAINS – Railway Vehicle and TRACK System Integration the.

Slides:



Advertisements
Similar presentations
Visual Scripting of XML
Advertisements

Information Systems Analysis and Design
Documenting a Software Architecture By Eng. Mohanned M. Dawoud.
© S. Demeyer, S. Ducasse, O. Nierstrasz Reverse Engineering.1 2. Reverse Engineering What and Why Setting Direction  Most Valuable First First Contact.
Parameterising Bayesian Networks: A Case Study in Ecological Risk Assessment Carmel A. Pollino Water Studies Centre Monash University Owen Woodberry, Ann.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Chapter Chapter 1: Introduction to Decision Support Systems Decision Support.
Requirements Engineering Processes
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Course Instructor: Aisha Azeem
Engineering Systems of.
Object-Oriented Analysis and Design
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
Špindlerův Mlýn, Czech Republic, SOFSEM Semantically-aided Data-aware Service Workflow Composition Ondrej Habala, Marek Paralič,
Systems Analysis And Design © Systems Analysis And Design © V. Rajaraman MODULE 14 CASE TOOLS Learning Units 14.1 CASE tools and their importance 14.2.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
1 CSE 2102 CSE 2102 CSE 2102: Introduction to Software Engineering Ch9: Software Engineering Tools and Environments.
Text CONSEG 09 Domain Knowledge assisted Requirements Evolution (K-RE)
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
Towards an activity-oriented and context-aware collaborative working environments Presented by: Ince T Wangsa Supervised by:
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
T. Dawson, TASC 9/11/13 Use of a Technical Reference in NASA IV&V.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
 Copyright 2005 Digital Enterprise Research Institute. All rights reserved. Semantic Web services Interoperability for Geospatial decision.
Software Architecture and Design Dr. Aldo Dagnino ABB, Inc. US Corporate Research Center October 23 rd, 2003.
Chapter 7 System models.
Lecture 7: Requirements Engineering
Business Process Change and Discrete-Event Simulation: Bridging the Gap Vlatka Hlupic Brunel University Centre for Re-engineering Business Processes (REBUS)
System models l Abstract descriptions of systems whose requirements are being analysed.
Pertemuan 19 PEMODELAN SISTEM Matakuliah: D0174/ Pemodelan Sistem dan Simulasi Tahun: Tahun 2009.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Systems Analysis and Design in a Changing World, 3rd Edition
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 Introduction to Software Engineering Lecture 1.
Illustrations and Answers for TDT4252 exam, June
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
SEEK Welcome Malcolm Atkinson Director 12 th May 2004.
Project CIRRUS Expertise Center Sustainable Business Operations 1 The CIRRUS approach Sustainable Development introduction in engineering education by.
Software Architectural Views By the end of this lecture, you will be able to: list and describe the views in the 4+1 view model of software architecture.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Metadata By N.Gopinath AP/CSE Metadata and it’s role in the lifecycle. The collection, maintenance, and deployment of metadata Metadata and tool integration.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
Proposed Course: ENG450: Multidisciplinary Design Bob Dennis.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
KNOWLEDGE MANAGEMENT UNIT II KNOWLEDGE MANAGEMENT AND TECHNOLOGY 1.
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
1 Architectural Blueprints—The “4+1” View Model of Software Architecture (
M253 Team Work in Distributed Environments Week (3) By Dr. Dina Tbaishat.
Virtual Track Surveying Paul Furniss. An introduction to Omnicom Engineering A few words from Gary Sanford the UK Sponsor What is the OmniSurveyor3D System?
Unified Modeling Language
Architecture Components
The Extensible Tool-chain for Evaluation of Architectural Models
Presentation transcript:

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY System Models to Assess the Impact of Change The IEE Railway System Modelling – Not Just for Fun Seminar Thursday 30 th September 2004 Clive Roberts Lecturer in Railway Systems University of Birmingham

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Background Rail Vehicle and Track System Integration Project is funded through the EPSRC Systems Integration Initiative A 3-year collaborative industry/academia research project (ending January 2005) Research split between University of Birmingham and Manchester Metropolitan University Multi-disciplinary team: Civil Engineers, Vehicle Dynamicists, Software Engineers, Metallurgists, Electrical Engineers

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Project Motivation Many problems span several engineering disciplines and can only be effectively tackled by understanding the system as a whole Systems engineering together with conceptual systems modelling allows problems to be investigated more effectively In particular the rail industry needs a means of investigating the effects of changes on the whole system, not just within individual subsystems or components

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Systems Engineering Process

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Project Work Packages Requirements Elicitation – to understand what is required System Modelling – to map the relationships and interconnections between components Compositional Modelling – to build new models from model fragments and infer knowledge TOOLS Database – to provide details of existing task specific tools and the links between them Decision Support System

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Requirements Elicitation Initial part of the Systems Engineering process Decomposition of the problem in order to further understanding Identify stakeholder and system level requirements Requirements modelling Understanding existing practices (cost modelling, wear modelling....)

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Scenarios Physical System Relationships

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Scenarios Model Identification (identification) –To provide the user with models/tools that may aid with a particular problem

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Scenarios Model Identification (data flow) –To provide a series of models/tools which when joined together may solve a particular problem

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Scenarios Document Database –To provide the user with information relating to all aspects of a particular component / process

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Scenarios Expert Identification –Provide details of experts in a particular field

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Forms the foundations of the decision support system knowledge base Hierarchical relationship model to show simple interactions between physical components (elements) Model elicited from domain experts Provides a means of communicating about the domain under consideration System Modelling

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY System Modelling

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY System Modelling

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Compositional Model The core of the decision support system engine Builds on the simple foundation of the hierarchical system relationship model Captures the systemic knowledge in an organised way System knowledge is represented in logical sets Software algorithms are linked to model fragments in order to compose a scenario model for a given scenario

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Compositional Model

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Compositional Modelling Terminology Decision Variables - elements that change the model depending on the decision that is made by the user Physical Properties- properties that relate to the physical arrangement of the model element Dependent Variables - elements that are only relevant when some interaction occurs in the relationship. They can form limiting parameters for behaviour i.e. if X>Y then Z.

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Tools used in the Railway System Infrastructure Vehicle V - I Interaction Wheel W – R Interaction Rail Substructure Management Environment TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY TOOLS Database

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY VAMPIRE : Vehicle Dynamics Simulation Package VAMPIRE Introduction TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Description Inputs OutputsContact Comments

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY ToolsInputs/Outputs Materials data Rail Plan Vehicle data Traction Data Tractive Effort & Speed ADAMS GENSYS NUCARS SIMPACK VAMPIRE Route data Tools Database - Agreed Case Studies Traction power/traction control on RCF – c2 the MANCHESTER METROPOLITAN UNIVERSITY Vehicle parameters, Track description Track Forces ABAQUS ANSYS HyperMesh I-DEAS Pro/MECHANICA Medina nCode RCF Fatigue Analysis

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY ADAMS GENSYS NUCARS SIMPACK VAMPIRE Track Forces Rail Plan Traction Data Vehicle data Route data RCF the MANCHESTER METROPOLITAN UNIVERSITY ToolsInputs/Outputs REFRAIL Chalmers WLRM Tractive Effort & Speed Vehicle parameters, Track description Tools Database - Agreed Case Studies Traction power/traction control on RCF – c3

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Decision Support System A decision support system to aid railway stakeholders to make decisions regarding system changes is being developed At the core of the DSS sits a hierarchical system relationship model which is used to compose models for a given scenario The user interface will be able to answer questions such as: –What affect does x have on y –What affect does changing x have......

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Decision Support System

TRAINS – Railway Vehicle and TRACK System Integration the MANCHESTER METROPOLITAN UNIVERSITY Conclusions and Further Work The project aims to generate a reasoned framework based on Systems Engineering Models and Principles to help railway engineers identify the affects of changes on the railway systems A prototype decision support system is being developed incorporating system modelling, composition modelling and the tools database Further work will be undertaken in a follow-on project to build economics into the models