· Choose an information system for an individual project.  During the course your project will be developing a hypothetical system.  Each week you will develop parts of the plan.  Weekly assignments include a system description, needs analysis, feasibility analysis, data analysis, process analysis, and financial analysis.  The final assignment will be to consolidate all previous assignments into one document. · The role of the facilitator will be to function as the business leader or stake holder who will use the proposed system for competitive advantage.  Each student will interview the facilitator as well as the balance of the class duringproject description and needs analysisphase. · Write and submit a detailed description of the information system chosen for the Information Systems Plan. Include the system name, type of system, key system benefits, along with interrelations and interdependencies with other systems. If there is an existing system to be replaced or upgraded, provide a description of the replacement or upgrade and the associated supporting technology.  · 1 1. Project Initiation Phase Validation Master Plan (VP) 2. Requirement Phase Traceability Matrix 3. Analysis Phase Phaseition Phase Traceability Matrix (update solution column) 5. Development Phase and Testing 6. Implementation Phase Planned Site SOPs Technology Architecture Project Definition PPQ Traceability Matrix (update test column) System Design Specification (SDS) 4. Design Phase Technical System Design Validation Report (VR) Traceability Matrix (update solution column) Test Plan (TP) Updated or created IT SOPs System and software IQ’s (Production) Testing System/OQ, Integration, User Acceptance Test cases (TC) (pre-approved and executed) Post Live Deliverable archiving Change Control procedure User and System manuals, training, guidelines System Retirement Strategy Transition Plan System and software IQ’s Test Report (TR) Requirements (System and Functional) Site Q review of each deliverable will occur as a consequence of project milestones. Delivered 2 Validation Packet  How is it done? Each packet is organized based on the uniqueness of the project. The basic deliverables really don’t change that much. Remember – Validation packet is based on a proven model based on an evolving IO/IA viewpoint  years of expertise has gone into this. . . The basic 6-phase SDLC approach is the structure. Makes little difference if SDLC or something else is the structure – project methodologies are basically the same . . . E-room and/or any team-accessed file structure solution is the working repository of documentation activity – that occur as a function of milestone project. A key element of validation packet is the fact that quality review is an active function - “Green Light”. Project team members are assigned key deliverables and off we go . . . The tracking of deliverables becomes a self-fulfilling prophecy of validated d.

1. · Choose an information system for an individual
project. During the course your project will be developing a
hypothetical system. Each week you will develop parts of the
plan. Weekly assignments include a system description, needs
analysis, feasibility analysis, data analysis, process analysis,
and financial analysis. The final assignment will be to
consolidate all previous assignments into one document.
· The role of the facilitator will be to function as the business
leader or stake holder who will use the proposed system for
competitive advantage. Each student will interview the
facilitator as well as the balance of the class duringproject
description and needs analysisphase.
· Write and submit a detailed description of the information
system chosen for the Information Systems Plan. Include the
system name, type of system, key system benefits, along with
interrelations and interdependencies with other systems. If there
is an existing system to be replaced or upgraded, provide a
description of the replacement or upgrade and the associated
supporting technology.
·
1
1. Project Initiation Phase
Validation Master Plan (VP)
2. Requirement Phase
Traceability Matrix

2. 3. Analysis Phase Phaseition Phase
Traceability Matrix
(update solution column)
5. Development Phase and Testing
6. Implementation Phase
Planned
Site SOPs
Technology Architecture
Project Definition
PPQ
Traceability Matrix
(update test column)
System Design Specification (SDS)
4. Design Phase
Technical System Design
Validation Report (VR)
Traceability Matrix

3. (update solution column)
Test Plan (TP)
Updated or created
IT SOPs
System and software IQ’s
(Production)
Testing
System/OQ, Integration, User
Acceptance Test cases (TC)
(pre-approved and executed)
Post Live
Deliverable archiving
Change Control procedure
User and System
manuals, training, guidelines
System Retirement Strategy
Transition Plan
System and software IQ’s
Test Report (TR)
Requirements
(System and Functional)
Site Q review of each deliverable will occur as a consequence
of project milestones.
Delivered

4. 2
Each packet is organized based on the uniqueness of the project.
The basic deliverables really don’t change that much.
Remember – Validation packet is based on a proven model
gone into this. . .
The basic 6-phase SDLC approach is the structure. Makes little
difference if SDLC or something else is the structure – project
methodologies are basically the same . . .
E-room and/or any team-accessed file structure solution is the
working repository of documentation activity – that occur as a
function of milestone project. A key element of validation
packet is the fact that quality review is an active function -
“Green Light”.
Project team members are assigned key deliverables and off we
go . . .
The tracking of deliverables becomes a self-fulfilling prophecy
of validated deliverables. No duplication of documentation
effort – no waste of time in determining what is needed and how
to document it.
3
What is Milestone Tracking?
Integrates Validation Packet deliverables into normal project
tracking. Positions key Validation Packet deliverables as
milestone events – which they are.
Microsoft Project should serve the project team not the other
way around . . . Meaning often, the administration of detailed
project plans via Microsoft Project, requires unnecessary
overhead and provides little value.
Key characteristics of Milestone Tracking
It assumes accountability by the professional project team. The

5. details of how to meet a milestone is the responsibly for those
that receive the assignment.
It is brief . . .
Resource balancing is de-emphasized. For example, milestone
tracking is not interested in the fact that project team members
have 20% of their time allocated towards meetings or other
projects. So – start dates and durations are not intended to be
accurate or tracked
But due dates and assignments are tracked. Weekly tracking is
the critical element.
4
What is Milestone Tracking?
Milestone tracking uses a rolling 2-4 week cycle.
Changes in dates and even changes within the milestones
themselves are allowed outside the rolling 4 week cycle
However, changes in deliverables and due dates within the
rolling 2-3 week cycle should be avoided.
5
Why Is It Successful?
Is simple with little administrative overhead.
Is flexible assuming it is tracked
Is empowering to team members which is a key component
Is a communication tool to management and other teams
Is proven but requires a strong and credible leader
SDLC (systems development life cycle)
1. Problem definition feasibility report why is it needed

6. 1. Human Information requirements interview, questionnaires,
watching, prototyping be on guard for “we have always done it
this way”
1. Systems needs always begin with a picture, a process flow, a
data flow diagram, structured decision points are identified
sometimes referred to as a decision tree output is a proposal
1. Design the solution the entry, processing and exit points of
data the importance of data organization (data dictionaries)
definitions, and consistency in data naming and use Technical
controls, backups, restores, security, roles of usage. The
guidelines of how the design is maintained. Sometimes includes
a disaster recovery plan.
1. Develop and document the system assume that a technician
(programmer) who is different than the author will be able to
understand and modify after implementation user help
regulatory needs FAQs, Read Me files, training
1. Test and maintain the system unit, process related and
volume testing and the capture of success or failure as evidence
started by the developer but should also utilize clients as a
reconnection from requirements to solution “traceability” time
and effort spent in testing always pays off at this stage phases
of SDLC are cyclical
Let’s discuss what change control is.
1. Implement and evaluate user training, data conversion
sometimes called the transition evaluate did you achieve the
objective as determined in the Problem Definition?
What’s more important humans or technology? Provide
personal doctor’s office example.
Once implemented why do we maintain it?
Needs change
Security updates are needed
Bugs are encountered
Hardware or hosting strategies change. A large 10-12 month
project should be able to be updated or upgraded in weeks.