CaseComplete Tutorial

treescattleSoftware and s/w Development

Nov 2, 2013 (3 years and 9 months ago)

192 views

Serlio Software
Development Corporation

-

1

-

CaseComplete 2009R2
Tutorial



CaseComplete
®

2009R2

Tutorial






Serlio Software
Development Corporation

-

2

-

CaseComplete 2009R2
Tutorial

Contents

CaseComplete
®

________________________________
________________________________
__

1

Introduction
________________________________
________________________________
______________

3

Installation

________________________________
________________________________
______________

3

Create a new project

________________________________
________________________________
_______

3

Explore the modeling process

________________________________
________________________________

4

Create a vision document
________________________________
________________________________
____

5

Open the
Introduction to Use Cases

PowerPoint presentation

________________________________
________

6

Define actors

________________________________
________________________________
_____________

7

Add custom fields

________________________________
________________________________
_________

8

Define actor goals

________________________________
________________________________
________

10

Convert goals to use cases

________________________________
________________________________
__

10

Change views

________________________________
________________________________
___________

11

Add new use cases and actors

________________________________
_______________________________

14

Add notes, open is
sues and related documents

________________________________
___________________

15

Change use case priority

________________________________
________________________________
___

15

Add a glossary entry

________________________________
________________________________
______

16

Get an immediate definit ion of a glossary term

________________________________
__________________

17

Add flow of events to use case
________________________________
_______________________________

18

Use quick insert tool tips

________________________________
________________________________
___

20

Add extensions to a use case step
________________________________
_____________________________

20

Add anytime extensions to a use case step

________________________________
______________________

21

Add a use case reference

________________________________
________________________________
___

22

Manipulate steps in flow of events

________________________________
____________________________

22

Refactor a use case

________________________________
________________________________
_______

24

Add additional details and access dynamic help

________________________________
__________________

27

Create packages
________________________________
________________________________
__________

28

Filter by pa
ckage

________________________________
________________________________
_________

29

Add Requirements

________________________________
________________________________
________

29

Add Requirement References

________________________________
_______________________________

30

Creat
e Child Requirements

________________________________
________________________________
_

32

Search

________________________________
________________________________
_________________

34

Generate reports

________________________________
________________________________
_________

35

Working in

Teams

________________________________
__________________
Error! Bookmark not defined.

Track changes

________________________________
________________________________
___________

36

Clone project elements

________________________________
________________________________
____

36

Generate Te
st Plans

________________________________
________________________________
_______

36

Create hyperlinks to use cases in other applications

_________________________
Error! Bookmark not defined.

Export data to UML tools

________________________________
____________
Error! Bookmark not defined.

Create domain object cross reference tables

_______________________________
Error! Bookmark not defined.

Incorporate Diagrams into your Project

________________________________
__
Error!
Bookmark not defined.


Serlio Software
Development Corporation

-

3

-

CaseComplete 2009R2
Tutorial

Introduction

This
tutorial

walk
s

you
through many of the features
found in Case
Complete
®
,
and
at the same
time

shows

you the various steps of the use case modeling process
.
Throughout the
tutorial
,
examples from a fictional doctor’s office appointment system
are

used.
You are encouraged to
tr
y each step as you read along, however many screen shots are used so you can get a good
feel for the capabilities from this document alone.

For your convenience, this tutorial is
available from both the Evaluation Guide

and from the Help menu of Case
Comple
te.

Installation

Double click on the installation file (e.g. CaseCompleteSetup
200
9
R2
.msi), or select “Run” when
downloadin
g from the Internet. CaseComplete
2009
R2
requires Microsoft’s .NET framework
version 2.0
, with Service Pack 1
. If you don’t have it i
nstalled on your system, you’ll get a
message to that effect.
You can
download and
install the .NET framework
version 2.0
in one of
two ways:



Via Windows update:
http://www.update.microsoft.com



By installing

the redistributable package
:
.NET version 2.0

Create a new
project

On the opening screen you will be presented with a choice of o
pening an existing
project

or
creating a new one
.
Click on “Create New
Project
”, or select “New…” from the File menu.




Serlio Software
Development Corporation

-

4

-

CaseComplete 2009R2
Tutorial

In the resulting dialog, type the name that you want to give to the
project

and indicate what
folder it should be stored in.
If you ha
ve an existing glossary from a previous project that is
applicable to this project
as well, you can browse to it.
In this case,
use the default glossary
name.
Leave the starting ID and prefix at their default values as well.



