Sample Team 2

8/3/2019 Sample Team 2

1/22

Software Requirements Specificationfor

APMS

Version 1.0

Prepared by:

Mountain High Consulting

TEAM 2Cathleen Brown

Lull MengeshaRobert Ward

Gary Westcott

November 24, 2007


2/22

SoftwareRequirements Specification for APMS

Page ii

Table of Contents

Revision History......................................................................................... iii1. Introduction ........................................................................................... 1

1.1 Purpose........................................................................................... 11.2 Intended Audience and Reading Suggestions ........................................ 11.3 Project Scope ................................................................................... 11.4 References....................................................................................... 12. Overall Description.................................................................................22.1 Product Perspective........................................................................... 22.2 Product Features .............................................................................. 22.3 User Classes and Characteristics ......................................................... 22.4 Operating Environment...................................................................... 3

2.4.1 APMS Small Business Edition O.E. .................................................... 32.4.2 APMS Enterprise Edition O.E............................................................ 4

2.5 Design and Implementation Constraints............................................... 42.6 User Documentation.......................................................................... 5

2.6.1 User Manuals ................................................................................ 52.6.2 Tutorial ........................................................................................ 52.6.3 On-Line Help ................................................................................. 5

2.7

Assumptions and Dependencies .......................................................... 5

3. System Features.....................................................................................63.1 Functional Requirements.................................................................... 6

3.1.1 Functional Requirements................................................................. 63.2 Use Cases...................................................................................... 11

4. Other Nonfunctional Requirements ...................................................... 164.1 Performance Requirements .............................................................. 164.2 Portability Requirements .................................................................. 164.3 Reliability Requirements .................................................................. 174.4 Usability Requirements .................................................................... 174.5 Security Requirements .................................................................... 184.6 Scalability Requirements.................................................................. 18

5. Other Requirements ............................................................................. 19Appendix A: Glossary ................................................................................19Appendix B: Analysis Models..................................................................... 19Appendix C: Issues List.............................................................................19

TablesTable 1: Revision History .............................................................................. iiiTable 2. Intended audience of this document .................................................... 1Table 3: References ......................................................................................1Table 4: User Classes and Characteristics......................................................... 2Table 5: Constraints......................................................................................4Table 6: Functional Requirements ................................................................... 6Table 7: Use Cases ..................................................................................... 11Table 8: Performance Requirements .............................................................. 16Table 9: Portability Requirements.................................................................. 16Table 10: Reliability Requirements ................................................................ 17Table 11: Usability Requirements .................................................................. 17Table 12: Security Requirements .................................................................. 18Table 13: Scalability Requirements................................................................ 18

Figures

Figure 1: Product Features ............................................................................. 2


3/22


Page iii

Revision History

Table 1: Revision History

Name Date Reason For Changes Version

Original 11/24/2007 Original Release 1.0.0


4/22


Page 1

1.Introduction

1.1 Purpose

The purpose of this document is to further define requirements for the APMSsystem.

1.2 Intended Audience and Reading Suggestions

Table 2. Intended audience of this document

Group of the readers Reasons for reading

APMS CEO To be kept informed of the teams progress

APMS Management To give feedback about the requirements

APMS Sales and Marketing To ensure the requirements continue to be feasible

Mountain High Consulting To get feedback from others on the accuracy and completeness of the

requirements

APMS System Architects To ensure continued accuracy of the system design and commence

architectural design

APMS Developers/System

Analysts

To give feedback about the requirements and commence functional

design

1.3 Project Scope

Advanced Project Management Systems (APMS) is a 100 Million Dollar, privately-owned company, specialized in software tool development. APMS would like tobecome a major player in the market for Distributed Project Management (DPM)software tools.

Advanced Project Management Systems (APMS) specializes in softwaredevelopment. The company is proposing to become a major player in the market forDistributed Project Management (DPM) software tools. Their vision is to become thepremier provider of high-quality, distributed project management tools toorganizations worldwide. APMS will compete with all key players in the market bycoming up with better tools that support planning, tracking, collaborating, re-planning, closeout, reflection, and historical data update in a distributedenvironment.

This project encompasses APMS efforts to design and construct a world class DPMsoftware package including capability for both large and small projects.

1.4 References

Table 3: References

Name of the document Short description of the document contents

User Requirements of

11/10/2007

User Requirements Document, dated October 10, 2007 for the APMS

project

