© Pearson Education Limited, 20041 Chapter 6 Fact-finding Transparencies.

Slides:



Advertisements
Similar presentations
DBS Development Lifecycle & DB Analysis
Advertisements

Fact-finding Techniques Transparencies
Fact Finding Techniques
Database Planning, Design, and Administration
CSC271 Database Systems Lecture # 18. Summary: Previous Lecture  Transactions  Authorization  Authorization identifier, ownership, privileges  GRANT/REVOKE.
Database Planning, Design, and Administration Transparencies
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Lesson 17 Requirements Discovery
Getting Started: Research and Literature Reviews An Introduction.
1 Pertemuan 14 Perencanaan, Desain dan Administrasi Databases Matakuliah: >/ > Tahun: > Versi: >
1 Pertemuan 18 Penemuan Fakta Matakuliah: >/ > Tahun: > Versi: >
Jump to first page Chapter 2 System Analysis - Determining System Requirements.
Chapter 29 conducting marketing research Section 29.1
Lecture Nine Database Planning, Design, and Administration
Fact-finding Techniques
Database System Development Lifecycle Transparencies
CSC271 Database Systems Lecture # 20.
CSC271 Database Systems Lecture # 21. Summary: Previous Lecture  Phases of database SDLC  Prototyping (optional)  Implementation  Data conversion.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
Chapter 33 Conducting Marketing Research. The Marketing Research Process 1. Define the Problem 2. Obtaining Data 3. Analyze Data 4. Rec. Solutions 5.
Team Dosen UMN Database System Development Lifecycle Connolly Book Chapter
Chapter 9 Database Planning, Design, and Administration Sungchul Hong.
Database Planning, Design, and Administration Transparencies
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Overview of the Database Development Process
ITEC224 Database Programming
Part3 Database Analysis and Design Techniques Chapter 04- Overview of Database Planning, Design and Administration Database Systems Lu Wei College of Software.
PRJ566 Project Planning and Management
1 Minggu 9, Pertemuan 17 Database Planning, Design, and Administration Matakuliah: T0206-Sistem Basisdata Tahun: 2005 Versi: 1.0/0.0.
©2002 South-Western Chapter 8 Version 6e1 chapter Marketing Research 8 8.
Chapter 29 conducting marketing research Section 29.1
There are many occasions for fact-finding during the database system development lifecycle. fact-finding is particularly crucial to the early stages of.
1 Chapter 10 Fact-Finding Techniques Transparencies.
Database Planning, Design, and Administration Transparencies
Database System Development Lifecycle 1.  Main components of the Infn System  What is Database System Development Life Cycle (DSDLC)  Phases of the.
Chapter 6 Determining System Requirements. 2 2 What are Requirements? “Requirements are … a specification of what should be implemented. They are descriptions.
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.
8/29/2012ISC 329 Isabelle Bichindaritz1 Database Application Example The Dreamhome.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Database Analysis and the DreamHome Case Study
Database Analysis Fact-finding techniques
Systems Development Lifecycle Analysis. Learning Objectives List the nine stages of the system life cycle Explain the system life cycle as an iterative.
Systems Analysis and Design in a Changing World, Thursday, Feb 1.
Chapter 4 Fact-Finding ( 實況調查 ) in Database Application Development.
IFS310: Module 3 1/25/2007 Fact Finding Techniques.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
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)
Information Gathering: Interactive Methods
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.
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.
Chapter 10 Fact-finding Techniques 1 © Pearson Education Limited 1995, 2005.
Centre for Information & Knowledge Management INFORMATION SYSTEMS MANAGEMENT Jamie O’Brien Centre for Information & Knowledge Management University of.
1 Fact-finding Techniques © Pearson Education Limited 1995, 2005.
© 2005 by Prentice Hall Chapter 6 Determining System Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph.
Designed & developed by E4 SBA SEMESTER ONE SESSION 5 BASICS OF MARKETING- I BASICS OF MARKETING I Session 5 Understanding marketing research.
Marketing Research Chapter 29. The Marketing Research Process The five steps that a business follows when conducting marketing research are: Defining.
1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design.
Information System Analysis Topic-2. Data Gathering Observations Questionnaires Interviews.
THE MARKETING RESEARCH PROCESS CHAPTER 29 Mrs. Simone Seaton Marketing Management.
Ondřej Přibyl L3: System Development Life Cycle page 1 Lecture 3: System Development Life Cycle Doc.Ing. Ondřej Přibyl, Ph.D. Department of applied mathematics.
Chapter 29 Conducting Market Research. Objectives  Explain the steps in designing and conducting market research  Compare primary and secondary data.
Chapter 9 Database Planning, Design, and Administration Transparencies © Pearson Education Limited 1995, 2005.
Information System Analysis Topic-2. Data Gathering Observations Questionnaires Interviews.
Systems Development Lifecycle Analysis. Learning Objectives (Analysis) Analysis Describe different methods of researching a situation. State the need.
The DreamHome Case Study
Database System Development Lifecycle
Essentials of Systems Analysis and Design Fourth Edition
Presentation transcript:

© Pearson Education Limited, Chapter 6 Fact-finding Transparencies

© Pearson Education Limited, Chapter 6 - Objectives When fact-finding techniques are used in the database system development lifecycle. The types of facts collected throughout the database system development lifecycle. The types of documentation produced throughout the database system development lifecycle.

© Pearson Education Limited, Chapter 6 - Objectives The most commonly used fact-finding techniques. How to use each fact-finding technique and the advantages and disadvantages of each. About a video rental company called StayHome. How to use fact-finding techniques in the early stages of the database system development lifecycle.

© Pearson Education Limited, Fact-finding The formal process of using techniques such as interviews and questionnaires to collect facts about systems, requirements, and preferences.

© Pearson Education Limited, When are fact-finding techniques used? Many occasions for fact-finding during the database system development lifecycle. Particularly crucial to the early stages of the lifecycle, including the database planning, system definition, and requirements collection and analysis stages.

© Pearson Education Limited, What facts are collected?

© Pearson Education Limited, Fact-finding techniques A database developer normally uses several fact-finding techniques during a single database project, including:  Examining documentation  Interviewing  Observing the business in operation  Research Questionnaires

© Pearson Education Limited, Examining documentation Examining documents, forms, reports, and files associated with the current system, is a good way to quickly gain some understanding of the system.

© Pearson Education Limited, Examples of documentation to examine

© Pearson Education Limited, Interviewing Interviewing is the most commonly used, and normally most useful, fact- finding technique. Objectives include: finding out and/or checking facts generating user interest and/or feelings of involvement, identifying requirements and/or gathering ideas and opinions.

© Pearson Education Limited, Advantages / disadvantages of interviewing

© Pearson Education Limited, Interviewing There are two types of interviews: unstructured and structured. Unstructured interviews are conducted with only a general objective in mind and with few, if any, specific questions. In structured interviews, the interviewer has a specific set of questions to ask the interviewee.

© Pearson Education Limited, Interviewing There are two types of questions: open-ended and closed. Open-ended questions allow the interviewee to respond in any way that seems appropriate. Closed-ended questions restrict answers to either specific choices or short, direct responses.

© Pearson Education Limited, Observing the business in operation One of the most effective techniques. Can either participate in, or watch a person perform activities to learn about the system.

© Pearson Education Limited, Advantages / disadvantages of observation

© Pearson Education Limited, Research Useful to research the application and problem. Computer trade journals, reference books, and the Internet are good sources of information. May find how others have solved similar problems, plus you can learn whether or not software packages exist to solve your problem.

© Pearson Education Limited, Advantages / disadvantages of research

© Pearson Education Limited, Questionnaires Can conduct surveys through questionnaires. Questionnaires are special-purpose documents that allow you to gather facts from a large number of people while maintaining some control over their responses.

© Pearson Education Limited, Advantages / disadvantages of questionnaires

© Pearson Education Limited, Questionnaires There are two formats for questionnaires: free-format and fixed- format. Free-format questionnaires offer the respondent greater freedom in providing answers. Fixed-format questionnaires contain questions that require specific responses from individuals.

© Pearson Education Limited, The StayHome case study This case study describes a company called StayHome, which rents out videos to its members. The first branch of StayHome was established in 1982 in Seattle but the company has now grown and has many branches throughout the United States.

© Pearson Education Limited, StayHome staff registration form

© Pearson Education Limited, Page of report listing members of staff

© Pearson Education Limited, Page of report listing videos

© Pearson Education Limited, StayHome member registration form

© Pearson Education Limited, Page of report listing members

© Pearson Education Limited, StayHome video rental form

© Pearson Education Limited, StayHome case study – database planning Define mission statement for the database project. Defines the major aims of the database system. Clarifies purpose of database and provides clearer path towards the efficient and effective creation of the required database system.

© Pearson Education Limited, StayHome case study – database planning Define mission objectives. Each mission objective identifies a particular task that the database must support. Additional information specifies, in general terms, the work to be done, the resources with which to do it, and the money to pay for it all.

© Pearson Education Limited, Mission statement for StayHome database system

© Pearson Education Limited, Mission objectives for StayHome database system

© Pearson Education Limited, StayHome case study – system definition Define scope and boundary of database system and its major user views. A user view represents requirements to be supported by a database system as defined by a particular job role (such as Manager or Assistant) or business application area (such as video rentals or stock control).

© Pearson Education Limited, Boundary for the StayHome database system

© Pearson Education Limited, User views for StayHome database system

© Pearson Education Limited, StayHome case study – requirements collection and analysis Gather more details on user views to create users’ requirements specification, which describes data to be held in database and how data is to be used.

© Pearson Education Limited, StayHome case study – requirements collection and analysis Collect general requirements for the system to create - systems specification - describes features to be included in new database system such as networking, shared access, performance, and security requirements.

© Pearson Education Limited, StayHome case study – requirements collection and analysis Decide how to manage project where database system has more than one user view. There are three approaches to dealing with multiple user views, namely: centralized approach view integration approach combination of both approaches

© Pearson Education Limited, StayHome user views and data