Scribd
Upload
12 views8 pages

Assignment 2 (SRE)

The document outlines an assignment on Software Requirements Engineering, focusing on requirements modeling and agile methodologies. It includes tasks such as creating various diagrams (DFD, Swimlane, State-Transition) and writing user stories for an AI-powered content delivery platform. Additionally, it details a collaborative approach for incorporating stakeholder feedback during sprint reviews to refine requirements and improve the platform.

Uploaded by

Hifza Nazir
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
12 views8 pages

Assignment 2 (SRE)

The document outlines an assignment on Software Requirements Engineering, focusing on requirements modeling and agile methodologies. It includes tasks such as creating various diagrams (DFD, Swimlane, State-Transition) and writing user stories for an AI-powered content delivery platform. Additionally, it details a collaborative approach for incorporating stakeholder feedback during sprint reviews to refine requirements and improve the platform.

Uploaded by

Hifza Nazir
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

assignment no: 2

SOFTWARE REQUIREMENTS ENGINEERING

SUBMITTED BY
HIFZA NAZIR SP23-BSE-117
SYEDA KHOULA ABID SP23-BSE-078
MEMOONA ASHRAF SP23-BSE-049
SAIF-ULLAH SP23-BSE-085

DECEMBER 25, 2024


SUBMITTED TO: MAAM AREEJ BASHIR
Part A: Requirements Modeling
(CLO3)

1. Data Flow Diagram (DFD):


o Create a context-level DFD

o Develop a level 1 DFD

2. Swimlane Diagram:
o Create a Swimlane Diagram

1
3. State-Transition Diagram:
a. Design a State-Transition Diagram

4. State Table:
a. Develop a State Table corresponding to the State-Transition Diagram,
listing states, events, and resulting actions.

2
5. Dialog Map:
Design a Dialog Map for the user registration and login process to illustrate the navigation flow
between screens or user interfaces

3
Part B: Requirements Engineering for Agile Methodologies
(CLO4)
1. User Stories:
Write at least five user stories for the key features of the application. Each user story
should follow the standard format:
As a [user role], I want to [perform an action] so that [achieve a goal].
Example:
o As a customer, I want to search for products by category and price so that I
can easily find items within my budget.

ANSWER:
User Stories:
1. As an end user, I want to receive personalized content recommendations so that I can
easily find articles, videos, or ads that match my interests.
2. As a registered user, I want to manage my content preferences (e.g., topics, categories)
so that I can further customize the content served to me.
3. As a developer, I want to integrate AI models into the platform so that personalized
recommendations are generated based on real-time user data.
4. As a business owner, I want to track user engagement metrics such as session time and
interaction rates so that I can measure the platform’s effectiveness in increasing
retention.
5. As a system administrator, I want to monitor platform performance and uptime so that I
can quickly address any outages or scalability issues.

Collaborative Requirements Engineering:


o Describe how your team will incorporate feedback from stakeholders
during sprint reviews to refine requirements.

ANSWER:
Collaborative Requirements Engineering for AI-Powered Content
Delivery Platform

4
Here’s how our team will work with stakeholders during sprint reviews to improve and
refine the platform’s requirements:

1. Involving Stakeholders
We will invite key stakeholders (like business owners, marketers, end users, and system
administrators) to participate in sprint reviews. During these sessions, they will:
 Test new features (e.g., content recommendations or dashboards).
 Share their opinions about what’s working and what needs improvement.
 Highlight any issues or suggest additional features they'd like to see.

2. Gathering Feedback
We’ll collect feedback in a few ways:
 Live demonstrations: Stakeholders can try out features and give immediate
feedback.
 Discussions: Open conversations to discuss their needs or concerns.
 Surveys: Quick forms to gather structured input, like “Is the content
recommendation accurate?”
This feedback will be carefully noted and categorized as:
 Urgent issues: Things that must be fixed immediately, like bugs or performance
problems.
 Improvements: Ideas to make the platform better, such as adding filters for
recommendations.
 Future ideas: Suggestions to explore later, like adding multilingual support.

3. Prioritizing What Matters


Not all feedback can be implemented at once. We’ll prioritize based on:
 Impact on users: Does it improve the user experience or engagement?
 Business goals: Does it help achieve key objectives like increasing revenue?
 Feasibility: Can it be done quickly without disrupting the sprint plan?

5
4. Making Changes
Based on the feedback, we’ll update our requirements, such as:
 Refining existing features (e.g., improving how recommendations adapt to user
behavior).
 Adding new user stories, like:
o “As a user, I want content recommendations that reflect seasonal trends so
that they feel more relevant to me.”
 Updating what we consider a successful outcome, like making sure 90% of
recommendations feel accurate.

5. Keeping Feedback Flowing


Stakeholders won’t have to wait until the next sprint review to see changes. We’ll:
Share early versions of updated features with them for quick feedback.
Make adjustments as needed before the next sprint ends.

6. Using the Right Tools


We’ll rely on tools like Jira or Trello to track feedback and changes. We’ll also review
analytics together (e.g., user engagement rates) to understand what’s working and what
needs attention.

Example in Action
Let’s say during a sprint review, a stakeholder notices the AI isn’t showing holiday-
specific content. They tell us:
 What’s wrong (missing seasonal relevance).
 What they’d like (recommendations that match holidays or events).
In response, we’ll:
1. Update the AI to account for seasonal trends.
2. Add a task to our backlog to improve this feature in the next sprint.
3. Show them the improved functionality in the following review to confirm it works
as expected.

6
By working closely with stakeholders like this, we’ll ensure the platform keeps improving,
stays relevant, and meets everyone’s expectations.

************************************************************************

You might also like