This element focuses on the collaborative process of identifying business needs and translating them into functional specifications for a new or improved i
Topic Synopsis
This element focuses on the collaborative process of identifying business needs and translating them into functional specifications for a new or improved information system. Learners must demonstrate the ability to evaluate alternative solutions, considering factors such as cost, scalability, and user requirements. Practical application involves working with stakeholders to ensure the system design aligns with organisational objectives and delivers measurable benefits.
Key Concepts & Core Principles
- Managing information: Understanding how to handle data securely, maintain filing systems, and use information management software to support decision-making.
- Supporting business events: Planning, coordinating, and evaluating events such as meetings, conferences, and training sessions, including budget management and risk assessment.
- Implementing change: Recognising the need for change, communicating it effectively, and supporting colleagues through transitions to improve business processes.
- Managing office facilities: Overseeing the maintenance, security, and efficient use of office space, equipment, and supplies to ensure a productive work environment.
- Building stakeholder relationships: Developing and maintaining professional relationships with internal and external stakeholders through effective communication and negotiation.
Exam Tips & Revision Strategies
- Use a recognised methodology like SSADM or Agile to structure your contribution, and reference it in your evidence to show professional approach.
- Include minutes from meetings with stakeholders and annotated drafts of documents to demonstrate iterative development and your role in the process.
Common Misconceptions & Mistakes to Avoid
- Collecting requirements without prioritising them, leading to scope creep and an unfeasible system design.
- Failing to consider data protection and security requirements (e.g., GDPR) when specifying system features.
- Recommending a development option based solely on cost without assessing technical compatibility or user adoption.
Examiner Marking Points
- Award credit for clearly documenting user requirements obtained through interviews, surveys, or workshops, linking each requirement to business goals.
- Expect evidence of a structured specification document that includes functional and non-functional requirements, data inputs/outputs, and process workflows.
- Look for a comparative analysis of at least two development options (e.g., off-the-shelf vs. bespoke), evaluating criteria such as cost, integration, and long-term support.
- Credit demonstration of stakeholder engagement, such as feedback logs or sign-off sheets, confirming requirements are agreed.