TU Dresden - Institut für Bauinformatik Folie-Nr.: 1 BIWO-04 Software Engineering (Software Systems) 2.Exercise System Capturing with IDEF0 TU Dresden.

Slides:



Advertisements
Similar presentations
Object-Oriented Software Engineering Visual OO Analysis and Design
Advertisements

Requirements Modeling Strategies
1 FUNCTION MODELING USING IDEF-0 IE 590 INTEGRATED MANUFACTURING SYSTEMS Lecture 7.
IFS310: Week 3 BIS310: Structured Analysis and Design 5/4/2015 Process Modeling and Data Flow Diagrams.
Chapter 7 Structuring System Process Requirements
Lecture #5 Agenda Cell phones off & name signs out Review Questions? UML class diagram introduction Our first class definition!
Introduction To System Analysis and Design
The Semantic Web Week 12 Term 1 Recap Lee McCluskey, room 2/07 Department of Computing And Mathematical Sciences Module Website:
CAD/CAM Design Process and the role of CAD. Design Process Engineering and manufacturing together form largest single economic activity of western civilization.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen - Bolzano Lesson 2 – Components.
FACULTY OF ENGINEERING DEPARTMENT OF CIVIL ENGINEERING SPRING SEMESTER ASSOC.PROF.DR. İBRAHİM YİTMEN CIVL 498 IMPLEMENTATION OF IT IN CONSTRUCTION.
Developed by Reneta Barneva, SUNY Fredonia Component Level Design.
1 Objective of today’s lesson S oftware engineering occurs as a consequence of a process called system engineering. Instead of concentrating solely on.
UML class diagrams (1) UML = Unified Modeling Language We use only class diagrams, not other UML diagrams Purpose: –keep OO concepts separate from implementation.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Course Instructor: Aisha Azeem
Introduction to Computer Technology
Chapter 7 Structuring System Process Requirements
Object-Oriented Analysis and Design
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
Introduction To System Analysis and design
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
Institute of Applied Informatics in Civil Engineering Dresden University of Technology A personal planning approach for the integration and coordination.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Chapter 1: The Database Environment and Development Process
PROF. ANNA MORENO ENERGY EFFICIENCY UNIT TRAINING AND INFORMATION SERVICE.
Towards Human-Executable Business Process Modeling Janis Barzdins, Edgars Rencis, Agris Sostaks Institute of Mathematics and Computer Science, University.
Business Process Management. Key Definitions Process model A formal way of representing how a business operates Illustrates the activities that are performed.
Data Flow Diagrams.
Lecture 6 Data Flow Modeling
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
` Tangible Interaction with the R Software Environment Using the Meuse Dataset Rachel Bradford, Landon Rogge, Dr. Brygg Ullmer, Dr. Christopher White `
TC Methodology Massimo Cossentino (Italian National Research Council) Radovan Cervenka (Whitestein Technologies)
An Introduction to Software Architecture
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 10 Use Case Design.
Modeling and simulation of systems Model building Slovak University of Technology Faculty of Material Science and Technology in Trnava.
IDEF0 Modelling techniques
1 Introduction to Software Engineering Lecture 1.
The Systems Development Life Cycle
Illustrations and Answers for TDT4252 exam, June
UML Diagrams: The Static Model Class Diagrams. The Static Model Define the static structure of the logical model Represent classes, class hierarchies.
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Chapter 8 Testing. Principles of Object-Oriented Testing Å Object-oriented systems are built out of two or more interrelated objects Å Determining the.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Software Engineering Lecture 10: System Engineering.
Faculty of Civil Engineering Institute of Construction Informatics, Prof. Dr.-Ing. Scherer Institute of Construction Informatics, Prof. Dr.-Ing. Scherer.
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
TU Dresden - Institut für Bauinformatik Folie-Nr.: 1 TU Dresden - Institut für Bauinformatik BIWO-04 Software Engineering (Software Systems) 4. Exercise.
Faculty of Civil Engineering Institute of Construction Informatics, Prof. Dr.-Ing. Scherer Institute of Construction Informatics, Prof. Dr.-Ing. Scherer.
Faculty of Civil Engineering Institute of Construction Informatics, Prof. Dr.-Ing. Scherer Institute of Construction Informatics, Prof. Dr.-Ing. Scherer.
TU Dresden - Institut für Bauinformatik Folie-Nr.: 1 TU Dresden - Institut für Bauinformatik BIWO-04 Software Engineering (Software Systems) Assignment/Examination.
Faculty of Civil Engineering Institute of Construction Informatics, Prof. Dr.-Ing. Scherer Institute of Construction Informatics, Prof. Dr.-Ing. Scherer.
TU Dresden - Institut für Bauinformatik Folie-Nr.: 1 TU Dresden - Institut für Bauinformatik BIWO-04 Software Engineering (Software Systems) 5. Exercise.
TU Dresden - Institut für Bauinformatik Folie-Nr.: 1 BIWO-04 Software Engineering (Software Systems) 1.Exercise System Capturing with IDEF0 TU Dresden.
School of Mechanical, Industrial, & Manufacturing Engineering Process Analysis and Modeling Using IDEF0.
School of Mechanical, Industrial, & Manufacturing Engineering Process Analysis and Modeling Using IDEF0.
Process Analysis and Modeling Using IDEF0
Method – Notation 8 Hours.
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Software Engineering Chapter 5 (Part 3) System Modeling Dr.Doaa Sami.
UML Diagrams: The Static Model Class Diagrams
Data, Databases, and DBMSs
CHAPTER 1: THE DATABASE ENVIRONMENT AND DEVELOPMENT PROCESS
System Concept Simulation for Concurrent Engineering
Software Design Methodologies and Testing
Software Architecture & Design
Presentation transcript:

