Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Requirements Management for BL Company Project, Assignments of Requirements Engineering

A requirements management plan for the BL Company Project. It includes high-level requirements analysis and Moscow prioritization, legal, social, ethical, and professional issues, and task breakdown with estimated hours. The document also discusses the data protection act, general data protection regulation, and British Computer Society Code of Conduct. It lists the requirements, their stakeholders, and whether they are functional or non-functional. useful for students studying project management, software engineering, and computer science.

Typology: Assignments

2022/2023

Available from 07/14/2023

TuanAnhMai
TuanAnhMai 🇬🇧

5

(3)

24 documents

1 / 17

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1
COMP1787:
REQUIREMENTS MANAGEMENT
Name: Mai Tran Tuan Anh
ID: 001308504
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff

Partial preview of the text

Download Requirements Management for BL Company Project and more Assignments Requirements Engineering in PDF only on Docsity!

COMP1787:

REQUIREMENTS MANAGEMENT

Name : Mai Tran Tuan Anh

ID : 001308504

Table of Contents

  • A. INTRODUCTION...........................................................................................................................
      1. Business goal
      1. Methods
  • B. HIGH LEVEL REQUIREMENTS ANALYSIS AND MOSCOW PRIORITIZATION
      1. Review Requirements
      1. High-level requirements
      1. MoSCoW methods
  • C. LEGAL, SOCIAL, ETHICAL AND PROFESSIONAL ISSUES
      1. Data Protection Act (DPA).....................................................................................................
      1. General Data Protection Regulation (GDPR)
      1. Data controller
      1. Role of data controller within the organization
      1. Legal, Social, Ethical and Professional issues (LSEPI)
    • 5.1 Legal issue
    • 5.2 Social issue
    • 5.3 Ethical issue
    • 5.4 Professional issue................................................................................................................
      1. British Computer Society Code of Conduct
    • 6.1 Public Interest
    • 6.2 Professional Competence and Integrity
    • 6.3 Duty to Relevant Authority
    • 6.4 Duty to the Profession
    • 6.5 Example of BCS in the BL company project
    • 7 Conclusion
  • D. REFERENCES..............................................................................................................................
  • Demonstrate control
  • DSDM is capable of handling the spans of the whole life cycle of a project, providing practice

guidelines for on-time and in-budget delivery of projects. During the progress of developing the

application, DSDM encourages to use various of techniques and artifacts including

  • Facilitated Workshops
  • MoSCoW methods
  • Time boxing
  • Modelling and Prototyping
  • In the stage of planning and analysis, when Flo was discussing with the rest of IT division,

beside from Agile method, his employees also recommend the Waterfall method. The waterfall

model is a static model and it approaches systems development in a linear and sequential

manner, completing one activity before the other (Adetokunbo & Basirat, 2013). Flo has listing

out some of the most important differences between these 2 models when applying for the

projects

Agile Waterfall

Process is divided into sprints Process is divided into different stages

Provide the flexibility, allow changes during

the development process

A structured software development method,

difficult for any changes during the process

Testing phase are performed after each

sprint

Testing phase are performed only after the

building phase

Focusing on satisfying customer needs and

change itself to adapt

Focusing on completing the projects

Might not work wells with low-budget

scenario because there are a lot of sprints as

well as changes.

Reduce risk with budget since risk

assessment is performed at the beginning of

the process

  • With all the differences listed out, Flo decided to use Agile model, for particular the DSDM

methodology. The crucial factor that he decided to use DSDM is that there are too many

requirements from the stakeholders and he has to prioritize each one of them. The DSDM

provide the MoSCoW methods which is the tools that is used to identify the importance and

priority of each requirement. In this way, the IT department will be able to identify which

requirement is the most important and works on them first. DSDM also allow Flo to develop the

application rapidly and focus on what the user really needs, which is the aim of the projects.

B. HIGH LEVEL REQUIREMENTS ANALYSIS AND MOSCOW

PRIORITIZATION

  • List of all requirements

ID Requirements Stake Holder

BL-RQ- 1 User can login

Daisy Watson (Treasury

Team)

BL-RQ- 2 Staff can keep account of funds, their distribution, and

their potential uses.

BL-RQ- 3 The system can synchronize with the organization’s

banking system

BL-RQ- 4 Staff can categorize e-sports donors

Francis Smith

