Information Systems Development Model, An Introduction for the Non-Technical 2005 National Immunization Conference March 22, 2005 Washington, DC.

Slides:



Advertisements
Similar presentations
Procurement Update Webinar January 6, TopicTime Introductions and Review Agenda1:00–1:10 Overview of SBACs Procurement Process1:10–1:30 Advice.
Advertisements

Configuration Management
Effective Contract Management Planning
Roadmap for Sourcing Decision Review Board (DRB)
Global Congress Global Leadership Vision for Project Management.
State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Course: e-Governance Project Lifecycle Day 1
Project Management 6e..
Can you plan without understanding what is it that you are planning for? e.g. - what is it we are doing? - what do we need to do?
NEES Project Management Workshop June 16 June 18 1 Segment 2.
GAI Proprietary Information
Defining the Project CHAPTER FOUR Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Project Management: A Critical Skill for Organizations Presented by Hetty Baiz Project Office Princeton University.
Panorama Consulting Group LLC ERP Assessment, Selection, and Planning SAMPLE APPROACH.
Rational Unified Process
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Software Project Transition Planning
Process, Communication, and Certification Padma Venkata
Michael S. Zachowski, Robert D. Walla Astrix Technology Group 1090 King Georges Post Rd Edison, NJ A Successful Approach to a LIMS Upgrade In A Public.
Managing Risk to Reduce Construction Claims (And Improve Project Success) Presented by Laurie Dennis, PE, CVS-Life, FSAVE.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
PROJECT MANAGEMENT FUNDAMENTALS Page 2 Course Overview 1. Introduction to Project Management 2. Project Roles and Expectations 3. Project Management.
State of Kansas Statewide Financial Management System Pre-Implementation Project Steering Committee Meeting January 11, 2008.
Release & Deployment ITIL Version 3
1 Configuration Management 101 ITS Professional Capacity Building Program T3 Webinar February 21, 2008.
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
S/W Project Management
Typical Software Documents with an emphasis on writing proposals.
4.2 Develop Project Management Plan
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Certificate IV in Project Management Introduction to Project Management Course Number Qualification Code BSB41507.
Kelly J. Harris SEARCH Deputy Executive Director
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
SacProNet An Overview of Project Management Techniques.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Develop Project Charter
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 1 Diploma of Project Management.
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Project Charter
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
1 - 1 Systems Analysis and Design, Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Understanding Registry Resources 2002 Immunization Registry Conference October 28, 2002 Philadelphia, PA.
Rational Unified Process (RUP)
State of Georgia Release Management Training
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Illuminating Britelite’s Internal Services for Success Strategy for Process Improvement.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Managing Multiple Projects Steve Westerman California Department of Motor Vehicles Steve Young Mathtech, Inc.
Project Life Presented by Chuck Ray, PMP ITS Project Manager.
Practical IT Research that Drives Measurable Results Establish an Effective IT Steering Committee.
Powerpoint Templates Page 1 Powerpoint Templates Project Angels Martin L. Harbolt PMP, CSM.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Systems Development Life Cycle
Project Management for Treasury Professionals
Project Management Processes
Project management for working professionals
2 Selecting a Healthcare Information System.
Description of Revision
Project Management Processes
Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
Executive Project Kickoff
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

Information Systems Development Model, An Introduction for the Non-Technical 2005 National Immunization Conference March 22, 2005 Washington, DC

Authors Katie Reed Michael Spurchise

Historical Perspective Good decision making is a result of the collection of good data. The development of information systems makes it possible across all industries to collect better data. Public health officials and information systems professionals are working together to develop quality systems for public health. IIS has lead this effort in many public health arenas.

The Challenge In order to meet the needs of public health; the development of quality systems requires participation and commitment from both program oriented staff, technical staff, and third party vendors. The challenge is to create a model and a language where communication and expectations are understood from all perspectives.

System Development Phases Phase 1 – Project Initiation and Planning Phase 2 – Requirements/Operational Analysis Phase 3 – Design Phase 4 – Configuration/ Build/Development Phase 5 – Testing/Validation/Evaluation

System Development Model Phase One Project Initiation and Planning –Business Case –Proposed Solution –Evaluation Criteria –Proposal Selection

