ICT2641
ASSIGNMENT 4 2025
UNIQUE NO. 858610
DUE DATE: 2025
, Question 1
1.1 Ten characteristics of an individual requirement:
1. ID/Reference Number – A unique code for easy identification.
2. Name/Title – A short, descriptive name of the requirement.
3. Description – A clear explanation of what the requirement is about.
4. Source – Where or who the requirement comes from (e.g., stakeholder,
regulation).
5. Owner – The person responsible for the requirement.
6. Priority – How important or urgent the requirement is.
7. Status – Whether it is proposed, approved, implemented, or rejected.
8. Type – Whether it's functional, non-functional, business, or technical.
9. Rationale – The reason or justification behind the requirement.
10. Acceptance Criteria – The conditions under which the requirement is
considered successfully met.
1.2 Four uses of a context diagram:
1. Show system boundaries – It helps to clearly show what is inside and outside
the system.
2. Identify external actors – It points out users or other systems that interact with
it.
3. Visualise data flow – It shows how information moves in and out of the system.
4. Provide a high-level overview – It gives stakeholders a simple visual of how the
system fits into the larger environment.
1.3 Information typically included in an outline use case description:
An outline use case focuses on the basics of how users interact with a system. It usually
includes:
Use Case Name – Title of the use case.
ASSIGNMENT 4 2025
UNIQUE NO. 858610
DUE DATE: 2025
, Question 1
1.1 Ten characteristics of an individual requirement:
1. ID/Reference Number – A unique code for easy identification.
2. Name/Title – A short, descriptive name of the requirement.
3. Description – A clear explanation of what the requirement is about.
4. Source – Where or who the requirement comes from (e.g., stakeholder,
regulation).
5. Owner – The person responsible for the requirement.
6. Priority – How important or urgent the requirement is.
7. Status – Whether it is proposed, approved, implemented, or rejected.
8. Type – Whether it's functional, non-functional, business, or technical.
9. Rationale – The reason or justification behind the requirement.
10. Acceptance Criteria – The conditions under which the requirement is
considered successfully met.
1.2 Four uses of a context diagram:
1. Show system boundaries – It helps to clearly show what is inside and outside
the system.
2. Identify external actors – It points out users or other systems that interact with
it.
3. Visualise data flow – It shows how information moves in and out of the system.
4. Provide a high-level overview – It gives stakeholders a simple visual of how the
system fits into the larger environment.
1.3 Information typically included in an outline use case description:
An outline use case focuses on the basics of how users interact with a system. It usually
includes:
Use Case Name – Title of the use case.
