Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 1 Systems Analysis Investigation Techniques.

Slides:



Advertisements
Similar presentations
Methodology and Explanation XX50125 Lecture 3: Interviews and questionnaires Dr. Danaë Stanton Fraser.
Advertisements

MIS (Management Information System)
Questionnaire Design.
Client survey Data collection team training presentation template.
Chapter 4.
Systems Analysis and Design 9th Edition
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 5.1.
S17: Field work. Session Objectives  To explain the manner in which field audit is carried out.  To explain the nature of evidence and the different.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Empowering Staff Through Institute Planning (ESTIP) Executive Workshop Institute Name: XXXXXX Presenter: XXXXXX Date: XXXXXX.
Typical SDLC Feasibility study Feasibility study Plan Plan Analysis Analysis Design Design Development) Development) Testing Testing Validation Validation.
IS Audit Function Knowledge
Monash University, SIMS, Semester One, DATA GATHERING FOR INFORMATION SYSTEMS DEVELOPMENT CSE Information Systems 1 CSE Information Systems.
Systems Analysis Requirements determination Requirements structuring
Gathering Information and Use Case Scenarios
Fact-Finding Fact-Finding Overview
Requirements Gathering : Determining the scope of the system 1. Elicitiation – fact finding 2. Specification 3. Validation.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
SYSTEMS ANALYSIS. Chapter Five Systems Analysis Define systems analysis Describe the preliminary investigation, problem analysis, requirements analysis,
Requirements Modeling
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Systems Analysis and Design: The Big Picture
Copyright 2010, The World Bank Group. All Rights Reserved. Training and Procedural Manuals Section A 1.
Lecture Outline 11 The Development of Information Systems Chapter 8 page 390+
Approaches to Investigating a System “Who knows what’s happening now?”
Accounting systems design & evaluation 9434SB 12 April 2002.
Slide 1 D2.TCS.CL5.04. Subject Elements This unit comprises five Elements: 1.Define the need for tourism product research 2.Develop the research to be.
PHASE 2: SYSTEMS ANALYSIS
INTRODUCTION TO AUDITING
The Information School at the University of Washington Information Audits Bob Boiko UW iSchool ischool.washington.edu Metatorial Services Inc.
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Report Writing.
Chapter 16 Structured Systems Analysis. Learning Objectives Know goals, plans, tasks, tools, & results of systems analysis Understand/appreciate costs.
System Analysis-Gathering Requirements.  System analysis is the process of gathering info about existing system, which may be computerized or not, while.
Chapter 5: NEEDS ASSESSMENT “Acting without thinking is like shooting without aiming.” B. C. Forbes.
University of Sunderland Professionalism and Personal Skills Unit 9 Professionalism and Personal Skills Lecture Data Collection.
Feasibility study A feasibility study is a preliminary investigation of a problem. It is used to decide whether a solution is possible and what effects.
Data flow & information requirements.  Establishing IPSO  Recording information about the existing system  Identifying the problems with the system.
Software Development Life Cycle by A.Surasit Samaisut Copyrights : All Rights Reserved.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
Data Gathering Techniques 27 th February Data Gathering Techniques System requirements specify what the system must do or what property or quality.
 Definition of a quality Audit  Types of audit  Qualifications of quality auditors  The audit process.
