Introduction Complex and large SW. SW crises. 1950 1960 1970 1980 1990 2000 Expensive HW. Custom SW. Batch execution Structured programming Product SW.

Slides:



Advertisements
Similar presentations
Modern Systems Analyst and as a Project Manager
Advertisements

Systems Investigation and Analysis
Chapter 1: The Context of SA&D Methods
Systems Analysis and Design, 7e Kendall & Kendall
Chapter 1 Assuming the Role of the Systems Analyst
Systems Analysis and Design, 7e Kendall & Kendall
1 SYS366 Week 1 - Lecture 2 How Businesses Work. 2 Today How Businesses Work What is a System Types of Systems The Role of the Systems Analyst The Programmer/Analyst.
Chapter 1 Assuming the Role of the Systems Analyst
Chapter 3 Managing the Information Systems Project
Systems Analysis and Design Kendall & Kendall Sixth Edition
Systems Analysis and Design Kendall and Kendall Fifth Edition
Chapter 2 Topics –Context-Level DFD –Entity-Relationship Diagrams.
Integrating New Technology Phases of analysis and design
Fundamentals of Information Systems, Second Edition
Systems Development Life Cycle
Chapter 1 Assuming the Role of the Systems Analyst
1-1 © Prentice Hall, 2007 Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Chapter 4 Determining Feasibility and Managing Analysis and Design Activities Systems Analysis and Design Kendall & Kendall Sixth Edition.
© 2008 Pearson Prentice Hall Project Management Systems Analysis and Design, 7e Kendall & Kendall 3.
Jump to first page 30/06/ Chapter 1 System Development Environment.
Introduction to Systems Analysis and Design
Lecture Note 4 Managing Analysis and Design Activities
Succeeding with Technology Systems Development An Overview of Systems Development Tools and Techniques for Systems Development Systems Investigation Systems.
©2008 Pearson Prentice Hall Project Management Systems Analysis and Design, 7e Kendall & Kendall CH#3.
CIS 321—IS Analysis & Design Chapter 1: The World of the Modern Systems Analyst.
Computers Are Your Future Eleventh Edition Chapter 13: Systems Analysis & Design Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall1.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
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,
Information Systems Analysis and Design
Introduction to Systems Development Life Cycle
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Chapter 10 Information Systems Analysis and Design
Chapter 1 Assuming the Role of the Systems Analyst Systems Analysis and Design Kendall & Kendall Sixth Edition.
Using Information Technology Pertemuan 12 Chapter 11 Information Systems.
Using Information Technology Chapter 11 Information Systems.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
1 Determining Feasibility and Managing Analysis and Design Activities.
SYSTEMSDESIGNANALYSIS 1 Chapter 3 Feasibility Jerry Post Copyright © 1997.
©2008 Pearson Prentice Hall Project Management Systems Analysis and Design, 7e Kendall & Kendall 3.
Systems Analysis and Design
The Project Management Life Cycle. What is the Project Management Life Cycle? A project life cycle simply includes the necessary steps, from beginning.
Computers Are Your Future Tenth Edition Chapter 13: Systems Analysis & Design Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall1.
INFORMATION SYSTEMS FOR MANAGEMENT. Agenda Information system project Organization analysis.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Lecture 10 8/10/15.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
BTS330: Business Requirements Analysis using OO Lecture 6: Systems.
Chapter 1 Introduction to Systems Design and Analysis Systems Analysis and Design Kendall and Kendall Sixth Edition.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
ANALISA & PERANCANGAN SISTEM Disusun Oleh : Dr. Lily Wulandari Program Pasca Sarjana Magister Sistem Informasi Universitas Gunadarma.
1-1 © Prentice Hall, 2004 Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Chapter 1 Assuming the Role of the Systems Analyst.
HO CHI MINH CITY NATIONAL UNIVERSITY HO CHI MINH CITY UNIVERSITY OF TECHNOLOGY SYSTEM ANALYSIS AND DESIGN LECTURER: Nguyen Thanh Tung.
©2008 Pearson Prentice Hall Assuming the Role of the Systems Analyst Systems Analysis and Design, 7e Kendall & Kendall CH#1.
Systems Development Life Cycle
Project planning The systems life cycle.
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design
Systems Analysis and Design Kendall and Kendall Fifth Edition
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Systems Analysis and Design Kendall and Kendall Fifth Edition
Systems Development Life Cycle
Systems Analysis and Design Kendall and Kendall Fifth Edition
Chapter 3 Determining Feasibility and Managing Analysis and Design Activities 1.
Systems Development An Overview of Systems Development
Presentation transcript:

Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW. Data orientation Expert systems AI distributed systems parallel programming

