Final Project Report: Broadcasting System - CS6P05 Project

This project report details the development of a broadcasting system designed to improve communication and management within an organization. The system, a desktop application with a back-end database, facilitates interactions between managers and staff. It includes features like user login portals for both managers and staff, staff signup, meeting scheduling, and the uploading of training materials. The report covers requirements analysis, software design (including user interface and database structure), implementation, testing, and evaluation of results. The project aims to enhance organizational efficiency and staff engagement through effective communication channels. The methodology involved requirement analysis, SRS document drafting, functional and non-functional requirements determination and the use of a project management plan with amendments. The system is intended to streamline administrative tasks and provide a platform for staff feedback and access to learning resources.

Running head: BROADCASTING SYSTEM 1
CS6P05 Project
BROADCASTING SYSTEM
Project Report
Final Submission
Name: Add your Full name
ID Number: Your ID number
Date: Sunday, 01 September 2024
First Supervisor: Add Your Supervisor’s Name Here
Second Supervisor: Add Your Second Marker’s Name Here
1.1.1

BROADCASTING SYSTEM 2
Declaration
Module: CS6P05 Deadline: 3pm Monday 7th January 2019
Module Leader: Student ID: ________________________

BROADCASTING SYSTEM 3
PLAGIARISM
I have read and understood rules and regulations concerning plagiarism as provided in the
extract below.
Student signature: ______________________ Date: 01/09/24
Extracts from University Regulations on Cheating, Plagiarism and Collusion
Section 2.3: "The following broad types of offence can be identified and are provided as indicative examples…
(i) Cheating: including taking unauthorised material into an examination; consulting unauthorised material
outside the examination hall during the examination; obtaining an unseen examination paper in advance of
the examination; copying from another examinee; using an unauthorised calculator during the examination
or storing unauthorised material in the memory of a programmable calculator which is taken into the
examination; copying coursework.
(ii) Falsifying data in experimental results.
(iii) Personation, where a substitute takes an examination or test on behalf of the candidate. Both candidate
and substitute may be guilty of an offence under these Regulations.
(iv) Bribery or attempted bribery of a person thought to have some influence on the candidate's assessment.
(v) Collusion to present joint work as the work solely of one individual.
(vi) Plagiarism, where the work or ideas of another are presented as the candidate's own.
(vii) Other conduct calculated to secure an advantage on assessment.
(viii) Assisting in any of the above.
Some notes on what this means for students:
1. Copying another student's work is an offence, whether from a copy on paper or from a computer file, and
in whatever form the intellectual property being copied takes, including text, mathematical notation and
computer programs.
2. Taking extracts from published sources without attribution is an offence. To quote ideas, sometimes using
extracts, is generally to be encouraged. Quoting ideas is achieved by stating an author's argument and
attributing it, perhaps by quoting, immediately in the text, his or her name and year of publication, e.g. "e
= mc2 (Einstein 1905)". A references section at the end of your work should then list all such references
in alphabetical order of authors' surnames. (There are variations on this referencing system which your
tutors may prefer you to use.) If you wish to quote a paragraph or so from published work then indent the
quotation on both left and right margins, using an italic font where practicable, and introduce the quotation
with an attribution.

BROADCASTING SYSTEM 4
Abstract.
Good communication is an essential tool in achieving productivity and maintaining strong
working relationships among managers and staff in an organisation (Kanki, 2019). An
organisation that focuses mostly on delivering clear and effective communication builds trust
among employees, and this boosts their morale as well as increasing productivity and output
(Bendell, 2017). In cases where an organisation has poor communication things always turn
out as unexpected, this may include staff losing morale, poor management and this sums up
to poor quality for such an organisation. Effective communication requires that both the
managers and staff are strong communicators. When managers are strong communicators,
they are able to handle and manage their staff effectively (Bryson 2017). The same applies to
staff who communicate effectively; this includes giving feedback or complaints, by so doing,
the managers get to know the staff’s opinions and act on them appropriately. The goal of the
project discussed in this report is to build a broadcasting system that will ensure that
managers and staff communicate with each other in a much more effective manner. The
broadcasting system is a desktop application that consumes a back-end database that manages
and stores data related to the system. The system has a login page for both the manager and
staff. During installation, the manager, the admin, in this case, is issued with a manager ID
and password stored in the back-end database. Upon the manager’s login, they get a redirect
to the admin portal where they can sign up the staff who can then access the staff portal after
login using credentials created for them by the manager. Other than staff sign up the
manager, schedules meetings, uploads learning and online training materials and views
feedback and complaints submitted by the staff. On the other hand, the staff can view
learning and online training materials uploaded by the manager and also sends complaints
and feedback from the staff portal.

BROADCASTING SYSTEM 5
Table of Contents
Declaration.................................................................................................................................2
Abstract......................................................................................................................................4
Table of Contents.......................................................................................................................5
List of Tables..............................................................................................................................7
List of Figures............................................................................................................................8
Chapter 1: Introduction..............................................................................................................9
1.2 Project topic and rationale................................................................................................9
1.3 Project Aims and Objectives............................................................................................9
1.4 Methodology...................................................................................................................10
1.5 The report structure........................................................................................................10
Chapter 2: Background Research.............................................................................................11
2.1 Literature review of related work...................................................................................11
2.2 Critical evaluation of related products...........................................................................11
2.3 The scope of the project.................................................................................................12
2.4 Review and justification tools selected for use in the project........................................12
Chapter 3: Requirements Analysis and Specification..............................................................14

