Student Name: XXX – XXXX - XXXX

HIỂN HOÀNG
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

Managerial model
AGILE METHODS
RAD and TIMEBOXING (Why RAD?)
Iterative development using prototyping.
 Timeboxing

The Chosen Method for development

Scrum

Section B
High Level requirements analysis and MoSCoW prioritisation tools:

Project management Tools

Discuss about project management
Evidence of Project management tool used

Agile project management

Figure 1: WBS and Gantt chart – Agile

Project ID Date
Project Name
Budget $20,000
People 17
Hardware PC, Projectors, Server
Software
Documents
Technical materials
Figure 2: Project Resources
 Phase Process Members Work/hr Cost/hr Total
Initiating
Develop Project 3
Charter

Project management 3 24hr $10 $720

Planning plan

Executin
g

Total
Table 1: project Cost

N Deliverables Note Date of Delivery

o
1

Table 2: Project Deliverables

Facilitated workshop (Meeting)

Project ID Date 14/03/2023
Project Scope
Project Name Management information system
Meeting Purpose
Time Description
Introduction and terms of 10 Minutes
reference
Agenda
Requirement’s exercise 20 Minutes
Small group discussion exercise 30 Minutes
Feedback and outline requirements 30 – 40 M
Meeting Location
Meeting Room A
Title Description
Flo Johnson Head of IT Chairman
Attendees
Daisy Watson Treasury Treasury Team
Table 3: facilitated workshop

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

Timebox guidelines.

Timeboxing and Scrum

<------------Typically, 2-4 (Exceptionally 6) weeks --------->
Sprint Planning Product Sprint
& Investigation Refinement consolidation Sprint
Kick-off Retrospective
@70-80% of @10 -20% of review
10% of effort
effort effort

B1: Identification of requirements that the student appropriate reasons

are not appropriate high-level requirements.

Documenting Requirements.
Functional requirements: Specify the actions that the software product must be able to
perform.
Non-functional: requirements specify properties of the product itself or compliance to
standards such as
Platform constraints, Reliability, Usability, Performance, Security, Portability.

Gathering User requirement.

N Problem User Understanding Requirement Specification

o definition
1 Login facility Ability to log in to the The system must have Functional
system a login functionality
2 Fund tracking Ability to track funds The system must have Functional
and their allocation a feature to track funds
and their allocation
3 Banking system Integration with the The system must be Functional
integration organization's banking integrated with the
system organization's banking
system
4 E-sports category A category for e- The system must have Functional
sports donors in a category for e-sports
fundraising activities donors
5 Fast and System must be fast The system must be Non-
responsive and responsive designed to be fast and Functional
system responsive
6 Communication Ability to communicate The system must have Functional
with donors with businesses, a feature to allow
individuals, and other communication with
sources of donations donors
7 Events planning Ability to plan events The system must have Functional
a feature to support
events planning
8 Collation of Ability to collate The system must have Functional
contacts and contacts and mailing a feature to collate
mailing lists lists contacts and mailing
lists
9 E-sports Categorization of The system must have Functional
categorization different e-sports a feature to categorize
different e-sports
10 Criteria Compilation of criteria The system must have Functional
compilation for each category into a feature to compile
preliminary application criteria for each
forms category into
preliminary application
forms
11 Candidate Tools to help choose The system must have Non-
selection the best candidates tools to help choose the Functional
best candidates
12 Real-time for Allow for real-time The system must have Non-
forms changes to be made a feature to allow real- Functional
to the application time changes to be
forms made to the application
forms
13 Applicant tracking Ability for applicants to The system must have Non-
track the status of a feature to allow Functional
their applications applicants to track the
status of their
applications
14 Notification of Notification of whether The system must have Functional
successful applicants were a feature to notify
applications successful applicants whether they
were successful
15 Acceptance of Ability for applicants to The system must have Functional
scholarship offer formally accept a a feature to allow
scholarship offer applicants to formally
accept a scholarship
offer
 16 Active scholarship Management of active The system must have Functional
management scholarships a feature to manage
active scholarships
17 Integration of Integration of relevant The system must be Functional
relevant parts of parts of the old system able to integrate
the old system relevant parts of the old
system
18 Applicant Ability for applicants to The system must have Functional
registration register on the system a feature to allow
applicants to register on
the system
19 Scholarship Ability for applicants to The system must have Functional
viewing view available a feature to allow
scholarships applicants to view
available scholarships
20 Notification of Automatic notification The system must have Non-
completed actions of completed actions a feature to Functional
automatically inform
users of completed
actions
21 Context-sensitive Ability for applicants to The system must have Non-
information in supply context- a feature to allow Functional
application sensitive information applicants to supply
in the application context-sensitive
information in the
application
22 User-friendliness User-friendliness The system must be Non-
designed to be user- Functional
friendly

Table 4: Capturing User requirements

The requirements not high-requirements

"A login facility" (Daisy Watson, Treasury Team): This is a specific feature that is
needed for the system to function properly, but it does not address the overall purpose
of the system.
"Categories different e-sports" (Rohan Singh, Scholarship Application and
Management Team): This requirement is specific to a particular aspect of the system
and does not address the overall purpose of the system.
"Remember that relevant parts of the old system need to be pulled, integrated
into the prototype and tested. Don’t forget about them, they should be part of the
requirements. I’m not going to list them – you should know what they are" (David Dahl,
Executive): This requirement is not specific enough to be considered a high-level
requirement, as it does not provide any information about what parts of the old system
need to be integrated into the new system or why.
"The system must be user-friendly, and it is important to convey knowledge of
each genre and respect for the various electronic games, or the applicants will be
reluctant to trust you" (Maya Lou, Contracted E-sports Expert): This requirement is
important for the success of the system, but it is not a high-level requirement as it does
not address the overall purpose of the system.

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 chose

