CAPSTONE PROJECT

PROPOSAL/REVIEW/FINAL
GUIDELINES

Submitted to
Computer Science Department

Advisor
[Advisor Name]

[Student Name] [Student ID]

Programme
Date of submission

Page 1 of 14
A Capstone Project is an undertaking appropriate to a professional field. It should significantly
address an existing problem need. HCS/HAI/HCC Capstone Projects focuses on the
infrastructure, application, or processes involved in introducing a Computing solution to a
problem.
For HCS, The Capstone Project, involving the development of the software system could involve
algorithm-based research and development founded on Computer Science principles. This
should be reflected in the final report
For HCC Capstone Projects, recommends cloud infrastructure and its implications on other
systems should be clearly specified in the final report with the introduction on the project
For HAI Capstone Projects, recommended AI infrastructure and its implications on other
systems should be clearly specified in the final report with the introduction on the project

Capstone Projects: To complete a project, a student must create a computational system that
contributes to society. Hence, completion of a project involves the design and implementation of
a suitably complex system of software and/or hardware system that benefits society.

Projects usually involve software components, hardware components, or both. An example of a

software-only project is the design and implementation of a new open-source operating system.
An example of a hardware-only project is the design and development of a new educational
robot. Finally, an example of a mixed project is the design and implementation of a new
biometric authentication device.

The primary contribution of the project need not be technical. An example of such a project is
the creation of a social networking site for the differently-abled. A project involves some type of
practical development with a deliverable. This may include development with computer
equipment, software packages, and programming or scripting languages. Alternately, it may be
the development and demonstration of an innovative process that addresses a current computing
issue or problem. As technologies change, capstone resources should keep pace. A well-written
professional report is required that details current thinking on the topic in the professional
literature, the design and implementation of development that was done, and a critical
evaluation of the results

Stages

1. Initial Discussion of the Topic with supervisor

2. Completion of an Initial Literature Review
3. Refinement of the Topic
4. Development of a Proposal
5. Proposal Presentation and acceptance
6. Review 1
7. Review 2
8. Final Project -artefact and writeup

Page 2 of 14
 9. Final Presentation

Based on the focus, capstone projects need not require descriptive methodologies, theoretical
frameworks, surveys/questionnaires, or statistical treatments, unless considered appropriate or
needed in determining project results.

Suggested Areas/Topics

As recommended by the Department, the following topics are considered for students taking up
(note there are other areas not listed here):

Software and Hardware

• Software Development
• Information Systems Development for an actual client (with pilot testing)
• Web Applications Development (with at least alpha testing on live servers)
• Mobile Computing Systems
• Hardware, IoT, Image processing, Computer vision among others
• Transaction Driven Data
• Medical Imaging
• Computer Aided Manufacturing
• Computer security
• Human Computer Interaction

2. Multimedia Systems

• Game Development
• e-Learning Systems
• Interactive Systems
• Information Kiosks
• Digitization of artefacts
• Human Computer Interaction

3. Data analytics and AI projects

• Data Erasure, Phonetic Lyrics Search, Machine Learning

• Sentence Completion, Digital Signature
• Similarity Search, Recommender Systems and Collaborative Filtering
• Data Retrieval and Topic Waves
• Prediction and Verification

4. Cloud computing

Page 3 of 14
 • Interface development, large scale analysis and sense making
• Security, Sharing,
• Provenance
• Create a cloud-based web application:
• Develop a cloud-based mobile application
• Build a Personal Cloud Storage
• Creating a disaster recovery
• Implementing a cloud-based load balancer
• Blockchain
• Secure text transfer/Secure transactions

Roles and Responsibilities of the Student

The student should initiate many of the activities in the supervision of project, in particular the
administration activities. Responsibilities of the student include:

• Selecting a project topic

• Informing the course Coordinator of the topic selected
• Preparing a software development/hardware/cloud /AI project proposal
• Maintaining progress as documented in the development project proposal
• Negotiating alterations to the proposal with the supervisor
• Meeting regularly with the supervisor (it is advisable to maintain a diary entry
that summarises each meeting email this to your supervisor after each meeting)
• Raising any issues or problems with the supervisor at an early date
• Ensuring that the writing style and presentation of the report is appropriate
• Printing, binding and submission of the report as outlined above.
• Reporting on progress to supervisor at the end of each semester
• Demonstrating the software to supervisor and possibly examiner(s), as required

