S.

NO CHECKLIST

Usability
Browser Support, screen locking & screen back/forward support

Ease-of-use, learnability, efficiency, etc

Reliability
Complete or partial loss of the module ability to perform a business
operation.

Recoverability
Plans to have a Continuity of Operations.

How soon after a failure is detected must service be restored?

Data Backup/Restore
If the hardware, data, and onsite backup are destroyed, Where backup
copies of the system and data held within it, will be stored?
Availability
System availability is the time when the application must be available for
use. Required system availability is used in determining when maintenance
may be performed.
Performance
What is the response time for reports, queries, and updates?

what is the total number of user sessions open for the entire application?

What is the total number of concurrent sessions that can be opened by a

single user?

What is the total amount of idle time before the user session is forced to
terminate?
Acceptable Transaction Response Times – peak

Acceptable Transaction Response Times – non-peak

Data Retention
Data Retention details the length of time that various data will be retained
in the system.
Capacity
Anticipated Number of Users

Anticipated Number of Concurrent Users

Anticipated Number of Locations

Anticipated Number of Daily Transactions

Security
Protection for sensitive information

Privacy issues & policy

Physical access security.

Internationalization
Multi-lingual implementation of application module
 EXAMPLE COMPLY

The requirement for different web browsers support like InternetExplorer,

FireFox alogn with screen locking & screen back/forward support.
Simple screens & understandable software features for the ease of use.
E.g. easy navigation, easy key handling, color scheme, standards etc.

Understanding how critical is the impact of non-operation of certain module

in system. E.g. if reception module fails due to system failure, how critical it
is for business, this will help in designing best solution and considering the
criticality of the module.

Alternative to be defined in case of failure of main process E.g. in case

mobile communication is failed, the user can upload the data in system
using using bluetooh.
Time limitation for restore of service in order to perform business
operation. E.g 10 min in case of system hang.

Storage location of system data in order to deal with any failure. E.g.
backup servers.

Defining peak and non-peak hours, this will help in organizing system
maintenance activity whenever required and least impacting any business
process.

How quickly , response is required while using an application or particular

module. E.g. a particular report should take 2 mintues to provide output.
How many user sessions shall be allowed during peak hours, this will define
the load on an application.
How many concurrent sessions can be used opened by a single user in
order to perform business operation. E.g. if one terminal is logged in from
particular user then no other terminal can be logged in using the same user
name.
e.g. After 5 min of non-activity on particular user session, it should be
terminated.
Response time on any screen, it's save, update response time. E.g. it
should not take more than 2 sec to fetach the whole information of packet
on consult screen during peak hours.
Response time on any screen, it's save, update response time. E.g. it
should not take more than 2 sec to fetach the whole information of packet
on consult screen during peak non peak hours.

e.g. The time frame of audit logs to be available for view in the system,
after stipulated time frame such data will be migrated and stored in
separate location.

How many users will use the application or a particular module? E.g. 2000
users will use the application.
How many concurrent users will be using the application module at same
time? E.g 1000 users will be using the application simulatenously.
How many Locations or terminals will be using the application? E.g. 200
terminals will be using the application 10 at Bogota, 10 in cali.
How many daily transactions can happen from a terminal using the
particualr module of an application? E.g 2000 packets reception, 1000
packets legalization etc.
Dictate protection for sensitive information. Some types of privacy
requirements include: data encryption for database tables, policies
regarding the transmission of data to 3rd parties, Data Security,Encryption
Requirements
Any privacy policy that need to be mentioned, for e.g. all the details
mentioned at the back side of Guias as privacy & guidelines.
The use of authentication of application from LDAP or any other security
framework.

Implications could be the need to have multi-language descriptions of

module . In general, internationalization focuses on the countries, time-
zones, currencies and languages that will be supported.