2019

BANNER ID: 001085680

STUDENT NAME: Ronald Fred Sikwese

COURSEWORK TITLE: Information and Content Management (Coursework 2)

COURSEWORK CODE: COMP1643

COURSEWORK LEADER: Pradeepan Manickam

CENTER NAME: NACIT Blantyre Campus (Blantyre, Malawi)

Group 2 Team Members

Member Name Role

Ronald Fred Sikwese (Self) Project Manager
Clement Makowa Quality Assurance Manager
Evah Simbeye Designer
Tony Kansilanga Developer
Leon Kachimanga Developer
Allen Kaluwa Tester

Links

The username and password to access the repository and team site are included:

username rs5706v@gre.ac.uk
password Greenwich@13021999
Group repository https://uogcloud.sharepoint.com/sites/Group2Repository-
H-CAM/Shared%20Documents/Forms/AllItems.aspx
Team Site https://uogcloud.sharepoint.com/sites/G2B
Presentation screencast https://youtu.be/5F-QQCnNizc
Functionality screencast https://youtu.be/X27ma7KxaII
Table of Contents
Introduction ..................................................................................................................................... 2

1 – Evaluation of product and process ....................................................................................... 3

1.1 – The product ................................................................................................................... 3

1.2 – The Process ................................................................................................................... 8

1.2.1 – Analysis.................................................................................................................. 9

1.2.2 – Design .................................................................................................................... 9

1.2.3 – Development .......................................................................................................... 9

1.2.4 – Testing.................................................................................................................... 9

1.2.5 – Documentation .......................................................................................................... 10

2 – Evaluation of team ............................................................................................................. 11

2.1 – Clement Makowa ........................................................................................................ 12

2.2 – Tony Kansilanga ......................................................................................................... 12

2.3 – Allen Kaluwa............................................................................................................... 12

2.4 – Evah Simbeye.............................................................................................................. 13

2.5 – Leon Kachimanga ....................................................................................................... 13

3 – Self-evaluation ................................................................................................................... 14

Conclusion .................................................................................................................................... 15

References ..................................................................................................................................... 16

Page 1 of 16
Introduction
This report is going to cover an evaluation of the team site and the process it took in the
developing it. Each group 2 team member is going to be evaluates as well as a section of self-
evaluation on the performance towards building the team site.

Page 2 of 16
1 – Evaluation of product and process
1.1 – The product
The navigation

The top navigation of the team site has been made exactly to mimic that of BBC itself. Though
due to space it does not display all of the links on it. Such as the drop-down list where TV and
Weather exist are nested on the ellipses after the Future tab.

Figure 1: Team site top navigation

On the other hand, the bottom navigation does not contain all the is on BBC itself, it contains
minimal items at most.

Figure 2: Team site bottom navigation

The homepage

The homepage of the team site contained an imitation of the real site links to several pages can
be accessed from. There user will get a glimpse of articles that are found under different topics

Figure 3: Site homepage

Page 3 of 16
Figure 4: More articles on the homepage

Figure 5: Weather on the homepage

Programming

The only thing the user can do on our programming page is to view the scheduled programs.
There is no feature that supports the admin to add programs to the page of the team site

Figure 6: Page for scheduling programs

Page 4 of 16
Weather

The BBC site displays a globe as a summary of temperatures in different cities. Our team site
uses Microsoft MSN to read weather in those different location displaying it in tabular form
instead of the graphical globe.

Figure 7: Weather forecast

Complaints

The contact page replicates that of BBC, and to file a complaint you click the button that says
Make a Complaint.

Figure 8: Team site contact page

Page 5 of 16
Using a webpart called Microsoft Forms, we were able to provide radio buttons that a user can
use to choose a category of their complaint and a text field to describe the complaint in details.
The forms also support if the user wishes to make an enquiry.

Figure 9: Complaint form 1

Figure 10: Complaint form 2

The admins of the site are able to view the responses that a user has filed.

Page 6 of 16
Figure 11: View site responses

Workflows

A few attempts were made to create the workflows, but upon creation they seemed not to
function later on. I did not understand how to add workflows to the SharePoint site.

Most of the colors were achieved on the site but SharePoint offered limited customization
towards the team site created. With the majority of the web parts within SharePoint, we were
able to create a BBC look alike site. The web parts offered ease of adding content to the site and
adding some functionality such as the sending of complaints.

Page 7 of 16
1.2 – The Process
The processes to develop the site inherited the Software Development Life Cycle (SDLC). It
makes use of phases that are used to create software that meet a user’s objectives (Alwan, 2019).
Planning involves finding out what must be done and the problems the product will solve. In
analysis, the user’s requirements are gathered. Design involves making prototypes of the product
by showing what it will look like and how it’ll function. Implementation and Deployment
produces a working product that is placed in a live environment. Testing will involve putting the
system up to challenges to see how it performs to tasks. Finally, maintenance is all about making
changes to the product if any issue rises (Alwan, 2019).

