SRE Assignment No 2

Requirements Elicitation Techniques

Submitted By: Naveed Ahmed 23K-3025

Department: Software Engineering

NOVEMBER 17, 2024

 Requirement Elicitation Techniques
 Project Type: Government Compliance Project
Selected Elicitation Techniques:
 Document Analysis
 Interviews

Justification:
 Nature of the Project: Adhering to new rules and regulations from the government, say
GDPR, demands a taxonomy because of the complex legalities involved as well as an
assurance that no part of the rules are violated. The project must achieve high levels of
accuracy to avert penalties of non-compliance.
 Key Stakeholders: Legal advisors, compliance officers, IT system architects, and
organizational end-users. Legal advisors clarify the regulations, while compliance officers
ensure that operational processes align with legal requirements.
 Effectiveness of Techniques:
o Document Analysis: Required for government agencies especially those
administering legal and business entities, political parties or any looking at
existing policies or documents. It guarantees compliance with the legal
provisions for the requirements of the project.
o Interviews: All legal advisors and compliance officers offer individual meetings
where requirements of regulations are explained in detail and often, certain
issues can be clarified. This makes it easy to address all issues that may be raised
by any other stakeholder.

 Project Type: Social Media Platform

Selected Elicitation Techniques:
 Focus Groups
 Prototyping

Justification:
  Nature of the Project: To create a successful social media platform for teenagers and
young adults one must have to consider trends, likes and use of the platform. This is set
to ensure high level engagement and to incorporate new features that will successful
captivate the market competition.
 Key Stakeholders: The target audiences of the site design will be teenagers and young
adults who will be its end-users, web designers and users involved in the creation of the
UI/UX design, managers of the site and application, as well as communication and
marketing departments. End-users offer information about requirements which should
be met by the system and designers and managers move this into functional
requirements.
 Effectiveness of Techniques:
o Focus Groups: Target users give qualitative responses to the proposed features
and designs in the overall design plan. It will help to understand preferences,
pains, and possible gains.
o Prototyping: Developing early-stage visual representations (e.g., mockups or
clickable prototypes) allows iterative testing of functionality and design. User
feedback on prototypes ensures the final product aligns with expectations.

 Project Type: Enterprise Resource Planning (ERP) System

Selected Elicitation Techniques:
 Workshops
 Observation

Justification:
 Nature of the Project: In the context of a large manufacturing company, the use of an
ERP system means combining processes in finance, HR or inventory, for example. The
challenge comes in trying to make the various processes run in harmony and integrate
data from different organizational units.
 Key Stakeholders: Leaders of departments, regular employees in the organization, IT
staff, and business analysts. Department heads offer process level information while
employees offer operational problem perspectives.
 Effectiveness of Techniques:
 o Workshops: Aids in the ability of multiple stakeholder groups to share
information to uncover issues and provide feedback on the needs. Workshops
are effective across teams because the goal is similar for all involved: they align
their departments.
o Observation: Taking a look at how employees work helps in getting an insight of
the current working environment, potential bottlenecks, and user’s behavior
that might not be possible to get out of them especially when holding a
discussion.

 Project Type: Small Business Website

Selected Elicitation Techniques:
 Interviews
 Brainstorming Sessions

Justification:
 Nature of the Project: Designing information-only site for a bakery involves establishing
the owner’s goals and aesthetic direction. The project requires low components but high
visibility of offered products by the bakery.
 Key Stakeholders: Bakery owner and possibly all the potential buyers. The owner gives
information related to business requirements while potential customer dictate design
choices that are client-oriented.
 Effectiveness of Techniques:
o Interviews: Discussions with the owner help identify specific requirements such
as design preferences, content needs, and branding goals.
o Brainstorming Sessions: Sharing time with the development team results into
coming up with additional features for the website employing creativity in
aspects to do with design of the website.

 Project Type: Healthcare Management System

Selected Elicitation Techniques:
 Surveys/Questionnaires
  Interviews

Justification:
 Nature of the Project: Designing a patient management system for a hospital therefore
entails guarantees of data security, ease of use and functionality of the system. The
system should be designed for medical staffs, administrative personal and patient.
 Key Stakeholders: Doctors, nurses, managers, technical employees, and patients. Each
group also has some requirements for the schedule convenience, the availability of
records, the durability of systems and others.
 Effectiveness of Techniques:
o Surveys/Questionnaires: Using paper-based questionnaires disseminates wide
feedback on the features of system and usability needs from a pool of
respondents.
o Interviews: Detailed discussions with doctors and administrators uncover critical
needs, such as compliance with healthcare standards and efficient appointment
handling.

 Project Type: E-commerce Platform Redesign

Selected Elicitation Techniques:
 Workshops
 Prototyping

Justification:
 Nature of the Project: The transformation of an existing streaming service includes
improvement of the UX and the addition of new elements such as AI-based suggestions.
The above project is to retain the existing users and at the same time attract more users
unto the system.
 Key Stakeholders: Current users, product managers, designers, and developers. User
feedback highlights pain points, while product managers prioritize features.
 Effectiveness of Techniques:
o Workshops: Stakeholders collaboratively refine feature ideas and prioritize
system requirements.
 o Prototyping: Visual mockups and interactive prototypes enable users to test new
designs and features, providing valuable feedback for iterative improvement.

 Project Type: Educational Mobile App

Selected Elicitation Techniques:
 Focus Groups
 Prototyping

Justification:
 Nature of the Project: The app should offer fun methods and approaches to learning,
more suitable for primary school children while at the same time giving progress
information to the teachers and parents.
 Key Stakeholders: Students, parents, teachers, and education experts. Teachers provide
curriculum insights, while parents and students focus on usability.
 Effectiveness of Techniques:
o Focus Groups: Facilitates collecting multiple opinions to develop an interesting
and utilitarian application; preferences and usability concerns are discussed
during student and teacher meetings.
o Prototyping: Interactive prototypes allow users to test features like quizzes and
progress tracking, ensuring the app meets educational and usability goals.

 Project Type: Smart Home Automation System

Selected Elicitation Techniques:
 Observation
 Prototyping

Justification:
 Nature of the Project: Smart Home System can be defined as the advanced system that
should learn and discover interaction between users and existing devices with simple
and intuitive control capability.
 Key Stakeholders: Homeowners, product designers, and technical teams. Homeowners
provide insights into preferences, while designers ensure usability.
 Effectiveness of Techniques:
o Observation: Observing how users engage in existing systems brings out issues
of usability and potential solutions.
o Prototyping: Early-stage prototypes of mobile app controls and automation
features provide users with hands-on experience, helping refine system design.