SMS Based Courier Management System in mobile app

From Champion's League Wiki
Jump to: navigation, search
Table of Contents
ABSTRACT 2
CHAPTER 1 –INTRODUCTION 3
1.1 Objectives 3
1.2 System Specifications 3
CHAPTER 2 – LITERATURE REVIEW 5
CHAPTER 3 OVERALL DESCRIPTION OF THE PROPOSED SYSTEM 10
3.1 Module Description 12
3.2 System Features 13
CHAPTER 4 – DESIGN 14
4.1UML Diagrams: 14
4.1.1Usecase Diagrams: 15
4.1.2 Sequence Diagram: 16
4.1.3 Collaborate Diagram: 17
CHAPTER 5 - OUTPUT SCREENSHOTS 21
CHAPTER 6 – IMPLEMENTATION DETAILS 22
6.1 Introduction to Html Framework 22
6.2 Cascading Style Sheets (CSS) 25
6.3 MYSQL Server 33
6.4PHP 34
6.5 ANGULAR JAVA SCRIPT 36
CHAPTER 7- SYSTEM STUDY 40
CHAPTER 8-TECHNICAL FEASIBILITY 41
CHAPTER 9-SYSTEM TESTING 44
CHAPTER 10– CONCLUSIONS 49
CHAPTER 11- REFERENCES 50




ABSTRACT
Courier management system project is management software designed by considering various factors in courier sms billing system. The proposed mobile app will help to manage customer information, package details, generate reports, sms billing. Courier management application will be a comprehensive and complete application will be able to manage all its operations and also the tracking and manage delivery info all registered consignments or packages, manage customer related information. The mobile app provide necessary info to the same as sms notifications will be send for both sender and receiver include status of booked package or consignment. User can track the courier through online site. 
CHAPTER 1 –INTRODUCTION
Mobile Courier Service system is a system that offers special delivery of packages, documents or information. Courier services usually boast of faster delivery times than any alternative method of transporting documents, and many services in the modern world. Couriers are distinguished from ordinary mail services by features such as door to door delivery, track and trace technology (US-ASEAN Business Council, 2005), speed, security, tracking, signature, specialization and individualization of services. Mobile Courier Service System is a special courier system where all courier transactions are done via a mobile phone. The system also pre-informs the user about how much it will cost them to send the package and also the arrival date of the package they want to send. The mobile courier service system also provides a map for the courier agents which will enable them to easily navigate to their picking or delivery point.

1.1 Objectives
The Application generally relates to a SMS Based Courier Management system and method to maintain transparency and efficiency in the delivery of goods through maintaining the Bill details and sending them by SMS.

1.2 System Specifications
Software Requirements: -
Front End: HTML5, CSS3, Bootstrap
Back End: PHP, MYSQL
Control End: Angular Java Script
Tools:
Android Emulator
xampp-win32-5.5.19-0-VC11
Android SDK - adt-bundle-windows-x86
IDE: Eclipse Mars
jdk-8u66-windows-i586
CHAPTER 2 – LITERATURE REVIEW
According to Wikipedia (2007), the use of courier or courier-like services has been in existence right from the ancient days. Tracing back to those days when runners and homing pigeons and riders on horseback were used to deliver timely messages. Thus initially, foot messengers physically ran miles to their destinations. To this day, there are marathons directly related to actual historical messenger routes. In the Middle Ages, royal courts maintained their own messengers who were paid little more than common labourers Small (2012). This system is not efficient because a messenger can only be allocated to one user; therefore there is under utilization of the messenger’s labour services and other resources. Following a report by US-ASEAN Business Council on Global Market ( 2005), the services provided by Courier companies share some characteristics which differentiate them from other traditional forms of delivery services: (i) Door to door delivery: This includes the seamless transfer across multiple modes of transport. The “integrated” aspect of the service offered frees the customer from the need to make complex transportation arrangements for pick-up and delivery. (ii) Close custodial control: Using sophisticated information systems that enhance security, EDS firms maintain close custodial and administrative control over all shipments. This is particularly important to reduce the risk of loss or damage to goods in transit, and (iii) Track and trace technology: Shippers and consignees may track the precise movement and location of their shipments and confirm delivery. Wikipedia Records (2007), wrote that the largest courier service in the world is the United Parcel Service (UPS), which delivers more than 12 million packages globally each day. Federal Express (FedEx) and DHL are other well-known global examples of the courier service, both with their roots in the early 1970s.
Orunga (2012) opined that parcel delivery companies experience a host of problems in their service delivery which culminate in increasing the cost of services, time wasting and poor service delivery. He further argued that lack of messaging services lead to weak audit trails for deliveries and that the manual system of managing deliveries often results to poor coordination of deliveries and collections and recommended the use of right technology to customize the services for a greater step ahead in the courier industry. His major reason for the technological approach is to increase the accuracy of courier records, and manage time effectively. Karlson et al,( 2008) took a study into the electronic file exchange aspect of courier. The study highlighted the essence and place of Courier leverages mobile phone and PCs especially in the activities of sharing of electronic files and URLs from users' personal work environment anywhere they have their phones and access to a shared display. It also portrays the usability issues that will require further refinement, such as users concerns with privacy, reliability and speed of package delivery. Chris (2006) came up with a design for a courier system meant for a desktop application. But this is not sufficient, implementation is also needed. Chauhan et al., (2010) in their paper came from the angle that web based application is the magic of today’s world and projected “e-Courier Services” for business to business interaction as a basic solution towards high-tech courier services in India. They presented an e-courier service that users can use and perform their courier transactions. Here the app was deployed as a web application targeted to Indian users. Their concept in the paper was deployed on the web and but was not targeted to mobile phone users. In Azeta et al (2010), it was noted that the existing express delivery system lack mobile facilities for customers to lodge complains and track which makes it difficult that while the shipment is on the move, the customers are kept in the dark about their consignment and also the courier agents are not able to access courier information while on the field. For this, the author therefore proposed the Mobile Express Delivery System (EDS) which will provide the courier customers with a means of tracing/tracking shipment, lodging of complaints and making financial transactions on shipment. This should also assist the courier staff to effectively manage courier related data with a mobile phone in order to enhance time, efficiency and documentation management for the customer and courier staff. The author took a critical look at the courier section in Nigeria and concluded that it was still far from using mobile device to support their operations, considering the enormous benefits of mobile applications in the global economy. Hence, there is need to scale it down to mobile since the number of mobile phone users now supersedes the number of PC users Murtagh,( 2014). The work of Karlson (2008) presented a system that enables two or more parties to share file from their mobile device. The limitation of this system is that it was just developed for sending and receiving of e-documents. Also, the system shares its documents over Bluetooth connection which has range limit. In Azeta et al., (2010), wap enabled phones was proposed to be part of designed considerations for a mobile express delivery system. The system enables user to perform various courier operations like tracking, check account statement and lodging complaint. In this contemporary period, mobile phones have become smarter with the advent of the Android operating system which now makes up 84% of the world’s smart phone market. The work in Azeta et al. (2010) was designed for mobile using java language; but the system proposed, due to technological revolutions, now has less use and will be seen as archaic. According to Fabiano (2010), the major selling point for logistics companies is access to the delivery status of a consignment which should be provided by courier and cargo companies for their clients through a toll free hotline, SMS and company website. In order to enhance this services, the author says that PT Repex Wahana (RPX), a local logistics company in partner with FedEx, is to offer a number of high tech service features which includes the RPX Global Positioning System (GPS) that is placed in every company vehicle so that its whereabouts can be traced and the RPX Tracker, which is an enhanced PDA complete with Wi-Fi and GPS that is carried by each courier to input data when the consignment is received by the customer or to update the status of the consignment. Emeje(2013) opined that effort are being made to educate the courier operators on how they can use ICTs for tracking and other trading activities. He throws light on “national economic potential of indigenous courier operators leveraging electronic commerce platform as canvassed by the Courier Regulatory Department to prosper the industry”. The Nigeria ICT Compumetrics report (2003) observed that multinational courier companies in developing countries such as Nigeria make use of sophisticated ICT products and equipment courtesy of their foreign partners. According to Schmidt (2015), the couriers and local delivery services in the US primarily provide express delivery and pickup of parcels. He highlighted that E-commerce trade is one of the major drivers of the global courier service industry. Electronic aspect of courier is recommended with the increasing demand of e-commerce all over the world. According to the author, there are 3 types of courier services in US, viz-a-viz; Carriers, Freight and Haulage.
The Carriers (they are large delivery companies that have a wide delivery network and a large fleet. Their fleet includes airplanes, trucks, vans, and ships). Carriers offer an entire supply chain solution for a large variety of goods. The Freight forwarders are subcontractors to airlines or carriers. Most freight forwarders offer specialized services like pallets, parcels, or bulky goods transport. The Haulage services transport bulky and heavy goods. Haulage services are not trackable like the services of carriers or freight forwarders. Most hauliers make use of rail networks to transport goods. In another work published in Yosep, (2014), a food ordering application was design for the Android platform. In Yosep, (2014) both the client-side (mobile phone) and the server side of the software were designed. It also included system that will be able to track an order. Courier business is presently a critical service sector of global economy, reaching to nearly every hamlet across the world in Isaac (2010). It is also one of the fastest growing sectors. Inability of state run postal systems to cope with 20th Century jet-age demands of speed, security & expanded delivery led to emergence of modern private courier firms, operating side by side with state run postal system that has become an endangered species. Despite influx of new entrants in the last 15 years, the sector is still far from saturation point.



