1 presented by: Tim Haithcoat University of Missouri Columbia QA/QC and Risk Management.

Slides:



Advertisements
Similar presentations
Software Quality Assurance Plan
Advertisements

1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.
More CMM Part Two : Details.
Project Scope Management
Project Change Management
Stepan Potiyenko ISS Sr.SW Developer.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Lecture 13 Revision IMS Systems Analysis and Design.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Computers: Tools for an Information Age
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Implementation. We we came from… Planning Analysis Design Implementation Identify Problem/Value. Feasibility Analysis. Project Management. Understand.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
Purpose of the Standards
ENVIRONMENTAL DATA MANAGEMENT & SHALE GAS PROGRAMS INTERNATIONAL PETROLEUM ENVIRONMENTAL CONFERENCE NOVEMBER 14, 2013.
1 Walk-in slide. 2 How to Manage a System Upgrade The Good, The Bad and The Ugly of Conversions David Cervelli Managing Consultant April 25, 2006.
Introduction to Computer Technology
Release & Deployment ITIL Version 3
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management 1.
Chapter 10.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Testing. Definition From the dictionary- the means by which the presence, quality, or genuineness of anything is determined; a means of trial. For software.
S oftware Q uality A ssurance Part One Reviews and Inspections.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
Software Quality Assurance Activities
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
ITEC224 Database Programming
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
Don’t Just “Test”… Validate!!
Chapter 14 Information System Development
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
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.
IT Requirements Management Balancing Needs and Expectations.
September 3, 2013 Project on Inventory Control System (PICS) P.I.C.S
Software Project Management Lecture # 10. Outline Quality Management (chapter 26)  What is quality?  Meaning of Quality in Various Context  Some quality.
Moving into Implementation SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED.Roberta M. Roth.
Quality Control/ Quality Assurance Annabelle Allison ITEP/TAMS Center.
© Copyright 2011 John Wiley & Sons, Inc.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Software Project Management Lecture # 11. Outline Quality Management (chapter 26 - Pressman)  What is quality?  Meaning of Quality in Various Context.
BE-SECBS FISA 2003 November 13th 2003 page 1 DSR/SAMS/BASP IRSN BE SECBS – IRSN assessment Context application of IRSN methodology to the reference case.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Vector data input and editing Scanning (scan digitizing) –drum scanner scanner scans in map image –specialized software ‘extracts’ point, line, and area.
GUS: 0262 Fundamentals of GIS Lecture Presentation 8: Data Input and Editing Jeremy Mennis Department of Geography and Urban Studies Temple University.
Construction, Testing, Documentation, and Installation Chapters 15 and 16 Info 361: Systems Analysis and Design.
1 Construction Chapter Key Concepts Be familiar with the system construction process. Understand different types of tests and when to use Understand.
Chapter 4 Requirements Engineering (3/3) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
DATAWHERE - MIAB1 DATAWHERE The MIAB Solution to Information Support and Data Conversion/Migration 통신망 연구실 석사 3 학기 임 수 정.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Data Quality Improvement This material was developed by Johns Hopkins University, funded by the Department of Health and Human Services, Office of the.
Unit 11.2a: Data Quality Attributes Data Quality Improvement Component 12/Unit 11 Health IT Workforce Curriculum Version 1.0/Fall
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
Requirements Analysis
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
1 CEN 4020 Software Engineering PPT4: Requirement analysis.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Session 6: Data Flow, Data Management, and Data Quality.
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
 System Requirement Specification and System Planning.
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Software Quality Assurance
Developing Information Systems
CMMI – Staged Representation
Quality Measurable characteristic Cyclomatic complexity Cohesion
Reportnet 3.0 Database Feasibility Study – Approach
Presentation transcript:

1 presented by: Tim Haithcoat University of Missouri Columbia QA/QC and Risk Management

2 Quality Control Cover Two Topics:  General Principles of Quality Assurance  Quality Management

3 Definitions Quality Assurance (QA) Pertaining to a comprehensive approach or system for ensuring product quality. Quality Control (QC) Pertaining to an action or step designed to test product quality for any number of properties.

4 Data Quality Properties  Positional Accuracy  Attribute Accuracy  Topological Correctness  Completeness

5 Establishing Baselines (What Constitutes an Error?)  Positional Off-sets  Edgematching  Single/double precision  Shaded border  Processing Standards  RMSE  fuzzy  dangle  weed tolerances  Database Design  table formats  valid codes  valid feature types  data resolution  Data Extraction Rules  source interpretation  photo interpretation  generalization

6 Analyzing QC Requirements 4Develop a process-oriented flow  (i.e., edge matching standards, digitizing standards) 4Identify key points in the conversion process where data properties could/are change(d)  (i.e., digitization, transformation, re-projection) 4Adjust process flow to concentrate QC property checking into as few steps as possible

7 Basic Production Flow with Common Quality Control Checks Pass/ Fail Edits Positional Accuracy, Completeness and Topology testing Identify & Correct Gross Errors Production Steps In-process QC Inspection Independent QC Inspection Process Decision Point Main Process Flow Interactive QC Loop Manual Digitizing Automate Maps Manuscript Verification Manuscript Prep Scanning/Vectorization Option Transfer & Convert Transform Coordinates Scan/ Vectorize Verify Image & Vector Quality Verify Data Completeness Review Transform Statistics

8 Basic Production Flow with Common Quality Control Checks Pass/ Fail Edits Positional Accuracy, Completeness and Topology testing Production Steps In-process QC Inspection Independent QC Inspection Process Decision Point Main Process Flow Interactive QC Loop Attribute Coding Manual Attribute Testing Pass/ Fail Edits Automated QC Checks Coordinate Transformations Edgematch Delivery Transformation Verification Edgematch Verification Final Sign-off

9 Independent Inspection Will always find errors that elude the data processor. In-Process Inspection Useful for controlling simple data processing actions.

10 General Guidelines for Cost-Effective Error Checking  Re-work is always more costly than doing it right the first time.  Check everything once, and then concentrate on maintaining data integrity through the remaining processes.  Minimize the amount of materials that have to be handled.

11 QUALITY MANAGEMENT Data Quality Control is Process Control  Process tracking and statusing  Error correction tracking & process sign-off charts

12  Documentation  Record existence of anomalous conditions  Maintain a complete data dictionary (including data extraction rules)  Always provide staff (or vendor) with detailed written procedures plus diagrams describing graphic decision rules QUALITY MANAGEMENT Data Quality Control is Process Control

13  Communication  Develop formal mechanisms (i.e., standard symbols/colors for errors)  Conduct frequent coordination and status meetings  Provide honest opinions and feedback QUALITY MANAGEMENT Data Quality Control is Process Control

14 Project Risk Management  Corporate Management  Project Funding & Budgeting  Project Planning  GIS Technology  System Implementation The successful GIS implementation plan must be carefully designed to minimize risk. An in-depth analysis of the potential individual risks to a GIS project can be grouped under the following categories.

15 Corporate Management  inadequate sponsorship  project management  lack of full-time project manager  inability to control pilot project scope  unrealistic project schedule  lack of user support by development team  understaffed project team

16 Project Funding & Budgeting  inadequate cost-benefit study  inadequate project funding/budgeting

17 Project Planning  failure to include all required activities  failure to include all effected groups  failure to set scope based on cost-benefit  unrealistic user expectations

18 GIS Technology  failure to interface to other corporate data

19  inadequate conversion staff  change/expansion of conversion scope  Labor and personnel issues System Implementation