ICT2641
ASSIGNMENT 4 2025
UNIQUE NO. 858610
DUE DATE: 2025
,Business Informatics IIA
Question 1
1.1 Ten characteristics of an individual requirement (10)
1. ID – A unique identifier for the requirement.
2. Name – A brief title summarising the requirement.
3. Description – A detailed explanation of the requirement.
4. Source – Origin of the requirement (stakeholder or document).
5. Owner – The person responsible for the requirement.
6. Type – Whether it is functional, non-functional, technical, etc.
7. Priority – Indicates the importance or urgency (e.g., High, Medium, Low).
8. Status – Current stage (e.g., Draft, Approved, Implemented).
9. Rationale – Justification for why the requirement is needed.
10. Acceptance Criteria – Conditions that must be met to satisfy the requirement.
1.2 Four uses of a context diagram (8)
1. Identify system boundaries – Clarifies what is inside and outside the system.
2. Stakeholder communication – Helps explain the system to non-technical users.
3. Visualise external entities – Shows interactions with external actors or
systems.
4. Scope definition – Defines what is included in the system scope and what is
not.
1.3 Outline use case description includes (5)
1. Use Case Name
2. Actors – Who interacts with the system.
3. Preconditions – Conditions that must be true before the use case begins.
4. Main Flow – The primary sequence of steps or actions.
, 5. Postconditions – The result or outcome after execution.
Question 2
2.1 Seven roles and responsibilities in a review group (14)
1. Author – Prepares the document and provides clarification.
2. Reviewer – Examines the content for accuracy and completeness.
3. Moderator – Facilitates the review meeting.
4. Scribe – Records defects and review comments.
5. Project Manager – Ensures the review aligns with project goals.
6. Tester – Checks for testability and completeness.
7. Customer Representative – Ensures the requirement meets business needs.
2.2 Three stages of change control (8)
1. Request for Change (RFC) – Formal submission of a proposed change.
2. Impact Assessment – Evaluation of the change’s impact on scope, cost, time,
and quality.
3. Change Approval/Decision – Approving, rejecting, or deferring the change
based on assessment.
2.3 Key features of automated support tools for managing BRDs or product
backlogs (9)
1. Version Control – Tracks changes and maintains history.
2. Traceability – Links requirements to design, development, and test cases.
3. Collaboration – Enables team members to work together.
4. Prioritisation Tools – Allows stakeholders to rank requirements.
5. Real-Time Updates – Ensures current information is always accessible.
ASSIGNMENT 4 2025
UNIQUE NO. 858610
DUE DATE: 2025
,Business Informatics IIA
Question 1
1.1 Ten characteristics of an individual requirement (10)
1. ID – A unique identifier for the requirement.
2. Name – A brief title summarising the requirement.
3. Description – A detailed explanation of the requirement.
4. Source – Origin of the requirement (stakeholder or document).
5. Owner – The person responsible for the requirement.
6. Type – Whether it is functional, non-functional, technical, etc.
7. Priority – Indicates the importance or urgency (e.g., High, Medium, Low).
8. Status – Current stage (e.g., Draft, Approved, Implemented).
9. Rationale – Justification for why the requirement is needed.
10. Acceptance Criteria – Conditions that must be met to satisfy the requirement.
1.2 Four uses of a context diagram (8)
1. Identify system boundaries – Clarifies what is inside and outside the system.
2. Stakeholder communication – Helps explain the system to non-technical users.
3. Visualise external entities – Shows interactions with external actors or
systems.
4. Scope definition – Defines what is included in the system scope and what is
not.
1.3 Outline use case description includes (5)
1. Use Case Name
2. Actors – Who interacts with the system.
3. Preconditions – Conditions that must be true before the use case begins.
4. Main Flow – The primary sequence of steps or actions.
, 5. Postconditions – The result or outcome after execution.
Question 2
2.1 Seven roles and responsibilities in a review group (14)
1. Author – Prepares the document and provides clarification.
2. Reviewer – Examines the content for accuracy and completeness.
3. Moderator – Facilitates the review meeting.
4. Scribe – Records defects and review comments.
5. Project Manager – Ensures the review aligns with project goals.
6. Tester – Checks for testability and completeness.
7. Customer Representative – Ensures the requirement meets business needs.
2.2 Three stages of change control (8)
1. Request for Change (RFC) – Formal submission of a proposed change.
2. Impact Assessment – Evaluation of the change’s impact on scope, cost, time,
and quality.
3. Change Approval/Decision – Approving, rejecting, or deferring the change
based on assessment.
2.3 Key features of automated support tools for managing BRDs or product
backlogs (9)
1. Version Control – Tracks changes and maintains history.
2. Traceability – Links requirements to design, development, and test cases.
3. Collaboration – Enables team members to work together.
4. Prioritisation Tools – Allows stakeholders to rank requirements.
5. Real-Time Updates – Ensures current information is always accessible.