Therefore, taking these phases into consideration, the Gantt Chart below shoes the process that
occurred when the site was being developed.

Figure 12: Team Gantt Chart (1)

Page 8 of 16
Figure 13: Team Gantt Chart (2)

1.2.1 – Analysis
We produced a document, “ANALYSIS SPECIFICATION” that contains user requirements for
the site. The functionalities were obtained from the scenario. There were no further
functionalities added by the team and no problem was faced under this phase.

1.2.2 – Design
A prototype of the team was made to give the developers an idea of what the product was to look
like and function. However, the design phase had taken longer than we had planned because it
took some 2 days from the Development phase time.

1.2.3 – Development
Adding workflows to the site was not an easy task. Two attempts have been made to try and
configure workflows but it still isn’t working as planned. Adding the feature of sending
complaints and enquiries was figured on the last of development, the future was almost left out.

1.2.4 – Testing
The “Test Plan” document contains the approach used for the planning stage. The QA Manager
and Tester had a major role playing in this part. The “Test Log” has a detailed description on
how the testing went. As mentioned earlier, once the workflow was configured it work for the
first few attempts. After time passed, the feature seemed not to be responding as planned.

Page 9 of 16
1.2.5 – Documentation
The only documentation that has been produced are the individual reports. The other two
documents were not produced due to the time the team has remaining.

Page 10 of 16
2 – Evaluation of team
Below is a table showing a breakdown of every team member:

Criterion Weight Team Members

Ronald Clement Tony Allen Evah Leon
Contribution 15% 10 10 10 8 8 6
Punctuality 5% 8 10 10 6 8 6
Attendance 10% 10 10 8 6 8 4
Communication 10% 8 8 8 8 8 6
Dependability 10% 10 10 10 8 6 6
Decision making 15% 10 8 10 8 6 8
Collaboration 15% 10 10 10 8 8 8
Initiative 5% 10 8 8 6 6 4
Innovative 5% 8 8 10 6 6 8
Commitment 10% 10 10 10 6 10 4
TOTAL 100% 9.6 9.3 9.5 7.3 7.5 6.2

Figure 14: Bar graph of team evaluation

Page 11 of 16
Figure 15: Team members grading

Below is commentary on each individual member:

2.1 – Clement Makowa

Clement was the QA Manager responsible for testing and making sure every document was up to
par. There were few occasions where we worked hand in hand with Allen Kaluwa when it came
to producing the Test Plan and Test Log. His performance was much appreciated and he really
put a lot of effort in the group work.

2.2 – Tony Kansilanga

Tony was the most performing developer in the group. He could be entrusted with tasks and
handle them with much ease. His creativity helped develop most of the site’s interface and
functionality.

2.3 – Allen Kaluwa

Allen set a very meaningful test plan with the supervision of Clement Makowa. He wrote a Test
plan that was impressed by the group members. Though on few occasions he missed some group
meetings of which his appearance was needed and reported late on two occasions.

Page 12 of 16
2.4 – Evah Simbeye
Evah was in-charge of designing the prototype that was to be used in developing the team site.
She was a bit troubled in using Axure, the software that was agreed to be used for prototyping,
and had help from Clement and I.

2.5 – Leon Kachimanga

Leon had time to shine when giving in ideas on the team site, but reported late on majority of
meetings and also didn’t show up on some. His role as a developer was not that satisfactory.

Page 13 of 16
3 – Self-evaluation
This section will contain commentary on my own performance and contribution to the team site.

As the project manager, I had to make sure every group member was at peak with the tasks left
in their hands. I provided decent information towards the group. Even though the information
was provided the group was there to help get it refined. When it came to designing, gave
minimal information towards the prototype. I mainly participated in the development of the site
by created the weather and about pages, and also the functionality of sending inquires and
complaints. Towards testing, I did not contribute much but I was there to view what had been
done by colleagues.

I would classify my performance to be above average. It was not excellent because I did not
make in on time on two group meetings. That does not reflect good leadership skills. However, I
managed to keep the group intact and made sure each member could participate and show their
potential.

Over the course of the group assessment I have acquired leadership knowledge and gained
collaborative skills that are a necessity in a team. Leading a team is tough because of different
characteristics possessed by each member. However, it can stressful to work with some
teammates that do not look for challenges.

Page 14 of 16
Conclusion
The group succeeded to produce a site with a nice user interface and some functionality even
though some aspects of the site did not meet all the requirements for the coursework. If we were
allocated more time, the team would look into adding themes on the SharePoint site to create a
better user interface. Paying for SharePoint subscriptions would have enabled full control in the
site because the version used in this coursework had limitations, to name one; only people within
the organization are permitted to view the site as a visitor.

Page 15 of 16
References
Alwan, M., 2019. What is System Development Life Cycle?. [Online]
Available at: https://airbrake.io/blog/sdlc/what-is-system-development-life-cycle
[Accessed 16 November 2019].

Page 16 of 16