Mada za sehemu hiiIdentifying and analysing software development requirementsMada 3
- Collecting requirements
- Analysing requirements
- Modelling use cases
Collecting Requirements
Before building any software system, developers must first understand what the system should do and what the users need. This process of finding out and gathering information about what a system should achieve is called requirements collection or requirements elicitation. It is like an architect asking a homeowner about the number of rooms, kitchen size, and special features before designing a house. Without this step, the final system may not meet the users' actual needs.
The first step in collecting requirements is to determine who will use or be affected by the system. These individuals or groups are called stakeholders. Stakeholders can include end-users, system administrators, managers, clients, or even government institutions.
Examples of Stakeholders
Student Information Management System (SIMS):
- Students – access their academic results and personal details
- Teachers – enter student marks and view performance reports
- School administrators – manage student and teacher data and generate reports
- Parents/guardians – check their children's academic progress
- Government authorities – access statistical reports for policy-making
Hospital Information Management System (HIMS):
- Patients – book appointments and check medical records
- Nurses – record patients' vital signs and update patient conditions
- Doctors – access patient history and prescribe medication
- Receptionists – register new patients and handle billing
- Pharmacists – manage medicine stock and track expiry dates
- Hospital administrators – manage staff records and generate reports
There are several methods to collect requirements from stakeholders. The choice of technique depends on the system's complexity and the nature of the stakeholders involved.
1. Interviews
An interview involves speaking directly with stakeholders to understand their needs. Before conducting an interview, the systems analyst prepares a set of questions to guide the discussion.
Example interview for SIMS:
| Speaker | Statement |
|---|---|
| Systems analyst | What kind of student information do you usually need to access? |
| Teacher | I often need to check students' attendance, examination results, and personal details. |
| Systems analyst | What challenges do you face with the current manual system? |
| Teacher | Sometimes, students' records go missing, or it takes too long to find past performance records. |
| Systems analyst | What features would you like in a new system? |
| Teacher | A way to easily enter and retrieve student grades, attendance tracking, and automated report generation would be helpful. |
2. Questionnaires
Questionnaires are structured written questions distributed to stakeholders to gather requirements. They are useful when collecting information from many people.
Sample questionnaire questions:
-
How do you currently check your examination results?
- Notice board ☐
- Asking the teacher ☐
- School website ☐
-
Would you like a system where you can check your results online?
- Yes ☐ No ☐
-
What features would you like in the system?
- Timetable access ☐
- Fee payment tracking ☐
- Homework submission ☐
3. Observation
Observation involves watching how people currently perform their tasks to understand their challenges and needs. The analyst visits the workplace and observes the current processes while taking notes.
Example: A systems analyst visits a microfinance agent to observe how transactions are recorded, noting the steps involved in each process.
4. Document Analysis
This technique involves examining existing documents such as reports, forms, and policies to understand current processes.
Example: A systems analyst creating a loan management system reviews loan application forms and approval documents to design a system that matches the existing workflow.
5. Workshops and Brainstorming Sessions
Stakeholder groups come together to discuss system features and expectations. Brainstorming helps generate many ideas quickly through group discussion.
Activity: Gathering requirements through an interview
In pairs, role-play an interview between a systems analyst and a user to gather requirements for a Library Services System (LSS).
Procedure:
- One student plays the role of a systems analyst; the other plays a librarian or student (user)
- The systems analyst prepares at least five questions to understand the user's needs
- Conduct the interview for about 10 minutes
- Switch roles and repeat the activity
Sample questions for Library Services System:
- What information do you need to access about books?
- How do you currently track borrowed books?
- What problems do you face with the current system?
- What features would you like in a new library system?
- How would you like to search for books?
- Requirements collection is the process of gathering information about what a system should do
- Stakeholders are people or groups who will use or are affected by the system
- Different techniques (interviews, questionnaires, observation, document analysis, brainstorming) are used to gather requirements
- The choice of technique depends on the system complexity and stakeholders involved
- Always document the gathered requirements for future reference
In Tanzania, when a school or hospital wants to computerise its operations, a systems analyst must first visit the premises to interview teachers or nurses, observe how they currently record patient files or student marks, and review existing paper forms. For example, if MkSecondary School in Dar es Salaam wants a system to manage student fees, the analyst would interview the headmaster, accounts clerk, and parents to understand what features they need, such as tracking payments, sending SMS alerts for overdue fees, and generating reports—all before any programming begins.
Jinsi utakavyotathminiwaTathmini ya mchakato · Tathmini ya matokeo · Tathmini ya maarifa
Tathmini ya mchakato
- Identify stakeholders and define their roles in requirements collection.
- Conduct requirementgathering sessions.
- Document requirements in an organized manner.
Tathmini ya matokeo
Well-documented requirements list capturing functional and non-functional needs, constraints, and assumptions.
Tathmini ya maarifa
Detailed knowledge of:
Method used: The student should explain how to
- collect requirements through structured techniques such as interviews, surveys, and focus groups
Principles: The student should explain the principles of:
- active listening
- stakeholder management
- thorough documentation
Theories: The student should explain:
- Requirement Engineering theories, such as the Requirements Hierarchy (functional, non-functional, and constraints).
Circumstantial knowledge:
Detailed knowledge about:
- Data collection challenges like ambiguous requirements, conflicting stakeholder needs, and evolving requirements during collection.
Swali
What is the main purpose of requirements collection in software development?
Ingia ili kuwasilisha jibu lako na lihesabiwe katika umahiri wako.
Ingia ili kufanya mazoeziMwalimu
Umekwama? Niulize chochote kuhusu mada hii.
Ingia ili kumuuliza Mwalimu wa AI wa Sonza kuhusu swali hili.
Ingia ili kuulizaMajadiliano
Hakuna maswali bado