RENG.CHAPTER2 Flashcards

1
Q

TYPES OF REQUIREMENTS?

A
  1. USER REQUIREMENTS
  2. sYSTEM REQUIREMENTS
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

User requirements

A

User requirements are high-level statements written in nutral language

These requirements come from the clients or users to explain what they need from the system

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

User requirements readers

A

Client Managers
System-End users
Client Engineers
Constractor Managers
System Architects

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

System Requirements Readers

A

System-End users
System Archtects
Client Engineers
System Developer

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

Client Managers ( Top Managment)

A

They will review the user requirements to ensure the budget and timeline match with the project proposal

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

System-End Users

A

They will focus on understanding the features which they will use it or need it in the system

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

Client-Engineers(Developers)

A

They analyze the requirements to develope and check the needed hardware and software resourses

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

System Architects

A

They will check how the system will deployed , especially the non-functional requirements like servers or firewalls

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

Functional requirements

A

Describe what the system should do , focusing on its features and behavior

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

None-funtional requirements

A

Focus on how the system operates, ensures it meets the quality and preformance standerd , rather than wht the system must do or does

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

Problem with functional Requirements

A

FUnctional requirements sometimes include ambiguous statment which means different people may interpret the requirements in diffrenet way which leading to misinterpretation

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

Non-functional requirements about?

A

Non-functional requirements is about how the system will work

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

Goal

A

Goal is a genral idea of what the user wants or needs

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

Why these matters goals and verifiable

A

Goals help developers understand what users want. Verifiable requirements make it easier to test if the system meets those goals.

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

What is System Context?

A

System Context refers to the enviroment impact a system’s functionalities and requirements

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

What is Scope?

A

Scope is defines the main requirements and functionalities that can be designed or shaped during system development