MARCH 27, 2023

REQUIREMENT MANAGEMENT
COURSEWORK
COMP1787 (2022/2023)

Student Name: Nguyen Duc Quang

Student ID: 00132718

Instructor: Micheal Omar

SUPERVISOR
MICHAEL OMAR
Greenwich University Vietnam
TABLE OF CONTENTS
LIST OF TABLES-------------------------------------------------------------------------------------------------------------------------------- 2
LIST OF FIGURES------------------------------------------------------------------------------------------------------------------------------- 2
SECTION A-------------------------------------------------------------------------------------------------------------------------------------- 2
INTRODUCTION----------------------------------------------------------------------------------------------------------------------------------2
THE TECHNICAL MODEL-------------------------------------------------------------------------------------------------------------------------2
SECTION B--------------------------------------------------------------------------------------------------------------------------------------- 3
HIGH LEVEL REQUIREMENTS ANALYSIS AND MOSCOW PRIORITISATION TOOLS:------------------------------------------------------------3
Project management Tools---------------------------------------------------------------------------------------------------------- 3
Evidence of Project management tool used-------------------------------------------------------------------------------------3
Agile project management---------------------------------------------------------------------------------------------------------- 4
FACILITATED WORKSHOP (MEETING)----------------------------------------------------------------------------------------------------------4
Planning communication------------------------------------------------------------------------------------------------------------ 5
Timebox guidelines.------------------------------------------------------------------------------------------------------------------- 5
B1: IDENTIFICATION OF REQUIREMENTS----------------------------------------------------------------------------------------------- 5
DOCUMENTING REQUIREMENTS.---------------------------------------------------------------------------------------------------------------5
Functional requirements:------------------------------------------------------------------------------------------------------------ 5
Non-functional:------------------------------------------------------------------------------------------------------------------------ 5
Gathering User requirement.------------------------------------------------------------------------------------------------------- 5
B2: REWRITE, AND ADD TO, THE LIST TO END UP WITH A TOTAL OF 8-10 ‘UPDATED’--------------------------------------5
B3: MOSCOW TECHNIQUE APPLIED APPROPRIATELY TO PRIORITISE THE REQUIREMENTS-------------------------------6
Discuss MosCow teschnique-------------------------------------------------------------------------------------------------------- 6
EXPRESSING REQUIREMENTS AND DESIGN WITH MODELS------------------------------------------------------------------------7
CAPTURING DESIGN-------------------------------------------------------------------------------------------------------------------------- 7
Module description------------------------------------------------------------------------------------------------------------------- 7
Functional Design artefacts from UML------------------------------------------------------------------------------------------- 7
Relational Database design artefacts--------------------------------------------------------------------------------------------- 7
UI Design-------------------------------------------------------------------------------------------------------------------------------- 8
SECTION C--------------------------------------------------------------------------------------------------------------------------------------- 8
LSEPI-------------------------------------------------------------------------------------------------------------------------------------------- 8
(C1) the role of the Data Controller within the organisation----------------------------------------------------------------8
(C2) any legal, social, ethical, and professional issues that MV may be faced with------------------------------------8
Legal-------------------------------------------------------------------------------------------------------------------------------------- 8
Social------------------------------------------------------------------------------------------------------------------------------------- 8
Ethical------------------------------------------------------------------------------------------------------------------------------------ 8
Professional issues-------------------------------------------------------------------------------------------------------------------- 8
BCS CODE OF CONDUCT--------------------------------------------------------------------------------------------------------------------- 8
- Public Interest:----------------------------------------------------------------------------------------------------------------------- 8
- Professional Competence and Integrity:---------------------------------------------------------------------------------------- 8
- Duty to Relevant Authority:------------------------------------------------------------------------------------------------------- 8
- Duty to the Profession:------------------------------------------------------------------------------------------------------------- 8
(C2) provide one practical example from the case study that relates to each aspect of LSEPI-----------------------8
ASSUMPTIONS--------------------------------------------------------------------------------------------------------------------------------- 9
CONCLUSION----------------------------------------------------------------------------------------------------------------------------------- 9
REFERENCES (HARVARD STYLE)----------------------------------------------------------------------------------------------------------- 9
NOTE:-------------------------------------------------------------------------------------------------------------------------------------------- 9

List of tables
TABLE 1: FACILITATED WORKSHOP-----------------------------------------------------------------------------------------------------------------3
TABLE 2: CAPTURING USER REQUIREMENTS------------------------------------------------------------------------------------------------------4
TABLE 3: LIST OF FR AND UPDATED LIST----------------------------------------------------------------------------------------------------------4
TABLE 4: LIST OF NF AND UPDATED LISTS---------------------------------------------------------------------------------------------------------5
TABLE 5: MOSCOW PRIORITIZATION--------------------------------------------------------------------------------------------------------------5

