1 Chapter 6 System Engineering. 2 System Engineering What is a computer-based system? A set or arrangement of elements that are organized to accomplish.

Slides:



Advertisements
Similar presentations
Business process engineering: an overview The goal of business process engineering (BPE) is to define architectures that will enable a business to use.
Advertisements

System Engineering based on Chapter 6 - Software Engineering: A Practitioner’s Approach, 6/e copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
TCS2411 Software Engineering1 System Engineering and Analysis “What is the role of the software product?”
CHAPTER 10 & 13 IS within the Organization & Acquiring IS and Applications.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
CATEGORIES OF INFORMATION There are three main categories of business information,and these are related to the purpose for which the information is utilized.
Requirements Analysis Concepts & Principles
Analysis Concepts and Principles
Business Performance Management (BPM)
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 Objective of today’s lesson S oftware engineering occurs as a consequence of a process called system engineering. Instead of concentrating solely on.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
1 Lecture 3 Requirement Analysis System Analysis Concepts Modeling Techniques.
The database development process
CIS 375 Bruce R. Maxim UM-Dearborn
Acquiring Information Systems and Applications
Enterprise Architecture
Chapter 7 Structuring System Process Requirements
Architectural Design.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Chapter 10 Architectural Design
Chapter 4 Requirements Engineering
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 COSC 4406 Software Engineering COSC 4406 Software Engineering Haibin Zhu, Ph.D. Dept. of Computer Science and mathematics, Nipissing University, 100.
Chapter 6 System Engineering
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Chapter 2 The process Process, Methods, and Tools
Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
1M.Sc.(I.T.), VNSGU, Surat. Structured Analysis Focuses on what system or application is required to do. It does not state how the system should be implement.
Introduction to Software Engineering
1 Chapter 10/11 System Engineering AND Analysis Concepts and Principles.
3231 Software Engineering By Germaine Cheung Hong Kong Computer Institute Lecture 1.
Architectural Design Based on Chapter 11 of the textbook [SE-8] Ian Sommerville, Software Engineering, 8t h Ed., Addison-Wesley, 2006 and on the Ch11 PowerPoint.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 6 System Engineering Overview of System Engineering.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
 Before software can be engineered, the system must be understood.  The overall objective of the system must be determined, the role of the system elements.
Database Development Process Lecture # 02 Instructor: Engr. Sana Ziafat.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 Supplementary Slides for Software Engineering: A Practitioner's Approach, 5/e Supplementary Slides for Software Engineering: A Practitioner's Approach,
Architectural Design Introduction Design has been described as a multistep process in which representations of data and program structure,
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
4+1 View Model of Software Architecture
Chapter 13 설계 개념 Architectural Design 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim for the book “Software Engineering: A Practitioner’s.
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
1 Chapter 10 System Engineering. 2 Computer-Based System  A computer-based system is a set or arrangement of elements that are organized to accomplish.
1-1 © Prentice Hall, 2004 Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Software Engineering Lecture 10: System Engineering.
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
Programming Techniques Lecture 5 Software Engineering Practice Based on: Software Engineering, A Practitioner’s Approach, 6/e, R.S. Pressman Software Engineering.
1 System Engineering. 2  Elements of a computer-based system 1.Software 2.Hardware 3.People 4.Database 5.Documentation 6.Procedures  Elements of a computer-based.
Chapter 2 Bring systems into being April Aims of this Lecture To explain what is “System Life-Cycle” To understand the systems engineering process.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Michael J. Novak ASQ Section 0511 Meeting, February 8, 2017
CGS 2545: Database Concepts Fall 2010
Software Engineering California State University, Fall 2008, Part I.
Chapter 13: Setting a Direction for Information Resources
Online Shopping APP.
CHAPTER 2 CREATING AN ARCHITECTURAL DESIGN.
The Open Group Architecture Framework (TOGAF)
Chapter 6 System Engineering
Overview of System Engineering
CS 8532: Advanced Software Engineering
Presentation transcript:

1 Chapter 6 System Engineering

2 System Engineering What is a computer-based system? A set or arrangement of elements that are organized to accomplish some predefined goal by processing information Elements of a computer-based system Software Hardware People Database Documentation Procedures Systems A hierarchy of macro-elements

3 The Hierarchy e.g., School Administrative Information System

4 System Modeling Define the processes that serve the needs of the view under consideration. Represent the behavior of the processes and the assumptions on which the behavior is based. Explicitly define both exogenous and endogenous input to the model. exogenous inputs link one constituent of a given view with other constituents at the same level of other levels; endogenous input links individual components of a constituent at a particular view. Represent all linkages (including output) that will enable the engineer to better understand the view.

5 Business Process Engineering (BPE)  Uses an integrated set of procedures, methods, and tools to identify how information systems can best meet the strategic goals of an enterprise  Focuses first on the enterprise and then on the business area  Creates enterprise models, data models and process models  Creates a framework for better information management distribution, and control

6 System Architectures Three different architectures must be analyzed and designed within the context of business objectives and goals: data architecture applications architecture technology infrastructure

7 System Architectures (cont.) Data architecture provides a framework for the information needs of a business or business function i.e., database schema Application architecture encompasses those elements of a system that transform objects within the data architecture for some business purpose i.e., programs Technology infrastructure provides the foundation for the data and application architectures i.e., hardware, software,

8 The BPE Hierarchy Information strategy planning (ISP)  strategic goals defined  success factors/business rules identified  enterprise model created Business area analysis (BAA)  processes/services modeled  interrelationships of processes and data Application Engineering  a.k.a... software engineering  modeling applications/procedures that address (BAA) and constraints of ISP Construction and delivery  using CASE and 4GTs, testing

9 The BPE Hierarchy (cont.)

10 Information Strategy Planning Management issues  define strategic business goals/objectives  isolate critical success factors  conduct analysis of technology impact  perform analysis of strategic systems Technical issues  create a top-level data model  cluster by business/organizational area  refine model and clustering

11 Defining Objectives and Goals Objective—general statement of direction Goal—defines measurable objective: “reduce manufactured cost of our product”  Subgoals:  decrease reject rate by 20% in first 6 months  gain 10% price concessions from suppliers  re-engineer 30% of components for ease of manufacture during first year Objectives tend to be strategic while goals tend to be tactical

12 Business Area Analysis Define “naturally cohesive groupings of business functions and data” (Martin) Perform many of the same activities as ISP, but narrow scope to individual business area Identify existing (old) information systems / determine compatibility with new ISP model  define systems that are problematic  defining systems that are incompatible with new information model  begin to establish re-engineering priorities

13 The BAA Process sales acct manufacturing QC eng’ring distribution admin. Data Model Process Decomposition Diagram Matrices e.g., entity/process matrix Process Flow Models

14 Product Engineering Goal: To translate customer’s desire into a working product Consist of four system components Software Hardware Data People

15 Product Engineering (cont.)

16 Product Architecture Template Proposed by Hatley and Pirbhai, also known as Hatley- Pirbhai modeling

17 Architecture Flow Diagram (AFD)

18 SFD Hierarchy A B C Top level AFD AFD for B AFD for A AFD for C

19 System Modeling with UML Deployment diagrams (Modeling hardware) Each 3-D box depicts a hardware element that is part of the physical architecture of the system Activity diagrams (Modeling software) Represent procedural aspects of a system element Class diagrams (Modeling data) Represent system level elements in terms of the data that describe the element and the operations that manipulate the data Use-case diagrams (Modeling people) Illustrate the manner in which an actor interacts with the system *These and other UML models will be discussed later

20 Deployment Diagram

21 Activity Diagram

22 Class Diagram

23 Use-Case Diagram Request bar code Request shunt control status Request box processing report Update product database Run system diagnostics CLSS operator