Something About Implementation of Digital Library

When all appropriate analysis and design parts of GRAPPLE are complete, the team complies its result into a design document and hads off copies to the client and to the programmers. It then falls to the programmers to start turning the design into code.After writing the code it will be teste, rewriten according to the results of the tests, and retested - a process that will continue back and forth until the code passes all tests. The use case analysis forms the basis of the tests.

The one possible implemented Digital Library that you'll wisit after today's workshop, is coded in Jasmine OODBMS. Jasmine is used because it is Object Oriented language, has possibility of adding Multimedia data into your database, and allows you to create stand alone applications, or applications that have Web interfaces. Other agvantages of using Web interface are client software shouldn't be installed to the client's machine (client only should have an Internet browser) and Web software doesn't depend on the hardware platform that runs on.

The Server side in the deployment diagram developed for the purpose of Digital Library, now will look like:

server-node The server node with part of its components
* The Jasmine OODBMS and WebLink are parts from the Jasmine package. With Jasmine OODBMS we created necessary classes, and with WebLink we implemented the web interface.

Document specialists begin creating documentation for the system, and they create training materials as well. A godd document creation effort should proceed like a good system development effort, with careful planing, analysis, and testing, and should begin early in the development process.

The main idea of modeling one system is to focus intense efforts on analysis and design so that implementation confronts as few challenges as possible and the result of the project is a system that fully meets the client's needs.