Explore the modeling process

After creating the new
project
, the start page displays the steps involved in
the use case
modeling process.
By moving
your mouse over each step, Case
Complete presents information
about that step and provides navigation links to more information as well a
s links that take you
to the

corresponding location in Case
Complete.


Serlio Software
Development Corporation

-

5

-

CaseComplete 2009R2
Tutorial


Create a vision document

Before starting on a new project, it’s a good idea to c
reate a short vision document.
Click on
the second step in the modeling pro
cess, “Create vision document
”.
This brings up Microsoft
Word with a vision document template that contains guidelines and tips for wh
at to include in
the document.
From this point forward, the document will be associated with this use case
project

and will be opened for each person t
hat clicks on the link.


Serlio Software
Development Corporation

-

6

-

CaseComplete 2009R2
Tutorial


Open the
Introduction to Use Cases

PowerPoint presentation

If you have team members that aren’t familiar with use cases, use the PowerPoint presentation
to bring them up to speed
.
From the Modeling Process start page, click on th
e “Teach
Stakeholders” link to start the PowerPoint presentation:


Serlio Software
Development Corporation

-

7

-

CaseComplete 2009R2
Tutorial


Define actors

When creating a new use case
project
, you typically start out by identifying and describi
ng the
“actors” in the system.
Click on the “Define Actors” link from the modeling p
rocessing page and
enter the following actors:



Serlio Software
Development Corporation

-

8

-

CaseComplete 2009R2
Tutorial



Things to note:



The Description in the bottom left pane is showing the description for the
AppointmentSystem top level package, which is selected in the
project

browser.



The Properties Window in the botto
m right pane is showing the properties for the
Appoin
tmentSystem top level package.
The Properties Window is used to view and
change prope
rties of selected item(s).
Y
ou can turn it off or on from the View menu.



“systu
m” is squiggle
-
underlined, indicati
ng a

potential spelling error.
If the spelling is
correct, the word can be

added to the custom dictionary by right clicking on it.



Case
Complete automatically underlines
“d
oct
or” indicating it is an actor.
In addition it is
a hyperlink which can be used to navi
gate to t
he details page for the actor.
It also shows
the description of the actor when you hover the mouse over it:



Add custom fields

You can add custom fields to use cases
,
actors,
requirements

and packages to hold information
beyond that provided by

predefined fields.
For example, you could create a “Computer Access”
field to indicate what type of

computer access an actor has.
From the Too
ls Menu, select
Custom Fields to bring up the following screen:


Serlio Software
Development Corporation

-

9

-

CaseComplete 2009R2
Tutorial



Click on the New Field button and change
the
name to “Computer Access”.
If desired, you can
add a Default Value or Va
lue Choices to your new field.
A Default Value will be assigned to your
custom field when a new
item of the appropriate type

is created

(in this case, a new actor)
.
If
Value Choices ar
e added, they will be presented and can be
selected

in

the Properties Window
of the selected use case.


You also have the ability to customize default values
and value choices
for
the
predefined fields
such as “Use
Case Status” or “Assigned To”.
For exampl
e, you may want to enter the names of
your project team members as value choi
ces for the Assigned to field.
From the Tools m
enu,
select Predefined Fields.
A dialog similar to the one shown above is presented
.


Once you have created a set of custom fields o
r
have
customized your predefined fields, you
can export them
to a file
for
import into
a different use case project or to share with other team
members.


Serlio Software
Development Corporation

-

10

-

CaseComplete 2009R2
Tutorial

Define actor goals

As you create actors, start adding their goals
.
What do they expect to get out of
the system?
For this example, click on the Receptionist, then click on the Goals tab along the bottom and
add to the bulleted list:





Convert goals to use cases

Once you have goals defined, you

can start creating use cases.
Since many of your goals wil
l
transl
ate directly to use cases, Case
Complete allows you to create use ca
ses from goals to save
typing.
From the Tools menu select “Create Use Cases from Actor Goals…
”:


Serlio Software
Development Corporation

-

11

-

CaseComplete 2009R2
Tutorial



In this screen shot we see goals for all the actors, not just the receptionist go
al
s created in the
previous step.
Note that for the selected goal we are specifying a different name for the
generated use case so that it more accurately refle
cts the system responsibility.
Click on the
Create button