ConOps of 10/27/2007 Concept of Operations Document, dated October 27, 2007 for the APMS

project


5/22


Page 2

Recommendation of

10/13/2007

Recommendation for Design and Development of Distributed Project

Management Software for Advanced Project Management Systems

2.Overall Description

2.1 Product Perspective

This Distributed Project Management (DPM) software product is a new development,planned to meet the needs of companies managing projects on a global basis. It is aself-contained product but includes the facilities required to export and import datain recognized, standardized formats.

2.2 Product Features

Figure 1: Product Features

2.3 User Classes and CharacteristicsTable 4: User Classes and Characteristics

User Group Description

Number of

Users Priority

Large System

Planner/Schedulers Responsible for schedule developmentand maintenance.

10 +

Mainta in P roject Rep ortingAnalyze Resource

Requ i rementsAnalyze CPM NetworkMainta in Cost Data

Mainta in Resource

Requ i rementsMainta in Schedu le

Mainta in Resource

Table

Create, Mainta in ,Repor t CPM Schedu le

Create Project

Modi fy Project

De lete Project

Create ResourceTable

Enter Resource

Modi fy Resource

Delete Resource

Create Schedu le

Enter A ct iv i ty

Modi fy Act iv i ty

Delete Activity

Enter Constra in t

Modi fy Constra in t

De lete Constra in t

Enter Resource

Requ i rement onSchedu le Act iv i ty

Modi fy Resource


De lete Resource


Budget Data

Actua l Data

Forecast Data

Enter on Schedu le

Activity

De lete on Schedu leActivity

Modi fy on Schedu leActivity

Enter on Schedu le

Activity


Modi fy on Schedu leActivity

Enter on Schedu le

Activity


Modi fy on Schedu le

Activity

Per formCalcu lat ions

Diagnose Er rors

Su mmar i z eResources

Leve l Resources

Schedu le Repor ts

Tabu lar Repor ts

Graph icRepor ts

Resource Repor ts

Tabu lar Repor ts

Graph icRepor ts

Cost Repor ts

Tabu lar Repor ts

Graph icRepor ts


6/22


Page 3

User Group Description

Number of

Users Priority

Engineers Responsible for schedule status inputs. 50 +

Cost Analyst Responsible for input and maintenance ofcommitted and actual cost data, alongwith estimates to complete.

20 +

Quantity Surveyors Responsible for input and maintenance ofphysical complete data along withremaining work. Also provide estimatesfor changes.

20 +

Managers Responsible for overall management ofspecified portions of the project.

30 +

Project Manager Responsible for overall projectmanagement primarily read andreporting access for schedule data, inputand maintenance of budgetary data.

1 +

Small System

Planner/Schedulers Responsible for schedule developmentand maintenance. 1 +

Engineers Responsible for schedule status inputs. 10 +

Cost Analyst Responsible for input and maintenance ofcommitted and actual cost data, alongwith estimates to complete.

2 +

Quantity Surveyors Responsible for input and maintenance ofphysical complete data along withremaining work. Also provide estimatesfor changes.

5 +

Area Managers Responsible for overall management ofspecified portions of the project.

5 +

Project Manager Responsible for overall projectmanagement primarily read andreporting access for schedule data, inputand maintenance of budgetary data.

1 +

2.4 Operating Environment

2.4.1 APMS Small Business Edition O.E.

APMS Small Business Edition will be able to operate on the following platforms:

Microsoft 2003 Server, Enterprise Server and Small Business Server

Linux Server All Major Business Versions

The Server software will have fail over capability between two servers as well asreplication capability. The UI will be functional on all major browsers includingInternet Explorer 6.0 and higher, as well as Mozilla and Firefox.

APMS SBE will be able to functionally interact with Adobe Acrobat, Microsoft Officeproduct suite and the Star Office product suite.

APMS will have a UI and functionality designed for PDAs including the Blackberry,Compaq, and the Palm.


7/22


Page 4

2.4.2 APMS Enterprise Edition O.E.

APMS Enterprise Edition will be able to operate will be able operate across multiplegeographical sites to truly be a world wide system. The system will be able toutilize DNS and site replication, operate on a cluster server environment. Thesystem will be operational on all server systems listed for APMS Small BusinessEdition as well as the Sun and HP UNIX platforms.

APMS will be operational with both Oracle and Microsoft SQL Server version 2000 orhigher.

