3. Specific requirements
In this section the it shows the functional requirements that will have
to be satisfied by the system. All the requirements exposed here are
ESSENTIAL, that is, a system would not be acceptable that does not satisfy
some of the requirements presented here.
These requirements have been specified considering, among others,
the criterion of testing: given a requirement,
it would have easily to be demonstrable if it is satisfied or not by the system.
Note: It is convenient to make the "requirements matrix", that confronts the
requirements with the verification method.
3.1. Functional requirements
3.1.1. REQ01: Library's Access
The user interface will be able to access to all the library
of a client donantonio.
3.1.2. REQ02: Library's Searches
The user interface will allow to make searches of descriptions,
for which it can be specified total or partially the descriptions to look for.
3.1.3. REQ03: Refinement
The user interface, after make a search and show the results to the user,
will allow to refine the search, that means, to rewrite it from the actual
making it more restrictive.
3.1.4. REQ04: Resource's Access
The results of the search will include mechanisms that will allow
to the user to ask for the making of a local copy of the referenced
resource by the description.
3.1.5. REQ05: Client's programming
The user will have mechanisms to program his client, that means,
introduce in this one the donantonio queries that will make in the
chosen servers, and when they will take place.
3.2. External requirements of interfaces
3.2.1. User's Interfaces
3.2.1.1. REQ06: General requirement of the user interface
The designed user interface must have an hig degree of usability
and have to be simple, fulfilling all the requirements specified.
3.2.2. Hardware's interfaces
They have not been defined
3.2.3. Software's interfaces
3.2.3.1. REQ07: Communication with other modules
The communication with the clients donantonio will be made with protocols
based on standards that allow to fulfill the other requirements of the system.
3.2.4. Communication's interfaces
They have not been defined
3.3. Performance requirements
3.3.1. REQ09: Resources consumption
The complexity of the applications of user must be low,
and consume few resources.
3.4. Development requirements
3.4.1. REQ10: Life's Cycle.
The chosen cycle of life to develop the system will be
the evolutionary prototype, so that changes and new
functions can be incorporated easily.
3.5. Technological requirements
3.5.1. REQ11: Bibliographical norms
The bibliographical schemes to use in the system will be expressed in RDF.
3.6. Attributes
3.6.1. REQ12: Free Software
The system will be free software and, therefore,
any software component that it also reuses will have to be free.
3.6.2. REQ13: Portability
The system will be designed portable. It will have to be possible
to implant donantonio applications in diverse languages and platforms.
3.6.3. REQ14: Maintenance
The system is susceptible to be extended.
Therefore it will have to be designed for easily maintenance,
applying for his development the methodologies that it will be necessary.
3.7. Other requirements
taca taca