Introduction Software Engineering is concerned with theories, methods and tools needed to develop high quality software products in a cost effective way. Cost effective: –limited resources. –Time schedule.

System Development Life Cycle

Software Development Life Cycle Maintenance is an ongoing process over the system life 60% of the time is spent on maintenance and 40% on the development –Correct errors –Add new features (business changes) –Adapt to environment changes Cost of correcting errors increase as you move in the life cycle

Software Development Life cycle Amount of resources consumed over the life cycle Minor maintenance Major maintenance

System Analysis and Design A systematic approach of: –Identifying problems and opportunities –Analyzing the flow of information in organization –Design computerized system to solve the problem

System Analyst A problem solver that requires communication skills, management skills and technical skills An agent of change Either: –An outside consultant –A supporting expert within the organization

System Analysis and Design Methodologies Systematic approaches of performing analysis and design Structured: –Based on showing the flow of data in the organization Object-Oriented: –Describes the objects interacting in the organization

Categories Information systems fall into one of the following eight categories: Transaction processing systems (TPS). Office automation systems (OAS). Knowledge work systems (KWS). Management information systems (MIS). Decision support systems (DSS). Expert systems (ES) and Artificial Intelligence (AI). Group decision support systems (GDSS) and Computer- Supported Collaborative Work Systems. Executive support systems (EES).

Organizations as Systems Interrelated subsystems –Product based –Service based Organization Goals input Output System environment

Organizations as Systems Organization Environment: –Physical –Economical –Political (rules and regulations) Feedback from environment and inside the organization to control and plan performance Organization Structure and Culture: –Culture: how people interrelate –Open organization: flow of information within organization –Management levels

Managerial Control The three levels of managerial control are: –Operations management. –Middle management. –Strategic management.

Computer-aided software Engineering tools Software packages that support the software development process Advantages: –Improves quality and productivity –Facilitate communication among team members and users –Provides continuity between life cycle phases –Facilitate maintenance But, they should be carefully chosen and staff should be properly trained.

Computer-aided software Engineering tools May be divided into several categories: –Upper CASE: perform analysis and design –Lower CASE: generate computer source code –Integrated CASE Other ways of classification –Functional –Breadth

Project Initiation Projects are initiated for two broad reasons: –Problems that lend themselves to systems solutions. –Opportunities for improvement through Upgrading systems. Altering systems. Installing new systems.

Identifying Problems Look for situations where the goals of the organization has not been met Check the output against performance criteria (e.g. errors and slow output) Observe behavior of employee (e.g. absence, turnover) Listen to external feedback from customers and vendors

Opportunities for improvement Speed up a process Duplicated steps Combining processes Reducing errors in input Reducing redundant output Improving integration of systems Improving workers satisfaction Improving customer or vendor interactions with the system

Feasibility Study Done by the system analyst Done quickly with minimum resources Interview high management people Define the objectives of the project & organization Output is feasibility report The decision whither to take the project is management

Feasibility Study Helps the organization attain overall objectives Is possible to accomplish with present organizational resources in the following three areas: –Technical Feasibility: Add on to present system Technology available to meet users’ needs –Economic Feasibility Cost of employees’ time Estimated cost of hardware Cost of packaged software/software development –Operational Feasibility Whether the system will operate when installed Whether the system will be used

Feasibility Impact Grid (FIG) A feasibility impact grid (FIG) is used to assess the impact of any improvements to the existing system. –Current or proposed systems are listed on the left. –Objectives are listed on the top. –Red arrows indicate a positive impact. –Green arrows indicate implementation.

Project Management Activities: –Selection of team members –Assignment of tasks to people –Estimate task time –Schedule project plan –Writing system proposal –Control by monitoring plan against activities –Motivating Team members

Project Planning Project is broken down into phases. Further project is broken down into tasks or activities. Finally project is broken down into steps or even smaller units. Time is estimated for each task or activity. Most likely, pessimistic, and optimistic estimates for time may be used.

Scheduling tools Gantt chart: Shows activities over a period of time as bars on a graph PERT-Program Evaluation and Review Technique –PERT diagrams show precedence, activities that must be completed before the next activities may be started. –Once a diagram is drawn it is possible to identify the critical path, the longest path through the activities. –Monitoring critical path will identify shortest time to complete the project.

Gantt Chart Example

PERT Diagram Example