All browser, software interoperability and PDA functionality required of the APMSSmall Business Edition operating environment will apply to APM Enterprise Editionoperating environment.

2.5 Design and Implementation Constraints

Table 5: Constraints

ID Ver Constraint Source Rationale Priority Status

Traces to use

cases

C1 1 The user interface must

run on any well-known

browser including IE,

Opera and Mozilla.

Technical

Coordinator

N.N

People have

different browsers

we want to serve

them all.

Must Proposed All use cases

involving a

browser

interface,

login, update,

etc.

C2 1 Activity must function

on single server small

business system as well

as international system

which multiple servers

and locations utilizing

DNS and replication.

Scalability Changes in

scalability will not

impact product

performance for

any product version


where

performance is

a Quality

Attribute.

C3 1 System will have

operative functionality

on portable handheld

devices (PDAs,

Blackberrys, etc.)

Portability Users are

constantly on the

go, and may not

have access to PC

or laptop.


where

performance is

a Quality

Attribute.

C4 All A new or emerging

Technical requirement

New

development

Adapting to new

changes in technical

software

Must As

needed

As needed

C5 1 Confusion between

where business rule

ends and technical

requirements begin

Business rule Both systems are

closely ingrained

Must Proposed TBD

C6 4 As application systems

live longer and grow in

size and complexity,

there is an ever

increasing need for

methods and tools that

can support software

builders in constructing

maintainable, well-

structured and

consistent systems.

Software

applications

Software

constraints make

rules and

conventions

commonly agreed

to in a given

programming

environment

explicit and

automatically

checkable.

TBD TBD TBD


8/22


Page 5

2.6 User Documentation

2.6.1 User Manuals

A user manual and a reference manual will be provided. The user manual will beorganized by function within the application, allowing the user to read the detailsassociated with each portion of the application. The reference manual will be

organized like an encyclopedia, allowing the user to look up specific topics forexplanation.

2.6.2 Tutorial

A tutorial will be provided. The tutorial will step a user through the completeprocess of setting up a project, entering data, performing calculations, andoutputting reports using example data which will also be provided in a tutorial folderupon installation of the application.

2.6.3 On-Line Help

On-line, context sensitive help will be provided for all screens and menus. The help

will be accessible via the F1 function key and right mouse click.

2.7 Assumptions and Dependencies

Assumed factors and constraints that could affect the requirements stated in thisSRS:

1. Changes or upgrades to Operating Systems APMS runs on. Any changeswould require retesting of software.

2. Changes or upgrades to Software interoperable with APMS, i.e. browsers, MSOffice, Star Office, etc. Any changes would require retesting of software.

3. Changes or upgrades operating systems running on PDAs or other portabledevice hardware. Any changes would require retesting of software


9/22


Page 6

3.System Features

3.1 Functional Requirements

Table 6: Functional Requirements

3.1.1 Functional Requirements

Priority Legend

M Must Have S Should Have N Nice to Have

ID Ver Feature Requirement Source Rationale

Traces to use

casesPriority

P1 1 Maintain Project User shall be able tocreate project databasefile

ProjectManager (DA)

Must be able to create aproject database file tocontain all project data

1.1, 2.1M

P2 1 Maintain Project User shall be able tomodify project database

file

ProjectManager (DA)

Must be able to modify aproject database file

TBDM

P3 1 Maintain Project User shall be able todelete project databasefile

ProjectManager (DA)

Must be able to delete aproject database file

TBDM

RT1 1 Maintain ResourceTable

User shall be able tocreate an availableresource table

PlannerScheduler (HB)

Must be able to create atable containing allavailable resources

1.1, 2.1M


User shall be able to entera resource into theavailable resource table


Must be able to enteravailable resource records

1.1, 2.1M

RT3 1 Maintain Resource

Table

User shall be able to

modify an existingresource in the availableresource table

Planner

Scheduler (HB)

Must be able to modify or

update available resourcerecords

1.3

M


User shall be able todelete an existingresource from theavailable resource table


Must be able to deleteavailable resource records

1.3

M


10/22


Page 7



Traces to use

casesPriority

S1 1 Maintain Schedule User shall be able tocreate a scheduledatabase


Must be able to create aschedule database file tocontain a schedules data

1.1M

S2 1 Maintain Schedule User shall be able to enteran activity into theschedule database


Must be able to add newactivity to the scheduledatabase

1.1, 2.1M

