OWSD: IMPLEMENTATION OF AN ONLINE JOURNAL WEBSERVICE

DIRECTORY
Muuka mweemba Cathrine Gondwe Castrol Chilumba
Department of Library Department of Library Department of Library
and and and
Information Science Information Science Information Science
University Of Zambia University Of Zambia University Of Zambia
Lusaka, Zambia Lusaka, Zambia Lusaka, Zambia
2017012984@student.unz 2017012930@student.unz 2017012961@student.unz
a.zm a.zm a.zm

Aaron Chibale Abraham Kamanga

Department of Library and Department of Library and
Information Science Information Science
University Of Zambia University Of Zambia
Lusaka, Zambia Lusaka, Zambia
2017012934@student.unza.zm 2017001431@student.unza.zm

KEYWORDS
Web service directory aggregator

1.0 PROJECT DESCRIPTION of Zambia. This Journals aggregators is a tool

Due to the variety and numerous of journals,
it should be easier for students and the UNZA
community to publish articles in the journal.
In fact, students feel more difficult to search,
select and sort journals that match their
fields. Likewise, lack of information about
frequency of publication, author guideline,
focus and scope of the journal become
problems for potential students. Therefore,
we proposed a solution by developing a
Journal Aggregator system for the University
that will be used to gather researchers/ writers
of papers and journal manager. The project
will aim at creating a web service that will
facilitate librarians at the University of
Zambia and the web service will also be used
to add information in the library collections
repository from various websites. Other roles
of aggregator for library collections will
include to facilitation of the user in accessing
the collection without opening some websites
and it will also be used to form a positive
image for the library and data entry
processing to help librarians in updating
references or collections.
1.1 Project Significance
This online journals aggregator system will
take the concept of a web portal that will be a
meeting system between journal managers,
journal, researchers, and visitor. It's will
facilitate the journal managers to be able to
promote the journals he managed, inviting
potential researchers to include their research
article and journal transactions inside it. For
the researcher, online journals aggregator
system will be a means to choose, like and
keep journals that are considered according
to the scientific field, so it will facilitate
researchers to obtain information related to
the journal. As for the general public, the
online journals aggregator system will
provide search facilities in journals, articles
and authors in the same system.
2.0 PROBLEM STATEMENT
Whereas accessing electronic information
resources offers opportunities to obtain
accurate and timely literature, observation
shows that there is low usage of E-resources
at The University of Zambia library. This is
evident from library statistics, register
records and from information obtained
verbally. When students asked as to whether
they have ever used E-resources, a low usage
of electronic resources was cited as a
challenge to the student’s populace. And the
University Library doesn’t even conducts
workshops, seminars to communicate to
students regularly about the available of e-
resource materials, students are not
effectively using electronic information
resources. Some of the available electronic
information resources have not been utilized
at all. Hence we saw the need for the UNZA
library to subscribe to our web service as
there will be total of electronic information
resource packages which include full text
electronic journals, current awareness
services and bibliographic databases. The
journal aggregator will also contain a
provision of electronic document delivery
about an average less than 8 (eight)
documents request forms will be submitted in
a month for articles in electronic journals. It
is not known why there is such low usage of
these resources in the university whose
student population is so large. This lack of
understanding is what is causing concern to
both the university and library managers.
2.1 Broad Objectives
To create the aggregator system of online
journal that will be a meeting system between
journal managers, journal, researchers, and
visitor.
Specific Objectives
 To ensure the journal managers are
able to promote the journals they
manage and getting potential
researchers and authors.
 To ensure researchers obtain
information related to the journal.
 To provide search facilities in
journals, articles and authors in the
same system.
 Users must be able to search title,
author, and year of publication
Questions
1. How can journal manages promotes
the journal and get potential
researchers and authors?
2. How researchers can gets the
information that are related to the
journal?
 3. In what way are the search facilities
