Reference no: EM133829779

Computing Science Project Proposal

Project - Predicting IELTS Performance by Nationality Using Machine Learning

Aims of the Project

Be required to combine previously acquired knowledge and techniques with newly investigated ideas, the results to be communicated in a report;
Work independently under the guidance of a Supervisor on a Project of your choice and be expected to develop it systematically;
Produce an extended piece of work covering a variety of activities related to a single theme.

Learning Outcome 1: Critically review the background related to an area of study

Learning Outcome 2: Develop a system or system artefact to enable a defined Computing Science/Cyber Security issue to be investigated via a practical project framework. Get Instant Solutions for Your Assignments!

Learning Outcome 3: Deploy appropriate design and development methods, tools and technologies.

Learning Outcome 4: Evaluate project findings and communicate these along with process and professional issues reflections in report form.

Part - A

Part A - What types of project to do?

Come up with a Computer System (report and software)
Software Application
Website
Mobile Application
Security Applications
Database Application
Games
Monitoring System
Robotic Project
AI project, etc

Part A - Where to get the project idea?

Come up with your own Idea
Older projects (school, assignments, etc)
Examples ideas from internet / books / magazines
Do a Project suggested by a member of staff
Develop a previous Project
Approach a Company
Do a small system that they need.

Personalized Assistance based on Location
Web Based Recruitment Management System
Gamification based E-Learning Platform
Exam Paper and Marking Scheme Generator Using Questions and Answers in Question Bank
Online Tour Assistance
College Library Management System
Restaurant Management System
Personal Appointment Management System

Select a few areas/titles that you want to do
Do background research on your chosen Project topic.
Choose the one which you are comfortable and confident to do.

Plan your project

As a rough guide the Project should take up to 300 hours of your time
Follow SDLC, plan your project for 12 weeks (or any methodology)
Part A and B
Draw a Gantt Chart
Stick to the timing
Keep a Project diary / log

Chapter-1: Introduction
Provisional Project title
Project Background
Introduction about the Company (if doing for one)
Introduction about the System (existing)
Project Aims and Objectives
Problem Statement
(3-5 problems that you are trying to solve)
Suggested Solutions.
Support with a Use Case
Project Deliverables
Software, hardware, reports, etc
Project Scope
Project Plan (Gantt Chart)
List of resources
Hardware and Software Requirements

Part A - What to Deliver?
A Project Proposal ... with the following sections;

Chapter-2
Literature Review
Literature Review
Technical Literature Review

Chapter-3
Methodology
Research Methodology
System Development Methodology

How to Fail?

Not reading this guide
Cheating and Plagiarism
Choosing a Project topic that requires the
use of resources that are not available
Failure to maintain regular contact with your Project Supervisor.
Including material taken from books, articles, etc., which you do not understand.
Using either program code or material taken from books, articles.
Not being honest in your Report, e.g., claiming that your program does something which it clearly does not.
No conclusion.
Thinking that a Project is just a large
course work.
Spend too much of their time and effort producing a ‘flashy' graphical user interface (GUI)
Rushing the write up of the Final Report, resulting in poor illogical structure, English, layout, contents, etc.

Project

Be required to combine previously acquired knowledge and techniques with newly investigated ideas, the results to be communicated in a report;
Work independently under the guidance of a Supervisor on a Project of your choice and be expected to develop it systematically;
Produce an extended piece of work covering a variety of activities related to a single theme.

Learning Outcomes

ILO1- Critically review the background related to an area of study
ILO2 - Develop a system or system artefact to enable a defined Computing Science/Cyber Security issue to be investigated via a practical project framework.
ILO3 -Deploy appropriate design and development methods, tools and technologies.
ILO4 - Evaluate project findings and communicate these along with process and professional issues reflections in report form.

Introduction
(From Project Proposal)
Literature Review
Methodology
Requirement Gathering
Analysis
Design
Implementation
Building (few snapshots, rest in Appendix)
Testing
Deployment Plan
Conclusion

Chapter 1 - Introduction

Project Background
Introduction about the Company (if doing for one)
Introduction about the System
(existing)
Problem Statement (five problems)
research hypothesis (if applicable)
Suggested Solutions.
Support with a Use Case
Move to Analysis
Project Deliverables
Software, hardware, reports, etc
Project Aims and Objectives
Project Scope
Project Plan (Gantt Chart)
List of resources
Hardware and Software Requirements
(special needs to do this project)
Outline the contents of the proceeding chapters.

Chapter 2 - Literature Review
Review related information to your ‘Project Title'.
Introduction to technology and techniques used in your project
Other people's similar findings
Current technology available to built your project
Similar systems
Technical LR
TOOLs you are planning to use in this project (compare and contrast)
Testing Software
Programming Languages
Hardware, etc

Chapter 3 - Methodology

Research Methodology
The methods that you use to collect,
compile, analyse and conclude data.
The use of any tools / software /
automated methods to do the above
Discuss why these methods used and
their benefits to your project.
1 page minimum
System Development Methodology
Identify the IS Methodology which is the most suitable for your type of project.
Discuss the benefits and features of
the methodology
Explain the stages and relevance to
the project
* your Project Planning Gantt Chart should be following your Methodology stages

Chapter 4 - Requirement Gathering

Interview (at least 5)
Questionnaire (at least 20)
Learning more about the old system / operations (if any)
Collecting more information to build a better new system
Clearing technical doubts.
Exploring current needs and trends.
Ethical Statement
A standard report to declare that your;
Information gathering is done in a ethical manner
Collected Information and the source will be protected.
Information collected will not be abused.

Chapter 5 - Analysis

Summarise the data that you have collected
Compare your Hypothesis with Primary and Secondary Data.
May use analysis tools
Conclusion
Comparison of what was though before and what is being found.
Consideration of changes to be made to the new system.
Write-up of Finalized Requirements
Functional and Non-functional requirement.
(Summary only. Full requirement to be included in Appendix)

Chapter 6 - Design

Diagrams
Use Case
Class
Activity
State
ERD
Prototype
Screenshots
Sketches

Chapter 7 - Implementation

Building (few snapshots of the UI, rest in Appendix if needed)
Testing
Test Plan
Test Result summary
Deployment Plan (if necessary)

Chapter 8 - Conclusion
Critical Evaluation
Review every chapter
Discuss Achievements, challenges and failures.
Comparing achievement against Aims and Objectives
Further Work / Future Enhancement
Lesson Learned

Referencing

Following APA Referencing Method