S3 1 Maintain Schedule User shall be able tomodify an existing activityin the schedule database


Must be able to modify anexisting activity

1.3, 1.4M

S4 1 Maintain Schedule User shall be able todelete an existing activityfrom the scheduledatabase


Must be able to delete anexisting activity

1.3, 1.4

M

S5 1 Maintain Schedule User shall be able to entera constraint into theschedule database


Must be able to enter logicconstraints linkingactivities to model the

work flow in the schedule

1.2, 2.2

M

S6 1 Maintain Schedule User shall be able tomodify an existingconstraint in the scheduledatabase


Must be able to modify anexisting logic constraint

1.4

M

S7 1 Maintain Schedule User shall be able todelete an existingconstraint from theschedule database


Must be able to delete anexisting logic constraint

1.4

M

RR1 1 Maintain ResourceRequirements

User shall be able to add aresource requirement toan activity in the schedule

database


Must be able to add arequired resource to aschedule activity in order

to support resourcescheduling

TBD

M


User shall be able tomodify a resourcerequirement on an activityin the schedule database


Must be able to modify anexisting resource on anactivity

TBD

M


11/22


Page 8



Traces to use

casesPriority


User shall be able todelete a resourcerequirement from anactivity in the schedule

database


Must be able to delete anexisting resource from anactivity

TBD

M

C1 1 Maintain CostData

User shall be able to enterbudget cost data onschedule activity

Cost Analyst(AC)

Must be able to enterbudget cost data on eachschedule activity in orderto summarize projectbudgets

TBD

S


User shall be able tomodify budget cost dataon schedule activity

Cost Analyst(AC)

Must be able to modifyexisting budget cost dataon a schedule activity

TBDS


User shall be able todelete budget cost datafrom schedule activity

Cost Analyst(AC)

Must be able to deleteexisting budget cost datafrom a schedule activity

TBDS


User shall be able to enteractual cost data onschedule activity

Cost Analyst(AC)

Must be able to enteractual cost data on eachschedule activity in orderto summarize projectactual costs

TBD

M


User shall be able tomodify actual cost data onschedule activity

Cost Analyst(AC)

Must be able to modifyexisting actual cost dataon a schedule activity

TBDM


User shall be able todelete actual cost datafrom schedule activity

Cost Analyst(AC)

Must be able to deleteexisting actual cost datafrom a schedule activity

TBDM

C7 1 Maintain Cost

Data

User shall be able to enter

forecast cost data onschedule activity

Cost Analyst

(AC)

Must be able to enter

forecast to complete costdata on each scheduleactivity in order tosummarize projectforecasted costs

TBD

M


12/22


Page 9



Traces to use

casesPriority


User shall be able tomodify forecast cost dataon schedule activity

Cost Analyst(AC)

Must be able to modifyexisting forecast tocomplete data on aschedule activity

TBD

M


User shall be able todelete forecast cost datafrom schedule activity

Cost Analyst(AC)

Must be able to deleteexisting forecast tocomplete data from aschedule activity

TBD

M

AN1 1 Analyze Network User shall be able toperform CPM analysiscalculations on schedule


Must be able to performcritical path analysis onthe schedule in order tocalculate the dates

1.5

M

AN2 1 Analyze Network User shall be able todiagnose CPM analysiserrors from schedule


Must be able to diagnoseany error that occurduring schedule analysis

1.5S

AR1 1 Analyze ResourcesUser shall be able to

summarize requiredresource quantities bymonth and resource nameacross schedule

Planner

Scheduler (HB)

Must be able to

summarize the resourcerequirements by timeperiod and resource inorder to plan resourcesacross the project

TBD

M

AR2 1 Analyze ResourcesUser shall be able toperform resource levelingon schedule


Must be able to managethe resource requirementsto constrained resourceavailability levels

TBD

S

R1 1 Reporting User shall be able toproduce tabular schedulereports

Area Manager(JS)

Must be able to producetabular schedule reportsto represent andcommunicate the work

flow across the project

TBD

M

R2 1 Reporting User shall be able toproduce graphicalschedule reports

Area Manager(JS)

Must be able to producegraphical schedule reportsto represent andcommunicate the workflow across the project

TBD

M


13/22


Page 10



Traces to use

casesPriority

R3 1 Reporting User shall be able toproduce tabular resourcereports

Area Manager(JS)

Must be able to producetabular resource reportsto represent andcommunicate the resource

