0% found this document useful (0 votes)
37 views26 pages

Sig Exam

This document describes a computer system for book management created by students for a class project. It includes 5 tables to store data on authors, books, borrowers, and loans. Integrity restrictions like field length requirements are defined for each table. Relationships between the tables are connected by primary and foreign keys. The application's main menu allows users to update data, process new loans and borrowers, and generate reports. Forms and queries are used to enter, view, and search data. The system aims to help libraries manage their book collections and lending activities.

Uploaded by

Mihai Constantin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
37 views26 pages

Sig Exam

This document describes a computer system for book management created by students for a class project. It includes 5 tables to store data on authors, books, borrowers, and loans. Integrity restrictions like field length requirements are defined for each table. Relationships between the tables are connected by primary and foreign keys. The application's main menu allows users to update data, process new loans and borrowers, and generate reports. Forms and queries are used to enter, view, and search data. The system aims to help libraries manage their book collections and lending activities.

Uploaded by

Mihai Constantin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 26

„Valahia” University of Targoviste

Faculty of Economics

Business Administration

Year II

Topic:

Computer System for Book Management

Students: Ioana Georgiana Professor: Radu Valentin

Vlad Gheorghe

2020

Content
1
1. The purpose of the application
2. Defining database and tables
3. Integrity restrictions at the table level
4. Relationships between tables
5. How the application works
6. Structural presentation of the application
6.1. Menu
6.2. Queries
6.3. Forms
6.4. Reports
7. Conclusions
8. Bibliography

1. The purpose of the application

2
The computer system is a component of the information system, namely that part of it that
takes over and solves the tasks of collecting, processing, transmitting and storing data using
computer systems. In order to fulfill its role in the information system, the computer system
includes the whole all resources, rules, procedures, means, methods and techniques, which
ensure the automatic processing of data.

The database management system represents the totality of the programs used by creating,
querying and maintaining a database.

The purpose of this management information system is to provide a way to organize all the
books in a library, regardless of its size, in a way easily accessible by a large number of people.
At the same time, this management information system allows library employees to check the
stock of books in real time, their availability and provide a prompt response to book seekers
without making the huge effort of physically searching for the book.

The main components of this computer system refer to:

o management of all titles in the library

o management of new books entered in the system

o management of new authors

o management of book loans

o the management of the borrowers and the history of each one (book file)

The main functions provided by the system are:

o displaying the availability of a book, searched by author, title, year of publication.

o automatic announcement of subscribers in connection with new events (book launch,


book reservation, etc.)

An important advantage of this system is that the interface is operable on a popular operating
system (Windows).

3
2. Defining database and tables

TABLE 1

“Author”
 This table shows the list of all the authors in the library:

AuthorID – is an unique identification number associated to each author from the library.

FirstName – is the first name of the author

SurName – is the surname of the author

Country – is the country of the author

TABLE 2

“AuthorBook”
 This table shows the author’s id and the ISBN of the books written by that author.

AuthorID - is an unique identification number associated to each author from the library.

ISBN – is an unique identification number for books.

4
TABLE 3

“BOOK”
 Table “BOOK” shows the list of all books in the library.

ISBN – is an unique identification number for books.

Title – is the title of each book.

Field – represents the interest field of the book

PublishingHouse – is the publishing house where the book appeared.

AppearanceYear – is the year of appearance of each book.

CopiesNumber – is the total number of copies of each book registered in the library.

TABLE 4
“LENDBOOK”

 This table shows information about the loans of the clients.

5
LenderID – is the unique identification number of each lender.

ISBN – is an unique identification number for books.

LoanDate – represents the day when the book was borrowed.

DueDate – represents the limit-day of the loan

ReturnDate – represents the day when the book was returned.

Status – represents the status of the book (returned, borrowed, time exceeded).

TABLE 5
“LENDER”

 Shows information about each lender.

LenderID – is the unique identification number of each lender.

FirstName – is the first name of the lender.

Surname – is the surname of the lender.

Date of Birth – Is the birth date of the lender.

