Beruflich Dokumente
Kultur Dokumente
OOP Project
Overview of the Project
The TESDA Learning Resource Center, formerly known as Information
and Documentation Services (INFODOS) is currently under the supervision of
the Qualifications and Standards Office.
Its main function is to support the research and training objective of the
agency by providing resources and information.
Currently, it is serving policy makers, school administrators, trainers,
teachers, curriculum developers, students, workers, employers and others. The
number of clients served by the center has doubled yearly from its first year of
operation. It started with an average of twenty (20) clients per day. Now after 5
years of operation, it is serving an average of eighty (80) clients per day.
The center is currently operating using manual recording of transaction
method which results in poor services and operations for its clients. As a
solution, the management decided to commission programmers to design an
automated system for the center that will be used for the next five (5) years of
operation.
B. Users
The system shall have following users:
1. Administrator
2. Member
3. Guests
C. Policies
The system will be operating under following policies:
1. Reservation Policy
Page|2
D. Sub-systems
1. Search Book Collection Facility
a. Main Features
Abstract
Page|3
c. Description
This interface is the first panel you will see when the electronic
library is opened. This allows guest (not logged in user) to browse
through the book collection.
Book information panel (1) This shows detailed
information about a particular book in the collection.
Validation of user
Role of the user
Validity of account (active in active)
Page|4
b. Interface
The illustrations below are the prescribed layout for the project.
3
1
Abstract
Abstract
Page|5
c. Description
Log in/Log out button (1) Initially the text in this button
indicates Log in. This is used to call and show the log in
panel. Once the user successfully logged in to the system,
the text in this button will indicate log out. This button is
now used to log out a user to the system.
Log in panel (2) This interface is where the user inputs
the user account and executes the user validation process
of the system (checking of authenticity of the user
account and validity of membership). After the process it
should render the following output:
o Message box indicating the message Welcome
<first name of the user> for valid user
account
o Message box indicating the message Sorry invalid
username or password for invalid account entry.
o Message box indicating Sorry your account is
currently inactive. Please update your membership
account before you can continue.
Account information (3) This indicates the first name and
role of the logged user. It displays Welcome Guest with
no user role if the current user has not logged into the
system.
Members Panel (4) This is the same form with the guest
panel. The difference is that there are elements of the
form that is active once the member logs in.
Administrator Panel (5) This form is called and displayed
when an administrator logs into the system. Elements of
this panel is described under the borrow transaction
facility.
3. Reservation Facility
Page|6
a. Features
This facility is available only for members. It should have the
following features:
The interface is active only when the member is logged
into the system.
Derives the book to be borrowed from the search facility
and stores the information into an electronic cart.
Books included into the cart can be deleted from the list
Automatic feedback indicating the number of books
reserved through message box.
Limit automatically the number of books that can be
reserved by the user.
b. Interface
Abstract
1
2
3
4
c. Description
Page|7
b. Interface
Page|8
The illustrations below are the prescribed layout for the project.
c. Description
Borrow Transaction Tab (1) Activate the panel for
managing the borrow transaction.
From Reservation Tab (2) Activate the panel for
searching reservation transaction record via entry of
members ID number.
Page|9
Date borrowed
Due date
Transaction number
Name of member
Members ID number
b. Interface
The illustrations below are the prescribed layout for the project.
Page|10
1
2
c. Description
Add to cart button (1) add the current book in the book
information panel to the cart panel.
Lend listed books (2) transfer the listed books to the
borrow records.
Members ID confirmation box (3) this panel asks the
user of the ID number of the borrower.
Generated printable report (4) This report is generated
as proof that a borrow transaction has undertaken.
6. Return Facility
a. Features
Page|11
b. Interface
The illustrations below are the prescribed layout for the project.
1
2
3
Page|12
c. Description
Return transaction tab (1) This control activates the
return transaction panel.
Search members record interface (2) This control can be
used in looking for borrow and return transaction record of
the member via entry of ID number.
List of borrow and return transaction record(3) This
control displays the record of returned books with the
following status:
o
Return only
Page|14
1
2
c. Description
Transaction record tab (1) This control is active only if
the member logs into the system. It is used to display the
personal transaction record of the member.
List of transaction record(2) - This control displays the list
of unsettled transactions such as:
o
8. Collection Maintenance
E. Transactions
a. Borrowing
c. Reservation
The member can reserve the title of the book to be borrowed. The
reservation policy should be strictly followed in this function. The
system should record the name of borrower, the books borrowed,
ISBN, transaction number and the date reserved
Page|16
F. Database Design
Below is the proposed database design for the system
Page|17