1.

INTRODUCTION

As part of the HND programme, each student is expected to complete an individual or a group project/research. This guide describes the process that students must follow when completing a project/research work. Much of the process is the same for both project and research, However, where there are differences it will be stated categorically. Most projects involve the development of software products, although a research project can also be done. 2.0 PROJECT CATEGORIES

A project involves the systematic creation and execution of a plan for addressing a significant computer problem. Students are expected to demonstrate skills and knowledge that thy have acquired by finding solution to the problem they choose, or conduct a research into a significant area of their programme of award. Computer science/network management projects may be in the form of: Software development Research project

Software development project are recommended. However, choice of a research based project will not students a grade greater than C. 2.1 SOFTWARE DEVELOPMENT PROJECT

Development project produces a working implementation of a problem solution. Students are expected to use software engineering technique and computer science principles to develop software by: Planning Analysing and specifying requirements Designing the software to the requirement specification Implementing the design in computer science 1

 2.2 3.0

Writing the appropriate documentation Demonstrating the project Delivering the software and the documentation RESEARCH PROJECT Analysing the problem/topic Conducting detailed research Summarising the findings from the research investigation Recommending additional research on the topic Drawing conclusion from the research. PREREQUISITE

This investigates a computer problem or topic by:

Student must register and study the following courses: Research Methods Systems Analysis and Design

as prerequisite for the final project work. Students are also expected to register for the CSD 321 (project) course during the fifth semester course registration, select a project topic and write a project proposal to be submitted to the computer science department for approval before the end of the fifth semester (3rd year, second semester). Good project topic should be appropriate to the student's course of study

4.0

PROJECT PROPOSAL

The project proposal is the background and planning document for the project (software development or research). It must be done with great care and thoroughness. It must be the product of the students original thought and effort.

The project proposal is written by the student in consultation with the supervisor, and must be approved by the supervisor, computer science department and the School of Applied Science and Technology before the student can proceed to the actual project. Any use of others work must be properly referenced. Students are required to start and complete their project proposal by the fifth semester. In writing the proposal, students need to introduce the chosen subject area to the reader, focusing their interest within the subject area on a specific problem. They are expected to develop arguments that back up the aim and objectives of the project. Students are advised that, one of the main purposes of the project proposal is to convince the reader that the project is worthwhile. Thus good justifications of the importance of undertaking the project are necessary at this point. See Appendix A for proposal cover page and Appendix B for proposal content structure. The proposal should include: 4.1 INTRODUCTION

A few paragraphs should be sufficient to cover the background to your project. Introduction to the project describes the main reasons for carrying the project, and placing the project in context. 4.2 OBJECTIVE

State clearly what is to be accomplished and its significant as Higher National Diploma (HND) project. 4.3 JUSTIFICATION

Students should justify the selected topic: reasons why it is important to investigate the chosen problem by explaining how the project will meet the requirements of the HND programme and the students course of study, why the topic interests the student, and what he/she hope to gain from the project.

4.4

SCOPE

The scope of a project is a description of what activities the student plan to carry out, and the functional or academic boundaries of the project project. In order for student to do this, it may be useful to list the boundaries of the project: areas where the project will not cover. Functional boundaries will help to define which parts of a problem or business you will be addressing. 4.5 ACTIVITY/METHODOLOGGY

Describe in details how the objective will be achieved, describing the development phases and task that will be performed. Include chart, graphics, diagrams and project model, if they will explain the activities more clearly. 4.6 ENVIRONMENT/TECHNOLOGY

This describes the computer programming language, software and hardware that will be used for the development or the research project. 4.7 DELIVERABLES

Define clearly what the final product of the project will be. Identify what will be delivered to the supervisor and the Computer Science Department when the project is completed. Possible deliverables include: Final report (required for all projects) Source code User manual etc.

The project format and content is described in Appendix B. 4.8 CONSTRAINTS

Students should identify and list possible constraints to the project. The main constraints are likely to be: Time: That you have available Existing skills: Unlikely that you will have the time to develop new skills, Particularly if the project involves a system development Resources: This could be technology, human etc. Data availability

4.9

SCHEDULE

The schedule is an important part of the project. It defines what student plan to achieve and at what time. Students should consider how long each activity will take, which activity must precede other and how much overlap is possible or desirable. The schedule indentifies task to be performed, milestones to meet and the estimated number of hours for each task. Student must work closely with the supervisor to develop the schedule. It helps in defining the scope of the project and establishes a baseline for measuring progress. A schedule must be within one-semester span. 4.10 ROPOSAL DEADLINES Students are expected to submit their project proposal before the end of the fifth semester. However, fixed date and time will be set by the Computer Science Department to regulate late submission. The proposal, if approved, the actual project is then put through under the guidance of the supervisor. 4.11 PROPOSAL SUBMISSION PROCEDURES

