Systems Analysis & Design N106

Slides:



Advertisements
Similar presentations
Systems Analysis and Design
Advertisements

Multimedia Specification Design and Production 2013 / Semester 1 / week 7 Lecturer: Dr. Nikos Gazepidis
1 Systems & Systems Analysis Yale Braunstein School of Information Management & Systems UC Berkeley.
Designing and Developing Decision Support Systems Chapter 4.
Systems Analysis and Design With UML 2
ZEIT2301- Design of Information Systems
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Slide 1 INTRODUCTION Chapter 1. Slide 2 Key Ideas The primarily goal of a system is to create value for the organization. Many failed systems were abandoned.
System Analysis and Design (SAD )
Introduction to System Analysis and Design
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
Slide 1 INTRODUCTION Chapter 1. Slide 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Systems.
Lab 1 Introduction Project Definition. Introduction and Project definition 2 Objective To give the Student an overview of the Lab Environment and tools.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
BIS310: Structured Analysis and Design Introduction and Systems Planning Week 1.
1 Introduction Chapter 1. 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan.
Lecture # 04 & 05 CS314 Introduction To Software Development Software Development Process (SDP) Instructor :Muhammad Janas khan
1 INTRODUCTION Chapter 1 Alan Dennis, Barbara Wixom, and David Tegarden John Wiley & Sons, Inc. Slides by Fred Niederman Edited by Solomon Negash.
Systems Analysis and Design CHAPTER 1
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Chapter 1: Introduction to Systems Analysis and Design
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
CSIS 3600 Systems Analysis and Design The Systems Development Life Cycle Intellectual Property of Dr. Meg Murray, dated August 2002.
Introduction to Systems Analysis and Design
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan.
Large Scale Systems Design G52LSS
1 - 1 Systems Analysis and Design, Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
SYSTEM ANALYSIS AND DESIGN SAFAA S.Y. DALLOUL. INTRODUCTION.
Systems Development Life Cycle
Chapter 2: System Development Methodologies & Automated Systems 1.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan.
ISTM 280, GWU1 Introduction to Systems Analysis and Design Lecture 1 Courtesy Subhasish Dasgupta.
Introduction To System Analysis and Design
Introduction to Systems Analysis and Design
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Chapter 1: Introduction to Systems Analysis and Design
Business System Development
Chapter 1 The Systems Development Environment
Software Life Cycle “What happens in the ‘life’ of software”
Chapter 1 The Systems Development Environment
Introduction to System Analysis and Design
Systems & Systems Analysis
Systems Analysis and Design
Chapter 1 The Systems Development Environment
Systems Analysis and Design With UML 2
Systems Analysis and Design
Systems Analysis and Design Third Edition
Chapter 1 The Systems Development Environment
Information Systems Development
Fereshte Shabany Moghadam
Software life cycle models
CIS 210 Systems Analysis and Development
CS101 Introduction to Computing Lecture 20 SW Development Methodology
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Systems Analysis and Design Third Edition
Chapter 1: Introduction to Systems Analysis and Design
Systems Analysis and Design With UML 2
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Chapter 1 The Systems Development Environment
SDLC (Software Development Life Cycle)
Chapter 1: Introduction to Systems Analysis and Design
Week 10 Systems Development
Presentation transcript:

Systems Analysis & Design N106 Sri Lanka Institute of Information Technology BSc (IT) – First Year Systems Analysis & Design N106

Lecture 1 Introduction

Course Identification Lecturer in charge – Nideshika Ellepola E-mail – nideshika.e@sliit.lk Meeting lecturer on Wednesday 2.30 PM to 3.30 PM

Unit Objective To provide students an overall knowledge on the Software Development Life Cycle (SDLC) and to facilitate a detailed learning of the main phases which are, Planning Analysis Design Implementation

Unit Learning Outcomes On completion of the unit you should know, The phases and the sub activities of the SDLC Should also have a good knowledge of the different mechanisms used in the sub activities Able to compare and select an appropriate mechanism according to the given situation

Unit Assessment Criteria Mid term examination – 30% Group Project – 15% Lab Attendance & Performance – 05% Final Examination – 50% To pass this unit, students are required to get at least 45% of the marks for the midterm, the assignment and the final examination.