CHAPTER 3 OVERALL DESCRIPTION OF THE PROPOSED SYSTEM
Existing Solution:
Courier service is not complete until the dispatched parcel gets to the final recipient and the delivery report to sender. This service is best if it can be efficient in the three stages of the service, viz-a-viz: pre-courier, courier and post-courier activities. The pre-courier activities encompass all the preparatory actions taken before the dispatch of the parcel. This includes identifying the courier agents/company, costing the service, specifying the delivery variables and registering the parcel for dispersal. The uncertainty of the costs of sending the package has become a big problem in the system. There is need for clients to know how much it will cost them to send a package from the comfort of their home or offices before making any move so as to eliminate some untold disappointments. The system will have the cost estimation capability using the parameters of date, time frame, weight, distance and delivery preference supplied by the clients thereby informing a potential user the cost of sending a particular package and the expected delivery date and time ahead of the initiation of the service proper. There are associated stress and time wastage from the customers’ point of view in going to the courier office as well as waiting on the service queue just to send packages. Therefore, it will be significant for the system to make room for users to send a request for service after the necessary pre-courier services and then a courier agent can come to clients location to pick up the package for delivery. Ineffective tracking system in the existing courier service is another problem to the customer’s satisfaction of the service. With a mobile network platform, an easier, better and faster way of tracking users parcels coupled with a notification service which can be in form of an app custom notification or telecommunication SMS can be provided. Some courier agents may find it difficult to locate recipient of the package being sent.
Proposed System & Advantages:
The user’s participation in the courier service using the mobile application makes the meeting ground very efficient. The courier agent can easily seek for direction and redirection from either/both the sender or/and the recipient using the mobile app. This is the turning point in the user’s participation in courier service. At android projects ideas in time, the courier agents can also use the app to easily locate a customer’s address with the aid of Google map API. This API assists courier agents navigating to their picking or delivery points. At the final dispatch, both the recipient and sender can acknowledge the service completion using the mobile platform. This is regarded as the user’s participation in post-courier service. In addition, It introduces a faster way to lay complain about a delay in delivery or missing package. In this regards, fast means of communication between the customer and the agency is enhanced via virtualization of space using sms billing for both sender and receiver.
Advantages:
1. Fast access.
2. Bill issued by sms procedure becomes fast.
3. Consignment note is easily generated by using preprinted stationary.
4. Manifest is prepared fastly.
5. Better storage capacity.
6. Easy and fast retrieval of information.


System Modules:
1. Admin Login
2. Create Bill
• From,to, courier type, delivery date, courier company
3. Update bill
4. Send sms
5. Manage Customer details
6. Reporting
7. Logout

3.1 Module Description
1. Admin Login
o Admin will have his/her own login details (username, password) to access the system
2. Create Bill
o Admin can create a Courier Bill after logging in. Bills contain the details of sender, receiver, courier type, delivery date and courier company.
3. Update bill
o They can also update the Bill with the entries and if there is any modification
4. Send SMS
o Once they created and updated the Courier Bill admin can send the Bill as SMS

