MARCH 27, 2023

REQUIREMENT MANAGEMENT
COURSEWORK
COMP1787 (2022/2023)

Student Name: XXX – XXXX - XXXX

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

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

Figure 1: Proeject management tool

Agile project management

Figure 2: WBS and Gantt chart – Agile

Project ID Date
Project Name
Budget $20,000
People 17
Hardware PC, Projectors, Server
Software
Documents
Technical materials

Figure 3: Project Resources

Phase Process Members Work/hr Cost/hr Total

Initiating
Develop Project Charter 3

Project management plan 3 24hr $10 $720

Planning

Executing
 Total
Table 1: project Cost

No Deliverables Note Date of Delivery

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/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 --------->
Sprint Planning & Sprint
Product Refinement
Investigation consolidation Sprint
Kick-off Retrospective
@10 -20% of review
10% of effort @70-80% of 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.

Problem User Understanding Requirement Specification

definition
FN
NF

Table 4: Capturing User requirements

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

1
2
3
4
5
6
7
8
9
10
Table 5: List of FR and Updated list

Existing NFR New NFR Reason why I chose

1
2
3
4
5
6
7
8
9
10
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

REQUIREMENTS MUST HAVE SHOULD HAVE COULD HAVE WON’T HAVE

1 LOGIN YES - - -
2
3
4
5
6
7
8
9
10
Table 7: MoScow Prioritization
Expressing Requirements and Design with Models
Capturing Design
Module description
o Flowcharts
o Pseudo-code
o Rich pictures
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 Story boards
o Navigations

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.
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 START RETRIEVE_scholarship_applications_for_evaluation()
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.