software requirements

1. Requirements &
Persona

2. Learning Outcome
• LO 1: By the end of this instruction, learners will be able to identify and
analyze the key components of software requirements.
• LO 2: Upon completion of this module, students will be capable of
creating detailed and realistic user personas.

3. Introduction to Requirements
• Discovering requirements focuses on exploring the problem space and defining what will be
developed
• this includes:
• understanding the target users and their capabilities;
• how a new product might support users in their daily lives;
• users’ current tasks, goals, and contexts;
• constraints on the product’s performance
• It may seem artificial to distinguish
• in an iterative development cycle, between requirements, design, and evaluation activities are all
intertwined, with some design taking place while requirements are being discovered and the design
evolving through a series of evaluation—redesign cycles.

4. Misunderstanding or
Miscommunication

5. What are Requirements
• Necessary conditions or criteria that must be fulfilled or satisfied in
order to achieve a certain goal, complete a project, or develop a
product or service.
• Requirements outline what is expected from the end result and
provide guidance for developers to design, develop, and test solutions
that meet the established standards and desires."

6. Types of Requirements
• Functional
• Data
• Environment
• User
• Usability
• User experience.

7. Types of Requirements
• What the product should do
Functional Requirements
• Capture the type, volatility, size/amount, persistence, accuracy, and value of the required
data
Data Requirements
• or "context of use"-circumstances in which interactive product must operate
Environmental Requirements
• Characteristics of the intended user group
User Requirements
• The usability goals and associated measures
Usability Requirements
• UX have an impact on all other requirements.
UX Requirements

8. Functional
Requirement
• For example, a functional
requirement for a robot working in a
car assembly plant might be that it
is able to place and weld together
the correct pieces of metal
accurately

9. Data Requirement
• If an application for buying and
selling stocks and shares is
being developed, then the data
must be up-to-date and accurate,
and it is likely to change many
times a day

10. Environmental
Requirement
• Touch screens may impose
environmental constraints on a
user due to clothing (e.g.,
wearing gloves in cold weather),
and they may be challenging to
use while moving, such as when
riding on a subway or in a car on
a bumpy road.
• Thus, Environmental
Requirements are fundamentally
important to an interface’s
design.

11. User Requirement
• Users should be able to comfortably and effectively use an interface to
accomplish the goals that it has been designed to support.
• When you can clearly define who will be using your interface, and the
environment(s) in which it will be used, you can specify User Requirements.

12. Usability Requirement
• An interface should be easy to learn how to use
and easy to remember how to use

13. UX Requirement
• User Experience Requirements have an impact on all other requirements.
• This is because in a User-Centered Design (UCD) process, users come first.
• A user’s experience can be enhanced by adding elements of delight to user
interactions.
• Delight may manifest as unexpected (by users) shortcuts that allow a user to
complete a common task more efficiently, or through the language used on a
website — when you speak the users’ language, you gain user trust.

14. Persona
• Personas are fictional characters, which you create based upon
your research in order to represent the different user types that
might use your service, product, site, or brand in a similar way.

15. Persona
• Capture a set of user characteristics (user profile)
• Synthesized from real people based on user research
• Typical, not idealized
• Bring to life with name, characteristics, goals, and personal
background
 Relevant to product under development
• Good persona helps designer with design decisions and reminds
team about who will use the product
• Develop a small set of personas with one primary

16. Persona

17. Persona

18. Persona

19. Assignment
• Suggest some key requirements in each category above (Functional,
Data, Environment, User Characteristics, Usability Goals and User
Experience Goals) for each of the following situations.
• An interactive product use in a University's Self-service Cafeteria for
that allows users to pay for their food using a contactless card or
smartphone

20. References
• John W. Satzinger, Robert B. Jackson, Stephen D. Burd. (2016). Systems
Analysis and Design in a Changing World, 7th Edition. 7. Cengage
Cengage Learning. -. ISBN: 978-1305117204.
• Preece, J., Rogers, Y., & Sharp, H. (2019). Interaction design: Beyond
human-computer interaction. 5th edition. New York, NY: J. Wiley & Sons.
J. Wiley & Sons. ISBN: 978-1-119-54725-9
• https://www.usabilityfirst.com/about-usability/requirements-
specification/index.html

21. Thank you