5. Manage Customer details
o Admin can manage all the Customer Details in a separate and secured Database
6. Reporting
o Reports of all the Bill can be viewed by the admin of the system
7. Logout
o At last they can logout if they have done with their actions on the database.
3.2 System Features
In the life of the software development, problem analysis provides a base for design and development phase. The problem is analyzed so that sufficient matter is provided to design a new system. Large problems are sub-divided into smaller once to make them understandable and easy for finding solutions. Same in this project all the task are sub-divided and categorized.
SMS Templates:
From = 'Dear '.$name.' you booked the shipment to '.$get_to_name.' the details are consigment number '.$get_cons.' From '.$get_from.' To '.$get_to.' Weight '.$get_weight.' gm Type '.$get_type.' Delivery in '.$get_del.' days. Tracking link '.$get_link.' Thank you Choosing us';


To = 'Dear '.$get_to_name.' you got the shipment from '.$name.' the details are From- '.$get_from.' To- '.$get_to.' Weight- '. android project ideas for beginners get_weight.'gm Type - '.$get_type.' Delivery in '.$get_del.' days. Tracking link '.$get_link.' Thanking you Choosing us';


Delivery sms = 'Dear '.$name.' your consigment number '.$get_cons.' is delivered successfull Thank you Choosing us';

CHAPTER 4 – DESIGN
Design is the first step in the development phase for any techniques and principles for the purpose of defining a device, a process or system in sufficient detail to permit its physical realization.
Once the software requirements have been analyzed and specified the software design involves three technical activities - design, coding, implementation and testing that are required to build and verify the software.
The design activities are of main importance in this phase, because in this activity, decisions ultimately affecting the success of the software implementation and its ease of maintenance are made. These decisions have the final bearing upon reliability and maintainability of the system. Design is the only way to accurately translate the customer’s requirements into finished software or a system.
Design is the place where quality is fostered in development. Software design is a process through which requirements are translated into a representation of software. Software design is conducted in two steps. Preliminary design is concerned with the transformation of requirements into data.

4.1UML Diagrams:
UML stands for Unified Modeling Language. UML is a language for specifying, visualizing and documenting the system. This is the step while developing any product after analysis. The goal from this is to produce a model of the entities involved in the project which later need to be built. The representation of the entities that are to be used in the product being developed need to be designed.

There are various kinds of methods in software design:
• Use case Diagram
• Sequence Diagram
• Collaboration Diagram
4.1.1Usecase Diagrams:
Use case diagrams model behavior within a system and helps the developers understand of what the user require. The stick man represents what’s called an actor. Use case diagram can be useful for getting an overall view of the system and clarifying who can do and more importantly what they can’t do.




Use case diagram consists of use cases and actors and shows the interaction between the use case and actors.
• The purpose is to show the interactions between the use case and actor.
• To represent the system requirements from user’s perspective.
• An actor could be the end-user of the system or an external system

4.1.2 Sequence Diagram:
Sequence diagram and collaboration diagram are called INTERACTION DIAGRAMS. An interaction diagram shows an interaction, consisting of set of objects and their relationship including the messages that may be dispatched among them.
A sequence diagram is an introduction that empathizes the time ordering of messages. Graphically a sequence diagram is a table that shows objects arranged along the X-axis and messages ordered in increasing time along the Y-axis.


4.1.3 Collaborate Diagram:
A collaboration diagram, also called a communication diagram or interaction diagram, is an illustration of the relationships and interactions among software objects in the Unified Modeling Language (UML).


DFD Diagram
Data Flow Diagram










Table Design
Courier Login
User ID Name Email Id Password Mobile Address City Question 1 Question 2


Courier Details
User ID From To Place To Cosigment Weight Type Days Tracking





CHAPTER 5 - OUTPUT SCREENSHOTS
















CHAPTER 6 – IMPLEMENTATION DETAILS
6.1 Introduction to Html Framework
Hyper Text Markup Language, commonly referred to as HTML, is the standard markup language used to create web pages. Along with CSS, and JavaScript, HTML is a cornerstone technology used to create web pages, as well as to create user interfaces for mobile and web applications. Web browsers can read HTML files and render them into visible or audible web pages. HTML describes the structure of a website semantically along with cues for presentation, making it a markup language, rather than a programming language.
HTML elements form the building blocks of HTML pages. HTML allows images and other objects to be embedded and it can be used to create interactive forms. It provides a means to create structured documents by denoting structuralsemantics for text such as headings, paragraphs, lists, links, quotes and other items. HTML elements are delineated by tags, written using angle brackets. Tags such as
and
<input /> introduce content into the page directly. Others such as

...

surround and provide information about document text and may include other tags as sub-elements. Browsers do not display the HTML tags, but use them to interpret the content of the page.
HTML can embed scripts written in languages such as JavaScript which affect the behavior of HTML web pages. HTML markup can also refer the browser to Cascading Style Sheets (CSS) to define the look and layout of text and other material.
HyperText Markup Language (HTML) is the standard markup language for creating web pages and web applications. With Cascading Style Sheets (CSS) and JavaScript it forms a triad of cornerstone technologies for the World Wide Web.[1] Web browsers receive HTML documents from a webserver or from local storage and render them into multimedia web pages. HTML describes the structure of a web page semantically and originally included cues for the appearance of the document.
HTML elements are the building blocks of HTML pages. With HTML constructs, images and other objects, such as interactive forms, may be embedded into the rendered page. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. HTML elements are delineated by tags, written using angle brackets. Tags such as
and
<input /> introduce content into the page directly. Others such as

...