in journals, articles and authors
going to be in a same system?
4. Will the users be able to search title,
author and year of publication?
3.0 PROCEDURES AND
METHODS
3.1 Specifications
The UNZA journal aggregator is an advanced
online web service integrated with the
Moodle Website that aims at allowing journal
seekers, authors, and managers to be able to
increase number of online journal in the field
of science, an effective promotion is needed
to introduce the journal to the researchers.
Meanwhile, the researchers find it difficult
and take a long time to find and open one by
one journal web pages to view the profile of
the journal which is supposed to accept the
results of the research he wrote. While the
public needs an access to obtain information
related to the results of research in more
detail and complete in the same places. For
virtue of the plugin having two target users,
that is, lecturers and students. It will have an
end-user interface (Students) and
administrator interface (Lecturers). The end-
user interface will be a form. It will consist of
a text area field and a pdf document searching
field. The text area field will be used to
provide a reason as to why a particular user
wants to access, update, publish and organize
data in the system. The file searched will be
portrayed. Once the journal has been
portrayed, the information will be sent to the
database after which a direct message
containing the search information will be sent
to the journal managers Moodle inbox and
the email as well. Once the response is given
by the manager. On the other hand, the
administrator interface will be a simple
rendering page that will display the
information searched by the user. The project
will be broken down into parts: the web
interface, integration, and database
repository.
Figure 1. Showcases the implementation of
the UNZA journal aggregator and how it will
allow users to interact with objects that allow
them to publish information into a database
repository, that can then be accessed or
viewed by their respective instructors from
whom to achieve this end user interface
HTML/CSS languages will be used (and
alternatively bootstrap). The integration with
the Moodle website facilitates the navigation
and access into various courses and
departments to ensure requests are directed
appropriately as determined by users and the
journal manager. The web-based journal
aggregator will act as an extension of already
existing Moodle web pages that connect to
key management folders through the
provision provided by the Moodle Activity
module where the plugin capabilities will be
defined. Additionally this functionality will
allow managers to access and view
information uploaded by the system users
and allows them to make remarks and reply
in the form of approval or denial in relation
to the user’s request.
Figure 1

Figure 1 shows the functionality of the
system.
3.2 software implementation methodology
With waterfall development based
methodologies, the analysts and users
proceed sequentially from one phase to the
next. The deliverables from each phase are
voluminous and are presented to the project
sponsor for approval as the project moves
form phase to phase. There are six phases that
are involved in the waterfall model which
comprises feasibility study phase,
requirement gathering and analysis phase,
system design phase, implementation phase,
testing phase, deployment of system phase
and maintenance phase. Once the phase is
approved by the sponsor, it ends and the next
phase begins.
1) Feasibility Study Phase
Here, we will carry out a study to gain
an understanding of the customers
(students) current system and
problems experienced in this system
through interviews, observations and
participations. We will use the
obtained data to determine the
viability of the system being proposed
in terms of technical, economic and
social feasibility.
2) Requirement Gathering and Analysis
At this stage, we will gather
information about what the customer
needs and define the problem the
system is expected to solve. We will
also include customer’s business
context, products functions and its
compatibility. We will gather
requirements such as the software like
the programming language to use,
database model and hardware needed
such as laptops, printers, etc. The
phase starts with brainstorming the
idea of current problem and system
request. Besides, meet up with user to
know the detail requirement for this
system. In this phase also, the
requirement gathering is been is been
discussed with supervisor to conclude
the requirement suitable for the
system.
3) System Design
At this stage, we will make an overall
design of the system architecture and
physical design which includes User
Interface and database design. It is at
this stage that we will identify any
faults before moving onto the next
phase. The output of this stage is the
design specification which is used in
the next stage of implementation. The
requirement specifications from the
second phase are studied in this phase
and the system design is prepared.
This system design helps in
specifying hardware and system
requirements and helps in defining
the overall system architecture.

