SRS document for library management system (Software Engineering)

Bachelor of Information Communication Technology Honours Degree

Faculty of Technology

University of Sri Jayewardenepura

Software Engineering – Semester 1

 

Assignment 1

Assume that you have been recently appointed as a software engineer of an information systems organization. The first job assigned to you was to do the requirement engineering part of a new software development project 

You are requested to produce the following for a development of software of your interest. 

1. A feasibility assessment on the aspects on functional feasibility, technical feasibility, financial feasibility, operational feasibility, organizational feasibility and human resources feasibility. (10 marks)

2.      Software Requirement Specification document (In line with the format given)      (50 marks)

3.      Write down the steps of 3 main scenarios and alternative scenarios                         (15 marks)

4.      Activities of the software process model should be explained relevant to your project (15 marks)

5.       Use case diagramme                                                                                                               (10 marks)

ANSWERS

 ONLINE LIBRARY MANAGEMENT SYSTEM

(1)

 

❖ Functional feasibility

•    We should identify the functionalities before developing the system and should figure out the possibilities of doing those processes.

-        A system administrator can add new users or books to the system.

-        An administrator can remove users or books from the system.

-        An administrator can see which registered users are available online at that moment.

-        A new user can register on the system themselves.

-        A user can reserve a book.

-        A librarian can issue a book. 

-    A user can read e- books.

❖ Technicfeasibilityal 

• This section describes the technical specs that the system should have.
• There is a computer in the library that is available with a multiuser system. It has 4GB of RAM, a 500GB hard drive, and Windows 10 as its operating system. 

 

❖ Financial feasibility

        •     We calculate the below expenditures.

 -         The cost of operations of the existing manual library system. 

 -         The cost of operations of the proposed internet-based system. 

-        The cost of creating the suggested system.

-        Concerning the advantages of the suggested system.

▪    So, according to the above details, it reveals that the new system is more profitable than the existing manual system. 

 

❖ Operational feasibility

▪  This describes how easy it is to use this system.

▪  This is an easy-to-use, simple application that can be used anywhere at any time.

▪  So, this is a user-friendly application.

▪  This system can be easily used by a person who does not have any computer literacy too.

❖ Organizational feasibility

•        The system will be established with the support of the organizational staff. 

•        The system engineers will provide training to the library staff.

•        Due to the easiness of this system, all users can use the system without any trouble.

•        A user manual will be provided to the new users.

❖ Human resources feasibility

•        In this section, we discussed the person who interacts with the admin side of the system.

•        This describes the people who participate in the system’s activities.

•        The librarian and other staff may enrol with the system by updating the books' info, users' info, and others. 

________________________________________________________________________________

(2) Click " Answer " to see it.

___________________________________________________________________________________

(3)

Main scenarios :

 

▪  User Registration and Login.

1.       Fill in the registration form.

2.       Make a username and a password.

3.       Verify the user account by email.

4.       Make use of the provided username and password to log in to the system.

 

▪  Add a book to the system.

1.       The system administrator should fill out the detailed form for adding the book to the system.

2.       Make up a book ID.

3.       Update the database.

 

▪  Issue a book

1.       The system administrator has to sign in.

2.       The administrator (librarian) should see the requests made by readers (users).

3.       Then the administrator should release the books if it is possible.

4.       The admin should see the available book list to see the possibility of releasing the book.

5.       After releasing the book, the admin should update the database.

Alternative Scenarios :

▪  Check the availability of a book

1.       The user should login to the system.

2.       Search for the book by its name or according to another method.

3.       See the book status.

 

  ▪  Reset the user password

 

1.       Click on the “Forgot password” button.

2.       Fill in the answers to the security questions asked.

3.       Verify it using the email.

4.       After that, type in a new password.

 

▪  See the due date  

1.       First, log into the library system.

2.       Then, see your borrowed book list.       

3.       There is the date you borrowed and the date you should bring it back. 

 

   

___________________________________________________________________________________

(4)

The waterfall model is used here. Because this is a linear process.

1. Requirement gathering, analysis and definition.

▪  Requirements for the library management system are collected by using the following methods.

 

➢  Questionnaire

➢  Interviews

➢  Prototypes

➢  Random people interviewed

➢  Observation  

 

▪  Then those requirements were categorized by requirements analysts according to functional and non-functional requirements basically. By studying requirements, the system’s basic functions and services were established. As well as the system’s constraints were established by studying and analysing requirements gathered.

 

2. System and software design.

▪  By establishing the overall system architecture, the technologies and developers allocate the requirements to either hardware or software systems.

▪  The architecture team creates the architectural diagrams and design documents.

▪  The developers use Java Script, MySQL and other languages in this stage.  

  

   3.    Implementation and unit testing 

       ▪ The issues in the system are solved here.

▪  Here, the system components are developed separately. After the development, they were checking for bugs.

▪  This process was done repeatedly until all the bugs disappeared.

▪  Each requirement is tested one by one.

▪  The validation process is responsible for fulfilling the customer's requirements.

4. Integration and system testing

▪    The separately developed components are integrated by the testing engineers and tested in an integrated hardware and software environment. Here, check whether the system is working according to the specific requirements. This is done by testing engineers and experts.

 

5. Operation and maintenance. 

▪    While the system is released to users, the users’ new requirements and the issues that occur at this stage are resolved.   

___________________________________________________________________________________

(5)