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: Registry of descriptions
The system must register descriptions of resources (metadata and
the corresponding URL localizer).
3.1.2. REQ02: Visibility of the descriptions
All donantonio server will implement query mechanisms that allow
to select from a client a set of the descriptions that this one has.
3.1.3. REQ03: Transportability of the descriptions
All donantonio server will allow the export of a selected set of descriptions.
3.1.4. REQ04: Selection of descriptions
All donantonio client will implement query mechanisms that allow acess
in a server to a set of the descriptions that this one has.
3.1.5. REQ05: Replication of descriptions
All donantonio client will be able to replicate a set of descriptions
obtained from donantonio server through a selection criterion of the
defined ones in REQ04.
3.1.6. REQ06: Independence between servers
The servers will be independent to able give the service
independently to the clients.
3.1.7. REQ07: unicity of the descriptions
The descriptions will have to be unique in each library.
3.2. External interfaces requirements
3.2.1. User's interfaces
3.2.1.1. REQ08: User Interface
The system will count with an user interface who allows to make
the queries of descriptions easily and to access to the referenced
resources of a query.
3.2.2. Hardware Interfaces
They have not been defined.
3.2.3. Software interfaces
They have not been defined.
3.2.4. Communication interfaces
3.2.4.1. REQ09: Standard protocols in Internet
The servers, clients and applications donantonio will communicate to each other
through standard protocols in Internet, whenever it is possible.
For example, to transfer files (resources or blocks of descriptions)
existing protocols will have to be used (FTP or another convenient one).
3.3. Performance Requeriments
3.3.1. REQ10: Response time
The response times to the interactive queries will have to be reduced,
considering a efficient communication network.
3.3.2. REQ11: Concurrence
The system will have to support concurrent attention to the queries.
3.4. Development requisites
3.4.1. REQ12: Life's Cicle.
The chosen life's cycle to develop the system will be the evolutionary
prototype, so changes and new functions can be incorporated easily.
3.5. Technological requirements
3.5.1. REQ13: Bibliographical norms
The bibliographical schemes to use in the system will be expressed in RDF.
3.6. Attributes
3.6.1. REQ14: Free Software
The system will be free software and, therefore, any software component
that it will be reused will have to be free.
3.6.2. REQ15: Portability
The system will be designed portable. It will have to be possible to
implement applications donantonio in diverse languages and platforms.
3.6.3. REQ16: Maintenance
The system is susceptible to be extended. Therefore it will have
to be designed easily supported, applying for his development
the methodologies what it be precise for that.