surround and provide information about document text and may include other tags as sub-elements. Browsers do not display the HTML tags, but use them to interpret the content of the page.
HTML can embed programs written in a scripting language such as JavaScript which affect the behavior and content of web pages. Inclusion of CSS defines the look and layout of content. The World Wide Web Consortium (W3C), maintainer of both the HTML and the CSS standards, has encouraged the use of CSS over explicit presentational HTML since 1997.[2]
In 1980, physicist Tim Berners-Lee, a contractor at CERN, proposed and prototyped ENQUIRE, a system for CERN researchers to use and share documents. In 1989, Berners-Lee wrote a memo proposing an Internet-based hypertext system.[3] Berners-Lee specified HTML and wrote the browser and server software in late 1990. That year, Berners-Lee and CERN data systems engineer Robert Cailliau collaborated on a joint request for funding, but the project was not formally adopted by CERN. In his personal notes[4] from 1990 he listed[5] "some of the many areas in which hypertext is used" and put an encyclopedia first.
The first publicly available description of HTML was a document called "HTML Tags", first mentioned on the Internet by Tim Berners-Lee in late 1991.[6][7] It describes 18 elements comprising the initial, relatively simple design of HTML. Except for the hyperlink tag, these were strongly influenced by SGMLguid, an in-house Standard Generalized Markup Language (SGML)-based documentation format at CERN. Eleven of these elements still exist in HTML 4.[8]
HTML is a markup language that web browsers use to interpret and compose text, images, and other material into visual or audible web pages. Default characteristics for every item of HTML markup are defined in the browser, and these characteristics can be altered or enhanced by the web page designer's additional use of CSS. Many of the text elements are found in the 1988 ISO technical report TR 9537 Techniques for using SGML, which in turn covers the features of early text formatting languages such as that used by the RUNOFF command developed in the early 1960s for the CTSS (Compatible Time-Sharing System) operating system: these formatting commands were derived from the commands used by typesetters to manually format documents. However, the SGML concept of generalized markup is based on elements (nested annotated ranges with attributes) rather than merely print effects, with also the separation of structure and markup; HTML has been progressively moved in this direction with CSS.
Berners-Lee considered HTML to be an application of SGML. It was formally defined as such by the Internet Engineering Task Force (IETF) with the mid-1993 publication of the first proposal for an HTML specification, the "Hypertext Markup Language (HTML)" Internet Draft by Berners-Lee and Dan Connolly, which included an SGML Document Type Definition to define the grammar.[9][10] The draft expired after six months, but was notable for its acknowledgment of the NCSA Mosaic browser's custom tag for embedding in-line images, reflecting the IETF's philosophy of basing standards on successful prototypes.[11] Similarly, Dave Raggett's competing Internet-Draft, "HTML+ (Hypertext Markup Format)", from late 1993, suggested standardizing already-implemented features like tables and fill-out forms.[12]
After the HTML and HTML+ drafts expired in early 1994, the IETF created an HTML Working Group, which in 1995 completed "HTML 2.0", the first HTML specification intended to be treated as a standard against which future implementations should be based.[13]
Further development under the auspices of the IETF was stalled by competing interests. Since 1996, the HTML specifications have been maintained, with input from commercial software vendors, by the World Wide Web Consortium (W3C).[14] However, in 2000, HTML also became an international standard (ISO/IEC 15445:2000). HTML 4.01 was published in late 1999, with further errata published through 2001. In 2004, development began on HTML5 in the Web Hypertext Application Technology Working Group (WHATWG), which became a joint deliverable with the W3C in 2008, and completed and standardized on 28 October 2014.[15]
6.2 Cascading Style Sheets (CSS)
CSS is a style sheet language used for describing the presentation of a document written in a markup language. Although most often used to set the visual style of web pages and user interfaces written in HTML and XHTML, the language can be applied to any XML document, including plain XML, SVG andXUL, and is applicable to rendering in speech, or on other media. Along with HTML and JavaScript, CSS is a cornerstone technology used by most websites to create visually engaging webpages, user interfaces for web applications, and user interfaces for many mobile applications.
CSS is designed primarily to enable the separation of document content from document presentation, including aspects such as the layout, colors, and fonts. This separation can improve content accessibility, provide more flexibility and control in the specification of presentation characteristics, enable multiple HTML pages to share formatting by specifying the relevant CSS in a separate .css file, and reduce complexity and repetition in the structural content, such as semantically insignificant tables that were widely used to format pages before consistent CSS rendering was available in all major browsers. CSS makes it possible to separate presentation instructions from the HTML content in a separate file or style section of the HTML file. For each matching HTML element, it provides a list of formatting instructions. For example, a CSS rule might specify that "all heading 1 elements should be bold", leaving pure semantic HTML markup that asserts "this text is a level 1 heading" without formatting code such as a
<bold>

tag indicating how such text should be displayed.



This separation of formatting and content makes it possible to present the same markup page in different styles for different rendering methods, such as on-screen, in print, by voice (when read out by a speech-based browser orscreen reader) and on Braille-based, tactile devices. It can also be used to display the web page differently depending on the screen size or device on which it is being viewed. Although the author of a web page typically links to a CSS file within the markup file, readers can specify a different style sheet, such as a CSS file stored on their own computer, to override the one the author has specified. If the author or the reader did not link the document to a style sheet, the default style of the browser will be applied. Another advantage of CSS is that aesthetic changes to the graphic design of a document (or hundreds of documents) can be applied quickly and easily, by editing a few lines in one file, rather than by a laborious (and thus expensive) process of crawling over every document line by line, changing markup.



The CSS specification describes a priority scheme to determine which style rules apply if more than one rule matches against a particular element. In this so-called cascade, priorities (or weights) are calculated and assigned to rules, so that the results are predictable.



Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of a document written in a markup language.[1] Although most often used to set the visual style of web pages and user interfaces written in HTML and XHTML, the language can be applied to any XML document, including plain XML, SVG and XUL, and is applicable to rendering in speech, or on other media. Along with HTML and JavaScript, CSS is a cornerstone technology used by most websites to create visually engaging webpages, user interfaces for web applications, and user interfaces for many mobile applications.[2]



CSS is designed primarily to enable the separation of document content from document presentation, including aspects such as the layout, colors, and fonts.[3] This separation can improve content accessibility, provide more flexibility and control in the specification of presentation characteristics, enable multiple HTML pages to share formatting by specifying the relevant CSS in a separate .css file, and reduce complexity and repetition in the structural content.



Separation of formatting and content makes it possible to present the same markup page in different styles for different rendering methods, such as on-screen, in print, by voice (via speech-based browser or screen reader), and on Braille-based tactile devices. It can also display the web page differently depending on the screen size or viewing device. Readers can also specify a different style sheet, such as a CSS file stored on their own computer, to override the one the author specified.



Changes to the graphic design of a document (or hundreds of documents) can be applied quickly and easily, by editing a few lines in the CSS file they use, rather than by changing markup in the documents.



