LIBRARY WEBSITE REDESIGN

Subject: Information system Project 1

Unit code: BISY3002
Student Name: Jaspreet Kaur(170296)
Student Name Jaspreet Kaur
Unit Name Information System
Project 1
Unit Code BISY3002/ISY3002/ISY302
Project Name Library Website Redesign
Unit Lecturer Dr Andrew Levula
Due Date 10/may/2019

Page 1 of 23
Table of Contents
.......................................................................................................................................................... 0
Executive Summary ........................................................................................................................... 4
Background ....................................................................................................................................... 5
Goal .................................................................................................................................................. 5
Project Charter .................................................................................................................................. 5
Work breakdown Structure ............................................................................................................... 7
Project Schedule................................................................................................................................ 7
Network Overview ......................................................................................................................... 9
Network Diagram .......................................................................................................................... 9
Cost Details ................................................................................................................................. 11
Risk Management Plan .................................................................................................................... 12
Requirements for projects ............................................................................................................... 14
User requirements....................................................................................................................... 14
Staff requirements: .................................................................................................................. 14
Customers’ requirements: ....................................................................................................... 14
Manager requirements: ........................................................................................................... 14
Systems requirements: ................................................................................................................ 14
Software requirements: ........................................................................................................... 14
Hardware requirements:.......................................................................................................... 14
Training requirements: ............................................................................................................ 15
Major capabilities: ................................................................................................................... 15
Project conditions: ................................................................................................................... 15
Security requirements: ............................................................................................................ 15
Major Functional and Non- Functional Requirements: ................................................................. 15
Functional Requirements: ........................................................................................................ 15
Non- Functional Requirements: ............................................................................................... 15
Domain Requirements: ................................................................................................................ 16
Case Diagram............................................................................................................................... 16
Conclusion....................................................................................................................................... 17
References ...................................................................................................................................... 18
Appendix ......................................................................................................................................... 19
Resource stats ............................................................................................................................. 19

Page 2 of 23
Resource status ........................................................................................................................... 19

Page 3 of 23
Executive Summary
In this report, it explained about the library website redesign or about the online page of the library.
Library member want to upgrade the website design. So, every age’s person feels the happy while
using the website. It will also increase the customers of the library. It will have less no of page so; the
user easily finds their demanding book. It will provide the 24 hours services also on public holidays.
It will improve the standard of the library. It will take 40 days to upgrade the website and it nearly
take $15,000 to complete the project.

In this project, it explains the procedure to redesign of the website. Project are involving into three
steps. Project charter explain about the budget, timing, dependences, deliverables, constraints,
descriptions and goals. Work breakdown structure explain about the activities which taking during
the project. That helps the project team to do the efficient work. Gantt chart give the more
clarification about the timing of every activities for the project and about the milestone of the
project. The risk requirements like user requirements, stakeholders and members of the library
requirements. If, the web is not according to the requirements that also creates the problems.
Project team also must focus on the maintained the website and using the technology according to
the all aged people.

Page 4 of 23
Background
The library has their website from the last 30 years. They did the many times changes in their
website during these years. Last redesign website is done before 4 years ago. Now, they want new
design for their website according to the modern time or new generation. They want to change in
the look, font and infrastructure.

The look and design of the website are old once. Modern people face the difficulties too familiar
with that old look. The structure of the web was not perfect. Books are not properly categories on
the site so, public faced the difficulties to search any book. So, they want to redesign the web
according to the requirements of the modern people as well as old age’s people. They want to set
the new design and standard of the library.

Goal
Design the library website which suit the library standard and meet the requirement of the public.
Implementing the new framework, design and font and maintain the original look of the library like
logo. Design the new website according to the old look. Website give the user a great experience like
they will never feel bored during using the website. User can easily find their required book from the
website.

Project Charter
It gives the overall information about the project like with the budget, time, description, objectives

, goals, exclusions, benefits, dependencies, assumptions and constraints.

Project Name: library website redesign Project manager: Jaspreet Kaur