4) Implementation/Coding
At this stage, we will be coding as per
the design specification(s). The
output of this is one or more product
components built according to a pre-
defined coding standard and
debugged, tested and integrated to
satisfy the system architecture
requirement.
The inputs from the system design are
converted, to small program called
unit in first developed then it will
have integrated in the next phase.
Each unit is developed and tested for
its functionality, which is referred to
as Unit Testing.
5) Testing
At this stage, we will ensure both
individual and integrated whole are
methodically verified to ensure they
are error free and satisfy customer
requirements. We will involve both
unit testing of individual code
module, system testing of the
integrated product and acceptance
testing conduct by or on behalf of
customer. We will ensure bugs found
are corrected before moving on to the
next stage. We will also prepare
review and publish product
documentation at this stage. All the
unit in implementation phase are
integrated into system after testing of
each unit. Any change of coding,
error, functionality or upgrades will
also be tested. User interface will be
checked to ensure they are connected
to database and appropriate with the
system.
6) Deployment of System
Once the functional and non-
functional testing is done, the product
is deployed in the customer
environment or released into the
market.
3.3 system evaluation
This stage occurs after installation. It
involves modifications on the system to
improve performance. Such changes are user
initiated or as a result of bug being discovered
which were initially not known. These
modifications are recorded for
documentation and system update. After the
system deploy in the customer environment,
there will be some issue arise. To fix that
issue, patches are released to enhance the
functionality of the system to better version.
4.0 RELATED WORK
Aggregators provide online access to
a large number of journals from
different publishers on a single
platform and customize information
for individual libraries based on the
needs of each library. This type of
arrangement is beneficial for both the
libraries and the publishers. Libraries
can enter into agreement with single
service provider instead of dealing
large number of publishers.
Publishers gain increased exposure
for their services by making their
contents available through more than
one source. There are large numbers
of aggregators providing e-journal
services on the Internet that exist and
are being employed around the world.
4.1 OCLC’S Electronic Collections Online
(ECO)
Online Computer Library Centre (OCLC) has
been a major force in bringing libraries into
the online world and continues its
contributions as a database and journals
aggregator. In the early 1990’s, as part of its
continuous research on information retrieval
and distribution, OCLC created the
Electronic Journals Online (EJO) program, a
pre-web experiment in the computerised
production and delivery of serials. Feedback
from pioneering EJO customers and the
program development experience laid the
foundations for Web-based Electronic
Collections Online (ECO) launched in 1997.
What OCLC learned from EJO is that users
want a critical mass of journals searchable via
the same interface, that electronic journals
need to be integrated with other electronic
resources, and that library buyers want
permanent access. What OCLC now offers
through ECO is full text of more than 4,000
journals from close to 100 publishers. The
collection is searchable via the FirstSearch
interface both as a freestanding collection
and through links from more than 35 of the
70 databases OCLC delivers through
FirtSearch. Libraries can choose to subscribe
to any or all of OCLC’s journals either
through the Print Subscriber Program or the
Journal Licensing Program. Under the Print
Subscriber Program, publisher’s provider no-
charge electronic rights to libraries that want
or need to maintain a print subscription. The
journal Licensing Program covers titles
whose online versions are not free with a
print subscription. Under this ECO program,
publishers charge a fee either for adding
electronic rights to a library’s print
subscription or to cover an e-only
subscription if that is preferred. OCLC
charges an account management fee under
both programs ranging from $12 to $20 per
title depending on the total number of ECO
subscriptions. In most instances, when
libraries pay publishers directly for electronic
rights (as in the case of Project MUSE, for
example) they also may access these titles via
ECO. ECO is unique because it offers not
only access but permanent ownership, which
is critical to libraries. Assuming an honest
broker role based on its position in the library
community, OCLC stepped forward to
guarantee the existence of permanent
archived electronic journals so libraries can
cancel print subscriptions if they so wish.
Centralized archives are maintained and
backed up on site, remote backups are in
place, and migration from obsolete formats is
promised.
4.2 Ingenta
U.K-based Ingenta (with whom Gale is
partnering) is a journal aggregator that offers
access to 5,400 titles (and counting). A
former investment banker founded Ingenta
with banking form London venture
capitalists. Its name, which means enormous
in Greek, declares high ambitions. Though
the emphasis on Science, Technology and
Medical (STM) journals, offerings include
journals from many other fields. Through the
2001 acquisition of its competitor,
Catchword, Ingenta has added many small
publisher and professional society titles to its
list. The companies provides services to both
libraries and publishers that benefit both.
Libraries are offered title, table of contents,
and indexing to a wide range of scholarly
journals. Electronic access is free to libraries
that subscribe in print or online once they
register their titles. Libraries create a free
institutional administrative account that can
be used to notify ingenta of titles they wish to
access. Ingenta does sell certain services to
libraries including document delivery. The
company bought CarlUncover with its reveal
alerting service, and libraries can purchase
current awareness services for users based on
reveal. Ingenta also offers a customized
service to help libraries create research
portals and to facilitate e-acquisitions
functions and track document delivery
spending. But ingenta does not rely heavily
on income from libraries. Publishers pay
Ingenta to create and host online versions of
their journals and to manage subscriptions
and transaction-based access. Fees for article
delivery, especially to corporations, are a
primary source of revenue. Ingenta has
partnered with many library information
providers to produce specialised reference
resources. Examples include websites for
MacMillan’s Grove dictionaries of art,
music, and opera, as well as its encyclopedia
of life sciences, astronomy, and astrophysics.
Ingenta also has worked with the
Organization for Economic Coorperation and
Development (OECD) to develop a web
presence and with CABI publishing to create
specialised sublect-based journal
aggregators.
4.3 Project MUSE
Project MUSE, like JSTOR, was an early
journal digitizing project funded in part by
the Mellon Foundation. It originally included
only the 40 or so titles published by the Johns
Hopkins University Press and has now
expanded to more than 200 publications
(with a commensurate increase in cost).
MUSE, with its focus on current literature
produced by academics, has not diversified
its readership beyond colleges and
universities.
4.4 HighWire Press
HighWire Press, a project of the Stanford
University libraries, began in 1995 to provide
electronic access to major STM journals.
HighWire was inspired by fears that
scientific societies might be unable to make
the expensive transition from print to online
production and distribution of journals on
their own. HighWire produces more than 300
STM sites. Partnering with professional and
scholarly associations, HighWire offers the
technical infrastructure and expertise to
create journals that move beyond simple
replication of the printed page in electronic
form. Links among authors, articles and
citations; interactivity; and high-resolution
images and multimedia add innovative
dimensions to HighWire Journals. In
addition, HighWire and many of its partners
subscribe to the view that the communication
of scientific information should be as barrier-
free as possible. Much (though not all) of the
archive of journal backfiles is available free
worldwide. HighWire also is involved in an
electronic archiving initiative called
LOCKSS (Lots of Copies Keep Stuff Safe).
4.5 JSTOR
JSTOR fits into the category of a journal
aggregator since it hosts a large collection of
unrelated journals. It is unique because this
aggregation was created through a massive,
ongoing digitization program. Conceived as
a model project, JSTOR has been a stunning
success in ways unforeseen by its creators.
Funded by the Mellon Foundation in 1995,
JSTOR was one of the earliest programs for
digitizing journals. The goals of the project
were to increase access to and preserve older
journal issues, and the same time give
libraries the opportunity to save the cost of
binding and storing backfiles. Starting with a
selection of 10 economics and history
journals, JSTOR has grown into a file of
almost 300 journals containing almost 2
million articles. Subject-based collections are
offered with pricing based on size and type of
library. Consortia are not eligible for
discounts, but group licensing is available for
administrative convenience. Though JSTOR
seems to have the most to offer to big,
research-oriented institutions, many small
college and university libraries, community
colleges, government agencies, foundations,
museums, and other cultural agencies are
among its almost 1,000 U.S. participants.
JSTOR’s relatively low cost allows smaller
academic institutions to provide students and
faculty with materials previously available
only at research libraries and has increased
opportunities for distant learners on all
campuses that subscribe. JSTOR has opened
up the use of older materials in teaching at the
college level and also is encouraging
possibilities for use in secondary schools and
public libraries. Only a small number of
public libraries are current subscribers, but
might want to consider this opportunity for
serving students, lifelong learners, freelance
writers, and independent scholars in their
communities. JSTOR continues to add new
collections on a regular basis, including, for
example, the remarkable record of the history
of science contained in its General Science
Collection. To reassure journal publishers
that they would not lose revenue through
subscription cancellation, JSTOR’s original
plan was to digitize backruns from the
beginning date of the journal to a point
mutually agreed on by the publisher: usually
five years from the current year. So, to see all
the issues of a title, the reader must visit
JSTOR for the older issues, and view current
issues on a different site. Ideally the two
locations should be linked, and JSTOR is
working, at least with Project MUSE, to
create these links. JSTOR is committed to
provide a trusted archive so those libraries
wishing to regain space in their stacks by
withdrawing older volumes might do with
confidence. Surveys of participants have
been conducted in 1999, 2000, and 2002 to
gauge the extent to which the existence of the
JSTOR archive has led libraries to withdraw
bound volumes, remove them to offsite
storage, or cease binding current issues.
Although the survey results do show some
impact on the management of print
collections in participating libraries, most
libraries are still maintaining bound volumes
of the core journals in JSTOR’s collection.
To complement its pledge to maintain its
electronic archive in perpetuity, JSTOR is
partnering with the Centre for Research
Libraries to coordinate creation of a
corresponding print archive. This
development, along with an increasing
willingness to substitute online for print for
current journal access, may eventually have
an impact on subscriber library policies
regarding bound volumes. Now a mature
project, JSTOR demonstrates the challenges
producers face in maintaining large files of
electronic journals. Problems for the
producer include acquiring rights to full runs
of serials digitize, integrating the digitized
material into broader information delivery
system, and ensuring perpetual access to the
electronic archive. Pricing for the collections
specify an archive capital fee to defray the
costs of digitization as well as annual access
fee. Significant additional outlays will be
required in the future, however, to ensure the
existence and integrity of the archive.
5.0 Proposed Solutions
An aggregator is an entity that gathers,
organizes, and classifies things into groups
that have similar characteristic or it is an
entity that transparently collects and analyses
information from different data sources. In
the process, the aggregator revolves the
semantic and contextual differences in the
system. Based on the results included in this
study, it is clear that aggregators provide a
service of high value to academic libraries.
Currently, librarians are very focused on the
very long term conservation of their
collection. Thus we will develop this
software system that will enable aggregation.
So it is right to say aggregators play a vital
role in the development of the library and
information resources. After a critical
analytic and technical quest which was done,
here are functionalities and roles which will
be executed by the system upon completion;
Functions such as handling, orders, billing,
payments, renewals and cancellations will be
performed. The system will challenge the
librarian’s role in collection development.
The emergence of this journal aggregator
system will have a considerable impact
especially on the role of the collection
manager in the library [4].
 The system will maintain the
