Health Insurance Management System

looneyvillestaticΛογισμικό & κατασκευή λογ/κού

15 Αυγ 2012 (πριν από 5 χρόνια και 3 μήνες)

395 εμφανίσεις



Health Insurance Management System


Team 1: Venkat Reddy

Jakka
, Sundeep Yama, Abe Elsaeed, Allen Tucker,
Ashley Plier, Tara Chengalva
la

CS656

Final Deliverable

Dr. Delugach



Team 1

7/31/2009


Team 1: Final Deliverable
2


Contents

Table of Figures

................................
................................
................................
................................
.............

5

Project Overview

................................
................................
................................
................................
...........

6

Additional Tests Executed

................................
................................
................................
.............................

8

Test

Summary

................................
................................
................................
................................
...............

8

Resources

................................
................................
................................
................................
......................

8

Team Process and Structure

................................
................................
................................
.........................

9

Iterative Development

................................
................................
................................
..............................

9

Test Approach

................................
................................
................................
................................
.........

10

Roles

................................
................................
................................
................................
........................

10

Lessons Learned

................................
................................
................................
................................
..........

11

Appendix A: Schedules

................................
................................
................................
................................

12

HIMS Project Schedule
Three week long iterations with use cases being divided up into behaviors.
...

12

Broke Down Semester Schedule
Each week in an iteration focuses on a different use case.

...............

13

Final Schedule

................................
................................
................................
................................
.........

14

Appendix B: Traceability Matrix and Functional Testc
ases

................................
................................
........

15

Traceability Matrix

................................
................................
................................
................................
..

15

Test Suites

................................
................................
................................
................................
...............

19

Test Cases

................................
................................
................................
................................
................

20

Test Case ID 1: Au
thentication

................................
................................
................................
............

20

Test Case ID 1.1.1: Invalid Login with Invalid Username

................................
................................
....

21

Test Case ID 1.1.2: Invalid Login with Invalid Password

................................
................................
.....

22

Test Case ID 1.1.3: Invalid Login with Invalid Username and Invalid Password

................................
.

23

Test Case ID 1.2: First Login

................................
................................
................................
................

24

Test Case ID 2: Change Password

................................
................................
................................
.......

25

Test Case ID 3.0.1: Member Viewing Account Information

................................
................................

27

Test Case ID 3.0.2: Employer Viewing Account Information

................................
..............................

29

Test Case ID 3.0.3: Provider Viewing Account Information

................................
................................

31

Test Case ID 3.0.4: Operator Viewing Account
Information

................................
...............................

33

Test Case ID 3.1.1: Member Privilege Not Granted

................................
................................
............

36

Test Case ID 3.1.2: Employer Privilege Not Granted

................................
................................
...........

39

Test Case ID

3.1.3: Provider Privilege Not Granted

................................
................................
............

42

Test Case ID 3.1.4: Operator Privilege Not Granted

................................
................................
...........

45

Test Case ID 3.2: Invalid User

................................
................................
................................
..............

47

Test Case ID 4: Update Account Information
................................
................................
......................

49

Team 1: Final Deliverable
3


Appendix C: Model Tests (Guided Inspections)

................................
................................
..........................

52

Authentication

Use case

................................
................................
................................
.........................

52

Change Password

Use case

................................
................................
................................
.....................

53

Update Account Information

Use case

................................
................................
................................
...

54

Update Account Information

Use case

................................
................................
................................
...

55

Design Class Diagram

................................
................................
................................
..............................

56

Authenticate Sequence Diagram

................................
................................
................................
............

5
7

Change Password

Sequence Diag
ram

................................
................................
................................
.....

58

View Account Information

Sequence Diagram

................................
................................
.......................

59

Update Account Information

Sequence Diagram

................................
................................
...................

60

Appendix D: Integration/Unit Tests

................................
................................
................................
............

61

AppFrameTest.java

................................
................................
................................
................................
.

61

AppMenuBarTest.java

................................
................................
................................
............................

67

ChangePa
sswordDialogTest.java

................................
................................
................................
............

69

HimsSuite.java

................................
................................
................................
................................
.........

72

LoginDialogTest.java

................................
................................
................................
...............................

73

LogInControllerTest.java

................................
................................
................................
.........................

76

LogInDataTest.java

................................
................................
................................
................................
..

79

LoginSuite
.java

................................
................................
................................
................................
........

82

AccountInfomrationPanelTest.java

................................
................................
................................
........

83

AccountInformationTest.java

................................
................................
................................
.................

85

PrivilegeTest.java

................................
................................
................................
................................
....

91

UserContollerTest.java

................................
................................
................................
............................

93

UserSu
ite.java

................................
................................
................................
................................
.........

96

MemberControllerTest.java

................................
................................
................................
....................

97

MemberDataTest.java

................................
................................
................................
............................

99

MemberSuite.java

................................
................................
................................
................................
.

102

EmployerTest.java

................................
................................
................................
................................
.

103

OperatorTest.java

................................
................................
................................
................................
.

105

ProviderTest.java

................................
................................
................................
................................
..

108

SuperUserSuite.java

................................
................................
................................
..............................

110

SuperUserTest.java

................................
................................
................................
...............................

111

Appendix E: GUI Designs

................................
................................
................................
...........................

113

Chan
ge password.png

................................
................................
................................
...........................

113

enable disable account.png

................................
................................
................................
..................

114

Team 1: Final Deliverable
4


Enrollment deny.png
................................
................................
................................
.............................

115

First login.png
................................
................................
................................
................................
........

116

Invalid account.png

................................
................................
................................
...............................

117

Invalid
information.png

................................
................................
................................
........................

118

Invalid login.png

................................
................................
................................
................................
....

119

Invalid member id.png

................................
................................
................................
..........................

120

Invalid password.png

................................
................................
................................
............................

121

Invalid user id.png

................................
................................
................................
................................
.

122

Login Su
ccess.png

................................
................................
................................
................................
.

123

member privalages not granted.png

................................
................................
................................
....

124

new password.png

................................
................................
................................
................................

125

password don't match.png

................................
................................
................................
...................

126

Privalage not granted.png

................................
................................
................................
.....................

127

pr
ivilage not granted.png

................................
................................
................................
......................

128

process plan enrollment request.png

................................
................................
................................
...

129

register member.png

................................
................................
................................
............................

130

registermember.png

................................
................................
................................
.............................

131

required field missing.png

................................
................................
................................
....................

132

Update account information.png

................................
................................
................................
.........

133

View account information.png

................................
................................
................................
.............

134

View list.png

................................
................................
................................
................................
..........

135

View recent
claims.png

................................
................................
................................
.........................

136

view request list.png

................................
................................
................................
.............................

137




Team 1: Final Deliverable
5


Table of Figures

Figure 1 Statement coverage inadequate.
Moved to boundaries and error predictive methods.
.............

6

Figure 2 Defects exists within the system.

................................
................................
................................
...

7

Figure 3 Insufficient amount of functional regression testing for certain features.

................................
...

7

Figure 4 Iterative Development

................................
................................
................................
....................

9

Figure 5 Testing Approach

................................
................................
................................
..........................

10




Team 1: Final Deliverable
6


Project Overview

An overview of the project from beginning to end. Regardless of whether you started the project in this
class or in CS 652, consider just this semester's
work.

