E-Tutoring

ROLE-BASED SYSTEM

Name: Wongani Msiska

| Enterprise Web Software Development |
9, 2019
Greenwich Course Leader: Mr Matthew Prichard
Course: COMP1640
Banner ID: 001074104
Zambia Centre for Accountancy Services
Lecturer: Mr. Billy Kahoota
URL to our video:
URL to our site:

Usernames and Passwords

Credentials
User Username Password
Administrator Admin Admin
Student Wmsiska 12345
Tutor Audreym 12345
Staff Chris 12345

Team Name: SWACK

Team Member Greenwich ID Role

Synod Phiri
Wongani Msiska 001074104
Audrey Mubambasu
Chris Kaluba
Kelvin

DONE BY WONGANI MSISKA 1|PAGE

TABLE OF CONTENTS
Abstract
Introduction
EVALUTION OF PRODUCT AND PROCESSES
Evaluation of Product
Individual Evaluation
Group Evaluation
Methodology
EVALUATION OF TEAM
B.1.1 Inappropriate high-level requirements
B.1.2 High-level requirements
B.2.1 MoSCoW Prioritization
B.2.2 MoSCoW Prioritization Justification
SELF-EVALUATION
Data Controller Role
BCS Code of conduct
Summary
Reference
CONCLUSION
REFERENCES

ABSTRACT
Modern times have shown an increase in demand for automated system to be used in our
higher learning institutions. These systems have erased the disadvantages that came with
manual systems such as paper work that became cumbersome for processes to be done on

DONE BY WONGANI MSISKA 2|PAGE

time and on demand. As a result of this the old way of processing resulted in low
productivity and frustration on the client side. Now the question is why their demand for
our high-learning institutions to have computerized system? It is to enable them to be
productive in delivering high quality service.

INTRODUCTION
The University would be pleased to have a role-based etutoring system which will
enhance collaboration between tutors and its students. A role-based system would be
ideal for the university because it will provide a restricted access to each user created on
the system. Knowing that this is a large university, a role-based system will provide
administrative security through assigning privileges to users. Prior to developing this
system, the group had to use a development methodology such as agile SCRUM.

Why use agile SCRUM?

One of the benefits the university will get from this kind of approach is the reduction on
money and time spent.
According to research “Scrum is part of the Agile movement. Agile is a response to the
failure of the dominant software development project management paradigms (including
waterfall) and borrows many principles from lean manufacturing. In 2001, 17 pioneers
of similar methods met at the Snowbird Ski Resort in Utah and wrote the Agile
Manifesto, a declaration of four values and twelve principles. These values and
principles stand in stark contrast to the traditional Project Manager’s Body of
Knowledge (PMBOK). The Agile Manifesto placed a new emphasis on communication
and collaboration, functioning software, team self-organization, and the flexibility to
adapt to emerging business realities.” Michael James (2017). Scrum Methodology
[Online] Available at: http://scrummethodology.com/ [Accessed 24th October 2019].

DONE BY WONGANI MSISKA 3|PAGE

EVALUATION OF PRODUCT AND SERVICES

Product Evaluation

The E-Tutoring system that has been developed will help the university speed the process
of reporting, increase effective communication between students and lecturers.

 Security:

The E-Tutorial portal has a logout button on all pages that will remove the session
variable and return to the login screen. Furthermore, where a user tries to put in a wrong
password the system will validate the inputs using JavaScript and show the user that their
input is wrong.

 Improved communication:
Screenshot 1.1

DONE BY WONGANI MSISKA 4|PAGE

The above screenshot shows that dashboard of the student Wongani Msiska after login.
A broadcast message was sent by the tutor indicating the what the student should do. This
way of communicating is effective as the student doesn’t have to waste time to go to the
lecturer’s office or check on the notice board for any announcements.
 Database Approach
The system shows how much privileges the administrator has, for example the ability to
activate an account and use the email address as key. As soon as the students account is
created, an email notification is sent. Other than that, the administrator and the student
can update details on the database about their accounts.
 Meeting Requirements:
