SE Taiz EM 01a1 Taiz master program Engineering & Management Course Systems Engineering Introduction Lecturer : John L Simons

Slides:



Advertisements
Similar presentations
Systems Investigation and Analysis
Advertisements

25 February 2009Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department.
Lecture # 2 : Process Models
Presentation for the Management Study of the Code Enforcement Process City of Little Rock, Arkansas August 3, 2006.
ACCOUNTING INFORMATION SYSTEMS
1 CSSE 477: Swre Arch – This year’s course… Steve Chenoweth Tuesday, 11/8/11 Week 10, Day 2 Right – Sunset at the Louvre, in Paris From
The Role of Software Engineering Brief overview of relationship of SE to managing DSD risks 1.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
BRIDGING THE GAP BETWEEN THEORY AND PRACTICE IN MAINTENANCE D.N.P. (Pra) MURTHY RESEARCH PROFESSOR THE UNIVERSITY OF QUEENSLAND.
Administrivia Lifecycle Architecture (LCA) group assignment will go out later today. Informal feedback meetings with LCO groups EasyShare: Mon, 2:45pm-3:15pm,
Project Life Cycle Jon Ivins DMU. Introduction n Projects consist of many separate components n Constraints include: time, costs, staff, equipment n Assets.
Fundamentals of Information Systems, Second Edition
ESD.83Cory R. A. Hallam1 An Introduction to Systems Engineering The Art of Managing Complexity Presented By Cory R. A. Hallam B.Eng., M.Eng., ISU SSP,
1 Introduction to System Engineering G. Nacouzi ME 155B.
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Trade Study Training Need and Goals Need Consistent methodologies and practices performing trade studies Pros/cons, advantages/disadvantages, customer/management.
Queueing and Hand Simulation (Project 03). Queueing Models Probabilistic and stochastic models Important aspects: –Interarrival time –Service time –Waiting.
Software Architecture Quality. Outline Importance of assessing software architecture Better predict the quality of the system to be built How to improve.
EE496A Senior Design Project I Dr. Jane Dong Electrical and Computer Engineering.
Waniwatining Astuti, M.T.I
Systems Engineering of Software-Intensive Systems 1.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Engineering Systems of.
Software Integration and Documenting
Chapter : Software Process
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
CIS 321—IS Analysis & Design
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
UNIVIRTUAL FOR INSTRUCTIONAL DESIGN Versione 00 del 29/07/2009.
1 Chapter 2 Socio-technical Systems (Computer-based System Engineering)
Chapter 1 The Systems Development Environment
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
Software System Engineering: A tutorial
Embracing change with Extreme Programming Method Engineering Erik ten Brinke
SOME IMPORTANT FACTORS IN TEACHING SOFTWARE ENGINEERING COURSES Presenter: Jingzhou Li Depart of ECE, University of Calgary,
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Business Process Change and Discrete-Event Simulation: Bridging the Gap Vlatka Hlupic Brunel University Centre for Re-engineering Business Processes (REBUS)
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
PLANNING ENGINEERING AND PROJECT MANAGEMENT By Lec. Junaid Arshad 1 Lecture#03 DEPARTMENT OF ENGINEERING MANAGEMENT.
Chapter 15 Introduction to Systems Development. Learning Objectives Learn how information systems are developed Understand importance of managing SD process.
Systems Analysis and Design in a Changing World, Fourth Edition
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
ITEC0700/ NETE0501/ ISEC0502 Research Methodology#5 Suronapee Phoomvuthisarn, Ph.D.
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
1 Problem based Learning – The AAU Way A Work Shop given by: Mona Dahms Department of development and planning Fibigerstraede 11, DK Aalborg East.
BSBPMG404A Apply Quality Management Techniques Apply Quality Management Techniques Project Quality Processes C ertificate IV in Project Management
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Week 1 -Introduction IT2005 System Analysis & Design.
DESIGNING FOR COMPREHENSIVE SUPPORT THOMAS L. NONDORF THE BOEING COMPANY Oct. 22, 2003
Smart Home Technologies
Lecture 2. An Overview of Engineering Design JANUARY 2016 GE105 Introduction to Engineering Design College of Engineering King Saud University.
ISE Key Concepts Terminology –systems engineering: an interdisciplinary approach and means to enable the realization of successful systems. It.
LABORATORY MANAGEMENT Lecture 4. Planning at the Departmental Level The laboratory director must determine both laboratory goals and objectives, as well.
SmartPosition Customer Review and Feedback Presentation.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
SmartPosition Customer Review and Feedback Presentation.
SYSE 802 John D. McGregor Module 0 Session 3 Systems Engineering QuickView.
Principles of Information Security, Fourth Edition Chapter 1 Introduction to Information Security Part II.
 Tata consultancy services Production Planning WORK CENTERS.
Advanced Software Engineering Dr. Cheng
Requirements Engineering
Terminal Learning Objectives
The Systems Engineering Context
CHAPTER 9 (part a) BASIC INFORMATION SYSTEMS CONCEPTS
Presentation transcript:

SE Taiz EM 01a1 Taiz master program Engineering & Management Course Systems Engineering Introduction Lecturer : John L Simons

SE Taiz EM 01a2 Just an example ! Enhancing safety procedures for a small airfield (i) What is safety? What affects safety? What to include/exclude? How to define a solvable problem?