List of figures
FIGURE 1: PROEJECT MANAGEMENT TOOL--------------------------------------------------------------------------------------------------------2
FIGURE 2: WBS AND GANTT CHART - AGILE-----------------------------------------------------------------------------------------------------3

Section A
Introduction
This section should consider the following components:
• Introduces the rationale and the business drivers of this project.
• To be written in third person
• Capture the reader's attention.

The Technical model:

Programming technologies and tools:
Technical model Type Tool Description
Programming Programming Html, css, JavaScript: is a flexible programming
technologies language javascript language that can run in many different
browsers, supports handling events on the
web, manipulating the DOM, and
performing interactive tasks with users
quickly. .

Framework React and RESTful React: is a JavaScript library for building

API for user interfaces, which helps to develop
communication single-page web applications efficiently,
with a database enables the reuse of components and
 improves the performance of the
application.

RESTful API: is a standard web API design

architecture that allows simple and
efficient transmission of data between
different applications and systems, and
supports standard HTTP methods and can
be used on many different platforms and
programming languages.

Web server Nginx Web server: Nginx is a popular web server

used for websites with medium traffic. It is
well extensible and customizable. Nginx
can run on many operating systems,
including Linux, Windows, and macOS.

Database MySQL server Database server: MySQL is a popular

server database management system used for
web applications. It has good extensibility
and security features. MySQL can run on
many operating systems, including Linux,
Windows, and macOS.

Technical Processor Intel Xeon Intel Xeon Platinum 8180 processor is

specifications Platinum 8180 ability to handle heavy tasks with high
reliability.
Memory 8GB RAM With 8GB of RAM, the system can meet
the needs of basic applications.
 Hard disk 500GB The storage capacity of the 500GB drive is
capacity enough to store basic data files.
Operating Windows Server Windows Server operating system is an
system operating system specially designed for
enterprise applications, with good
manageability and security.

Table 1: Programming Technologies

Managerial model:
AGILE METHODS :
According to Hamilton(2023), Agile methodology is a technique that encourages ongoing
testing and development throughout the project's software development lifecycle. As opposed
to the Waterfall methodology, the Agile model for software testing involves concurrent
development and testing.
The choice of Agile method for this project can be explained by the following reasons:
The Agile methodology allows the product development team to focus on creating real product
value that meets the needs of the customer. Customers often have constantly changing
requirements, and the Agile approach allows the development team to adapt to these changes
flexibly.
Agile helps to increase responsiveness and speed of product development. By using themes
(sprints) and short-term development cycles, Agile allows development teams to control
progress and create more stable software products.
Agile also helps increase transparency in the project, helping members of the product
development team understand the requirements, progress and goals of the project.
Finally, Agile also helps increase creativity and innovation. Product development teams are
encouraged to periodically come up with new ideas and solutions during product development,
making the product unique and better.
RAD and TIMEBOXING
Rapid Application Development, or RAD, is a flexible approach to software development that
places less of a focus on detailed design and more on experimentation and quick feedback. In
general, the RAD approach places more emphasis on prototyping and development than it does
on planning.
The following arguments explain why I used Rapid Application Development for this project:

- RAD facilitates quicker application development and deployment using methods like
prototyping and iterative development, which cuts down on development time and
expenses.

- In order to increase interactivity and consumer involvement, RAD enables customers

and stakeholders to take part in the development process and offer ideas and feedback
on the product.

- Rapidly adjust to changing requirements: RAD allows projects to quickly adjust to

changing requirements by using methods like timeboxing, which restricts the scope and
duration of development, and iterative development, which tests and evaluates
changes.

- RAD focuses on fundamental product functionality and aids in streamlining

development procedures to meet project objectives.

Iterative development using prototyping.

In this project, I use a RAD tool. It is iterative development using prototyping. The steps
involved in iterative development utilizing prototype are as follows:

- Determine the functional requirements and client needs.

- Create a basic design for the project system's user interface.

- Create a first prototype with few features.

 - Reviews and comments from clients and users to identify issues or suggest
improvements.
- Adapt, enhance, and expand the prototype in response to user feedback.
- To make sure that the system satisfies the needs of the customer and the necessary
functional requirements, iterate the development, change, and enhancement of the
prototype.

Figure 1: Iterative development using prototyping