Descriptions:
• Redesign the site architecture and • Implement the new management
improve the findability and usability. system to control the activities on the
• Redesign the homepage with a new website.
look.
• Implement the new system to
maintenance
• Implement the new design that meet
the standard and requirements of the
library.
Objective/s: Goals:
• User-centred redesign • Provide great user experience and
• Reduction in size navigation system.
• Architectural overhaul • Clear idea to maintain and develop the
• Updated and intuitive navigation activities of the website.
structure • The website will be design according to
• Accessibility compliance the user needs and requirements.
• Coherent content strategy • Meeting the library standard and
requirements.

Page 5 of 23
Deliverables: Exclusions:
• Providing the manufacturing • Providing the training to the public
information. about the website.
• Information about the security systems. • After completed the project, they must
• Compliant with accessibility set their own management team.
requirements.
Benefits expected: Dependencies:
• less duplication • Before launch the security system, first
• Easy to update the information on giving the information about the system
website and giving training about it like how to
• Smaller (easily find information) control that issue with the system.
• Easily manageable like the new content • Need to upload the high-tech system to
the added in the website. secure that.
• Less dead content and less out of date
content

Assumptions: Constraints:
• The budget control overall project • The project must be completed in given
expenses. time frame work.
• The set of project goal and objects are • Website must design with limited
achievable and help to finish project colour schema
successfully. • The content must be properly
• All the required skills in the project categories
development are available. • Weekly meeting must with the key
• All stakeholders are contributing in the stakeholders.
project and help to assist the project. • Maintain the confidence in the project
team. Also valued the individual
requirements.
Timeframe:40 days Budget: nearly$15,000

Sign-offs: Sehaj, Jaspreet Kaur Project manager sign-off & Date: Jaspreet kaur
and 8/04/19

Page 6 of 23
Work breakdown Structure
In this structure, it explains about the different steps related to the planning like project charter,
meeting and business case and related to the designing, implementing, security , testing and back up
planning.

Figure 1

Project Schedule
In a schedule, it defines about the time for every single activity during the 40 days like each activity
specific starting date as well as closing date. The project started on 10/May and it will end on11/
July. It provides the information about the spending of the cost and the different person of the
project like which person doing the which activities during the

Project.

In this schedule, it provides about the different sources of the project.

Project Manager

Project Team

Testing Team

Project Management Team

Designing Team

Page 7 of 23
Figure 2

In this Gantt chart, it defines about each activity starting and closing date and how many days by
every activity during the 40 days. Resources and predecessors also define in it. Predecessors give
information of the relation of the activities like which activity is depend on which activity. If, one
activity was finished then, start the next activity but, before that can not start the second activity. It
is compulsory, first finish the first activity then, second. Resources explains the duty of the persons
who involved in the project like about the project manager, project Team.

Page 8 of 23
Network Overview
It explains the done activities in the project in the form of percentage.

Figure 3

Network Diagram
This diagram represents the same Gantt chart data in a different form.

Page 9 of 23
Figure 4

Page 10 of 23
Cost Details
It explains the cost details about each activities of the project.
Table 1

Name Remaining Actual Cost ACWP BCWP BCWS

Cost Cost

Gathering $0.00 $3,680.00 $3,680.00 $320.00 $0.00 $0.00

information

Business Case $0.00 $1,440.00 $1,440.00 $0.00 $0.00 $0.00

PMP $0.00 $480.00 $480.00 $0.00 $0.00 $0.00

SRS $0.00 $0.00 $0.00 $0.00 $0.00 $0.00

complete PMP and $0.00 $0.00 $0.00 $0.00 $0.00 $0.00

SRS

Implement new $3,200.00 $0.00 $3,200.00 $0.00 $0.00 $0.00

design

create wireframe $480.00 $0.00 $480.00 $0.00 $0.00 $0.00

new content $10,240.00 $0.00 $10,240.00 $0.00 $0.00 $0.00

management system

develop backend $800.00 $0.00 $800.00 $0.00 $0.00 $0.00

workflows for staff

Page 11 of 23
 Risk Management Plan
Anything which create the problem for a website that is a risk. Some strategies is used to reduce the
impact of risk and that called risk management. Following table explains the different types of the
risks for a website and explain the solutions like how to reduce that risks. Risks related to the
security, requirements, technology and maintained.