note that the ID’s of the generated
use cases are added to the goal name so
you can easily see which goals have already generated use cases should you later add more
goals.

Change views

After generating the use cases, switch to the Use Cases tab to see them:


Serlio Software
Development Corporation

-

12

-

CaseComplete 2009R2
Tutorial



The view shown above is calle
d the description view and is good when you want to quickly add
new use cases during brainstorming or get an overview of

the use cases defined so far.
If you
want to see more details for each use case, switch to the details view via the View m
enu or the
co
rresponding button

on the toolbar:


Serlio Software
Development Corporation

-

13

-

CaseComplete 2009R2
Tutorial



Note the primary act
or field is already filled in.
This is because the use cases we
re generated
from actor goals.


By default, use cases are sorted alphabetically, but you can also sort on any column by
clicking
on th
e column header.
Clicking on it agai
n will reverse the sort order.
Holding the Shift key
while clicking on a different column header will allow you to set a secondary sort order (e.g.
sort first by
release, then by priority).

You may sort up to 3 columns.


To add or remove columns, choose “Select Columns…” from the View menu or from the right
mou
se menu on the column headers.
Choose the fields and their

display

order according to
what ma
ke
s most sense for your project.
You may also set column sort order her
e as well (does
the same thing as shift
-
click described above):


Serlio Software
Development Corporation

-

14

-

CaseComplete 2009R2
Tutorial


Add new use cases and actors

At any time
, you can add a new use case,
actor

or requirement
.
Th
ere are many ways to do
this.
For example, you can add a new use case by:

1.

Clicking the New Use
Case button on the toolbar:

2.

Selecting “Add Use Case” from the right mouse menu in the details list

3.

Selecting “Add Use Case” from the right mouse menu on a package in the
project

browser (packages discussed below)

4.

Clicking below the last use case in the d
escription view (description view is described
above in the “Change views” section).

5.

Hitting Enter when the cursor is positioned at the end of the use case name or
description in the description view

6.

Selecting “New Use Case” on the Edit menu


Similar rules

apply for actors

and requirements
.

Serlio Software
Development Corporation

-

15

-

CaseComplete 2009R2
Tutorial

Add
notes, open issues and related documents

Select the desired tab along the bottom of the window to add or edit the description, notes,
related documents, and open issues for the currently selected use case
, actor, pac
kage or
requirement
.
Notes can be anything from reviewer comments to reminders
.
For example, select
the “View daily schedule” use case in any view or in the
project

browser and add the following
note:




When writing use cases, you often will have questio
ns that need to be researched or
can’t
immediately be answered.
Add the
se to the Open Issues section.
For example:




If you have external documentatio
n for any given use case, actor, requirement,
or package,
you can add it to
the related documents sectio
n.
To add a new related document, you can
either drag and drop the file

from Windows Explorer

into the related documents pane, or you
can browse to it by selecting “Add related documen
t…” from the right mouse menu.
You can
also enter a URL in the same mann
er:




If you add a standard image file, such as a .jpg, or a document that supports embedding, such
as a Visio picture

or PowerPoint slide
, these
pictures
can automatically be displa
yed in
generated Word reports.
Control this behavior via the options but
ton found on the Generate
Word Report screen.

Change use case priority

Prioritizing use cases is helpful both for determining which use cases should be written first,
and once written, which use case
s should be implemented first. Case
Complete makes it easy

to
change the priority of use cases
.
In the details view, select one or more use cases and click the
appropriate priority button on the toolbar,
, or the ‘+’ and ‘
-
’ keys to increase or
decrea
se the priority, respectively.
In addition, you can change the

priority for all the selected
use
cases in the Properties window.
Recall you can sort on any column in the detail view by
clicking on the column header, so it is easy to sort use cases by priority.

Serlio Software
Development Corporation

-

16

-

CaseComplete 2009R2
Tutorial

Add a glossary entry

As you encounter terms that are ambi
guous or not widely known you sh
ould add them to the
glossary.
You should also add “domain objects” to the glossary, i.e. the real world entities that
the system is responsible
for, e.g. the patient history.

This will become important later on when
you wan
t to do domain object modeling using UML or generate a domain object analysis
report
(both described below).
You can add

glossary entries in two ways.
Via the glossary tab:




Or you can add a glossary entry for the current word or highlighted phrase whil
e editing any
text via the right mouse menu:


Serlio Software
Development Corporation

