*** Plagiarism is not acceptable *** As part of activity 1 need to complete on “ Activity 1 – Identify Stakeholders and the Root Causes of a problem” based on case study you have slected . Overview of Project – Vision Document and associated Use CasesIntroduction: Systems development is a complicated process which typically doesn’t conclude as a success story – as you can easily see from the CHAOS reports over the years. Factors that contribute to the failure of systems development do not typically include technical complexities. The causes of many failures include solving the wrong problem, scope creep, failure to manage customer expectations, luck of buy-in from all the stakeholders, and finally, the ability to embrace and plan for change and flexibility in the process of systems development.For this project, you will . . . develop a Vision Document, and the associated Use Case for a new system in a fictitious company. The company doesn’t have to be an IT company but it must be of substantial size (at least 5,000 employees) and have an established IT Department. **Kindly refer attached project overview and tasks for the topic carefully.** Please find attached sample document for my classmate so you will get an idea**Instructions: Research Paper in in APA format. Plagiarism is not acceptable. (Please consider this top priority). For Activity 1 complete instructions are attached. All instructions or tasks must be addressed.( Try to address all the information specified in each task ) Activity 1 is minimum 4 to 7 pages.( and reference page) Paper must be included APA format References only and in-text citations. The references you cite should be credible, scholarly, or professional sources and Not older than 3 years
project_overview_and_week_1_tasks.docx

sample_project_document.docx

Unformatted Attachment Preview

Week 1 Project Overview
An information system (IS) is a system, whether automated or manual,
maintaining data records and organizing activities for an organization.
For this assignment, you will analyze the development process of an IS for an
enterprise of your choice. You will focus on the stakeholders’ needs, and
problems to be solved for your selected case study. In addition, you will tackle the
requirements management, analysis, and design of your selected case study and
make decisions including the articulation of needs, features, requirements, test cases, and design decisions.
You will be completing this assignment in five weeks. In each week, you will work
on a component of the report. By the end of Week 5, you will integrate these
separate components into a final report.
In this week, your task for the project is to research in the University Online
Library and on the Internet to identify a case study of your choice with a pertinent
information system application.
Some examples could be: a health care organization, such as a health care
insurance company, a major hospital, or medical laboratory; an academic
institution, such as a university or a professional institute; a commerce and
transportation center, for example a major airport, or maritime port; a
transportation carrier, such as an airline company, a railroad company, or even a
car transportation service; a network service provider, such as a
telecommunications service carrier/provider, an Internet and voice digital service
provider, or a cloud service provider; a major media organization, such as
television network, or a multimedia service operator; an industry firm that
manufactures products, such as a computer products manufacturer, a car
manufacturer, or a hardware manufacturer; a major retailer, for example a food
retailer, a home maintenance retailer, or clothes outlet; an entertainment
complex, such as a hotel, a vacation resort, or a large recreation and
entertainment complex; a financial institution, for example a banking system, a
credit card service, or an investment trading service.
The above are examples to guide you with your research, but you are not limited
to these areas. It is important that you arrive at your own case study, based o n
your personal interests, and one that is well suited to explore from an information
systems analysis for this course. Some criteria that you should consider in
arriving at your case study are listed below:
1. Your case study may be based on an actual company, or organization, using facts
from research, or it could be fictional, in the sense that you could entirely define it
yourself as a hypothetical case, with your own assumptions.
2. Your case study must require an underlying information system as an essentia l
element for its operation.
3. The information system must be reasonably complex. One way to determine
whether an information system is reasonably complex is to think in terms of
entities and relationships that you will need to model. Even without knowing
exactly how the data model will look, having some early notion of how many
entities and relationships you should expect to model the information in your case
will give you an appreciation for your case’s complexity. A reasonable complexity
would be at least ten entities and ten relationships.
4. At some point in your research you must be able to think in terms of use cases for
your information system. Think of use cases as transactions that different end
users will invoke when interacting with your information s ystem. At the time you
select your research area and define your case study, you need not know exactly
the use cases you will be working with, but you should have some appreciation for
the types of scenarios that you will explore as you progress with your project.
5. Finally, you must submit your area of study to your instructor via e -mail and have
your instructor’s approval that you may go ahead with your selection.
Once you have selected your study area and case, and have received approval
from your instructor, you may proceed to the next steps described below. Create
a report that focuses on the IS used to support the operation of your organization
in your case study and answer the following questions.
Week 1 Project Tasks
In this week, create a report that focuses on the current status of your IS. In the
report complete the following tasks:
1. Create a scope for your application that you’ll design. The scope should consist
of the following components:

General project information (name, sponsor, and project manager)

Problem or opportunity statement

Project objective

Project description

Business benefits