requirements across theproject

TBD

M

R4 1 Reporting User shall be able toproduce graphicalresource reports

Area Manager(JS)

Must be able to producegraphical schedule reportsto represent andcommunicate the resourcerequirements across theproject

TBD

M

R5 1 Reporting User shall be able toproduce tabular costreports

Area Manager(JS)

Must be able to producetabular cost reports torepresent andcommunicate the projectcosts

TBD

M

R6 1 Reporting User shall be able toproduce graphical costreports

Area Manager(JS)

Must be able to producegraphical cost reports torepresent andcommunicate the projectcosts

TBD

M


14/22


Page 11

3.2 Use Cases

Table 7: Use Cases

Use CaseUse Case 1.1 - Interactive Gantt Chart

Add Activity

DescriptionGoal: Activity, with associated resources, added to schedule.

Source: Interactive Web Gantt Chart

ActorsProject Scheduler

Planner

AssumptionsNew activity is required to describe a work task.

Planner/Scheduler has access to the application.

Steps

1. User accesses application opens applicable schedule file.2. User selects Gantt Chart from menu bar.3. Application displays interactive Gantt chart screen.4. User selects Add Activity from menu bar5. Application provides New Activity input form.6. User completes required fields.7. User clicks on Add Activity button.8. Application adds activity to database.9. Application presents Add Constraint? dialog to user.10. User clicks either Yes or No

If Yes - application presents Add Constraint form (see Use Case 1.2)If No application returns to interactive Gantt chart screen.

VariationsNone

Traces to Quality

Attributes:

Pe1, Po1, Po2, Se1 Se4, R1 R3, U1, U3


Add Constraint

DescriptionGoal: Constraint added to schedule.



Planner

AssumptionsNew constraint is required to describe relationship between two work tasks.


Steps

1. User accesses application, opens applicable schedule file.2. User selects Gantt Chart from menu bar.3. Application displays interactive Gantt chart screen.4. User selects Add Constraint from menu bar5. Application displays Gantt chart of activities and constraint dialog panel.6. User locates and clicks on first activity, then clicks on appropriate

identifier (predecessor or successor) in constraint dialog panel.7. User locates and clicks on second activity, then clicks on appropriate

identifier (predecessor or successor) in constraint dialog panel.8. User completes additional information in constraint dialog panel type of

constraint, delay.9. User clicks on Add Constraint button.10. Application adds constraint to database.

11. Application presents Add Additional Constraint? dialog to user.12. User clicks either Yes or No