(Fundraising Team)

BL-RQ- 5 The system should work quickly and effectively.

BL-RQ- 6 The system should enable contact with organizations,

people, and other potential donors.

BL-RQ- 7 Planning activities should be supported by the system.

BL-RQ- 8 The system should facilitate the collation of contacts and

mailing lists.

BL-RQ- 9 Different e-sports categories Rohan Singh (Scholarship

Application and

Management Team)

BL-RQ- 10 Consult with the scholarship application and management

team and experts to find suitable criteria for each category.

BL-RQ- 11 Compile criteria for each category into preliminary

application forms.

BL-RQ- 12 Tools to choose finest candidates

BL-RQ- 13 Real time adjustment to entry forms

Jan Dalton (Scholarship

Application and

Management Team)

BL-RQ- 14 User can monitor the progress of their application.

BL-RQ- 15 Notice the applicants when the result is accounced

BL-RQ- 16 Ability to accept scholarship offer by applicants

BL-RQ- 17 Staff members can keep track of deadlines, set up alerts,

and record comments on the system to handle current

scholarships.

BL-RQ- 18 Old system will be integrated to the new system David Dahl (Executive)

BL-RQ- 19 Candidates may open an account. Maya Lou (Contracted E-

sports Expert) BL-RQ- 20 Candidates must be able to see the grants that are offered.

BL-RQ- 21 Users should be immediately informed by the system when

activities are finished. (Successful registration or

submission)

BL-RQ- 22 The method ought to let candidates enter context-sensitive

data. Additionally, the user should be able to enumerate

their achievements.

2. High-level requirements

  • Functional requirements can be most simply defined as something the system must do, while

non-functional requirements can be explained as requirements that describe how the system

works (Gorbachenko, 2020). Below is the list of high-level requirements that are needed to

build the application.

Requirements ID Functional (FR)/

Non-functional

(NFR)

Reason

BL-RQ- 3 NFR This feature is not developed on the current system,

which has brought a lot of disadvantages such as

duplicated data, additional employees to double

check the data to minimize number of mistakes and

so on. It has also been given high priority, so it must

be developed

BL-RQ- 9 FR It makes easier for both staff and applicants to

choose which type of e-sport they have interested in

BL-RQ- 10 FR Because number of scholarships are limited but

there are a lot of applicants, appropriate criteria

must be discussed carefully

BL-RQ- 11 FR This will make it easier for new applicants to apply

for scholarships. It will also reduce the time for the

process by providing standards for application forms

BL-RQ- 13 FR This feature is included so that if there is anything

lacking in the application, user can add them in time.

It also improves the proficiency of the system.

BL-RQ- 20 FR This belongs to the main scope of the application

BL-RQ- 21 FR The applicants will be reminded about the actions

they have done. The notification will also be

included information so that the user can perform

double-check

BL-RQ- 22 FR Many scholarships demand the applicants to provide

personal information. There will be a security

measure to ensure that the information will not be

leaked. There will also field for applicants to enter

their accomplishment

BL-RQ- 23 NFR Although this is an NFR, this feature is also

important. E-sport is still a new definition to a lot of

people, so the website needs to play a role as

communicator to bring e-sport closer to the user.

3. MoSCoW methods

  • The MoSCoW method is a technique used by organizations to communicate the importance

and priority of the various requirements (Waida, 2022). The acronym MoSCoW stands for four

priority categories.

  • Must have
  • Should have
  • Could have
  • Will not have
  • Approaching MoSCow methods will help the team in working toward their project around the

limitation they are facing. Some of the aspects the team may need to consider when applying

this method to prioritize initiatives are:

  • The needs of the system: Across multiple requirements from the customers, the IT team

need to point out which requirement is high level. After that, among all high-level

requirements, the team will again have to choose which aspects they need to focus on.

They must be crucial part of the system and without it, the system cannot run normally

  • Budget: Budget is important things to consider when working on a project. When

receiving the list of requirements, the product owner will have to estimate the cost

needed of each requirement and decide which requirement will be executed

  • Team skillset: The skill of the IT developer will also play into scoring the items during

MoSCoW analysis. If the requirement required advanced skills to be done, then the

prioritization of the initiative will also be lower if it is not necessity

  • As the head of IT department, Flo will be responsible for holding the MoSCoW methods

