Oregon Benefits Online Scope to System Comparison 1.

Slides:



Advertisements
Similar presentations
Roadmap for Sourcing Decision Review Board (DRB)
Advertisements

State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
P5, M1, D1.
1. 2 RE Case Study What was the Project Objective? When did it all Start? What was the Plan? How did Negotiations take place? What were the Benefits of.
Cingular Case Studies September 24, © 2007 BearingPoint, Inc.IM – Content, Portals and IntegrationCommunications and Utilities AT&T B2B Wireless.
Panorama Consulting Group LLC ERP Assessment, Selection, and Planning SAMPLE APPROACH.
May 2007Phase One Consulting Group, Inc. Applying NIST’s SOA Lifecycle Measures to NPS’ SOA Project October 2, 2007 Randy Leonard
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Validating and Improving Test-Case Effectiveness Author: Yuri Chernak Presenter: Lam, Man Tat.
Submitting Projects and the Approval Process Brownbag lunch February 9, 2005 Paul Craft.
SERVICE EVALUATION APPROACHES AND COMPARISON WITH THE USE OF ITIL Matthew Fazo BIS 461.
Project Risk Management Risk Mitigation. Risk Management  The prime objective of risk management is to minimize the impact and probability of the occurrence.
What is Business Analysis Planning & Monitoring?
Discussion Items with Bruce
S/W Project Management
CC20O7N - Software Engineering 1 CC2007N Software Engineering 1 Requirements Engineering Practices with Techniques.
Software Project Management Lecture # 8. Outline Chapter 25 – Risk Management  What is Risk Management  Risk Management Strategies  Software Risks.
Project Risk Management. The Importance of Project Risk Management Project risk management is the art and science of identifying, analyzing, and responding.
Where Innovation Is Tradition SYST699 – Spec Innovations Innoslate™ System Engineering Management Software Tool Test & Analysis.
Software Testing Life Cycle
The Systems Proposal What the book calls the “Updated Baseline Project Plan” - no standard name for it Presents the different options to the customer along.
Chapter 10 Contemporary Project Management Kloppenborg
New Business Architecture
Smart Digital Valve Control Simulator May April 25, 2001 Client: Client: Fisher Controls Intl. Inc. Contacts: Contacts: Patrick Ryan and Jeff Seyller.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
CIS 321—IS Analysis & Design Chapter 4: Analysis— Investigating System Requirements.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
- 1 - Roadmap to Re-aligning the Customer Master with Oracle's TCA Northern California OAUG March 7, 2005.
Feasibility Study.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
2Object-Oriented Analysis and Design with the Unified Process The Requirements Discipline in More Detail  Focus shifts from defining to realizing objectives.
Serena Project Case Study Sapphire, Atlanta April 23, 2007.
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.
Software Requirements Engineering: What, Why, Who, When, and How
Current and Future Applications of the Generic Statistical Business Process Model at Statistics Canada Laurie Reedman and Claude Julien May 5, 2010.
Technology Transfer Execution Framework. 2 © 2007 Electric Power Research Institute, Inc. All rights reserved. Relationship Between Your EPRI Value and.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 The Analysis Phase System Requirements Models and Modelling of requirements Stakeholders as a source of requirements.
Systems Life Cycle A2 Module Heathcote Ch.38.
The Traditional System Development Life Cycle There are a number of important steps in the creation of a system, regardless of which approach you use.
CSCI 521 Final Exam Review. Why Establish a Standard Process? It is nearly impossible to have a high quality product without a high quality process. Standard.
Software Requirements and Design Khalid Ishaq
Developing an Electronic Dossier System for UCLA Faculty: Planning Proposal Presentation to Committee on IT Infrastructure November 30,
FEASIBILITY STUDY.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Project & Risk Management
GCSE ICT Systems Analysis. Systems analysis Systems analysis is the application of analytical processes to the planning, design and implementation of.
Module 5 Session 5.2 Visual 1 Module 5 Refining Objectives, Scope, and Other Project Parameters Session 5.2 Reviewing the PAR and refining key project.
Thomas Kern | The system documentation as binding agent for and in between internal and external customers April 24th, 2009 | Page 1 The system documentation.
A BRIEF LOOK AT THE COMPONENTS THAT MAKE UP THE SYSTEM LIFE CYCLE.
Software Project Management Lecture # 9. Outline Chapter 25 – Risk Management  What is Risk Management  Risk Management Strategies  Software Risks.
ClearCube markets an alternative to traditional desktop PCs. Primary Matters developed a Sales Tool that presented to ClearCube prospects the costs and.
SERVICE REQUEST MANAGEMENT IMPLEMENTATION Rev Mar 11, 2008.
ERCOT Portal Replacement Phase 2 Project Update to RMS Presented by Dave Odle Thursday, October 16 th, 2003.
PROJECT PLANNING & MANAGEMENT Brittany Hamilton. PROGRESS TRACKING Do we understand customer’s needs? Can we design a system to solve customer’s problems.
CS628 - Object Oriented Analysis And Design. The Four Pillars of Successful Software Development -Avoid Classic Mistakes -Apply Development Fundamentals.
A brief look at the components that make up the system life cycle.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
ITEC 275 Computer Networks – Switching, Routing, and WANs
Introducing pdri for mega projects As a Planning quality Control tool
C. What is a Feasibility report
Systems Analysis and Design
FEASIBILITY STUDY Feasibility study is a means to check whether the proposed system is correct or not. The results of this study arte used to make decision.
Chapter 4 Systems Planning and Selection
The End of the first Sprint
Jess Neuner Esri Corporate Template-Dark v3.3
Presentation transcript:

Oregon Benefits Online Scope to System Comparison 1

What We Did The Oregon Benefits Online (OBO) Scope Identification work group conducted a high level analysis of the Oracle system built for OBO using the Master Scope document. Compared each line of the Master Scope document to the demonstrated system to evaluate alignment. The comparison was focused on the needs of the business. The comparison was completed and findings were determined based on demonstrations of the OBO system. Completed the analysis ahead of schedule. 2

What We Did Not Do Hands-on testing. Any technical analysis of the underlying foundation. Prioritize any scope items beyond the already identified Future Phases section. 3

Categories Usability – The general intuitiveness, workflow, navigation and ease of data entry. User Interface – The look and feel of the OBO system. Verbiage/Content – Displays accurate information, wording, phrasing and correct placement. Functionality – Does what it is supposed to do in order to meet the business need. 4

Findings Our analysis concluded the OBO system did not meet the Master Scope and it appears extensive customization would need to occur. Issuing benefits timely will be at risk due to the communication inconsistencies within the Customer Portal. Workload and accuracy will be negatively impacted due to the usability deficiencies within the OBO system. Extensive staff training and business process re- engineering would have to occur to use the “out of the box” OBO system. 5

Findings 6

7

8

Proposals The Scope to System Comparison Workgroup recommends that DHS should not implement the OBO system as is. Additionally: Stop all project activity Create a thorough project roadmap Determine future needs of the business Gather requirements Research systems that would meet the needs Once these are done – reinitialize the project The recommendation is to not spend the time and money to do a time estimate for OBO system completion because of lack of agreed upon requirements. 9

D i s c u s s i o n 10