Lesson-16 Systems Analysis(2)

Slides:



Advertisements
Similar presentations
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Advertisements

Mahmut Ali GÖKÇEIndustrial Systems Engineering Lecture 2 System Identification ISE102 Spring 2007.
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
IS Theories & Practices Systems Architecture & Infrastructure IS 655: Supplementary Note 1 CSUN Information Systems.
5 C H A P T E R Modeling System Requirements: Events and things.
Karolina Muszyńska Based on
SYSTEM DEVELOPMENT Dr Manolya Kavakli Department of Computing
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Unit 211 Requirements Phase The objective of this section is to introduce software system requirements and to explain different ways of expressing these.
Chapter 2 Succeeding as a Systems Analyst
1 Info 1409 Systems Analysis & Design Module Lecture 5 - Feasibility HND Year /9 De Montfort University.
5.1 Dr. Honghui Deng Assistant Professor MIS Department UNLV MIS 370 System Analysis Theory.
Bina Nusantara 5 C H A P T E R SYSTEMS ANALYSIS. Bina Nusantara Systems Analysis Define systems analysis and relate the term to the scope definition,
Review Questions List and describe the purpose of the four phases of Systems Analysis. The preliminary investigation phase quickly determines whether or.
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
Systems Development Life Cycle
1 CSC-3324: Chapter 4 Title: What is a requirement? Mandatory reading: Sommerville 6, 7 th ed., Chap.: 7.
Chapter 5: Systems Analysis Objectives
Chapter 5 System Analysis.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 5 Systems Analysis.
SYSTEMS ANALYSIS Pertemuan 05
SYSTEMS ANALYSIS. Chapter Five Systems Analysis Define systems analysis Describe the preliminary investigation, problem analysis, requirements analysis,
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Context of Software Product Design.
The Software Development Life Cycle: An Overview
Chapter 5 System Analysis Sarah El Sehemawy Karim Elsabee Sherine Meshad Hakim Meshriky Ahmed Zaki Ismail Abou Hamda.
Systems Analysis & Design
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.
Business Analysis and Essential Competencies
Project design & Planning The Logical Framework Approach An Over View Icelandic International Development Agency (ICEIDA) Iceland United Nations University.
5 SYSTEMS ANALYSIS C H A P T E R
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
2131 Structured System Analysis and Design
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Advanced Higher Computing SOFTWARE DEVELOPMENT PROCESS.
5-1 Repository Repository – a location (or set of locations) where systems analysts, systems designers, and system builders keep all of the documentation.
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
1 Introduction to Software Engineering Lecture 1.
Systems Analysis and Design
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
IS Analysis and Design. SDLC Systems Development Life Cycle Break problems into management review stages Control cost and time Works best with well understood.
1 6 C H A P T E R REQUIREMENTS DISCOVERY. 2 Chapter Six Requirements Discovery Define system requirements and differentiate between functional and nonfunctional.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
OBJECT-ORIENTED SYSTEM ANALYSIS AND DESIGN 河北农业大学面向对象系统分析与设计课程组版权所有 5 C H A P T E R SYSTEMS ANALYSIS.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
1 Systems Analysis & Design 7 th Edition Chapter 2.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
MBI630: Class 5 6/10/2016 Process Modeling and Data Flow Diagrams (Supplemental)
Is 581 assist Inspiring Minds/is581assistdotcom FOR MORE CLASSES VISIT
Systems Development Life Cycle
System.
Unit 6 Application Design Practice Assignment.
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design
Context and Data Flow Diagrams
Operational Feasibility
Chapter 5 Systems Analysis.
Analyzing the Business Case
System Analysis System Analysis & Design Course
Systems Development Life Cycle
Information Systems Development (ISD) Systems Development Life Cycle
Chapter 5: Systems Analysis Objectives
Joint Application Development (JAD)
Presentation transcript:

Lesson-16 Systems Analysis(2) Describe the preliminary investigation, problem analysis, requirements analysis, and decision analysis phases in terms of purpose, participants, inputs, outputs, techniques, and steps. Identify those topics and modules in this courses that can help you learn specific systems analysis tools and techniques.

Problem Analysis Phase Context Conversion Notes In this edition we are trying hard to reinforce the building blocks. Teaching Notes The focus is on both system owner and system user perspectives. We are looking at the building blocks of the existing system.

Problem Analysis Phase Context No additional notes

Cause-and-Effect Analysis Cause-and-effect analysis is a technique in which problems are studied to determine their causes and effects. In practice, effects can be symptomatic of more deeply rooted or basic problems which, in turn, must be analyzed for causes and effects until such a time as the causes and effects do not yield symptoms of other problems. Teaching Tip Analyze a problem using cause-and-effect analysis. If you know “fishbone diagrams”, demonstrate cause-and-effect analysis using the diagrams.

System Improvement Objectives An objective is a measure of success. It is something that you expect to achieve, if given sufficient resources. Reduce the number of uncollectible customer accounts by 50 percent within the next year. Increase by 25 percent the number of loan applications that can be processed during an eight-hour shift. Decrease by 50 percent the time required to reschedule a production lot when a workstation malfunctions. A constraint is something that will limit your flexibility in defining a solution to your objectives. Essentially, constraints cannot be changed. Teaching Tips Formulate objectives as an in-class exercise.

Cause-and-Effect / System Improvement Objectives PROBLEMS, OPPORTUNITIES, OBJECTIVES, AND CONSTRAINTS MATRIX No additional notes

Requirements Analysis Phase Context Conversion Notes In this edition we are trying hard to reinforce the building blocks. Teaching Notes The focus is on system user perspectives. Requirements can be expressed in narrative, model, and prototype forms, or any combination thereof.

Requirements Analysis Phase Tasks Teaching Notes Some of the tasks are completed in parallel.

Business Requirements A functional requirement is a description of activities and services a system must provide. A nonfunctional requirement is a description of other features, characteristics, and constraints that define a satisfactory system. No additional notes

Logical System Models Logical system models depict what a system is or what a system must do—not how the system will be implemented. Because logical models depict the essential requirements of a system, they are sometimes called essential system models. Process models (e.g., data flow diagrams) Data models (e.g., entity relationship diagrams) Interface models (e.g., context diagrams) Object models (e.g., Uniform Modeling Language diagrams) Teaching Notes The opposite is physical system models, which will be introduced in the systems design chapter.

A Simple Interface Model No additional notes

Requirements Statement No additional notes

Decision Analysis Phase Context Conversion Notes In this edition we are trying hard to reinforce the building blocks. Teaching Notes The focus is on system user and system designer perspectives. Notice the transition to technical concerns leading to a system proposal that includes data, process, and interface elements.

Decision Analysis Phase Tasks No additional notes

Feasibility Analyses Technical feasibility. Is the solution technically practical? Does our staff have the technical expertise to design and build this solution? Operational feasibility. Will the solution fulfill the users’ requirements? To what degree? How will the solution change the users’ work environment? How do users feel about such a solution? Economic feasibility. Is the solution cost-effective? Schedule feasibility. Can the solution be designed and implemented within an acceptable time period? No additional notes

Candidate Systems Matrix No additional notes (Continued)

Candidate Systems Matrix (concluded) No additional notes

Feasibility Matrix No additional notes