*** Plagiarism is not acceptable *** Overview of Project – As part of identifying a case study of my choice with a pertinent information system application. I have selected fictitious company called “Polltrack System “. As part of activity 4 need to complete on below tasks based on my activity 3. I have attached the previous activities and sample projects documents for week 4 assignment.i have also attached my classmate project just for the reference to complete for my assignment.(Just sample reference only ,my topic project was different than sample project) Week 4 Project Tasks Now that you have created use-case models for your system, you plan your design, implementation, and test phases Discuss the development methodology that you will use for your development process, clearly explaining the rationale of your choice.Determine a plan to study whether the implementation of your target system will be successful or not.Outline a test plan for your application, and design a format for test documentation that your testing members would use to explain how they tested the system (including what types of testing) to document the results of these tests. Create at least five (5) detailed test cases for your system-test phase.Design a stakeholder feedback form that will be used to capture comments from stakeholders during the acceptance phase. Include measures of usability that should be established and collected in the feedback form. Instructions: Research Paper in in APA format. Plagiarism is not acceptable. (Please consider this top priority).For Activity 4 complete instructions are specified. All instructions or tasks must be addressed.( Try to address all the information specified in each task )Activity 4 is minimum 4 to 6 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
polltrack_system__a3.doc
sample_project.docx
Unformatted Attachment Preview
Running head: POLLTRACK SURVEY SYSTEM
1
PollTrack Survey System
1) Online Survey payment
Typically, our user is the survey respondent and since they are not required to make any payment we will
assume the client are the ones to be making the online payment. Therefore, for this case when we refer to
user we mean the client who needs the survey. All user will be required to register with the Polltrack
system. The system will then request them to make payment and once they do their accounts will be
updated and a confirmation email will be sent to them saying that payment has been received.
POLLTRACK SURVEY SYSTEM
2
2) Place survey Request
Once the payment is made then the survey requests are placed to generate questionnaires to participate in
the survey. Placing survey request is our second user case model and here clients enter the information
about their survey. The scope of place survey request involves the client logging and finalize the
questionnaires they will available for the survey. The client can further use the case model to modify the
questionnaires list to make the changes. The Process include system generate random questions based on
the information provided by client and admin can do necessary changes to that. Admin and client needs to
update on the questionnaires for each survey. The process further includes the displaying of finalize
questionnaires list to confirm the survey request.
POLLTRACK SURVEY SYSTEM
3
3. Survey Results
This is our third subject for use case model. Unlike the other two which were process this is component.
The scope of survey results includes survey data from various users. Furthermore, Analyst work on the
database which store all the survey data and analyzes the data to generate the reports. The final survey
reports sent to clients.
POLLTRACK SURVEY SYSTEM
4
Use Case Descriptions
1)
User case Title
Online Survey Payment
Description
A survey client need to be able to log into his account and
make payment using the availed payment method if they are
pending payments on his profile
Flow of events
Special requirement
Client/user require a valid payment form such as a debit card
POLLTRACK SURVEY SYSTEM
5
or credit card
Precondition
Client /user ought to have valid credentials
Post condition
The profile of the user need to have the pending payment
updated
Extension
A valid card used to make payment should process the pay
Relationships
Update system for online payment
2)
User case title
Place Survey Request
Description
A survey client need to be able to log into his
account and enter their business names, location,
service or product offered, target interviewees
which can be used system to generate sample
questionnaires to users.
POLLTRACK SURVEY SYSTEM
6
Flow of events
Special requirement
none
Precondition
Client need to have credentials that are valid and
cleared the payments.
Post condition
Survey questionnaires need to be updated
Extension
none
Relationship
Confirm questionnaires and edit questionnaires
POLLTRACK SURVEY SYSTEM
7
References
Requirements management: A practice guide. (2016). Newtown Square, Pennsylvania
Contents
Development Methodology ……………………………………………………………………………………………… 1
Evaluation Plan ………………………………………………………………………………………………………………. 1
Test Plan………………………………………………………………………………………………………………………… 2
Test Template ……………………………………………………………………………………………………………… 2
Stakeholder Feedback Form …………………………………………………………………………………………….. 5
References ……………………………………………………………………………………………………………………… 6
MIS 6000 PROJECT – WEEK 4
1
Upgrading Piper Clinic WinOMS System
Development Methodology
The project of upgrading Piper Clinic WinOMS System will take about 16 weeks and includes
quite a few requirements. It’s important for the project team to choose the correct development
methodology to complete the project in time and within budget. Some of the important
requirements for this project are about improving the user experience. Agile development
methodology enables the team to receive regular feedback as product is develop in small iterations
in Sprints that are 2 weeks long. When dealing with such requirements, it’s very important to
receive regular user feedback to develop the features for complete user satisfaction and in time.
The requirements also cover various parts of the WinOMS system like payments, appointments,
dashboards etc. Since these are major components of the system it’s important to test them
thoroughly and this is possible if the features are tested independently and immediately after their
development and Agile development also enables the team to do it. This also enables to find issues
early in the process and fix them so that other dependent features are not affected. Because of the
above specified reasons, the project development team will be implementing the Agile
Development methodology and Scrum will be used.
Evaluation Plan
It’s important to have a plan about how to evaluate the implementation of the project and determine
if the current rate of development will be sufficient for the successful implementation of the
project. For this project, the project team will create an estimated project time line with multiple
beta releases to implement all the features in stages. After each Sprint, the timeline will be
evaluated, and decisions will be taken about altering the development timeline or
MIS 6000 PROJECT – WEEK 4
2
excluding/including certain feature to finish the minimum viable product in time. Also burn down
charts will be created using Target Process tool to calculate the progress of both the project and
the sprint. These tools will help the Project Manager to study the implementation of the project
and determine if any changes are required for it to be successful.
Test Plan
Each feature’s implementation is broken down into number of stories in the beginning of the sprint.
For each story the tester will be creating a test plan that includes all the tests for the story. The test
plan goes into a test suite which is associated with the feature. The individual tests are created by
the tester during the planning phase after discussion with the developers and Business Analyst to
clearly understand the product of the story.
Test Template
Below is the test template that will used by testers to show what’s been tested for each story. Again,
this will be an electronic form within target process tool for each story. Integration testing will
have a similar form but will attached to the features/epics instead of the story.
Test-case-template.
doc
1. Online Payment Test Case
Test Step
Expected Result
Users clicks on profile page
Profile page opens
User clicks on payments
Payments subsection opens
MIS 6000 PROJECT – WEEK 4
User has a pending payments
3
Payments subsection shows the exact value in dollars
and pay button should be shown.
User has no pending payments
Payments subsection shows ‘no pending payments’
and pay button should not be shown
Users clicks on pay button
All the available payment options should be shown
User enters valid payment type Payments get processed and user gets a notification
information
User enters invalid payment type Payments doesn’t get processed and user gets a failure
information
notification
2. Online Scheduling Test Case
Test Step
Expected Result
Users clicks on profile page
Profile page opens
User clicks on appointments
Appointment subsection opens
User has a pending appointments
Appointment
subsection
shows
the
pending
appointments and modify/cancel button and new
button are shown
User has no pending appointments
Appointment subsection shows no appointments and
modify/cancel button is not shown but shows new
button.
Users clicks on new button
User
button
clicks
on
All the available appointment options are shown
modify/cancel All the appointment details are shown, and user can
change the details
MIS 6000 PROJECT – WEEK 4
User enters submit button
4
Appointment is booked, and user gets a notification
3. Online Portal Login Test Case
Test Step
Users enters the portal address
Expected Result
Portal home page opens
User enters correct email and Portal opens the user home page
password
User enters invalid email and User gets an invalid warning and ‘Forgot Password’
and ‘Forgot Username’ buttons
password
4. Patient Search Feature Test Case
Test Step
Clinic staff logs into the system
Expected Result
System home tab opens
Users clicks on search feature in the Patient Search form opens
patient tab.
User enter last name and clicks on Patient results are shown if there are any patients in the
search
database matching the criteria and if not shows no
patients found matching the parameters
User enters first name and clicks on Patient results are shown if there are any patients in the
search
database matching the criteria and if not shows no
patients found matching the parameters
MIS 6000 PROJECT – WEEK 4
5
User enters referral doctor name Patient results are shown if there are any patients in the
and clicks on search
database matching the criteria and if not shows no
patients found matching the parameters
User enters doctor name and clicks Patient results are shown if there are any patients in the
on search
database matching the criteria and if not shows no
patients found matching the parameters
User enters insurance type and Patient results are shown if there are any patients in the
clicks on search
database matching the criteria and if not shows no
patients found matching the parameters
5. Dashboard Test Case
Test Step
Expected Result
Clinic staff logs into the system
System home tab opens
Users clicks on dashboard tab
Dashboard opens showing all the KPIs
User clicks on any individual KPI
All the KPI details are shown
Stakeholder Feedback Form
Attached is the stakeholder feedback form. This form will be in Target Process and can be filled
electronically. The feature will be a dropdown that will contain all the available features and that
will attach the feedback to the feature for better collaboration.
Stakeholder
Feedback Form.doc
MIS 6000 PROJECT – WEEK 4
6
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