Category – represents the category of the lender (student, employee, retired).

E-mail – represents the mail of the lender.

6
3. Integrity restrictions at the table level

Table LENDER
 LenderID – must have a four digits code, for this we use LEN function.

If we enter a code with more or less digits, a warning like the one below will appear in the
database.

 Category – must have three predefined options (student, employee, retired) and for this
we use “Select” function.

7
After we introduce “Select “ Default Value, we access the Lookup menu to introduce the desired
categories in the Raw Source.

Table LENDBOOK
 LenderID – must have a four digits code, for this we use LEN function.

 ISBN- must have a 13 digits code , for this we use LEN function

8
 LoanDate – is a field where we need to introduce a date, and for fastening this task, we
use DATE function.

We introduce DATE() function in Default Value, so the date will be automatically introduced.

 Status- can have only three completing options( borrowed, returned, time exceeded).

After we introduce “Select “ Default Value, we access the Lookup menu to introduce the desired
categories in the Raw Source. ( borrowed, returned,term exceeded)

9
TABLE BOOK
 ISBN- must have a 13 digits code , for this we use LEN function.

TABLE AUTHOR
 AuthorID- must have 4 digits code, for this we use LEN function.

TABLE AUTHORBOOK
 AuthorID- must have 4 digits code, for this we use LEN function.

 ISBN- must have a 13 digits code , for this we use LEN function.

4. Relationships between tables

o The link between the AUTHOR table and the AUTHORBOOK table is made through the
AuthorID field.

10
o The link between the AUTHORBOOK table and the BOOK table is made through the
ISBN field.

o The link between the BOOK table and the LENDBOOK table is made through the ISBN
field.

o The connection between the LENDBOOK table and the LENDER table is made through
the LENDERID field.

5. How the application works


MainMenu

Form View Mode shows the main menu which includes four disctinct segments:

 UPDATES – includes the following buttons: LENDER UPDATE, AUTHOR UPDATE,


BOOK UPDATE;

 DATA PROCESSING – includes the following buttons: NEW LENDER, NEW LOAN,
BOOKSHEET;

 REPORTS/STATEMENTS - includes the following buttons: LOAN IN DAY…,


BOOKS LENDED BY CATEGORY, SITUATION OF CUSTOMERS;

 LABELS – includes button BOOK LAUNCH;

This menu also contains an “CLOSE” button.

11
SEGMENTS:

UPDATES SEGMENT

 → opens the existing registers and permits editing,


deleting and changing data for each lender.

12
We also used “Previous” and “Next” record buttons for navigating between registrations and
“close” button for returning to the menu.

 → opens the existing registers and permits editing,


deleting and changing data for each author.

13
We also used “Previous” and “Next” record buttons for navigating between registrations and
“close” button for returning to the menu.

 - opens the existing registers and permits editing, deleting and


changing data for each book.

We also used “Previous” and “Next” record buttons for navigating between registrations and
“close” button for returning to the menu.

DATA PROCESSING

 →opens a form for introducing a new lender in the system.

14
We also add a “close” button.

 → opens a form for adding new loan to the database.

We also add a “close” button.

15
 - opens a registration which shows lenders personal
information and their loans.

We also used “Previous” and “Next” record buttons for navigating between registrations
and “close” button for returning to the menu.

REPORTS/STATEMENTS

 → opens a query that shows all the loans registered in a day.


( You have to enter a date for the query to open).

If you do not enter a date, no data will show up.

16
 → open a query that shows all the books
lended by a category of lenders (student, employee, retired).

If you do not enter one of the 3 parameter value, no data will show up.

 → opens a report that shows the actual situation of


the lenders.

17
LABELS

 → this button opens a label about a book launch that will


be held in the library

o → this button close the repor and return to the MainMenu.

18
6. Structural presentation of the application

6.1. Menu

For an easier accessing of the menu, we used objects type “Label” and “Button”. For
example, we used label for writing the title and the name of the menu and the segments. Objects
type Button were used for queries, forms, reports and to close the menu.

6.2. Queries
19
QUERY 1 – Loans in a day

