Requirements Engineering Flashcards
What is the requirements engineering
Requirements is a process of collecting data that you want to put it in the new system to build new system
What is Requirements
These are the rules or instructions that explain what the new system must do to meet its goals.
Requirements also know as ?
Requiremnts Gethering or System Investigation
Two types or requirements
High Level Requirements and low level requiremnts
High-Level Requirements ?
The high level represent the overgoall of the system , determine during the initial planning stage by the system analyst
Low-Level Requirements
Provied the detailed functions the system must perform
Output of requirements engineering
The result of the RE process which is System requiremnets specification which document all requirement in detail
The RE process invloves some steps ?
- Collect Requirements
- Analyze Requirements
- Create SRS
What are the tools and techniques used in the requirements engineering ?
- Use Case Diagram
- Context Diagram
- Flow Chart
- State Machine Diagram
- Activity Diagram
Collect Requirements?
Collect Requirements from users and stakeholders
Analyze Requirements
Analyze and document requirements
Create SRS
Create a detailed specification of the system
Importance of SRS
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
What are these steps or stages of requirements engineering
- Requirememnts Elicitation
- Requirements Compilation
- Requirements Anlaysis and Validation
Requirements Elicitation
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
Requirements Compilation
This step ensure all requirements are gathered and organized in one place
Requirements Anlysis and Validation
After collected the requirements in this step we will reviwed and refined to ensure the requirements is auurate and feasible for implementation
TheSRS contains the following information?
- Functional Requirements
- Business Requirements
- Security Requirements
- User Requirements
Functional Requirements
THe features and functions which is the system must have to meet the needs of the users and stakeholders
Business Requirements
These are the requirements where is related to the business goals and objctives of the organization
Security Requirements
These are the requirements are related to the scurity of the system
User Requirements
These are the requirements are related to the needs and expectations of the users
How is SRS created?
The SRS is created through process called requirements engineering
The SRS Process involves?
- Collecting requirements from users and stakeholders
- Analyzing and documnting the requirements
- Creating a detailed specification of the system
How to Collecting requirements from users and stakeholders?
Understadning them needs and expectaions of users and stakholders
How to analyzing and documnteing the requirements
Break down the collected requirements , and checking for feasiblity , and documnting them clearly
How to creating a detailed specififcation of the system
Writing a clear and complete document that explains what the system should do (functional requirements) and how it should perform (non-functional requirements).
Functional Requirements
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.
Non-Functional Requirements
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.
Popular RE Tchniques
- Interview
- Questionnaires/Survey
- Research
- Observation
- Document Review
6.Sampling
What is an interview?
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
Why interview is imporatnt?
Interview helps you to understanding the users and stakholders needs from the new system
Skills required for successful interviews
You need to know how to plan, ask questions, documnet the answers ,and evaluate the information effectively
Types of Questions in
- Open-Ended Questions
- Close-Ended Questions
Open-Ended-Questions
These allow for more detailed answers and encourage free discussion
Example / مثال:
“What features would you like to add to the system?”
Close-Ended Questions
These are specific and limit answers, often used to gather facts
Example / مثال:
“How many employees use this system?”
Questionnaires / Survey
In projects where input needed from many people, questionnaires can be helpful
Research
Research is a process of researching again , looking at materials, reports, past reports, news, published papers, and books
Types of Research
- Secondray data collection
- Primary data collection
Secondray data collection
Is collecting data from existing sources
Primary data collection
Is collecting original data through some method as , interviews, questionnaires, observation
Document Review
Document Reviewcan help you to understand how the current system supposed to work .
Risk managment
In any IT project , there are risks can affect the project , and these risks handled by system analysts and project managers
What is risk managment
Risk managment is identifiying, analyzing, predicting, and monitoring risks to reduce or avoid and impact on the system
Why do projects fail?
1.The developer did not identify all risks
- The deveopler ignored the risks
- The developer did not monitor risks
- The developer did not prepare a backup plan for risks
What are the processes of risk managment
- Planning
- Risk identification
- Risk analysis
- Risk resonse
- Risk Monitoring
Risk managment strategies
- Risk Transfer
- Risk Avoidance
- Risk Reduction
- Risk Acceptance