Table of contents

1 Project Proposal.......................................................................................................................7
1.1 Introduction.......................................................................................................................7
1.2 Novelty of project.............................................................................................................7
1.3 Aims and objectives..........................................................................................................7
1.4 Project Scope.....................................................................................................................7
1.5 Literature review...............................................................................................................7
1.6 User and System Requirements Gathering.......................................................................7
1.7 Conceptual framework/ Architecture................................................................................7
1.8 Methodology.....................................................................................................................7
1.8.1 Software /Artefact Development Model....................................................................7
1.8.2 Required Tools...........................................................................................................8

Page 4 of 14
 1.9 Ethical considerations.......................................................................................................8
1.10 Risks and Challenges........................................................................................................8
1.10.1 Technical Challenges.................................................................................................8
1.10.2 Project Risks..............................................................................................................8
1.11 Project Deliverables..........................................................................................................8
1.12 Proposed innovation and IP plan......................................................................................8
1.13 Project Plan.......................................................................................................................8
1.13.1 Distribution of Tasks.................................................................................................9
1.13.2 Execution Plan (Gantt Chart).....................................................................................9
1.14 Summary...........................................................................................................................9
1.15 References.........................................................................................................................9
1.16 Appendices........................................................................................................................9
2 Capstone Project review Report I............................................................................................9
2.1 Introduction.......................................................................................................................9
2.2 System Requirements........................................................................................................9
2.2.1 Requirements Elicitation Approach...........................................................................9
2.2.2 Requirements Specification.......................................................................................9
2.3 System Architecture and Design.......................................................................................9
2.4 Developed Artifacts........................................................................................................10
2.5 Current Issues..................................................................................................................10
2.5.1 Design Challenges...................................................................................................10
2.5.2 Risk Management....................................................................................................10
2.5.3 Newly Discovered Risks..........................................................................................10
2.6 Plan of the Next Stage.....................................................................................................10
2.7 Summary.........................................................................................................................10
2.8 References.......................................................................................................................10
2.9 Appendices......................................................................................................................10
3 Capstone Project Review II...................................................................................................10
3.1 Introduction.....................................................................................................................10
3.2 Detailed system architecture...........................................................................................11
3.3 System Design.................................................................................................................11
3.4 Newly Discovered Requirements....................................................................................11
3.5 Implementation Details...................................................................................................11

Page 5 of 14
 3.5.1 Frameworks and Platforms......................................................................................11
3.5.2 Component and Code Reuse....................................................................................11
3.5.3 CASE Tools.............................................................................................................11
3.6 Current Issues..................................................................................................................11
3.6.1 Design Challenges...................................................................................................11
3.6.2 Risk Management....................................................................................................12
3.6.3 Newly Discovered Risks..........................................................................................12
3.7 final project plan.............................................................................................................12
3.8 Summary.........................................................................................................................12
3.9 References.......................................................................................................................12
4 Final Project Writeup.............................................................................................................12
4.1 Introduction and Background..........................................................................................12
4.2 Aim objectives and scope...............................................................................................12
4.3 User and System Requirements......................................................................................12
4.4 Literature review.............................................................................................................12
4.5 Methodology...................................................................................................................13
4.5.1 Artefact Development Model..................................................................................13
4.5.2 Tools........................................................................................................................13
4.5.3 System Architecture.................................................................................................13
4.5.4 System Design Artifacts..........................................................................................13
4.5.5 Modifications of the Original Plan (Optional).........................................................13
4.6 Implementation Framework and Details.........................................................................13
4.6.1 Tools and Component Reuse...................................................................................13
4.6.2 Testing.....................................................................................................................14
4.6.3 Implemantation and roll out.....................................................................................14
4.7 Artefact evaluation..........................................................................................................14
4.8 Proposed innovation and IP plan....................................................................................14
4.9 Conclusions and Lessons Learned..................................................................................14
4.10 References.......................................................................................................................14
4.11 Appendices......................................................................................................................14
5 Presentation............................................................................................................................15
5.1.1 Assessment Criteria.................................................................................................15

Page 6 of 14
1 PROJECT PROPOSAL

1.1 INTRODUCTION

