REQUIREMENTS

MANAGEMENT
COMP1787
Table of Contents
1. Section A: Management Summary.................................................................................................. 3
1.1. Introduction ............................................................................................................................... 3
1.2. Software Development Methodologies .................................................................................... 3
1.3. Agile Approach.......................................................................................................................... 3
1.3.1. SCRUM .............................................................................................................................. 3
1.3.2. Rapid Application Development (RAD) ......................................................................... 4
1.3.3. Dynamic Systems Development Method (DSDM) ......................................................... 4
1.3.4. Conclusion ......................................................................................................................... 5
2. Section B: High-level requirements analysis and MoSCoW prioritization ................................. 5
B1: Requirements Analysis .................................................................................................................. 5
B1.1: Non-High-Level Requirements .............................................................................................. 5
B1.2: High-Level Functional Requirements ................................................................................... 6
B2: Requirements prioritized. ............................................................................................................. 7
B2.1: Updated High-Level Requirements list. ................................................................................ 7
B2.2: Explanation of requirements prioritizing and timebox....................................................... 8
3. Section C: Legal, Social, Ethical and Professional Issues ............................................................. 9
C1: LSEPI Issues................................................................................................................................... 9
Legal Issues ........................................................................................................................................ 9
Social Issues ..................................................................................................................................... 10
Ethical Issues ................................................................................................................................... 10
Professional Issues .......................................................................................................................... 11
C2: BCS Code of Conduct .................................................................................................................. 11
Four BCS Code of Conduct ........................................................................................................... 11
4. Conclusion ....................................................................................................................................... 12
References ................................................................................................................................................ 13
Table of Tables
Table 1. Non-High-Level Requirements..................................................................................................... 6
Table 2. High-Level Requirements (Including Assumptions) .................................................................... 7
Table 3. Updated High-Level Requirements List with priority. ................................................................. 8
1. Section A: Management Summary
1.1. Introduction
Green Groceries, a medium-sized company known for organic and locally sourced groceries, plans
to launch an online platform to expand its market reach and promote sustainability in three months.
They have built a solid reputation by collaborating with local farmers and eco-conscious suppliers.

1.2. Software Development Methodologies

As described in the case study, there are two main ways of managing this project: Waterfall and
Agile. Planning is crucial in the Waterfall approach where a very specific scope of the project is
defined, and performance standards set. They also determine the average which is a weighted average
of all projects being undertaken and, on their completion, it will be subtracted from revenues realized
to obtain net income or profit. However, as an aside in this case study: “The company has experienced
difficulties with previous ‘waterfall’ projects.” – thus waterfall approach cannot be considered.

From here on, we will use the next alternative, the Agile method. The agile event calls for system
development that changes as conditions change through collaboration between Green Groceries and
System Concepts. Identifying the target audience and outlining possibilities, issues, and values that
need to be considered starts with the product owner. This vision is achieved by working together with
interdisciplinary teams. Nevertheless, complex software components are encouraged in agile
methodology.

1.3. Agile Approach

1.3.1. SCRUM

An agile technique called Scrum was first proposed by Hirotaka Takeuchi and Ikujiro Nonoka in
1986 with the goal of accelerating the development of commercial systems with more flexibility and
speed. Leybourn (n.d.) describes Scrum as a "framework that enables the utilization of diverse
processes and techniques," as opposed to having a particular methodology or method for creating
products. Scrum is superior to the conventional Waterfall paradigm in many ways.

It is beneficial to build the online system using Scrum in conjunction with Agile principles as it places
a strong emphasis on reducing development costs without sacrificing productivity. Scrum eliminates
waste and inconsistency in the development process by focusing on the demands of the client.
Furthermore, Scrum has a number of benefits, such as:
• Flexibility and Adaptation: Green Groceries' three-month schedule and past project setbacks
are well suited to Scrum's iterative methodology. It permits flexibility as needs change or new
information becomes available.
• Stakeholder Collaboration: Scrum encourages regular dialogue and cooperation between the
development team and stakeholders, making sure that everyone's opinions are considered
throughout the project.
• Fast Feedback Loops: Scrum's brief iterations facilitate fast feedback loops, which are in line
with Green Groceries' objective of a three-month platform launch. Frequent feedback lowers
the possibility of miscommunication and expensive adjustments.
 • Prioritizing needs: Scrum's product backlog facilitates the order of needs according to their