BROADCASTING SYSTEM 6
3.1 Functional requirements:................................................................................................14
3.2 Non-functional requirements..........................................................................................14
3.2.1 Performance requirements.......................................................................................14
3.2.2 Software system attributes.......................................................................................15
Chapter 4: Software Design.....................................................................................................16
4.1 User Interface Design.....................................................................................................16
4.2 Database tables structure design.....................................................................................21
4.3 System Architecture.......................................................................................................22
4.4 Detailed software class design........................................................................................23
4.5 Use cases realization.......................................................................................................24
Chapter 5: Implementation and Testing...................................................................................26
5.1 Software Implementation...............................................................................................26
5.2 Software Testing or Analysis of the results....................................................................26
Chapter 6: Evaluation of Results..............................................................................................28
Chapter 7: Conclusions............................................................................................................29
7.1 A summary of what has been achieved in the project....................................................29
7.2 Reflections and lessons learned......................................................................................29
7.3 Future work....................................................................................................................29

BROADCASTING SYSTEM 7
Appendices...............................................................................................................................30
Appendix A: Project Management.......................................................................................30
1.1 The original project plan from the Proposal..........................................................30
1.2 Review of your project process.............................................................................32
1.3 Amendments to the original plan...........................................................................32
1.4 Lessons learned in project management................................................................33
References................................................................................................................................34
Bibliography.............................................................................................................................37

BROADCASTING SYSTEM 8
List of Tables
Table 1: Project plan from proposal.........................................................................................30
Table 2: Project milestone........................................................................................................32

BROADCASTING SYSTEM 9
List of Figures
Figure 1: Login page of the software.......................................................................................16
Figure 2: Admin portal of the software....................................................................................17
Figure 3: Sign up for staff........................................................................................................18
Figure 4: Staff portal of the software.......................................................................................19
Figure 5: Feedbacks page of the software................................................................................20
Figure 6: Database tables structure design...............................................................................21
Figure 7: System Architecture of Desktop Application...........................................................22
Figure 8: class diagram of the broadcasting system.................................................................23
Figure 9: Use case diagrams....................................................................................................24
Figure 10: Use case Realisation...............................................................................................25
Figure 11: Revised Gantt chart................................................................................................32

BROADCASTING SYSTEM 10
Chapter 1: Introduction
1.2 Project topic and rationale
The idea behind the project is to improve on an organisation’s broadcasting system to enable
better planning and efficient management within the organisation. Arguably communication
contributes a lot to the success running of any organisation. Organisations and businesses that
employ an effective mechanism for communication more likely achieve their objectives in
due time. It would be right to say that communication contributes greatly to increased job
satisfaction among employees as well the easier management by the managers. Therefore it is
a an essential consideration for any business or organisation to employ effective
communication channels to see to it that the organisation run smoothly so as to attain the set
goals for the same organisation. The broadcasting system discussed in this report is a desktop
application with a back-end database that manages and sores data through the system.. The
system will comprise of two users, the manager and staff. The manager will carry out
administrative roles, such roles will include; signing up of new staff, scheduling meetings for
various purposes, adding resources such as online trainings and learning material. What is
more, he will be able to access feedbacks and complaints submitted by the staff from the staff
portal. On the other hand, when a staff logs in the system they will be able to access learning
materials via the system. This is only possible after the manager has signed the staff with a
staff ID and password that the staff uses when logging in. The two coordinate through the
system to see to it that they communicate effectively for the smooth running of the
organisation.

BROADCASTING SYSTEM 11
1.3 Project Aims and Objectives
The projects aims and objectives were as follows.
I. First aim is to develop the broadcasting system. The objectives for this are that this
system must have the desktop application with the back-end database that manages
and stores data through the system this plan to develop this project should craft out as
the guideline.
II. The second aim is to ensure about the security of this system. The objectives for this
are that the manager of the organization will have administrative authority and the
staff will be able to watch all activities that is uploaded by manager only when he
approves these staff to system. The manager serves as the admin of the system and
therefore staff only accesses only what they are authorised to access by the manager.
III. Third aim for this is to allow different staff members for using this system. The
objectives are that the manager will add staff members in this system and after that
they will be able to access the online trainings and learning material. The staff does
this by signing up staff where they upload information about the staff in the system.
Among the uploaded staff information is a staff ID and password that the staff uses to
log in the system.
1.4 Methodology
Described below was the methodology used.
A requirement analysis was carried out after which an SRS document for the broadcasting
system was drafted. Several issues were addressed during this phase, that included what kind

BROADCASTING SYSTEM 12
of problem we are solving, why is it important, why choose the solution we are offering, data
inputs and output through the system, likely complexities to be dealt with and other external
software and hardware required to interface with the system to be developed. It after this that,
functional requirements, non-functional requirements and goals of the system are determined.
The three properties are then given well description in the SRS document. Functional
requirements included admin and staff login and the portal each lands to after login. Non-
functional requirements included performance requirements and software system attributes.
The system design was then drafted. During system design, UML diagrams for the flow of
the project were to be derived, more to that use case diagrams were drawn to clearly show the
functionalities of each actor in the system. That’s roles for both the manager and staff in the
system were clearly represented. More to these, mock-ups showing the various system
interfaces were drawn to visualise the way the system will appear like after implementation.
The architecture of the broadcasting system was also drafted to fully understand the
functionality and roles of each component in the system. That include the system itself, the
backed server, the cache database and the database itself. Class diagrams were also derived
during this phase so as to determine classes to be used through the system, their attribute and
functionalities each class will be require to carry out. Further a detailed class system design
was derived for visualisation of every component in the system together with the roles they
play and how they relate to each other. Database tables were also designed to determine
entries for each database entry as well as their primary and other keys associated with the
database entries. This made it possible for database creation within the PhpMyAdmin server
on Xampp during the implementation stage. The system was then to be implemented, in this
phase the system is implemented and tested to find out whether it fulfils its requirements as
started earlier in the SRS document. It is during the implementation stage that various
software to be used as well the preferred technologies to implement the system are identified.