Estimated project duration for the whole development cycle of the project, not just
the design
2. Identify the stakeholders for your project and identify at least five (5) key
stakeholders’ needs. For each need, discuss the business problems to be solved
3. From your needs, determine at least seven (7) target-system features.
4. Produce a requirements management plan for your project. This plan will
include:

Requirements criteria or categories

Feature request process

Methodology for collecting input into the requirements process

Traceability

Meta-data to track

Deliverables to produce

Processes, policies, and procedures
Running Head: PROJECT – WEEK 1
Contents
Project Scope ………………………………………………………………………………………………………………… 1
Project Information ……………………………………………………………………………………………………… 1
Problem Statement ………………………………………………………………………………………………………. 1
Project Objective …………………………………………………………………………………………………………. 1
Project Description ………………………………………………………………………………………………………. 2
Project Timetable ………………………………………………………………………………………………………… 3
Stakeholders …………………………………………………………………………………………………………………. 3
Stakeholder Needs ……………………………………………………………………………………………………….. 4
Target-System Features…………………………………………………………………………………………………. 5
Requirement Management Plan …………………………………………………………………………………….. 5
Requirements Collection ………………………………………………………………………………………………. 5
Requirements Tracking and Approval ……………………………………………………………………………. 6
Requirements Analysis …………………………………………………………………………………………………. 6
Categories ………………………………………………………………………………………………………………. 6
Priority …………………………………………………………………………………………………………………… 7
Deliverables ………………………………………………………………………………………………………………… 7
References …………………………………………………………………………………………………………………….. 9
MIS 6000 PROJECT – WEEK 1
1
Upgrading Piper Clinic WinOMS System
Project Scope
Project Information
Project Name
Piper Clinic WinOMS System
Project Sponsor
Piper Clinic
Project Manager
Sneha Vepuri
Problem Statement
To operate a healthy business, healthcare providers are required to manage large amounts of
information in an efficient manner. Due to this fact, information systems play a critical role in the
operations of the smallest private practices to the largest hospitals. The Piper Clinic, a specialty
dental practice in St. Petersburg, Florida. The Piper Clinic has been using the WinOMS system for
over a decade which is a practice management software designed to help small to medium sized
dental offices store, retrieve and make use of information to enhance business operations.
However, WinOMS system currently used at the clinic doesn’t meet all the requirements of the
employees. It isn’t user friendly and can be improved to improve the business efficiency.
Project Objective
The goal of this report is to evaluate the WinOMS software and see if it meets all the objectives
required by The Piper Clinic staff. The WinOMS system will be discussed in more detail and
requirements for system enhancements will be developed through suggestions from The Piper
Clinic employees. Recommendations on how to implement the system requirements will be
provided and discussed.
MIS 6000 PROJECT – WEEK 1
2
Project Description
The Piper Clinic is a small specialty dental clinic located in St. Petersburg, Florida. The clinic is
focused on treating a small subset of dental patients who suffer from a condition known as
temporomandibular joint (TMJ) disorder. The practice has 6 doctors who provides treatment to
patients both domestic and internationally.
The staff consists of 25 employees, who perform the various duties to keep the business
running. Due to the complexity of treating TMJ patients and the amount of information they
generate, there is a large need for a system that can store, retrieving and manipulating this
information in an elegant fashion. On a typical day the practice will see around 20-25 patients,
which is a small amount for typical dental offices. The difference with the Piper Clinic is that most
of these patients present with complex facial disorders and most are surgical candidates that require
2-3 hours of diagnosis and consultation. A typical patient of record will have a chart with well
over 30 pages of medical information.
To keep track of all this information and run the practice with minimal staff, The Piper Clinic has
been using the WinOMS system for the past 12 years. Before the integration of this system all this
information was paper driven and was catalogued in an extensive filing system. The Piper Clinic
is a service-oriented business. Its survival is dependent on providing treatment to new patients and
returning patients in pain. Below is an outline of the processes provided by The Piper Clinic to a
patient. Also note that there is a large amount of information generated with each patient.
The project will be focused on analyzing the existing Information system in Piper Clinic and
updating it to meet the business and the stakeholder needs that will help in improving the business
efficiency of the clinic.
MIS 6000 PROJECT – WEEK 1
3
Project Timetable
Below is a table that shows the estimated duration for the completion of the project. The estimation
assumes that the development team will consist of 3 developers, a Business Analyst, 2 testers and
a project manager. After the initial development testing and development will happen at the same
time like in Agile world.
Outcome/Deliverable
Estimated Completion
Detailed Business Requirement Documents
Week 2
Project Design Document
Week 4
System development and implementation Stage 1
Week 6
System Testing 1
Week 7
System development and implementation Stage 2
Week 10
System Testing 2
Week 11
System development and implementation Stage 3
Week 14
System Testing 3
Week 15
Final Release
Week 16
Stakeholders
The key stakeholders for the WinOMS system are:
1. Patients
Whenever patient has any dental trouble, he visits the doctor to consult about the issue. After
consultation with the referring doctor, he contacts the Piper Clinic to consult about his problem
and book an appointment.
MIS 6000 PROJECT – WEEK 1
4
2. Referral Doctors
Referral doctor performs the routine check-up of the patient and if he finds that the patient needs
a treatment from a specialist dentist, the doctor refers him to the Piper Clinic.
3. Paper Clinic Doctors
Paper clinic doctor performs the diagnosis and treats the patient.
4. Assistants
The assistant at the Piper Clinic does the lab check-up of the patient and assist the Paper Clinic
doctor during the treatment.
5. System Administrators
System Administrators at the Piper Clinic are responsible for the smooth running of the WINOMS
system. They administer the system and do the daily health check of the system.
6. Receptionists
Receptionists are responsible for appointments s, acting as a help desk and coordinating with
patients for payments.
Stakeholder Needs
Some of the stakeholder needs related to the WinOMS system are:
1. Ability to track key numbers like patient statistics (daily, monthly, yearly), revenues and
payments.
MIS 6000 PROJECT – WEEK 1
5
2. Ability to search for a patient based on name, insurance number and have the ability to
search both structured and non-structured data.
3. Ability to book/reschedule/cancel and pay online.
4. Ability to notify patients about appointments, treatment and payment reminders.
5. Ability to login in any system or platform (including mobile devices).
Target-System Features
1. Add Key Performance Indicators dashboard to the home screen.
2. Add patient search feature in the home screen.
3. Enable the existing software to integrate with a web portal.
4. Add automated notification feature for patients and other stakeholders.
5. Add online payment feature for patients.
6. Migrate from the onsite server to the cloud.
7. Human – Computer Interaction (HCI) improvement.
Requirement Management Plan
Requirements Collection
Development of project requirements will begin by understanding the business requirements if the
Piper clinic followed by the examination of the current system. Various interviews and discussions
will be conducted with the doctors and other employees of the piper clinic as well as select patients.
Once all the stakeholder needs are acquired, use cases will be used to further dissect the stakeholder
needs and create requirements.
Any change to the requirements can be communicated to the development team by the Piper Clinic
through email or by adding comments to the requirements in Target Process or in the bi-weekly
MIS 6000 PROJECT – WEEK 1
6
discussions which will conducted by the development team to get feedback and provide updates
to Piper Clinic management and staff.
Requirements Tracking and Approval
All the project requirements identified will be logged in Target Process – a project management
software. Requirements listed there will be analyzed, categorized, prioritized and quantified. Those
that survive analysis and receive approval will be added to the requirements traceability matrix
and traced through to project completion. Piper Clinic management will approve all the project
requirements.
Target process will also help in tracking the following metadata.
1. Dependencies
2. Hours spent to finish tasks which can be translated to budget spent
3. Impediments
4. Timeline
Requirements Analysis
Categories
The requirements will be categorized as follows:
1. Business Requirements
a. Provide 24/7 access to the system.
b. Improve business efficiency
2. Functional Requirements
a. Provide a dashboard with all the important indicators
b. Improve patient search functionality
MIS 6000 PROJECT – WEEK 1
7
c. Enable web appointments and payments
3. Non-Functional Requirements
a. Make the system user friendly
b. Make the system available through all platforms
Priority
All the requirements will be prioritized in the Target Process using these tags.
1. Must Have – High priority
These are the features that must be implemented into the system before going live and
need to be implemented first due to importance of the feature and the amount of testing
that he features need. These include Adding the performance indicators to the dashboard,
allowing appointment, payments to be made online through the system.
2. Must Have – Low Priority
These are the features that are needed for the system to go live but will need little testing
and development effort and are independent of other features. These include usage of
system through all platforms, improve patient search functionality.
3. Nice to Have
These are the features that can be implemented after the system goes live. These include
improving the user friendliness of the system, moving to cloud.
Deliverables
The following deliverables will be provided by the development team to Piper Clinic.
Deliverable 1 – Beta 1 release with ‘Must Have – High Priority’ features implemented.
Deliverable 2 – Beta 2 release with ‘Must Have – Low Priority’ features implemented.
MIS 6000 PROJECT – WEEK 1
Deliverable 3 – Alpha release with all features implemented.
Deliverable 4 – Final release.
After each release, Piper Clinic staff can provide feedback to the development team and any
necessary changes based on the feedback will be implemented in the next release.
8
MIS 6000 PROJECT – WEEK 1
9
References
Coventry, T. (n.d.). Requirements management – planning for success!: techniques to get it right
when planning requirements. PMI® Global Congress 2015—EMEA. London: Project
Management Institute.
Project Management Institute. (2016). Requirements Management : A Practice Guide. Newtown
Square, Pennsylvania: Project Management Institute.

Purchase answer to see full
attachment