Dr. Stephania Loizidou Himona1 ACSC 155 System Analysis and Design 2. Systems Investigation ACSC 155 System Analysis and Design 2. Systems Investigation.

Slides:



Advertisements
Similar presentations
Communication Transferring information from one person to another. Communication is used to instruct, clarify interpret, notify, warn, receive feedback,
Advertisements

Session # 2 SWE 211 – Introduction to Software Engineering Lect. Amanullah Quadri 2. Fact Finding & Techniques.
Lecture 3 Planning and Development Methodologies.
MIS (Management Information System)
© 2005 Prentice Hall13-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. 7 Design of Work Systems.
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Determining systems requirements Updated: September 2014.
Delegation Skills.
Requirements Analysis Dr. Merle P. Martin CSU Sacramento.
Chapter 11 - Performance Management
Choosing Among Different Assessment Methods. Learning Objectives  Determine which assessment is best to utilize in the hiring process  Learn what required.
員工訓練與發展 教 師:林昌榮 員工訓練與發展 Employee Training & Development Training DevelopmentEducation.
System Implementation
Systems Analysis and Design
© Pearson Education Limited, Chapter 6 Fact-finding Transparencies.
Fact-finding Techniques
SYSTEM ANALYSIS AND DESIGN
Human Resource Management ELEVENTH EDITON
Sharif University of Technology Session # 4.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Approaches to ---Testing Software Some of us “hope” that our software works as opposed to “ensuring” that our software works? Why? Just foolish Lazy Believe.
A volunteer is interested in our organisation, what do I do next? Friday 25 th January
Chapter 11 Create the Job and Life You Want Copyright Raymond Gerson.
Approaches to Investigating a System “Who knows what’s happening now?”
Dr. Stephania Loizidou Himona1 ACSC 155 System Analysis and Design 1. Introduction ACSC 155 System Analysis and Design 1. Introduction.
Managing Information Systems Enhancing Management Decision Making Part 2 Dr. Stephania Loizidou Himona ACSC 345.
3.2.1 The role of Market Research and Methods Used:
PRJ566 Project Planning and Management
CSE323 การวิเคราะห์และออกแบบระบบ (Systems Analysis and Design) Lecture 03: Requirements Capture Requirements Analysis.
Data Collection Methods
Systems Life Cycle 1.Project Idenification 2. Initial Investigation 3. Feasibilty Study 4. Analysis 5. Design 6. Development and testing 7. Implementation.
1 Chapter 10 Fact-Finding Techniques Transparencies.
Fact-finding Transparencies 1. ©Pearson Education 2009 Objectives When fact-finding techniques are used in the database system development lifecycle.
System Analysis-Gathering Requirements.  System analysis is the process of gathering info about existing system, which may be computerized or not, while.
Database Analysis and the DreamHome Case Study
Systems Life Cycle. Know why it is necessary to evaluate a new system Understand the need to evaluate in terms of ease-of- use, appropriateness and efficiency.
Systems Development Lifecycle Analysis. Learning Objectives List the nine stages of the system life cycle Explain the system life cycle as an iterative.
Different approaches an analysis might use when investigating a system including: – Questionnaires – Interviews – Document gathering and analysis.
Quality and Quality Assurance IB Business and Management.
12/10/15.  It is a Cross Life Cycle Activity (CLCA) that may be performed at any stage ◦ In fact, some part of it (e.g. risk analysis and management)
Data Gathering Techniques 27 th February Data Gathering Techniques System requirements specify what the system must do or what property or quality.
1 Fact-Finding Techniques. 2 u Critical to capture necessary facts to build the required database application. u These facts are captured using fact-finding.
Centre for Information & Knowledge Management INFORMATION SYSTEMS MANAGEMENT Jamie O’Brien Centre for Information & Knowledge Management University of.
INFO1002 Systems Modelling Lecture 10 Establishing User Requirements Department of information Systems.
The techniques involved in systems analysis Explanation of a feasibility study:Explanation of a feasibility study: –economic, –legal, –technical, –time.
9.351 Systems Analysis & DesignRequirements Determination1 Requirement Determination Collecting information that specify what system needs to do/support.
Systems Development Life Cycle
Unit 2 AS Sociology Research Methods Examination Technique.
GCSE ICT Systems Analysis. Systems analysis Systems analysis is the application of analytical processes to the planning, design and implementation of.
IB Business and Management 5.4 Quality Assurance.
Definitions of GIS Works with geographic information Performs data input, management, manipulation/analysis, and output functions Composed of hardware,
Requirements in the product life cycle Chapter 7.
The Importance of Thinking Skills.  Because if you don’t – you’re a dumpling!  Dumplings don’t think – they just get gobbled up!
Chapter 3 Needs Assessment. Objectives 1.Discuss the role of organization analysis, person analysis, and task analysis in needs assessment. 2.Identify.
Unit 8 Recruitment, Selection & Employment – Assignment 3.
Chapter 2 Research Methods Please fill in your slides as we proceed.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
MGT 301 Class 3: Chapter 4 Job Analysis FEIHAN AHSAN BRAC University Sep 22nd, 2013.
Systems Development Lifecycle Analysis. Learning Objectives (Analysis) Analysis Describe different methods of researching a situation. State the need.
NEEDS ASSESSMENT HRM560 Sheikh Rahman
3 Chapter Needs Assessment.
Rekayasa Perangkat Lunak Part-14
Investigation Techniques
SYSTEMS ANALYSIS Chapter-2.
Requirements Analysis and Specification
Conducting Job Analysis (Chapter 2 – Part 2)
CIS 210 Systems Analysis and Development
Rekayasa Perangkat Lunak
Job Analysis Prof Srividya Iyengar.
System Development Life Cycle
ACSC 155 System Analysis and Design 4. Systems Design
Presentation transcript:

