Save Inconspicuous Components and Enthusiasm of Stock Openness

The project aims to develop an online library system that enables students and staff of Federation University (FedUni) to access and borrow physical and digital resources. The system will allow users to login, register for a university membership, and access various resources such as books, journals, and other materials. The system will also send reminders for returning borrowed items and provide reports on the status of student borrowing activity. The project will be developed in sprint cycles, with a focus on creating a user-friendly interface and easy maintenance.

P a g e | 1
ASSIGNMENT COVER SHEET (INDIVIDUAL)
ATMC Sydney
Assignment has to be submitted online on Moodle on or before the due date.
SUBJECT CODE: ITECH 6101
SUBJECT TITLE: Software Engineering Processes and Methods
ASSIGNMENT
NUMBER AND TITILE: Assignment 1 – Case Study (Library Management)
WORD COUNT (IF
APPLICABLE):
DUE WEEK: 21st August 2016
LAB/TUTORIAL
GROUP:
LECTURER: Umesh Poudel
TUTOR: Umesh Poudel
STUDENT ID (FedUni): 30133198
STUDENT FAMILY NAME: Anjana
STUDENT GIVEN NAMES: Prajapati
I declare that this assignment is my individual work. I have not worked collaboratively nor
have I copied from any other student’s work or from any other source except where due
acknowledgement is made explicitly in the text, nor has any part been written for me by
another person. I realize that the penalties may ensure for late submission or any other
breaches of assignment rules.

P a g e | 2
Table of Contents
Nalanda University Library Scope Document........................................................................................3
Title Page:.............................................................................................................................................3
Version Control Table:......................................................................................................................4
 Part 1 (part of a project charter)...............................................................................................4
Nalanda University Library Documentation.........................................................................................4
Organizational Objectives and how the proposed system will improve processes in the
Organization:.................................................................................................................................5
 Part 2: List of Stakeholders and user roles...............................................................................5
List of definitions for keywords related to the organization and system:...................................5
The major stakeholders that may be involved in this project:....................................................6
All key user types/roles:...............................................................................................................6
 Part 3: User Profile and Example scenarios..............................................................................7
Members.......................................................................................................................................7
Library:..........................................................................................................................................8
 Part 4: Scopes and Constraints.................................................................................................9
(High level broad objectives of the project)..................................................................................9
“Scopes”........................................................................................................................................9
“Constraint”..................................................................................................................................9
 Part 5: Product backlog User stories.......................................................................................10
 Part 6: User Interface Sketch..................................................................................................11
6.1 - Sketching Requirement:-....................................................................................................11
6.2 - Sketching REQUIREMENT:-.................................................................................................11
6.3 - Sketching REQUIREMENT:-.................................................................................................12

P a g e | 3
Nalanda University
Library Scope Document
Title Page:
Author Name: Anjana
Project Name: Ana
Client name: Nalanda university library
Date: 18/08/2016
Version Control Table:
Document Name Project Name Author Name Date Version Number
Draft Scope
Document
Nalanda university
library
Anjana 18/08/2016 1.0

P a g e | 4
 Part 1 (part of a project charter)
Nalanda University Library
Documentation
Organizational Objectives and how the proposed system will
improve processes in the Organization:
The university library is hoping to develop and develop its business through web showcasing and
bargains. One of the essential destinations is to showed understudy with library resources a sorted
out database which contains all the part purposes of enthusiasm including their area, contact
numbers and their portion unpretentious components, in like manner masterminding people in light
of their enlistment status which will along these lines help the business gathering to appreciate the
once-over of all people and their interest status.
The Organization intends to give a straightforward domain to the clients (individuals and mentors)
by allowing them to get search the diverse library module, once the module is picked online
Students can obtain, return and restore things, for instance, (yet not compelled to): books, journals,
eBooks and online journals, DVDs, CDs, cameras, tripods, tablets, recording equipment and
therapeutic models, used for the most part by nursing understudies. This made books available, in
like manner outfit them with a decision to save their inconspicuous components if they have to
besides give the purpose of enthusiasm of stock openness for everything, customers can have their
unobtrusive components saved additionally for their future getting. Potential supporters and
associations who might need to join in will have the ability to join and make responsibilities.

P a g e | 5
 Part 2: List of Stakeholders and user
roles
List of definitions for keywords related to the organization and
system:
Library system
books,
journals,
eBooks and online journals,
DVDs,
CDs,
cameras,
tripods,
laptops,
recording equipment
medical models
Tutors
University library
Members
Volunteers
Information Helpdesk
The major stakeholders that may be involved in this project:
Employees
Share holders
Prospective members
Investors
Competitors

P a g e | 6
All key user types/roles:
Administration
IT helpdesk
Members
Tutors
Employees
Technician
Student

P a g e | 7
 Part 3: User Profile and Example
scenarios
Choosing two different potential users of the proposed system:
Members
User profile:
 Members are for the most part understudies who have selected online or at the school
library.
 FedUni understudies and staff, and other enrolled customers, can get things from any
FedUni grounds library.
 To obtain, FedUni staff and understudies must make their current FedUni ID card.
 Other library customers must be enrolled and have the fitting card when getting. Gaining