SE Taiz EM 01a3 Just an example ! Enhancing safety procedures for a small airfield (ii)  Rather than separate, well- defined functions, systems today interact in complex ways to perform operational missions. Seemingly minor design errors can cost lives.  Error Cost explosion >>>  The discipline and concepts of systems engineering provide ways to manage this complexity  System (re)design is the key Definition1 System design 3 Preliminary design 10 Detail design50 Development200 Use500

SE Taiz EM 01a4 SE Today overview  About the course setup  What are systems? What is SE?  Applicability  Methodology  List of cases  List of caput items for research  List of journal articles

SE Taiz EM 01a5 What is Systems Engineering? From INCOSE … an interdisciplinary approach and means to enable the realization of successful systems. It focuses on defining customer needs and required functionality early in the development cycle, documenting requirements, and then proceeding with design synthesis and system validation while considering the complete problem. Systems Engineering considers both the business and the technical needs of all customers with the goal of providing a quality product that meets the user needs …

SE Taiz EM 01a6 What are systems? From INCOSE … A “system” is a construct or a collection of different elements that together produce results not obtainable by the elements alone. The elements include hardware, software, facilities, people, policies and information. The results include system level requirements, properties, characteristiscs, functions, behavior and performance …

SE Taiz EM 01a7 The blinder of System Engineers ! Everything is a system that can be redesigned to perform better !

SE Taiz EM 01a8 The focus of SE SE (1) deals with real life problems of problem owners and (2) advocates systematic solving these problems by designing a system. This being the case, a university course cannot equally pay attention to these two aspects since lecturer and students practice SE methods and techniques under laboratory conditions.

SE Taiz EM 01a9 Yet another view on SE ! A more abstract view on SE emphasizes the translation process of a world problem Pw to a model problem Pm to a model solution Sm to a world solution Sw and the necessity to define these milestone products and their relations.

SE Taiz EM 01a10 The regulativ problem solving cycle ??? ? ! !!! PwPw PmPm SmSm SwSw

SE Taiz EM 01a11 The role of SE in the E&M master  Methods in this course elaborate on methods in courses OR, Methods engineering, Product design and Production systems.  The courses Strategic management and Methods of research reflect on methods of SE.  SE offers the student a range of models, methods and techniques which can be used in the individual master’s research.

SE Taiz EM 01a12 About the course setup (i)  Student working groups of 2-3 students  Self-activity with (E-)coaching  Group assignment covers model analysis for case, caput study, journal article review, methodology questions  Each group presents two times (for active audience) with feedback from lecturer  Report on time on target i.e. in this two week period

SE Taiz EM 01a13 About the course setup (ii) Daily four hours schedule  Introduction of theoretical key concept by lecturer and/or students  Groupwise case study (caput, journal, methodology) discussion  Presentation of results (case, caput,jornal article) by groups  Feedback on approach, methodology, real life SE organisations

SE Taiz EM 01a14 Cases (from the Blanchard book)  Failure mode effects and critically analysis FMECA  Fault tree analysis FTA  Reliability centered maintenance RCM  Maintenance task analysis MTA  Level of repair analysis LORA  Design evaluation of alternatives  Life cycle cost analysis LCCA. > If such a case is chosen the focus is on the managerial aspects of SE. The approach must be applied to a new problem (preferably real life example from organization of the student).

SE Taiz EM 01a15 Other cases (full text from lecturer)  Spread of sleeping sickness. Model (system of differential equations) of populations of active and non-active malaria flies and infected and non- infected humans in a rural area. Analysis of spreading speed and stability points.  Waiting queues for study loan processes. Simulation of queues based on arrival and processing assumptions. Analysis via random number generation. Modeling of university schedule quality.  Definition and evaluation of schedule quality. Least squares model fitting to survey results of perceived quality. See /1996/j.h.oldenkamp/ /1996/j.h.oldenkamp/ > If one of these last cases is chosen, the focus shifts to applying a mathematical method and reflecting on the applicability.

SE Taiz EM 01a16 SE is a team effort ! staring or doing

SE Taiz EM 01a17 Student’s goals for today (and tomorrow)  Form groups of 2 students. Each group chooses a case (use your preferences)  Each group must choose two presentation slots in the coming two weeks  Each group presents its problem definition, analysis, solution (1) and its caput or article (2) according to schedule  Schedule fixed after today  Choice of caput and journal article during days 1 and 2

SE Taiz EM 01a18 Presentation slots  Day 2 (first week) up to day 11 (second week)  Each day has two slots of max 20 minutes and max 10 slides  Each group chooses two slots (one for case, other for caput or article)  First come first serve  Quality groups choose early slots for optimal feedback

SE Taiz EM 01a19 Further plans for today (second hour)  Forming groups, choosing a case study, applying for presentation slots.  Start of group discussion. Anything goes.

SE Taiz EM 01a20 Further plans for today (third hour)  Continuation of group discussion. > At the end third hour each group must have at least one slide with three remarks/questions for plenary discussion (SE field, case, plans, caput, confusion...)

SE Taiz EM 01a21 Further plans for today (fourth hour)  Plenary discussion on items raised by groups  Feedback and tips for groups from lecturer

SE Taiz EM 01a22 SlotCase studyCaput/Article Day 2Group 01 … Day 3Group 05 … Day 4… Day 5… … Day 6…Group 03 Day 7… Day 8 Day 9 Day 10 Day 11