Include a clear problem statement, definitions, scope of the project, objectives, and, the
challenges facing the design, implementation, and testing of the final product.

1.2 NOVELTY OF PROJECT

Discuss what innovation you are bringing and projected financial benefits of the project

1.3 AIMS AND OBJECTIVES

Define aims and objectives

1.4 PROJECT SCOPE

Define boundaries of the project

1.5 LITERATURE REVIEW

Discuss on areas of application of proposed idea and its novelty as a gap. A critical
discussion of the relevant literature. This section should demonstrate the student's
knowledge.

1.6 USER AND SYSTEM REQUIREMENTS GATHERING

A proposed set of user and system requirements covering functional and nonfunctional
requirements and goals that cover all aspects of the developed product. Student to list
stakeholders, data gathering tools

1.7 CONCEPTUAL FRAMEWORK/ ARCHITECTURE

Models of architecture with clear semantics that capture the proposed high-level design of
the system.

1.8 METHODOLOGY

1.8.1 SOFTWARE /ARTEFACT DEVELOPMENT MODEL

Page 7 of 14
Include discussion on conceptual design / systems architecture/ block diagrams and algorithms

1.8.2 REQUIRED TOOLS

The proposed software development model and approach, prescriptions, tools, equipment,
and steps required to complete the project. Tools may include, but are not limited to,
modeling, project management, and code generation tools.

1.9 ETHICAL CONSIDERATIONS

Discuss ethics on requirements gathering and use of artefact

1.10 RISKS AND CHALLENGES

1.10.1 TECHNICAL CHALLENGES

1.10.2 PROJECT RISKS

A project specific list of technical challenges and their details and a vision to approach the
problems. Another project specific list of anticipated risks and possible mitigation plans.

1.11 PROJECT DELIVERABLES

The deliverables include: software system components, technical documentations, end-user

manual., project development costs). Based on the nature of the project deliverables may vary.

1.12 PROPOSED INNOVATION AND IP PLAN

Detail how the proposed deliverable will be commercialized and intended

customer/stakeholders

1.13 PROJECT PLAN

1.13.1 DISTRIBUTION OF TASKS

1.13.2 EXECUTION PLAN (GANTT CHART)

Page 8 of 14
 According to your software development model, describe the decomposition of the project
into tasks and the way the tasks are distributed along with a time plan for the execution of
the project.

1.14 SUMMARY

The summary of the project proposal and plan.

1.15 REFERENCES

A reference list created using the built-in functions to be compatible the departments
reference format.

1.16 APPENDICES

2 CAPSTONE PROJECT REVIEW REPORT I

1.17 INTRODUCTION

An overview of the document, the project, and the progress made so far.

1.18 SYSTEM REQUIREMENTS

1.18.1 REQUIREMENTS ELICITATION APPROACH

A discussion on the elicitation approach used (e.g., interviews).

1.18.2 REQUIREMENTS SPECIFICATION

A description of the user and system requirements elicited so far.

1.19 SYSTEM ARCHITECTURE AND DESIGN

An architecture of the system to be developed. The architecture is specific to your system and
may be based on existing architectural styles. Include the style used in the appendix.

1.20 DEVELOPED ARTIFACTS

Artifacts developed so far. In case of incremental or agile projects, by this time, the team
may have design documents, code, or testing cases.

1.21 CURRENT ISSUES

Page 9 of 14
1.21.1 DESIGN CHALLENGES

Challenges currently faced and anticipated solutions, challenges resolved so far

1.21.2 RISK MANAGEMENT

Risks resolved so far.

1.21.3 NEWLY DISCOVERED RISKS

Newly discovered risks and their resolutions.

1.22 PLAN OF THE NEXT STAGE

Describe changes to the original plan (if any), and the plan for the next stage.

1.23 SUMMARY

A summary of what has been achieved so far.

1.24 REFERENCES

A reference list created using the built-in functions to be compatible the APA format.

1.25 APPENDICES

3 CAPSTONE PROJECT REVIEW II

1.26 INTRODUCTION

An overview of the document, the project, and the progress made so far.

1.27 DETAILED SYSTEM ARCHITECTURE

Various views of the system architecture to be presented showing the overall decomposition
of the system, interaction of internal and external structures, and any other specifically
applicable architectural models.

