LECTURE 29. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

Slides:

Advertisements

Similar presentations

10 Golden Questions for Concept Exploration & Development Dr. Dan C. Surber (317)

Advertisements

Mahmut Ali GÖKÇEIndustrial Systems Engineering Lecture 2 System Identification ISE102 Spring 2007.

Software Quality Assurance Plan

Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz

1 Chapter 2: Product Development Process and Organization Introduction Importance of human resources: Most companies have similar technology resources.

USING ORG-MASTER FOR KNOWLEDGE BASED ORGANIZATIONAL CHANGE Dmitry Kudryavtsev – Lev Grigoriev – Valentina Kislova –

Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 1998 by Carnegie Mellon.

Introduction to Software Testing Chapter 9.3 Challenges in Testing Software Test Criteria and the Future of Testing Paul Ammann & Jeff Offutt

COURSE “SYSTEM DESIGN: STRUCTURAL APPROACH” DETC Inst. for Information Transmission Problems Russian Academy of Sciences, Moscow , Russia.

1 SYS366 Week 1 - Lecture 2 How Businesses Work. 2 Today How Businesses Work What is a System Types of Systems The Role of the Systems Analyst The Programmer/Analyst.

Capturing the requirements

1 IS112 – Chapter 1 Notes Computer Organization and Programming Professor Catherine Dwyer Fall 2005.

1 Software Testing and Quality Assurance Lecture 1 Software Verification & Validation.

University of Jyväskylä – Department of Mathematical Information Technology Computer Science Teacher Education ICNEE 2004 Topic Case Driven Approach for.

CSC230 Software Design (Engineering)

Advanced Manufacturing Laboratory Department of Industrial Engineering Sharif University of Technology Session #6.

WPI Center for Research in Exploratory Data and Information Analysis From Data to Knowledge: Exploring Industrial, Scientific, and Commercial Databases.

LECTURE 1. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow Inst.

©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements l.

Multi-Agent Model to Multi-Process Transformation A Housing Market Case Study Gerhard Zimmermann Informatik University of Kaiserslautern.

7.1 The Software Engineering Discipline 7.2 The Software Life Cycle 報告者 : 林建任.

Free Mini Course: Applying SysML with MagicDraw

S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.

LECTURE 5-6. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

1 CS 456 Software Engineering. 2 Contents 3 Chapter 1: Introduction.

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.

European Network of Excellence in AI Planning Intelligent Planning & Scheduling An Innovative Software Technology Susanne Biundo.

Information systems defined small enterprise characteristics Information needs of the small enterprise the systems development life cycle computer information.

LECTURE 28. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

2 Systems Architecture, Fifth Edition Chapter Goals Describe the activities of information systems professionals Describe the technical knowledge of computer.

Software Requirements Engineering CSE 305 Lecture-2.

1 ENGINEERING DESIGN AND PRODUCTION. 2 What is design? To create something that has never been. To create something that has never been. To pull together.

LECTURE 8-9. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements.

LECTURE (compressed version). Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering.

OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.

2007 Introduction to System Engineering 1 ECET/CPET 491 Senior Design Project II Intro to System Engineering Reference: System Engineering Management,

LECTURE 19. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

LECTURE Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 6 System Engineering Overview of System Engineering.

LECTURE 13. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.

LECTURE 26. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

Towards Communication Network Development (structural systems issues, combinatorial models) Mark Sh. Levin Inst. for Inform. Transmission Problems, Russian.

Model Checking and Model-Based Design Bruce H. Krogh Carnegie Mellon University.

LECTURE 4. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow Inst.

University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 systems analysis 1 what is systems analysis? preparation of the system’s requirements/definition,

LECTURE 16. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.

STUDENT RESEARCH PROJECTS IN SYSTEM DESIGN Inst. for Information Transmission Problems Russian Academy of Sciences, Moscow , Russia

LECTURE Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

LECTURE 2-3. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

ANU comp2110 Software Design lecture 8 COMP2110 Software Design in 2004 lecture 8 Software Architecture 1 of 2 (design, lecture 3 of 6) Goal of this small.

LECTURE 10. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

Advanced Manufacturing Laboratory Department of Industrial Engineering Sharif University of Technology Session #19.

LECTURE 27. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

LECTURE Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow.

LECTURE 7. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow Inst.

Software Engineering Lecture 10: System Engineering.

Toward product architecture oriented requirements analysis for product line development in systems engineering Kei Kurakawa Nara Institute of Science and.

Introduction. System Design Hardware/Software Platform Selection Software Architectures Database Design Human-Computer Interaction (HCI) Interface Object.

1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.

TOWARDS FOUR-LAYER FRAMEWORK OF COMBINATORIAL PROBLEMS

BSA 385 Week 3 Individual Assignment Frequent Shopper Program Part 2 Check this A+ tutorial guideline at

Chapter 1 Computer Technology: Your Need to Know

Session 2 Dr. Dan C. Surber, ESEP

Overview of System Engineering

Software Engineering Lecture #14.

CS 8532: Advanced Software Engineering

System architecture, Def.

Presentation transcript:

LECTURE 29. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow Inst. of Physics and Technology (University) / Mark Sh. Levin Inst. for Information Transmission Problems, RAS Nov. 26, 2004 PLAN: 1.Requirements engineering: preliminaries 2.Types of requirements 2.Additions 3.Systems under analysis 4.Models

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T OLD RUSSIAN ENGINEEIRNG EXPERIENCE: NB!!!

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T OLD RUSSIAN ENGINEEIRNG EXPERIENCE: NB!!! WEST EXPERIENCE: 1.Ralph R. Young, The Requirements Engineering Handbook, Artech House, 2004 (Carnegie Mellon Univ.) 2.S. Robertson, J. Robertson, Mastering the Requirements Process. Addison-Wesley, K.E. Wiegers, Software Requirements. 2 nd ed., Microsoft Press 2003.

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T OLD RUSSIAN ENGINEEIRNG EXPERIENCE: NB!!! WEST EXPERIENCE: 1.Ralph R. Young, The Requirements Engineering Handbook, Artech House, 2004 (Carnegie Mellon Univ.) 2.S. Robertson, J. Robertson, Mastering the Requirements Process. Addison-Wesley, K.E. Wiegers, Software Requirements. 2 nd ed., Microsoft Press JOURNALS: “Requirement Engineering” (Springer), etc.

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T OLD RUSSIAN ENGINEEIRNG EXPERIENCE: NB!!! WEST EXPERIENCE: 1.Ralph R. Young, The Requirements Engineering Handbook, Artech House, 2004 (Carnegie Mellon Univ.) 2.S. Robertson, J. Robertson, Mastering the Requirements Process. Addison-Wesley, K.E. Wiegers, Software Requirements. 2 nd ed., Microsoft Press JOURNALS: “Requirement Engineering” (Springer), etc. CONFERENCES: IEEE Requirement Engineering Conference, etc.

1.Preliminaries: Layers (product, requirements, standards) R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T 1.Standards 2.Requirements 3.System (product, product family, platform)

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T Neighbor disciplines: 1.Systems engineering (& life cycle engineering) 2.Strategic management 3.Marketing 4.Forecasting 5.Knowledge engineering (acquisition of experience)

1.Preliminaries: Main Roles and Responsibility (system testing) TESTER: * model checking * etc.. DESIGNER: * unit test * integration test USER(S): * functional test SYSTEM EXPERT(SPECIALIST) : * system performance * system safety * system life cycle * new requirements * new generations * new standards

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T SYSTEM Requirements specifications Designer User Customers System specialist

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T SYSTEM Requirements specifications Designer User Customers System specialist Personnel with skills (LITERACY)

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T SYSTEM Requirements specification

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T SYSTEM Requirements engineering process (special project) NB! Requirements specification

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T Requirements engineering process (special project) Requirements specification SOURCES: 1.Information from users, etc. 2.Previous experience (e.g., design, manufacturing) 3.Analogue-Systems 4.Use Cases

1.Preliminaries R & D t ManufacturingTestingMarketing Utilization & Maintenance Recycling 0 T Requirements engineering process (special project) Requirements specification SOURCES: 1.Information from users 2.Previous experience (e.g., design, manufacturing) 3.Analogue-Systems 4.Use cases PROBLEMS & TOOLS (TECHNIQUES): 1.System analysis 2.Discovering 3.Acquisition of knowledge, skills, experience 4.Structuring & Integration 5.Modeling & Representation 6.Analysis of dynamics 6.Testing 7.Forecasting

2.Types of requirements (a hierarchical system of requirements) TYPES: 1.Business requirements 2.User’s requirements 3.High-level or system requirements 4.Functional requirements (things the system must do) 5.Non-functional requirements (properties the system must have) 6.Design requirements / design constraints 7.Manufacturing constraints 8.Performance requirements 9.Interface requirements (with other systems) 10.Qualification requirements 11.Logistics requirements 12.Environmental requirements 13.System, subsystem and component requirements 14.Reusing requirements ETC.

3.Additions ADDITIONS: 1.Criteria for evaluation of requirements 2.Prototyping 3.Scenarios 4.Reusing requirements

3.System under analysis (hierarchical layers; product, product family) OBJECT & HIERARCHY 1.System and / or system part (component, unit) 2.System state, group of states, state chart 3.System function, function cluster, digraph of function clusters

3.System under analysis (hierarchical layers; product, product family) OBJECT & HIERARCHY 1.System and / or system part (component, unit) 2.System state, group of states, state chart 3.System function, function cluster, digraph of function clusters 1.SYSTEM / PRODUCT 2.PRODUCT FAMILY 3.PLATFORM

3.System under analysis (scenarios) SCENARIOS: 1.STRUCTURE (e.g., chain, tree) of system states, functions 2.Qualitative scenarios 3.Integration of use cases & forecasting

3.System under analysis (scenarios) SCENARIOS: 1.STRUCTURE (e.g., chain, tree) of system states, functions 2.Qualitative scenarios 3.Integration of use cases & forecasting MODELS: 1.Entity relationship 2.State transition model 3.Entity relationship & state transition diagrams

4.Models MODELS: I.HIERARCHY OF REQUIREMENTS 1.Hierarchy of information 2.Integration of information (fusion), etc. II.SCENARIOS 1.Coneptual maps 2.Graph models, etc. III.DYNAMICAL MODELING 1.Simulation 2.Testing, etc.