The product when tested did meet the requirements that where presented.
 User Interface:

 Scrum Methodology:
With the use of the above approach, the group performed daily scum meeting that did not
last more than 15 minutes. The purpose of these meeting was to make all members aware
of any impediments, progress of tasks and pending tasks. These meetings helped plan-
ahead and this was measured by inspecting the progress made since the last meeting. On
a brighter note, there was more communication amongst the group through chatgroups on
application such as WhatsApp, on any changes or progress made. Below where the high-
level objectives which were discussed.
1. Was the discussion in the previous meeting profitable in meeting the development
objective spring?
2. What was to be done to help achieve the development goal?
3. Did the group see any hinderances to the development of the objective?
In the group the scrum master ensured that all members participated and made us aware
that the meeting should not last 15 minutes. The master also highlighted how beneficial

DONE BY WONGANI MSISKA 5|PAGE

the meeting would help in improving communication, identify and make sure that the
obstacles where removed from our development process.
Through out this process, the scrum methodology was applied and the result of this is a
work e-tutoring system.

EVALUATION OF TEAM
Group Evaluation
1. Synod Phiri:
- Attitude: Synod Phiri was had a positive attitude as he would always make
himself available for team meetings. If at any time he was tied up, he would
communicate via phone or on the WhatsApp platform.
- Teamwork:
- Technical Ability:
- Overall Evaluation:
- Score: 7/10
2. Audrey Mubambasu:
- Attitude: Audrey Mubambasu had slow start understanding the importance of
working in a group and the methodology we were using. She would make it to
meetings occasionally and would rarely update the team on how much
progress was made. Therefor her attitude was not in the right place for this
development process.
- Teamwork:
- Technical Ability:
- Overall Evaluation:
- Score: 4/10
3. Chris Kaluba:
- Attitude: Chris Kaluba brought so much energy to the team with his positive
energy and encouragement. He took it upon himself to call all members of the
team to inform them about the meeting we were to attend.
- Teamwork: He always participated in the discussion group and had ideas and
good suggestions. He didn’t reject the criticism that the group brought out
during discussions. Above all he never dominated during the group studies but
gave chance to other members to share their thoughts as well.
- Technical Ability:
- Overall Evaluation:
- Score: 9/10
4. Kelvin:
- Attitude: Kelvin on the other hand did not show much urgency to making the
team understand the methodology we were to use, but he showed commitment
to attending most meetings and would be willing to ask questions on things he
did not understand.
- Teamwork:

DONE BY WONGANI MSISKA 6|PAGE

 - Technical Ability:
- Overall Evaluation:
- Score: 5/10
5. Wongani Msiska:
- Attitude:
- Teamwork:
- Technical Ability:
- Overall Evaluation:

SELF-EVALUATION
Prior to developing the e-tutoring system, I came with the knowledge of PHP, JavaScript,
SQL and HTML. I had to apply the scrum methodology, it took me about 3 weeks to
understand and apply its principles to the development process. As a result, I managed to
ensure that most requirements were met under the role I was given by the group. In my
first role, I was the web designer.

Lessons Learned
After completing the project, I gained the knowledge about the importance using a
methodology such as agile scrum for development. About software development, I
learned that if you have a working software that meets all requirements, its more valuable
than documentation. At the core of development is constant collaboration between the
team and the owners of the project. Overall our response to change is more important
than following a plan.

Conclusion
In this project we have applied the Scrum Agile development methods, after the project is finished I
have a very positive conclusion for this method, it is exactly what we study. This method helps us
to ensure the completion of projects on time, to satisfy requirements of the project through early
and continuous delivery, the members work together and check the progress of meeting weekly,
award decide which changes regularly. We completed the project to ensure the requirements of the
project.

Especially when applying this method, we learned so most things, discussion skills, problem
solving, team work skills, teamwork skills are always important, it is an important factor when
project development.

In the future we will upgrade and develop a better system

DONE BY WONGANI MSISKA 7|PAGE

References

DONE BY WONGANI MSISKA 8|PAGE