Students are expected to submit a hard copy of the proposal, with a signed cover to the Computer Science Department for review and approval. It must be submitted on or before the deadline date. When the student submits the proposal, he or she signs up on the next available line on the list of project proposals. The student may be asked to submit electronic copy of the proposal. 4.12 ACTION ON APPROVAL The department, computer science receives all proposal, review and pass it on to the School Of Applied Science and Technology (SAST) for approval. SASTs response on submitted proposal will be posted on the Computer Science Departments notice board before the end of the fifth semester. The possible approval responses are: 4.12.1 ACCEPTED:

The student may start work on the project, but should contact the supervisor for comments; 4.12.2 CONDITIONALLY ACCEPTED:

The student must modify the proposal according to the supervisors indications and approval; upon subsequent approval, the student may then start the project; 4.12.3 REJECTED:

Proposal is unacceptable: The student must contact the supervisor for advice. Proposals that are conditionally accepted or rejected must be resubmitted to the department one week before the start of the next semester. Students are not allowed to start the project until the proposal is approved.

5.0

SELECTION OF PROJECT TOPIC

Normally, a topic is suggested by the supervisor or the Computer Science Department. However, a student may propose a topic to the supervisor, but the supervisor has every right to reject or refuse to supervise a project on a student generated topic. The project topic is expected to be of sufficient depth so as to lead to a paper submitted for publication in a professional journal or presentation at a professional conference if possible. 6.0 SUPERVISION

The supervisor is one of the most important support resources available. Students will be allocated a supervisor who may or may not have knowledge of your topic. However they will be able to point students to sources of information. Most supervisors are limited in the time that they have to support students project and will be supervising a number of other projects. Thus student must be efficient and effective in the use of their supervisors. Being efficient means making sure they turn up promptly for meetings. Make sure the issues they want to discuss are the important ones and prepare in advance for the meetings. Supervisors are advisors and critical reviewer of the project. Students must not expect supervisors to do their project for them or consult them on every trivial issue as that creates impression that students are not able to work on their own. If students arrange meeting with supervisor but unable to make it, they are to make supervisors know in advance. A summary of the supervisors responsibilities for the project are:

To meet with the student at regular intervals to advise and guide the progress of the project;

Manage and oversee the administration of the project and help the student from time to time to identify the direction that the project should take;

Give the student reasonable assistance in obtaining access to advice, material and resources with which to carry out the project and reasonable advice on documenting and presenting the project;

Recommend appropriate methodologies Mark the project elements Establish whether the project meets the NAPTEX requirements for award of HND project.

7.0

RESPONSIBILITY OF THE STUDENT

Students are to begin working on the project immediately it is approved by the supervisor, department and the school (faculty). They are expected to work hand in hand with their supervisors till completion of the project. Students are expected to: Make periodic progress reports to the supervisor; weekly is recommended. This will help the supervisor to compare the actual progress with the schedule and discuss any problems with the student.

Create draft versions of the required documents and submit them to the supervisor for review

Demonstrate the final project to the project defence committee (Computer Science Department) at a meeting. For research projects, an oral presentation will substitute the demonstration. Students will present their project to the committee and defend their conclusions.

8.0

THE PROJECT

The type of project will dictate the content and structure; therefore students are advised to discuss content of the project with their supervisors. The computer science department expect development project to include the following: 8.1 DEVELOPMENT PROJECT

8.1.1 TITLE PAGE State the name of the polytechnic, the faculty (school), department and the title of the project (topic) on this page. Label the page with other relevant details, such as the course code and title, your name, identification number and the examiner's name (see appendix E). 8.1.2 DECLARATION See appendix D 8.1.3 ABSTRACT This should be two or three short paragraphs (100-150 words total), summarising the project. This should not be a restatement of the original project outline. A suggested flow is background, objective and main achievements. From the abstract a reader should be able to ascertain if the project is of interest to him/her and presents results that he/she would like to know the details of. 8.1.4 ACKNOWLEDGMENTS Students are expected to show appreciation to whoever may have helped in the project in anyway. 8.1.5 CONTENTS Table of content should include titles and page numbers of all sections and subsections. Chapter 1 begins on page 1.

10