1.28 SYSTEM DESIGN

Page 10 of 14
 Design decisions made in the system as a means of models, algorithms, and technical
descriptions.

1.29 NEWLY DISCOVERED REQUIREMENTS

Requirements discovered after the previous stage or requirements modified.

1.30 IMPLEMENTATION DETAILS

1.30.1 FRAMEWORKS AND PLATFORMS

Describe the framework you use for development (e.g., xcode) as well as the target platform
(e.g., iOS).

1.30.2 COMPONENT AND CODE REUSE

Describe the reusable libraries, source code, or APIs your development benefits from.

1.30.3 CASE TOOLS

Name the tools that aid you in the entire lifecycle including tools used for documentation,
testing, and project management. Describe the copyright rules associated with any reuse you
may have.

1.31 CURRENT ISSUES

1.31.1 DESIGN CHALLENGES

Challenges currently faced and anticipated solutions and challenges resolved so far.

1.31.2 RISK MANAGEMENT

Risks resolved so far.

1.31.3 NEWLY DISCOVERED RISKS

Newly discovered risks.

1.32 FINAL PROJECT PLAN

Describe changes to the original plan (if any), and the plan for the final stage.

1.33 SUMMARY

Page 11 of 14
 A summary of what has been achieved so far.
1.34 REFERENCES

A reference list created using the built-in functions to be compatible the APA format.

4 FINAL PROJECT WRITEUP

1.35 INTRODUCTION AND BACKGROUND

An overall description of the project, the motivations behind it, deliverables, and scope of the
work.

1.36 AIM OBJECTIVES AND SCOPE

Aims, objectives and scope defining boundaries

1.37 USER AND SYSTEM REQUIREMENTS

A completed set of user and system requirements covering functional and nonfunctional
requirements and goals that cover all aspects of the developed product.

1.38 LITERATURE REVIEW

Discuss on areas of application of proposed idea and its novelty as a gap. A critical
discussion of the relevant literature. This section should demonstrate the student's
knowledge.

1.39 METHODOLOGY

1.39.1 ARTEFACT DEVELOPMENT MODEL

Include discussion on conceptual design / systems architecture/ block diagrams and algorithms

1.39.2 TOOLS

The development model used and approach, prescriptions, tools, equipment, and steps
required to complete the project. Tools may include, but are not limited to, modeling, project
management, and code generation tools.

1.39.3 SYSTEM ARCHITECTURE

Page 12 of 14
 Models of system architecture with clear semantics that capture the high-level design of the
system.

1.39.4 SYSTEM DESIGN ARTIFACTS

All the design decisions and models and artifacts reflecting the requirements and
representing the code.

1.39.5 MODIFICATIONS OF THE ORIGINAL PLAN (OPTIONAL)

In case of change of directions, mention what changes made to the original plan including
but not limited to requirements, design, models, schedules, etc.

1.40 IMPLEMENTATION FRAMEWORK AND DETAILS

Algorithms developed or used, coding decisions made, frameworks and the choice of
operating systems, languages, and compilers.

1.40.1 TOOLS AND COMPONENT REUSE

Tools used throughout the project and the benefits of using them. A documentation of all
code or design reuse.

1.40.2 TESTING

1.1. Testing Plan

1.2. Unit Test Cases
1.3. Integration Tests
1.4. Stress and Performance Tests
1.5. Reliability Tests

A rich documentation of the tests performed. Students are welcome to add subsections for
additional tests (if any).

1.40.3 IMPLEMANTATION AND ROLL OUT

Details how the product/artifact will be used in real world

1.41 ARTEFACT EVALUATION

Evaluate artefact with experts or users

Page 13 of 14
1.42 PROPOSED INNOVATION AND IP PLAN

Detail how the proposed deliverable will be commercialized and intended

customer/stakeholders

1.43 CONCLUSIONS AND LESSONS LEARNED

Final remarks on the project and technical lessons learned.

1.44 REFERENCES

A well-formed list of references according to writing standards.

1.45 APPENDICES

Additional material such as screenshots, algorithms, etc.

5 PRESENTATION

1.45.1 ASSESSMENT CRITERIA

• Product Demonstration
• All objectives met?
• Creativity /Originality of the Project
• Knowledge of content
• Answering Skill

Page 14 of 14