Stakeholder Identification for Elicitation Process

The assignment is about identifying stakeholders to be interviewed for a mobile app development project, determining the purpose of each interview, designing structured questions, and exploring potential open tracks. The project involves developing an API, integrating data from different tables, and ensuring data integrity. The stakeholders include users, software engineers (API and DCE), and ad vendors. The assignment also involves identifying functional and non-functional requirements, providing scenarios, finding weakly conflicting requirements, and conducting risk management.

CS/SE 3RA3 Assignment 1
1. Identify the set of stakeholders to be interviewed and explain why each of them is
relevant to the elicitation process.
Answer
Stakeholders Relevance
1. Users They are the end users of the app so they need
to be contacted and their interests and
preferences need to be identified.
2. Software Engineer API They will develop the database and the APIs.
This is required for inserting the data and
fetching the data which will be done through
the APIs. Their concerns, suggestions and
skills needs to be considered before starting
this project.
3. Software Engineer DCE This stakeholder will test the data entered by
the users and he will maintain the integrity in
the database so that the data is not overloaded.
Their concerns, suggestions and skills needs to
be considered before starting this project.
4. Ad Vendor They will display the advertisements for the
app and they are the third party. So, they are an
important part of this elicitation process.
1

2. For each interviewee, determine the purpose of the interview and the type of
information to be acquired.
Answer
Interviewee Purpose of the interview Type of information
Users Their requirements need to be
identified so that the app can
suit their needs and
requirements and they are able
to use it without any problem.
Preferences of the users on the
basis of functionality and
design.
Software Engineer API To inquire about the format
that he will use to design the
database and the database
engine that he will use.
The number and the attributes
of the table that will be put in
the database.
Software Engineer DCE To inquire about the method
that will be deployed for
testing and to inquire about
the way by which data error
will be corrected.
Testing methods, type of
program for correction of the
errors.
2

Ad Vendor To inquire about the things
that they look for before
placing the ads and the
requirements of the ad vendors
for their ads.
The design of the template for
ad and the specific
requirements of the ad
vendors.
3. Design a structured set of questions for that purpose and that interviewee.
Answer
Interviewee Questions
Users 1. Are you willing to customize the offers on your phone?
2. Will you agree to share your information via the app?
3. What are the reasons for your refusal of the authentication or
the sharing of the information process?
4. Do you wish to login from many different accounts? Would
you like to access the data from more than one source like
Facebook, LinkedIn or Twitter?
5. Would you like the app to access your location so that the
offers can be displayed accordingly?
6. Would you like to have an option of not seeing certain kinds
of ads?
7. Would you like to have an option of turning off the
notifications for the ads etc.?
3

8. Would you like to have an option by which you can change
your settings within the app anytime you want?
Software Engineer
API
1. How would you normalize the database with the given
structure?
2. How do you generate API token and authenticate with that
particular user?
Software Engineer
DCE
1. How would you detect and correct the duplicate data?
2. How do you integrate the data from different tables to
minimize the number of tables?
3. How will you check the inconsistency of the information and
the errors within the data? Which attribute will you use to do
this?
Ad Vendor 1. What is the design of the template that you prefer?
2. How much space do you wish to use to place the ad?
3. How would you like your ad to be displayed? As banner? As
video in between the usage of the app? Or as a separate
window that will get open in between the app usage?
4. Identify open tracks that might be worth exploring at the end of the interview.
Answer
a. What can do done to increase the visibility of the ads and the frequency of the views of
the ads?
4

b. What can be done to improve the signing-in process of the users? How the number of
fields for the process of authentication can be reduced?
5. Identify as many functional requirements as you can.
Answer
a. During the signing-up process, the mail or the OTP should be sent to the user.
b. The location can be accesses by the GPS directly if the user allows the use of GPS in the
app.
c. If the user turns of ad notifications, then the notifications should not be displayed in or on
the app.
d. The personal data and information of the user must be encrypted.
6. Identify as many non-functional requirements as you can. For classification of
nonfunctional requirements use the pattern from Lecture Notes 4.
Answer
a. The content or the message that will be delivered to the user should contain appropriate
content and it should be sent to him as soon as possible.
b. If the user does not allow sharing of the information, then his information must not be
sent or shared with any third party.
c. The view of the app should be interactive and user-friendly.
d. In any situation, the app should not be crashed.
5

7. Provide two positive (normal) scenarios, one negative scenario and one abnormal
(positive) scenario.
Answer
Positive (normal) scenarios Negative scenario Abnormal (positive) scenario.
1. The users are able to
opt for options like
turning off and on of
the notifications,
advertisements etc.
2. The users are able to
choose the options as
per their preferences
like the type of ads
they want to see and
the location
preferences etc.
1. The app crashes
whenever the users
click on any of the off
button.
1. The users are able to
switch off the
notifications, but then
also some kinds of the
notifications are
displayed.
8. Find two weakly conflicting requirements and a boundary condition that makes
these requirements strongly conflicting. Explore alternative resolutions for the
problem.
6

Answer
Weakly conflicting
requirements
Boundary condition that
makes these requirements
strongly conflicting
Alternative resolutions for the
problem
1. The software engineer
for API will design the
database and the
software engineer of
DCE will maintain the
integrity and avoid the
duplicity of the data.
So, both of them have
to use the same
database. So, a
conflict may arise
when the data structure
of the database needs
to be changed for
rectifying the duplicity
of the data issues and
DCE does not have
access to the database
design and structure.
The database is not
normalized. The DCE is not
allowed to participate in the
designing of the database by
the API.
1. Normalize the
database.
2. Allow booth the
engineers to participate
in each other’s work
and task.
7

2. The generation of
token can be
conflicting when the
two users are signing
up at same time and
the same token gets
generated which will
not let the users’ login
or they will get
incorrect details at the
time of login.
9. Identify two risks; provide their severity of consequences using tables like Table 3.2
in the textbook. Also provide a fault tree (like Figure 3.3) for the risk you consider
bigger.
Answer
Risks Severity
1. The design of the app should fit all the
screens of the mobile phones and it
should be compatible with the screens
of the mobile phones of different
inches.
If the app is not compatible with the size of the
screen, then it is of no use. The users will fall.
The failure of server will reduce the usability
of the app and the customers will not be able to
use the app.
8

2. The server that will be purchased is not
authentic and fails again and again.
Fault tree
10. Use your imagination and provide a sample of DDP risk management for this
system. Do all calculations and provide appropriate comments.
Answer
Phases Data detection Prevention
Requirement gathering The proper and full
requirement that was gathered
could not be given
Brainstorming, interviewing to
collect full data
Making DB structure Structure not normalized Normalize the structure
9
Poor server
purchase
Break in the
comnnection
server down
for long
hours
loss of
customers
Bad service competition