Students are expected to use roman numerals for all pre-text pages, e.g. title page (i), signed declaration (ii) abstract (iii), acknowledgments (iv) and contents (v) etc. It is preferable, but not compulsory, to include a separate list of all the figures in the project (figure number, label, page number), and a separate list of all tables in the project (table number, label, page number).

8.1.6 CHAPTER 1: INTRODUCTION The introduction has several purposes. Introduction paints a picture of the project by giving relevant background information to catch the reader's interest early. Another is to make clear the aims and objectives of the project and the constraints that might affect the way in which the project is carried out. Should the project involve the solution of a specific problem or the development of a specific system, the introduction should specify in an informal way the solution. It should also summarise the remaining chapters of the project, to give the reader an overview of what is to come. 8.1.7 CHAPTER 2: LITERATURE REVIEW The main focus of the chapter is a review of relevant work by other authors and the relationship between this and the project. If several other people have done closely related work in a different way then the reasons for your approach should be summarised here. A good literature review is synthetic: general trends and positions in the research area should be identified, and the cited papers should be compared and contrasted. A literature review is not simply an annotated list of papers you may have read; it should cover a range of relevant material to the project. Any material used should be cited by reference to the bibliography at the end of the project.

11

Everything that the student writes at this section must be his/her own words and must cite other people using references. Students may also quote sentences from the work of others. These must be included in quotation marks and again the relevant work must be cited. It is recommended that not less than fifteen books, journal articles, web materials etc. be used for the literature review. Failure to do proper referencing will amount to plagiarism which attracts punishment based on the polytechnics code of conduct. 8.1.8 CHAPTER 3: REQUIREMENTS AND ANALYSIS This should state, in a more details, the objectives of the project in terms of requirement and the analysis. It should break the problem down into manageable steps. There may be more than one suitable approach; the analysis may cover more of the area than is finally implemented. Testing and evaluation should be given due consideration. It is important that student state how they intend to evaluate the project. For a design project it is appropriate to consider testing at the same time as specification. For the Analysis stage students are required to develop a number of models. These can include if appropriate: Process models (DFD and supporting descriptions) Data Models (Entity Relationship diagrams) Use Case diagrams Business models Any others which you feel are appropriate.

These may be included in the chapter or in an appendix. 8.1.9 CHAPTER 4: DESIGN

12

This should explain the design technique chosen (and justify why it is appropriate) from the various ones available; it should select a suitable subset of the things described in the analysis chapter and develop a design. Where trade-offs exist between different designs, the chosen approach should be justified. Suitable diagram-techniques (eg UML, other drawings) should be used where appropriate. If a method is applied selectively, explain which parts were used and why. 8.1.10 CHAPTER 5: IMPLEMENTATION AND TESTING

The implementation of the project should provide a clear description of how the solution to the problem is realised. As with the other parts of the project, the selection of the implementation method should be described and justified, and the nature of the solution will depend on the nature of the project. This section should include: Discussion of the technology used and how this was applied to the project. How the design was converted into a working system. o Any differences from the design stage should be discussed. Discussion of what was successfully implemented and what was not Did any of the key features prove to be particularly challenging and involve more work than originally anticipated? How did you overcome these problems? 8.1.10.1 System documentation

This should include a user manual, administrator information and technical support information. The manual could be online or annotated page shots. If there is a written code, it should be commented appropriately.

13

8.1.10.2

Testing strategy

The testing of the project should address the evaluation of the solution against its objectives and success criteria. Students are required to give a description of the testing strategy and the choice of testing method e.g. Functional testing such as black-box and white box testing, also usability testing.

8.1.11

CHAPTER 6: RESULTS AND DISCUSSION

The main results of the project should be presented, together with critical discussion. The chapter should cover three things (although these might not be used as section headings): 8.1.11.1 FINDINGS:

Present all the results (products, experimental findings, theories, etc.) generated during the project. This may also include some offtopic findings that were not expected, or which were side-effects of other explorations. 8.1.11.2 GOALS ACHIEVED: Describe the degree to which the

findings support the original objectives laid out for the project. The goals may be partially or fully achieved, or exceeded. Note that reporting of failures to achieve goals is important since a fundamental feature of the assessment procedures is that the processes (how you went about your project) are often as important as the products of the project. 8.1.11.3 FURTHER WORK:

This should address two things: new areas of investigation prompted by developments in this project, and secondly parts of the current

14

work which was not completed due to time constraints and/or problems encountered. 8.1.12 CHAPTER 7: CONCLUSIONS