-

17

-

CaseComplete 2009R2
Tutorial



The following dialog is then displayed:



Get an immediate definition of a glossary term

Glossary entries are
automatically displayed

using a customizable color, and just as for actors,
you can pop up the d
efinition for a term by hovering your mouse over it:


Serlio Software
Development Corporation

-

18

-

CaseComplete 2009R2
Tutorial


Add flow of events to use case

The “meat” of a use case is its flow of events
.
Here you describe the
main success scenario

that
an act
or takes to achieve some goal.
To edit the flow of events open the

use case details form
by double clicking on a use case in the details list or
project

browser, or via the “Open details…”
right mouse menu:


Serlio Software
Development Corporation

-

19

-

CaseComplete 2009R2
Tutorial



A few things to note in this screen shot:

1.

You can use numbered steps or prose to document the flow of events.

2.

T
he text can be increased using the “A” button when
using a conference room projector.

3.

The flow of events section

and description

can be expanded to use the entire window.

4.

You can change the size of the window and the fields will resize accordingly.

It shou
ld also be noted that you
can

have multiple use case windows open simultaneously
allowing you to easily switch between 2 or more us
e cases.
When you switch
to another use
case, or back to the main
application
, your changes will automatically be applied (al
though it is
still up to you to save your changes to disk).


The steps for the Schedule Appointment use case might look something like this:


Serlio Software
Development Corporation

-

20

-

CaseComplete 2009R2
Tutorial


Use quick insert tool tips

Notice that “Receptionist” is used ma
ny times in the list of steps. Case
Complete prov
ides “quick
insert tool tip
s” to help speed up data entry. When Case
Complete recognizes that you are
typing the start of an actor or definition, it presents you with the option of automatically
inserting the rest of the word when you press enter:



Add ex
tensions to a use case step

As implied by the name, the “main success scenario” describes the steps that are taken most of
the time and when not
hing goes wrong.
In order to enter an alternate flow of events or an
exceptio
n, add an extension to a step.
Add
extensions via the right mouse menu or via Ctrl+E
.
For example, let’s add an extension to the 2
nd

step:


Serlio Software
Development Corporation

-

21

-

CaseComplete 2009R2
Tutorial



Extensions start with a verifiable condition and are followed by a list of steps that are taken
when the condition is true
.
For example:



Add anyt
ime extensions to a use case step

If an extension can happen at any time, an asterisk (*) is us
ed instead of the step number.
Case
Complete allows you to add Anytime Extension
s

via the right mouse menu or via Alt
+
E
.
For example, if you know the network can
go down at anytime, you could add this as an
Anytime Extension:



Serlio Software
Development Corporation

-

22

-

CaseComplete 2009R2
Tutorial

Add a use case reference

Recall that we already have a use case
that describes

add
ing

a new patient to the system.
Case
Complete allows you to create

a reference to that use case.
While typi
ng the text for the
extension, select “Insert Use Case Reference…” from the rig
ht mouse menu, or type Ctrl+U.
This will bring up the lis
t of use cases defined so far.
Type in the start of the desired use case
name, or scroll to it with the arrow keys and p
ress enter (in this case it’s the first one):




Case
Complete will insert the name of the use case and its ID which acts as a hype
rlink.
You are
free to fix up the name of the use case so it is grammatically correct:




Just as with actor and glossary hy
perlinks, you can navigate to the use case by clicking on the
ID and you can see the description of the use case by hovering your mouse over it.

You can
insert a use case refere
nce into any text field of Case
Complete, e.g. preconditions.

Manipulate steps i
n flow of events

You will undoubtedly need to manipulate the order and indentation of the step
s in your flow of
events. Case
Compl
ete makes this extremely easy.
For example, let’s say you later decide that
the receptionist should first enter the scheduling
portion of the system befor
e looking up the
patient name.
Sim
ply move the step up using Ctrl+
UpArrow or via the right mouse menu:


Serlio Software
Development Corporation

-

23

-

CaseComplete 2009R2
Tutorial



After moving step 5 up to step 2,
you end up with the following.
Notice that the extension for
the patient look up step (f
ormerly step 2) was automatically renumbered t
o 3.a and

continue
at step 3


was automatically renumbered to
refer to
step 4:


Serlio Software
Development Corporation

-

24

-

CaseComplete 2009R2
Tutorial



