apu project handbook

Table of Contents

Asia Pacific University of Technology & InnovationAsia Pacific University College of Technology and Innovation

Asia Pacific University of Technology & InnovationProject HandbookInformation Technology Programmes

Interactive Entertainment Programmes

Applied Information Technology Programmes

Table of Contents

1.Introduction42.Project Processes52.1.Duration52.2.Assessment53.Project Responsibilities53.1.Responsibilities of a final year project student:53.2.Responsibilities of a supervisor are to:63.3.Responsibilities of the second marker are to:63.4.The Project Leader63.5.Project Administrators73.6.Project Team74.Project Report84.1.Project report style84.2.Project report structure85.Project Description96.Project Assessment97.Project Submission & Extensions9APPENDICES10

Appendix A : Project Team 10

Appendix B : Project Description and Suggested Titles 11

Appendix C : Draft Project Proposal 13

Appendix D: Project Specification Form14

Appendix E : Timelines 15

Appendix F : Minimum Requirements for Investigation, Analysis & Design Report21

Appendix G : Minimum Requirements for Final Report 23Appendix H : Project Report Format25

Appendix I : Title Page 26

Appendix J : Referencing 271. Introduction

One of the most challenging aspects for an undergraduate degree is undertaking the Final Year Project (FYP). Each student must complete his / her FYP where he / she is expected to apply the knowledge and skills gained through modules that were covered as well as new knowledge and skills which were discovered and developed during the duration of the project. The project must involve the investigation, analysis, development and testing of a solution for a real-world problem in a managed approach within the given time frame. It is necessary for the student to demonstrate academic ability (i.e. critical analysis some of the models and theories) and practical skills (for example design, fianancial analysis and programming) with an equal emphasis.

This is a major piece of work that is the equivalent of three modules and is worth 10.5 credits at Level 3. Therefore, it is expected that student will spend about 420 hours working on the project over the two semesters. The first semester will consist of two project related modules namely the Investigations module and part of the Project module. Contact hours for both the modules in the first semester would comprise of scheduled briefings with project team members and supervisory meetings with an appointed project supervisor.

All the projects by students from the Information Technology, Interactive Entertainment and Applied Information Technology programmes should contain a large enough element of software demonstrating that the student can produce a deliverable appropriate for the award / programme the student is in. It must be stressed that the project deliverables must be of the students own work. Any attempt to copy anothers work, or to represent anothers work, as being your own will be dealt with severely under APIITs regulations regarding plagiarism.

All the relevant materials, such as Draft Project Proposal Form (PPF), Project Specification Form (PSF), documentation guidelines and slides used in briefings is made on available on MOODLE which is accessible from http://webspace.apiit.edu.my/ver2/APU Project Assessment and Guidance Online (APU PAGOL) shall be used by all final year project students to submit their PSFs online as well as to maintain an online diary which can be viewd by supervisors and second markers in order to monitor the students progress. 2. Project Processes 2.1. Duration

Students will complete the project over TWO (2) semesters Project Timelines in Appendix E. Students are reminded to constantly refer to the timelines furnished during the commencement week for further details. Any changes to the timelines and / or datelines will be made known to the students via email and / or during the project briefings. 2.2. Assessment

The project is a very important part of the undergraduates degree; it accounts for 25% of the marks at level 3. As such the Award Board tends to treat the project modules differently from other modules at level 3. It may also exercise its discretion by applying compensation to project modules less generously than it might do for other modules. Students would need to bear this in mind when allocating their effort between their FYP and other modules.In common with all work at Levels 2 and 3 the project is subject to moderation by internal examiners as well as external examiners from both SU and universities appointed by SU. This is designed to safe guard the standards of the degree as well as to protect the students interests.

3. Project Responsibilities

3.1. Responsibilities of a final year project student:

Define an appropriate area of investigation/research. Arrange, prepare for and attend regular meetings with his / her supervisor and record such meetings in the online diary on APU PAGOL and the Project Log Sheet. Complete and submit the draft project proposal form. Complete and submit the Project Specification Form using the APU PAGOL.

Complete and submit the appropriate Ethics Form before carrying out the research.

Plan, carry out, manage and document the investigation and project work and maintain a file of such work. Submit the Investigations, Analysis and Design report at the specified dateline. Attend the Signing Off Learning Contract session with his / her supervisor to get feedback on the research done to date

