Chapter 9: Systems architecting: Principles (pt. 1) ISE 443 / ETM 543 Fall 2013.

Slides:



Advertisements
Similar presentations
S Y S T E M S E N G I N E E R I N G.
Advertisements

Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
Systems Engineering in a System of Systems Context
1 Lecture 1.2: Systems Engineering and Architecting Definitions & Relationships Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Security Extensions to the DOD Architecture Framework Kevin Richardson Information Assurance Lab Auburn University Computer Science and Software Engineering.
K.M. Corker, Ph.D.Industrial & Systems Engineering System Engineering ISE 222 Spring 2005 Notes & Course Materials
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,
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
Software Architecture in Practice
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
DATA FLOW DIAGRAMS IT 155.
Chapter 10: Architectural Design
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Engineering Systems of.
What is Software Architecture?
Dr. Howard Eisner Professor Emeritus, GWU SEDC CONFERENCE, April 2014 SYSTEM ARCHITECTING – VIEWS vs. FUNCTIONS vs. ALTERNATIVES.
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
Use Case Diagrams – Functional Models Chapter 5. Objectives Understand the rules and style guidelines for activity diagrams. Understand the rules and.
What is UML? What is UP? [Arlow and Neustadt, 2005] January 23, 2014
Chapter 7: Architecture Design Omar Meqdadi SE 273 Lecture 7 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Chapter 7: The 30 elements of systems engineering
Requirements Analysis
1 Lecture 3.1: Project Planning: Work Breakdown Structure (WBS) [SEF Ch 9] Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
The Architecture Business Cycle. Software Architecture Definition The software architecture of a program or computing system is the structure or structures.
Mod I Georgia Tech Aerospace Systems Engineering CC ppt Aerospace Systems Engineering Synthesis.
SOFTWARE DESIGN.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
10 Software Architecture CSCU 411 Software Engineering.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 6 System Engineering Overview of System Engineering.
Information Systems in Organizations 2
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
CPSC 372 John D. McGregor Module 3 Session 1 Architecture.
System Context and Domain Analysis Abbas Rasoolzadegan.
1 CMPT 275 High Level Design Phase Modularization.
CPSC 871 John D. McGregor Module 3 Session 1 Architecture.
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
CSC480 Software Engineering Lecture 10 September 25, 2002.
Systems Analysis and Design in a Changing World, Fourth Edition
1 Introduction to Design. 2 Outline Basics of design Design approaches.
Mahmut Ali GÖKÇEIndustrial Systems IEU Introduction to System Engineering ISE 102 Spring 2007 Notes & Course Materials Asst. Prof. Dr. Mahmut.
The Software Development Life Cycle: An Overview
Requirements Analysis
Information Systems in Organizations 2.1 Analyzing organizations as systems and processes.
1 PDS MC Requirements Process March 29, 2007 (v2).
Lecture VIII: Software Architecture
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Systems Architectures System Integration & Architecture.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
SOFTWARE DESIGN & SOFTWARE ENGINEERING Software design is a process in which data, program structure, interface and their details are represented by well.
Review Business Analyst vs. Systems Analyst – A Business Analyst identifies a problem and states – in business terms -- what the solution is. They define.
Chapter 9: Systems architecting: Principles (pt. 3) ISE 443 / ETM 543 Fall 2013.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Wrap up. Structures and views Quality attribute scenarios Achieving quality attributes via tactics Architectural pattern and styles.
Information Systems in Organizations 2.1 Analyzing organizations as systems and processes & Modeling Processes with Swimlane Diagrams.
Information Systems in Organizations 2
Elaboration popo.
Systems Analysis and Design in a Changing World, Fourth Edition
ITEC 3220A Using and Designing Database Systems
What is UML? What is UP? [Arlow and Neustadt, 2005] October 5, 2017
The Engineering Design of Systems: Models and Methods 3rd Edition
Unified Modeling Language
Lecture 9- Design Concepts and Principles
Part 3 Design What does design mean in different fields?
Overview of System Engineering
Application of Systems Engineering to Nuclear Fusion projects
Lecture 9- Design Concepts and Principles
CS 8532: Advanced Software Engineering
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
Systems Architecture & Design Lecture 3 Architecture Frameworks
Presentation transcript:

Chapter 9: Systems architecting: Principles (pt. 1) ISE 443 / ETM 543 Fall 2013

Architecting a large-scale complex system is the centerpiece of systems engineering 2 443/543– 9 Recall, from chapter 2, the essential elements of systems architecture: RRequirements MMission engineering RRequirements analysis/allocation FFunctional analysis/allocation AArchitectural design/synthesis SSystem analysis LLife-cycle costing RRisk analysis OOther system/subsystem considerations FFormulation of a preferred system architecture

What is a system architecture? NASA defines an architecture as: How functions are grouped together and interact with each other. Applies to the mission and to both inter- and intra-system, segment, element, and subsystem. Mission design is viewed in terms of 3 early phases 1. The conceptual design process: Prephase A 2. The mission analysis process: Phase A “The purpose of the Phase A study is to refine the mission and systems(s) requirements, determine a baseline mission configuration and system architecture, identify risks and risk mitigation strategies, identify the “best” candidates, and select one.” 3. The definition process: Phase B 3 443/543– 9

The DoD provides 3 different views of system architecture  The operational architecture view is a description of the tasks and activities, operational elements, and information flows  The systems architecture view is a description, including graphics, of systems and interconnections  The technical architecture view is the minimal set of rules governing the arrangement, interaction, and interdependence of system parts or elements, whose purpose is to ensure that a conformant system satisfies a specified set of requirements And provides 6 steps for building an architecture  See page /543– 9

The IEEE definition is simple... A structure of components, their relationships, and the principles and guidelines governing their design and evolution over time We can define the process of system architecture using elements 3-10 of the 30 elements of SE (refer back to – ):  Requirements analysis/allocation (element 3)  Functional analysis/decomposition (element 4)  Architecture design/synthesis (element 5)  Alternatives analysis/evaluation (element 6)  Technical performance measurement (element 7)  Life-cycle costing (element 8)  Risk analysis (element 9)  Concurrent engineering (element 10) 5 443/543– 9

Your turn... Select one of the systems architectures illustrated in the chapter  Identify the functional decomposition; that is, state “function xxx is decomposed into the following subfunctions....”  Identify the characteristics of a functional decomposition as illustrated in this example 6 443/543– 9

Characteristics of functional decomposition Physical facilities at the top level, decomposed to functions and/or other physical facilities External systems/functions differentiated from internal systems/functions Use of subsections to group common elements of the system – layering of the elements to represent multiple elements of the same type Functions/subfunctions connected by arrows indicating direction of information flow Coding of different types of connections (data types) 7 443/543– 9

Your turn (again)... Look at problem 9.3 on page 301 As a group, agree on the major functions of a personal computer system Begin the functional decomposition The complete architecture is due on Tuesday, October 29.  This is to be an INDIVIDUAL assignment.  You may (but you are not required to) use the work you did in the group as a starting point, but the final architecture should be your own work.  The final product must be a graphical representation /543– 9