Roles and Responsibilities Public Health owns this phase. Problem identification. RFP developed and released. Contract awarded between Public Health and Vendor.

Caution Areas Scope of project must be clearly defined. –Understand RFP’s are estimates as to what one thinks it will take given the information provided. –Understand resource needs. Development process is articulated and clearly understood by both sides. –Fluidity, not rigidity allows for creative solutions. –Identify decision makers and escalation procedures.

Caution Areas As part of the RFP response and selection, changes may be made to the initial “proposed solution”, should be agreed upon through the selection process and contract negotiation. Is this a “big bang” project or can it be broken into sub-deliverables? Helpful to think this through up front and possibly tie payment as part of this.

System Development Model Possible Outcomes of Phase One –Project Charter –System Initiation –Risk Definition –Initial Project Plan –Define/Approve Deliverables Both Vendor and Public Health agree

System Development Model Phase Two Requirements/Operational Analysis –Typical Requirements Analysis JAD Sessions (Joint Application Development) SRS (Software Requirement Specifications) FRS (Functional Requirements Specifications)

Roles and Responsibilities Public Health and Vendor own this phase. Process is facilitated by Vendor. Subject Matter Experts provide the information that will drive the system, this is key! SMEs from Public Health part of JAD and SRS process. FRSs, understand your involvement.

Caution Areas Must have commitment from SMEs, maybe take off site for JAD sessions, made clear priority, train them well on process. Time commitments are not insignificant on the part of the Public Health SMEs. Do not underestimate who will be available. JAD sessions, don’t solutionize, focus on business requirements. Short change this part of the process, assume a rocky road. Recognize, this is an iterative process!!! Make sure infrastructure can support system requirements.

System Development Model Possible Outcomes of Phase Two –SRS, FRS, SOW –Possible mockups/screens/prototype Both Vendor and Public Health agree

System Development Model Phase Three Design –Architectural Design –Establish Data Model and Dictionary –High Level Documentation –Develop Test Plans QA - Programmatic Functionality - Technical –Updated FRS as needed

Roles and Responsibilities Design is predominantly owned by Vendor. Public Health may be involved in iterations of SRS/FRS.

Caution Areas Recognize possible warning signs –How often are SRS/FRS being updated? –Team still aligned with goals and objectives? –Resources still on track, any major gotchas? –Public Health, do you still feel you own this system?

System Development Model Possible Outcomes of Phase Three –FRSs updated as necessary –Development Plan –Use Case Models –Mockup or Prototype Ready to “throw over the wall”

System Development Model Phase Four Configuration/Build/Development –Change Requests –Vendor Testing Unit Integration

Roles and Responsibilities Vendor owns this as they construct system. “BLACK BOX” Public Health with Project Management team monitor activities, resource allocation, and scope. Communication between Public Health and Vendor routine and systematic. (Microsoft Project) –Status Meetings and/or Reports

Caution Areas If Phase 2 and 3 were done correctly this shouldn’t have many gotchas. Must feel comfortable that they can “show me” what has been done so far. Watch level of contact between vendor and SMEs, too much contact needs to be investigated, could be a warning sign.

System Development Model Outcomes of Phase Four –User Manuals –Product –Description of Release –Ready for “beta” Both Vendor and Public Health agree

System Development Model Phase Five Testing/Validation/Evaluation –Beta Testing –Parallel Operations –Tuning activates based on testing outcomes

Roles and Responsibilities Public Health and Vendor own this together. Public Health is critical in testing and validation. Commitment is key. Communication avenues and clearly delineated process. Public Health needs to be ready to “own” the product.

Caution Areas Recourses must be committed by Public Health to this process. Testing must be understood, see back to Use Cases and training the SMEs.

System Development Model Outcomes of Phase Five –Go live –System Maintenance –System Enhancements –Support Both Vendor and Public Health agree

Tools to Consider Project Plan Software Familiarize with development methodology prior to process, i.e. RUP: ibm.com/developerworks/rational/lib rary/content/RationalEdge/archives/rup. html ibm.com/developerworks/rational/lib rary/content/RationalEdge/archives/rup. html Communication Strategy –Project Team –Steering Committee –Stakeholders

Contact Information Katie Reed Vice President Partners in Health Systems 5789 Widewaters Parkway P.O. Box 249 Dewitt, NY ext