General Guidelines

Group Structure

1. Manager --- Assign members role, Oversee the project, weekly reports about project (1 )
2. Coordinator --- Assist in cooperation of members, facilitate time of meeting, resources, oversee
the project from the user perspective (fix left features) (1 member)
3. Design Team have role of designing, intergrating and other related roles ( 3 member)
4. Construction (SWAT) Team :- The SWAT (Skilled Workers with Advanced Tools) Team who are
programmer, who have high skill in typing, knowledge of using CASE tools, etc (5 member)
Requirements from Teams
a) Manager must report weekly the progress of the project
b) Coordingator must arrange time and space for all members
c) Design team must design timely any required one
d) SWAT team must report to manager any progress of work.

General Requirements

1) Must be connected to any Database (prefered MySQL and Ms Access) and perform CRUD
operations
2) Any errors must be fixed before sumbitted (Errors are your faults)
3) Wel structured SRS and SDS documents must be summitted
i) SRS document first week
ii) SDS document second week
4) All groups must exist on final report (Defense Day)
5) Manual about the system has to consists {wel formatted manual]
i) Overview of System
ii) Requirements needed to install
iii) Steps to install the system
iv) How it works
v) Steps to be followed during doing specific system job like reporting
vi) How errors [if occurred] fixed
vii) References [if there]
Manual report Cover Page format
 RIFT-LMS Project Final Submission Date : June 11, 2017

Rift Valley University

Computer Science Department
RAD Course Semester Project
Rift Valley Library Management System abbreviated as RIFT-LMS.
Executive Summary
The Library management system provides a Desktop/web based solution for management of
books information. This solution is aimed for Staffs in a Rift Valley University. The various users
of this application are students, teachers, staffs and University management.

Specific Details of requirements

The System must divided into the following modules:
a) Authentication and Authorization
b) Book
c) Administrator
d) Report
e) Help
f) Forgot password
g) Setting
A) Authentication and Authorization
R1 System shall provide mechanism to authenticate the user. Upon first request to the
application, the application must redirect to the login page. Once the user submits
username and password, the system perform authentication. If the username and
password does not match or not exist, the system must provide appropriate message and
redirect to login page. If the username and password are correct, system must proceed
to the dashboard of that user. Note here that the dashboard of Student, teachers, staffs
and administrator are not the same.
R2 System shall provide mechanism to authorize the user based on the role. Menu and
dashboard should be rendered based on the role. Only those links should be displayed
based on the priviledge. The roles are as per shown on the followng table.
RIFT-LMS Project Final Submission Date : June 11, 2017

B) Books Module
Books module must consists of the following functional requirements.
a) Load Students - System shall load Books based on Book ID.
b) BookInfo Displays detailed Book information of selected (Double clicked) data
Book Information must consists [but not only] of the following data.

Note: Use TextBox for Name

Use NumericUpDown for BooktID, Edition, , ComboBox for Provided
Use MaskedTextBox for SBN, DateTimePicker for Edition Year
c) New Book Page
Adds Books to database [if not exist], update [if exist]. This page must used for new
Books..
[Please, obtain Basic Book information required from librarian]
d) Book Display
Displays selected Books. The form must similar to screenshot below.
RIFT-LMS Project Final Submission Date : June 11, 2017

C) Report page

D) Help Page
Add some descriptions about system, how to use it and your group members names list.
Use a well formatted structure. Separate about page and help page in this menu. It must be
available for all users of the system.
E) Forgot Password
Used for requesting password reset to system adminstrator. It asks the requestor to insert a
valid username and comment textBox [Describes what admin shall do for]. If username is
not exist on database, system must inform the user that the user is not exist. If exist, send
the username and comment to admin page, and admin should able to see the requested
username and comments. After that, admin must redirected to setting username password
page to set it.
F) Setting
Adminstrator[only] shall set system features like overall settings like login page features,
dashboard features and users creation and updating features. Other users like teachers and
clerks [staffs] can change their own setting like password and dashboard pages but not
overall settings.
RIFT-LMS Project Final Submission Date : June 11, 2017

Overall users and their Roles

Admin

Duration of Project : 4 weeks Reports

Project Grade load : 40% week-1 (Database Design) week-2 (Interface Design)

Consideration for grading: Week-3 (Progress Report) Week-4 (Manual + Deployment)

Weekly reports (15%), Design (15%), Functionality (70%), Performance (5%)