This query will display all the loans from a certain day. Thus, we will introduce the elements that
must be displayed conditioned by the loan date.

DESIGN VIEW:

SQL VIEW:

SELECT LENDER.[First Name], LENDER.Surname, AUTHOR.FirstName,


AUTHOR.Surname, BOOK.Title, LENDBOOK.LoanDate

FROM (BOOK INNER JOIN (LENDER INNER JOIN LENDBOOK ON LENDER.LenderID =


LENDBOOK.LenderID) ON (BOOK.ISBN = LENDBOOK.ISBN) AND (BOOK.ISBN =
LENDBOOK.ISBN)) INNER JOIN (AUTHORBOOK INNER JOIN AUTHOR ON
AUTHORBOOK.AuthorID = AUTHOR.AuthorID) ON BOOK.ISBN = AUTHORBOOK.ISBN

WHERE (((LENDBOOK.LoanDate)=[Introduce a date]));

QUERY2 – BOOKS LENDED BY CATEGORY

20
This query will display the loans made by a certain category of lenders. So, use put a condition
that will permit to open the records. That condition is: [Insert category(student,
employee,retired)]

DESIGN VIEW:

SQL VIEW:

SELECT BOOK.Title, LENDBOOK.ISBN, LENDER.Category, BOOK.PublishingHouse

FROM LENDER INNER JOIN (BOOK INNER JOIN LENDBOOK ON (BOOK.ISBN =


LENDBOOK.ISBN) AND (BOOK.ISBN = LENDBOOK.ISBN)) ON LENDER.LenderID =
LENDBOOK.LenderID

WHERE (((LENDER.Category)=[Insert category (student, employee, retired)]))

ORDER BY BOOK.PublishingHouse;

21
6.3. Forms
The forms are used both to update existing data and to add new data.

Form 1: BOOK UPDATE

Form view: Design view:

This form is used for updating, editing or deleting existing data about books. We also added
buttons for easier navigation , e.g. previous record, next record, close button and return to the
MainMenu.

Form 2 and Form 3, respectively LENDER UPDATE and AUTHOR UPDATE were made in
the same way as Form1: BOOK UPDATE.

The following 2 Forms, NEW LENDER and NEW LOAN have the characteristic that they
allow the introduction of new data.

Thus, using the "Property Sheet" section, changing the "Data Entry" from NO to YES allowed
the creation of an empty form for entering new data.

22
 NEW LENDER FORM:

 NEW LOAN FORM:

6.4. Reports
Report is a tool which brings information to the selected persons, usually presenting an
information generated automatically following the report configuration.

23
Connecting a table / query to the report is done by activating the Property Sheet menu and
using the Record Source property (hidden list).

DESIGN VIEW OF THE REPORT:

PROPERTY SHEET MENU:

LABEL
Labels create messages that combine text and information from tables. The option by which
we can create such labels can be found in the Create menu, Labels section.

Our label automatically generates invitations to library events, such as the launch of a book in
the near future.

24
REPORT VIEW OF THE LABEL: DESIGN VIEW OF THE LABEL:

7. Conclusions

The use of such a computer system adapted to the system in which a library works is
absolutely necessary due to the large volume of information that must be centralized, sorted and
categorized.

25
This computer system is a very useful work tool saving huge amounts of time and effort and
thus making great savings. A big plus is the almost insignificant cost of operation and almost
non-existent maintenance.

At the same time, it allows the integration of a huge database in the online system, available to
anyone who wants information or books. All system components define a set of tools that
facilitate the entire activity of the library.

Queries, forms and reports were used for this computer system. The queries used allow the
classification of the records in the tables defined according to certain conditions. Also, the forms
have the role of facilitating the way of working, creating different menus and calculation forms
as the case may be. And last but not least, the reports have the role of preparing the data for
printing, but still these reports allow the addition of some changes, this greatly facilitating the
work.

8. Bibliography

https://ro.wikipedia.org/wiki/Sistem_de_gestiune_a_bazelor_de_date

https://studocu.com/ro

26

You might also like