You may also wish to break a step into multiple sub steps or ad
d sub steps to any given step.
Indent steps by using the tab ke
y to move a s
tep underneath the step above.
To break a step
into two, simply hit enter at the appropriate place in the te
xt.
For example:



Refactor a use case

As you add more and more use cases to your
project

you may find sets of steps that are

common t
o multiple use cases.
Or you may find that the flow of events is getti
ng too long in
some use cases.
In either case you may find it useful to refactor your use case, that is, break
out a subset of steps into a new use case.


As a simple example, let’s say
that steps
2
-
4 above, where
the receptionist enter
s

the patient
s
cheduling portion of the system
occur in multiple use cases
.
In addition, you feel that the use
case is becoming more difficult to read because it is cluttered with too much detail

(a
lthough
in
this example there are only 3 steps, you could imagine situations where there are many
more
steps involved
,

each
with many extensions
)
.


Begin by selecting the steps you wish to move out, right clicking on any of the selected steps,
and selecting Move s
teps to new Use Case:


Serlio Software
Development Corporation

-

25

-

CaseComplete 2009R2
Tutorial



Notice

that extension 3.a is bolded.
This indicates that it
belongs to a selected step

and will be
moved to the new use case along with the selected steps.


You will be presented with the following dialog where you can give the ne
w use case a name
and brief description, and indicate which package it should be created in:




After selecting Create, a reference to the new use case will automatically be created in the
original use case
in place of the steps that were just moved
, in t
his case, step 2.
Notice also
that extension

3.a is no longer in this use case because it has been moved to the new use case:

Serlio Software
Development Corporation

-

26

-

CaseComplete 2009R2
Tutorial




As before, you are free to fix up the grammar

of the use case reference

to match your flow of
events, e.g.

Receptionist

looks

up
patient

(
UC
-
7
)”
.


Serlio Software
Development Corporation

-

27

-

CaseComplete 2009R2
Tutorial

Add additional details and access dynamic help

Many additional details are available to be filled in for a use case, all of which are explained in
the dynamic help window that automatically updates depending

on which field you are edi
ting.
Open the help window by clicking the blue question mark in the upper left:



Serlio Software
Development Corporation

-

28

-

CaseComplete 2009R2
Tutorial

Create packages

Instead of maintaining one long list of use cases, it’s a good idea to organize them into
categories
, known as packages
.
Create a new package by selecting “
Add Package” from the
right mouse menu on an existing package in the
project

browser:




How you select your categories is up to you, but one common way is to organize use

cases by
their primary actor.
After you create a new package, you can drag and drop

existing

use cases
and actors into it.
Here we have created a new package for each actor and moved the use
cases and actors into the appropriate package:




Serlio Software
Development Corporation

-

29

-

CaseComplete 2009R2
Tutorial

Filter by package

If you are primarily working with use cases and actors in one given package, yo
u might want to
show only the items in that package
.
Do this by selecting the desired package on the toolbar:




In addition to filtering out use cases you aren’t currently interested in, it also has the advantage
that any new use cases or actors that you

create will automatically get added to that package.

Add
Requirement
s

Depending on your organization’s standards and processes, you may want to add requir
ements
to your use case
project
.
Although use cases
can stand on their own as

a detailed description
of
behavioral requirements, some organizations start with use cases as a way to
identify

their
formal requirement
s.
Others start with requirements and
make sure they ar
e all described in a
use case.
Most likely, it will be a c
ombination of the two methods.

You may also want to add

n
on
-
functional (or non
-
behavioral) requirements

since these requirements are not

describe
d
in

the use case.
These requirements

deal
with things like reliability, performance a
nd security.

Other supported requirem
ent types include
business rules
, testing, constraint
s
, and change
request
s
.

As with all predefined fields, you are free to customize your own choice lists.


Requirements are
owned

by packages (or in the case of child requirements, other requirements

which is covered in a l
ater section
).
Create a new requirement
the same way you create new
actors and use cases, e.g. from the toolbar,
in

the requirements tab, o
r in the
project

browser.
For

example
,
switch to the description view,
select the
Requirements tab,
and enter the
fol
lowing requirement:


Serlio Software
Development Corporation

-

30

-

CaseComplete 2009R2
Tutorial



Note that just as for use cases and actors, you can add a description, notes, related documents
and open issues to a requirement. In addition, requirements have various properties such as
priority, type and status which you can assi
gn using the properties window or by opening the
requirement details page. You may also create your own custom fields for requirements.