Timeboxing:
According to Team(2022), timeboxing is a time management approach that restricts a task to a
predetermined (but realistic) timetable that, depending on the task complexity, may be
minutes, hours, days, or even weeks long.
I will apply time boxing to the this project which can be done as follows:
- Depending on the difficulty of the work in the backlog, each sprint has a time constraint
of 2 weeks.
- Team members gather to plan and assess the feasibility of completing tasks during each
sprint.
- The sprint's tasks must all be finished and satisfy the established quality standards.
- The team will hold a review and feedback session at the conclusion of each sprint to
assess its work and make adjustments for the following sprint.
- When some tasks are unable to be finished during the sprint, they are added to the
backlog to be finished during the following sprint.
The Chosen Method for development :

The primary reason why I chose Scrum as the method for developing the project is its flexibility.
Scrum is designed to accommodate changes in requirements and priorities, which is essential
for a project subject to change, as is the case with the project in question. The iterative
approach of Scrum ensures that the project is delivered in small increments, allowing constant
feedback and evaluation.

Another reason why I chose Scrum is that it is a highly collaborative approach to project
management. The Scrum team is cross-functional and self-organising, meaning that each team
member is responsible for a specific aspect of the project. The team members work together to
identify the requirements, create the product backlog, and prioritise tasks. This approach
encourages communication and collaboration, which is essential for the success of any project.

Furthermore, Scrum emphasises the importance of continuous improvement. At the end of

each sprint, the team conducts a retrospective, an opportunity to reflect on the progress made
during the sprint and identify areas for improvement. This approach ensures that the project
constantly evolves and improves, which is crucial for delivering a high-quality product.

In conclusion, Scrum is an excellent methodology for managing complex and changing projects,
and it offers a flexible, collaborative, and iterative approach to project management. The
benefits of Scrum, including its ability to accommodate change, encourage collaboration, and
promote continuous improvement, make it an ideal choice for the project at hand.

Section B
High Level requirements analysis and MoSCoW prioritisation tools:
Project management Tools :
I choose Project Plan 365 as my project management tool because:
- Ease of use: Project Plan 365 has a simple and easy-to-use interface that allows users to
quickly and efficiently create project schedules, manage resources, and schedule tasks.

- Flexibility: Project Plan 365 allows users to customize project templates and
management options to fit the needs of specific projects.

- Update information in sync: Project Plan 365 allows users to store and share project
information in the cloud, and update information on multiple devices.

- Data analysis features: Project Plan 365 provides a variety of data analysis features,
helping users to track project progress and detect problems that may occur during
project implementation.

Discuss about project management

Evidence of Project management tool used
Figure 2: Proeject management tool

Agile project management

 Figure 3: WBS and Gantt chart – Agile

Project ID BL1787 Date 4/25/2023

Project Name Bright Light 123
Budget $50,000
People 21
Hardware PC, Projectors, Server
Software Html, css, javascript, React , Project Plan 365
Documents Flowchart, Use case, WBS
Figure 4: Project Resources

Phase Process Members Work(hrs) Cost/hr Total

Initiating
Develop Project 3 30 $15 $1350
Definition
Planning Project management plan 2 24 $15 $720
Make a cost management 1 20 $15 $300
plan
Meeting planning 1 30 $15 $450
Resource management 2 25 $15 $375
planning
Executing
Develop project 10 100 $15 $15000
Test 2 50 $15 $1500
Risk $5000
Total 21 279 $15 $20195
Table 2: project Cost
 No Deliverables Note Date of Delivery
1

Table 3: Project Deliverables

Facilitated workshop (Meeting)

Project ID BL1787 Date 24/04/2023
Project Scope
Project Name Management information system
Meeting Purpose
Time Description
Introduction 10 Minutes Overviewing of the objectives of
and terms of the meeting and how the e-
reference sports prototype system will be
integrated with the current
system.
Requirement’s 20 Minutes Identifying the key features and
exercise functions that the e-sports
prototype system should have.
Agenda
Small group 30 Minutes Discussing and prioritizing the
discussion identified requirements.
exercise
Feedback and 30 – 40 M Discussing the priorities and
outline identified the tasks that need to
requirements be done in order to achieve the
executive's target of getting the
prototype system up and
running within 3 months
Meeting Location
Google Meeting
Title Description
Flo Johnson Head of IT Chairman
Daisy Watson Treasury Team Manage financial and budget for
Attendees
the project
Francis Smith Fundraising Seek funding for the project
Team
Rohan Singh Scholarship Receive, process and evaluate
 Application and scholarship applications.
Management
Team
Jan Dalton Scholarship Evaluation and selection of
Application and scholarship candidates
Management
Team
David Dahl Executive Make strategic decisions for the
project
Maya Lou Contracted E- Provide knowledge and skills
sports Expert related to E-sports.
Angel Wilmott Secretary to Ensure daily operations are
Operations carried out smoothly and
Director efficiently.

Table 4: facilitated workshop