If Yes - application presents Add Constraint form (see Use Case 1.2If No application returns to interactive Gantt chart screen.

VariationsNone

Traces to Quality

Attributes:

Pe1, Po1, Po2, Se1 Se4, R1 R3, U1, U3


15/22


Page 12


Modify Activity

DescriptionGoal: Activity, with associated resources, modified in schedule.



Planner

AssumptionsAn activity describing a work task requires modification.


Steps

1. User accesses application, opens applicable schedule file.2. User selects Gantt Chart from menu bar.3. Application displays interactive Gantt chart screen.4. User right clicks on activity to be selected5. Application provides dialog panel.6. User clicks on Modify Activity option.7. Application provides Activity Information panel.8. User completes/modifies required fields.9. User click on Save Activity button.10. Application saves modified activity to database.11. Application returns to interactive Gantt chart screen.

VariationsNone

Traces to Quality

Attributes:

Pe1, Po1, Po2, Se1 Se4, R1 R3, U1, U3


Modify Constraint

DescriptionGoal: Activity, with associated resources, modified in schedule.



Planner

AssumptionsA constraint linking activities requires modification.


Steps

1. User accesses application and opens applicable schedule file.2. User selects Gantt Chart from menu bar.3. Application displays interactive Gantt chart screen.

4. User right clicks on selected activity5. Application provides dialog panel.6. User clicks on Modify Constraint option.7. Application provides list of constraints linked to selected activity.8. User clicks on constraint requiring modification.9. Application provides Constraint Information panel.10. User completes/modifies required fields.11. User click on Save Constraint button.12. Application saves modified constraint to database.13. Application returns to interactive Gantt chart screen.

VariationsNone

Traces to Quality

Attributes:

Pe1, Po1, Po2, Se1 Se4, R1 R3, U1 U3


16/22


Page 13


Perform CPM analysis

DescriptionGoal: Analyzed Critical Path Schedule.



Planner

AssumptionsSchedule has been modified, requires (re)analysis.


Steps

1. User accesses application and opens applicable schedule file.2. User selects Gantt Chart from menu bar.3. Application displays interactive Gantt chart screen.4. User selects Analyze Schedule from menu bar5. Application provides Schedule Analysis dialog panel.6. User completes required fields Status Date.7. User clicks on Analyze Schedule button.8. Application performs CPM analysis on schedule.

If Errors Application displays diagnostics dialog panelIf No Errors Application displays success dialog panel with informationabout results of analysis.

9. User clicks OK button10. Application returns to interactive Gantt chart screen.

VariationsNone

Traces to Quality

Attributes:

Pe1, Po1, Po2, Se1 Se4, R1 R3, U1 U3

Use Case Use Case 2.1 - Interactive Network Diagram Chart

Add Activity

Description Goal: Activity, with associated resources, added to schedule.

Source: Interactive Web Network Chart

Actors Project Scheduler

Planner

Assumptions New activity is required to describe a work task.


Steps 1. User accesses application, opens applicable schedule file.

2. User selects Network Diagram from menu bar.3. Application displays interactive network diagram screen.4. User selects Add Activity from menu bar5. Application provides New Activity input form.6. User completes required fields.7. User clicks on Add Activity button.8. Application adds activity to database.9. Application presents Add Constraint? dialog to user.10. User clicks either Yes or No

If Yes - application returns to network diagram screen (see Use Case2.2)If No application returns to interactive network diagram screen.

Variations None

Traces To Quality

Attributes:

Pe1, Po1, Po2, Se1 Se4, R1 R3, U1, U3


17/22


Page 14

Use CaseUse Case 2.2 - Interactive Network Diagram

Add Constraint

DescriptionGoal: Constraint added to schedule.

Source: Interactive Web Network Diagram Chart


Planner

AssumptionsNew constraint is required to describe relationship between two work tasks.


Steps

1. User accesses application, opens applicable schedule file.2. User selects Network Diagram from menu bar.3. Application displays interactive network diagram screen.4. User locates and clicks on first activity.5. User drags line to second activity and releases mouse button.6. Application presents Constraint Information dialog panel.7. User completes additional information in constraint dialog panel type of

constraint, delay.8. User clicks on Add Constraint button.9. Application adds constraint to database.10. Application returns to interactive network diagram screen.

VariationsNone

Traces To Quality

Attributes:

Pe1, Po1, Po2, Se1 Se4, R1 R3, U1, U3

Use CaseUse Case 3.1 Issue Log

Add issue

DescriptionGoal: Issue is added to the log

Source: Interactive Web

Actors Team Member

Assumptions New issue has been raised and needs to be documented

Steps

1. User accesses Web and opens issue log.2. User selects add issue from menu.3. Next available issue number is displayed.4. User selects his name as Originator from dropdown menu.5. Users enters project name from dropdown menu. (Optional step

depending on needs of the company)

6. User enters a title for the issue.7. User enters description of the issue.8. User sets the status to new from a dropdown menu.9. User selects priority from dropdown menu.10. User clicks on submit button.11. Application adds issue to the log.12. Application returns to main Issue Log menu.

Variations

Step 5 is optional. A small company may only have one project. In a large

company with many projects related issues may want/need to be grouped

together.

Traces to

requirements

Pe1, Po1, Po2, Se1 Se4, U1 - U3, Sc1, R1 R3


18/22


Page 15

Use CaseUse Case 3.2 Issue Log

Update Existing Issue

DescriptionGoal: Issue is updated either status or responsible person


ActorsOriginator of Issue, Responsible person, or

Project Manager (PM)

Assumptions Existing Issue needs to updated

Steps

1. User accesses Web and opens issue log.2. User selects Update Issue from menu.3. List of Issue numbers and titles is displayed.4. User selects issue.5. Issue is displayed.6. User updates field(s) as needed using dropdown menus where available.7. User clicks on submit button.8. Application updates issue in the log.9. Application returns to main Issue Log menu.

VariationsIf a non-PM tries to update responsible person field an error message will

be generated and that field will not be updated.

Traces to

requirements

Pe1, Po1, Po2, Se1 - Se4, U1 - 3 R1 R3

Use Case Use Case 3.3 Issue LogRequest Report

DescriptionGoal: A report is generated


Actors Team Member

Assumptions User requests a report

Steps

1. User accesses Web and opens issue log.2. User selects Request Report from menu.3. List of reports is displayed.4. User selects report.5. Report is displayed.6. User is asked if he wants to print the report, save the report, request

another report, or return to main menu.7. User clicks on appropriate button.8. The application takes appropriate action.

9. When reporting requests are complete user clicks on return to mainmenu button.

10. Application returns to main Issue Log menu.

Variations Steps 2 through 8 may be repeated multiple times.

Traces to Pe2, Po1, Po2, Se1 Se4, U1 - U.3, R1 R3


19/22


Page 16

4.Other Nonfunctional Requirements

4.1 Performance Requirements

Table 8: Performance Requirements

ID Ver Requirement

Quality

Attribute

Type Rationale

Traces to

use cases

Priority Stable\

Pe1 1 System response time less

than two seconds

Performance System network latency must

be kept to a minimum.

Multiple users making

multiple updates

simultaneously.

All except

3.3

M St

Pe2 1 Report must be generated

within 10 seconds.

Performance Processing large volumes of

data may take more than 2

seconds.

3.3

M St

4.2 Portability RequirementsTable 9: Portability Requirements

ID Ver Requirement

Quality

Attribute

Type Rationale

Traces to

use cases

Priority Stable\

Po1 1 System response time less

than 8 seconds on wireless

devices.

Portability System network latency must

be kept to a minimum.

Multiple users making

multiple updates

simultaneously. Network

latency can be expected to

be greater on wireless or nonT1 networks.

All

M uns

Po2 1 Any work done off line will

automatically synchronize

upon networking device.

Portability Users must be able to

synchronize their offline

changes as quickly as

possible after networking.

All

M uns


20/22


Page 17

4.3 Reliability Requirements

Table 10: Reliability Requirements

ID Ver Requirement

Quality

Attribute

Type Rationale

Traces to

use cases

Priority Stable\

R1 1 Data input into the systemwill have multiple daily

incremental backups as well

as daily full backups.

Reliability Data will be restored as closeto the time it is lost as

possible.

All

S St

R2 1 Data backup on large

systems will be replicated to

other site locations for fail

over disaster recovery.

Reliability Larger volumes of data are

harder to recover so storing

in a separate location makes

good sense.

All

M St

R3 1 Data recovery will take no

more than 30 minutes from

the time user contacts the

help desk.

Reliability The Users inability to do

their work will be kept to a

minimum.

All

M Uns

4.4 Usability Requirements

Table 11: Usability Requirements

ID Ver Requirement

Quality

Attribute

Type Rationale

Traces to

use cases

Priority Stable\

U1 1 System shall be menu driven Usability Menus make it easy to

navigate and will encourage

exploration of the system.

All

M St

U2 1 System shall use dropdown

menus where feasible.

Usability Dropdown menus show the

valid options and makes

learning quicker and easier.

1.4, 1.5,

3.1, 3.2,

3.3

S St


21/22


Page 18

ID Ver Requirement

Quality

Attribute

Type Rationale

Traces to

use cases

Priority Stable\

U3 1 The user interface will be

intuitive and easy to

negotiate.

Usability Users will not spend

unnecessary time navigating

the UI.

All

M St

4.5 Security RequirementsTable 12: Security Requirements

ID Ver Requirement

Quality

Attribute

Type Rationale

Traces to

use cases

Priority Stable\

Se1 1 Only registered users are

allowed to use the system

Security Confidential information must

not leak out of the company.

AllM St

Se2 1 User Name and password are

encrypted.

Security http is easily hackable.

Identities would be

compromised.

All

M St

Se3 1 Data is encrypted when

traveling over http.

Security Hackers can easily hack into

http systems to steal data.

AllM St

Se4 1 Access to menus/functions is

based on the role of the

user.

Security Only the authorized role can

perform certain functions.

All

M St

4.6 Scalability Requirements

Table 13: Scalability Requirements

ID Ver Requirement

Quality

Attribute

Type Rationale

Traces to

use cases

Priority Stable\

Sc1 1 Menus can be added or

deleted as needed

Scalability Not all menus or options are

needed for a small business

3.1

N Uns


22/22


5.Other Requirements

Appendix A: Glossary

Appendix B: Analysis Models

Appendix C: Issues List

< This is a dynamic list of the open requirements issues that remain to be resolved, includingTBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>

Documents

Sample Team 2