business value and urgency. This helps the team to meet deadlines by producing a minimum
viable product and adding new features in later iterations.
• Cross-Functional Teams: Scrum encourages cooperation between people with different
backgrounds, which complements the knowledge of System Concepts staff members. This
guarantees the provision of a top-notch platform that satisfies the standards and principles of
Green Grocery.
Unlike conventional techniques, where clients often receive functioning software at the conclusion
of the project, Scrum has a distinct delivery strategy. Working software is given at the conclusion of
each Sprint, which is a brief, time-limited iteration. This iterative methodology enables the
incremental delivery of value from the start of the project, with explicit deliverables at the end of
each Sprint. As a result, the project's worth is realized gradually rather than at the conclusion.

Over 80% of Agile projects currently use Scrum, making it one of the most popular Agile methods
(Parabol, 2024). Other agile ideas, such as the Dynamic Systems Development Method (DSDM) and
Rapid Application Development (RAD), fall under the Agile umbrella and are relevant to this project.
1.3.2. Rapid Application Development (RAD)
According to James Martin (1991), Rapid Application Development (RAD) is an Agile approach that
emphasizes timely delivery in a fast-paced environment through prototyping and iterative
development. Geeksforgeeks (2024), argues that the method gives priority to user input and program
use over careful planning and requirement documentation.

A Forbes Technology Council member (Stiner, 2016.) agrees that "minimizing development time
while maximizing progress" is an essential tactic in environments where software development is
subject to regular modifications. In a setting that moves swiftly and is always changing, the RAD
approach enables developers to quickly adapt to changing needs.

Other advantages of RAD include reduced manual coding owing to code reuse and faster testing
periods, which minimize the possibility of mistakes. This shortens the development time when
combined with short iterations. The partnership between users, developers, and clients results in a
high level of customer satisfaction.

Development procedures in Rapid Application Development (RAD) will persist notwithstanding

talks and code vulnerability resolution. In the end, the emphasis is on developers creating precisely
what the client requests. This lowers the development costs.

1.3.3. Dynamic Systems Development Method (DSDM)

The success of DSDM teams in accomplishing project goals may be attributed to the attitude "that
any project must be aligned to clearly defined strategic goals and focus upon early delivery of real
benefits to the business,” which is backed by eight additional principles (Biondi, 2021.). Rapid
Application Development (RAD) is the foundation of DSDM, an incremental and iterative Agile
methodology with governance and stringent requirements.
 DSDM offers best practice guidelines that are scalable to handle projects of any size and for any
industry, ensuring that projects are completed on schedule and under budget. The method encourages
the application of many tried-and-true techniques, including time boxing, MoSCoW prioritization,
modeling, and iterative development, and led workshops.
1.3.4. Conclusion
However, it is important for System Concepts employees to maintain control of their actions,
especially when conflicts arise with the client. Nonetheless, Scrum is most effectively executed in
environments where team members can collaborate with stakeholders while still keeping discipline.
An experienced and committed representative should be appointed for this purpose throughout the
project so as to secure ongoing involvement and decision making considering Green Groceries’
human availability problems. Within the Agile framework, giving freedom to team members in terms
of deciding and authorizing would enhance full participation and success of the projects undertaken
by teams.

2. Section B: High-level requirements analysis and

MoSCoW prioritization
B1: Requirements Analysis
B1.1: Non-High-Level Requirements
After reviewing the baseline requirements, I have requirements that do not fit in the high-level
requirements category of the system.
No Requirements Reason
Maintain at least 20 office plants as This need has less to do with the essential
part of the company’s commitment features of the web platform and more to do
to a green and healthy workspace with office administration and business
1
culture. Instead of being treated as a high-
level system need, it ought to be handled as
a distinct organizational effort.
Organize a virtual celebration on the The major purpose of the internet platform
website for the CEO’s birthday to is not to organize virtual parties. It is more
2
showcase the company’s fun and appropriate to treat it as an organizational
friendly culture task than as a high-level system need.
The company should adopt pet- The main features of the internet platform
friendly policies to create a positive have little to do with pet-friendly
and inclusive work environment regulations. It would be more appropriate to
3
meet this demand through corporate policy
as opposed to high-level system
requirements.
The development team should It has nothing to do with how the internet
participate in a team-building event platform works. This is not so much a high-
4
every quarter to foster collaboration level system need as it is more of an
and a positive work environment
 organizational practice centered around