between developers. All requirements should be prioritize using the 60- 20 - 20 rule, which

means that 60% of the requirements will be marked as Must-have and 40% left divided equally

for Should-have and Could-have.

  • We will calculate the total effort of the IT department
    • Assume developers: 6 people
    • Working hour per day: 8 hours * 6 = 48 hours
    • Number of working day: 3 months * 20. working day = 60 days
    • Total effort = 48 hours * 60 days = 2880 hours

also takes a fair number of resources to deploy, so this function will be

marked as could-have

Requirements

ID

Task break-down Estimated

hour

BL-RQ- 3 - Understand the organization's banking system and gather

requirements: 150 hours

  • Design the system architecture, including software and hardware

components, determine integration points between 2 system: 100 hours

  • Develop the code for the system: 250 hours
  • Testing, training and documenting: 100 hours

600 hours

BL-RQ- 9 - Research existing e-sports categories and analyze their popularity,

potential for growth and target audience: 100 hours

  • Code function: 100 hours

200 hours

BL-RQ- 10 - Research the current criteria for each e-sport category and develop a

plan for consultation: 100 hours

  • Hold consultation sessions with the scholarship application,

management team, experts to discuss about the criteria and identify any

gaps: 25 0 hours

  • Documentation, feedback and revision: 100 hours

45 0 hours

BL-RQ- 11 - Determine basic criteria needed for each scholarship: 50 hours

  • Create standard preliminary application forms: 50 hours
  • Testing and revision: 50 hours

150 hours

BL-RQ- 13 - Understand requirements and system design: 150 hours

  • Develop real-time application management system: 200 hours
  • Testing and documentation: 100 hours

450 hours

BL-RQ- 20 - Design user interface: 50 hours

  • Coding for function: 50 hours

100 hours

BL-RQ- 21 - System design: 100 hours

  • Develop notification system: 150 hours
  • Testing: 50 hours

300 hours

BL-RQ- 22 - Form design: 50 hours

  • Develop measurement for customer sensitive data (encrypted,

authorization, limited actions of admin, etc.): 15 0 hours

  • Write regulations about how customer’s data will be use: 50 hours

250 hours

BL-RQ- 33 - User experience design: 100 hours

  • E-sport knowledge research: 100 hours
  • Develop additional features to improve user experience: 1 0 0 hours
  • Optimize system UI: 100 hours

40 0 hours

Total hours: 2900 hours

4. Role of data controller within the organization

  • Brightstar (BL) is a charitable organization in UK that host fundraising events to secure funds

for academic and sports scholarships. Basically, the company play a role as the middle-man,

which connect students with scholarships they want to achieve. For this reason, the amount of

information they stored in their system is huge, including student’s personal information,

scholarship information, university and so on.

  • Because BL is located in the UK and processes personal data is part of their business, the

company must comply with the GDPR. Therefore, the company needs to have a data controller.

The main responsibility of data controller is to taking the necessary organizational and

technological steps to ensure that the processing is done in accordance with the General Data

Protection Regulation and to be able to prove it.

  • In case of the BL company, the data controller will have to inform the customer that their data

is being collected by the company for reasons that complied with 7 fundamental principles has

been listed above. They have to ensure that customer can use their rights to access,

rectification, deletion, restriction of their personal data and so on. These data also have to be

secure with proper technical measurement which are deployed by the data controller. Besides,

there are many other things the data controller needs to do in order to finish their jobs, for

example choosing appropriate processors, notify data breaches, data protection fee, etc.

5. Legal, Social, Ethical and Professional issues (LSEPI)

5 .1 Legal issue

  • Anything that occurs that has legal ramifications is referred to as a legal issue. It is a question

or issue that the law responds to or fixes. BL is an organization that hosts fundraising events to

secure funds for scholarships. It allows student to apply for the scholarship want to. Because

information is an important aspect of the system, BL have to keep an eye on is candidate data,

especially sensitive information. BL must follow the GDPR principles and announce to the user

when the company collect personal data.

  • A data controller is also needed inside the system to comply with GDPR. Data controller will be

the one ensures that these data are used in proper ways and secure within the GDPR principles.

Failed to do this will result in a massive penalty for the company

5 .2 Social issue

  • Social issues are difficulties and issues that occur in the social and physical environment and

have a detrimental effect on people's wellbeing and the well-being of society as a whole. One

