Requirements Engineering Flashcards

1
Q

What is the requirements engineering

A

Requirements is a process of collecting data that you want to put it in the new system to build new system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is Requirements

A

These are the rules or instructions that explain what the new system must do to meet its goals.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Requirements also know as ?

A

Requiremnts Gethering or System Investigation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Two types or requirements

A

High Level Requirements and low level requiremnts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

High-Level Requirements ?

A

The high level represent the overgoall of the system , determine during the initial planning stage by the system analyst

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Low-Level Requirements

A

Provied the detailed functions the system must perform

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Output of requirements engineering

A

The result of the RE process which is System requiremnets specification which document all requirement in detail

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

The RE process invloves some steps ?

A
  1. Collect Requirements
  2. Analyze Requirements
  3. Create SRS
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What are the tools and techniques used in the requirements engineering ?

A
  1. Use Case Diagram
  2. Context Diagram
  3. Flow Chart
  4. State Machine Diagram
  5. Activity Diagram
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Collect Requirements?

A

Collect Requirements from users and stakeholders

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Analyze Requirements

A

Analyze and document requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Create SRS

A

Create a detailed specification of the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Importance of SRS

A

The SRS serves as a guide for deveoplers , designers, and stakeholdrs , it also ensure the system meets with needs and expectations of users and stakeholders and developed on time and within the budget

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are these steps or stages of requirements engineering

A
  1. Requirememnts Elicitation
  2. Requirements Compilation
  3. Requirements Anlaysis and Validation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Requirements Elicitation

A

Is a collecting data from users and stakeholders, this step it involves gathering requiremnets dirctly from users and stakeholders

it also know as , Requirements collection which means collect data from old system and new system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Requirements Compilation

A

This step ensure all requirements are gathered and organized in one place

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Requirements Anlysis and Validation

A

After collected the requirements in this step we will reviwed and refined to ensure the requirements is auurate and feasible for implementation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

TheSRS contains the following information?

A
  1. Functional Requirements
  2. Business Requirements
  3. Security Requirements
  4. User Requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Functional Requirements

A

THe features and functions which is the system must have to meet the needs of the users and stakeholders

20
Q

Business Requirements

A

These are the requirements where is related to the business goals and objctives of the organization

21
Q

Security Requirements

A

These are the requirements are related to the scurity of the system

22
Q

User Requirements

A

These are the requirements are related to the needs and expectations of the users

23
Q

How is SRS created?

A

The SRS is created through process called requirements engineering

24
Q

The SRS Process involves?

A
  1. Collecting requirements from users and stakeholders
  2. Analyzing and documnting the requirements
  3. Creating a detailed specification of the system
25
Q

How to Collecting requirements from users and stakeholders?

A

Understadning them needs and expectaions of users and stakholders

26
Q

How to analyzing and documnteing the requirements

A

Break down the collected requirements , and checking for feasiblity , and documnting them clearly

27
Q

How to creating a detailed specififcation of the system

A

Writing a clear and complete document that explains what the system should do (functional requirements) and how it should perform (non-functional requirements).

28
Q

Functional Requirements

A

These describe what the system must do to meet the needs of users. For example:

Features like user login, data entry, or generating reports.
Specific tasks the system should perform, like processing payments or managing inventory.

29
Q

Non-Functional Requirements

A

These define how the system should behave or perform under different conditions. For example:

Speed: How fast the system should respond.
Security: Protecting user data from unauthorized access.
Scalability: How the system can handle more users or data over time.

30
Q

Popular RE Tchniques

A
  1. Interview
  2. Questionnaires/Survey
  3. Research
  4. Observation
  5. Document Review

6.Sampling

31
Q

What is an interview?

A

It is planned meeting to ask questions and collecting information from someone, it is usually used interview in the system analysis phase of system development project

32
Q

Why interview is imporatnt?

A

Interview helps you to understanding the users and stakholders needs from the new system

33
Q

Skills required for successful interviews

A

You need to know how to plan, ask questions, documnet the answers ,and evaluate the information effectively

34
Q

Types of Questions in

A
  1. Open-Ended Questions
  2. Close-Ended Questions
35
Q

Open-Ended-Questions

A

These allow for more detailed answers and encourage free discussion

Example / مثال:
“What features would you like to add to the system?”

36
Q

Close-Ended Questions

A

These are specific and limit answers, often used to gather facts

Example / مثال:
“How many employees use this system?”

37
Q

Questionnaires / Survey

A

In projects where input needed from many people, questionnaires can be helpful

38
Q

Research

A

Research is a process of researching again , looking at materials, reports, past reports, news, published papers, and books

39
Q

Types of Research

A
  1. Secondray data collection
  2. Primary data collection
40
Q

Secondray data collection

A

Is collecting data from existing sources

41
Q

Primary data collection

A

Is collecting original data through some method as , interviews, questionnaires, observation

42
Q

Document Review

A

Document Reviewcan help you to understand how the current system supposed to work .

43
Q

Risk managment

A

In any IT project , there are risks can affect the project , and these risks handled by system analysts and project managers

44
Q

What is risk managment

A

Risk managment is identifiying, analyzing, predicting, and monitoring risks to reduce or avoid and impact on the system

45
Q

Why do projects fail?

A

1.The developer did not identify all risks

  1. The deveopler ignored the risks
  2. The developer did not monitor risks
  3. The developer did not prepare a backup plan for risks
46
Q

What are the processes of risk managment

A
  1. Planning
  2. Risk identification
  3. Risk analysis
  4. Risk resonse
  5. Risk Monitoring
47
Q

Risk managment strategies

A
  1. Risk Transfer
  2. Risk Avoidance
  3. Risk Reduction
  4. Risk Acceptance