Requirments Engineering

Question 1

What is a requirment?

Answer 1

Statement about one feature of system expressed with natural language/ Model Based(Graphs, Forulas, Pseudo-Code)

Question 2

Requirment elicitation

Answer 2

Determine requirments for your system
usually hard-> lack domain knowledge
stackeholders don’t know what is a possible feature

Question 3

What is a stakeholder?

Answer 3

Person who influences the system or impacted by the sysyem
Person who has interest in the system under development
Developers also stakeholders

Question 4

Elicitation tehniques

Answer 4

Interview
Questionnaires
Writing scenarios
Contextual Inquiry
Brainstorming

Question 5

User requirments

Answer 5

Statements(natural language+diagrams) od what services the system is expected to provide for users

Question 6

System requirment

Answer 6

Detailed description of softwware system’s functions, services, operational contrains(how system provides this)

Question 7

Functional Requirments for ISBN

Answer 7

-The system shall provide a search function that allows users to search for
books by title, author or ISBN
– The search results shall display a list of books matching the search criteria,
including the book title, author, ISBN and availability status.
– The system shall allow users to filter search results by genre, publication
date and customer ratings.

Question 8

Non-functional requirments for isbn

Answer 8

-The search feature should return results within 2 seconds for up to 100,000
books.
– The system shall be able to handle up to 500 simultaneous search
requests without degradation of performance

Question 9

Requirment vs Functionality difference

Answer 9

Requirment -> something that someone wants from the system
Functionality-> Something that the system exhibits

– A requirement can require a functionality from the
system.
– There are requirements that are not functionalities.

Question 10

Functional vs non Functional Requirments

Answer 10

Functional
– What services the system should provide
– How the system should react to particular inputs
– What the system shouldn’t do

Non-functional
– Constraints on the services or functions offered
– Timing contraints
– Constraints on the development process
– Constraints imposed by standards

Question 11

Non Functional requirements classification:
Product requirements
Organizational requirements
External requirements

Answer 11

Product requirements: Specify that the product must behave in a particular way. Examples:
performance requirements on how fast the system must execute and
how much memory it requires, reliability, etc.

Organizational requirements
These requirements are broad system requirements derived from
policies and procedures in the customer’s and developer’s organization.
Examples:
* Process standards used
* Programming language
* Operating System

External requirments:
Arise from factors which are external to the system and its development
process
e.g., legislative requirements (such as GDPR

Question 12

What are SMART requirments

Answer 12

Specific-goal is concrete and tangible
Measurable- is an objective measure of success
Achievable- achievable with the resources available
Time related- Includes a timeline for expected results

Question 13

process requirment analysis

Answer 13

Identify stakeholders and use elicitation techniques to find requirments

Classify the requirements in function and non functional requirements. Non functional can be further organized in product organizational external

Make an agreement on the priorities for the requirements

Output the requirement specification document

Question 14

Prioritization se face cu MoSCoW

Answer 14

Must have - critical to the current delivery time-box

Should have- important but not as time-critical, delivered in future time-box

Could have- desirable but not necessary. Usually improves user or customer experience

Won’t have- least critical by stakeholders. Considered for future versions of the project

Advantages:
-simple
-helps in managing scope
-easy to communicate with stakeholders

Disadvantages:
– Does not help decide between multiple requirements in
the same priority.
– Ambiguity over timing for won’t haves
– Political focus on building new features over techincal
improvements

Question 15

Prioritization Kano

Answer 15

Basic Needs (Must-be)
* Performance Needs (One-dimensional)
* Excitement Needs (Attractive)
* Indifferent Needs
* Reverse Needs

• Advantages
  – Helps aligning product development with actual
  customer needs and expectations
  – Focus on delivering features that enhance customer
  satisfaction and loyalty
  – Provides insights into features that are essential, which
  can be enhanced, and which can be omitted
• Disadvantages
  – Requires customer surveys and analysis to accurately
  categorize features (time-consuming and costly)
  – May require regular reevaluation as customer
  expectations and perceptions change.

Question 16

Identufy actors

Answer 16

1)Analysis of requirred document - usually Natural Language

2)Analysis of expectations of future users
Answers -who uses main use cases
-who needs support for daily work
-who is responsible for system administration
-who has an interest in the result of the system

Question 17

Find out what the custumer actually wants ->UML caracteristics:

Answer 17

Model- image of something- Mapping
- not containing all attributes only relevant - Reduction
- need to answer questions(usefullness)-for who, why, what for Pragmatitic

Question 18

Qualitiy of a model-

Answer 18

Abstraction -reduced reprez of a system
Understandability- omit irelevant detailes
Accuracy-relevant proparties as colse as possible
Predictivebess- be predictive
Cost effective

Question 19

Diferenta dintre include and extend

Answer 19

Include- indicates that one use case requires behaviour of another-> cannot be completed without the included use case aldo being executed at least once CAND APELEZI A SE APELEAZA SI B

– Extend
* When a use case conditionally adds behavior to another
use case. Optional relationship.
* The base use case can be used without triggering the
extending use case. Under certain conditions, it will trigger
the extending use case
A CAN USE BEHAVIOUR OF B BUT DOESN’T HAVE TO