Requirements Specification Report for Community Concern Charity

Overview of the current system and critical evaluation of its problems

This assignment requires you to produce a requirements specification for the system outlined below.

The learning outcomes for Information Systems Engineering are as follows:

LO1: Critically assess the concepts of development stages and methods

LO2: Elicit user requirements

LO3: Evaluate possible models, designs and specify elements of existing/proposed systems

LO4: Construct and critically evaluate a system using system construction tool(s)

This individual assignment is a formal piece of work primarily assessing LOs 1 and 2, and also contributing to the understanding of LOs 3 and 4.

It is worth 50% towards your final assessment for this module (the second piece of coursework is also worth 50%). Statement You are a contract systems analyst available to local organisations that wish to hire you.

You have been approached by Community Concern, a charity, to evaluate their information system needs with a view to helping them better computerise their current systems for managing volunteers and clients, with a view to expanding their services in a sustainable manner, building on their reputation for trustworthiness, and providing better governance reports. You are to focus your report around their latest initiative which currently runs in an area of Edinburgh, but which they are hoping to roll out across the whole of Scotland. You plan to interview key stakeholders in the charity.

Note; You will be provided with a set of “interview” notes on Moodle, and you may ask supplementary questions in the lab sessions.

Requirements Prepare a Requirements Specification in the form of a report (~2,500 words), including all necessary diagrams as detailed below.

Report structure and Assessment Criteria Present your findings in the form of a report to the trustees of the charity.

Your report must include the following analysis elements and should clearly state any assumptions you have made. Diagrams may be hand-drawn or using a tool such as draw.io. However, they must be incorporated in the report in a legible format.

1. Overview of the current system, and critical evaluation of its problems as you see them. [10 marks]

2. Requirements Definition: in the form of an overall proposal for the new system, and a numbered list of prioritised functional and non-functional requirements for the proposed system. [10 marks]

3. A basic High Level Use Case Diagram of the Current System, and a Detailed Written Use case description with developed Actor Descriptions and Scenario for the subset of the system requested as being top priority by the Manager of the Charity that links to 2 above (see interview notes on Moodle for more details). [10 marks]

4. Activity diagram(s) showing the activities of the Detailed Written Use Case description from 3 above. For this diagram you should have swim-lanes and include correct notation for at least two of: selection, iteration, and parallelism as appropriate for the scenario [10 marks]

5. Critically Assess the Systems Lifecycle approach that should be taken, and the Tools, Project Team, and Infrastructure that will be required for developing a fully functioning, robust, scalable, trusted, and maintainable system for the charity (with appropriate citations to back up your recommendations) [20 marks]

6. Report formatting and presentation: Your final document should use a formal style and formatting as detailed below and should incorporate the above diagrams and writing into a coherent document. In addition to the elements listed above, the report must also include an introduction and a conclusions section, both of which must be understandable by a non-specialist.