Information System Development Project

This document provides a Gantt chart, requirement documentation, use case, and sequence diagram for an information system development project. It includes tasks, durations, and dependencies, as well as details on the pay fine scenario and book search functionality. The document also discusses the role of the head librarian and provides a bibliography of relevant sources.

Running head: INFORMATION SYSTEM DEVELOPMENT PROJECT
Information system development project
Name of the Student
Name of the university
Authors note

1INFORMATION SYSTEM DEVELOPMENT PROJECT
Task 1
Gantt chart of the Project is provided below for this assignment as a project.
Task Name Duration Start Finish Predecessors
LMS DEVELOPMENT
PROJECT 28 days Wed
09/01/19 Fri 15/02/19
Project Initiation 4 days Wed
09/01/19
Mon
14/01/19
Identify Stakeholders 2 days Wed 09/01/19 Thu 10/01/19
Determine Scope of
the Project 2 days Fri 11/01/19 Mon 14/01/19 3
Feasibility Study 28 days Wed
09/01/19 Fri 15/02/19
Analysis of System
requirements 3 days Tue 15/01/19 Thu 17/01/19 4
Feasibility Study of
the Project 2 days Fri 18/01/19 Mon 21/01/19 6
Project Proposal
submission 2 days Tue 22/01/19 Wed 23/01/19 7
Completing Project
plan 1 day Thu 24/01/19 Thu 24/01/19 8
Requirement
analysis 28 days Wed
09/01/19 Fri 15/02/19
Preparation of
functional and Non-
functional requirement
4 days Thu 24/01/19 Tue 29/01/19 8
review and
Elicitation of the
Requirement
3 days Wed 30/01/19 Fri 01/02/19 11
Revised project plan 2 days Wed 09/01/19 Thu 10/01/19
Development and
Design of the system 13 days Wed
30/01/19 Fri 15/02/19
Draft Design
document 2 days Wed 30/01/19 Thu 31/01/19 11
Design Use case
Diagrams 3 days Fri 01/02/19 Tue 05/02/19 15
Completing Use
case Textual Description 2 days Wed 06/02/19 Thu 07/02/19 16
Completing
Sequence diagram 2 days Fri 08/02/19 Mon 11/02/19 17
Designing class
diagram 2 days Tue 12/02/19 Wed 13/02/19 17,18
Completion of
system Interface design 2 days Thu 14/02/19 Fri 15/02/19 19

2INFORMATION SYSTEM DEVELOPMENT PROJECT
Gantt chart for the Project
The Gantt chart is very useful in controlling a multiple activities while ensuring that those
activities are completed on the stipulated time.
Trello Board

3INFORMATION SYSTEM DEVELOPMENT PROJECT

4INFORMATION SYSTEM DEVELOPMENT PROJECT
Task 2
Requirement documentation for Pay Fine Scenario for the Borrower:
The Borrower must be an active, inactive, temporary, pending, but not a suspended member
of the library.
The borrower or the student must have a card with the barcode so that the librarian or the
staff can track the status of the borrowed book and the amount of the fine incurred by the
borrower.
The return date must be a later than the return date of the books.
The Fine must be paid only in person to the librarian.
In case the total fine reaches the value $25, then no books or papers will be allowed to the
borrower.
After the fine is paid to the staff then the staff will be responsible for providing the receipt to
the borrower.
The staff must change the status of the borrower from suspended to the active status.

5INFORMATION SYSTEM DEVELOPMENT PROJECT
Head librarian will be able to generate periodical reports based on item / books/ paper usage,
borrowing rates of the items in the library, usage of the papers/ books by different
departments as well as other user types such as staff, students.
Task 3
Following is the use case for the pay fine scenario. The use case diagram specifies
the context of the specific scenario of the proposed system. In this way it becomes easy to
find and capture accurate functional requirements of the proposed information system for the
library. Moreover, it becomes easy to validate the architecture of the system and
implementation as well as the generation of the test cases.

6INFORMATION SYSTEM DEVELOPMENT PROJECT
Task 4
Name Searching for a book by using key words using the library
information system.
Version U502
Goal Finding availability of some book matching with the
keywords related to the subject/publication/ author. If the book is
available then the students and other borrowers can borrow the
book by using the library Information system.
Summary Search books use case will include all of the actors and
their respective actions in order to compete the goal of the user to
borrow a book depending on its availability. The books
previously issued to other user will be displayed in the search
result.
Actors Library staff, head librarian, administrator of the system
Student and other borrowers of the books.
Pre-conditions Student or the borrower have no pending fines to be paid
and the account status for the user is active in the information
system. The Required book must be in stock of the library so that
it can be allowed to the other student.
Triggers Students or borrowers logs in to the system and using the
system searches for the book to be borrowed using the keywords
such as book name, author name, publication etc.
Basic Course of
Events
Using different related key words related to
author/subject/ year or publication book or paper is searched by
the user (either by a student or other type of borrower).

7INFORMATION SYSTEM DEVELOPMENT PROJECT
The borrower then sends a borrow requests to the library
staff. After checking the borrower account as well as pending fine
information the book is assigned against the account by scanning
the barcode of the library card of the borrower.
Post-Conditions Intended book is issued for specific days against a certain
user account in the information system so that the fine can be
calculated by the system after the return date assigned for the
account.
Business Rules The borrower account must be in active status.
The user account must not have any outstanding fine
amount against any book.
The library staff must assign a return date after the issue
date for a newly borrowed book.
Books that have hold request on it must be assigned to the
user who requested the hold first.
For a pending account, the books will be issued only if the
fine is paid in person to the library staff.
Task 5
The sequence diagram is useful for dynamic modelling of the response of the system
against some user interaction. In addition to that, the sequence diagram also presents the
interaction among the objects and processes that live concurrently.

8INFORMATION SYSTEM DEVELOPMENT PROJECT
In addition to that the system calls and messages that are switched among the
different modules in order to perform a specific functionality before the object lifeline ends.
In the following diagram the main actor is student or the borrower that interacts with the
library management system.

9INFORMATION SYSTEM DEVELOPMENT PROJECT
Bibliography
Chemweno, P., Pintelon, L., Van Horenbeek, A., & Muchiri, P. (2015). Development of a
risk assessment selection methodology for asset maintenance decision making: An
analytic network process (ANP) approach. International Journal of Production
Economics, 170, 663-676.
Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems analysis and design: An object-
oriented approach with UML. John wiley & sons.
El Ahmar, Y., Le Pallec, X., & Gerard, S. (2016). Empirical Activity: Assessing the
Perceptual Properties of the Size Visual Variation in UML Sequence Diagram.
In HuFaMo workshop.
Jena, A. K., Swain, S. K., & Mohapatra, D. P. (2015). Test case creation from UML sequence
diagram: a soft computing approach. In Intelligent Computing, Communication and
Devices (pp. 117-126). Springer, New Delhi.
Mythily, M., Valarmathi, M. L., & Durai, C. A. D. (2018). Model transformation using
logical prediction from sequence diagram: an experimental approach. Cluster
Computing, 1-12.