CO5021 Systems Development Week 1

Slides:



Advertisements
Similar presentations
Lecture # 2 : Process Models
Advertisements

1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Chapter 2 The Software Process
Information Systems Analysis and Design
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
The Role of Software Engineering Brief overview of relationship of SE to managing DSD risks 1.
Chapter 1 The Systems Development Environment
6.1 Copyright © 2014 Pearson Education, Inc. publishing as Prentice Hall Building Information Systems Chapter 13 VIDEO CASES Video Case 1: IBM: Business.
Lecture 13 Revision IMS Systems Analysis and Design.
Chapter 2 Succeeding as a Systems Analyst
System Development Environment 1/12/2015 © Abdou Illia MIS Spring 2015.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
1 Lecture 6 The Systems Analyst (Role and activities) Systems Analysis & Design Academic Year 2008/9.
Software Engineering Principles Chapter 3 From Software Engineering by I. Sommerville, Slide 1 project managementorganizing planning scheduling Learning.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
Continuation From Chapter From Chapter 1
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
Software Project Management Introduction to Project Management.
Information Systems in Organisations System Development: The Environment.
Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Software System Engineering: A tutorial
Object-Oriented Analysis and Design OVERVIEW. Objectives  Describe Information Systems  Explain the role of a systems analyst  Introduce object-oriented.
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.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
1 SYS366 Lecture 1: Introduction to Systems. 2 What is Software Development? Software Development implies developing some software – but it does not involve.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
SYSTEM ANALYSIS AND DESIGN 1. Topics to include.. WHAT IS SAD? NEED FOR SAD ROLE OF THE SYSTEM ANALYST QUALITIES OF SYSTEM CHARACTERISTICS FEASIBILITY.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
The Systems Development Life Cycle
Systems Analysis and Design in a Changing World, Fourth Edition
1 EE29B Feisal Mohammed EE29B: Introduction to Software Engineering Feisal Mohammed Ph: x3156.
MNP1163 (Software Construction).  SDLC and Construction Models  Construction Planning  Construction Measurement.
Modern Systems Analysis and Design Third Edition Chapter 2 Succeeding as a Systems Analyst 2.1.
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
1-1 © Prentice Hall, 2004 Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
Welcome to Software Project Management. CONVENTIONAL SOFTWARE MANAGEMENT The BEST and WORST thing about software is its flexibility. 1.Software development.
1 Systems Analysis and Design  Instructor: Dr. Andre Kushniruk  Class site:  Office: Ross N636 
Information Systems Development
Software Engineering Management
Chapter 1: Introduction to Systems Analysis and Design
CASE Tools and Joint and Rapid Application Development
Quality Management chapter 27.
Assistant Professor of Computer Science Washington State University
Software Project Management
It’s not all about the tool!
Chapter 2 Succeeding as a Systems Analyst
Succeeding as a Systems Analysts
IEEE Std 1074: Standard for Software Lifecycle
Manajemen Proyek Sistem Informasi
Design Thinking for Additive Manufacturing
Software Life Cycle Models
Systems Analysis and Design: What is it?
Software Engineering (CSI 321)
Software Project Management
Design and Implementation
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Baisc Of Software Testing
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
CS385T Software Engineering Dr.Doaa Sami
Succeeding as a Systems Analysts
CHAPTER 9 (part a) BASIC INFORMATION SYSTEMS CONCEPTS
Chapter 1: Introduction to Systems Analysis and Design
CSC 480 Software Engineering
Software Design Lecture : 5
Chapter 1: Introduction to Systems Analysis and Design
Presentation transcript:

CO5021 Systems Development Week 1 Introduction to System Development: Reducing the Risk of IT Development Failure

Some Formal Course Objectives To provide you with new ways of looking at information in the world in order to solve business problems; To introduce you to concepts and methods of System Analysis and design (SAD); To describe the systems development life cycle (SDLC); To teach you effective methods for gathering essential information during system analysis; To teach you effective methods for designing systems to solve problems effectively.

But Why Bother? ‘Software engineers’ (and other types of IT specialists) aren’t always popular with ‘real’ engineers e.g. civil, mechanical and electrical engineers They sometimes maintain that we aren’t as ‘professional’ as they are IT qualification schemes and professional bodies not as rigorous (yet) IT projects have a bad reputation for coming in behind schedule, over budget and off quality Other groups of engineers have had plenty of time and opportunity to learn from earlier mistakes, e.g. Tay Bridge Disaster (1879) Tacoma Narrows Bridge failure (1940) As a young profession, IT has some catching up to do…. Lives can depend on IT too… Formal analysis, design and testing methods are essential professional skills in IT

Characteristics of Systems Systems are made up of interrelated subsystems (e.g. a nuclear reactor is composed of boilers, reactor components etc.). Functional decomposition – dividing a system into components based on subsystems (which are in turn further divided into subsystems). System boundary – the separation between a system and its environment (which inputs and outputs cross). Automation boundary – separation between the automated part of system and the manual part.

“Systems” Thinking To identify something as a system, and describe it properly, we must first be able to identify:- characteristics and functions inputs and outputs to systems where the boundaries are (or should be) subsystems relationships among subsystems.

What is System Development? Systems Development: Activities that go into producing an information system to solve an organisational problem (or make the most of an opportunity) Systems analysis Systems design Programming Testing Conversion Production and maintenance.

System Development Analysis – understand information needs understanding and specifying in detail what an information system should do Design – define the system architecture (based on needs) specifying in detail how the parts of an information system should be implemented Implementation – the actual construction of the system

System Analysis Establishing information requirements Who needs what information, where, when, and how? Define objectives of new/modified system Detail the functions new system must perform Faulty requirements analysis is a leading cause of systems failure, and causes high systems development costs.

System Design Describe system specifications that will deliver functions identified during systems analysis Cover all managerial, organisational, and technological components of system solution.

Systems Design: Role of End-Users User information requirements drive system building; Users must have sufficient control over design process to ensure that system reflects their business priorities and information needs; Insufficient user involvement in design effort is major cause of system failure;