customer-supplier relationship with
publishers.
 It will help small publishers to gain a
very careful deal-market.
 It will offer libraries a great range of
choices with different access models
available for different subsets of
content. Options for the library and
publishers will be increased.
 The diversity of publications from
large numbers of publications will be
facilitated
 It will allow librarians and publishers
to search and access quickly any
document they seek in an electronic
environment.
Ethical Considerations
The study will ensure that the research ethics
are taken into consideration throughout the
research process. On the respondent’s side,
the researchers will make sure that
participants are informed of the main purpose
of the study before engaging them into the
study. Information sheet will be provided to
further explain the study and they will be
given time in this case 48 hours to read the
information sheet. Participants will be based
on voluntary basis; consent will be obtained
from the potential respondents in which they
are required to sign the informed consent
before the interview and online
questionnaires indicating their permission to
be part of the study. Respondent will also be
guaranteed of privacy and confidentiality of
data. There will be no recording of names or
any personal identification during interviews
and online questionnaires data collection
which will be conducted individually in the
private and quiet rooms in their respective
appropriate area without access to outsiders
and data will be analysed in aggregate.
Ethical approval will be also sought from a
recognized ethic body: The School Research
Ethics Committee (SREC) under School of
Education Department of Library and
Information Sciences the University of
Zambia. Furthermore, the researchers will
watch over the proposed research
methodology that will be conducted
throughout the study. This means that there
will be no alteration of the research findings
because they aim at satisfying the
researcher’s views.
6.1 Privacy
Personal information: The system will
ensure that the student’s personal information
will only be available to themselves and their
intended instructor, it will also ensure that it
has a comfort within the system so as to instil
appropriate privacy and behavior [2]. The
database will be allowing the lecturers to see
all the documents that the students have
submitted, as proof of the reason to why the
student did not write the assessment, these
details may be sensitive therefore it can only
be seen by the lecturer, and even so, the
lecturer is only allowed to view that as proof,
and not having authority to use it in any way
it was not intended to.
6.2 Accessibility
The platform will be made in such a way
that, it will be able to allow the lecturers to
choose the information they want to access
and the way they want to access it, either
some documents provided can be
downloaded or they can just be viewed in the
view mode. However to the manager of the
journal sometimes difficult to get a
researcher who would put his paper into the
journal he manages. Meanwhile, with the
number of journals that have been online,
researchers will find it difficult to get
information from the journals. Researchers
should open their journal entries, read their
profiles and publications, until they are
interested to include papers in the journal.
Moreover to ensure easy access to
information with an online journal aggregator
system, a software development method is
needed that directly captures the needs of its
users.
6.3 Accuracy
The student's personal information and
documents should appear in the database in
the same way they were submitted by the
student. If any errors along the way arise, the
student will have to resend the request to the
lecturer which The Gantt Chart will clearly
show the timeline of the project as well as key
milestones and timelines, The online journals
aggregator system takes the concept of a web
portal that will be a meeting system between
journal managers, journal, researchers and
general public. It will facilitate the journal
managers to be able to promote the journal
managers, inviting potential researchers to
include their research article, and journal
transactions inside it. For the researcher,
online journal aggregator system will be a
means to choose, like and keep journals that
are considered according to the scientific
field, so it will facilitate researchers to obtain
information related to the journal. As for the
general public, the online journals aggregator
system will provide search facilities in
journals, articles and authors in the same
system.
6.4 Cybercrimes
6.4.1 Hacking: breaking into the system
with malicious software
To prevent these threats, the web service will
be censored to allow fair use for authorized
users and ensure that no one’s rights are
violated, the integrity of the data is preserved.
Most of this is covered by the evaluation sub
section for under procedures and methods.
By heavily testing the repository as it is built
and this will ensure that the student or any
other user can only access the information
provided through the logging in into moodle
which holds the link for the webservice
journal aggregator.
7.0 PROJECT MANAGEMENT
7.1 Work Distribution
The project will be distributed among the
group members according to interest and
ability. Our system consist of three
components and our work allocation will be
building all systems components together due
to inexperience team members. The group
members however will be involved in all key
tasks in some form of either responsibility,
accountability, consultancy or informative as
shown in the fig A.1
7.2 Deliverables
 Project proposal document
 Proposal presentation
 Project website
 Prototype
 Project report