1 Commissioned by PAMSA and German Technical Co-Operation National Certificate in Paper & Pulp Manufacturing NQF Level 4 Perform physical and chemical.
The techniques involved in systems analysis Explanation of a feasibility study:Explanation of a feasibility study: –economic, –legal, –technical, –time.
Systems Development Life Cycle
Compliance Monitoring and Enforcement Audit Program - The Audit Process.
Systems Analysis and Design 8th Edition
1Lecture 8 Introduction to Systems Analysis l Objectives –Explain how systems analysis relates to business needs, problems, and opportunities –List and.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Main tasks of system analysis ? 1-study exit=sting information system 2-identify problem 3-spelify system requirement 4-asalysis decision ========= How.
Conduct User Analysis Website Design With handout UseNeedsAnalysis.doc.
Fashion MARKETING TID1131. Types of research Quantitative research Information relating to numbers – quantity. Method - surveys Qualitative research To.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
1 The System life cycle 16 The system life cycle is a series of stages that are worked through during the development of a new information system. A lot.
1 Systems Analysis & Design 7 th Edition Chapter 2.
6-1 Functional vs. Nonfunctional Requirements Functional requirement - something the information system must do Nonfunctional requirement - a property.
Week 2: Interviews. Definition and Types  What is an interview? Conversation with a purpose  Types of interviews 1. Unstructured 2. Structured 3. Focus.
Topic 2 – Techniques involved in Systems Analysis Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
1 International Institute of Business Analysis Vision: The world's leading association for Business Analysis professionals” Mission: To develop and maintain.
1 Audit Interviewing. 2Topics  Why Conduct Interviews  The Interview Process  Interview Best (and Worst) Practices  Summary.
Rekayasa Perangkat Lunak Part-14
Fundamentals of Information Systems, Sixth Edition
G063 - Data flow diagrams.
Programme Site Visit Dhaya Naidoo Director: Quality Promotion
Programme Site Visit Directorate of Quality Promotion QP_DN.
SYSTEMS ANALYSIS Chapter-2.
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
The Development of Information Systems Chapter 8 page 348+
G063 - Data flow diagrams.
Rekayasa Perangkat Lunak
Presentation transcript:

Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 1 Systems Analysis Investigation Techniques

Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 2 Recap DFDs are typically produced in the form of a context diagram, level 1 and level 2 diagram. Context diagram typically shows entities involved in required system. Level 1 diagram typically shows main processes and data stores of system under investigation. Level 2 diagram typically shows detail of processes, including any data stores unique to a process.

Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 3 Investigation techniques Why investigate? Need to know how existing system operates. Find out problems / opportunities. Identify ‘new’ services / functions. Initiate involvement with relevant stakeholders.

Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 4 Preliminary work Terms of reference Who wants the analysis performed? Any restrictions – time, money, quality issues, H/W, S/W, legacy applications, security, personnel issues? Reporting structures / formats? Background Organisation structure. Current documentation. Previous reports. Surveys / marketing information. Staff availability.

Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 5 Planning Data gathering – such as interviews, documentation, system overview, observations, audit trails. To include: Resources – people, equipment, accommodation. Environment – layout, conditions. Method of work – supervised, planned, interrupt. Information flow – purpose, content and suitable samples. Procedures – formal / informal for normal / exceptional. Volumes / frequencies Controls – physical, financial, quality Problems – symptoms and potential causes.

Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 6 Information flow Inputs – documents and messages Outputs – reports, letters, messages Storage – data storage, reference Data Flow Diagrams useful for this

Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 7 Methods of investigation Observation – not widely used, due to potential resentment and Hawthorne effect. Searching / reviewing current documentation. Sampling – reviewing a small number of a process. Questionnaires Interviews

Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 8 Interview Technique Interviews should be planned – participants, date/time, location, sequence, objective, points to cover. Interviews must be arranged with relevant personnel. Introduction – analyst should put people at ease, explain why interview is required and relevant reasons.

Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 9 Information gathering Use appropriate language, respect people, present facts not opinions, take notes quickly. Do not criticise! Be aware of: Pace – adjust, as required, listen carefully. Sequence – Try to keep to a pre-planned sequence, avoid being sidetracked. Questions – Avoid leading questions, and too many open questions. Flow – ensure questions are at least attempted. Pause, as and when appropriate.

Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 10 Interview conclusion Try to finish when agreed, else interviewee may become annoyed. Summarise interview and request confirmation. Request additional interview, if required. Outline what happens next – possibly provide documented overview, if they request it.

Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 11 Interview record After interview, document interview – does not have to be verbatim. Cross-check interview, where possible, with other stakeholders. Maintain documentation within a central project file.

Copyright © 2005 Bolton Institute Copyright © 2005 University of Bolton 12 Recap See handout documentation / examples.