3. Specific requirements

In this section the it shows the functionalrequirements 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: Selection of descriptions

All donantonio client will implement queries mechanisms that allow to access in a server to a set of the descriptions that this one have.

3.1.2. REQ02: Replication of descriptions

All donantonio client will be able to replicate a set of descriptions obtained from a donantonio server by a criteria of selection of the defined in REQ01.

3.1.3. REQ03:Storage of descriptions

All client will have a local library where it will store the descriptions that it obtains by means of queries to the servers.

3.1.4. REQ04: Unicity of the descriptions

The descriptions will have to be unique in the library of each client.

3.1.5. REQ05: Queries Programming

All client will internally store the different queries what will make periodically to update the content of his library. The programming of queries will consist of adjust all the necessary information to execute them (the own query, the server against which it is executed and when it is executed).

3.2. Extern interfaces requisites

3.2.1. User's interfaces

3.2.1.1. REQ06: User interface.

The donantonio client will be able to configure all its functions by a user interface easy to use.

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 interfaces

3.2.4.1. REQ08: 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. REQ09: Response time

The response times to the interactive queries will have to be reduced, considering a efficient communication network.

3.4. Development requisites

3.4.1. REQ10: 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. 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 will be reused will have to be free.

3.6.2. REQ13: 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. REQ14: 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.

3.7. Other requisites