1. Case Study. The suitability of a case study can be determined by referring to examples provided on Moodle and the progress test. You must decide on one case study. A case study can also relate to selected system enhancements for an existing system. For this coursework, a case study should be one of the following:
2. 1. A small business information system or part of a larger system
3. 2. A specification of a non-trivial game or a simulation
4. . The project report contents should be:
   1. UML Diagrams (i.e. use-case diagrams, class diagrams, sequence diagrams ) and associated descriptions. You may use tools such as Violet UML, Argo UML and Star UML.
   2. Project plans including a Work Breakdown Structure

o INTRODUCTION Define Business Information System (Ref) Define Transaction processing and Management Information Systems (Ref) include operational documents & databases and management reports o Aim and Objectives o Submission structure (Chapter breakdown) PROJECT MANAGEMENT Define Project Management (Ref) o Activity List, including Task Dependencies Work Breakdown Structure (WBS) Gantt Chart, including slack/critical activities and critical path Risk Management, including Risk Matrix CASE STUDY o 1-4 page narrative description O Business Case Statement o Define and List Functional and Non-Functional Requirements o Discuss formal methods of Primary data collection, e.g. interviews, questionnaires, focus groups, observation, documents analysis, etc. (Ref) UML SCHEMATIC MODELS Define UML (Ref) Define each of the UML schematic models Use Case Diagram and 4-6 Use Case Descriptors Class Diagram and corresponding Entity Relationship Diagram 4-6 Activity Diagrams 4-6 Sequence Diagrams and corresponding collaboration diagrams 4-6 User Interfaces incorporating good HCl design principles, e.g. Nielsen's Heuristics CONCLUSIONS O o o INTRODUCTION Define Business Information System (Ref) Define Transaction processing and Management Information Systems (Ref) include operational documents & databases and management reports o Aim and Objectives o Submission structure (Chapter breakdown) PROJECT MANAGEMENT Define Project Management (Ref) o Activity List, including Task Dependencies Work Breakdown Structure (WBS) Gantt Chart, including slack/critical activities and critical path Risk Management, including Risk Matrix CASE STUDY o 1-4 page narrative description O Business Case Statement o Define and List Functional and Non-Functional Requirements o Discuss formal methods of Primary data collection, e.g. interviews, questionnaires, focus groups, observation, documents analysis, etc. (Ref) UML SCHEMATIC MODELS Define UML (Ref) Define each of the UML schematic models Use Case Diagram and 4-6 Use Case Descriptors Class Diagram and corresponding Entity Relationship Diagram 4-6 Activity Diagrams 4-6 Sequence Diagrams and corresponding collaboration diagrams 4-6 User Interfaces incorporating good HCl design principles, e.g. Nielsen's Heuristics CONCLUSIONS O o