Planning communication
No Task Method Type Description
1 Meet with a Online Google meet/
Director MSTeams/Zoomz
Meet with Project In-person/Verbal Meeting room G410
Manager
Developers team Face to face Stand Up Meetings/
Users and Teams JAD JAD Join app
development

Timebox guidelines.

Timeboxing and Scrum

<------------Typically, 2-4 (Exceptionally 6) weeks --------->

Integrating
Planning and
the completed
exploring phase Develop project
work of a Sprint
Kick-off of a sprint Improved
sprint evaluation

@20 -30% of
10% of effort @60-70% of effort
effort

B1: Identification of requirements that the student appropriate reasons are not
appropriate high-level requirements.
Documenting Requirements.

Gathering User requirement.

Specification
(Functional or Non-
Requirement functional
Person Problem User Understanding Definition Requirement)
Users need to
Daisy Lack of login securely access the A login facility should
Watson facility system be implemented FN: A login facility.
FN: A facility to keep
Need to keep Users need to track A facility to track track of funds, how
track of funds funds and funds and their they are allocated and
and their understand how allocation should be where they can be
allocation they are being used implemented applied.
Synchronization with
Need for Users need to see the organization's NF: Synchronization
synchronization accurate and up-to- banking system between the system
with banking date information should be built into and the organization’s
system about funds the prototype banking system.
FN: Addition of a
category for e-sports
Users want to donors when the
Lack of category categorize donors A category for e- facility for fundraising
Francis for e-sports based on their sports donors should activities is ported to
Smith donors interests be added the new system.
Users want to
Need for fast and efficiently access The system should NF: The system needs
responsive and process be fast and to be quick and
system information responsive responsive.
Users want to
Need to communicate with The system should
communicate businesses, allow for NF: Communication
with various individuals, and communication with with businesses,
sources of other sources of different types of individuals, and other
donations donations donors sources of donations.
Users need to plan
and manage events The system should
Need for events related to support events FN: Assistance in
planning support fundraising planning event planning.
Need for contact Users need to The system should FN: Facilitation of the
and mailing list manage contacts facilitate the collation of contacts
 and mailing lists
related to collation of contacts
management fundraising and mailing lists and mailing lists.
Users want to
Need to categorize e-sports Different categories
Rohan categorize based on different for e-sports should FN: Classification of
Singh different e-sports criteria be created various e-sports.
FN: Consultation with
the scholarship
application and
Suitable criteria for management team
Users want to set each category should and experts to find
Need for criteria specific criteria for be defined with the suitable criteria for
for each category each category help of experts each category.
FN: Compilation of the
Users want to criteria for each
Need for tools to efficiently choose Tools to choose the category into
choose the best the best candidates best candidates preliminary
candidates for scholarships should be developed application forms.
Need to consult
with the scholarship Consult with the
application and scholarship
management team application and
Consult with the and experts to management team
scholarship determine suitable and experts to find FN: Availability of
application and criteria for each suitable criteria for tools to help choose
management t... category. each category. the best candidates.
The system should
allow real-time
changes to FN: Ability to make
application forms to real-time changes to
Real-time The scholarship be made by the the application forms
changes to be application and scholarship by the scholarship
Jan made to management team's application and application and
Dalton application forms workflow management team. management team.
The system should FN: Ability for
allow applicants to applicants to track the
track the status of status of their
Applicants Applicants need to their applications applications
tracking know the status of throughout the throughout the
application status their applications selection process. selection process.
Notification of Applicants need to The system should FN: Ability to notify
application know if they were notify applicants of applicants whether
 the outcome of their
outcome successful or not application. they were successful.
The system should
Successful allow successful FN: Ability for
applicants need to applicants to applicants to formally
Ability to accept a accept scholarship formally accept a accept a scholarship
scholarship offer offers scholarship offer. offer.
The system should
allow the FN: Ability to manage
management of active scholarships by
active scholarships tracking deadlines,
by tracking setting up
Management of Management of deadlines, setting up notifications, and
active scholarships and notifications and making notes on the
scholarships their deadlines making notes. system.
NF: Inclusion of
relevant parts of the
Integration of The old system The prototype should old system,
relevant parts contains relevant integrate relevant integration into the
David from the old parts for the new parts from the old prototype, and
Dahl system prototype. system. testing.
The system should
Applicant Applicants need to allow applicants to FN: Ability for
Maya registration on register for the register on the applicants to register
Lou the system scholarship program system. on the system..
The system should
Applicants need to allow applicants to FN: Ability for
Viewing available view available view available applicants to view
scholarships scholarships scholarships. available scholarships.
The system should
automatically inform NF: Automatic
users of completed notification of
Applicants need to actions, such as completed actions,
Notification of know when they registration or such as registration or
completed have completed an submission of an successful submission
actions action application. of an application.
The system should FN: Ability for
allow applicants to applicants to supply
Context-sensitive Context-sensitive supply context- context-sensitive
information in information is sensitive information information when
scholarship required for each e- in their scholarship applying for a
application form sport game application form. scholarship.
User-friendly The system must be The system must be NF: User-friendliness
 of the system, with