The conclusions can be summarised in a fairly short chapter (1 or 2 pages). This chapter brings together many of the points that you will have made in other chapters, especially in the previous results and discussion chapter. Do not be afraid of repeating some of your earlier statements here, using a different wording.

8.1.12

REFERENCES/PLAGIARISM

There is no doubt that a project will build upon and contain references to the work of others, proper referencing should be employed. (See Appendix F) Any attempt to copy the work of others will be dealt with severely under the Polytechnics regulations regarding plagiarism. Note that the whole scale copying from the Internet or books as opposed to using and clearly referencing the source of any material will also be treated as plagiarism. Plagiarism will not be tolerated. It is very important for students to make references to all materials and resources (books, online, journals, articles etc) used in the project to: acknowledge debts to other writers demonstrate the body of knowledge upon which the research is based enable all those who read the work locate the sources easily

The department of Computer Science recommends the Harvard system of referencing: this is by far the most straightforward way of

15

references, because all that a writer needs to do is to mention the author and the date of publication of the material in the text and a bibliographic list of sources at the end of the project. The department will check for plagiarism using open source software known as Viper, Students are therefore encouraged to check plagiarism level of their works before submitting them to the department.

16

9.0

RESEARCH PROJECT

To maintain uniformity in the presentation of a research project, the following outline or format is recommended: 9.1 9.2 Title page Acknowledgement Dedication Abstract Table of content List of table and figures CHAPTER ONE: INTRODUCTION Background Problem statement Objectives Hypothesis Significance of the study (justification) Conceptual framework Scope of the study Limitation (Constraints) Organisation of the study Definition of terms CHAPTER TWO: LITERATURE REVIEW It is recommended that students use not less than 20 books, journals, articles, emails and other electronic material and reference them appropriately to avoid plagiarism. 9.3 CHAPTER THREE: METHODOLOGY Population Sample and sampling procedure Research instruments

17

 9.4 9.5 9.6

Procedure for data collection Method of data analysis CHAPTER FOUR: DATA PRESENTATION AND ANALYSIS Data presentation and analysis CHAPTER FIVE: SUMMARY, CONCLUSION AND Summary Conclusion Recommendation Suggestions for further research REFERENCES

RECOMMENDATIONS

Harvard system of referencing is recommended. (See 8.1.13, REFERENCES) 9.7 APPENDICES

10.0 TECHNICAL REQUIREMENT Students are expected to type minimum of five thousand (5,000) words 10.1 PAGE SETUP Paper size: Students must use A4 (21cm/29.7cm) for printing of the project Page Orientation: Portrait is mostly used. Landscape is used only when necessary Margins: 1.0inch (2.54 cm) at the top and bottom; 1.5inches and 1inch at the left and right respectively.

18

10.2 PARAGRAPH Alignment: justified Line spacing: double No extra spaces between paragraph

10.3. FONT Font size: 12points Font: Calibri Font colour: black

10.4 PAGE NUMBERING Use Arabic numeral for text Use small roman numerals for the pretext(abstract, acknowledgement, dedication etc) Numbering should be at the footer and centred

19

APPENDIX A:
COVER PAGE OF PROJECT PROPOSAL

KOFORIDUA POLYTECHNIC
TITLE OF PROJECT PROPOSAL FOR HND COMPUTR SCIENCE/NETWORK MANAGEMENT Students Name: ____________________________________ Date: _________ Department/Program: __________________________________________________ Award: _______________________________________________________________ Tentative Title (or final title): _____________________________________________

Approved by Dean, School of Applied Science and Technology Signature Date: _____________________________________ Approved by Head of Department Computer Science Signature Date: ___________________

20

APPENDIX B: PROJECT PROPOSAL 1. A sample table of contents and outline for the proposal is shown below 2. Cover Page (see Appendix A) 3. Table of Contents (including Tables, Figures. and Appendices) 4. Introduction 5. Objectives 6. justification 7. scope 8. Activities/methodology and technology 9. Deliverables 10. 11. 12. 13. constraints Schedule References Appendices (as needed, for supporting documentation)

21

APPENDIX C: DEVELOPMENT PROJECT REPORT A sample table of contents for the final report for a development project is shown below PRETEXT i. ii. iii. iv. v. 1. Approval Cover Page (see Appendix G) Abstract acknowledgement Keyword List Table of Contents (including Tables, Figures. and Appendices) CHAPTER ONE: INTRODUCTION a. Description of the Problem b. Project Objectives c. justification d. Development Environment (software and hardware) e. Operational Environment (software and hardware) f. Project management g. Team management 2. CHAPTER TWO: LITERATURE REVIEW

22

