Courier and cargo management system

Abstract

This project proposal is about Cargo and courier management system developed using PHP, JavaScript and MYSQL. This system is an online application which can be hosted on the company’s website and therefore the user needs an internet connection or the company’s local area network. The proposal is divided into three major parts name: chapter one, chapter two and chapter three. Chapter one introduces the cargo and courier management system and explains how courier companies emerged. The problem statement has been identified under this chapter since most courier companies are still using the manual systems and delays in delivery of services are bound to occur. The chapter ends with a study of project objectives that should be achieved at the end of system development. Chapter two covers the literature review under which the background of the proposed system has been discussed. Examples of cargo ships and couriers are covered in details to bring out the differences between the two. Literature review aims at reviewing the existing systems so that in case there is one that meets the needs, then it can be adopted instead of wasting time and other resources re-inventing another. Chapter three covers the methodology used in developing the system. The methodology applied in this case is waterfall model which follows the steps of system development life cycle (SDLC). This is because it was best suited for a system that can be deployed in parallel changeover mode. The steps discussed under waterfall model include: requirement gathering and analysis, system design, implementation, integration and testing, deployment of the system and maintenance. Other types of software methodologies discussed include: code and fix, spiral development and rapid prototyping. The chapter ends by discussing the requirements for the proposed systems that is both hardware and software requirements. Chapter four covers the system analysis and requirement modelling. The following have been discussed under this chapter. Current physical model, current logical model, description of the existing courier system, data flow diagrams, uml diagrams (activity diagram for the current system), use case diagram for the current system, component diagram for the current system, facts and data gathering, process of interviewing, disadvantages of the existing system, advantages of the proposed system required logical model and conclusion. Chapter five discusses system design. Under this chapter the following have been discussed: data flow diagrams, flow chart for the proposed system, unified modelling language diagrams for the proposed system, class diagram for the proposed system, use case diagram for the proposed system, use case diagram (branch admin), activity diagram for the branch admin, activity diagram for the user, sequential diagram (admin), entity relationship diagram, database design and interface design. Chapter six: this chapter discusses implementation of the system. Under this chapter the following have been discussed: form input design, tools used for coding, testing plan has been discussed in details to show testing adopted for the system, the chapter ends by discussing the type of proposed changeover method for the system. The changeover method proposed for the system is parallel changeover method. Chapter seven: this is the last chapter of this report. The following have been discussed under this chapter. Limitations of the proposed system, conclusions and recommendations.