knowledge and
user-friendly and respect conveyed for
convey knowledge of each genre and
each genre and various electronic
system with easy to use and respect for the games, to ensure
knowledge of e- respect various e- various electronic applicants trust the
sport games sport games games. system.

Table 5: Capturing User requirements

Below is a list of requirements that I feel it is not appropriate the high-level requirements:
Requirements Reason why I choose
FN: Ability for applicants to track the status It is a process phase and makes no claims
of their applications throughout the selection about a particular result or outcome.
process.
FN: Availability of tools to help choose the The requirement is excessively general and
best candidates non-specific since it lacks precise standards
or techniques for judging candidates.
NF: Communication with businesses, The criteria is excessively general and non-
individuals, and other sources of donations. specific because it doesn't specify any
particular communication routes or protocols
to be employed.
FN: Ability to manage active scholarships by The requirement lacks specific tracking
tracking deadlines, setting up notifications, mechanisms or interfaces, making it too
and making notes on the system. vague and non-specific

B2: Rewrite, and add to, the list to end up with a total of 8-10 ‘updated’
functional and non- functional requirements for building the system. Approriate justification to
be provided for each of your requirements against information you have gathered from the
case study.

Existing FR New FR Reason why I choose

1 Functional Requirement: A The login facility has a SSO will improve user
login facility. registration system that experience and security by
allows students to apply for allowing users to sign in to
the scholarship program the system using their
and integrates with Single existing credentials.
Sign On (SSO) for ease of
use and security.
2 Functional Requirement: A Ability to generate reports The ability to generate
facility to keep track of on fund allocation and reports will help the
 funds, how they are spending. treasury team to keep
allocated and where they track of fund allocation
can be applied. and spending and provide
transparency to
stakeholders.
3 Functional Requirement: Addition of a feature to This feature will enable the
Addition of a category for allow donors to specify fundraising team to track
e-sports donors when the their donation towards e- donations towards e-
facility for fundraising sports. sports and help in planning
activities is ported to the fundraising activities.
new system.
4 Functional Requirement: Addition of a feature to Allowing applicants to
Categorization of different allow applicants to choose choose multiple e-sports
e-sports. multiple e-sports for their will increase the chances
scholarship application. of finding suitable
candidates for each
scholarship category.
5 Functional Requirement: Integration of a secure A secure login system is
Ability for applicants to login system to ensure the necessary to protect
register on the system. privacy of applicant applicant information and
information. prevent unauthorized
access.
6 None Ability for scholarship This new requirement
providers to view and provides scholarship
analyze applicant data, providers with valuable
including demographic insights into applicant
information and application behavior and
metrics. demographics, which can
inform future scholarship
offerings and improve the
scholarship selection
process.
Table 6: List of FR and Updated list

Existing NFR New NFR Reason why I chose

1 Non-functional Integration with banking API Real-time synchronization
Requirement: for real-time synchronization will help the treasury team
Synchronization of funds. to have up-to-date
between the system information on funds and
and the organization’s avoid discrepancies.
banking system.
2 Non-functional Minimum acceptable response Defining and maintaining
Requirement: System time should be defined and the minimum acceptable
should be fast and maintained. response time will ensure
 responsive. that the system is fast and
responsive, which will lead
to a better user
experience.
3 Non-functional Ability to handle concurrent As the system grows and
Requirement : System user requests without more users access it, it
should be fast and performance degradation must be able to handle
responsive concurrent user requests
without performance
degradation to ensure an
optimal user experience.
4 Non-functional Thorough testing of the The inclusion of relevant
Requirement: Inclusion integrated system with the old parts of the old system is
of relevant parts of the and new components to necessary for continuity,
old system, integration ensure seamless functionality. but thorough testing is
into the prototype, and needed to ensure the new
testing. and old components work
together efficiently.
5 Non-functional Ability for applicants to Real-time updates on the
Requirement: receive real-time updates on status of an application
Automatic notification the status of their application. will keep applicants
of completed actions, informed and reduce
such as registration or anxiety while waiting for
successful submission results.
of an application.
6 Non-functional Inclusion of educational Educational resources and
Requirement: User- resources and FAQs to help FAQs will foster trust in
friendliness of the applicants understand the the system by providing
system, with knowledge application process and make information and guidance
and respect conveyed informed decisions. to applicants.
for each genre and
various electronic
games, to ensure
applicants trust the
system.
7 None Non-functional Requirement: This new requirement
Compliance with relevant data ensures that applicant
protection laws, such as GDPR data is protected and
and CCPA, and implementing secure, which is critical for
appropriate security building trust and
measures, such as multi-factor complying with legal
authentication and regular requirements.
security audits.

