Prepared By
Axton Grams
Version 1.00
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
Table of Contents
1
1.1
1.2
2
2.1
2.2
2.3
3
3.1
3.2
3.2.1
3.2.1.1
3.2.1.2
3.2.1.3
4
4.1
4.2
4.3
4.3.1
4.3.1.1
5
5.1
5.1.1
5.1.2
5.2
5.3
5.4
5.5
5.5.1
5.5.1.1
5.5.1.2
5.5.1.3
5.5.1.4
6
6.1
6.2
6.3
Versi on Control..................................................................................................................... 3
Purpose .................................................................................................................................3
Revision History......................................................................................................................3
Introduction .......................................................................................................................... 4
Purpose .................................................................................................................................4
Document Scope ....................................................................................................................4
Audience................................................................................................................................4
Development and Production Architecture ........................................................................... 5
Development and Production Configuration ..............................................................................5
Migrating Changes ..................................................................................................................5
Methods of Migration ..............................................................................................................5
Difference Reports..................................................................................................................5
Form Definition Migration ........................................................................................................5
Workflow Migration .................................................................................................................5
Functional Requirement Specifications................................................................................ 6
Inputs.....................................................................................................................................6
Outputs ..................................................................................................................................6
Sample Functional Requirement Statement ..............................................................................6
Phase 1 (version 5.x implementation).......................................................................................6
Shared Workflow Functional Requirements ..............................................................................6
Functional Requirement Test Scripts ................................................................................... 7
Test Script Requirements ........................................................................................................7
Licenses ................................................................................................................................7
Data.......................................................................................................................................7
Test Script Specifications ........................................................................................................7
Inputs.....................................................................................................................................8
Outputs ..................................................................................................................................8
Sample Test Script ............................................................................................................... 10
The system shall enable users to query all open Help Desk or Change requests by module. ..... 10
Questions and Requirements ................................................................................................ 10
Description........................................................................................................................... 10
Test Script 1-35-A: Query Change Requests .......................................................................... 11
Test Script 1-35-B: Query Help Desk Cases ........................................................................... 12
Functional Requirement Technical Documentation and Packaging Methods..................... 14
Specifications ....................................................................................................................... 14
Inputs................................................................................................................................... 14
Outputs ................................................................................................................................ 14
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
1 Version Control
1.1 Purpose
This section is made available so that different revisions of this document may be differentiated against one
another. Each time this document is made publicly available, an attempt to increase the version, and recap
the changes, date changed, and person making the changes will be recorded. Due to the lack of a sufficient
document control system, the revision data may contain inaccuracies.
Description of Changes
Document Name
Date
Changed by
1.00
Original Draft
UNT-DEV_METH -1 00.doc
06-08-2003
Axton Grams
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
2 Introduction
This document is intended to define the methods used to facilitate the development, documentation, and
packaging of additional requirements to the Remedy RSM applications. This document is not intended to
define the actual requirements, but instead serves as an outline of the steps and methods used to follow
custom requirements from concept to production.
2.1 Purpose
The intended purpose of this document is to outline a method to achieve the following requirements as they
pertain to application development:
Several documents produced a direct result of the methodologies outlined in this document. These
documents include:
Doc #: UNT-FRS-xxx
Doc #: UNT-TEST-xxx
Doc #: UNT-FRS_TECH-xxx
This document will outline the definition and composition of each of the above mentioned documents.
2.3 Audience
The paper is intended for UNTs Remedy Administrators, UNTs Remedy Developers, and all other interested
members of UNTs Remedy user community. The processes and methodologies outlined in this document
should be considered proprietary and confidential information to the University of North Texas.
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
4.1 Inputs
Current production 4.x Help Desk applications functionalities implemented in the past. These requirements
were typically not documented in any formal documentation. The requirements must be extrapolated from the
application based on code changes from the vanilla application.
4.2 Outputs
Description
ALL-01-0001
ALL-01-0002
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
Original Application
Behavior
New Feature
New Feature
Server License
Fixed or Floating User Licenses
HelpDesk-Fixed or HelpDesk-Floating Licenses
SLA Fixed Licenses
5.1.2 Data
The Remedy server that is used for testing must have the following data loaded. The data set does not need
to mirror production or be a complete data set, but should include sufficient data for testing.
Categorizations
Locations
Groups
Support Groups
Special Permission Groups
People
Assets from CEATS
User Ids and Passwords for access
When a person designates the requester using the UNT ID field, ensure all the additional fields
are populated.
When a person designates the requester using the Login Name field, ensure all the additional
fields are populated.
When a person designates the requester using the Search People dialog, ensure all the
additional fields are populated.
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
4.
5.
When a person creates a people profile for the requester, ensure all the additional fields are
populated.
When a person designates the requester using the Name field, ensure all the additional fields are
populated.
Several critical elements must be present when developing test scripts. These include:
<Phase>-<APP>-<TestScriptID>
99-AAAAA-9999
<Phase>-<APP>-<TestScriptID>-<StepID>
99-AAAA-9999-999
5.3 Inputs
5.4 Outputs
FRS #
Test ID #
Role
Role
Description
Administrator
This Role includes the application administrator. Test scripts belonging in this role will usually
pertain to application configuration tasks, and not to support specific tasks. Users performing
these tasks must belong to the APP-Administrator and/or Administrator group(s), and are
generally not accessible by general support staff.
This Role includes tests to be performed by people that will be designated as managers who
have cleared the FERPA data accessibility requirements. These tasks will usually include
approvals, service level agreements, and various other managerial tasks. Users performing
these tasks must generally belong to the APP- Management group and APP-FERPA group.
This Role includes tests to be performed by people that will be designated as managers who
have not cleared the FERPA data accessibility requirements. These tasks will usually include
approvals, service level agreements, and various other managerial tasks. Users performing
these tasks must generally belong to the APP- Management group.
The Role includes tests to be performed by people that use the application on a daily basis to
perform work related tasks, manage problem/change requests, and create new requests who
have cleared the FERPA data accessibility requirements. Users performing these tasks must
generally be in the APP-Support group and APP-FERPA group.
The Role includes tests to be performed by people that use the application on a daily basis to
perform work related tasks, manage problem/change requests, and create new requests who
have not cleared the FERPA data accessibility requirements. Users performing these tasks must
generally be in the APP-Support group.
This Role includes tests to be performed by any user, whether via the web and/or the native
client.
Public
Description
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
Action
Expected Result
Response Time
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
ALL-23
<< The system shall enable users to query all open Help Desk or Change requests by module. >>
Tester Signoff
Tester:
Signature/Initials:
5.5.1.1.2
Title:
Date:
Prerequisites
5.5.1.1.3
PC Information
REMEDY Version:
WEB or Client: (circle one)
Client Version:
Browser Type:
Browser Version:
Java Make:
Java Version:
5.5.1.2 Description
This can be accomplished by opening the main form for the module desired in search mode, then performing a Query by Example (QBE) or Advanced
query from that particular form
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
10
Test/Step ID #
Role(s)
Description
ALL-23
ALL-23-A
ALL-23-A -001
Support
<< The system shall enable users to query all open Help Desk or Change requests by module. >>
Login to Remedy User
1. Login to the Remedy
Remedy User is opened
with a valid account.
User tool.
with no forms open.
Open the Support
1. Click File-> Open
The Remedy Support
Console.
2. Click on the Find tab
Console is displayed in
3. Type Remedy Support in the Remedy User tool
the Search what
keywords? Text field
4. Double-click the row
where the name is
Remedy Support
Open the search
1. Click the Search for
The Main Change form is
Change Request form
Request button
opened in Search mode
(CHG:Change).
2. When prompted with
the Search dialog box,
click the Change
Request button
a. If you are not
prompted with a dialog
to select Change
Request or Help Desk
Case, then you need
to set up your
Personal Preferences.
This can be
accomplished
following the steps
provided below
i. Click on the Utilities> Personal
Preferences menu
ii. When the Setup
Personal
Preferences dialog is
presented, verify that
ALL-23-A -002
ALL-23-A -003
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
11
Action
Expected Result
Actual Result
Response
Time
ALL-23-A -004
Action
Expected Result
Test/Step ID #
Role(s)
Description
ALL-23
ALL-23-B
ALL-23-B -001
Support
<< The system shall enable users to query all open Help Desk or Change requests by module. >>
Login to Remedy User
1. Login to the Remedy
Remedy User is opened
with a valid account.
User tool.
with no forms open.
Open the Support
1. Click File-> Open
The Remedy Support
Console.
2. Click on the Find tab
Console is displayed in
3. Type Remedy Support
the Remedy User tool
in the Search what
keywords? Text field
4. Double-click the row
where the name is
Remedy Support
Open the search Help
1. Click the Search for
The Help Desk form is
Desk Cases form
Request button
opened in Search mode
(HPD:HelpDesk).
2. When prompted with
the Search dialog box,
click the Help Desk
button
ALL-23-B -002
ALL-23-B -003
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
12
Actual Result
Response
Time
ALL-23-B -004
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
13
6.1 Specifications
Ensure that these packages can be migrated into the vanilla RSM application without intefering with
oob workflow.
Ensure that this package can interoperate with other packages without introducing inteference.
Ensure that this package contains all the contents required to operate independantly of all other
packages.
All of the above requirements should be met with the expectation that each may be loaded to the
vanilla application without being dependant on any other packages, and interoperate with all other
packages. Each of these packages may then be easily retrofitted in the future for subsequent
releases of the RSM application. Also, each and packages shall be versioned according to the RSM
application to which they apply.
6.2 Inputs
6.3 Outputs
Packing List
DEF file of the following:
o Forms, which only include the fields that were created and/or modified for this particular
functional requirement.
o Active Links which pertain to this package. All new active links shall be prefixed with a plus
sign (+), and all modified active links shall be prefixed with an asterisk (*).
o Filters which pertain to this package. All new filters shall be prefixed with a plus sign (+), and
all modified filters shall be prefixed with an asterisk (*).
o Menus which pertain to this package. All new menus shall be prefixed with a plus sign (+),
and all modified menus shall be prefixed with an asterisk (*).
o Escalations which pertain to this package. All new escalations shall be prefixed with a plus
sign (+), and all modified escalations shall be prefixed with an asterisk (*).
o Active Link Guides which pertain to this package. All new active link guides shall be
prefixed with a plus sign (+), and all modified active link guides shall be prefixed with an
asterisk (*).
o Filter Guides which pertain to this package. All new filter guides shall be prefixed with a plus
sign (+), and all modified filter guides shall be prefixed with an asterisk (*).
o Applications which pertain to this package. All new application shall be prefixed with a plus
sign (+), and all modified applications shall be prefixed with an asterisk (*).
o Web Services which pertain to this package. All new web services shall be prefixed with a
plus sign (+), and all modified web services shall be prefixed with an asterisk (*).
ARX Data files for the following:
o All new permission groups which are required for this particular functional requirement
o All configuration records which are required for this particular functional requirement
For example:
Menu Value entries
SHRCFG:ConfigTmpIndex entries
SQL script to disable modified workflow objects.
o When workflow is modified, its name shall be captured and included in the packing list. A
comprehensive list of the modified workflow shall be used to generate a SQL script which will
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
14
disable the original workflow, so that when the modified workflow is migrated to a server, the
two will not conflict.
Development Methodologies
For UNT Internal Use Only
Document Number: UNT-DEV_METH-001
15