of the social issues in the fundraising business, including BL company is that there is a chance of

prejudice and exclusion occurring throughout the scholarship and award selection process.

Qualified applicants from underrepresented populations may be missed or rejected from

funding opportunities as a consequence of unconscious prejudices and structural hurdles. An

example of this phenomenon is the gender inequality. At some places, there is still prejudice

about men and women, which assume that men tend to be better than women in many

different aspects. A solution that BL can apply in this scenario is an open-application scholarship

for everybody with equal conditions to both genders. This will help eliminate the prejudice

while ensuring that both men and women will have the same opportunity.

5 .3 Ethical issue

  • BL is a charitable organization that deal with fundraising, scholarship application and

management. The company should be very transparent about raising funds, as it is critical to be

clear about everything. The company should public necessary information about the funds such

as when and how funds are released, or how to keep track of funds. When the information is

updated, for example be available on the website or automatically send to customer email, it

demonstrates to the public that they are trustworthy and instills faith in them. This will attract

more donors as well as students to use the service and make the business growth.

5 .4 Professional issue

  • A difficulty or conundrum that people or organizations encounter in the course of their

professional duties is referred to as a professional issue. These challenges or conundrums are

frequently connected to ethical or moral issues. In this scenario, the professional issue will

mainly in the IT department. Flo, who is the head of IT division, has decided that he will issue

Agile approach for this project. Because Flo has just completed his course on Agile approach

and does not have any experience using it, it might be challenging for him to play the role as

the leader and guide his team. This will be also difficult for the whole team if they have not

participated in Agile approach before, since they cannot do anything to help Flo.

  • For this reason, BL might have to recruit a product manager. It is responsibility of product

manager to be the person in charge of overseeing the project and making sure it is finished on

schedule and within budget. Flo would be a great technical coordinator managing the technical

aspect of the project, but since he does not have any experience, being a product manager

might be overwhelming. Although hiring an additional product manager can be more

expensive, this ensure that the project will be completed on time and make the process

become a lot easier.

6. British Computer Society Code of Conduct

  • The British Computer Society (BCS) Code of Conduct is a set rules and professional standards

to direct the behavior of its members in professional matters. It set out the professional

standards required by BCS as a condition of membership, apply to all members, irrespective of

their membership grade, the role they fulfil, or the jurisdiction where they are employed or

discharge their contractual obligations (Trustee Board, 2022)

6.1 Public Interest

  • This concept related to the to the welfare, prosperity, and advantages of the province's

general populace to the welfare, prosperity and advantages of the general public. It is often

professional obligations with due care. Information about how candidate data will be used

must be also publish to the user

7. Conclusion

  • After the studying of this subject, I have come to understand how crucial it is to evaluate and

assess requirements when working on a project. I have developed the skills to analyze the

requirements from customer, point out which is functional and non-functional requirements,

distinguish between high-level requirements and the other, etc.

  • Knowledge about Agile methods, in particular the DSDM framework is also what I have gained.

Which scenario to apply a specific Agile method, the process of DSDM, roles in a DSDM team,

how team can communicate and work effectively with each other and so on. Another thing that

is also importance is learn how to apply DSDM tools and techniques into real scenario.

Personally, the tools that bring the most benefits to me is the MoSCow methods. It provides

your team with a concrete method to demonstrate how the company is prioritizing initiatives

for your goods or projects, which function you want to focus your resources on and make the

developing process become a lot more clearly.

  • Furthermore, I have chance to access with Legal, Social, Ethical and Professional Issues (LSEPI)

in case of the BL company. These aspects are crucial and must be considered when launching a

business.

D. REFERENCES

Adetokunbo, B. a. (2013). Software Engineering Methodologies: A Review of Waterfall Model

and Object-Oriented Approach.

Brown, M. (2015). High level mandatory requirements.

Castagna, R. (2021). General Data Protection Regulation (GDPR).

Frankenfield, J. (2020). General Data Protection Regulation (GDPR) Definition and Meaning.

Gorbachenko, P. (n.d.). What are Functional and Non-Functional Requirements and How to

Document These.

Hamilton, T. (2023). Agile vs Waterfall – Difference Between Methodologies.

Stapleton, J. (1997). DSDM: Dynamic Systems Development Method: The Method in Practice.

Waida, M. (2022). A Quick Guide to the MoSCoW Method Technique.