3231 Software Engineering By Germaine Cheung Hong Kong Computer Institute Lecture 1.

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.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
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.
CIS 375 Bruce R. Maxim UM-Dearborn
1 College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 2 Chapter 6 & 7 System.
Acquiring Information Systems and Applications
Enterprise Architecture
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 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
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.
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.
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,
CSI315 Web Applications and Technology Overview of Systems Development (342)
Chapter 2 The process Process, Methods, and Tools
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Succeeding as a Systems Analyst 2.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
ArchiMate Authors : eSchoolink Group - ITNLU. Contents 1. What’s ArchiMate ? 2. Why ArchiMate ? 3. Main Benefits of ArchiMate 4. Layers of ArchiMate 5.
The Challenge of IT-Business Alignment
Introduction to Software Engineering
1 Chapter 14 Architectural Design 2 Why Architecture? The architecture is not the operational software. Rather, it is a representation that enables a.
2131 Structured System Analysis and Design By Germaine Cheung Hong Kong Computer Institute Lecture 2 (Chapter 2) Information System Building Blocks.
1 Chapter 10/11 System Engineering AND Analysis Concepts and Principles.
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.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
 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.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
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.
Computer Science 340 Software Design & Testing Software Architecture.
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.
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.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 4: Analysis and Design Overview.
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.
CS 8532: Adv. Software Eng. – Spring 2009 Dr. Hisham Haddad , Monday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
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.
Reference Architecture for NASA’s Earth Science Data Systems Richard Ullman ES-DSWG-SPG Chair NASA/GSFC Code 586.
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
Software Engineering California State University, Fall 2008, Part I.
The Open Group Architecture Framework (TOGAF)
Chapter 6 System Engineering
Overview of System Engineering
CLINICAL INFORMATION SYSTEM
UML profiles.
CS 8532: Advanced Software Engineering
CHAPTER 9 (part a) BASIC INFORMATION SYSTEMS CONCEPTS
Software Engineering Practice: A Generic View
Presentation transcript:

3231 Software Engineering By Germaine Cheung Hong Kong Computer Institute Lecture 1

Miss Germaine Cheung Bachelor of Business Systems (Monash University – Australia) Master of Business Systems (Monash University – Australia) Master of Science in Information Technology in education (University of Hong Kong)

Assessment Method Assignment 120% Assignment 220% Quiz10% Examination 50%

Chapter 6 System Engineering

Elements of a computer-based system –Software –Hardware –People –Database –Documentation –Procedures Systems –A hierarchy of macro-elements

The Hierarchy

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.

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 Business Process Engineering

System Architectures Three different architectures must be analyzed and designed within the context of business objectives and goals: data architecture applications architecture technology infrastructure data architecture provides a framework for the information needs of a business or business function application architecture encompasses those elements of a system that transform objects within the data architecture for some business purpose technology infrastructure provides the foundation for the data and application architectures

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 modeling applications/procedures that address (BAA) and constraints of ISP Construction and delivery using CASE and 4GTs, testing

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

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

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

Product Engineering

Product Architecture Template

Architecture Flow Diagram

System Modeling with UML Deployment diagrams –Each 3-D box depicts a hardware element that is part of the physical architecture of the system Activity diagrams –Represent procedural aspects of a system element Class diagrams –Represent system level elements in terms of the data that describe the element and the operations that manipulate the data These and other UML models will be discussed later

Deployment Diagram

Activity Diagram

Class Diagram

The End