ID Current Risk category Risk Risk Probability Risk Risk Response Assigned to
Status Description Impact of Rating Response strategy
Occurrence Strategy
R1 Open Security In every High Medium High Mitigation To protect Project
website, it the website, Managemen
always has risk must need to Team
of virus like install the
website are perfect
easily affected frame wall
by the virus that protect
with some the web
words, or from the
functions. external
Malware is a virus. Install
harmful virus the strong
that mostly security
effected every function that
website and protect
damage that internally of
web. the web.
R2 Open Wrong Stakeholder Medium Low Medium Avoidance They must Project
Requirements requirements need to note Manager
are important down the
to shape any correct
project. If, expectation
anyone from the
understand stakeholders.
the wrong Or must
requirement record the
so as a result, conversation.
their all hard Explain every
work is point in front
nothing in of the
front of stakeholder
stakeholder. so, after that
That’s too they would
much wastage not have any
of the time. doubt..
R3 Open Maintaince After Medium Low Low Acceptance To resolve Project
implement the this, they managemen
web, process must have to Team
is very update their
important. website

Page 12 of 23
 Like continuously.
sometime, So, the web
web take too will work
much time to properly.
just perform
the one task.
That create
the many
problems for
the users.
R4 Open Technology The redesign Medium Medium Low Avoidance Provide the Project
website that template Manager
will come us about the
with the new new website
technique. and giving
Which will the proper
new for the information
old person, about it. So,
who are they can
already used easily do
to of the old their work.
web. New look Also, train
will create the the staff
problems for member
that age’s about the
person web. So, they
easily help
the older
person.
R5 Open Rogue Software It is a software High Medium Low Avoidance For reduce Project Team
who effect the this, it must
web in such a have a
way that proper
website goes security
offline for system. So, it
some time. will give the
Software’s like signal before
ransomware. effect on the
It happened software.
just for
money.
R6 Open Resources To do this Low Medium Low Avoidance It is essential Project
project, it is to first check Manager an
important that the all Project Team
all the resources
important available
resources are before
available at starting the
that time. activities.
Like design

Page 13 of 23
 of the
website

Requirements for projects

User requirements
There will be three main actors involve using this website are staff, customers and manager.
They have their own requirements from the website according their roles and needs.
Staff requirements:
➢ Need option for check the book issue date and time
➢ Check the payment for printing
➢ Access to the customers username and address

Customers’ requirements:
➢ Check the updated related to the library
➢ Easily access to any book through internet
➢ Create username by signing up
➢ Give feedback and service reviews
➢ Access to the daily activities
➢ Check their past activities
➢ Easily they can change their password

Manager requirements:
➢ Need a menu control system
➢ Needs and option to generate daily, weekly or monthly progress report
➢ Access to customer’s feedback and reviews on website
➢ Access to customer details
➢ Need to maintain the website like security system
➢ Need option to check the current activities of the customers on web
➢ Need option to update information related to the books
➢ Improve customer services

Systems requirements:
Software requirements:
➢ Window SQL library software
➢ Library automation system
➢ Fully-integrated library management system

Hardware requirements:
➢ 10 GB RAM for data
➢ Processer: intel math kernel library
➢ 300GB of hard disk

Page 14 of 23
Training requirements:
After completing the all work client have full authority to the system framework. Then, need a
training to manage and control it. Training is essential for the managers, employees and user must
know some information about it.

Major capabilities:
The client gives some website capabilities which client would like to the web:

➢ Website is easily accessed by phone and desktop

➢ Website must be available during the weekends and public holidays
➢ Web must be secure

Project conditions:
Some project conditions for the successful website:

➢ Web must be user friendly for any age person so, they can easily use
➢ It must complete the online user expectation
➢ Books must properly categories on web

Security requirements:
Some requirements for secure the websites are:

➢ Must secure customer details

➢ Payment system will be secure
➢ Secure web services

Major Functional and Non- Functional Requirements:

Functional Requirements:
Functional requirements for library website redesign are as follows:

➢ Website must be accessed by mobile phone or any handheld device through internet.
➢ Website must provide great user experience.
➢ Website must be flexible with the opening of the different book’s sections.
➢ Website must secure the general information of the public.
➢ Website must provide the feedback and the reviews features where customers give the
rating about the service.
➢ Website must analyse the time spending of the user on the web on the weekly basics.
➢ Website must provide the information about the new books.
➢ Website must inform the users about the events like sale or discount periods.
➢ Website must aware users about the procedure of issue and returning of the books.
➢ Website must show the books according to the categories.
➢ Website must upgrade when the new books is appearing so, the user can read that book.

Non- Functional Requirements:

Non- Functional requirements for library website redesign are as follows:

➢ When making reports, journal, article students need resources which is available through
search query
➢ Data must be update on website through the local network.
➢ Website must send the email to the user about any event or new books.

Page 15 of 23
 ➢ Website must have a help options so, if anyone feel any difficulties to using the website then,
they can take information from that option.

Domain Requirements:
As it is just redesigning the website so, there is no need to change the domain. Like public are more
familiar with the one domain name. That is not compulsory to change the domain name for library
website.

Case Diagram

Figure 5

It is a way to show the relationship between the user and the librarian. If, anyone wants to login and
when that person enters their account details. Then, the library person checks the details rather it is
right or wrong. Sometime, person search about the specific book like the previous book so, at that
time librarian need to check that. If, they want to reserve and renew the book they must inform the
librarian so, they can change. At the end, user provide the feedback about the library on the
website. After seeing that reviews the library member can more improve their services.

Page 16 of 23
Conclusion
It is a conclusion for a report that this website is redesign for library. It will help the library to
increase their customer like attract the new generation with the new look, structure and design. It
will completed in 40 days and within the budget. It will completed with the new design and less
number less and with the proper categories the each book category.

For this website, the project charter, schedule, network diagram, work breakdown structure, cost
detains are completed and risk management plans which helps to reduce the level of risks for
website. The requirements are already prepared according to the user, system, functional and non-
function requirements.

Page 17 of 23
References
1. S.casual.pm.s3.amazonaws.com. (2019). [online] Available at:
http://s.casual.pm.s3.amazonaws.com/toolkit/WebsiteDesign.pdf [Accessed 8 May 2019].
2. Uwaterloo.ca. (2019). [online] Available at: https://uwaterloo.ca/library/web-
redesign/sites/ca.library.web-
redesign/files/uploads/files/uwaterloolibrarywebsiteredesign_projectcharter_feb202014_0.pdf
[Accessed 8 May 2019].
3. Projectmanagementinlibraries.files.wordpress.com. (2019). [online] Available at:
https://projectmanagementinlibraries.files.wordpress.com/2012/02/wbs1.pdf [Accessed 8 May
2019].
4. University of Guelph Library Website Redesign. (2019). The Project Charter. [online]
Available at: https://uglib.wordpress.com/2013/03/18/the-project-charter/ [Accessed 8 May
2019].
5. Moody, B. (2019). Mitigate Risk with a Website Redesign Process | The Marketing Squad.
[online] The Marketing Squad. Available at: https://themarketingsquad.com/blog/mitigate-risk-
with-website-redesign-checklist/ [Accessed 8 May 2019].
6. Dropsuite.com. (2019). 7 Common Website Threats and How To Prevent Costly Downtime.
[online] Available at: https://dropsuite.com/7-common-website-threats-prevent-costly-
downtime/ [Accessed 8 May 2019].
7. Capterra.com. (2019). Best Library Automation Software | 2019 Reviews of the Most Popular
Systems. [online] Available at: https://www.capterra.com/library-automation-
software/?utf8=✓&feature%5B1%5D=39274&commit=Apply+Filters&sort_options= [Accessed
8 May 2019].
7.8. Uml-diagrams.org. (2019). An example of UML use case diagram for an
online library public access catalog - patrons can search library catalog online, reserve or
renew item, provide feedback, and manage their account.. [online] Available at:
https://www.uml-diagrams.org/online-library-uml-use-case-diagram-example.html [Accessed 9
May 2019].

Page 18 of 23
Appendix
Resource stats
Project status for all resources

Figure 6

Resource status

Table 2

Name Start Finish Remaining Work

Project Manager Fri 12/04/19 Thu 11/07/19 168 hrs

Project Team Fri 12/04/19 Thu 4/07/19 104 hrs