Add Requirement References

Requirements are
referenced

by use cases
. Since a given requirement may be applicable t
o
many

use cases
, many use cases may reference the same requirement. For example, you may
have a performance requirement indicating that a screen must be rendered in less than 2
seconds. That requirement may be applicable to any use case which brings up a screen
.


O
pen the use case form for the “V
iew patient history” use case.
On the Details tab click the
“Select” button to choose
existing
requirements that ar
e applicable to this use case.
(Note you
may also create new requirements from

here).
In this case, there

is only one requirement
defined so far:


Serlio Software
Development Corporation

-

31

-

CaseComplete 2009R2
Tutorial



As with all lists in
CaseComplete
, you can sort by clicking on the column header, or sort on
multiple columns by holding Shift while clicking.



Another technique to
assign requirements to use cases
is
by draggi
ng and dropping
requirements on to
p of a use case or vice
-
versa.
For example, try dragging the requirement
from the
project

browser
and dropping it
on top of the
“Add new patient” use case in the main
list view
.



By associ
ating requirement
s

with
use case
s
, developers can make sure that the requirement is
met when designing
and implementing the use case.
In addition, testers can find all the use
cases that
a

requirement applies to and make sure that each use case meets the requirem
ent
during functional test
ing.
To that end, a

powerful capability that Case
Complete provides is the
Requirements
Cross Reference

Word report showing which
requirements apply to a use case
and which
use cases
reference

a given requirement.

For example, here is an excerpt from that
r
eport
(
after adding
a printing

requirement
and assigning it to applicable use cases
)
:


Use Cases

(By ID)


ID

Name

Referenced Requirements

UC
-
3

Add new patient



REQ
-
1 Only doctors and nurses
can access patient history.

UC
-
5

View daily schedule



REQ
-
2 Must b
e able to print.

UC
-
6

View patient history



REQ
-
1 Only doctors and nurses
can access patient history.



REQ
-
2 Must be able to print.


Use cases that do not reference any requirements:



UC
-
1 Cancel appointment



UC
-
2 Schedule appointment



UC
-
4 Generate patient c
all list



Requirements

Serlio Software
Development Corporation

-

32

-

CaseComplete 2009R2
Tutorial

(By ID)


Requirement

Name

Referenced by

REQ
-
1

Only doctors and nurses can
access patient history.



UC
-
3 Add new patient



UC
-
6 View patient history

REQ
-
2

Must be able to print.



UC
-
5 View daily schedule



UC
-
6 View patient history


Req
uirements that are not referenced by any use cases:


This report is
useful when a requirement changes
,

because you can easily see which use cases
may need to be reworked (or retested if you are changing the requirement after the u
se case
has been implement
ed).
For example, if
the first

requirement were changed to “Patient history
is accessible via password only”, the
referencing

use case
s

would likely have to change.


CaseComplete also
enables

you to create requirement to requirement references
. This allows

a
dependency to be created between requirements, e.g. when one requirement can’t be fulfilled
unless the other requirement is implemented. To create requirement to requirement references,
open the requirement form for

an existing requirement
and select th
e Details tab. Then click
the select button and
cho
o
se

the

existing requirements that are
referenced by

the

requirement.


Dragging and dropping a requirement onto another requirement will
not

create a requirement
to requirement reference relationship; inst
ead, it will create a parent
-
child requirement
relationship. Child requirements
are

covered in the next section.

Create

Child Requirements

You can
create
a
c
hild requirement

by adding a new child requirement to an existing
requirement. For example,
if you
right mouse click on the

Only doctors and nu
rses can access
patient history


Requirement
in the main list
or
project

browser
and select “Add

Child
Requirement”
,
a new child requirement will be created.


Serlio Software
Development Corporation

-

33

-

CaseComplete 2009R2
Tutorial




Shown below are
three

child requirements for REQ
-
1

displayed in the Requirements tab
:




T
he three child requirements for REQ
-
1 displayed in the
Project

Browser:




Serlio Software
Development Corporation

-

34

-

CaseComplete 2009R2
Tutorial

Another way to create a child requirement is by re
-
parenting an existing requirement. For
example, if you drag and drop an existing requi
rement onto another requirement in the main
list or
project

browser, it will move and assign it
to
a new parent. Or you can use the Owner
drop down list box on the requirement form to set the requirement’s Owner to a
nother

