Review the given requirements using the checklist and discover possible problems with them.                                                                                                                                                 
The following requirements are for a library system which is an interactive system providing access to a large document database and which allows the automated ordering and electronic delivery of documents to local and remote end-users. Some requirements for this system are:

Req. 1 The user interface shall be html. Users shall access the system via standard web browsers such as Netscape and Internet Explorer.

Req. 2 The system shall primarily an end-user system. Users shall use the system within the constraints of the permissions assigned by the administrator to identify, locate, order and receive documents.

Req. 3 Users shall communicate with the system mainly via the html interface.

Req. 4 User shall provide input to the system via the html interface.

Req. 5 The system shall give output to the user via the html interface, email and print. The print output shall mainly be documents.

Answer:

A requirement checklist for a system should be able to indicate the requirements that the purposed system should meet once the development is completed. The requirements should have unambiguity and should be able to give a clear vision to developers that what is needed to be developed.

The given checklist has below problem:

Req1: End user may not know HTML:

The requirements have mentioned HTML development in each requirement where HTML is a keyword associated with software development. A standard requirement checklist should not be created from development point of view, but should be from end users point of view. Thus instead of using HTML, the requirements should specify ‘web site’. The requirement should simply indicate the platform as below:

The end users will be able to access the system via a web URL using supported browsers.

Req2: Constraint are not clearly identified

The requirement states that users will have constraints of permissions, but the requirement contents do not indicate how and what constraints will be applied on which type of users.

Req3 and Req4: HTML interface should be changed with web application. There is nothing mentioned about how the user will start communicating with system e.g. login, sign up process and what data (username, password, email etc.) is needed from a user to start interaction with system.

Req5: The requirement should have clearly defined what information will be printed and what should be emailed. In case of printed document what will be the document types i.e. should it be .pdf , .doc or .jpg & .png files. The given requirement does not clarify the exact implementation required