Designing Team Wed 22/05/19 Mon 136 hrs

24/06/19

Testing Team Mon 17/06/19 Tue 18/06/19 16 hrs

Project Management team Tue 25/06/19 Thu 4/07/19 64 hrs

Page 19 of 23
 100 hrs
90 hrs Remaining
80 hrs Availability (Project
70 hrs Manager)
60 hrs Remaining
50 hrs Availability (Project
Team)
40 hrs
30 hrs Remaining
Availability
20 hrs
(Designing Team)
10 hrs
0 hrs Remaining
Availability (Structure
and modify team)

Figure 7

Following diagram, explains about the tasks, timing, cost and resources. It is like overall view.

Page 20 of 23
ID Task WBS Task Name Duration Start Finish Predecessors
Resource Names % Complete Cost
Mode
1 1 Gathering information 6 days Fri 10/05/19 Fri 17/05/19 Project Manager,Project Team[50%]100% $3,680.00
2 1.1 Planning 2 days Fri 10/05/19 Sun 12/05/19 Project Manager 100% $320.00
3 1.2 Develop a project charter 2 days Mon 13/05/19 Tue 14/05/19 2 Project Team 100% $960.00
4 1.3 meeting with stakeholders 1 day Wed 15/05/19 Wed 15/05/19 3 Project Manager 100% $160.00
5 1.4 Kick-off meeting with stakeholder 1 day Wed 15/05/19 Wed 15/05/19 3 Project Manager 100% $160.00
6 1.5 Sign Project Charter 1 day Thu 16/05/19 Thu 16/05/19 4 Project Manager 100% $160.00
7 1.6 Finalise project management plan 2 days Thu 16/05/19 Fri 17/05/19 5 Project Team 100% $960.00
8 2 Business Case 3 days Sat 18/05/19 Tue 21/05/19 4 Project Team 100% $1,440.00
9 3 PMP 1 day Tue 21/05/19 Tue 21/05/19 Project Team 100% $480.00
10 4 SRS 1 day Tue 21/05/19 Tue 21/05/19 100% $0.00
11 5 complete PMP and SRS 0 days Fri 12/04/19 Fri 12/04/19 Project Manager,Project Team 100% $0.00
12 6 Implement new design 13 days Wed 22/05/19 Fri 7/06/19 8 Designing Team 0% $3,200.00
13 6.1 implement new navigation 4 days Wed 22/05/19 Sat 25/05/19 8 0% $0.00
14 6.2 research new navigation technologies 5 days Mon 27/05/19 Fri 31/05/19 13 Project Manager 0% $800.00
15 6.3 Brainstrom new navigation with web team 3 days Mon 3/06/19 Wed 5/06/19 14 Project Team 0% $1,440.00
16 6.4 implement new look 2 days Thu 6/06/19 Fri 7/06/19 8 Project Team 0% $960.00
17 4 create wireframe 13 days Sat 8/06/19 Mon 24/06/19 12,16 0% $480.00
18 4.1 host facilitated workshop for staff 3 days Sun 9/06/19 Tue 11/06/19 16 Project Manager 0% $480.00
19 7.2 design final wireframe 5 days Tue 11/06/19 Sun 16/06/19 18 0% $0.00
20 7.3 conduct wireframe testing 2 days Mon 17/06/19 Tue 18/06/19 19,18 Testing Team 0% $0.00
21 7.4 implement new design 4 days Wed 19/06/19 Mon 24/06/19 20 Designing Team 0% $0.00
22 8 new content management system 8 days Tue 25/06/19 Thu 4/07/19 17 Project Management team 0% $10,240.00
23 8.1 find CMSs tool 8 days Tue 25/06/19 Thu 4/07/19 17,20 Project Manager 0% $5,120.00
24 8.1.1 narrow down CMSs to top3 3 days Tue 25/06/19 Thu 27/06/19 20 Project Team 0% $1,440.00
25 8.1.2 web team rearch CMS 5 days Fri 28/06/19 Thu 4/07/19 Project Team 0% $2,400.00
26 9 develop backend workflows for staff 5 days Fri 5/07/19 Thu 11/07/19 14 Project Manager 0% $800.00

Figure 8

Page 21 of 23