The document outlines the requirements analysis process in software engineering, detailing five key steps: identifying stakeholders, capturing and categorizing requirements, interpreting and recording them, and obtaining sign-off. Each step involves specific techniques for effective communication and understanding of user needs, ensuring the product aligns with both technical and functional requirements. The importance of obtaining formal agreements at the end is emphasized to prevent scope creep and ensure commitment from stakeholders.

1. REQUIREMENT ANALYSIS PROCESS
SOFTWARE REQUIREMENT ENGINEERING
PREPARED BY MUHAMMAD SAAD
B.S SOFTWARE ENGINEERING (PUCIT)

2. REQUIREMENTS ANALYSIS PROCESS
A requirements analysis process involves the following steps:
Step 1: Identify Key Stakeholders and End-Users
Step 2: Capture Requirements
Step 3: Categorize Requirements
Step 4: Interpret and Record Requirements
Step 5: Sign off

3. STEP 1: IDENTIFY KEY STAKEHOLDERS AND END-USERS
Start by identifying key project sponsors who hold decision-making power. Next, pinpoint end-users to
grasp their needs thoroughly. Incorporating their input ensures the development of a user-centric
product that aligns with project objectives.
Example:
In developing a new mobile banking app, the CTO acts as the key sponsor, while bank customers are the
end-users. Engaging both ensures the app meets technical standards and user needs for a successful
launch.

4. STEP 2: CAPTURE REQUIREMENTS
Ask each of the stakeholders and end-users their requirements for the new product. To gather
requirements from stakeholders and end-users for the new product, utilize various analysis
techniques:
1. Interviews: Conduct one-on-one or group interviews with stakeholders and end-users to gather their
requirements, preferences, and expectations for the new product.
2. Surveys: Distribute surveys to stakeholders and end-users to collect feedback on their needs, pain points,
and desired features for the product.
3. Workshops: Facilitate workshops or focus groups with stakeholders and end-users to brainstorm ideas,
identify requirements, and prioritize features collaboratively.
4. Observation: Observe end-users in their natural environment or during their interactions with existing
systems to understand their workflows, challenges, and requirements.
5. Prototyping: Create prototypes or mockups of the product to demonstrate its functionality and gather
feedback from stakeholders and end-users on usability and features.
6. Use Cases: Develop use cases to describe how different stakeholders and end-users will interact with the
product and what tasks they need to accomplish.

5. STEP 3: CATEGORIZE REQUIREMENTS
Since requirements can be of various types, they should be grouped to avoid confusion. Requirements are usually
divided into four categories:
1. Functional Requirements: These define the specific tasks and features the product must perform to meet user
needs. For example, a social media platform's functional requirements might include posting content,
commenting, and messaging.
2. Technical Requirements: These encompass the technical considerations necessary for successful product
implementation, such as hardware, software, security, and performance. For instance, technical requirements for
a mobile app might include compatibility with different operating systems and encryption protocols.
3. Transitional Requirements: These outline the steps needed to smoothly transition to the new product, including
data migration, user training, and deployment strategies. For instance, transitioning to a new software system
might involve transferring existing data and conducting training sessions for users.
4. Operational Requirements: These detail the ongoing operations and support activities required for the product's
continuous functioning, such as maintenance, monitoring, and scalability. For example, operational requirements
for a cloud-based service might include regular updates, data backups, and customer support channels.

6. STEP 4: INTERPRET AND RECORD REQUIREMENTS
Once requirements are categorized, it's crucial to assess their achievability and document them systematically.
Utilize these techniques for analysis and interpretation:
1. Define Requirements Precisely: Ensure requirements are clear, detailed, and aligned with business needs.
2. Prioritize Requirements: Rank requirements based on criticality, distinguishing between essential and desirable
features.
3. Conduct Impact Analysis: Assess the implications of requirements to understand their consequences thoroughly.
4. Resolve Conflicts: Facilitate discussions with stakeholders to address conflicting requirements and explore
scenario based solutions.
5. Analyze Feasibility: Evaluate product feasibility based on gathered requirements to ensure reliability and identify
potential issues.

7. STEP 5: SIGN OFF
After reaching a consensus on requirements, it's vital to obtain signed agreements from key
stakeholders. This ensures alignment and prevents scope creep or uncontrolled growth in the project.
Signed agreements serve as a formal commitment, providing clarity and stability throughout the project
lifecycle. By obtaining these signatures, all parties acknowledge and commit to the agreed-upon scope,
reducing the likelihood of misunderstandings or disputes later on."