*** 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 5 need to complete on below tasks based on my previous activities. I have attached the previous activities and sample projects documents for week 5 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 5 Project Tasks Now that you have created use-case models for your system, you will continue your system design by completing your class diagram and applying behavioral diagrams. 1. Extend your class diagram by including associations, indicating the object role and multiplicity on each end of your associations. Add any new classes, attributes, or operations that you may not have considered in your Week 3 diagram. Specify the data type and visibility of each attribute. 2. Develop sequence diagrams for two use-case scenarios from your W3 Project. Justify any assumptions on some of the messages passed between objects. Clearly indicate what objects are involved in each diagram. 3. Develop activity diagrams for two usecase scenarios from your W3 Project. The use-case scenarios may be the same or different from task 1. 4. Develop a non-trivial state diagram (the diagram must feature at least four (4) states) for at least one use-case or usecase scenario for your system. Instructions: Research Paper in in APA format. Plagiarism is not acceptable. (Please consider this top priority). For Activity 5 complete instructions are specified. All instructions or tasks must be addressed.( Try to address all the information specified in each task ) Activity 5 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
polltrack_system__a4.doc
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
Running Head: POLLTRACK SYSTEM
1
PollTrack System
Name
Institutional Affiliation
Date
POLLTRACK SYSTEM
2
PollTrack System
Development Methodology
To develop the system, we will use the Agile Software development methodology. The reason
for using this methodology is because it allows requirements and solutions to evolve during
development. That is, it allows changes to be made where necessary during the development
hence making sure the application delivered is of high quality. The methodology promotes
adaptive planning allowing the system developers to come up with a good plan for developing
the Polltrack System. In addition, the methodology allows evolution development where new
features can be easily added during the development hence leading to continual improvement
(Vijayasarathy & Butler, 2016). It is for reasons like this the system will be easy to develop and
correct errors and bugs in time.
The PollTrack System will be developed through the use of iterative and incremental
development methods which are part of agile software development methodology (Abrahamsson
et al., 2017). This method will develop a working system quickly in the early stages of the
software lifecycle. It is more flexible hence making it easier to make changes on scope and
requirements. It will also be easier to test and debug the PollTrack System in a small iteration. In
addition, risks are easily identified and managed in a given iteration (Papadopoulos, 2015).
Test Plan
The PollTrack System will be tested thoroughly before final deployment. All features will be
tested and documented. In case of an error, the feature will have to debug and retested again until
it is error free. This will ensure the final system is working as expected and of high quality.
POLLTRACK SYSTEM
3
Test Cases
The table below represents test cases for the PollTrack System.
Test
Test Case
Precondition
Test Data
Steps
Cas
Expected
Actual
Output
Result
e ID
TC1
TC2
s
Check if the
The system
Valid
Enter correct
The system is
client can log
should be up
username
client login
expected to
in into the
and running
and
details.
accept the
system.
and the client
password
client’s login
should be
details and
already
login
registered.
successfully.
Check if the
The client
Valid credit
Enter valid
The system
client can
should have
card details.
credit card
should accept
make
already
details.
the credit
payment.
signed in the
card details
system.
and make
payment
selected by
the client. In
addition, the
system show
POLLTRACK SYSTEM
4
display
payment
success
message and
the client
should
receive a
notification
about the
same.
TC3
Check if the
The user
Business
The client
The system
client can
should have
names,
will have to
should
place a
already
location,
enter
generate
survey
signed in the
service or
business
questionnaire
request
system and
product
names,
s and display
through the
selected Place offered, and
location,
them to the
system.
Survey
target
service or
client. In
Option.
interviewees
product
addition, a
.
offered, and
dialog will
target
pop up on the
interviewees
system asking
.
if the client is
satisfied with
POLLTRACK SYSTEM
5
the generated
question. If
the client is
not satisfied
with the
questionnaire
then he/she
can modify it
otherwise the
system will
save the
questionnaire
as it is.
TC4
Check if the
The client
Click event
The Data
The client
client will
should have
for the send
Analyst will
should
receive
already
to the client
analyze data
receive the
survey
placed survey
button.
stored in the
generated
results.
request and
database and
results send.
the
the results
questionnaire
are then sent
s filled online
to the client
through the
by clicking
POLLTRACK SYSTEM
TC5
6
system by the
send to the
targets.
client button.
Check if the
The
Click event
The
The displayed
administrator
administrator
for the
administrato
questionnaire
can Display
should be
display
r will have
should be
client’s
signed in and
button.
to view the
visible to the
questionnaire
the client
questionnair
target
s to the target
should have
e then click
audience for
audience
already
the display
them to fill it.
through the
generated
button to
system.
his/her
display it.
questionnaire
s through the
system.
The actual results column will be filled during the actual testing of the system.
Evaluation Plan
The PollTrack System will be regularly evaluated to check if the project is on the right track.
Through iterative software development method, the team will create prototypes and the beta
releases in a given timeline. The timeline will help to determine the rate of system development.
The prototypes and the beta releases are used by users in order for them to test the various
elements of Human-Computer Interaction (HCI). The user’s feedback is collected and analyzed
in order to determine which areas are okay and which areas need to be improved. This is also
useful when it comes to determining if the project will be a success or a failure.
POLLTRACK SYSTEM
7
Through iterative development, the project has a high probability of being a success as long as
the project manager will pay attention to users new requirements. This means the manager will
have to incorporate the requirements to the existing ones and change the project scope where
necessary. With this kind of flexibility, it will be possible to deliver what the stakeholders need
at the end of development.
Project management tools will also be used to track the progress of development in real time.
These tools will indicate the areas which are going on as expected and which are not. These tools
are good in visual presentation by providing necessary graphical charts such as Gantt charts and
burn down charts. These charts help the project manager and the development team to have a
clear picture of the project progress.
Stakeholder feedback form
Name_____________________________________________
Date___________________________
Which type of user are you?
Survey Client☐ Survey Responder☐Administrator☐Data
Analyst☐other_____________________
Kindly answer the question below to your knowledge best.
Questions
Fill or check where
appropriate
Any Comment
POLLTRACK SYSTEM
1. How does the
system interface
8
Poorly Designed ☐ Fairly
designed☐ Best Designed☐
look generally?
2. Was the system easy Yes☐ No☐
to use?
3. How learnable is the
Hard☐ Easy☐ Very Easy☐
system?
4. The number of
_______Errors
errors encountered
during a single use?
5. Is the system
Yes☐ No☐
memorable?
6. Did the system
satisfy you?
Very satisfied☐
Somewhat
satisfied☐Neutral☐
Somewhat dissatisfied☐
Very dissatisfied☐
7. Which features did
➢ ___________________
you expect in the
➢ ___________________
system and were
➢ ___________________
missing?
➢ ___________________
➢ ___________________
POLLTRACK SYSTEM
9
➢ ___________________
➢ ___________________
8. Does the system
Yes☐ No☐
perform all the basic
tasks in your area of
use?
9. What is your
➢ ___________________
attitude towards the
➢ ___________________
system?
➢ ___________________
10. Are you comfortable Yes☐ No☐
to continue using the
system?
11. What is the system
High☐ Medium☐Slow☐
performance speed?
12. What kind of
_________________________
improvements do
you want in the
future?
The above form will be used to test the usability of the PollTrack System. The stakeholders’
feedback will determine if the system will be rejected or accepted or even accepted with changes
to be made later. Acceptance phase is very important since it determines if the stakeholders are
POLLTRACK SYSTEM
10
happy with the system. If they are not then something is needed to be done. In case the system is
poorly designed then the stakeholders do not accept and this can even lead to a project failure
(Ammann & Offutt, 2016). This is why it is important to involve all stakeholders in all stages of
system development.
POLLTRACK SYSTEM
11
References
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Ammann, P., & Offutt, J. (2016). Introduction to software testing. Cambridge University Press.
Papadopoulos, G. (2015). Moving from traditional to agile software development methodologies
also on large, distributed projects. Procedia-Social and Behavioral Sciences, 175, 455463.
Vijayasarathy, L. R., & Butler, C. W. (2016). Choice of software development methodologies:
Do organizational, project, and team characteristics matter? IEEE Software, 33(5), 86-94.
…
Purchase answer to see full
attachment