The CSS specification describes a priority scheme to determine which style rules apply if more than one rule matches against a particular element. In this so-called cascade, priorities (or weights) are calculated and assigned to rules, so that the results are predictable.



The CSS specifications are maintained by the World Wide Web Consortium (W3C). Internet media type (MIME type) text/css is registered for use with CSS by RFC 2318 (March 1998). The W3C operates a free CSS validation service for CSS documents.



In CSS, selectors declare which part of the markup a style applies to by matching tags and attributes in the markup itself.



Selectors may apply to:



all elements of a specific type, e.g. the second-level headers h2



elements specified by attribute, in particular:



id: an identifier unique within the document



class: an identifier that can annotate multiple elements in a document



elements depending on how they are placed relative to others in the document tree.



Classes and IDs are case-sensitive, start with letters, and can include alphanumeric characters and underscores. A class may apply to any number of instances of any elements. An ID may only be applied to a single element.



Pseudo-classes are used in CSS selectors to permit formatting based on information that is not contained in the document tree. One example of a widely used pseudo-class is :hover, which identifies content only when the user "points to" the visible element, usually by holding the mouse cursor over it. It is appended to a selector as in a:hover or #elementid:hover. A pseudo-class classifies document elements, such as :link or :visited, whereas a pseudo-element makes a selection that may consist of partial elements, such as ::first-line or ::first-letter.[5]



Selectors may be combined in many ways to achieve great specificity and flexibility.[6] Multiple selectors may be joined in a spaced list to specify elements by location, element type, id, class, or any combination thereof. The order of the selectors is important. For example, div .myClass color: red; applies to all elements of class myClass that are inside div elements, whereas .myClass div color: red; applies to all div elements that are in elements of class myClass.



CSS information can be provided from various sources. These sources can be the web browser, the user and the author. The information from the author can be further classified into inline, media type, importance, selector specificity, rule order, inheritance and property definition. CSS style information can be in a separate document or it can be embedded into an HTML document. Multiple style sheets can be imported. Different styles can be applied depending on the output device being used; for example, the screen version can be quite different from the printed version, so that authors can tailor the presentation appropriately for each medium.



The style sheet with the highest priority controls the content display. Declarations not set in the highest priority source are passed on to a source of lower priority, such as the user agent style. This process is called cascading.



One of the goals of CSS is to allow users greater control over presentation. Someone who finds red italic headings difficult to read may apply a different style sheet. Depending on the browser and the web site, a user may choose from various style sheets provided by the designers, or may remove all added styles and view the site using the browser's default styling, or may override just the red italic heading style without altering other attributes.



CSS was first proposed by Håkon Wium Lie on October 10, 1994.[16] At the time, Lie was working with Tim Berners-Lee at CERN.[17] Several other style sheet languages for the web were proposed around the same time, and discussions on public mailing lists and inside World Wide Web Consortium resulted in the first W3C CSS Recommendation (CSS1)[18] being released in 1996. In particular, Bert Bos' proposal was influential; he became co-author of CSS1 and is regarded as co-creator of CSS.[19]



Style sheets have existed in one form or another since the beginnings of Standard Generalized Markup Language (SGML) in the 1980s, and CSS was developed to provide style sheets for the web.[20] One requirement for a web style sheet language was for style sheets to come from different sources on the web. Therefore, existing style sheet languages like DSSSL and FOSI were not suitable. CSS, on the other hand, let a document's style be influenced by multiple style sheets by way of "cascading" styles.[20]



As HTML grew, it came to encompass a wider variety of stylistic capabilities to meet the demands of web developers. This evolution gave the designer more control over site appearance, at the cost of more complex HTML. Variations in web browser implementations, such as ViolaWWW and WorldWideWeb,[21] made consistent site appearance difficult, and users had less control over how web content was displayed. The browser/editor developed by Tim Berners-Lee had style sheets that were hard-coded into the program. The style sheets could therefore not be linked to documents on the web.[22] Robert Cailliau, also of CERN, wanted to separate the structure from the presentation so that different style sheets could describe different presentation for printing, screen-based presentations, and editors.[21]



Improving web presentation capabilities was a topic of interest to many in the web community and nine different style sheet languages were proposed on the www-style mailing list.[20] Of these nine proposals, two were especially influential on what became CSS: Cascading HTML Style Sheets[16] and Stream-based Style Sheet Proposal (SSP).[19][23] Two browsers served as testbeds for the initial proposals; Lie worked with Yves Lafon to implement CSS in Dave Raggett's Arena browser.[24][25][26] Bert Bos implemented his own SSP proposal in the Argo browser.[19] Thereafter, Lie and Bos worked together to develop the CSS standard (the 'H' was removed from the name because these style sheets could also be applied to other markup languages besides HTML).[17]



Lie's proposal was presented at the "Mosaic and the Web" conference (later called WWW2) in Chicago, Illinois in 1994, and again with Bert Bos in 1995.[17] Around this time the W3C was already being established, and took an interest in the development of CSS. It organized a workshop toward that end chaired by Steven Pemberton. This resulted in W3C adding work on CSS to the deliverables of the HTML editorial review board (ERB). Lie and Bos were the primary technical staff on this aspect of the project, with additional members, including Thomas Reardon of Microsoft, participating as well. In August 1996 Netscape Communication Corporation presented an alternative style sheet language called JavaScript Style Sheets (JSSS).[17] The spec was never finished and is deprecated.[27] By the end of 1996, CSS was ready to become official, and the CSS level 1 Recommendation was published in December.



Development of HTML, CSS, and the DOM had all been taking place in one group, the HTML Editorial Review Board (ERB). Early in 1997, the ERB was split into three working groups: HTML Working group, chaired by Dan Connolly of W3C; DOM Working group, chaired by Lauren Wood of SoftQuad; and CSS Working group, chaired by Chris Lilley of W3C.



The CSS Working Group began tackling issues that had not been addressed with CSS level 1, resulting in the creation of CSS level 2 on November 4, 1997. It was published as a W3C Recommendation on May 12, 1998. CSS level 3, which was started in 1998, is still under development as of 2014.



In 2005 the CSS Working Groups decided to enforce the requirements for standards more strictly. This meant that already published standards like CSS 2.1, CSS 3 Selectors and CSS 3 Text were pulled back from Candidate Recommendation to Working Draft level.















