This page covers Detailed design document for library management system. Detailed design starts after the system phase and system has been certified through the review. The goal of this phase is to develop internal logic of each of the modules identified during system design. In the system design, the focus is an identifying the modules, whereas during the detailed design the focus is on designing the logic for the modules. In other words in system design attention is on what components are needed, while in the detailed design how the component can be implemented in the software is the issue.
The design process for software system has two events. At the first level focus is on deciding which modules are needed for the system, the specification of these modules and how the modules should be interconnected. This is called system design or top level design. In the specification of the module can be satisfied is decided. This design level is often called detailed design or logic design, because the detailed design is extension of system design, system design controls the major structural characteristics of the system. The system design has a major impact testability and modifiability of a system and impacts its efficiency much of the design efforts for the designing software are spent creating the system design.
The detailed design refers the system documents hence the first application documents here is system design, also we are referring the data structure. Hence second application document here is database design
Structure of software package:
The software package consists of following functional components.
- Functional component 1: Registration.
- Functional component 2: Book issue.
- Functional component 3: Book return.
- Functional component 4: Search/view book details.
- Functional component 5: Update book details.
- Functional component 6: Payment (Fine).
It is graphics representation of the control logic of processing function or module representation of the system. It is one of the most common methods used for system design. In a structure charts each program module is represented by a rectangle box, modules at the top level of the structure charts call the modules at the lower level. The connection between modular are represented by lines between the rectangular boxes. The connection describes the data flows between the called and calling modules.
In this form the users have to enter the details about the student like name, regno, course…etc. If the proper details are not entered at the same time error message will be displayed and record will not be stored…And if the entered register number is already exist then the details can’t be stored and error message will be displayed.
Delete student details:
In this case admin can delete individual student details by entering his register number .If the Register no is not entered at same time message will be displayed and record will not be stored…And if the entered number is already deleted then it will be giving the message.
In this form the Liberian can issue the books to the student. If the books are already distributed to students then Liberian can’t issue those particular books.
Here the user must return the book on given date… Otherwise fine will be calculated…
In this case we can maintain the late fine of library member who return the issued book after the due date…