Develop and test his / her artefact and provide supporting documentation of the work done.

Submit the documentation in the correct format by the specified dateline. Present his / her artefact and discussion of the work done.

3.2. Responsibilities of a supervisor are to: Discuss with supervisee and thereupon agree on a learning contract of the FYP that the student will embark, including methods, deliverables, milestones and meetings Be available, where possible, for regular pre-scheduled supervisory meetings with the supervisee and, by appointment at other times, either through Lecturer Consultaiton System or email, within reasonable time frame in relation to the learning contract. Provide supervisee with reasonable assistance in obtaining access to advice, material and resources with which to carry out the project. Provide supervisee with reasonable support and advice on managing, documenting and presenting the project. Approve / Reject PPF / PSF. If PPFs are to be rejected, the supervisor shall advise the students accordingly before the student prepares the PSF. Ensure that any changes to the project proposal and specification, which were discussed and agreed upon by both the supervisor and second marker, are made and adhered to by the supervisee.

3.3. Responsibilities of the second marker are to:

Mark and comment of PSF Together with the supervisor, mark and provide reasonable comments in the Investigation, Analysis and Design report on how the project and research can be improved. Together with the supervisor, mark the FYP artefact, documentation and presentation. 3.4. The Project ManagerThe overall role of the Project Manager is to manage the process. More specifically the responsibilities will include:

advising new supervisors and second markers as to what is expected of them and the project in relation to the award;

briefing the students at the start of the award on project processes and what is an acceptable project; receiving the project proposals (PPFs); consulting with the Group Leader on the allocation of projects to the academic groups. Staff loads within each group to be monitored using APU PAGOL. The proposals (PPFs) will be forwarded to the appointed supervisors;

making sure that all the PPFs, PSFs and Signing Off Learning Contracts have been assessed within a reasonable time period and appropriate feedback have been given back to the supervisees;

monitoring the support given to the students by their supervisors;

monitoring of conformance to datelines and reporting non conformances to the academic group heads;

ensuring that the mark spreadsheet is available for the module and award boards;

ensuring the necessary facilities and assistance is provided to students who fail and would need to retake the project;

maintaining the APU PAGOL system

3.5. Project AdministratorsAPU has designated two persons (Ms. Chow Yee Mei and Ms Punitha) from the administration to manage day-to-day projects matters as follows:

(i) Responsible for scheduling of Signing Off Learning Contracts and final presentations

(ii) Sending out letters

(iii) Advise on payment of fees related to referrals(iv) Administration of certain functionalities within APU PAGOL Miss. Yee Mei can be contacted at [email protected] (ext. 5137)

Miss. Azizatun Zahariah Binti Alias can be contacted at [email protected] (ext. 5126)Miss.Punitha can be contacted at [email protected] (ext. 5126)3.6. Project Team

The Project Team consists of the following lecturers who you may additionally consult in the absence of the Project Manager(s) and / or your supervisor. You may also meet them to obtain insights, suggestions or advice pertaining to your project. 4. Project Report

Undertaking a project is not a sequence of unrelated activities. A good project is based on a systematic, well-managed or 'engineered' approach with a sound philosophical foundation. The fundamental principal of carrying out an effective project is to match the project plan to the resources that are available for its completion. Disruption to the project can be minimised by setting a realistic time scale for completing the activities and for presenting the deliverables in a way that takes into account any other commitments. All of this has to be documented in the project report (the major deliverable), which will be handed in at the submission date.

4.1. Project report style

The report should be written in a formal style in the third person form. For instance, 'It was found that...' is expected instead of 'I found that...'. Careful attention should be paid to the use of grammar and correct spelling, and students are encouraged to use such aids as are available for this purpose. You are expected to use italics for words in languages other than English (e.g. pro forma) and capitals to begin proper nouns (e.g. MS Windows). If you wish to paraphrase or comment on another author's work, appropriate reference should be made according to the Harvard system (Appendix J). This also applies to material gained from electronic sources such as the World Wide Web, although students are reminded that such sources are often not refereed and may not have the same authority as academic journals.