Table 7: List of NF and updated lists

B3: MoSCoW technique applied appropriately to prioritise the
requirements in your updated ‘requirements prioritsed list’.
Discuss MosCow teschnique and how you apply to your project
According to (Brush, 2023), The MoSCoW method is a four-step process for determining which
project requirements generate the greatest return on investment (ROI). MoSCoW stands for
must have, should have, could have, and will not have; the o's help to pronounce the acronym.
The MoSCoW approach is used in a range of business fields. It allows everyone participating in a
project to understand what work needs to be done first and how that work contributes to
increased income, lower operational costs, more productivity, or increased customer
happiness. When selecting a software vendor, it can assist stakeholders frame talks about the
relevance of specific product features. On the IT side, the MoSCoW technique aids Agile project
management by assisting project teams in prioritizing story points.
In this project, I use the MoSCoW approach to prioritize the project's required features.
Prioritizing requirements assists project teams to understand how much effort and resources
each project piece requires. This knowledge enhances the time management of the team,
makes the project more manageable, increases the possibility of completion ahead of schedule,
and maximizes ROI.

REQUIREMENTS MUST SHOULD HAVE COULD WON’T

HAVE HAVE HAVE
1 The login facility has a YES - - -
registration system
that allows students to
apply for the
scholarship program
and integrates with
Single Sign On (SSO)
for ease of use and
security.
2 Ability to generate YES - - -
reports on fund
allocation and
spending.
3 Integration with - YES - -
banking API for real-
 time synchronization
of funds.
4 Communication with YES - - -
businesses, individuals,
and other sources of
donations.
5 Facilitation of the YES - - -
collation of contacts
and mailing lists.
6 Addition of a feature - YES - -
to allow donors to
specify their donation
towards e-sports.
7 Support for events YES - - -
planning.
8 Ability to handle - - YES -
concurrent user
requests without
performance
degradation.
9 Categorization of YES - - -
different e-sports.
10 Consultation with the YES - - -
scholarship application
and management
team and experts to
find suitable criteria
for each category.
11 Compilation of the YES - - -
criteria for each
category into
preliminary application
forms.
12 Availability of tools to - YES - -
help choose the best
candidates.
13 Ability to make real- YES - - -
time changes to the
application forms by
the scholarship
application and
management team.
14 Ability for applicants to YES - - -
track the status of
their applications
 throughout the
selection process.
15 Ability to manage YES - - -
active scholarships by
tracking deadlines,
setting up
notifications, and
making notes on the
system.
16 Ability to notify YES - - -
applicants whether
they were successful.
Ability for applicants to
formally accept a
scholarship offer.
17 Thorough testing of YES - - -
the integrated system
with the old and new
components to ensure
seamless functionality.
18 Integration of a secure YES - - -
login system to ensure
the privacy of
applicant information.
19 Ability for applicants to YES - - -
supply context-
sensitive information
when applying for a
scholarship.
20 Ability for applicants to YES - - -
view available
scholarships.
21 Ability for applicants to - YES - -
receive real-time
updates on the status
of their application.
22 Inclusion of - - - YES
educational resources
and FAQs to help
applicants understand
the application process
and make informed
decisions.
23 Ability for scholarship - - YES -
providers to view and
 analyze applicant data,
including demographic
information and
application metrics.

24 Ability for scholarship YES - - -

providers to view and
analyze applicant data,
including demographic
information and
application metrics.

Table 8: MoScow Prioritization

Expressing Requirements and Design with Models

Capturing Design
Module description
o Flowcharts

Figure 5:

o Pseudo-code:
Requirement : The login facility has a registration system that allows students to apply for the
scholarship program and integrates with Single Sign On (SSO) for ease of use and security.
Algorithm:
 Infinite loop initialization
 Ask users to enter student information and scholarship information
 Check the validity of student information and scholarship information. If the information
is invalid, ask the user to re-enter it.
 Call the function that enrolls the student in the scholarship program with the
information entered.
 Check registration results. If successful, notify the user that the registration was
successful and exit the loop. If unsuccessful, error message and ask user to re-enter
student and scholarship information.
 Go back to step 2 and continue the loop until registration is successful.