6.3 MYSQL Server



MySQL is an open-source relational database management system (RDBMS);[6] in July 2013, it was the world's second most widely used RDBMS, and the most widely used open-source client–server model RDBMS. It is named after co-founder Michael Widenius's daughter, My. The SQL acronym stands for Structured Query Language. The MySQL development project has made its source code available under the terms of the GNU General Public License, as well as under a variety of proprietary agreements. MySQL was owned and sponsored by a single for-profit firm, the Swedishcompany MySQL AB, now owned by Oracle Corporation. For proprietary use, several paid editions are available, and offer additional functionality.



SQL Server Management Studio (SSMS) is a software application first launched with Microsoft SQL Server 2005 that is used for configuring, managing, and administering all components within Microsoft SQL Server. The tool includes both script editors and graphical tools which work with objects and features of the server.[1]



A central feature of SSMS is the Object Explorer, which allows the user to browse, select, and act upon any of the objects within the server.[2] It also shipped a separate Express edition that could be freely downloaded, however recent versions of SSMS are fully capable of connecting to and manage any SQL Server Express instance. Microsoft also incorporated backwards compatibility for older versions of SQL Server thus allowing a newer version of SSMS to connect to older versions of SQL Server instances.



Starting from version 11, the application was based on the Visual Studio 2010 shell, using WPF for the user interface.



In June 2015, Microsoft announced their intention to release future versions of SSMS independently of SQL Server database engine releases.[3].







6.4PHP



PHP is a server-side scripting language designed for web development but also used as a general-purpose programming language. Originally created by RasmusLerdorf in 1994, the PHP reference implementation is now produced by The PHP Group. PHP originally stood for Personal Home Page, but it now stands for therecursive backronym PHP: Hypertext Preprocessor.



PHP code may be embedded into HTML code, or it can be used in combination with various web template systems, web content management system and web frameworks. PHP code is usually processed by a PHPinterpreter implemented as a module in the web server or as a Common Gateway Interface (CGI) executable. The web server combines the results of the interpreted and executed PHP code, which may be any type of data, including images, with the generated web page. PHP code may also be executed with a command-line interface(CLI) and can be used to implement standalone graphical applications.



The standard PHP interpreter, powered by the Zend Engine, is free software released under the PHP License. PHP has been widely ported and can be deployed on most web servers on almost every operating system andplatform, free of charge.



The PHP language evolved without a written formal specification or standard until 2014, leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to create a formal PHP specification.



PHP is a server-side scripting language designed primarily for web development but also used as a general-purpose programming language. Originally created by Rasmus Lerdorf in 1994,[4] the PHP reference implementation is now produced by The PHP Development Team.[5] PHP originally stood for Personal Home Page,[4] but it now stands for the recursive acronym PHP: Hypertext Preprocessor.[6]



PHP code may be embedded into HTML or HTML5 code, or it can be used in combination with various web template systems, web content management systems and web frameworks. PHP code is usually processed by a PHP interpreter implemented as a module in the web server or as a Common Gateway Interface (CGI) executable. The web server combines the results of the interpreted and executed PHP code, which may be any type of data, including images, with the generated web page. PHP code may also be executed with a command-line interface (CLI) and can be used to implement standalone graphical applications.[7]



The standard PHP interpreter, powered by the Zend Engine, is free software released under the PHP License. PHP has been widely ported and can be deployed on most web servers on almost every operating system and platform, free of charge.[8]



The PHP language evolved without a written formal specification or standard until 2014, leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to create a formal PHP specification.[9]



PHP development began in 1995 when Rasmus Lerdorf wrote several Common Gateway Interface (CGI) programs in C,[10][11][12] which he used to maintain his personal homepage. He extended them to work with web forms and to communicate with databases, and called this implementation "Personal Home Page/Forms Interpreter" or PHP/FI.



PHP/FI could help to build simple, dynamic web applications. To accelerate bug reporting and to improve the code, Lerdorf initially announced the release of PHP/FI as "Personal Home Page Tools (PHP Tools) version 1.0" on the Usenet discussion group comp.infosystems.www.authoring.cgi on June 8, 1995.[13][14] This release already had the basic functionality that PHP has as of 2013. This included Perl-like variables, form handling, and the ability to embed HTML. The syntax resembled that of Perl but was simpler, more limited and less consistent.[5]



Lerdorf did not intend the early PHP to become a new programming language, but it grew organically, with Lerdorf noting in retrospect: "I don’t know how to stop it, there was never any intent to write a programming language […] I have absolutely no idea how to write a programming language, I just kept adding the next logical step on the way."[15] A development team began to form and, after months of work and beta testing, officially released PHP/FI 2 in November 1997.



The fact that PHP lacked an original overall design but instead developed organically has led to inconsistent naming of functions and inconsistent ordering of their parameters.[16] In some cases, the function names were chosen to match the lower-level libraries which PHP was "wrapping",[17] while in some very early versions of PHP the length of the function names was used internally as a hash function, so names were chosen to improve the distribution of hash values.[18]







6.5 ANGULAR JAVA SCRIPT



AngularJS (commonly referred to as "Angular" or "Angular.js") is an open-source web application framework mainly maintained by Google and by a community of individuals and corporations to address many of the challenges encountered in developing single-page applications. It aims to simplify both the development and the testing of such applications by providing a framework for client-side model–view–controller (MVC) and model–view–viewmodel(MVVM) architectures, along with components commonly used in rich Internet applications.



The AngularJS framework works by first reading the HTML page, which has embedded into it additional custom tag attributes. Angular interprets those attributes as directives to bind input or output parts of the page to a model that is represented by standard JavaScript variables. mca mini project titles with abstract of those JavaScript variables can be manually set within the code, or retrieved from static or dynamic JSON resources.



According to JavaScript analytics service Libscore, AngularJS is used on the websites of Wolfram Alpha, NBC,Walgreens, Intel, Sprint, ABC News, and approximately 8,400 other sites out of 1 million tested in July 2015.



AngularJS is the frontend part of the MEAN stack, consisting of MongoDB database, Express.js web application server framework, Angular.js itself, and Node.js runtime environment.



AngularJS is an open source web application framework. It was originally developed in 2009 by Misko Hevery and Adam Abrons. It is now maintained by Google. Its latest version is 1.4.3.



