PadhaiBy Astra Cloud
Search notes and questions
Ask a doubtProgramsNoticesGPA calculatorMy studyClassroom

Tribhuvan University

BSc CSITBachelor of Science in Computer Science and Information TechnologyBCABachelor of Computer ApplicationBITBachelor of Information TechnologyBIMBachelor of Information ManagementBBABachelor of Business AdministrationBBSBachelor of Business StudiesBBMBachelor of Business ManagementBITMBachelor of Information Technology Management

Pokhara University

BE Computer (PU)Bachelor of Engineering in Computer EngineeringBBA (PU)Bachelor of Business Administration (Pokhara University)

National Examinations Board (+2)

Class 10Class 10 (SEE)+2 Science+2 Science (Class 11 and 12)+2 Management+2 Management (Class 11 and 12)+2 Humanities+2 Humanities (Class 11 and 12)
All universities and programs

Comp Computer Science

Computer ScienceNEB 2081

How do various requirement gathering techniques help in achieving a careful grasp of user needs and system requirements during SDLC's analysis phase ? [5]

5

Answer

· Based on the official syllabus and past papers
Updated
✔ Direct 1:1 communication with stakeholders (e.g., develope✔ Clarifies ambiguous requirements via follow-up questions✔ Customizable depth (structured/unstructured)1. Interviews✔ Quantitative data from large groups (e.g., Likert scale qu✔ Standardized responses for trend analysis✔ Low-cost for broad input (e.g., Google Forms)2. Surveys/Questionnaires✔ Real-time workflow analysis (e.g., watching a cashier proc✔ Identifies unspoken pain points (e.g., bottlenecks)✔ Best for process-heavy systems (e.g., manufacturing)3. Observation✔ Extracts implicit requirements from existing docs (e.g., S✔ Reveals historical context (e.g., past system failures)✔ Cost-effective for legacy systems4. Document Analysis✔ Validates assumptions via interactive mockups (e.g., Figma✔ Early feedback reduces rework (e.g., 'Does this UI match u✔ Visualizes abstract requirements (e.g., 'How should the ch5. Prototyping✔ Collaborative sessions with stakeholders (e.g., 'What’s mi✔ Rapid consensus-building (e.g., sticky-note voting)✔ High engagement but requires facilitation6. Workshops (JAD)Requirement Gathering Techniques in SDLC Analysis Phase
Comparison of 6 key techniques with real-world examples (SDLC Analysis Phase)

Various requirement gathering techniques play a crucial role in achieving a careful grasp of user needs and system requirements during the analysis phase of the Software Development Life Cycle (SDLC). Each technique offers unique advantages that collectively ensure a comprehensive understanding of stakeholder expectations and system constraints.

  1. Interviews facilitate direct communication with stakeholders, allowing analysts to clarify doubts, explore nuances, and tailor questions based on responses. This technique ensures personalized attention and deeper insights into user needs.

  2. Surveys/Questionnaires are effective for gathering structured input from a large group of users. They provide quantifiable data, making it easier to identify trends, priorities, and common pain points. This method is particularly useful when dealing with geographically dispersed stakeholders.

  3. Observation involves studying users in their natural work environment. It helps uncover hidden inefficiencies, workflow bottlenecks, and unspoken requirements that might not surface in interviews or surveys. This technique is invaluable for systems where user interaction is complex or process-driven.

  4. Document Analysis involves reviewing existing system documentation, user manuals, and historical records. It provides a foundation for understanding past decisions, compliance requirements, and legacy constraints, ensuring the new system aligns with organizational goals.

  5. Prototyping allows stakeholders to visualize and interact with a preliminary version of the system. Early feedback from prototypes helps validate assumptions, identify usability issues, and refine requirements before significant development efforts are undertaken. This iterative approach reduces the risk of costly revisions later in the SDLC.

  6. Brainstorming sessions encourage collaborative idea generation among stakeholders, developers, and domain experts. This technique fosters creativity, uncovers innovative solutions, and ensures that diverse perspectives are considered in shaping system requirements.

By combining these techniques, analysts can mitigate biases, validate assumptions, and develop a robust set of requirements that align with user needs and business objectives. This holistic approach minimizes ambiguity, enhances stakeholder satisfaction, and lays the groundwork for a successful software development project.

Discussion

Loading…

More Computer Science questions

Which of the following is the purpose of using primary key in database ? a) To uniquely identify a record b) To store duplicate record c) To backup data d) To…NEB 2082 (MCQs)1A company needs to modify an existing table by adding a new column for employee email addresses. For this, which SQL command should be used ? a) CREATE b)…NEB 2082 (MCQs)1Which protocol is used for secure communication over a computer network ? a) HTTP b) FTP c) HTTPS d) TelnetNEB 2082 (MCQs)1Which control structure in JS (Java Script) is used to execute a block of code repeatedly based on a given condition ? a) For loop b) if else c) switch case…NEB 2082 (MCQs)1Select the invalid variable name in PHP. a) $name b) $ name c) $1name d) $name123NEB 2082 (MCQs)1The statement int number ( int a); is a ... a) function call b) function definition c) function declaration d) function executionNEB 2082 (MCQs)1

All Computer Science old questions