Given the sensitive nature of
the data being handled, the
Two-factor authentication for system must ensure that user
Login Facility enhanced security login information is secure
Social media is a powerful tool
for raising awareness and
promoting fundraising
activities, therefore, the system
Addition of e-sports donor Integration with social media must integrate with popular
category platforms for broader outreach social media platforms
Online event management
platforms can help streamline
the planning process and
ensure that all necessary
components are in place,
Integration with online event therefore, the system must
Support for events planning management platforms integrate with these platforms
Automated email marketing
can help increase engagement
with potential donors,
therefore, the system must
Collation of contacts and Automated email marketing have the ability to send
mailing lists capabilities automated emails to contacts
By integrating with online
gaming communities, the
system can gain a better
understanding of the various e-
sports categories, and connect
Categorization of different e- Integration with online gaming with potential scholarship
sports communities applicants and donors
Document management
systems can help streamline
the application process;
Integration with document therefore, the system must
Preliminary application forms management systems integrate with these systems
The system must have the
ability to process payments
Management of active Integration with payment processing and track the disbursement of
scholarships systems scholarship funds
To ensure the integrity of the
scholarship application
process, the system must have
Integration with identity verification the ability to verify the identity
User registration systems of users
Table 5: List of FR and Updated list

Existing NFR New NFR Reason why I chose

As the organization grows, the
system must be able to handle
Synchronization with Scalability to handle large volumes larger volumes of transactions
organization's banking system of transactions and user data
To ensure a positive user
experience, the system must
Availability and reliability to ensure be highly available and
Fast and responsive system uninterrupted service reliable, with minimal downtime
The system must ensure that
sensitive information is
protected at all times, in
Tools for choosing best Data security and privacy to protect compliance with data privacy
candidates sensitive information and security regulations
As scholarship criteria evolve,
the system must be flexible
enough to accommodate real-
Real-time changes to Flexibility to accommodate changes time changes to the application
application forms in scholarship criteria process
The system must be designed
with usability in mind, to
ensure that users can easily
track the status of their
Status tracking for applicants Usability to ensure ease of use scholarship applications
The system must be designed
for optimal performance and
efficiency, to ensure that users
receive timely notifications
Notification of application Performance and efficiency to about the status of their
status ensure timely notifications scholarship applications
The system must support
multiple languages, to
Multilingual support to accommodate users from
accommodate users from different different linguistic backgrounds
Context-sensitive information linguistic backgrounds and ensure inclusivity
The system must be designed
with user experience in mind,
to ensure that users can easily
User experience design to ensure a navigate the system and
User-friendliness positive user experience complete tasks efficiently
Table 6: 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

NO REQUIREMENTS MUST SHOULD COULD WON’T

HAVE HAVE HAVE HAVE
1 Login facility
2 Fund tracking
3 Banking system integration
 4 E-sports category
5 Fast and responsive system
6 Communication with donors
7 Events planning
8 Collation of contacts and mailing lists
9 E-sports categorization
10 Criteria compilation
11 Candidate selection
12 Real-time for forms
13 Applicant tracking
14 Notification of successful applications
15 Acceptance of scholarship offer
16 Active scholarship management
17 Integration of relevant parts of the old
system
18 Applicant registration
19 Scholarship viewing
20 Notification of completed actions
21 Context-sensitive information in
application
22 User-friendliness
Table 7: MoScow Prioritization

Expressing Requirements and Design with Models

Capturing Design
Module description
o Flowcharts
o Pseudo-code
Functional Design artefacts from UML
o Use cases
 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 and
- DPA
- CIA
AAA
GDPR
- The role of DC within organization
-
(C2) any legal, social, ethical, and professional issues that MV may be faced with.

Legal
Social
Ethical
Professional issues

Discuss: About Code of Conducts, with examples of professional issues

Discuss Professional bodies:
- 1984 British Computer Society.
- A Code of Conduct and Practice
BCS Code of Conduct
- Public Interest:
- Professional Competence and Integrity:
- Duty to Relevant Authority:
- Duty to the Profession:

As a part of your answer to

(C2) provide one practical example from the case study that relates to each aspect of LSEPI.

- Legal
- Social
- Ethical
- Professional issues

Assumptions

Conclusion

References (Harvard style)

Note:
Professional written communication for English proficiency [5%]
Professional standard and formatting, professional writing style and language use.
 1. Evaluation
2. Assign evaluators to each application
3. Evaluate applications based on predetermined criteria
4. Score each application based on evaluation
5. Identify top candidates based on scores
6. Notify successful candidates

Algorithm – Pseudocode - Scholarship Candidate Evaluation

1 STAR RETRIEVE_scholarship_applications_for_evaluation()
T evaluat
2 EVALUATORS ASSIGN_evaluators_to_applications
3 FOR each application in applications
SCORE EVALUATE_application(application,
evaluators
4 SAVE scores_in_database(scores
5 ENDFOR
6 END
7 STOP

START Scholarship Candidate Evaluation

applications = RETRIEVE_scholarship_applications_for_evaluation()
evaluators = ASSIGN_evaluators_to_applications(applications)
FOR each application in applications
scores = EVALUATE_application(application, evaluators)
SAVE_scores_in_database(scores)
ENDFOR
top_candidates = IDENTIFY_top_candidates_based_on_scores()
NOTIFY_successful_candidates(top_candidates)
END

This pseudo code describes the process of evaluating scholarship candidates.

The system retrieves scholarship applications for evaluation and assigns
evaluators to each application. The evaluators evaluate the applications based
on predetermined criteria and score each application. The system then
identifies the top candidates based on the scores and notifies successful
candidates.