Here is a pseudocode for the login facility has a registration system that allows students to apply
for the scholarship program and integrates with Single Sign On (SSO) for ease of use and
security:
1. Display login page
2. If user clicks on "Register" button, go to step 3, else go to step 4
3. Display registration form with the following fields:
- First Name
- Last Name
- Email
- Password
- Confirm Password
- Checkbox for Scholarship program application
4. User enters their SSO credentials and clicks on "Sign In"
5. Validate the user's credentials with SSO provider
6. If the user is authenticated, redirect them to the home page, else display an error message
7. If user has applied for Scholarship program in step 3, save their details and mark them as
"Applied" in the database

The purpose of this algorithm is to help users log into the scholarship registration system and
apply the SSO feature to ensure security and convenience for users. The above pseudocode is
to describe an algorithm for login function for scholarship registration system. It helps users log
into the system and integrates the SSO feature to ensure safety and convenience for users.

Functional Design artefacts from UML

o Use cases
Name,
description Login
Actors
Pre-condition
Post-condition

Main
Success
Path
Actor Actions System Respones

Alternate
Path A1
Actor Actions System Respones

Exception E1
Path
Actor Actions System Respones

Scenarios(Insert additional rows for each scenario)

Scenario Post-conditions Flow

o Sequence diagram

Relational Database design artefacts

o ERD’s

o DFD’s
 Must provide context diagram of the entire system
 Followed by data flow diagram
UI Design
o Screen layout
o
Section C
LSEPi
(C1) the role of the Data Controller within the organisation
In recent years, organisations have become increasingly aware of the importance of protecting
the personal data of their customers, clients and employees. Brightstar Ltd. (BL), a charitable
organisation in the UK, is no exception. As part of its commitment to data protection, BL is
looking to appoint a Data Controller (DC) to help them comply with legal, social, ethical, and
professional requirements.

According to European Commission(2018), a data controller is a person, organization, or entity

who decides how and why personal data is handled. The data controller is the person or
organization that determines the purpose and means of data processing and is ultimately
responsible for ensuring that personal data is processed in accordance with applicable data
protection laws and regulations. The DC is responsible for ensuring that the organisation is
compliant with data protection legislation, such as the Data Protection Act (DPA), the Computer
Misuse Act (CMA), the Access to Medical Reports Act (AMRA), and the General Data Protection
Regulation (GDPR). They are also responsible for implementing data protection policies and
procedures, training staff on data protection issues, and responding to data subject access
requests (DSARs) and other requests from individuals who have a right to access their personal
data.

