Intranet-Based Wiki with Instant Messaging Protocol

 – Intranet-Based Wiki with Instant Messaging Protocol –

Download Intranet-Based Wiki with Instant Messaging Protocol project materials: This project material is ready for students who are in need of it to aid their research.

ABSTRACT

This project developed an Intranet-Based Wiki with Instant Messaging Protocol (IBWIMP) for the Staff of the Department of Computer Science, University of Nigeria, Nsukka to enable them collaborate on tasks; like writing of documents like, memo, project guidelines, proposal/grants, and circulars with online security consideration.

The essence of this work is to improve on the contributions staff make during work, in carrying out tasks with their colleagues irrespective of the person’s location at that point in time.

The existing system on ground would always require the presence of the staff within the department before they can carry out the tasks meant for them or respond to the available mails within their mail boxes located within the general office of the department.

In regard to such situation, there is always delay in the processing of such mails or documents that could require urgent attention of the supposed staff therefore could cause serious damages.

This project established a better internet connection for the security of the system and the documents therein by the use of virtual private server (VPS) hosting on virtual private network (VPN).

This system allows the collaboration between the staff of the department and external persons or partners classified as external staff user on documents like circulars that normally come from outside the department.

This system automatically sends emails to the supposed users whenever the admin posts a document via the Short Message Transfer Protocol (SMTP).

The system is accessed online by the users from any location once there is internet connection available and users can collaborate on the development of any posted document at the same time.

This application was designed using Object Oriented Analysis and Design Methodology (OOADM) and implemented using Hypertext Markup Language (HTML), JavaScript, Cascading Style Sheet (CSS), CkEditor, Hypertext Pre-Processor (PHP) and MySQL database management system.

TABLE OF CONTENTS

Title page – – – – – – – – – – i
Certification – – – – – – – – – – ii
Approval – – – – – – – – – – iii
Dedication – – – – – – – – – – iv
Acknowledgment – – – – – – – – – v
Abstract – – – – – – – – – – vi
Table of Contents – – – – – – – – – vii
List of figures – – – – – – – – – – ix
List of tables – – – – – – – – – – x

Chapter 1: Introduction

1.1 Introduction – – – – – – – – – 1
1.2 Statement of the problem- – – – – – – – 2
1.3 Aims and objectives of the study- – – – – – – 2
1.4 Scope of the study- – – – – – – – – 2
1.5 Significance of the study- – – – – – – – 3

Chapter 2: Literature Review

2.0 Introduction – – – – – – – – – 4
2.1 Theoretical Background – – – – – – – 4
2.1.1 The Technological Approach – – – – – – – 4
2.1.1.1 HTML (HyperText Markup Language) – – – – – – 4
2.1.1.2 CSS (Cascading Style Sheet) – – – – – – – 5
2.1.1.3 PHP (Hypertext Preprocessor) – – – – – – – 6
2.1.1.4 JavaScript – – – – – – – – – – 7
2.1.1.5 CKEDITOR – – – – – – – – – 7
2.1.1.6 MySQL – – – – – – – – – – 7
2.2 Review of Related Literature – – – – – – – 8

Chapter 3: System Analysis and Design

3.0 Introduction – – – – – – – – – 12
3.1 Description of the Existing System- – – – – – – 12
3.2 Analysis of the proposed System- – – – – – – 13
3.2.1 System Requirement Specification – – – – – – 14
3.3 Design of the Proposed System – – – – – – 17
3.3.1 Database Design – – – – – – – – 17
3.3.2 Input Design – – – – – – – – – 19
3.3.3 Output Design – – – – – – – – – 20
3.3.4 The Algorithm/Flowchart of the System – – – – – 20
3.3.5 The System Architecture – – – – – – – 21
3.3.6 The Network Architecture – – – – – – – 22

Chapter 4: System implementation

4.0 Introduction – – – – – – – – – 24
4.1 Choice of Development Environment – – – – – 24
4.2 Implementation Architecture – – – – – – – 24
4.3 Software Testing – – – – – – – – 25
4.4 Documentation – – – – – – – – 30
4.4.1 User Manual – – – – – – – – – 30
4.4.2 Source Code Listing – – – – – – – – 31

Chapter 5: Summary and Conclusion

5.0 Summary – – – – – – – – – 32
5.1 Conclusion – – – – – – – – – 32
5.2 Recommendation – – – – – – – – 32
5.3 Suggested Areas for Further works – – – – – – 33
References – – – – – – – – – – 34
Appendices – – – – – – – – – – 36

INTRODUCTION

With the growing activities in both the academic and business world comes a growing amount of information: manuals, procedures, best practices, ideas, important documents, sales leads, expenses etc. Organizing all this information and processing all these documents increasingly becomes more work.

It might be a small academic department or a small business organization, but simply using notes and paper documents is less convenient for the staff, and spending all this time on sharing information by the use of manual mail boxes known as “pigeon holes” and finding back information in file repository in the file cabinets is a huge waste of time and energy.

The absence of administrative staff in the office puts a hold on the workflow, in the sense that some documents to be moved from a location in the office to another, in the name of information dissemination, remain unmoved.

As a result of that, there could be damages depending on the need for which the information is meant to meet at that moment.

Therefore, the introduction of the use of a Wiki that is Intranet-Based with an Instant Messaging Protocol will enhance the throughput of the performance of the staff in such an environment, thereby increasing their throughput on the delivery of quality services to their clients.

A wiki is an application, typically a web application, which allows the collaborative modification, extension, or deletion of content and structure.

This application will enable the staff to easily disseminate information. The application will equally grant the staff of the organization the enablement of collaborating with themselves during work from any given location.

REFERENCES

Deborah Ginsberg (2006), A Wiki Wiki (Quick ) Introduction to the Wide World of Wikis. Available at: www.aallnet.org/products/pub_sp0607/pub_sp0607_ProDev.pdf&sa=U&ved=0CBsQFj AHahUKEwifrKCKyYjJAhWC1RQKHZfuADE&sig2=SVEHXL- 5DjocHxvqsPOB4w&usg=AFQjCNHEljcgslqoqboWaTvyIyt9flulzA. Viewed 8th November, 2015.

Bradley Mitchel (2015), “Intranet.” Available at: www.compnetworking.about.com/cs/intranets/g/bldef_intranet.htm.   Viewed   1st   May, 2015.

Danielle Bibbo, James Michelich, Eric Sprehe, Young Eun Lee (2012), “Employing Wiki for knowledge management as a collaborative information repository”, an NBC universal case. Journal of Information Technology Teaching Cases. Vol. 2, pp (17–28). Available at: www.palgrave-journals.com/jittc/journal/v2/n1/pdf/jittc20121a.pdf. Retrieved 30th April, 2015.

Miloš Milovanović, Miroslav Minović, Velimir Štavljanin, Marko Savković & Dušan Starčević (2012). Wiki as a corporate learning tool, case study for software development company – Behaviour & Information Technology – Volume 31, Issue 8, pages 767-777. Available at: www.tandfonline.com/doi/abs/10.1080/0144929X.2011.642894. Viewed 29th August, 2015

Jennifer Gonzalez-Reinhart (2005). Wiki and the Wiki Way: Beyond a Knowledge Management Solution. Available at: www.uch.edu.ar/Imagenes/contenidos/wiki_way_brief1-jennifer_05.pdf. Pp.5 & 6. Retrieved 20th September, 2015.

Join Our Newsletter!

Don’t miss this opportunity

Enter Your Details

Be the first to comment

Leave a Reply

Your email address will not be published.


*