Professional Documents
Culture Documents
Software Engineering Lab Report CS-355 Assignment: Name: Siddharth Mohan Singh Roll No: B17CS033
Software Engineering Lab Report CS-355 Assignment: Name: Siddharth Mohan Singh Roll No: B17CS033
Report CS-355
Assignment
1. Introduction
The Personal Library Software will be an application where the Library ADMINISTRATOR
(ADMIN) will issue, renew, and handle returned books as per the request of the USER
and where the USER can view their borrowed books and their respective deadlines.
1.3. Overview
Admin
o Can Issue and renew books to the USER and handle book
returns by the USER.
o Can view different categories of the books available.
o Can view books in each category
User
o Can view their borrowed books.
o Can view borrowed books’ respective deadlines.
1.4. Environmental Characteristics
1.4.1. Operating Environment (Hardware)
The software can be operated under the following minimum
specifications:
Windows XP
Intel i3 – 3.1Ghz (Dual Core)
2GB RAM
5GB HDD Space
1.4.2. People
The USERS are the students who will be able to
check their borrowed books and the respective
deadlines for each book from the application.
The ADMIN will have administrator privileges and
can do their functions from the application as well.
2. Functional Requirements
2.1.Issuing Books
Description: Book is issued only if the USER is registered and if the USER has less
than 4 (< 4) books borrowed already i.e. a USER can have a total of 4 books
issued at a time. The USER’s account is updated accordingly.
2.2.Returning Books
Description: When a book is returned by the USER, the deadline is checked and
their account is updated. If the deadline is missed, then a fee will be charged.
The book is also put back into the library.
3. Non-Functional Requirements
i. Performance Requirements:
Login/Registration will not take more than 1 minute
Any financial transactions will not take more than 1 minute.
ii. Software Quality Attributes:
System will be reliable
System can be easily maintained.
iii. Scalability:
System can be scaled easily. New Features can be added whenever
needed.
iv. Availability:
System will be available via the web, and by using Amazon Web
Services, its availability can be assured.
v. Maintainability:
System can easily be maintained.
vi. Database:
MYSQL database will be used.
1.3. Overview
User
o The User will be able to manage students’ attendance.
o The User will be able to input students’ marks and grades.
o The User will be able to view student information (Courses
Opted, Stream, Batch, Contact information etc.)
1.4.2. People
The User in the application will be the Administrative
Staff and the Teaching Faculty of the college.
2. Functional Requirements
2.1. Manage Attendance:
Description: Mark a student present or absent for a particular date.
3. Non-Functional Requirements
i. Performance Requirements:
Login/Registration will not take more than 1 minute
1.3. Overview
User
o Users can view the tickets.
o Users can book Bus, Train and Flight tickets.
o Users can download their tickets.
o Users can cancel their bookings.
1.4.2. People
The USERS are the general public. They can book or
cancel tickets. They will also have to pay for their
tickets.
2. Functional Requirements
3. Non-Functional Requirements
i. Performance Requirements:
Login/Registration will not take more than 1 minute
Any financial transactions will not take more than 1 minute.
ii. Software Quality Attributes:
System will be reliable
System can be easily maintained.
iii. Scalability:
System can be scaled easily. New Features can be added whenever
needed.
iv. Availability:
System will be available via the web, and by using Amazon Web
Services, its availability can be assured.
v. Maintainability:
System can easily be maintained.
vi. Database:
MYSQL database will be used.
1.3. Overview
Users
o Users will be able to view the menu.
o Users will be able to order food if the item is
available.
o Users will be able to make payments for their food.
1.4.2. People
The USERS are the general public. They can order food
and make payment for food accordingly.
2. Functional Requirements
2.1. View Menu
Description: Displays a list of items that can be ordered.
3. Non-Functional Requirements
i. Performance Requirements:
Login/Registration will not take more than 1 minute
Any financial transactions will not take more than 1 minute.
ii. Software Quality Attributes:
System will be reliable
System can be easily maintained.
iii. Scalability:
System can be scaled easily. New Features can be added whenever
needed.
iv. Availability:
System will be available via the web, and by using Amazon Web
Services, its availability can be assured.
v. Maintainability:
System can easily be maintained.
vi. Database:
MYSQL database will be used.