If a direct quote (i.e. the use of another author's exact words) is made, this should be placed in quotation marks and references with the page number on which they appear in the source document. Long quotations should be used sparingly and only when they are particularly relevant. Students are reminded not to use diagrams / images without first obtaining the permission from the necessary source. Students are reminded of the importance of originality and consequences of plagiarism.

4.2. Project report structure

The range of project titles covers a variety of topic areas with different emphases, therefore impossible to be prescriptive about the organisation of project documentation. However, it is possible to suggest a general structure for a 'typical' computing project report for both the Investigations, Analysis and Design Report and the Final Report see Appendices F, G and H It is particularly important to pay attention to the structure of the report, as a poorly structured document is unlikely to do justice to the contents in terms of assessment.

5. Project Description

A brief description of what is expected of your final year project according to your award and / or specialisation, as well as its theme and an updated list of FYP titles are available in Appendix B6. Project Assessment

The APU Project Assessment Marking Scheme (APU PAMS) will be used to determine the marks to be awarded. It should be noted that you are required to pass each module of the project. If you fail to achieve a mark lower than 50% in any module it is likely that you may be required to rework and resubmit that module as well as pay a referral fee.

7. Project Submission & ExtensionsA soft copy of the project on a DVD (or CD) containing the implementation and documentation must be submitted either before, or on, the submission date. Kindly refer to Appendix H for report format.

Late submissions will not be accepted (i.e. deemed an automatic fail) unless there are extenuating circumstances involved that are backed-up with evidence.

Extenuating circumstances usually consist of an incapacitating illness or events that are outside the students control which makes study very difficult (for example, a death in the family). Please ensure you submit a fully completed Extenuating Circumstances Form.

You may also defer submission date if your circumstances significantly change during your period of registration. However, any deferment should be applied for at least one month before the actual submission date. Should the request to defer the submission is anything less than a month from the actual submission date, the student would be required to submit a completed Extenuating Circumstances Form with the necessary evidence.

Appendix A Project Team

(i) Mr David Tan & Ms Salmiah specialising in Network Computing and IT in Network Computing

(ii) Mr Au Yit Wah specialising in Mobile Technology

(iii) Dr Ali specialising in Forensic Computing, Information Systems Security, Computer Security and Digital Forensics

(iv) Ms Khalida specialising in Enterprise Computing

(v) Mr Kesava & Mr Siva Chelliah specialising in Software Engineering

(vi) Mr Nicholas & Mr Leong Swee Kee specialising in Business Information Systems, Technopreneurship, Business Information Technology, E-Commerce, Business Computing

(vii) Ms Mary & Ms Vinothini specialising in Intelligent Systems and Information Technology

(viii) Mr Harsha Rao specialising in Games Development and Game Design.

(ix) Mr Harsha Rao & Mr Naresh specialising in Web Media Technology, Multimedia Technology, Digital Audio, Computer Graphics & Imaging, and Animation.

(x) Mr Wong Chung Wei specialising in Web Programming & Internet Technology

(xi) Mr Selvakumar specialising in Database Administration & Management

(xii) Mr Ehsan Rana specialising in Computer Science

(xiii) Mrs Kwan specialising in Computational Mathematics and Industrial Modelling

(xiv) Ms Zety Marlia specialising in Technology in Teaching and Learning

Appendix B Project Description and Suggested Titles

BSc (Hons) in Software Engineering

Main Theme:

Software Engineering projects are developmental projects undertaken in a structured organized approach leading to the development of a computer application which includes not only the development of software and hardware systems, but also of process models, methods and algorithms. It may well include evaluation, requirements documentation, designs, analyses and fully documented test results, along with user manuals or guides.

Description:

Emphasis is placed on the development and evaluation of a piece of software following a particular process models that generate interim evaluator documentation. An analysis (e.g. of user requirements) and a formal design is expected, with a sophisticated implementation evaluated against a balance of technical and functional criteria.

Sample Projects:

Project Management Resource Optimization System

Human Resources Monitoring System

Document Creator and Management System Home Security Surveillance SystemBSc (Hons) in Enterprise ComputingMain Theme:

Development of a technical solution to an enterprise computing problem, but the range is restricted to enterprise software (application development), real-time systems, database systems, infrastructure and robust technologies.

Description:

Application area which is amenable to improvement by the enterprise computing solution which identifies common problem domains within a business and provides a shared infrastructure as a solution for those identified problems.

Sample Projects:

An Enterprise Intranet System for Asset Management An Enterprise System for Pharmaceutical Products Distributions Live Stock Database System

Customer-centric Advertisement Board in Social Network

BSc (Hons) in IT with Specialism in Network ComputingMain Theme:

Production of a system, tool or application that is well documented able to solve real world network problems available in any Information Technology industry.

Description:

Developing the project in one of the following domains: network monitoring, network analysis, network management, network auditing, and network issues.

Sample Projects:

Network monitoring system communication

Data centralization system over network

An Application of Shortest Path First Algorithm (SPF) in Intelligent Vacation Recommender

A network application of ambulance routing

Network lab management system

Personal entertainment network system

Network auditing management system

Network load distribution and balancing system

WAP Reservation System

Wireless Network Theft Monitoring System

Network Server Monitoring System in Local Area Networks

Network Performance Analysis SystemBSc (Hons) in Network ComputingMain Theme:

Development of a technical solution and well documented network computing recommendations to solve real world network problems available in any industry.

Description:

Students expected to show how to test and solve real network problems such as network routing protocols and algorithms, network resources and services problems, network mechanisms, tools and applications to monitor and analyse network issues.

Sample Projects:

Analysis of Dynamic Network Routing Protocols

Remote Server Control by desktop through Internet

Wireless Integrated System for Efficient Restaurant

Online network device controller

Network stopwatch

Automatic IP allocation detection for institution labs

Finding the Quickest Time Route using the Dijkstras Algorithm

BSc (Hons) in Technopreneurship

Main Theme:Development of a technical solution to an entrepreneurship problem

Description:Using appropriate technologies such as web development, mobile technology, social media, database management, data mining, or any other pertinent technologies learned throughout the bachelor degree programme, student will develop a prototype of the proposed solution in a simulated environment in an entrepreneurship perspective, which consist of areas such as business management, supply chain management, e-commerce, marketing, customer relationship management, and other areas suggested by students provided it is relevant to the specialism.

Sample Projects: E-Commerce System Enhancement for Keith EyeLab

Fuel Inventory Monitoring System using SMS APIIT Library Mobile Customer Relationship Management System

BSc (Hons) in Business Information Technology

Main Theme:Development of a technical solution to a business management problem

Description:Using appropriate technologies such as web development, mobile technology, social media, database management, data mining, or any other pertinent technologies learned throughout the bachelor degree programme, student will develop a prototype of the proposed solution in a simulated environment in a business management perspective, which consists of areas such as e-commerce, supply chain management, procurement, quality management, e-learning, and other areas suggested by students provided it is relevant to the specialism.

Sample Projects:

KK Mart E-Commerce Portal and Delivery System HealthNet A Wellbeing Online Community and Healthcare Business Portal Online E-Tuition

Appendix C Draft Project Proposal

Office Record

Date Received:

Received by whom:

Receipt

Student name:

Student number:

Received by:

Date:

Draft Project Proposal Form

Student Name:

Student No:

Email Address:

Programme Name:

Title of project:

Please record which modules your topic is related to:--------------------------------------------------------------------------------------------------------------------------- Instruction:

This is the draft proposal of your FYP which needs to be submitted to the project administrator by hardcopy refer to your timeline for submission deadline.

1. Introduction

Assume the reader has very little knowledge of the subject.

Introduce the topic, the sector of business/industry concerned and how the project relates to it. Define the context of the problem and identify the research required to solve it.

2.Problem Statement

Identify past and current work in the subject area.

Outline the key references to other peoples work, indicate for the most pertinent of these how your proposal relates to the ideas they contain.

3.Project Aims and Objectives

Identify the AIM(s) of the project, i.e. what the overall achievement is intended to be, in terms of both academic and commercial/industrial advances.

Identify the particular intellectual difficulties posed by the proposal, the problems to be addressed, and explain how these might be solved.

Clearly list individual measurable OBJECTIVES which can be related to the workplan and deliverables.

Aims and objectives are subject to approval from supervisor and students are expected to revise them if deemed inappropriate for a Level 3 project.4.Deliverables

Provide a clear list of the outputs from the project.Appendix D Project Specification Form (PSF)A. Project Title.

B. Brief description on project background.(.i.e. problem context, rationale, description of problem area, nature of challenge)

C. Brief description of project objectives.(i.e. scope of proposal and deliverables)

D. Brief description of the resources needed by the proposal.(i.e. hardware, software, access to information / expertise, user involvement etc.)

E. Academic research being carried out and other information, techniques being learnt.(i.e. what are the names of books you are going to read / data sets you are going to use)

F. Brief description of the development plan for the proposed project.(i.e. a general description of the development plan, the major areas of functions to be developed and the order in which developed)

G. Brief description of the evaluation and test plan for the proposed project.(i.e. what is the success criteria and how will be evaluated & implementation will be tested, indicate the estimated size of the demonstration/test database)

Appendix E Timelines

Timelines for APU Final Year Project

Investigations, Analysis and Design (Semester 1)

Information Technology / Interactive Entertainment / Applied IT Programmes DATE (Week Beginning)EVENTStudent ActivityReference

1

(Orientation)Session 1: FYP Commencement Briefing Set timescale for conducting work and review of milestones

Read description and requirements of project specialism from Project Handbook. Commence preliminary research on suitable topic for project

Discuss with lecturer and/or CTI staff to obtain inputs on specific topic and/or research interest during session with supervisors

Preparation of Draft Project Proposal (PPF) MOODLE Project Handbook

Staff Directory: http://webspace.apiit.edu.my/staff_profile/index.jsp

2Milestone 1:

Draft Project Proposal Submission

Assigning of supervisors and second markers

Download draft proposal

form from MOODLE

3Supervisor Clinic: Proposal Review

Attend supervisor clinic see timetable for venue and time Refer to APU PAGOL / email to know who your supervisor is.

4Session 2: Project Specification Writing Prepare draft Project Specification (PSF)

MOODLE

5Session 3:

Ethics

Supervisory Meeting Project Specification Writing Prepare Ethics form

Meet supervisor having booked an appointment via consultation hour. Log Sheet

6Supervisory Meeting Ethics Form & Project Specification Writing

Milestone 2:

Ethics Form (Part 1)Submission

Meet supervisor having booked an appointment via consultation hour.

Submission of Ethics Form (Part 1) after obtaining supervisors signature. Ensure you make a photocopy of the signed Ethics Form which must be included in the Investigation Report and the project documentation. APU PAGOL Log Sheet

7 Milestone 3:

Project Specification Form Submission Completion and submission of PSF

APU PAGOL

Log Sheet

8Session 4: Project Objectives and Project Management

Supervisory Meeting Project Objectives and Project Management

Begin research plan and initial research to produce Chapter 1 of the documentation Meet supervisor having booked an appointment via consultation hour.

If PSF was rejected by supervisor or advisor, immediately meet your supervisor or Project Leader MOODLE

Log Sheet

9 - 11Session 5:

Research Literature Review / Secondary Research / Primary Research

Supervisory Meeting Research

Proceed with research


Remember to get questionnaire / survey / interview questions and / or observation / experiment checklists approved by supervisors before carrying out primary research

Submission of Ethics Form (Part 2) after obtaining supervisors signature. Log Sheet

12Session 6:

Analysis & Design

Supervisory Meeting Analysis & Design

Proceed with Analysis and Design


Supervisors to create turnitin accounts for supervisees Log Sheet

13Session 7: Documentation & Presentation Requirements

Supervisory Meeting Analysis & Design

Complete Investigations, Analysis and Design report

Insert completed documentation into Turnitin and make changes where necessary Turnitin

14Milestone 4:

Submission of Investigation, Analysis and Design Report Go through Project Handbook to ensure report is in the right format including cover page.

Report must be submitting along with Signing Off Learning Contract form (carbonized version provided along with the commencement pack) during orientation week. MOODLE

15 - 16Signing Off Learning Contract Both supervisor and second marker mark and provide feedback on the Investigations, Analysis and Design Report

See schedule posted at Webspace / sent via email to know the actual date and time you will have to meet your supervisor for the Signing Off Learning Contract

If your name does not appear on the schedule, send an email to your Project Leader

Feedback given to student and learning contract form handed over by supervisor during Signing Off Learning Contract session.

Supervisor may provide feedback and seek clarifications on the project.

Supervisees are expected to consider inputs provided and make due corrections and/or changes to the research where applicable and expected.

Student to sign-off learning contract based on outcome of research investigation in the presence of supervisor.

Note: Where dates are stated as week number, please refer to timetable for specific date, time and venue. A supervisee is expected to engage in a meeting with his or her supervisor once during each mandatory supervisory meeting. Hence there are a total of 6 meetings expected from a student. Failing to do this amounts to poor project management (planning) resulting in marks being affected. Students must ensure appointments are made in advance. If a supervisor cannot be reached after repeated attempts, the projects manager must be duly informed and a meeting will be consequently arranged.

Project ( Semester 2 )Week BeginningACTIVITYStudent ActivityReference

1Session 8:

Review of the feedback from previous semester

Supervisory Meeting


2Session 9: Implementation of Artefact

Supervisory Meeting


3Session 10:

Testing / Evaluation mechanism

Supervisory Meeting Meet supervisor having booked an appointment via consultation hour. Log Sheet

4Session 11:

Reflection on project


5Session 12:

Presentation and Submission


6 - 14Independent work on artefact and documentation

Supervisory Meeting Meet supervisor having booked an appointment via consultation hour.

Show supervisor progress of final system and documentation Log Sheet

14Milestone 5:

Submission of Artefact and Documentation (Comb-bound & DVD / CD) Collect submission form ( pink form )

Review submission guidelines within Project Handbook

Print and bind project ( comb binding ) with DVD / CD attached


15Milestone 6:

Submission of Documentation (Hardcover Bound)

Use pink form for submission

Review submission guidelines within Project Handbook

Print and bind project (hardcover)

15 - 18FYP Presentation* Rehearse for presentation

Thoroughly scrutinize documentation and artefact

Refer to Project Handbook on preparation of slides for presentation

Check schedule for presentation date and time

Foreign students who would need to an early presentation may write in to the Project Leader to request the same.

Schedule at Webspace

Note: Where dates are stated as week number, please refer to timetable for specific date, time and venue. A supervisee is expected to engage in a meeting with his or her supervisor once during each mandatory supervisory meeting. Hence there are a total of 6 meetings expected from a student. Failing to do this amounts to poor project management (planning) resulting in marks being affected. Students must ensure appointments are made in advance. If a supervisor cannot be reached after repeated attempts, the project manager must be duly informed and a meeting will be consequently arranged.

*FYP presentations will NOT be held during examination week.Appendix F MINIMUM REQUIREMENTS FOR INVESTIGATION, ANALYSIS AND DESIGN REPORT

CHAPTER 1: INTRODUCTION TO THE STUDY

Background to the project

This should include the identification to the problem situation and the rationale for carrying out the project, based on review of past research work where the gaps are identifiedScope and objectives

Identify clearly the scope, in terms of the level of challenge. Specifically identify areas / functionalities which will not be consideredProject plan

Description of how the project will proceed and how it would be evaluatedCHAPTER 2: LITERATURE REVIEW

Analyse the existing literature and give justification as to how your research will fit into the existing body of knowledge (CQU Library, 2000)

Introduction

Domain Research

Depending on the area of research Contribution to the body of knowledge that is relevant to the research problem,

How it compares and contrasts with the positions developed by other researchers.

Similar Systems

Technical Research Language

Database

Architecture

Methodology

Conclusions

Note: Literature Research materials should be from academic sources, journals, conference proceedings and books as far as possible. Do not merely cite what others are saying about the various aspects / concepts etc but analyse and use what they are saying to justify why you are doing what you are doing as well as how you plan to carry this out.CHAPTER 3: PRIMARY RESEARCH

Introduction

Explain which primary research you have considered justify your reason for the selection

Note:

For each primary research you have chosen,

If it is questionnaire, survey or interview, list the questions asked, the objective of the question(s), the findings and the conclusions. Also, note that it is not mandatory each question should have a different objective / finding / conclusion. You could have one objective for a couple of questions and hence, have one set of findings with one conclusion. If it is observation, prepare a checklist of what is to be observed. Include the objective, findings and conclusions. Ensure the questions and checklist are pertaining to the project / what you intend to do and not generic in nature.

Supervisors should approve the questions / checklist, before these are used by signing the 2nd part of the Ethics Form.

Questionnaire / Survey

Question Objective

Findings

ConclusionInterview

Question Objective

Findings

Conclusion

Conclusion

Overall conclusion of your primary research based on your objectives were these fulfilled? Were your doubts cleared through the findings? What is the impact of the findings on your overall project aims and objectives?CHAPTER 4: ANALYSIS

Reintroduce your requirements / project aims and objectives. Relate how the findings of the various research methods applied affected your decision to either retain the requirements or make changes to them. Provide examples from your findings to support your decisions.

CHAPTER 5: DESIGN

Introduction

Which modeling tool was chosen for this project? What designs will be produced in this chapter?

Note: Include here appropriate designs to represent the system, the database, the interface, etc.

For each set of designs produced, provide explanation on what was produced and how it relates to the analysis.

Ensure the designs relate to the system to be produced

Additional designs that cannot be included in the documentation can be included in the CD insteadCHAPTER 6: CONCLUSION AND RECOMMENDATIONS

What was achieved at the end of the first leg of the project?

Were you able to do enough investigation / research with regards to what you want to achieve / do?

Were there any gaps in your research, analysis and design where you may want to further explore and identify/ improve?REFERENCES

APPENDIX

Log Sheet

Gantt Chart

PSF

Ethics

Interview/Questionnaire sample (some with answers)

Statistics- This can be included in CD / DVD and omitted from the AppendixAppendix G MINIMUM REQUIREMENTS FOR FINAL REPORT

CHAPTER 1: INTRODUCTION TO THE STUDY Background to the project

This should include the identification to the problem situation and the rationale for carrying out the project, based on review of past research work where the gaps are identifiedScope and objectives

Identify clearly the scope, in terms of the level of challenge. Specifically identify areas / functionalities which will not be considered

Gaps Identified

Identify gaps from previous documentation / research investigation, analysis and design. This is based on feedback from Signing Off Learning Contract, discussions with supervisor and second marker, and your own thoughts / reflections / later findings. Can be from any chapters of the previous documentation.Project plan

Description of how the project will proceed and how it would be evaluatedCHAPTER 2: LITERATURE REVIEW

Introduction

Domain Research

Technical Research Language

Database

Architecture

Methodology

Conclusions

CHAPTER 3: PRIMARY RESEARCH

Introduction

Explain which primary research you have considered justify your reason for the selection

For each Questionnaire / Survey / Interview / Observation / Experiment Question Objective

Findings

ConclusionConclusion

Overall conclusion of your primary research based on your objectives were these fulfilled? Were your doubts cleared through the findings? What is the impact of the findings on your overall project aims and objectives?CHAPTER 4: ANALYSIS

Reintroduce your requirements / project aims and objectives. Relate how the findings of the various research methods applied affected your decision to either retain the requirements or make changes to them. Provide examples from your findings to support your decisions.

CHAPTER 5: DESIGN

Introduction

Which modeling tool was chosen for this project? What designs will be produced in this chapter?

Note: Include here appropriate designs to represent the system, the database, the interface, etc.

Additional designs that cannot be included in the documentation can be included in the CD insteadCHAPTER 6: IMPLEMENTATION

Note:

In this chapter, demonstrate how the literature review led to the implementation

demonstrate / illustrate how the design flowed into the implementation explain how you exploited / utilized the package to meet the requirements

include codes that were challenging identify the challenges you encountered in the implementation and how you overcame these challenges

DO NOT CODE DUMP

CHAPTER 7: TESTING

Introduction

Which testing will / did you decide to do & Why

EACH TEST PLAN

Include who the testers were and what was the outcome

Have a conclusion for each test

Note the difference between unit (developer) and functional (user) testing

Conclusion

Implication in reference to the PSF (if any) what you started out to do

Any changes made if yes what were they comments received

If not why not?CHAPTER 6: CONCLUSIONS AND RECOMMENDATIONS

Critical Evaluation what would you have done different

What is your learning curve?

Conclusions relating to the Research ObjectivesRecommendations and SuggestionsLimitationsSelf-Review (How the project was managed)Further research

Conclusion

REFERENCES

APPENDICES Log Sheet

Gantt Chart

PSF

Ethics

Interview/Questionnaire sample (some with answers)

Statistics- This can be included in CD / DVD and omitted from the Appendix

Designs This can be included in the CD / DVD and omitted from the Appendix

Appendix H Project Report FormatAn adequate project report will be between 12,000 and 20,000 words in length, excluding the log sheet and the appendices. The number of pages in total should not exceed 200 including log sheet and appendices. The student may choose the font Times New Roman but the main text must be 10 or 12 point type with line spacing of 1.5. Chapters, headings and pages should be numbered sequentially for reference. The report must be laser-printed or high quality printed on A4-size paper with a weight between 70 and 100g/sm and should be on the right-hand (i.e. recto) page with a left margin of 40-50mm and other margins of 15-20mm. The final report must have a title page bearing the following information (see sample title template):

The full title of the project.

The full name of the student as registered with APU.

The Student ID in brackets.

The award for which the student is registered.

A statement that the qualification is awarded by Asia Pacific University of Technology and Innovation and that the report is submitted in partial fulfilment of that programme.

The full name of the supervisor.

Month and year when submitting project

The spine of the hard-bound copy of the report must have:

The full title of the project (on the left of the spine when the title page is facing upwards).

The full name of the student (on the right of the spine)

The Student-ID in brackets (on the right of the spine, below the name)

Two copies of the report will be submitted, one soft-bound and one hard-bound. The soft-bound copy will be accompanied by a DVD/ CD containing softcopy of project documentation and source codes of the running program. The soft-bound copy of the report and the DVD / CD must be submitted on the due date. The hard-bound copy must be submitted up to a week later, this copy will be retained by UCTI and might be put on display if judged to be of a suitable quality. The colour of the covers in the hard-bound copy will be dark blue. DVD / CD is not required for the hard-bound submission. Important Notes:

1. The DVD / CD submitted shall be used during presentation to demonstrate the final system. Please verify the contents of the DVD / CD before submission.

2. Students are expected to bring along their own computer during presentation. Students may alternatively opt to use the desktop computer in the presentation room. However, it is the sole responsibility of the student to ensure that the system is sufficiently tested (inclusive of software & necessary components) prior to the presentation. Arrangements can be made with the lab assistant if assistance is required. Such request if any should be planned well in advance. Appendix I Title Page

1 Stop Personal Knowledge Based SystembyAILEEN MA YEW YUEN(TP010339)UC3F1002 ITP{IS}BSc (Hons) in Information Technology with Specialism in Intelligent SystemsAsia Pacific University College of

Technology & InnovationA project submitted in partial fulfilment of the award of the Bachelor of Science (Honours) in Information Technology with Specialism in Intelligent SysemsSupervised by Mary TingAppendix J Referencing The most commonly accepted and used method of referencing is known as Harvard. Be sure to use this to avoid any risk of plagiarism and to receive full reward for the research you conduct.

1. In the text include:

a. The authors surname

b. The year of publication

c. Page number(s) if appropriate

PunctuationAfter the date use either a colon followed by the page number on which the quotation can be found (1997:12) or a comma followed by P. and the page number (1997, P.12), it is conventional to put pp. when the quotation or theme covers more than one page (1997, pp. 12-15).

2. In the list of references at the end of the text include:

a. The authors surname (followed by a comma) e.g. Smith,

b. The authors initial(s), (followed by full stops) e.g. Smith, P.

c. The date of the publication of the work cited (written in brackets) e.g. Smith, P. (1997).

d. If the work is a book, the title (in Italics followed by a coma) e.g. Smith, P. (1997) Promotional Communications,e. The place of publication (followed by a comma) e.g. Smith, P. (1997) Promotional Communications, London,

f. The name of the publisher (followed by a full stop) e.g. Smith, P.(1997) Promotional Communications, London, The Academic Press.

g. If the work is an article, include the title of the article (in inverted commas, followed by a comma) followed by the volume number and pages on which the article appears in the journal (each followed by a full stop) e.g. Jones C. (1997) The Rudiments of Reflection, Journal of Advanced Education, Vol.12, No.3, pp.23-26.

APU library website link below will show you how to cite traditional references as well as internet and electronic sources.

http://crypto.apiit.edu.my/library/ReferenceSite.htm

2127Project Handbook

apu project handbook

Documents