7.3 The Gantt chart will clearly show the
timeline of the project proposal as well as the
key milestones and timelines, shown in fig
A.1 in the Appendix
7.4 Activity Network Diagram
The Activity Network Diagram will
accurately show the flow of tasks required to
complete the project in proper time, as shown
in Fig A.4 in Appendix A
7.5 Risks
There are several risks associated with the
journal aggregator project and table A.5 in
Appendix provides a summary of them
together with their mitigation strategies.
7.6 Timeline
The project timeline for the aggregator
system project beginning from 9th March and
ending on 15 November is depicted in fig A.3
in Appendix
8.0 ANTICIPATED OUTCOMES
As our project is cantered at accessing
information from different sources. The
following are the key expected outcomes
 Efficient and faster access of précised
information.
 Make the submission for proof when
requesting authenticated source of
information
 Eliminate face-to-face appointments
for interactions with lecturers.
 System gives more satisfaction to
users and increases the usefulness of
the system itself because since the
beginning the user has been involved.
The main key to the success of system
design using the method is to develop
a harmonious proximity between
system developers or programmers
with users, in order to obtain the
actual needs and desires of the user.
For systems that require precision and
high accuracy, collaboration is
required with other software
development methods so the
perspective is used as a benchmark in
system design not only from the user
side only.
REFERENCES
[1] Ball, David 2006. The Place of
Universities in the Information Value
Chain. URL (last checked 15 May, 2021
http://www.iatul.org/conference/proceedings/vol11/papers/Ball/Ball.htm

[2] Brunell, David H. 1997. Library

Networking and Cooperation in 1996
In The Bowker Annual Library and
Book Trade Almanac 1997 (New
Providence, N.J.: R.R. Bowker, (1997).

[3] Case, Mary M. 2001. Trends and Issues

In Implications of Aggregate Subscriptions
To Electronic Journals, EBSCO Information
Services, Vantage Point Series, no.55
(Jan/Feb/March 2001).

[4] Hickey, Thomas B. 1995. Present and Future

Capabilities of the Online Journal, \Library
Trends 43: 528-543.

[5] Inger, Simon 2001. The Importance of

Aggregators, Learned Publishing,
Vol.14, No.4, October, pp. 287–290.

[6] Monroe, William S. 1997. The Role of

Selection in Collection Development: Past,
Present, and Future” in G.E. Gorman and
Ruth H. Miller, eds., Collection Management
For the 21st Century Westport, CT: Greenwood
Press, 1997.
 Appendix
Fig A.1 Work Breakdown Structure

Fig
A.2 RACI Matrix
Fig A.3 Gantt chart

Fig A.4 Activity Network Diagram

 Fig A.5 Risks

Risks Probability Consequence Mitigation Management

High
Lack of communication The project is likely Find out what the Team meetings should be
Among group members to fall behind the major cause is and held as soon as lack of
schedule work on it communication is
detected.
Lack of knowledge on the tools to be High Consult some
used The project could individuals with Try finding other tools
Designing the system result into failure. knowledge on how with which majority of
tools are used. the team members are
familiar.
Poor management of Low The project is likely Ensure that all Ensure that every team
Time by the team fall behind the schedules and time member is allocated a
scheduled time. are adhered to. part of the task.
Conflicts arising between the Low The project may Each team member Consult some individuals
members of the team result into failure. should ensure to not part of the team to
consult each other. supervise the team.

Time wasted on identifying the tools High The project is likely Avoid using If possible, work on the
to be used instead of working on the to fall behind the complex tools. reduction of the project’s
project. anticipated time. scope.

Very high May result into Hold a meeting to discuss

Shortages of resources to buy data failure of the project Ensure how this challenge can
for communication since there are if persists. communication be curbed.
no physical meetings whenever
resources are
available.