employee engagement and business culture.
As the Marketing Director, I would The web platform does not fundamentally
like an offer or discount page so that work with an offers or discount page. It
5 we can inform our customers of the would be more appropriate to treat it as a
aforementioned lower-priority feature as opposed to a
crucial system necessity.
Table 1. Non-High-Level Requirements

B1.2: High-Level Functional Requirements

No Requirements Justification
Users should be able to register and This need is in line with the case study's
manage their accounts, including focus on the necessity for users to update
1 updating personal information and their account information and customer
preferences. registration. It guarantees accurate data and a
flawless user experience.
The system must support secure The necessity of encrypting user data and
online transactions, including ensuring the system complies with data
payment processing and order protection laws emphasizes how crucial safe
2
tracking. transactions are. Customers' confidence is
increased, and confidential data is
safeguarded.
Customers should have the option to Customers' desire to alter their minds about
modify their shopping carts and purchases is addressed by this need, which
review their orders before checkout. also gives users more control over their
3
purchasing experience. Order mistakes are
decreased, and client satisfaction is
increased.
The platform must be scalable to This rule addresses the need to manage an
handle peak traffic periods, ensuring increase in traffic of 30% to 50% during peak
4 optimal performance and reliability. hours. It avoids system outages during times
of heavy demand and ensures continuous
service delivery.
The system should provide multiple Customers' convenience is increased, and
delivery options, allowing different delivery preferences are
customers to choose delivery slots accommodated by providing options for
5
and enter separate delivery and delivery slots and allowing for separate
invoice addresses. address entries. Both order accuracy and user
happiness are increased.
Implement a robust data encryption In addition to guaranteeing compliance with
mechanism to safeguard user regulatory requirements like the Data
6
privacy and comply with data Protection Act, this need addresses the
protection regulations. necessity to encrypt all user data. It reduces
 the possibility of data breaches and
safeguards critical information.
Maintain consistent branding Maintaining consistency in branding
elements and design across the enhances consumer recognition and fortifies
7 website to reinforce the company's the company's reputation. It increases
brand identity. consumer familiarity and trust, which
strengthens brand loyalty and legitimacy.
Provide responsive customer In order to handle customer problems and
support through various guarantee a great user experience, timely
communication channels, including customer care is crucial. It increases client
8
email, chat, and phone, to address satisfaction and retention by fostering loyalty
inquiries and resolve issues and trust.
promptly.
Incorporate analytics and reporting Analytics and reporting features are essential
features to track website for tracking platform efficacy, seeing
performance, user behavior, and patterns, and refining corporate tactics. It
9
sales metrics, enabling data-driven increases operational efficiency and helps
decision-making and continuous make well-informed decisions.
improvement.
Table 2. High-Level Requirements (Including assumptions)

B2: Requirements prioritized.

B2.1: Updated High-Level Requirements list.
No Requirements Priority Timebox
Users should be able to register and manage
1 their accounts, including updating personal Must have 3 Days
information and preferences.
The system must support secure online
2 transactions, including payment processing Must have 5 Days
and order tracking.
Customers should have the option to modify
3 their shopping carts and review their orders Must have 3 Days
before checkout.
The platform must be scalable to handle
4 peak traffic periods, ensuring optimal Should have 7 Days
performance and reliability.
The system should provide multiple
delivery options, allowing customers to
5 Should have 5 Days
choose delivery slots and enter separate
delivery and invoice addresses.
Implement a robust data encryption
6 mechanism to safeguard user privacy and Must have 3 Days
comply with data protection regulations.
 Maintain consistent branding elements and