TU Dresden - Institut für Bauinformatik Folie-Nr.: 1 BIWO-04 Software Engineering (Software Systems) 2.Exercise System Capturing with IDEF0 TU Dresden - Institut für Bauinformatik

Overall Process of an Engineering System Treatment 1.System Capturing High level definition of the purpose, functions, processes and behaviour Formal Representation of the System (IDEF0) 2.data structure = {O,R} based on a specific meta model (= O-O-Model) development of a data model as an O-O-schema = ideal data structure of the concepts 3.transformation of the conceptual data model in an operational database; today being most appropriate as a relational data structure (approximations) 4.implementation of the schema in a data base software; 5.instantiation of an engineering model = configure the domain-specific engineering model from the data model 6.numerical program for the computation of the system behaviour = simulation = prognosis based on a model + model assumptions + quantitative values (statistics) (= {O-O + Impl.} + {Instantiation} ) 7.Communication M2M: between data base (= information) and computation program (= numerics) = data exchange (data conversion by importing program) M2H: Reports, i.e. graphical and alphanumerical representation of results (output and system changes) but also input, model and model assumptions 8.Monitoring + Evaluation + Reporting

TU Dresden - Institut für Bauinformatik Folie-Nr.: 3 cf. Klauer 2005 Needed documents Already built elements New built elements Cooperation, Actor Control data Produced documents Knowledge, experience Resources IT Input data Output data Mechanism Conditions, Codes, Laws Project specifications, Client requirements Function Function, Input,…

TU Dresden - Institut für Bauinformatik Folie-Nr.: 4 Example 1 An excavator is digging a foundation pit. The process can start, when the construction site is prepared The process follows a excavation plan If the bucket is full, the platform will be turned to the truck If the platform has the correct position, the full bucket will be emptied. If the bucket is empty, the digging can continuous.

TU Dresden - Institut für Bauinformatik Folie-Nr.: 5 Example 1 An excavator is digging a foundation pit. The process can start, when the construction site is prepared The process follows a excavation plan

TU Dresden - Institut für Bauinformatik Folie-Nr.: 6 Example 1 If the bucket is full, the platform will be turned to the truck

TU Dresden - Institut für Bauinformatik Folie-Nr.: 7 Example 1 If the platform has the correct position, the full bucket will be emptied.

TU Dresden - Institut für Bauinformatik Folie-Nr.: 8 Example 1 If the bucket is empty, the digging can continuous.

TU Dresden - Institut für Bauinformatik Folie-Nr.: 9 Example 1 An excavator is digging a foundation pit. The process can start, when the construction site is prepared The process follows a excavation plan If the bucket is full, the platform will be turned to the truck If the platform has the correct position, the full bucket will be emptied. If the bucket is empty, the digging can continuous. The truck will be replaced, if it is fully loaded.

TU Dresden - Institut für Bauinformatik Folie-Nr.: 10 Example 1 The truck will be replaced, before it is fully loaded. Truck Position is fix

TU Dresden - Institut für Bauinformatik Folie-Nr.: 11 Bundling and Unbundling Unbundle arrow meaning A into arrow meanings B and C. C B A A B C Bundle arrow meaning B and C to form arrow A Bundling/Unbundling: The combining of arrow meanings into a composite meaning (bundling), or the separation of arrow meanings (unbundling), is expressed by arrow join and fork syntax.

TU Dresden - Institut für Bauinformatik Folie-Nr.: 12 Example 2 Use example 1 for describing the process of “Constructing Foundation Plate” A0 A-0 Parent Diagram Child Diagram More General More Detailed 0 This box is parent of next diagram A4 Top-Level Context Diagram Parent Diagrams Represent a Higher Level of Abstraction than Child Diagrams

TU Dresden - Institut für Bauinformatik Folie-Nr.: 13 Example 2 Use example 1 for describing the process of “Constructing Foundation Plate”

TU Dresden - Institut für Bauinformatik Folie-Nr.: 14 Example 2 Use example 1 for describing the process of “Constructing Foundation Plate”