Case study - VCI Case Study Description

Introduction

The aim is that your team (3-4 members) should produce a requirements document that captures the functional requirements for the creation of an information system based on the VCI case study provided within this document.

OR
Create your own case study

Find your own business system (or sub system) as a case study. The system can be of interest to you (i.e. your team) or to someone else who is willing to be your client. Be aware that you must be able to gather sufficient information so that you can that satisfy all aspects of the assignment. You must obtain approval for your proposed case study from your tutor. Your tutor will need to be satisfied that the case study is suitable and of appropriate scope. Provide a brief overview of your proposed case study and of its suitability for your tutor.

Your group's task is to provide the following models:

- A context diagram: This must be for the whole System. You need to show relevant external agents together with data flows between the system and the external agents.

- A set of levelled Dataflow diagrams: By this we mean a Level 0 diagram, and for some processes may mean further decomposed to their primitive level (Level 1 and 2) diagrams.

- Use Case diagrams, use case descriptions

- A high level data model as an ER diagram (many to many relationships are acceptable).

- CRUD analysis and sample screen shots. Sample screenshots will help necessary stakeholders to visualize the capabilities of the system.

You are to make recommendations for the new system which will form the basis of further discussion with the client so that an informed decision can be made. You should research and present possible solutions which will address the requirements and the potential advantages and disadvantages of each recommendation. Your recommendations can include further functionality you believe would benefit the client. Your proposal should be comprehensible to management and to users who are computer literate

Individual Component:

Compare and contrast the structured analysis and design approach with other modelling techniques (e.g., the object-oriented approach), and clearly identify the strengths and weaknesses of each approach. Your justification should be supported by appropriate references.

Introduction
- What is the organisation and what does this organisation do?
- What is the business problem we are trying to solve OR what is the opportunity that we can make use of?

Expected benefits

How would the organisation be better off by solving this problem or taking up this opportunity

Dataflow diagrams
- Context Diagram
- Diagram 0
- Lower Level Data flow diagrams as required

- ERD Diagram of the high level data model
Data dictionary
- Data flow description
- Data element descriptions
- Data stores/Entities in the ERD diagram

Process Descriptions in the Structured English CRUD Analysis
User Stories and acceptance criteria

Use Case description
- Use case diagram
- Intermediate level use case description for each function

Recommendations

You are to make recommendations for the new system which will form the basis of further discussion with the client so that an informed decision can be made.

- Discuss possible solutions which will address the requirements and the potential advantages and disadvantages of each recommendation. Each solution may contain a CRUD analysis and sample screen shots to help in understanding.

-  Your recommendations can include further functionality you believe would benefit the client.
Your proposal should be comprehensible to management and to users who are computer literate

Appendices

- DFD fragments, event list etc.

- This contains any other documents that might be useful for reference or too detailed or lengthy to put into the main part of the document.

Attachment:- RAM ASSIGN.rar