Professional Documents
Culture Documents
Interview Preparation
Interview Preparation
1. Requirement Collection
1.1 Interviews
1.2 Questionnaires or Surveys
1.3 User Observation
1.4 Document Analysis
1.5 Brainstorming
1.6 Role-Play
1.7 Workshops
1.8 Use Cases and Scenarios
For Existing Software
1. Interface Analysis
2. Focus Groups
3. Prototyping
Ref: https://www.jamasoftware.com/requirements-management-guide/requirements-gathering-and-
management-processes/11-requirements-gathering-techniques-for-agile-product-teams
2. Business Analysis
2.1 Business Process Modeling (BPM)
2.2 Brainstorming
2.3 SWOT Analysis
2.4 CATWOE
2.5 MoSCoW (Must or Should, Could or Would)
2.6 MOST (Mission, Objectives, Strategies, and Tactics) Analysis
2.7 PESTLE Analysis
3. Identifying issues, risks and benefits of existing and proposed solutions and
outlining business impacts
Non-Functional Requirements
Usability. This focuses on the appearance of the user interface and how people interact
with it. What colour are the screens? How big are the buttons?
Reliability / Availability. What are the uptime requirements? Does it need to function
24/7/365?
Scalability. As needs grow, can the system handle it? For physical installations, this
includes spare hardware or space to install it in the future.
Performance. How fast does it need to operate?
Supportability. Is support provided in-house or is remote accessibility for external
resources required?
Security. What are the security requirements, both for the physical installation and from
a cyber perspective?
7. Communication
1.1 VERBAL COMMUNICATION
2. Critical thinking
3. Problem solving
4. Decision making
7. Confident presenter