Definition of AngularJS as put by its official documentation is as follows −



AngularJS is a structural framework for dynamic web apps. It lets you use HTML as your template language and lets you extend HTML's syntax to express your application's components clearly and succinctly. Angular's data binding and dependency injection eliminate much of the code you currently have to write. And it all happens within the browser, making it an ideal partner with any server technology.



Features



 AngularJS is a powerful JavaScript based development framework to create RICH Internet Application(RIA).



 AngularJS provides developers options to write client side application (using JavaScript) in a clean MVC(Model View Controller) way.



 Application written in AngularJS is cross-browser compliant. AngularJS automatically handles JavaScript code suitable for each browser.



 AngularJS is open source, completely free, and used by thousands of developers around the world. It is licensed under the Apache License version 2.0.



 Overall, AngularJS is a framework to build large scale and high performance web application while keeping them as easy-to-maintain.



Core Features



Following are most important core features of AngularJS −



 Data-binding − It is the automatic synchronization of data between model and view components.



 Scope − These are objects that refer to the model. They act as a glue between controller and view.



 Controller − These are JavaScript functions that are bound to a particular scope.



 Services − AngularJS come with several built-in services for example $https: to make a XMLHttpRequests. These are singleton objects which are instantiated only once in app.



 Filters − These select a subset of items from an array and returns a new array.



 Directives − Directives are markers on DOM elements (such as elements, attributes, css, and more). These can be used to create custom HTML tags that serve as new, custom widgets. AngularJS has built-in directives (ngBind, ngModel...)



 Templates − These are the rendered view with information from the controller and model. These can be a single file (like index.html) or multiple views in one page using "partials".



 Routing − It is concept of switching views.



 Model View Whatever − MVC is a design pattern for dividing an application into different parts (called Model, View and Controller), each with distinct responsibilities. AngularJS does not implement MVC in the traditional sense, but rather something closer to MVVM (Model-View-ViewModel). The Angular JS team refers it humorously as Model View Whatever.



 Deep Linking − Deep linking allows you to encode the state of application in the URL so that it can be bookmarked. The application can then be restored from the URL to the same state.



 Dependency Injection − AngularJS has a built-in dependency injection subsystem that helps the developer by making the application easier to develop, understand, and test.







CHAPTER 7- SYSTEM STUDY







7.1 FEASIBILITY STUDY



The feasibility of the project is analyzed in this phase and business proposal is put forth with a very general plan for the project and some cost estimates. During system analysis the feasibility study of the proposed system is to be carried out. This is to ensure that the proposed system is not a burden to the company. For feasibility analysis, some understanding of the major requirements for the system is essential.



Three key considerations involved in the feasibility analysis are



• ECONOMICAL FEASIBILITY



• TECHNICAL FEASIBILITY



• SOCIAL FEASIBILITY







ECONOMICAL FEASIBILITY







This study is carried out to check the economic impact that the system will have on the organization. The amount of fund that the company can pour into the research and development of the system is limited. The expenditures must be justified. Thus the developed system as well within the budget and this was achieved because most of the technologies used are freely available. Only the customized products had to be purchased.



CHAPTER 8-TECHNICAL FEASIBILITY







This study is carried out to check the technical feasibility, that is, the technical requirements of the system. Any system developed must not have a high demand on the available technical resources. This will lead to high demands on the available technical resources. year-projects.html mca final year projects titles will lead to high demands being placed on the client. The developed system must have a modest requirement, as only minimal or null changes are required for implementing this system.



SOCIAL FEASIBILITY



The aspect of study is to check the level of acceptance of the system by the user. This includes the process of training the user to use the system efficiently. The user must not feel threatened by the system, instead must accept it as a necessity. The level of acceptance by the users solely depends on the methods that are employed to educate the user about the system and to make him familiar with it. His level of confidence must be raised so that he is also able to make some constructive criticism, which is welcomed, as he is the final user of the system.







8.1Non Functional Requirements



Non-functional requirements are the quality requirements that stipulate how well software does what it has to do. These are Quality attributes of any system; these can be seen at the execution of the system and they can also be the part of the system architecture.











8.2 Accuracy:



The system will be accurate and reliable based on the design architecture. If there is any problem in the accuracy then the system will provide alternative ways to solve the problem.







8.3 Usability:



The proposed system will be simple and easy to use by the users. The users will comfort in order to communicate with the system. The user will be provided with an easy interface of the system.







8.4 Accessibility:



The system will be accessible through internet and there should be no any known problem.







8.5 Performance:



The system performance will be at its best when performing the functionality of the system.







8.6 Reliability:



The proposed system will be reliable in all circumstances and if there is any problem that will be affectively handle in the design.







8.7 Security:



The proposed system will be highly secured; every user will be required registration and username/password to use the system. The system will do the proper authorization and authentication of the users based on their types and their requirements. The proposed system will be designed persistently to avoid any misuse of the application.











































































CHAPTER 9-SYSTEM TESTING







The purpose of testing is to discover errors. Testing is the process of trying to discover every conceivable fault or weakness in a work product. It provides a way to check the functionality of components, sub-assemblies, assemblies and/or a finished product It is the process of exercising software with the intent of ensuring that the



Software system meets its requirements and user expectations and does not fail in an unacceptable manner. There are various types of test. Each test type addresses a specific testing requirement.







TYPES OF TESTS







Unit testing



Unit testing involves the design of test cases that validate that the internal program logic is functioning properly, and that program inputs produce valid outputs. All decision branches and internal code flow should be validated. It is the testing of individual software units of the application .it is done after the completion of an individual unit before integration. This is a structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform basic tests at component level and test a specific business process, application, and/or system configuration. Unit tests ensure that each unique path of a business process performs accurately to the documented specifications and contains clearly defined inputs and expected results.



Integration testing



Integration tests are designed to test integrated software components to determine if they actually run as one program. Testing is event driven and is more concerned with the basic outcome of screens or fields. Integration tests demonstrate that although the components were individually satisfaction, as shown by successfully unit testing, the combination of components is correct and consistent. Integration testing is specifically aimed at exposing the problems that arise from the combination of components.







Functional test



Functional tests provide systematic demonstrations that functions tested are available as specified by the business and technical requirements, system documentation, and user manuals.