The DPA is a UK law that governs the processing of personal data. It gives individuals certain
rights in relation to their personal data, such as the right to access their data, the right to have
their data corrected, and the right to object to the processing of their data (Information
Commissioner's Office, 2021). The DC must ensure that BL complies with the DPA by
implementing appropriate policies and procedures, and by training staff on their obligations
under the Act.

According to Chai(2023), Confidentiality, integrity, and availability (CIA) are the three pillars of
information security. The DC must ensure that BL's data is secure and that access to it is
restricted to authorised personnel only. They must also ensure that data is accurate and up-to-
date, and that it is available when it is needed.

According to Wolford(2020), The GDPR is a European Union regulation that came into effect in
May 2018. It governs the processing of personal data and applies to all organisations that
process the data of EU citizens, regardless of where the organisation is based. The DC must
ensure that BL complies with the GDPR by implementing appropriate policies and procedures,
and by training staff on their obligations under the regulation.

The role of the DC within BL is crucial to ensuring that the organisation is compliant with data
protection legislation and that its data is secure. The DC must work closely with senior
management to develop and implement data protection policies and procedures, and must
ensure that staff are trained on their obligations under these policies. They must also respond
promptly and appropriately to DSARs and other requests for information.

In conclusion, the appointment of a Data Controller is an essential step for BL to ensure that
they are compliant with legal, social, ethical, and professional requirements. The DC plays a
critical role in ensuring that the organisation's data is protected and that staff are aware of their
obligations under data protection legislation. By appointing a DC, BL can demonstrate their
commitment to protecting the personal data of their stakeholders, and can enhance their
reputation as a responsible and trustworthy organisation.
(C2) Any legal, social, ethical, and professional issues that MV may be faced with.

Legal
Social
Ethical
Professional issues

BCS Code of Conduct

The Code of Conduct is a set of guidelines that specify the concepts and ethical standards
that professionals in a specific sector must follow. The British Computer Society (BCS) is a
professional organization in the United Kingdom that represents IT professionals. The BCS
has a Code of Conduct that specifies its members' responsibilities to act with honesty,
professionalism, and accountability in their work.

There are various professional concerns that can develop in the case of BL, a nonprofit
organization that oversees scholarship applications and funds. Data privacy and security is
one such concern. The collecting and storage of sensitive personal data from candidates is
part of the scholarship application process. To guarantee that data is not mishandled or
misused, it is critical that BL's IT division implements proper security measures and that all
staff members are taught on data privacy rules and procedures.

Conflict of interest is another professional concern that might occur. BL has affiliations with
various universities and colleges, and certain staff members may have personal or financial
ties to these schools. All employees, especially those involved in scholarship application and
management, must preserve impartiality and justice in their decision-making procedures.

The BCS Code of Conduct can assist professionals in the IT industry, particularly those at BL,
in acting with integrity and accountability. Several principles are outlined in the BCS Code,
including acting in the public interest, preserving professional competence and integrity,
and performing duties to relevant authorities and the profession.

Acting in the public interest requires IT workers to examine the larger influence of their
work on society and accept responsibility for the potential consequences of their activities.
BL's IT division, for example, should guarantee that their systems and processes are
designed to preserve the privacy and security of scholarship candidates' personal data.

Maintaining professional competence and integrity entails constantly increasing skills and
knowledge in the sector, as well as ensuring that work is completed with honesty and
diligence. BL's IT section should maintain current on best practices in data security and
privacy, and all employees should be taught in these areas.

The duty to relevant authority entails IT professionals adhering to legal and regulatory
standards and cooperating with authorities as needed. BL's IT section should guarantee that
data protection rules and regulations, such as the GDPR, are followed and that any data
breaches are reported to the appropriate authorities.

Finally, obligation to the profession entails promoting the profession's ideals and beliefs as
well as acting with professionalism and accountability. In their work, BL IT professionals
should respect ethical standards and support the concepts of justice, transparency, and
responsibility.

To summarize, the BCS Code of Conduct establishes a framework for IT professionals to

work with honesty and professionalism. Adherence to the Code at BL can assist ensure that
scholarship applications and funding are administered fairly, transparently, and
accountable, and that sensitive personal data is not misused or mishandled.
 Legal: One example of a legal issue in the case study is the requirement to comply with data
protection laws such as the General Data Protection Regulation (GDPR). BL is a charitable
organization that manages personal data of scholarship applicants and donors. Therefore,
they must comply with GDPR regulations regarding the collection, processing, storage, and
sharing of personal data to avoid legal consequences.

Social: BL's decision to branch out into esports scholarships can be seen as a social issue.
Esports is a rapidly growing industry that appeals primarily to younger generations. By
offering esports scholarships, BL is catering to the changing needs and interests of younger
students, who may not have previously considered academic or sports scholarships.
However, there may be concerns that esports is not a socially acceptable activity and may
not be viewed favorably by all stakeholders.

Ethical: The ethical issue in the case study is the development of a new system to manage
esports scholarships. The head of the IT division, Flo Johnson, proposed building a highly
functional prototype system by re-using parts of the current system and adding new
functionalities. While this approach may be more efficient, it raises ethical concerns about
data privacy and security. BL must ensure that the new system adheres to ethical standards
and protects the privacy and security of personal information.

Professional issues: One example of a professional issue in the case study is the
development of a synchronisation system between the platform and the organization's
banking system. The lack of automatic communication or synchronisation between the two
systems has caused data integrity issues in the past, which is a professional issue. BL must
address this issue by developing a synchronisation system that minimizes human error and
ensures data integrity. This requires a professional approach and the involvement of IT
experts who can develop a robust system.

Assumptions

Conclusion

References:

Brush, K., 2023. Techtarget. [Online]

Available at: https://www.techtarget.com/searchsoftwarequality/definition/MoSCoW-method
[Accessed 26 4 2023].
Chai, W., 2023. TechTarget. [Online]
Available at: https://www.techtarget.com/whatis/definition/Confidentiality-integrity-and-
availability-CIA
[Accessed 27 4 2023].
European Commission, 2018. EUR-Lex. [Online]
Available at: https://eur-lex.europa.eu/eli/reg/2016/679/oj
[Accessed 27 4 2023].
Hamilton, T., 2023. Guru99. [Online]
Available at: https://www.guru99.com/agile-scrum-extreme-testing.html
[Accessed 21 4 2023].
Information Commissioner's Office, 2021. ICO.. [Online]
Available at: https://ico.org.uk/for-organisations/guide-to-data-protection/introduction-to-dpa-
2018/about-the-dpa-2018/
[Accessed 27 4 2023].
Team, L. C., n.d. Lucidchart. [Online]
Available at: https://www.lucidchart.com/blog/what-is-timeboxing
[Accessed 21 4 2023].
Wolford, B., 2020. Gdpr.eu. [Online]
Available at: https://gdpr.eu/what-is-gdpr/
[Accessed 27 4 2023].