Unit Outline - Lectures Week Lecture Assignments Week 1 Introduction to SAD Week 2 Project Initiation Group Registration Week 3 Project Management Week 4 Systems Analysis Week 5 Gathering Information Assignment 1 Week 6 Process Modeling Week 7 Mid Term Examination Week 8 System Design Week 9 Architecture Design Week 10 User Interface Structure Design Week 11 User Interface Design Components Assignment 2 Week 12 Program Design Week 13 Construction & Installation Week 14 Revision

Unit Outline - Labs Week Lecture Week 2 Introduction to Microsoft Visio 2010 Week 3 Introduction to Microsoft Project 2010 Week 4 Exercises on Microsoft Project Week 5 Compiling a survey for information gathering Week 6 DFD Tutorial 1 & 2 Week 7 Mid Term Examination Week 8 DFD Tutorial 3 & 4 Week 9 DFD Tutorial 5 & 6 Week 10 DFD Tutorial 7 & 8 Week 11 DFD – Past Papers Week 12 Structure Chart Tutorial 1 Week 13 Structure Chart Tutorial 2 & 3 Week 14 Structure Chart - Past Papers

References Systems Analysis & Design By – Alan Dennis & Barbra Haley Wixom

Attention Attendance for the lecture + tutorial sessions is compulsory. (80% of attendance is compulsory) Lab Attendance is compulsory and marks will be given for performance. Plagiarism is prohibited. You will be penalized.

Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization. The primarily goal is to create value for the organization.

Key Ideas The systems analyst is a key person analyzing the business, identifying opportunities for improvement, and designing information systems to implement these ideas. It is important to understand and develop through practice the skills needed to successfully design and implement new information systems.

THE SYSTEMS DEVELOPMENT LIFE CYCLE

Major Attributes of the Lifecycle The project – Moves systematically through phases where each phase has a standard set of outputs Produces project deliverables Uses deliverables in implementation Results in actual information system Uses gradual refinement

Project Phases Planning (Why build the system?) Analysis (Who, what when, where will the system be?) Design (How will the system work?) Implementation (System delivery)

A “Simple” Process for Making Lunch

Planning Identifying business value Analyze feasibility Develop work plan Staff the project Control and direct project

Analysis Analysis Information gathering Process modeling Data modeling

Design Physical design Architectural design Interface design Database and file design Program design

Implementation Construction Installation

Processes and Deliverables Product Project Plan System Proposal System Specification New System and Maintenance Plan Planning Analysis Design Implementation

SYSTEM DEVELOPMENT METHODOLOGIES

What Is a Methodology? A formalized approach or series of steps Examples Process-Centered Data-Centered Object-Oriented

Waterfall Development Method

Pros and Cons of the Waterfall Method Identifies systems requirements long before programming begins Design must be specified on paper Long time between system proposal and delivery of new system

Alternatives to the SDLC Parallel Development Rapid Application Development (RAD) Phased Development Prototyping Spiral Development Packaged Systems

Parallel Development Method

Pros and Cons of Parallel Development Reduces Scheduled Time Less Chance of Rework Still Uses Paper Documents Sub-projects May Be Difficult to Integrate

Rapid Application Development CASE tools JAD sessions Fourth generation/visualization programming languages Code generators

Three RAD Categories Phased development Prototyping A series of versions Prototyping System prototyping Throw-away prototyping Design prototyping

Phased Development

Phased Development Advantages Disadvantage Identification of important requirements. Quickly get a useful system to the users. Disadvantage Difficult to include all the important features in the version 1.

How Prototyping Works

Prototyping Advantages Disadvantage Have a system in place for the user at an early stage. Ability to quickly refine real requirements. Reassures the client. Disadvantage Requirements have to be analyzed quickly and carefully.

Throwaway Prototyping

Throwaway Prototyping Advantages Resolve technical issues. Enables the users to understand the system. Disadvantage Do not make use of the prototype.

Criteria for Selecting the Appropriate Methodology Clear user requirements Familiar technology Complexity Reliability Time schedule Schedule visibility

TEAM ROLES AND SKILLS

Information Systems Roles Business analyst System analyst Infrastructure analyst Change management analyst Project manager

Summary The Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and Implementation There are five major development methodologies: the waterfall method, the parallel development method, the phased development method, system prototyping and design prototyping. There are five major team roles: business analyst, systems analyst, infrastructure analyst, change management analyst and project manager.

Thank you! Q & A