Refer to your previous deliverables (I have them already) if need be. Make sure any references are clear
and specific (don't just say "this test was in deliverable 2"); refer to page numbers, sections, test ids, etc.
Do NOT turn in copies of the prev
ious deliverables (but do read numbers 3, 4 and 5).

Team 1 has selected to implement the Health Insurance Management System project. As described in
the project’s proposal document, “t
he system could be used to help better manage the human
resources of a
health care maintenance organization, a
n

HMO.
” Where possible, the design
specification, as it is described in the project’s package, shall be implemented. However, we
have

allow
ed

for adjustments when deemed necessary.
Any

c
hanges to the specification in terms of
requirements and design models
have

be
en

identified and thoroughly documented. The general
architectural style presented within the design specification is component
-
based. One of the major
components in the
design is a database for storing user data. The design specification does not dive into
the specifics of this component and as such, neither shall the implementation for the purpose of this
project. However, in order to develop some of the targeted behav
iors, this component has been
identified as being necessary and will be implemented with stubbed code. Over all, the design
specification has been documented very thoroughly, the models and diagrams are clear and concise,
and the functional requirements a
re traceable.























0%
20%
40%
60%
80%
100%
120%
14-Jun
16-Jun
18-Jun
20-Jun
22-Jun
24-Jun
26-Jun
28-Jun
30-Jun
2-Jul
4-Jul
6-Jul
8-Jul
10-Jul
Coverage (%)

Timeline (Date)

Verification Test Coverage

Goal Coverage
Packages
Classes
Lines of Code (LOC)
Figure
1

Statement coverage inadequate. Moved to boundaries and error predictive methods.

Team 1: Final Deliverable
7










































Personnel shifts due to deliverable deadlines



Outstanding Work Items



Functionality (use cases not
implemented)

HIMS_
0.01
HIMS_
0.02
HIMS_
0.03
HIMS_
0.04
HIMS_
0.05
HIMS_
0.06
HIMS_
0.07
HIMS_
0.08
HIMS_
0.09
Total Passed
1
3
5
22
16
18
18
22
13
Test Count
5
5
5
26
16
19
19
32
13
0
5
10
15
20
25
30
35
System Test Runs

Functional Test Analysis

0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
Failure Rate

Feature Based Failure Rates

Authentication
Change Password
Invalid Login
Update Account Information
View Account Information
Invalid UserID
Figure
3

Insufficient amount of functional regression testing for certain features.

Figure
2

Defects exists within the system.

Team 1: Final Deliverable
8




Defects


Additional Tests Executed

Turn in any additional tests that you performed since your last deliverable. If some tests were described
but not run in the last deliverable, then turn them in again with the results filled in.

Test Summary

An overall test summar
y, summarizing ALL of the tests you have, indicating whether they were run,
whether they passed, whether they have been run through regression testing, and whether any
detected errors were fixed (don't identify error source in the summary).

Resources

Java
and JUnit

After our team had chosen a project to implement and test, which was the Health Insurance
Management System project, we decided to develop our system in Java. Java has some nice features
such as JUnit. JUnit is very handy in the fact that it
creates the test suites for the developer as well as

in

stubbing out the test classes for the unit tests and integration tests.


NetBeans IDE

We decided the best solution for us for our development environment was to use Netbeans 6.5 because
it was free

and of

good quality, and

majority of the developers in our group were familiar with
this

IDE.
It

also

ha
s

some nice built
-
in features as well as plug
-
ins for testing software. Netbeans provides a
textual and visual output of the results from
the executed JUnit tests. It

also

provided our team with an
html reporting capability that contains information such as total tests executed, number of failures,

number of errors, success rate,

execut
ion time
s
.


EMMA


In addition to using JUnit, we also used EMMA. EMMA is a code coverage tool that can create reports
of the exact amount of lines of executable lines of code that was tested in the integration and unit tests
as well as showing visually to the developer wha
t classes, methods, and lines in the methods were
executed in the integration and unit tests executed. This is very convenient for the developer because
it allows them to see if there were any parts of a class that was not tested or any parts of a method

that
was not tested, such as if all conditions in a method were covered.


Apache Ant

For our weekly software builds, integration testing, unit testing, and regression testing, our team used
Apache Ant. It is a build tool that allows the developer to tailor the build scripts better to their software
application, and
that

is what Netbeans

uses, as well. The build tool created our build and then executed
all unit and integration tests each week.




Team 1: Final Deliverable
9


GoogleCode

At the beginning of our project, we were unsure of which route to go for ou
r

version control. However,
in one of the classes

at the beginning of the semester, GoogleCode was mentioned as a good source for
version control, defect tracking, and documentation. After checking into it, we decided that this had
everything we needed. The version control was SubVersion
,

which
plugged in easily with Netbeans. It

also

ha
s

a nice feature
,

which

shows


the entire software package as well as all versions of the individual
files on the GoogleCode website.

In order to track our defects, we used the GoogleCode issue tracker.
For

the
size of

our

project, we didn’t need anything more meticulous. The issue tracker had all fields we
needed such as date found, issue summary, creator of the issue, and prior
ity. As far as documentation

is
concerned
, we used Microsoft products, such as Word
,

Excel

and PowerPoint
.

Team Process and Structure

Iterative Development

Team 1 has chose
n

to utilize an iterative development process for the implementation of the

Health
Insurance Management System project with the adoption of several practices from
the agile
methodologies. We

assum
ed

that the Inception phas
e of the development process had

been completed
and
that the resulting artifacts were

contained within the p
roject package with the exception of an
y
source code and binaries. Those artifacts would have
begun

to be delivered during the first iteration of
the Elaboration phase. Functional behaviors

that were

identified and documented

via use cases,

were

analyzed

in the inception phase of the process

and

were

assigned an iteration for implementation.


Figure
4

Iterative Development

Test
-
driven development, where developers create automat
ed unit tests that define code requirements
before writing the code itself,
was

utilized during the implementation activity. In addition, all source
code
was

continuously integrated through an autom
ated build process that executed unit tests and
provided
the test results. This allowed

the

developers to identify problematic areas and adapt code as
necessary as well as provide regression testing.


Team 1: Final Deliverable
10


Test Approach

A mixture of both
white and black box testing was

conducted during the development of the Health
Insurance Management System project. As behavio
rs were

selected for implementation, collaborative
classes
were

identified an
d assigned to components. I

T
he intention of this assignment
was
to group
classes that provide
d

like behaviors to the same component level for reusability purposes and to reduce
co
de redundancy. Components were
then assigned to a developer or smal
l group of developers, who
wro
te
the
class level unit tests and component level
unit tests as well as d
eveloped

the component
itself. This all
was

developed to meet the design specification. Source code
was

then written in order to
realize the design specification until all class and component level unit test
s

pass
ed. Once this occur
r
ed
,
the refactoring
of the source code
took

place to account for optimizations. In addition to the
component developers, an integration developer, or group of developers
were

responsible for
producing the “glue code” to achieve the component
collaborations, which actualized

the desired
functional behavior. A separate set of unit tests w
ere

written by this group of developers in order to
verify these behaviors. Integrated software
was

then delivered to the

validation test team, who
execute
d

the functional tests that were dev
eloped based on the requirements of the behaviors under
development. Th
e results of these tests were

documented and captured

in an issue log where they
were

evaluated and scheduled

for work.




Figure
5

Testing Approach

Roles

Val
idation

Team Duties:

This team will write and test the Functional Tests for the project as well as
write up the documentation. They will be able to pull software builds from the code repository as well
as push/pull from the Defect List. The software buil
ds will be what this team will execute in order to run
the tests. They will also push final releases to the Release Repository.

Team members:

1.

Venkat Reddy

2.

Sundeep Yama

Team 1: Final Deliverable
11


Integration Development Team:

This team will develop the functional build that can be executed by a
user. This will be done by integrating the components into a collaboration for the software. The
executable will be passed off to the Validation team. They will be able to push soft
ware builds as well as
push/pull code from the code repository. They will also be able to push/pull from the Defect List. The
automated build scripts will be written by this team, as well.

Team members:

1.

Abe Elsaeed

2.

Allen Tucker

Component Development Team
:

This team will develop the unit
-
level tests as well as the component
-
level tests. They will develop the components that will be passed off to the Integration Development
Team. This team will also develop any stubs for the components not yet developed
which are necessary
for the integration development of the software for the current iteration. These, too, will be passes off
to the Integration Development Team. They will be able to push/pull code from the code repository as
well as push/pull from the
Defect List.

Team members:

1.

Ashley Plier

2.

Tara Chengalva

Note
:

Each team will pass their completed work up to the team directly
above

it. All teams will have
access to the Defect List. The Verification Team will, however, verify that the defects have bee
n
successfully fixed.


Lessons Learned

Lessons learned
-

if you have specific examples, use them.




Guided inspection of models decrease wasted coding effort



White box statement coverage insufficient



Adopt new strategy given chance to do complete rework of
project (e.g.
boundaries, error guessing)



Flexible Team



Team 1: Final Deliverable
12


Appendix A: Schedules

HIMS Project Schedule

Three
week long iterations with use cases being divided up into behaviors.






























Iterative Development

Use Case

Inception

Elaboration

Construction

Transition

ID

Title

I1

E1

E2

C1

C2

C3

C4

T1

1

Authenticate

------

X







1.1

InvalidLogin

------


X






1.2

FirstLogin

------


X






2

ChangePassword

------

X







2.1

InvalidPass
word

------



X





2.2

PasswordsDon’tMatch

------



X





3

ViewAccountInformation

------

X







3.1

PrivilegeNotGranted

------


X







3.2

InvalidUserID

------


X







4

UpdateAccountInformation

------

X








4.1

InvalidInformation

------



X





5

ViewRecentClaims

------




X




5.1

MemberPrivilegeNotGranted

------





X



5.2

InvalidMemberID

------





X



6

ViewList

------




X




7

SearchForMember

------




X




7.1

InvalidAccount

------





X



7.2

PrivilegeNotGranted

------





X



8

ViewRequestList

------




X




9

ProcessPlanEnrollmentRequest

------






X


9.1

EnrollmentDeny

------







X

10

Enable/DisableAccount

------






X


11

ResetPassword

------






X


12

RegisterMember

------






X


12.1

RequiredFieldMissing

----
--







X

Team 1: Final Deliverable
13


Broke Down Semester Schedule

Each week in an iteration focuses on a different use case.



















Weekly Schedule

Use Case

Elaboration 1 (E1)

Elaboration 2 (E2)

ID

Title

June 8
-
14

June 15
-
21

June 22
-
28

June 29


July 5

July 6
-
12

July 13
-
19

1

Authenticate

X






1.1

InvalidLogin




X



1.2

FirstLogin





X


2

ChangePassword


X





3

ViewAccountIn
formation


X





3.1

PrivilegeNotGranted





X


3.2

InvalidUserID






X

4

UpdateAccountInformation



X





Team 1: Final Deliverable
14


Final Schedule

Natural grouping of features mandated schedule adjustments…(birds of a feather).


Team 1: Final Deliverable
15


Appendix B:
Traceability Matrix and
Functional Testcases


Traceability Matrix

Indicates items that are out of our scope for this project.



ID

Requirement

Use Case(s)

Test Case(s)

1

The system shall have a User user type.

UC1

TC1

1.1

Users shall use the system by starting it as a
java application.

UC1

TC1

1.2

The User shall enter the following to login
to the system: User ID Number, Password

UC1

TC1

1.3

The User shall have the ability to change
their password once they have logged into
the system.

UC2

TC2

2

The system shall have a SuperUser user
type.

UC1

TC1

2.1

The SuperUser shall have the ability to view
a list of all of the Members in the system.

UC6


2.2

The SuperUser shall have the ability to
search for a Member based on the
following information: Member’s Name,
Member’s User ID

啃U


3

周攠
獹獴Vm⁳桡 l⁨慶攠愠Prov楤敲⁵獥爠瑹p攮

啃U

呃T

3⸱

䥦⁴桩猠楳V瑨攠晩f獴⁴im攠瑨攠P牯v楤e爠桡猠r獥V
瑨攠Wy獴VmⰠ瑨攠Prov楤敲⁳ 慬a⁢攠慳a敤⁴o
晩f氠lu琠a⁳業pl攠one
-
瑩m攠en牯汬m敮琠eorm.

啃ㄮU

呃T⸲

3⸱⸱

周攠敮eo汬m敮琠eorm⁳桡 氠慳欠瑨W⁐rov楤敲e
景爠
瑨攠景汬o睩湧⁩湦orm慴aonJ 瑨敩爠Won瑡W琠
楮景牭a瑩Wn

啃ㄮU

呃T⸲

3⸱⸲

䅬氠晩敬l猠Vn⁴U攠敮牯汬m敮e⁦ 爠獨慬l⁢攠
牥煵楲敤.

啃U


3⸱⸳

䅦瑥爠rUe⁐rov楤敲eU慳⁦楬 eTu琠瑨攠
敮牯汬m敮琠eormⰠ瑨攠Wy獴em⁳桡 氠l慶攠瑨W
Provider’s enrollment information.

啃ㄮU

呃T

3⸲

周攠P牯v楤敲emay⁶i敷r⁵ T慴a⁴Ue
敮牯汬m敮琠楮eorm慴aon⁦ om 睩瑨楮⁴U攠
獹獴Vm⁡晴 r⁴U攠楮楴i慬agin映fU攠
P牯v楤敲e

啃㌬UU䌴

呃TⰠ呃
3.0⸳

3⸳

周攠P牯v楤敲e獨V汬⁶楥眠 o爠upT慴a⁡捣oun琠
楮景牭a瑩Wn⁦o爠瑨敩爠o睮wanT⁦ 爠rUe
景汬o睩湧J

Employer’s and Member’s

啃㌬UU䌳⸱Ⱐ
啃U

呃TⰠ呃
3.0⸳.呃T.1⸳

3⸳⸱

周攠慣aoun琠楮form慴aon⁴U慴a瑨攠Prov楤敲e
獨V汬⁶楥眠o爠異T慴a⁦o爠瑨敩爠e睮⁡捣oun琠
楳i

啃㌬UU䌴

呃TⰠ呃
3.0⸳


Team 1: Final Deliverable
16


3.3.1.1



The Provider’s contact information

啃㌬UU䌴

呃Tⱔ䌳⸰.3

3⸳⸱.2



The Provider’s User ID number



3⸳⸲

周攠慣aoun琠楮form慴aon⁴U慴a瑨攠Prov楤敲e
shall view or update for the Employer’s
慣捯un琠i猺

啃㌬UU䌴

呃Tⱔ䌳⸰.3ⱔH3⸱.3

3⸳⸲.1



The Employer’s contact information

啃㌬UU䌴

呃T⸰.3ⱔH4

3⸳⸳

周攠慣aoun琠
楮form慴aon⁴U慴a瑨攠Prov楤敲e
shall view or update for the Member’s
慣捯un琠i猺

啃㌬UU䌴

呃T⸰.3ⱔH4

3⸳⸳.1



The Member’s contact information

啃㌬UU䌴

呃T⸰.3ⱔH4

3⸳⸳.2



The Employer’s name



3⸳⸳.3



The Member’s Health Plan



3⸳⸳.4



Whether or not
the Member’s
M敤e捴慢汥⁨慳⁢ 敮em整.



3⸴

周攠P牯v楤敲e獨V汬⁢攠慢汥⁴o v楥i⁡汬⁣污 m猠
晩f敤⁦牯m⁴U敩爠o晦f捥c

啃U


4

周攠獹獴Vm⁳桡 l⁨慶攠慮⁅mp汯y敲euV敲e
瑹p攮

啃U

呃T

4⸱

䥦⁴桩猠楳V瑨攠晩f獴⁴im攠瑨攠Wmp汯y敲eU慳
u獥搠VU攠Vy獴emⰠHUe⁅mploy敲e
獨V汬⁢
慳步T⁴o⁦楬 ouW⁡ 獩mp汥lone
-
瑩W攠
敮牯汬m敮琠eorm.

啃ㄮU

呃T⸲

4⸱⸱

周攠敮eo汬m敮琠eorm⁳桡 氠慳欠瑨W⁅mp汯y敲e
景爠rU攠景汬o睩湧⁩湦orm慴aonJ 瑨敩爠Won瑡W琠
楮景牭a瑩Wn

啃ㄮU

呃T⸲

4⸱⸲

䅬氠晩敬l猠Vn⁴U攠敮牯汬m敮e⁦ 爠獨慬l⁢攠
牥煵楲敤.



4⸱⸳

䅦瑥爠rUe⁅mp汯y敲eU慳⁦楬 eTu琠瑨攠
敮牯汬m敮琠eormⰠ瑨攠Wy獴em⁳桡 氠l慶攠瑨W
Employer‘s enrollment information.

啃ㄮU

呃T⸲ⰠHC4

4⸲

周攠Nmp汯y敲emay v楥眠o爠upT慴a⁴U攠
敮牯汬m敮琠楮eorm慴aon⁦ om 睩瑨楮⁴U攠
獹獴Vm⁡晴 r⁴U攠楮楴i慬agin映fUe

䕭p汯y敲e

啃㌬UU䌴

呃TⰠ呃
3.0⸲

4⸳

周攠Nmp汯y敲e獨V汬⁶i敷 o爠upT慴a⁡捣oun琠
楮景牭a瑩Wn⁦o爠瑨敩爠o睮wanT⁦ 爠rUe
following: Employer’s and Member’s

啃㌬UU䌳⸱Ⱐ
啃U

呃TⰠ呃
3.0⸲

4⸳⸱

周攠慣aoun琠楮form慴aon⁴U慴a瑨攠䕭ploy敲e
獨V汬⁶楥眠o爠異T慴a⁦o爠
瑨敩爠e睮⁡捣oun琠
楳i

啃㌬UU䌴

呃TⰠ呃
3.0⸲

4⸳⸱.1



The Employer’s contact information

啃㌬UU䌴

呃TⰠ呃
3.0⸲

4⸳⸱.2



The Employer’s User ID number



4⸳⸲

周攠慣aoun琠楮form慴aon⁴U慴a瑨攠䕭ploy敲e
shall view or update for the Member’s
慣捯un琠i猺

啃㌬U
U䌴

呃TⰠ呃
3.0⸲

4⸳⸲.1



The Member’s contact information

啃㌬UU䌴

呃TⰠ呃
3.0⸲

Team 1: Final Deliverable
17


4.3.2.2



The Employer’s name



4⸳⸲.3



The Member’s Health Plan



4⸳⸲.4



Whether or not the Member’s
M敤e捴慢汥⁨慳⁢ 敮em整



4⸴

周攠Nmp汯y敲e獨V汬⁢攠慢l攠瑯⁡摤⁡
Memb敲e瑯⁴U攠Vy獴em.

啃ㄲ


5

周攠獹獴Vm⁳桡 l⁨慶攠愠Memb敲euV敲eWyp攮

啃U

呃T

5⸱

䥦⁴桩猠楳V瑨攠晩f獴⁴im攠瑨攠Memb敲eU慳⁵獥搠
瑨攠Wy獴VmⰠ瑨攠Memb敲⁳U慬a⁢攠慳a敤⁴o
晩f氠lu琠a⁳業pl攠one
-
瑩m攠en牯汬m敮琠eorm.

啃ㄮU

呃T⸲

5⸱⸱

周攠敮eo汬m敮琠eorm
獨V汬 慳欠瑨W⁍敭b敲e
景爠rU攠景汬o睩湧⁩湦orm慴aonJ 瑨敩爠Won瑡W琠
information and their Employer’s name.

啃ㄮU

呃T⸲

5⸱⸲

䅬氠晩敬l猠Vn⁴U攠敮牯汬m敮e⁦ 爠獨慬l⁢攠
牥煵楲敤.



5⸱⸳

䅦瑥爠rUe⁍emb敲eU慳⁦楬aeTu琠瑨攠
敮牯汬m敮琠eormⰠ瑨攠Wy獴em⁳桡 氠
V慶攠瑨W
Member‘s enrollment information.

啃ㄮUH⁕䌴

呃TⰠ呃
3.0⸱

5⸲

周攠Memb敲em慹⁶i敷 o爠upT慴a⁴U攠
敮牯汬m敮琠楮eorm慴aon⁦ om 睩瑨楮⁴U攠
獹獴Vm⁡晴 r⁴U攠楮楴i慬agin映fU攠
Memb敲e

啃㌬UU䌴

呃TⰠ呃
3.0⸱

5⸳

周攠Memb敲e獨V汬 v楥眠o爠upT慴a⁡捣ounW

楮景牭a瑩Wn⁦o爠瑨敩爠o睮wanT⁦ 爠rUe
following: Employer’s and Provider’s

啃㌬UU䌳⸱Ⱐ
啃U

呃TⰠ呃
3.0⸱

5⸳⸱

周攠慣aoun琠楮form慴aon⁴U慴a瑨攠Memb敲
獨V汬⁶楥眠o爠異T慴a⁦o爠瑨敩爠e睮⁡捣oun琠
楳i

啃㌬UU䌴

呃T

5⸳⸱.1



The Member‘s contact information

啃㌬UU䌴

呃T

5⸳⸱.2



The Member’s User ID number



5⸳⸱.3



The Employer’s name



5⸳⸱.4



The Member’s Health Plan



5⸳⸱.5



Whether or not the Member’s
M敤e捴慢汥⁨慳⁢ 敮em整



5⸳⸲

周攠慣aoun琠楮form慴aon⁴U慴a瑨攠Memb敲
獨V汬⁶楥眠o爠異T慴a⁦o爠
the Provider’s
慣捯un琠i猺

啃㌬UU䌴

呃T⸰.1

5⸳⸲.1



The Provider’s contact information

啃㌬UU䌴

呃T⸰.1

5⸳⸲.2



The Provider’s User ID number



5⸳⸳

周攠慣aoun琠楮form慴aon⁴U慴a瑨攠Memb敲
shall view or update for the Employer’s
慣捯un琠i猺

啃㌬UU䌴

呃T⸰.1

5⸳⸳.1



The Employer’s contact information

啃㌬UU䌴

呃T⸰.1

6

周攠獹獴Vm⁳桡 l⁨慶攠慮⁏p敲慴er⁵獥爠
瑹p攮

啃U

呃T

6⸱

佰敲慴o爠慣roun瑳⁳桡 氠扥l獥V⁵ o爠


Team 1: Final Deliverable
18


deleted by the system developers.

6.1.1

Their information shall include:



6.1.1.1



The Operator’s contact information



6⸱⸱.2



The Operator’s User ID number



6⸲

周攠佰敲O瑯r⁳桡 氠扥⁡扬攠瑯⁳敬散琠Wo v楥眠
o爠異T慴a⁴U攠fo汬o睩湧⁴yp敳eof⁡捣oun瑳W
b敳楤攠eU敩e睮㨠Prov楤敲H⁅mploy敲Ⱐ慮T
Memb敲

啃㌬UU䌳⸱Ⱐ
啃U

呃T⸰.4ⱔH4

6⸲⸱

周攠佰敲O瑯r⁳桡 氠扥⁡扬攠瑯 v楥眠o爠
upT慴a⁴U攠fo汬o睩湧⁩湦orm慴aon⁦o爠rU敩e
o睮⁡捣cunWJ

啃㌬UU䌴

呃T⸰.4ⱔH4

6⸲⸱.1



The Operator’s contact information

啃U

呃T⸰.4ⱔH4

6⸲⸱.2



The Operator’s User ID number



6⸲⸲

周攠佰敲O瑯r⁳桡 氠扥⁡扬攠瑯
v楥眠o爠
upT慴a⁴U攠fo汬o睩湧⁩湦orm慴aon⁦o爠rUe
Provider’s account:

啃㌬UU䌴

呃T⸰.4

6⸲⸲.1



The Provider’s contact information

啃㌬UU䌴

呃T⸰.4

6⸲⸳

周攠佰敲O瑯r⁳桡 氠扥⁡扬攠瑯 v楥眠o爠
upT慴a⁴U攠fo汬o睩湧⁩湦orm慴aon⁦o爠rUe
Employer’s account:

啃㌬UU䌴

呃T⸰.4

6⸲⸳.1



The Employer’s contact information

啃㌬UU䌴

呃T⸰.4

6⸲⸴

周攠佰敲O瑯r⁳桡 氠扥⁡扬攠瑯 v楥眠o爠
upT慴a⁴U攠fo汬o睩湧⁩湦orm慴aon⁦o爠rUe
Member’s account:

啃㌬UU䌴

呃T⸰.4

6⸲⸴.1



The Member’s contact information

啃U

呃T⸰.4

6⸲⸴.2



Their Employer’s name



6⸲⸴.3



The Member’s Health Plan



6⸲⸴.4



Whether or not the Member’s
M敤e捴慢汥⁨慳⁢ 敮em整



6⸳

周攠佰敲O瑯r⁳桡 氠桡v攠瑨攠慢楬楴i⁴o
慵瑨W物r攠a⁍敭b敲eWo⁢ ⁩n⁡ p慲瑩捵污l
H敡汴栠e污l.



6⸴

周攠佰敲O瑯r⁳桡 氠
Uav攠瑨攠慢楬楴i⁴o⁶i敷
瑨攠汩獴Wo映f敱e敳eV⁦ r⁈敡 瑨⁐污l
敮牯汬m敮琠m慤e⁢礠Memb敲献

啃U


6⸵

周攠佰敲O瑯r⁳桡 氠桡v攠瑨攠慢楬楴i⁴o
p牯捥cV⁴Ue楳琠o映f敱e敳e猠景爠䡥慬瑨⁐污l
敮牯汬m敮琠m慤e⁢礠Memb敲献

啃U


6⸶

周攠 佰敲慴o爠 獨V汬 U慶e 瑨攠
慢楬楴i Wo
敮慢汥l or T楳慢汥
Memb敲INmp汯y敲IProv楤敲e慣aoun瑳W

啃㄰


6⸷

周攠佰敲O瑯r⁳桡 氠桡v攠瑨攠慢楬楴i⁴o⁲ V整
瑨攠灡獳Wo牤 on
Memb敲INmp汯y敲IProv楤敲e慣aoun瑳W

啃ㄱ




Team 1: Final Deliverable
19


Test Suites

1.

Authentication

2.

Change Password

3.

View Account Information

4.

Update
Account Information



Team 1: Final Deliverable
20


Test Cases

Test Case ID 1: Authentication


Description

This test case authenticates the user for logging into the system.


Testing Environment/Configuration

The user with the username “John” and with the password “password” should be stored in the
Database.


Initialization

1. The application has been started.


Actions

Steps

Expected Results

Pass/

Fail

Actual

Results

1.

The user selects the “Login”
menu option

from the “File”
menu.


A login dialog is shown on the screen.



2.

Type in “John” in the
username text field.


“John” is displayed in the username
text field.



3.

Type in “password” in the
password text field.


“••••••••” is displayed in the
password text
field.



4.

Select the button to submit
the username and password
to login to the system.


A dialog is displayed explaining that
the login was successful.



5.

Dismiss the success dialog.

The success dialog is removed from
the screen.




Finalization

None

Tester Comments

_____________________________________________________________________________________
_____________________________________________________________________________________
______________________________________________________________________
_______________




Team 1: Final Deliverable
21


Test Case ID 1.1.1: Invalid Login with Invalid Username


Description

This test case verifies that the system can differentiate the invalid username and valid password as an
unsuccessful login.



Testing Environment/Configuration

The user with the username “Bob” and with the password “invalid” should not be stored in the
Database. The user with the username “John” and with the password “password” should be stored in
the Database.


Initialization

1. The application has been start
ed.


Actions

Steps

Expected Results

Pass/

Fail

Actual

Results

1.

The user selects the “Login”
menu option from the “File”
menu.


A login dialog is shown on the screen.



2.

Type in “Bob” in the username
text field.


“Bob” is displayed in the username text
field.



3.

Type in “password” in the
password text field.


“•••••••
” is displayed in the password
text field.



4.

Select the button to submit the
username and password to login
to the system.


An error dialog is displayed explaining
that the username and/or
password are
incorrect and the login was
unsuccessful.



5.

Dismiss the error dialog.

The error dialog is removed from the
screen.



Finalization

None


Tester Comments

_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________




Team 1: Final Deliverable
22


Test Case ID 1.1.2: Invalid Login with Invalid Password


Description

This test case verifies that the system can differentiate the valid username and invalid password as an
unsuccessful login.



Testing Environment/Configuration

The user with the userna
me “Bob” and with the password “invalid” should not be stored in the
Database. The user with the username “John” and with the password “password” should be stored in
the Database.


Initialization

1. The application has been started.


Actions

Steps

Expec
ted Results

Pass/

Fail

Actual

Results

1.

The user selects the “Login” menu option
from the “File” menu.


A login dialog is shown
on the screen.



2.

Type in “John” in the username text field.



“John” is displayed in
the username text field.



3.

Type in
“invalid” in the password text field.



“•••••••” is displayed
in the password text
field.



4.

Select the button to submit the username
and password to login to the system.





An error dialog is
displayed explaining that
the username and/or
password are
incorrect
and the login was
unsuccessful.



5.

Dismiss the error dialog.

The error dialog is
removed from the
screen.





Finalization

None


Tester Comments

_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________




Team 1: Final Deliverable
23


Test Case ID 1.1.3: Invalid Login with Invalid Username and Invalid
Password


Description

This test case verifies that the system can differentiate the invalid username and invalid password as an
unsuccessful login.



Testing Environment/Configuration

The user with the username “Bob” and with the password “invalid” should not be stored in the
Database. The user with the username “John” and with the password “password” should be stored in
the Database.


Initialization

1. The application has been
started.


Actions

Steps

Expected Results

Pass/

Fail

Actual

Results

1.

The user selects the “Login” menu option
from the “File” menu.


A login dialog is shown
on the screen.



2.

Type in “Bob” in the username text field.



“Bob” is displayed in the
username
text field.



3.

Type in “invalid” in the password text field.



“•••••••” is displayed
in the password text
field.



4.

Select the button to submit the username
and password to login to the system.





An error dialog is
displayed explaining that
the username

and/or
password are incorrect
and the login was
unsuccessful.



5.

Dismiss the error dialog.

The error dialog is
removed from the
screen.




Finalization

None


Tester Comments

_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________




Team 1: Final Deliverable
24


Test Case ID 1.2: First Login


Description

This test case verifies that when a user with an account in the system logs in initially, the user will have
the option to update their account information.


Testing Environment/Configuration

The user with the
username “NewUser” and with the password “password1” should be stored in the
Database, but has never logged into the system.


Initialization

1.

The application has been started.


Actions

Steps

Expected Results

Pass/

Fail

Actual

Results

1.

The user selects the
“Login” menu option
from the “File” menu.


A login dialog is shown on the
screen.



2.

Type in “NewUser” in the username text
field.


“NewUser” is displayed in the
username text field.



3.

Type in “password1” in the password text
field.


“•••••••••” is
displayed in
the password text field.



4.

Select the button to submit the username
and password to login to the system.

A success dialog is displayed
explaining that the login was
successful and the user has
the option to view/update his
or her account info
rmation.

See Test Case 4.




Finalization

None


Tester Comments

_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________

Team 1: Final Deliverable
25


Test Case ID 2: Change Password


Description

This test case verifies that a user can change his/her password.


Testing Environment/Configuration

The user with the username “ChangePassword” and with the password “ChangePasswordpw” should be
stored in the D
atabase.


Initialization

1.

The application has been started.

2.

The user must be logged into the system.


Actions

Steps

Expected Results

Pass/

Fail

Actual

Results

1.

The user selects the “Change Password”
menu option from the “File” menu.


A change password dialog is
shown on the screen.



2.

Type in “ChangePasswordpw” in the
“Old Password” text field.



“••••••••••••••••” is
displayed in the “Old
Password” text field.



3.

Type in “newpassword” in the “New
Password” text field.



“•••••••••••”

is displayed
in the “New Password” text
field.



4.

Retype in “newpassword” in the
“Confirm New Password” text field.



“•••••••••••” is displayed
in the “Confirm New
Password” text field.



5.

Select the button to submit the new
password.



A success dialog
is displayed
explaining that the password
has been updated.



6.

The user selects the “Log Out” menu
option from the “File” menu.


The user is logged out of the
system.



7.

The user selects the “Login” menu
option from the “File” menu.


A login dialog is
shown on the
screen.



8.

Type in “ChangePassword” in the
username text field.



“ChangePassword” is
displayed in the username
text field.



9.

Type in “ChangePasswordpw” in the
“••••••••••••••••” is


Team 1: Final Deliverable
26


password text field.



displayed in the password
text field.

10.

Select the button to submit the
username and password to login to the
system.





An error dialog is displayed
explaining that the username
and/or password are
incorrect and the login was
unsuccessful.



11.

Dismiss the error dialog.



The error dialog is

removed
from the screen.



12.

The user selects the “Login” menu
option from the “File” menu.


䄠汯g楮⁤楡汯g⁩猠獨V睮won⁴U攠
獣牥Vn.



13.

Type in “ChangePassword” in the
u獥牮慭V⁴e硴⁦ 敬e.



“ChangePassword” is
T楳i污祥T⁩渠瑨 ⁵獥牮am攠
瑥硴⁦楥汤.



14.

Type
in “newpassword” in the password
瑥硴⁦楥汤.


“•••••••••••” is displayed
楮⁴U攠p慳a睯牤 瑥x琠晩敬f.



15.

Select the button to submit the
username and password to login to the
system.



A dialog is displayed
explaining that the login was
successful.



16.

Dismiss the success dialog.

The success dialog is
removed from the screen.




Finalization

None


Tester Comments

_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________

Team 1: Final Deliverable
27


Test Case ID
3
.0.1: Member Viewing Account Information


Description

This test case verifies that Member user type can view his/her account information.



Testing Environment/Configuration

The user with the username “Member” and with the password “Memberpw
” should be stored in the
Database. This account should have the following account information stored with it:


First name: mfirst


Middle name: mmiddle

Last name: mlast

Phone number: 000
-
000
-
0000

Street: mstreet

City: mcity

State: mstate

Zip code: 00000

Email: memail@email.com


Initialization

1.

The application has been started.

2.

The user must be logged into the system with username “Member” and password “Memberpw”.


Actions

Steps

Expected Results

Pass/

Fail

Actual

Results

1.

The user selects the “View Account
Information” menu option from the
“Account Information” menu.




A screen appears displaying a
field to enter the user ID of
the user whose account
information
is
to be
displayed.



2.

Type “Member” into the User ID text field.

“Member” is displayed in the
User ID text field.




3.

Select the “View Account Information”
button.

A screen appears displaying
the current user’s (Member)
account information that is
specified under Testing
Environment/

Configuration in this Test
Case.




Finalization

None



Team 1: Final Deliverable
28


Tester
Comments

_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________
________

Team 1: Final Deliverable
29


Test Case ID
3
.0.2: Employer Viewing Account Information


Description

This test case verifies that Employer user type can view his/her account information as well as any valid
Member’s account information.



Testing Environment/Configuration

The
user with the username “Member” and with the password “Memberpw” should be stored in the
Database. This account should have the following account information stored with it:


First name: mfirst


Middle name: mmiddle

Last name: mlast

Phone number: 000
-
000
-
0000

Street: mstreet

City: mcity

State: mstate

Zip code: 00000

Email: memail@email.com

The user with the username “Employer” and with the password “Employerpw” should be stored in the
Database. This account should have the following account information st
ored with it:


First name: efirst


Middle name: emiddle

Last name: elast

Phone number: 111
-
111
-
1111

Street: estreet

City: ecity

State: estate

Zip code: 11111

Email:
eemail@email.com


Initialization

1.

The application
has been started.

2.

The user must be logged into the system with username “Employer” and password “Employerpw”.


Actions

Steps

Expected Results

Pass/

Fail

Actual

Results

1.

The user selects the “View Account
Information” menu option from the
“Account
Information” menu.




A screen appears displaying a
field to enter the user ID of
the user whose account
information

is

to be
displayed.



2.

Type “Employer” into the User ID text
field.

“Employer” is displayed in the
User ID text field.




Team 1: Final Deliverable
30


3.

Select the “View

Account Information”
bu瑴on.

䄠獣牥An⁡灰敡牳⁤楳e污y楮g
the current user’s (Employer)
慣捯un琠楮form慴aon⁴U慴⁩
獰散楦V敤⁵eT敲e呥獴楮V
䕮癩牯nm敮eI

䍯n晩fu牡瑩rn⁩ ⁴U楳⁔敳e
䍡獥C




4.

The user selects the “View Account
Information” menu option from t
Ue
“Account Information” menu.




䄠獣牥An⁡灰敡牳⁤楳e污y楮g⁡
晩敬f⁴o⁥nW敲e瑨W⁵獥爠 M of
瑨攠畳敲W睨w獥Va捣cunW
楮景牭a瑩Wn
i猠
Wo⁢攠
T楳i污祥T.



5.

Type “Member” into the User ID text field.

“Member” is displayed in the
啳敲⁉M⁴e硴⁦ 敬e.




6.

Select
the “View Account Information”
bu瑴on.

䄠獣牥An⁡灰敡牳⁤楳e污y楮g
the selected user’s (Member)
慣捯un琠楮form慴aon⁴U慴⁩
獰散楦V敤⁵eT敲e呥獴楮V
䕮癩牯nm敮eI

䍯n晩fu牡瑩rn⁩ ⁴U楳⁔敳e
䍡獥C




Finalization

None


Tester Comments

_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________

Team 1: Final Deliverable
31


Test Case ID
3
.0.3: Provider Viewing Account Information


Description

This test case verifies that Provider user type can view his/her account information as well as any valid
Member’s account information.



Testing Environment/Configuration

The user with

the username “Member” and with the password “Memberpw” should be stored in the
Database. This account should have the following account information stored with it:


First name: mfirst


Middle name: mmiddle

Last name: mlast

Phone number: 000
-
000
-
0000

Street: mstreet

City: mcity

State: mstate

Zip code: 00000

Email: memail@email.com

The user with the username “Provider” and with the password “Providerpw” should be stored in the
Database. This account should have the following account information stored
with it:


First name: pfirst


Middle name: pmiddle

Last name: plast

Phone number: 222
-
222
-
2222

Street: pstreet

City: pcity

State: pstate

Zip code: 22222

Email:
pemail@email.com


Initialization

1.

The application has
been started.

2.

The user must be logged into the system with username “Provider” and password “Providerpw”.


Actions

Steps

Expected Results

Pass/

Fail

Actual

Results

1.

The user selects the “View Account
Information” menu option from the
“Account Information”
menu.




A screen appears displaying a
field to enter the user ID of
the user whose account
information
is
to be
displayed.



2.

Type “Provider” into the User ID text field.

“Provider” is displayed in the
User ID text field.




Team 1: Final Deliverable
3
2


3.

Select the “View Account
Information”
bu瑴on.

䄠獣牥An⁡灰敡牳⁤楳e污y楮g
the current user’s (Provider)
慣捯un琠楮form慴aon⁴U慴⁩
獰散楦V敤⁵eT敲e呥獴楮V
䕮癩牯nm敮eI

䍯n晩fu牡瑩rn⁩ ⁴U楳⁔敳e
䍡獥C




4.

The user selects the “View Account
Information” menu option from the
“Accou
nt Information” menu.




䄠獣牥An⁡灰敡牳⁤楳e污y楮g⁡
晩敬f⁴o⁥nW敲e瑨W⁵獥爠 M of
瑨攠畳敲W睨w獥Va捣cunW
楮景牭a瑩Wn
i猠
Wo⁢攠
T楳i污祥T.



5.

Type “Member” into the User ID text field.

“Member” is displayed in the
啳敲⁉M⁴e硴⁦ 敬e.




6.

Select the “View
Account Information”
bu瑴on.

䄠獣牥An⁡灰敡牳⁤楳e污y楮g
the selected user’s (Member)
慣捯un琠楮form慴aon⁴U慴⁩
獰散楦V敤⁵eT敲e呥獴楮V
䕮癩牯nm敮eI

䍯n晩fu牡瑩rn⁩ ⁴U楳⁔敳e
䍡獥C




Finalization

None


Tester Comments

_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________

Team 1: Final Deliverable
33


Test Case ID
3
.0.4: Operator Viewing Account Information


Description

This test case verifies that Operator user type can view his/her account information as well as any valid
Member’s, Employer’s, and Provider’s account information.



Testing Environment
/Configuration

The user with the username “Member” and with the password “Memberpw” should be stored in the
Database. This account should have the following account information stored with it:


First name: mfirst


Middle name: mmiddle

Last name: mlast

Phone number: 000
-
000
-
0000

Street: mstreet

City: mcity

State: mstate

Zip code: 00000

Email: memail@email.com

The user with the username “Employer” and with the password “Employerpw” should be stored in the
Database. This account should have the following
account information stored with it:


First name: efirst


Middle name: emiddle

Last name: elast

Phone number: 111
-
111
-
1111

Street: estreet

City: ecity

State: estate

Zip code: 11111

Email:
eemail@email.com

The user wit
h the username “Provider” and with the password “Providerpw” should be stored in the
Database. This account should have the following account information stored with it:


First name: pfirst


Middle name: pmiddle

Last name: plast

Phone number: 222
-
222
-
2222

Street: pstreet

City: pcity

State: pstate

Zip code: 22222

Email:
pemail@email.com

The user with the username “Operator” and with the password “Operatorpw” should be stored in the
Database. This account should have
the following account information stored with it:


First name: ofirst


Middle name: omiddle

Last name: olast

Phone number: 333
-
333
-
3333

Team 1: Final Deliverable
34


Street: ostreet

City: ocity

State: ostate

Zip code: 33333

Email: oemail@email.com


Initialization

1.

The application has
been started.

2.

The user must be logged into the system with username “Operator” and password “Operatorpw”.


Actions

Steps

Expected Results

Pass/

Fail

Actual

Results

1.

The user selects the “View Account
Information” menu option from the
“Account Information”
menu.




A screen appears displaying a
field to enter the user ID of
the user whose account
information
is
to be
displayed.



2.

Type “Operator” into the User ID text field.

“Operator” is displayed in the
User ID text field.




3.

Select the “View Account
Information”
button.

A screen appears displaying
the current user’s (Operator)
account information that is
specified under Testing
Environment/

Configuration in this Test
Case.




4.

The user selects the “View Account
Information” menu option from the
“Accou
nt Information” menu.




A screen appears displaying a
field to enter the user ID of
the user whose account
information
is
to be
displayed.



5.

Type “Member” into the User ID text field.

“Member” is displayed in the
User ID text field.




6.

Select the “View
Account Information”
button.

A screen appears displaying
the selected user’s (Member)
account information that is
specified under Testing
Environment/

Configuration in this Test
Case.



7.

The user selects the “View Account
Information” menu option from the
A screen appears displaying a
field to enter the user ID of


Team 1: Final Deliverable
35


“Account Information” menu.




瑨攠畳敲W睨w獥Va捣cunW
楮景牭a瑩Wn
i猠
Wo⁢攠
T楳i污祥T.



Type “Employer” into the User ID text
晩敬f.

“Employer” is displayed in the
啳敲⁉M⁴e硴⁦ 敬e.




9.

Select
the “View Account Information”
bu瑴on.

䄠獣牥An⁡灰敡牳⁤楳e污y楮g
the selected user’s
⡅(ploy敲⤠慣捯unW
楮景牭a瑩Wn 瑨慴⁩W⁳灥捩晩 T
unT敲e呥獴楮V 䕮癩Nonm敮eI

䍯n晩fu牡瑩rn⁩ ⁴U楳⁔敳e
䍡獥C



10.

The user selects the “View Account
Information” menu opti
on 晲fm⁴Ue
“Account Information” menu.




䄠獣牥An⁡灰敡牳⁤楳e污y楮g⁡
晩敬f⁴o⁥nW敲e瑨W⁵獥爠 M of
瑨攠畳敲W睨w獥Va捣cunW
楮景牭a瑩Wn
i猠
Wo⁢攠
T楳i污祥T.



11.

Type “Provider” into the User ID text field.

“Provider” is displayed in the
啳敲⁉M⁴e硴⁦ 敬e.




12.

Select the “View Account Information”
bu瑴on.

䄠獣牥An⁡灰敡牳⁤楳e污y楮g
the selected user’s (Provider)
慣捯un琠楮form慴aon⁴U慴⁩
獰散楦V敤⁵eT敲e呥獴楮V
䕮癩牯nm敮eI

䍯n晩fu牡瑩rn⁩ ⁴U楳⁔敳e
䍡獥C




Finalization

None


Tester Comments

_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________

Team 1: Final Deliverable
36


Test Case ID
3
.1.1: Member Privilege Not Granted


Description

This test case verifies that Member user type cannot view the account information of employers,
providers, operators, or other members.



Testing Environment/Configuration

The user with the use
rname “Member” and with the password “Memberpw” should be stored in the
Database. This account should have the following account information stored with it:


First name: mfirst


Middle name: mmiddle

Last name: mlast

Phone number: 000
-
000
-
0000

Street: mstr
eet

City: mcity

State: mstate

Zip code: 00000

Email:
memail@email.com

The user with the username “Member1” and with the password “Member1pw” should be stored in the
Database. This account should have the following
account information stored with it:


First name: mfirst


Middle name: mmiddle

Last name: mlast

Phone number: 000
-
000
-
0000

Street: mstreet

City: mcity

State: mstate

Zip code: 00000

Email: memail@email.com

The user with the username “Employer” and with the p
assword “Employerpw” should be stored in the
Database. This account should have the following account information stored with it:


First name: efirst


Middle name: emiddle

Last name: elast

Phone number: 111
-
111
-
1111

Street: estreet

City: ecity

State:
estate

Zip code: 11111

Email:
eemail@email.com

The user with the username “Provider” and with the password “Providerpw” should be stored in the
Database. This account should have the following account information st
ored with it:


First name: pfirst


Middle name: pmiddle

Last name: plast

Phone number: 222
-
222
-
2222

Team 1: Final Deliverable
37


Street: pstreet

City: pcity

State: pstate

Zip code: 22222

Email:
pemail@email.com

The user with the username “Operat
or” and with the password “Operatorpw” should be stored in the
Database. This account should have the following account information stored with it:


First name: ofirst


Middle name: omiddle

Last name: olast

Phone number: 333
-
333
-
3333

Street: ostreet

City:

ocity

State: ostate

Zip code: 33333

Email: oemail@email.com


Initialization

1.

The application has been started.

2.

The user must be logged into the system with username “Member” and password “Memberpw”.


Actions

Steps

Expected Results

Pass/

Fail

Actual

Results

1.

The user selects the “View Account
Information” menu option from the
“Account Information” menu.




A screen appears displaying a
field to enter the user ID of
the user whose account
information
is
to be
displayed.



2.

Type “Operator” into the User ID
text field.

“Operator” is displayed in the
User ID text field.




3.

Select the “View Account Information”
button.

An error dialog is displayed
explaining that the current
user (Member) does not have
the privilege to view this
user’s account information.





4.

The user selects the “View Account
Information” menu option from the
“Account Information” menu.




A screen appears displaying a
field to enter the user ID of
the user whose account
information
is
to be
displayed.



5.

Type “Provider” into the User ID
text field.

“Provider” is displayed in the
User ID text field.




Team 1: Final Deliverable
38


6.

Select the “View Account Information”
bu瑴on.

䅮⁥牲rr⁤楡汯g⁩ ⁤楳 污祥T
數p污ln楮g⁴U慴a瑨攠捵c牥r琠
u獥爠(Memb敲⤠To敳 W⁨ v攠
瑨攠灲Wv楬敧攠eo v楥眠瑨W猠
user’s account information.





7.

The user selects the “View Account
Information” menu option from the
“Account Information” menu.




䄠獣牥An⁡灰敡牳⁤楳e污y楮g⁡
晩敬f⁴o⁥nW敲e瑨W⁵獥爠 M of
瑨攠畳敲W睨w獥Va捣cunW
楮景牭a瑩Wn
i猠
Wo⁢攠
T楳i污祥T.



8.

Type “Employer” into the User ID
瑥硴
晩敬f.

“Employer” is displayed in the
啳敲⁉M⁴e硴⁦ 敬e.




9.

Select the “View Account Information”
bu瑴on.

䅮⁥牲rr⁤楡汯g⁩ ⁤楳 污祥T
數p污ln楮g⁴U慴a瑨攠捵c牥r琠
u獥爠(Memb敲⤠To敳 W⁨ v攠
瑨攠灲Wv楬敧攠eo v楥眠瑨W猠
user’s account information.





10.

The user selects the “View Account
Information” menu option from the
“Account Information” menu.




䄠獣牥An⁡灰敡牳⁤楳e污y楮g⁡
晩敬f⁴o⁥nW敲e瑨W⁵獥爠 M of
瑨攠畳敲W睨w獥Va捣cunW
楮景牭a瑩Wn
i猠
Wo⁢攠
T楳i污祥T.



11.

Type “Member1” into the User ID text

晩敬f.

“Member1” is displayed in
瑨攠啳敲e䥄⁴e硴⁦ 敬e.




12.

Select the “View Account Information”
bu瑴on.

䅮⁥牲rr⁤楡汯g⁩ ⁤楳 污祥T
數p污ln楮g⁴U慴a瑨攠捵c牥r琠
u獥爠(Memb敲⤠To敳 W⁨ v攠
瑨攠灲Wv楬敧攠eo v楥眠瑨W猠
user’s account information.






Finalization

None


Tester Comments

_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________

Team 1: Final Deliverable
39


Test Case ID
3
.1.2: Employer Privilege Not Granted


Description

This test case verifies that Employer user type cannot view the account information of operators,
providers, or other employers.



Testing Environment/Configuration

The user with the username

“Member” and with the password “Memberpw” should be stored in the
Database. This account should have the following account information stored with it:


First name: mfirst


Middle name: mmiddle

Last name: mlast

Phone number: 000
-
000
-
0000

Street: mstreet

C
ity: mcity

State: mstate

Zip code: 00000

Email: memail@email.com

The user with the username “Employer” and with the password “Employerpw” should be stored in the
Database. This account should have the following account information stored with it:


First n
ame: efirst


Middle name: emiddle

Last name: elast

Phone number: 111
-
111
-
1111

Street: estreet

City: ecity

State: estate

Zip code: 11111

Email:
eemail@email.com

The user with the username “Employer1” and with the pass
word “Employer1pw” should be stored in
the Database. This account should have the following account information stored with it:


First name: efirst


Middle name: emiddle

Last name: elast

Phone number: 111
-
111
-
1111

Street: estreet

City: ecity

State: estate

Zip code: 11111

Email:
eemail@email.com

The user with the username “Provider” and with the password “Providerpw” should be stored in the
Database. This account should have the following account information stored w
ith it:


First name: pfirst


Middle name: pmiddle

Last name: plast

Phone number: 222
-
222
-
2222

Team 1: Final Deliverable
40


Street: pstreet

City: pcity

State: pstate

Zip code: 22222

Email:
pemail@email.com

The user with the username “Operator” an
d with the password “Operatorpw” should be stored in the
Database. This account should have the following account information stored with it:


First name: ofirst


Middle name: omiddle

Last name: olast

Phone number: 333
-
333
-
3333

Street: ostreet

City: ocity

State: ostate

Zip code: 33333

Email: oemail@email.com


Initialization

1.

The application has been started.

2.

The user must be logged into the system with username “Employer” and password “Employerpw”.


Actions

Steps

Expected Results

Pass/

Fail

Actual

Results

1.

The user selects the “View Account
Information” menu option from the
“Account Information” menu.




A screen appears displaying a
field to enter the user ID of
the user whose account
information
is
to be
displayed.



2.

Type “Operator” into the User ID text
field.

“Operator” is displayed in the
User ID text field.




3.

Select the “View Account Information”
button.

An error dialog is displayed
explaini
ng that the current
user (Employer
) does not
have the privilege to view this
user’s account information.





4.

T
he user selects the “View Account
Information” menu option from the
“Account Information” menu.




A screen appears displaying a
field to enter the user ID of
the user whose account
information
is
to be
displayed.



5.

Type “Provider” into the User ID text
field.

“Provider” is displayed in the
User ID text field.




Team 1: Final Deliverable
41


6.

Select the “View Account Information”
bu瑴on.

䅮⁥牲rr⁤楡汯g⁩ ⁤楳 污祥T
數p污lni
ng⁴U慴a瑨攠捵c牥r琠
u獥爠⡅mp汯y敲
)⁤ 敳eno琠
U慶攠瑨攠p物癩r敧攠瑯 v楥眠WU楳i
user’s account information.





7.

The user selects the “View Account
Information” menu option from the
“Account Information” menu.




䄠獣牥An⁡灰敡牳⁤楳e污y楮g⁡
晩敬f⁴o⁥nW敲e瑨W⁵獥爠 M of
瑨攠畳敲W睨w獥Va捣cunW
楮景牭a瑩Wn
i猠
Wo⁢攠
T楳i污祥T.



8.

Type “Employer1” into the User ID text

晩敬f.

“Employer1” is displayed in
瑨攠啳敲e䥄⁴e硴⁦ 敬e.




9.

Select the “View Account Information”
bu瑴on.

䅮⁥牲rr⁤楡汯g⁩ ⁤楳 污祥T
數p污lni
ng⁴U慴a瑨攠捵c牥r琠
u獥爠⡅mp汯y敲
)⁤ 敳eno琠
U慶攠瑨攠p物癩r敧攠瑯 v楥眠WU楳i
user’s account information.






Finalization

None


Tester Comments

_____________________________________________________________________________________
_____________________________________________________________________________________