Requirements and Models for Disaster Relief Co-ordination System (DRCS)

Business Modeling for DRCS

These all relate to the description of Disaster Relief Co-ordination System (DRCS) case study given below. This description should not be regarded as complete but can be regarded as accurate (in other words you can expand upon it but your answer should not contradict it). You may want to investigate similar dating agency websites for ideas! Please note that there are no absolutely definitive (or correct) answers to these. You will be assessed on your ability to present the requirements in a clear and logical manner, the way you have addressed the description of the system provided, and the quality of your discussion of the issues arising.

Note that you are required to present requirements and models for the new system at DRCS – much of the discussion below relates to the current system.

1. Business Modeling for DRCS: Mission Statement, Business Realisation plan using a Balanced Business Scorecard, SWOT analysis, PESTLE Analysis and Porters 5 Forces Analysis (20 marks) – about 4 A4 pages

Define the Mission Statement and Business Realisation plan using a Balanced Business Scorecard. Also Perform a SWOT analysis, PESTLE analysis and Porters 5 forces analysis of DRCS.

2. Develop various Project Initiation Products (15 marks) – about 2 A4 pages You should identify an IS/IT project that DRCS need. Develop a Project Vision statement, a Scope diagram, cost benefit analysis and a profit loss analysis for 3 years.

3. Produce a Requirements Catalogue (15 marks) – about 3 A4 pages This should take the following form:

A list of at least 10 summary functional requirements, each characterised by a name, a short description (< 25 words), and a priority. Produce a list of 5 non-functional requirements, each including a 50 –100 words description.

Two of these functional requirements should be expanded in more detail to give a full description of the requirement and include any associated non-functional requirements such as those associated with performance, usability, and security. For an example of how this can be done see course notes –but other formats are acceptable.

4. Produce a Use Case model of the required system (10 marks) - about 3 A4 pages Produce a Use Case Diagram (use UML standards) and a detailed description of a Use Case of your choosing (use the standard provided by Cockburn in the notes or any other recognised standard - quote the source you used). In one A4 page describe any decisions you have made in producing your use case models: what to include or exclude, any areas requiring further definition, any assumptions made, and how it relates to the requirements you have defined in part 3.

5. Produce a Class Model of the required system (10 marks) – about 2 A4 pages

Class Model – follow UML standards. For each class include attributes (full set) and operations (samples only) for each association include a name and a multiplicity and any other constraints. In a further A4 page describe any decisions you have made in producing your model: what to include or exclude, a discussion of alternative ways of modelling that you rejected, any clarification of your model, any areas requiring further definition, any assumptions made, and how it relates to the requirements you have defined in part 3.

6. Consider the soft, human stakeholder aspects of this project (10 marks) – about 3 A4 pages What factors could affect its acceptance by the users and ability to achieve its business benefits? Use a rich picture (one A4 page) to describe the potential problem situation arising from the implementation, provide a twopage explanation of this considering stakeholder attitudes and change management. Discuss how the problems you have identified might be avoided or overcome.

7. a) Critically explain the benefits of using the Zachman Framework.

b) Draw the Zachman Framework and populate it with the appropriate content from the DRCS Case Study (20 marks)

Demonstrate your understanding of the Zachman framework by populating this grid with some Dating Agency type development objects. Critically explain, with references, the benefits of modelling the Enterprise Architecture for this case study.