requirement, making it a child re
quirement.
Drag and drop and the Owner drop down list box
can also be used to move child requirements out of their current parent requirement and into
packages or other requirements, changing them into top level requirements or children of other
requiremen
ts.

Search

Case
Complete provides search capability, best described by this screen shot:




The entire
project

is searched and results are presented in a tab along the bott
om. As with all
lists in Case
Complete, y
ou can click on any column header to sort o
n that column
, or
Shift+Click to sort on multiple columns
.
Double click on an item to navigate to it (or select
“Open Details…” from the right mouse menu)
.
Choose “Select in list” from the right mouse
menu to highlight
the given item in the main list:


Serlio Software
Development Corporation

-

35

-

CaseComplete 2009R2
Tutorial


G
enerate reports

With Case
C
omplete,
you
can

easily
generate a variety of reports
in HTML,
Word
,

and
Excel
formats. Since Case
Complete tracks each element in your
project

individually, you can generate
very specific

and concise

reports
.
For example, you may
want to generate a report that shows
all open issues fo
r your daily “hot list” meeting. The following is an example of the Open

Issues
HTML report;
this report is also available in Word format.




Or you may want to generate a report showing only the brie
f descriptions of the use cases as a
handy overview of the system
.
Of course, you
can

generate complete report
s

showing all
details for all elements in your
project

in various sorting orders
.
R
eports are easily customizable
to suit your organization’s need
s
; f
or
instructions

on customizing
Word and Excel

reports, select

Custom Reports…” from the H
elp menu.


Serlio Software
Development Corporation

-

36

-

CaseComplete 2009R2
Tutorial

Track changes

CaseComplete

allows you to track changes, additions and deletions to your
project
.
Change will
only be recorded and shown
after

you have
performed a save.
To see how track changes
behaves:

1.

Save your
project

to set a “baseline”, i.e. the version to compare with
.

2.

Select “Track Changes” from the Tools menu
.

3.

Make changes to the
project
, for example, add a use case, delete a different use case,
modify a description, add a note or open issue
.

4.

Save your
project

so the changes are recorded
.

5.

View the changes by selecting “Show Changes…” from the Tools menu
.

6.

Changes are cumulative.
When you want to set a new baseline, select “Accept
Changes…” from the

Tools menu
.

Clone
project

elements

Sometimes it is useful to create a new use case based on an existing one
.
Or you may even
want to duplicate the contents of an entire package
.
To create duplicates, selec
t one or more
actors, use cases, requirements
or p
ackages in any of the lists or
project

browser and select
“Duplicate Selected Items…” from the right mouse menu, or click the toolbar button:



Duplicate item(s) will be created with “copy of” added as a prefix.

Generate Test Plans

Use Cases serve as an e
xcellent
foundatio
n for your functional testing.
Not only do they
describe how the system should behave, they describe the steps needed to elicit the behavior
,

and the

exceptions that can occur and alternative paths that the user can take

during those
step
s
. Case
Complete takes this one step further by allowing you to enter testing procedure,
suggested inputs and expected result
s for each step and extension.
You enter this information
directly in the flow of events section of the use case, keeping this infor
mation all in one place.


When you

are ready to
enter testing information, click on the “Show Testing Procedure” check
box in the use case’s flow of even
ts to reveal the testing grid.
Here is a portion of
our “Schedule
Appointment”

use case
with the testin
g grid turned on and examples what you might enter for
the testing columns
:


Serlio Software
Development Corporation

-

37

-

CaseComplete 2009R2
Tutorial



In addition to this information,
on the supplemental tab of the use case
you can also
add:



Testing

setup
, the steps that must be performed in order to get to the point where th
e
use case can be tested,
e.g. start main application, log in as Guest
.



Testing configurations,
e.g. operating systems, browser ve
rsions, foreign languages, etc.


Likewise, requirements have a testing procedure field

that describes how the requirement can
be verified
.
For example, for our first requirement (only doctors and nurses can access patient
history), your testing procedure might be “Log in as receptionist, verify patient history
menu
item

is grayed out”.


Once you have entered testing information t
o an appropriate level of detail, you can generat
e
test plans via Word reports. Case
Complete comes with 2 standard test plan

templates: one a
testing check
list which shows each use case and the extensions for each use case, the other a
complete report of t
he testing grid shown above.

As with all reports, you can easily customize
these reports.