7 design across the website to reinforce the Should have 5 Days
company's brand identity.
Provide responsive customer support
through various communication channels,
8 Could have 7 Days
including email, chat, and phone, to address
inquiries and resolve issues promptly.
Incorporate analytics and reporting features
to track website performance, user
9 behavior, and sales metrics, enabling data- Could have 9 Days
driven decision-making and continuous
improvement.
Table 3. Updated High-Level Requirements List with priority.

B2.2: Explanation of requirements prioritizing and timebox.

The capacity to determine which activities and goals are more crucial to a project and to give those
tasks and goals top priority is known as prioritization. It is the solution to issues with time
management. To maximize your time, you don't need to work more quickly or close productivity
gaps. The proper items should be the focus of your time. (Johnson, 1998).

The DSDM method of MoSCoW prioritization aids in comprehending and controlling needs. It
supports groups in moving forward and meeting deadlines. The technique is frequently employed to
assist important stakeholders in appreciating the importance of projects in a particular release.

Understanding the work that needs to be done is essential to moving forward and fulfilling deadlines
in a DSDM project when the time has been set. Prioritization was used with these specifications.

When it came to resolving issues with more straightforward approaches to prioritization—such as the
use of "Must Have, Should Have, Could Have, or Won't Have this time"—the MoSCoW technique
performed especially well. It did this by giving a clear indication of the completion expectations.

The foundation of the eight principles of the DSDM approach is, first and foremost, the belief that
"best business value emerges when projects are aligned to clear business goals, deliver frequently,
and involve the collaboration of motivated and empowered people."

Before devoting much time to major development, the project might benefit from a solid foundation
that allows for an early knowledge of the challenges and their recommended solutions.

For example, various incorrect criteria for website development were originally included in the
baseline requirements. These criteria were sorted to determine "High-Level Requirements" using
MoSCoW Prioritization. This approach defined the scope of target deliverables based on the principal
objective of providing a working system within the specified period, with the remaining features
scheduled for incremental deployment.
.
 High-level criteria were then determined and added to the list after being evaluated and given
assumptions based on the case study. Consequently, crucial functional and nonfunctional needs for
the new system were identified.

The prioritization process is explained by the following criteria:

• Must have: These prerequisites must be met to provide a working system. It would be useless to
introduce the new system without the team implementing these activities, thus they are necessary.
• Should have: These were categorized as those specifications that, given the constraints of time and
people, need to be carried out whenever feasible.
• Could have: Those that were determined to be unnecessary for the system's primary operation.
These are good qualities to have, but only if you have the extra time and money to put them into
practice.
• Won’t have this time: were decided not to be implemented right away and were postponed. A
feature in this category indicates to the development team that it is not a top priority for the duration
of this project. This does not imply, however, that you should ignore them. They are recorded for
further examination.
Besides MoSCoW being applied to prioritizing the requirements, the updated requirements list also
applied the Timebox rule. While the MoSCoW rule prioritizes the importance of requirements in the
project, the Timebox rule is mainly to limit the time spent on each task. The Timebox rule is based
on the complicated requirements and its priority to set the maximum time for each task. This helps
System Concepts focus on completing tasks within a set timeframe, preventing scope creep and
ensuring the delivery date.

3. Section C: Legal, Social, Ethical and Professional Issues

This section explains how the established system affects social, legal, ethical, and professional
concerns. It also explains how the BCS code of conduct helps to prevent certain difficulties that may
arise from the Data Protection Act of 1998 being violated.

C1: LSEPI Issues

Ignoring legal, social, ethical, and professional considerations poses a risk to any systems
development project. It is not an afterthought; rather, it is a crucial component of the development
process from the start. To minimize risks and minimize liabilities, system developers must
comprehend the extent of their organization's legal and ethical obligations. They need to be aware
of emerging and new concerns, stay current on laws and regulations, and have a solid awareness of
the legal contexts of today.
Legal Issues
A component of the Green Groceries system will manage its users' personal data. The sixth principle
of the Data Protection Act of 1998 requires that customer data be handled and used in accordance
with data protection legislation. Private information must be protected from internet risks, kept
secret, and available only to authorized personnel. Mishandling or illegal change of this data might
result in legal consequences for the relevant parties.
.
In the case study, the customer has the right to choose whether to share their marketing information
to avoid receiving excessive junk mail. It is against the legislation to send unsolicited marketing
materials or direct marketing. As such, the system should give the customer the option to subscribe
to the service or not.