3.

CHAPTER THREE: REQUIREMENTS ANALYSIS a. Introduction to Requirements Analysis b. Characterisation of the Current System c. Requirements Gathering d. Functional Requirements e. Non-functional 4. CHAPTER THREE: DESIGN DESCRIPTION a. Introduction to design b. Market analysis c. Prototypes d. Interface design e. Database design 5. CHAPTER FOUR: IMPLEMENTATION AND TEST (PLAN AND RESULTS) a. Introduction to Coding and implementation b. Code testing c. Usability testing d. Browser testing(if necessary)

6.

CHAPTER FIVE: RESULTS AND DISCUSSION a. Findings b. Goals achieved c. Lessons learned d. Recommendations for Enhancements (further works)

7.

CHAPTER SIX: CONCLUSION APPENDICES a. user manual b. maintenance manual c. References (citing all references used)

23

APPENDIX D: DEVELOPMENT PROJECT REPORT DECLARATION I hereby declare that the project work entitled Online Hospital Management System submitted to the Koforidua Polytechnic, is a record of an original work done by me under the guidance of Mr. Kwaku Nuamah-Gyambrah, Head Dept of Computer Science, School of Applied Science and Technology. This project work is submitted in partial fulfilment of the requirements for the award of the Higher National Diploma (HND) in Computer Science/Networking Management. The results embodied in this project have not been submitted to any other Polytechnic, University or Institution for the award of any degree or diploma.

STUDENT NAME -------------------------------------INDEX NO.

24

APPENDIX E: PROJECT COVER PAGE

KOFORIDUA POLYTECHNIC SCHOOL OF APPLIED SCIENCE AND TECHNOLOGY (DEPARTMENT OF COMPUTER SCIENCE)

ONLINE HOSPITAL MANAGEMENT SYSTEM

A PROJECT WORK SUBMITTED TO THE DEPARTMENT OF COMPUTER SCIENCE, SCHOOL OF APPLIED SCIENCE AND TECHNOLOGY IN PARTIAL FULFILMENT OF THE AWARD OF THE HIGHER NATIONAL DIPLOMA (HND) IN COMPUTER SCIENCE/NETWORK MANAGEMENT PROGRAMME. BY STUDENT NAME INDEX NO

CSD 402: PROJECT IN COMPUTER SCIENCE/NETWORK MANAGEMENT, SEPTEMBER, 2011

25

APPENDIX F: HARVARD REFERENCING When citing: referring to an article or book within the text of your report, you should include just the surname(s) of the author(s) and the year of publication, for example: Jones (2002) has suggested that. (Department of Information, 2001), It has been argued (World Bank, 2009) that

If a work has more than one author, it is recommended that all the authors surnames are listed or use et al if there are more than two, For example: Jones, (2002) and Smith et al. (2004) If students wish to refer to a specific page you should add the page number after the date: Jones, (200e2, 54) For each article or book referred to in the report, students must include a full entry in the list of references: provision of a consistent description of the elements needed to identify a source: author, date, title, publisher etc. in the bibliography at the back of the report. The Harvard system format for: A FULL BOOK: Surname, forenames or initials of each author (year of publication) Full Title (edition), place of publication, publisher. For example: Jones, (2002) Your project (3rd edition), London, FT Prentice Hall. FOR A FULL JOURNAL ARTICLE: Surname, forenames or initials of each author (year of publication) Article title, Journal Title, Volume (issue), page numbers. For example: Jones, (2002) How to program, Journal of your project, 6 (2), 120123.

26

INTERNET REFERENCING If you have obtained a journal article or electronic version of a book from an internet site, you should add the (URL) and access date to the end of the reference, For example: Yin,J., Alvisi,G., Dahlin,M and Iyengar,A. (2002) Engineering web cache consistency ACM Transactions on Internet technology, 2(3),224-229. Available from http://www.research.ibm.com/people/i/iyengar/toit02.pdf (10 January 3003). If the article has been published solely on the internet you should attempt to record as much information as you would collect for a printed article. In many cases volume and issue numbers will not exist, but you should attempt to record at least the following: Full names of the authors (may be an organisation), Year of publication, Full title of article, Full name of on-line journal, Publisher, Place of publication (if known) Internet address, Date of access For example: DSDM Consortium (2002) The Underlying Principles DSDM Website. Available from http://www.dsdm.org/en/about/principle.asp (accessed 7 January 2003). Students can also reference CD-ROM, online databases, email etc. visit: http://libweb.anglia.ac.uk/referencing/harvard.htm for more information.

27