- The following outline is intended as a guide only
- See Understanding The Report Structure for more information
- Remember that each chapter is interconnected – Video or Simple Image
- You will need to submit a report (research) proposal, which forms most of chapter one
- A feasibility report leads to a prototype or testing a particular solutions
- Remember there are two parts:
- The report which and the deliverable
- The deliverable in this case is the feasibility report
- Remember there are two parts:
- The report and the deliverable (the deliverable, in this case, the feasibility report)
- If you are not sure about your project read this.
- Most universities will require you to undertake a midpoint assessment.
Research Title
Prologue
- Report\ Project Overview
- Acknowledgement
- Statement of Authenticity
- Table of Content
- List of Tables
- List of Figures
Chapter One – Introduction
- Introduction
- Statement of The Problem
- Aim, Objectives and Outcomes
- Deliverables
- Resources
- Planning
- Assumptions, Limitations & Delimitations (Scope)
Chapter Two – Current Situation (Infrastructure)
- A detail analysis of current situation/ infrastructure
- For example:
- Highlight hardware and software
- Highlight networking capacity
- Use system system data to support change/ argument
- You could complete staff interviews/ questionnaires
- For example:
Chapter Three – Literature Review (Alternative Solutions)
- Plan Your Literature Review
- Finding Research
- Writing the review
- Comparing Software
- Top Tips
- You will need to complete a SWOT analysis for each solution
Chapter Four – Research Methods
- International Standards and Best Practices
- What national and international standards do you need to follow (ISOs)
- Consider legal requirements if you have not covered them in your literature review
- Project Management Framework/ Approach
- Which framework will you use to structure your feasibility report
- Software Requirements
- Research Approach
- See, Data Collection tools (below) and Data Collection and the Artefact
- See, Chapter Three for research associated keywords
- Data collection and control
- Planning Implementation
Chapter Five – Implementation
Using one of the possible solutions which you highlighted in your literature review
- System analysis (what the system needs to do)
- use top level computational maps (UML)
- highlight how the system components are interconnected
- highlight top level view of the system and how data enters and leaves
- Link this to the current system and likely up grades
- use top level computational maps (UML)
- Feasibility assessment
- think about the how much time the project will take
- think about how much money it will cost to develop (hardware, software and people)
- think about how much money it will cost the company to install on their system
- Proposed System Requirements
- System requirements: formalise/ list about what infrastructure changes you will need to make
- User Requirements: formalise/ list highlighting user needs
- access to the system
- interacting with the system
- inserting and extracting data
- Software Requirements:
- Focus on the software needs
- For more ideas look here, here and here
Chapter Six – Critical Evaluation
- Identify strength and weakness in your research in-relation to the results
- Discuss your result in relation to your requirements or problem (fit for purpose)
- Link your results to theories and practices in your literature review
- Link your result back to your aims, objectives and deliverables
Chapter Seven – Recommendations & Conclusions
Chapter Eight – Future\ Further Research
Chapter Nine – Critical Reflection
Chapter Ten – References
- Use a reference manager Mendeley
- Very quick reference sheet
- Interactive Version
Dan Campbell 