Another example of a case study is the personal payment information and details. It is against the
law to see user’s private information without their consent, although the system could hide the
information from employees, it could be exposed due to cyber-attacks. Therefore, encrypting user’s
personal information is very important in every website, especially e-commerce websites like Green
Groceries.
Social Issues
Green Groceries’ platform is developed in response to business demands. Like many other e-
commerce websites, this platform also collects and stores customer data even if not intentionally or
for the user’s satisfaction like remembering the delivery location, remember user’s credit card
information, and so on. This raises concerns about data privacy and security. If this problem is not
managed properly, sensitive information could be at risk of leaking or cyber-attack, leading to
privacy violations and loss of trust among customers. Luckily, this could be somewhat prevented by
encrypting user’s information.
Another issue that this online platform could affect is the local communities. The online platform
will indeed increase Green Groceries’s reach but it could also unintendedly harm the community
cohesion and the local economy.
Ethical Issues
According to Mason (1995), ethical problems occur when one party acts in a way that substantially
interferes with the ability of another party to accomplish its objectives. Controllers are required by
law and ethics to maintain confidentiality and privacy when collecting consumer data, allaying any
worries that personal information may be misused. Unless the person already possesses this
information, the controllers are required to notify people about how their data is processed.

According to the Data Protection Act of 1998, people who collect and use personal data are required
to be transparent about their plans for handling it. This includes processing personal data in a way
that respects the rights of the subject, securing the data, and ensuring that it is not transferred overseas
without sufficient protection.

Onto the case study, users of the Green Groceries’ website before signing up, must be aware of the
terms of service and conditions so they know what their information will be used for and that they,
at their own will, agree with the terms of service and conditions. This then legalizes the use of any
customer data provided in the system by the company.

One other aspect of Green Groceries’ website is that it must be safe and secure. This lies on the
System Concepts company to ensure that the system is secure to keep private information. This
includes encrypting private information, setting up firewalls, etc.
 Professional Issues
Every profession has its own set of rules and regulations that must be followed. Expert responsibility
We may try to guarantee that those in charge of ensuring the safe operation of these systems will
make every effort to guarantee that systems are safe and will reduce risks by fostering a strong sense
of professional accountability (Davison, 2000). The British Computer Society Code of Conduct is
something that an IT worker must adhere to maintain a certain degree of responsibility and
dependence. A practicing IT professional should follow the following guidelines to make sure they
are doing it appropriately.

• Duty to the Profession: Participate in and uphold professional standards to aid in their
development and advancement.
• Duty to Relevant Authority: When possibilities present themselves, the idea aims to include all
societal sectors and encourages equitable access to the advantages of information technology.
• Public Interest: This guarantees that the public's interests—health, privacy, security, and the
environment's and people's inherent well-being—are not violated.
• Professional Competence and Integrity: Don't take on projects that are outside of your
professional skill set; instead, stick to what you are trained or knowledgeable in.
This professional issue mainly falls on the System Concepts team instead of both sides like all the
mentioned issues above.

C2: BCS Code of Conduct

The British Computer Society, or BCS for short, is a professional association that makes sure the
legal, moral, and social concerns about the IT business are adhered to and guarantee that the right
procedures are followed in the UK. An organization of individuals in a studied profession who are
tasked with upholding supervision or control over the acceptable conduct of their trade is known as
a professional body ("Analytic Quality Glossary," n.d.).

The BCS, as a professional organization, oversees establishing guidelines and standards that govern
its members' conduct in work-related situations. "The Chartered Institute for IT 2018, Code of
Conduct" (2018), states that it is governed by a Code of Conduct that "defines the characteristics of
practitioners who are dedicated to building a responsible computing profession." Four fundamental
ideas comprise the code.

Four BCS Code of Conduct

• The Public Interest:

Concerns about security and privacy are crucial in the IT sector. Take the Green Groceries online
store, where consumers use online payment processors like VISA or PayPal to make their
purchases. Green Groceries also ask for the personal address to deliver the item. Since this
information is sensitive, questions about the trustworthiness of the data collection process and the
system's security are raised. Protection of such data ought to be considered from the outset of system
construction.
 • Duty to Relevant Authority:
An IT project manager is aware that technological problems and poor management are to blame
for the software development project's delays and overspending. Even if upper management is
pressuring the project manager to keep the status a secret, the manager understands that they have
a responsibility to pertinent authorities, such as regulatory agencies and stakeholders. They
facilitate responsible and informed decision-making by being open and honest about the project's
difficulties, dangers, and possible effects.

• Duty to the Profession:

A prominent industry association hosts a professional development program that a data scientist
attends. By exchanging expertise, working together, and providing guidance, data scientists
advance the field and encourage a culture of ongoing innovation and learning. Data scientists
respect professional standards, encourage ethical practices, and contribute to the profession's
overall growth and reputation by carrying out their professional obligations.

• Professional Competence and Integrity:

A crucial weakness in a client's network architecture is found by a cybersecurity specialist. Rather
than taking advantage of the weakness for their benefit or going unnoticed, the consultant notifies
the customer right away and offers suggestions for fixing it. The consultant exhibits honesty,
dedication, and a commitment to protecting the client's interests and sustaining the profession's
confidence by upholding professional competence and integrity.

4. Conclusion
The study concludes by offering a detailed analysis of software development practices, requirements
management, and prioritization strategies relevant to the Green Groceries online platform project. The
use of the Agile method in particular Scrum is advocated for because it iteratively promotes
stakeholder collaboration. MoSCoW priority setting technique was used in the research to identify
strategic functional needs that are crucial to the project's success. This also highlights how important
it is to address Legal, Social, Ethical, and Professional Issues (LSEPI) that come naturally during
systems development by showing some examples from the case study. By following the BCS Code of
Conduct there is promotion of public interest, professional competence and integrity, duty towards
relevant authority as well as duty towards the profession.

The paper also highlights how important it is to follow ethical guidelines, handle needs methodically,
and adhere to legal criteria to complete the Green Groceries online platform project. The project could
provide benefits like; increasing stakeholder engagement, improving system reliability, or even
enhancing customer confidence by considering vital functional requirements and recognizing
importance of moral virtue. The study acts as a complete manual for project stakeholders outlining
key elements required in successful development and implementation of Green Groceries online
platform while ensuring conformity with legality, social responsibility and professional ethics..
References
Analytic Quality Glossary [online], n.d. Available at: Analytic Quality Glossary
(qualityresearchinternational.com) [Accessed 4.11.24].

Biondi, H., 2021. What is DSDM in Agile? Guide to the 8 Principles of this framework [online].
Available at: What is DSDM? Learn the 8 Principles of This Agile Framework (appvizer.com)
[Accessed 4.11.24]

BCS, The Chartered Institute for IT 2018, Code of Conduct, PDF,

https://cgi.csc.liv.ac.uk/~leszek/COMP702/BCS_CoC.pdf. [Accessed 4.11.24]

Davison, R.M., 2000. Professional Ethics in Information Systems: A Personal Perspective. CAIS, 3.
Available at: "Professional Ethics in Information Systems: A Personal Perspective" by Robert M.
Davison (aisnet.org).

Johnson, C.R., 1998. CEO logic: how to think and act like a chief executive. Career Press, Franklin
Lakes, NJ.

Leybourn, E., n.d. Introduction to Agile Methods- Released under Creative Commons. Available at:
Introduction to Agile Methods - Released under Creative Commons – The Agile Director.

Martin, J., 1991. Rapid Application Development. Macmillan

Mason, R.O., 1995. Applying ethics to information technology issues. Commun. ACM, 38, pp.55–57.
Available at: Applying ethics to information technology issues | Communications of the ACM.

Parabol, 2024. How many companies use Scrum in 2024 [online]. Available at: How Many Companies
use Scrum in 2024? (+ Other Scrum FAQs) (parabol.co) [Accessed 4.11.24]

Stiner, S., 2016. Council Post: Rapid Application Development (RAD): A Smart, Quick And Valuable
Process For Software Developers [online]. Forbes. Available at: Rapid Application Development
(RAD): A Smart, Quick And Valuable Process For Software Developers (forbes.com) [Accessed
4.10.24].