Functional testing is centered on the following items:



Valid Input : identified classes of valid input must be accepted.



Invalid Input : identified classes of invalid input must be rejected.



Functions : identified functions must be exercised.



Output : identified classes of application outputs must be exercised.



Systems/Procedures: interfacing systems or procedures must be invoked.







Organization and preparation of functional tests is focused on requirements, key functions, or special test cases. In addition, systematic coverage pertaining to identify Business process flows; data fields, predefined processes, and successive processes must be considered for testing. Before functional testing is complete, additional tests are identified and the effective value of current tests is determined.







android project with source code ensures that the entire integrated software system meets requirements. It tests a configuration to ensure known and predictable results. An example of system testing is the configuration oriented system integration test. System testing is based on process descriptions and flows, emphasizing pre-driven process links and integration points.







White Box Testing



White Box Testing is a testing in which in which the software tester has knowledge of the inner workings, structure and language of the software, or at least its purpose. It is purpose. It is used to test areas that cannot be reached from a black box level.







Black Box Testing



Black Box Testing is testing the software without any knowledge of the inner workings, structure or language of the module being tested. Black box tests, as most other kinds of tests, must be written from a definitive source document, such as specification or requirements document, such as specification or requirements document. It is a testing in which the software under test is treated, as a black box .you cannot “see” into it. The test provides inputs and responds to outputs without considering how the software works.







9.1 Unit Testing:







Unit testing is usually conducted as part of a combined code and unit test phase of the software lifecycle, although it is not uncommon for coding and unit testing to be conducted as two distinct phases.







Test strategy and approach



Field testing will be performed manually and functional tests will be written in detail.







Test objectives



• All field entries must work properly.



• Pages must be activated from the identified link.



• The entry screen, messages and responses must not be delayed.







Features to be tested



• Verify that the entries are of the correct format



• No duplicate entries should be allowed



• All links should take the user to the correct page







9.2 Integration Testing



Software integration testing is the incremental integration testing of two or more integrated software components on a single platform to produce failures caused by interface defects.



The task of the integration test is to check that components or software applications, e.g. components in a software system or – one step up – software applications at the company level – interact without error.



Test Results: All the test cases mentioned above passed successfully. No defects encountered.







9.3 Acceptance Testing



User Acceptance Testing is a critical phase of any project and requires significant participation by the end user. It also ensures that the system meets the functional requirements.







Test Results: All the test cases mentioned above passed successfully. No defects encountered.























CHAPTER 10– CONCLUSIONS



This paper presents a mobile courier service system for the courier service sector in Nigeria. A critical look at the courier section in Nigeria shows that they are still far from using mobile device to support their operations, considering the enormous benefits of mobile applications in the global economy. The system as developed provides an easier means to send documents and other package like laptops, books, etc. with less delay and stress. People do not have to visit the courier offices again for any reason. The Mobile courier service system provided in this paper, when fully deployed, will help to improve the services rendered by courier companies in Nigeria. So far, this system provides complete client side courier software which customers can use to send their package to various destinations By the resources available to us and considering the limitation, we were able to completely implement the client side of the mobile courier service system and we leave the rest as recommendation for further development.











CHAPTER 11- REFERENCES



¬¬¬[1] Azeta, A. A., Ogunlana A. O. and Ezeh C. O., (2010) Design and Implementation of a Mobile Express Delivery System, Proceedings of the International Conference on Software Engineering and Intelligent Systems, Ota, Nigeria SEIS 2010. Vol 1.



[2] Chauhan A., Singh S., Jain A. and Kumar R. (2010). High-Tech Courier Services as an E-Courier services in India Prospective. Report and Opinion 2010;2(5):86-93. ISSN:1553-9873.



[3] Chris. (2006). Courier System report.



[4] http://d1dlalugb0z2hd.cloudfront.net/highlight/pdfgenerator/courier.pdf



[5] Emeje, S (2013) Many courier companies are going down, interview with Punch newspaper August,19.



[6] Emeje, S (2014) Online Courier Business: Untapped Goldmine interview with Daily Newswatch September 15..



[7] Express Delivery Services (2005): Integrating ASEAN to Global Market. A report by US-ASEAN Business Council June 2005



[8] Fabiano R., (2010) Challenges and innovations in the courier and cargo industry, Supplement News, November 25 2010, 10:54 AM available on http://www.thejakartapost.com/news/2010/11/25/challenges-and-innovations-courier-and-cargo-industry.html#sthash.XcNh8y77.dpuf35



[9] Karlson A., Smith G. , Meyers B., Robertson G., and Czerwinski M., (2008), Courier: A Collaborative Phone-Based File Exchange System., Technical Report MSR-TR-2008-05, http://research.microsoft.com.



[10] Murtagh R. (2014) Mobile Now Exceeds PC: The Biggest Shift Since the Internet Began, available at: http://searchenginewatch.com/sew/opinion/2353616/mobile-now-exceeds-pc-the-biggest-shift-since-the-internet-began



[11] Nigerian ICT Handbook (2003), a report of ICT product and services usage in Nigeria, published by Compumetrics Solutions Ltd, Lagos. http://compumetricsolutions.com.



[12] Orunga, E(2012), Challenges facing the Courier industry and their solutions available on http://www.d-trail.co.ke



[13] Yosep, Ricky M. (2014). Mobile Food Ordering Application using Android OS Platform. Paper presented at International Conference on Advances Science and Contemporary Engineering, Jarkata, Indonesia, volume 68.



[14] Isaac O (2010) Optimizing Opportunities for Courier Business In Nigeria, md/ceo, Red Star Express



[15] Schmidt A. (2015), 'A Look at the Courier Service Industry in the United States' in What Investors Should Know about the Courier Services Industry (Part 1 of 11), available on http://www.marketrealist.com/2015/07/look-courier-service-industry-united-states/



[16] Small C. M. (1990) Messengers In The County Of Artois, 1295-1329 Canadian Journal of History, 25 (2), pp. 163•175, ISSN 0008-4107, Retrieved Aug 15, 2012.



[17] US-ASEAN Business Council,(2005) Express Delivery Services: Integrating ASEAN to Global Markets.



[18] Wikipeida the free encyclopedia (2007) available online at http://en.wikipedia.org/wiki/Courier [accessed: 6 July 2007]







</bold>