ought to moreover be conceivable – for most things - at the self-serve BOB ("Borrow Own
Book") stations arranged in the library - this resemble the self-checkout structures used
as a part of various stores.
 Undergraduate understudies there is a 30 thing acquiring limit and the development time
frame on most things is two weeks.
 There is a two-day ease period for by and large things. In case things are not returned or
restored inside or before the ease time frame, you're acquiring capabilities are
suspended at all grounds libraries.
 Borrowed things get the opportunity to be late in case they are not returned by closing
time on the due date. Late notice will be sent by email.
Example of high level scenario:
 Login to the website
 Register for being a part of university
 Select books available
 Provide register details.
 Provide proof of students.
 Place an order of books.
 Returns book.
Library:
User Profile:  Items for credit on the Reserve work zone of the library are for two
hours and may not be removed from the library.

P a g e | 8
 There is a two-day ease period for the most part things. In case
things are not returned or reestablished inside or before the
magnificence time frame, you're getting capabilities are suspended
at all grounds libraries.
 Three days before a thing is normal, a no-answer email is sent to the
borrower as a benevolence upgrade.
 Borrowed things get the chance to be late if they are not returned
by closing time on the due date. Past due warning will be sent by
email.
 There is a two-day ease period for by and large things. If things are
not returned or reestablished inside or before the excellence time
frame, you're getting capabilities are suspended at all grounds
libraries.
Example of high level scenario:
 Login to the website
 Check user details.
 Check due date.
 Send no reply message.
 Send overdue date notice email.
 Part 4: Scopes and Constraints
(High level broad objectives of the project)
“Scopes”

P a g e | 9
We will discuss two or three basic sweeping focuses of this suspect. One of the principal focuses of
the assignment library organization is to manufacture an ensured and an accommodating online web
base database system for the customers who might need to secure any online books, journals, dvds,
compact discs. This library structure will allow customers to acquire and save their own profile which
consolidates purposes of interest like name, address and contact number consequent to affirming
themselves using their understudy id and watchword and in the wake of picking their login
unpretentious components. Another objective will be the online portal itself, this helps the
understudies and the library to save a lot of time through manual entry and rather select themselves
online and experience a self-look for technique for having the odds to research through all
distinctive courses open and their cost structures moreover record names available for get and more
so the events. It is similarly seen as basic to have the ability to make due date notice for the
understudy which fuse the summary of all books and their present enlistment status, this will be
done by characterizing the people into dynamic, unmoving, enduring in perspective of the repeat of
their activity on the site. Borrowers should have the ability to login from any region to use the library
system. They should have the ability to see which things they have out together with other
information, for instance, due date and any holds set on things that they have. They should in like
manner have the ability to see what requests they have and have the ability to wipe out a sales if
they wish.
“Constraint”
One of the requirement that we should comprehend that changing over the manual data put away
in the workplace to the online framework won't be actualized in this anticipate.
 Part 5: Product backlog User stories
Listed below are a few user stories categorized based on Functional and non-functional
requirements.
Functional Requirements:
Requirement
ID.
Requirement Description
FReq_1 Store students basic details like name, address, telephone etc.
FReq_2 Collect student’s information
FReq_3 Send notice to students for return.

P a g e | 10
FReq_4 Members can access the system remotely to update their personal details
FReq_5 Report that show list of all students details of books borrow.
FReq_6 Report for books available for students
FReq_7 Report to show students status
FReq_8 Library can send two days early notice to return books.
FReq_9 Members can order items online
FReq_10 System keeps track of inventory of items available
FReq_11 System support online return method
FReq_12 Reports to show items status e.g. – in stock, on order, out of stock
FReq_13 System has postgraduate borrower can request an Inter Library Loan (ILL)
from another library.
FReq_14 System will be accessed from remote other university also
FReq_15 System should show return policy
Non Functional Requirements:
Requirement
ID.
Requirement Description
NFReq_1 Performance
NFReq_2 User friendly interface
NFReq_3 Easy to maintain
 Part 6: User Interface Sketch
In this part of the documentation we will sketch a high level draft concept of the user interface for
the component of the system that we anticipate being developed in Sprint cycle 1 from the above
mentioned user stories. For now we will include a sketch and a detailed description of 3 screens.
6.1 - Sketching Requirement:-

P a g e | 11
As shown in the below image, in the Product page screen, each time a product shows out of stock it
will not allow the user to buy the item which means the “Buy Item” button will be disabled and will
not allow the user to click on it.
6.2 - Sketching REQUIREMENT:-
The Login screen will now allow users to input or register with their email address instead of their
membership id. The user will be required to input their email address and password and once they
click ‘ok’ an automatic validation will run and authenticate the user. If the system is unable to
validate the user then the user can choose to click on the 3 hyperlinks ‘Forgot Password’, ‘unable to
sign in’ and ‘New user click here’. Users are required

P a g e | 12
6.3 - Sketching REQUIREMENT:-
This requirement outlines how the customer should be able to choose the quantity of a
product that they chose to buy. This below sketch shows that the ‘Quantity in stock’ is
displayed for the customer, this will help them to choose the number for ‘Select Quantity’
which will be a dropdown menu with numbers to choose from, after selecting the quantity
they can click on ‘Buy Item’