Dr. Stephania Loizidou Himona1 ACSC 155 System Analysis and Design 2. Systems Investigation ACSC 155 System Analysis and Design 2. Systems Investigation

Dr. Stephania Loizidou Himona2 Systems Investigation (4 methods)  1. Interview  2. Questionnaire  3. Record Inspection  4. Observation

Dr. Stephania Loizidou Himona3 1.Interviewing  Always start at the top people of the company asking permission to interview subordinates – ask them as well  You will need a check list before you conduct the interview Advantage: Straight from the ‘horse’s mouth’ Disadvantage: Without initial model or existing system, very difficult to where to start (time)

Dr. Stephania Loizidou Himona4 2. Questionnaire  Suitable for large number of ‘users’  Distributed over large geographical area  General public users Advantage: Time saving when a lot of far flung interview would otherwise be required Disadvantage: Unrepresentative sample due to low response

Dr. Stephania Loizidou Himona5 3. Record Inspection  Necessary for data analysis and definition Advantage: Impossible to investigate current system without seeing documentation (imagine describing in detail an order form in an interview) Disadvantage: You could be viewing out-of-date, used differently now documents

Dr. Stephania Loizidou Himona6 4. Observation  Watch ‘users’ work  Work with ‘users’  Partial observation, user ‘talks through’ process Advantage: See informal system. See exactly which documents used and how Disadvantage: Observes may feel under pressure to go by the book. Time

Dr. Stephania Loizidou Himona7 Problems in Investigation  Commitment to old system  Resistance to change  Embarrassment  Fear of Job Loss  Lack of interest  Analyst's lack of skill. Conflicting interests  Territorial Instincts  Expressing position too early

Dr. Stephania Loizidou Himona8 Project Initiation  A problem with the existing system  New technology - greater benefits or lower costs  Formalise manual or informal system  New information required  Resources become available for ‘frozen’ investigation

Dr. Stephania Loizidou Himona9 Past History 1. Little Analysis 2. Poorly Defined Tasks 3. Well defined User Role End Products Lengthy Narrative Specifications 1. Difficult to: Read, Understand, Change 2. Confused: Requirements, Design, Implementation

Dr. Stephania Loizidou Himona10 Resulting Systems 1. Took too long to build 2. Cost too much 3. Failed to meet requirements 4. Failed to meet constraints 5. Were inflexible 6. Were poorly documented