YORN Shuttle Service

By Hammad Alam Usmani Student ID No. BB-35071 Muhammad Shakeeb Alam Student ID No. BB-25215
Submitted to the Faculty of Computer Sciences and
Information Technology

Institute of Business & Technology, Karachi
In Partial fulfillment of requirement for the degree of Bachelors of Science in (Computer Science) (Software Engineering)

YORN Shuttle Service

by Hammad Alam Usmani Student ID No. BB-35071 Muhammad Shakeeb Alam Student ID No. BB-25215

Project Supervisor: Sir Tayyab Yaqoob
Lecturer
IBT, Karachi

Faculty of Computer Sciences & Information Technology
Institute of Business & Technology (IBT), Karachi

Certificate

This is to certify that Hammad Alam Usmani (ID No. BB-35071) and Muhammad Shakeeb Alam (ID No. BB-25215) has completed their Final Year project having title “YORN Shuttle Service”.

The Project is submitted to the IS committee of the Institute of Business & Technology, Karachi, Pakistan for evaluation.

_______________________ Sir Tayyab Yaqoob Thesis Supervisor | ________________________ Prof.Dr.Mansoor-uz-Zafar Dean Faculty of Computer Sciences & Information Technology |

Acknowledgement

I would like to thank Allah who made it possible for us to work on this Project. This project was developed at IBT, Karachi and we are glad, that there we got a chance to complete this useful and informative project work. we would like to extend our sincere gratitude to out research supervisors, Mr. Sir Tayyab Yaqoob, for their assistance and guidance towards the progress of this project This Project was enabled and sustained by their vision and ideas. Throughout the study, Mr. Sir Tayyab Yaqoob has been patiently monitoring our progress and guided us in the right direction and offering encouragement. Obviously the progress we had now will be uncertain without their assistance.

We would also like to thank the entire faculty members for their support and encouragement. We definitely wish to thank Sir Adnan Alam, Sir Muhammad Misbahuddin, and Sir Ziauddian the Faculty of Computer Science program for providing us useful guidelines throughout our project.
We are deeply indebted to our family, thanks to our family members for supporting us. Their constant inspiration and guidance kept us focused and motivated.

Abstract

Navette pick and drop system (NPP) is about to maintain the information for the persons who are getting facility of the pick and drop. This system will maintain the information or the status of the person that either is he/she coming or not on that day. The user’s information will be their pick and drop status. By default the status will be YES (Taking service) for both pick and drop for each day but the user can change the status for any one either for pick or drop. There will be a common screen for all the members; the status will be viewable by any member in that group. And the user or the driver can also broadcast a message so that every user can check the status of that person either he/she is late or any status they want to share. The user can also check the status for the coming days as we are maintaining the information for each day and for each user. The user can also update the status for any day coming in the future. So that he don’t need to worry to update the status and to wait for that day. There is also a facility that the user can also schedule the holidays so it will be very easy and simple for the users. There will be the defined roles in the database i.e. the Admin and the Super Admin or the simple user and the options/features will be available to the user according to their roles defined.
The Admin can use the application either as a user or the Admin. The admin can add/delete/block any user anytime but cannot assign the role of admin to anyone. As the Super Admin have all the privileges as Admin and can also assign the role of admin to anyone. In this project we will use the latest technology CORDOVA/PHONEGAP for the development. Our main concern is to focus the all the devices e.g. Android tablets, Android cell phones of all the sizes, IPhones, I pads and so on.
The internet connection is required to communicate with the application and to change/update the status and to avail all the services. The internet connection could be anyone e.g. Wi-Fi, 3G, GRPS or the any one you are connected to

Table of Contents

Introduction 9 Background 13 Motivation 15 Litrature Review 16 Theory Error! Bookmark not defined. Methodolody 30 Results & Discussion 90 Conclusion 91 References 92 Index 94 Glossary 96

No table of figures entries foun
LIST OF TABLES Table 1. Analysis. Error! Bookmark not defined. Table 2. Desing. Error! Bookmark not defined. Table 3. Coding and Implementation Error! Bookmark not defined. Table 4. Testing. Error! Bookmark not defined. Table 5. Document and Evaluation Error! Bookmark not defined. Table 6. Timeboxing. Error! Bookmark not defined. Table 7. Hwmn-rec Error! Bookmark not defined. Table 8. Swmn-rec Error! Bookmark not defined. Table 9. Hwrc-rec Error! Bookmark not defined.

LIST OF FIGURES Figure 1. a [2] Error! Bookmark not defined. Figure 2. b[2] Error! Bookmark not defined. Figure 3. c [3] Error! Bookmark not defined. Figure 4. A [5]. Error! Bookmark not defined. Figure 5. ee Error! Bookmark not defined. Figure 6. f Error! Bookmark not defined. Figure 7. g Error! Bookmark not defined. Figure 8. h Error! Bookmark not defined. Figure 9. i Error! Bookmark not defined.

Chapter 1

1.1 Introduction

A shuttle service is transport service which is designed to prompt transport people backward and forth from one point to another. Shuttle service has assigned drop-off and pick-up point and vehicles run between the place and target. These services save people essential time by saving them from the high run before and after an event. Closely any vehicle can used to provide the service bus, van or truck but small busses and van are common. One can be the most common types of shuttle service run in business organization where employee travel from home to office and office to home. We all have to agree that in commercial, business and industrial enterprise environment customer expectations are more advanced than at any other point in history. In reality any business company’s reputation is now only as best as its servicing effort. Customer satisfaction is soft to lose and hard to win. To avoid the Erosion of customer it is necessary to implement an integrated service or improve the exist service such as Shuttle service.
Our YORN (Yes and no) shuttle management mobile application for both the iOS and Android. This is the conveyance solution for any organizational, commercial, business and industrial environment customers where user download application and signup within minutes and able to take service and mark status. YORN app makes you able to mark status on one slide. You can put status on current or future base, share your client information with set message status across the organization and quickly access the user profile and other fine detail which help you strength relationship, Including the maintenance and history record collecting and reporting feature. You can also being able to see the others status. The user’s information will be stored as pick and drop status. By default the status will be YES (Taking service) for both pick and drop for each day but the user can change the status for any one either for pick or drop. A common screen for all the members. User can broadcast a message so that every other user can check the status of that person either he/she is late or any status they want to share. The user can also check the status for the coming days as we are maintaining the information for each day and for each user. The user can also update the status for any day coming in the future. So that he don’t need to worry to update the status and to wait for that day. There is also a facility that the user can also schedule the holidays so it will be very easy and simple for the users. The Admin can use the application either as a user or the Admin. The admin can add/delete/block any user anytime but cannot assign the role of admin to anyone. As the Super Admin have all the privileges as Admin and can also assign the role of admin to anyone. To become application Responsive (portable application) the latest technology is CORDOVA/PHONEGAP for the development. Html(Hypertext markup language), CSS(Cascade style sheet) and J-query is used from designed layout. MySQL database is used as backend for storing user information Internet connection will required in order to use YORN app. Easier to use, platform compatibility is designed with the true layout methodologies such Web-based, mobile App.
User will feel Simplicity with the Manner of setup of the display logics. With best practices of user to ensure that the couple of hour user will be handy using the system like a professional. With the advantage of good user friendly system all requirement are satisfy without bother.

1.1.1 Responsive Architecture
Fig [1]
Fig [1]
In this century there are large numbers of screen across desktop, laptop, tablets, phone, TVs, game consoles. Screen sizes will always a matter to be changing. So it is important for application to adapt to any screen size for future or today. On phone user see app content shown in each column and it might be the same content shown in two columns in different device as shown in figure 1. [1]Responsive Architecture is approach of design to provide an optimal viewing experience, easy navigation and reading with minimum effort of scrolling, resizing and panning in across of wide range of devices from (Desktop computer monitor to mobile phones) and their corresponding orientations. Approach behind the designed is that no content and features are lost from phone to desktop to tablets. The design is fluid so that element may or will be displayed differently. Might be some element changed to a pop-out menu and info-box on phone but nothing is going away. YORN application with RA sweep up the layout the viewing environment by using fluid, flexible images, proportion-based grids and CSS3 media queries. Elements which are in application will grow and shrink based on displayed screen resolution. It will avoid the Baleful horizontal scrolling. Technically elements on a page are arranged 12 column grid and group by fluid grid. In each row may have data table which span from 9 columns and in info-box which spans for 3. Another row have Element X spanning for 6 column and Y spanning for 6 as well as. Both rows will place alongside each other in a wider resolution. When screen change in phone resolution these elements will heap on top of each other. User does not have to scrolling left to right and right to left to view these elements. The general Hypothesis is scrolling to the down is good, scrolling right is good.[4] Fluid grid and Flexible image are the concept for calls for page element resizing relative like percentages instead of absolute units like point or pixels in order to prevent them from displaying outside the body.
Media queries let the page use different CSS style rules which is based on device being display the width of the browser.[2][3]
1.1.1.1 Look of Media Query The Traditional query:
Fig [2]
Fig [2]
<link rel="stylesheet" type="text/css" href="core.css" media="screen" />
<link rel="stylesheet" type="text/css" href="print.css" Media="print" />
The media query:
<link rel="stylesheet" type="text/css" media="screen and (max-device-width: 480px)" href="shetland.css" />.
Two main Components in above media query:
1. A media type (screen)
2. The actual query enclosed within parentheses, containing a particular media feature (max-device-width) to inspect, followed by the target value (480px). [5]

1.1.1.2 Advantage of Responsive Design a) Comfortable Experience with Responsive Design
People using their device as more they access to the network and they are looking for the comfortable interface they navigate to desktop website. People are using different mobile device such as tablets, smartphone. If you are not providing a smooth appearance from your application you will not get these visitor as comfortable experience so using responsive design is better. User is likely to switch on your application. [2] b) Maintenance and Efficiency Issue
Double maintenance will be solved. Free from content and some strategies involve in you web application and other in mobile web application. Don’t need to create all new content for each channel. Instead, you simply need to adjust the amount and layout of the visual content that you have initially created. From a responsive “code” design perspective, programming and deploying stand-alone code for multiple channels is not required. Efficiency is gained because one “set” of code can account for the additional channels, allowing for a single code change to migrate across every channel. [2] c) Let’s your application perform better
Using the mobile-first-approach, can lead to cleaner and, therefore, faster performing code on mobile and desktop size devices.[2]

1.1.1.3 Possible disadvantage a) Heavy Load on Application
All elements including images, text content has to load in single application [2] b) Equally available Content on all Platforms
To avoid hard work might just hide contents to handle on mobile device. [2] c) Visitors don’t need same basic experience
This is most likely the case because content on that device is not available or harder to handle [2]

1.1.2 Phone Gap
PhoneGap is a mobile development framework produced by Nitobi, purchased by Adobe Systems in 2011. It enables software programmers to build applications for mobile devices using JavaScript, HTML5, and CSS3, instead of relying on platform-specific APIs like those in iOS or Android It enables wrapping up of HTML, CSS and JavaScript code depending upon the platform of the device. It extends the features of HTML and JavaScript to work with the device. The resulting applications are hybrid, meaning that they are neither truly Mobile native application native (because all layout rendering is done via web views instead of the platform's native UI framework) nor purely web-based (because they are not just web apps, but are packaged as apps for distribution and have access to native device APIs). [7] he easiest way to think of PhoneGap is a web view container that is 100% width and 100% height, with a JavaScript programming interface that allows you to access underlying operating system features. You build your user interface using traditional web development skills (HTML, CSS, & JavaScript), and use the PhoneGap container to deploy to different application ecosystems and devices. When packaged for deployment, the PhoneGap application is a binary distributable file that can be distributed by the “normal” application marketplaces (iTunes, Google App Market, Amazon Market, etc…)[8] he core of PhoneGap applications use HTML5 and CSS3 for their rendering, and JavaScript for their logic. Although HTML5 now provides access to underlying hardware such as the accelerometer, camera and GPS, browser support for HTML5-based device access is not consistent across mobile browsers, particularly older versions of Android. To overcome these limitations, the PhoneGap framework embeds HTML5 code inside a native Web View on the device, using a foreign function interface to access the native resources of the device [7]

1.1.2.1 Apache Cordova
Apache Cordova is a set of device APIs that allow a mobile app developer to access native device function such as the camera or accelerometer from JavaScript. Combined with a UI framework such as jQuery Mobile or Dojo Mobile or Sencha Touch, this allows a smartphone app to be developed with just HTML, CSS, and JavaScript.
When using the Cordova APIs, an app can be built without any native code (Java, Objective-C, etc.) from the app developer. Instead, web technologies are used, and they are hosted in the app itself locally (generally not on a remote http server).
And because these JavaScript APIs are consistent across multiple device platforms and built on web standards, the app should be portable to other device platforms with minimal to no changes Apps using Cordova are still packaged as apps using the platform SDKs, and can be made available for installation from each device's app store.
Cordova provides a set of uniform JavaScript libraries that can be invoked, with device-specific native backing code for those JavaScript libraries. Cordova is available for the following platforms: iOS, Android, Blackberry, Windows Phone, Palm Webhost, Bade, and Symbian[9]

Chapter 2

2.1 Background
2.1.1 Purpose
The purpose of the project is to reduce the maximum human manual effort and makes the application efficient and portable. In this century every person have own phone device or computer. As getting access to the internet people, website, and applications are used in every area. An efficient application can play vital role to attract the user for any organization. In order to get customer trust application should friendly and easy to use.

2.1.2 Scope
While developing the project it was important to consider their suitability for organization use. Organization will used for as pick and drop service. The feature of application will increase the communication relationship between the employee and the organization. The milestones of the project are planning with the flow chart which starts from the 1st week, design the database and layout back and forth in 2nd week. Implementation and Integration testing will do at last of the month.

2.1.3 Glossary
a) Html Hypertext markup language
b) CSS Cascade style sheet
c) RWD Responsive web design
d) Gprs General packet radio service.
e) 3G 3rd Generations
f) DBA Database Administrator

2.1.4 Problem Definition
The General problem with the shuttle service is lack of communication between the customer and driver. Miss-communication often disaster for the organization for this reason. Employee absent will stop the specific work for example: Database Administrator is only one in one organization. If the DBA absent without inform the data management might effects the performance. Sometime driver wait for the customer to pick but customer does not come. Many times employee goes on leaves with informing the shuttle service management this cause very haptic. This reasons a lot of problems for the management and they are as follows:

2.1.4.1 Slow and time consuming
The manual system is time consuming and slow. An organization has to look for the pick and drop of their customer. Organization may have also issue to maintain the record. First the employee sent a request letter for shuttle service then it approve by management. Bus driver have to remember the employee name and address. Bus driver some time forget to pick the employee or some time employee forget to inform the unavailability. This is all a slow process and very time taking. Sometimes bus driver run out of the customer without noticing and this bother the customers resulting in then going to avail another shuttle service.

2.1.4.2 Difficult to manage data
All the data of employee who are availing the service has to be store in register and so keep tracing of employee is difficult. Difficult to search the record from the register which is stored on cabinets.

2.1.4.3 Human mistakes
All data is written down by manually, so lot of mistake occurs. Written recorded data is not accurate and often not reliable. Shuttle application could easily validate the data to the user when some incorrect data would inserted.

2.1.4.4 No backup of manual system
Manual data stored in register could be misplaced or accidently lost. Phone numbers are written in register and organization need to inform all employees the tomorrow bus driver will not come and register is misplace. Ultimately this will very bother the users. Many employees would be lost.

2.1.4.5 High consumption of paper
All the data are stored on paper. Over time more paper work is using and paper take lot of space and has to paid heavy cost for paper. This space can be used if all data migrate to mobile application

2.1.5 Application related objectives

2.1.5.1 Data must be secure
Data must be secure from unofficial and unauthorized user of the internal employee. They can only access the data which have privileges

2.1.5.2 User friendly
Application must be user friendly with respect to layout, color and content size.

2.1.5.3 Data organize
Data must store with organize and updated at every time by using database management system. Data should be retrieved with any bother

2.1.5.4 Care of abnormal and normal date
Abnormal data should be rejected and normal data must insert and accepted. For example if users insert phone number in name field it must reject the insertion.

2.1.6 General Business Related Objectives

2.1.6.1 To make the system fast, efficient and time conserving
To prevent delays, the system will be designed to run in the most efficient of manners. No time will be wasted in making reports as they will be generated by the computerized system automatically.

2.1.6.2 To increase customer satisfaction
This objective carries great worthy and is one of the most essential ones that must deal with. It is very important the customers leave satisfied and are loyal to the YORN application. That situation where the customer has to use another application must avert.

2.1.6.3 To Increase Profits
Once the YORN application is implemented, the number of employees will be reduced to a minimum. This will end up as a profit because fewer salaries will have to be paid. The running cost of the system will be low.

2.1.6.4 To make it Dependable
The application will be made as dependable as possible, so that both the employee and the customer have no doubt about the working and can fully trust it 2.2 Motivation
The motivation of this project to provide the facility to the people who are facing problem in transportation. Commonly in shuttle service which is used under the organization facing problem like late pick late drop miss communication. Another reason is the idea we are going to implement in this project is unique and essential. In our daily life the waiting is one of the major problem we facing because we commitment with other on specific time we don’t follow the time. This application will play significant role in our daily life. To application will make us to realize the cost of time.

2.3 Intended Audience The intended audience of this Project report consists of: • Software designers • Systems engineers • Software developers • Software testers
• Customers (user)

Chapter 3

3.1 Literature Review

3.1.1 Plan of Action

Project Phase | Objective(s) | Task(s) | Duration | Analysis | Recognize the problems in Manual System | Observing the working of general shuttle service of any organization and get data with the help of Interviewing the management and employee. Elicit questionnaires. Identifying problems using the above methods | 3 Days | | Defining the solution with their evaluation | Present the solution of with their advantage and disadvantage | 1 Week | | Analysis Impact on business | Analysis the scope of project in business domain | 1 Day |
Table 1.Analysis
Table 1.Analysis

Project Phase | Objective(s) | Task(s) | Duration | Design | Prepare the plane of action and define the detail of the project | Plan and set the target and objective to be achieved. | 1 Day | | Set Deadlines | Set the deadline for each and whole objective. | 1 Day | | Use different methods and techniques to solve the problems. | Flowcharts Designing of system | 1-2 Days | | Finalizingthe Design | Finalize Design | Recheck make necessary changes if need | 3 Days | | Gather Hardware and Software requirements | Analyzing the hardware and software requirements for the Application | 2 Days | | | Analysis the hardware and software to use for the application and availability in local market | |
Table 2.Design
Table 2.Design

Table 2.Desing
Table 2.Desing

Project Phase | Objective(s) | Task(s) | Duration | Coding and Implementation | Security of Data | An Effectual authorization method to make sure that data cannot be accessed by unauthorized personnel. | 3 Days | | Data Management | Data will be managed by creating tables of the following; User, group, messages, users availability | 1 Week | | User Friendly System | Sliding will make application more user friendly and will be portable by using the PhoneGap technology | 2-3 Weeks | | Simple searching and using features | Easy query and coding will be used for searching the data and using feature such as yes or no status and future updating. | 2-4 Weeks |
Table 3.Coding and Implementation
Table 3.Coding and Implementation

Project Phase | Objective(s) | Task(s) | Duration | Testing | Creating Reports | Reports will be easily generated based upon : Employee past and future information | 5-6 Hours | | Normal Data will be Accepted | The validation will be tested by entering correct and valid data. The test will confirm that all valid data is being allowed in the database | 1 Day | | Abnormal Data will Rejected | The validation will be tested by entering un correct and un-valid data. The test will confirm that all un-valid data is being not allowed in the database | 1 Day | | Extreme Data Values will be Accepted | The extreme values of all the fields’ ranges would be inserted and checked that if they are being accepted or not | 1 Day | | Clean Room testing | Check all Variable, functions, structures, classes and its method are declared with their Specific Name | 1 Day | | Performance Testing | Testing the time take for the each task | 1 Day | | Compatibility Testing | Test the application on every device and mobile operating system | 1 Day |
Table 4.Testing
Table 4.Testing

Project Phase | Objective(s) | Task(s) | Duration | DOCUMENTATIONSYSTEM EVALUATION DEVELOPMENT | All User Manual Documentation provided | Create the user manual for how application will work step by step learning | 2 week | | All Technical Manual Documentation provided | Create technical document for the person if client want to update the feature in application by other developer team | 2 week | | Ensure all target have been achieved. | Evaluation of the new system | 1 Week |
Table 5.Document and Evaluation
Table 5.Document and Evaluation

3.1.2 Time Boxing with Gantt Chart

Plane of Action | Project Activity | Months (Each dark color on small cell represent one week) | | Months | September | October | November | December | | 1 | 2 | 3 | 4 | 1 | 2 | 3 | 4 | 1 | 2 | 3 | 4 | 1 | 2 | 3 | 4 | | 1 | Analysis | | | | | | | | | | | | | | | | | 2 | Design | | | | | | | | | | | | | | | | | 3 | Coding and Implementation | | | | | | | | | | | | | | | | | 4 | Testing | | | | | | | | | | | | | | | | | 5 | Documentation | | | | | | | | | | | | | | | | | 6 | System evaluation | | | | | | | | | | | | | | | | | 7 | Presentation | | | | | | | | | | | | | | | | | | | |
Table 6.Time boxing
Table 6.Time boxing

3.1.3 System Requirement

3.1.3.1 Minimum Hardware Requirement

The Minimum requirement for the application has been improvised to provide at minimum cost, whether these requirement are not recommend.

Reqr.code | Requirement | Description | Hw-Mn-101 | Processor | 1.0-GHz Processor | Hw-Mn-102 | Internal Memory | 500 MB | Hw-Mn-103 | External Memory | 2 GB | Hw-Mn-104 | Device | Mobile with Gprs enable | Hw-Mn-105 | | | Hw-Mn-106 | | | Hw-Mn-107 | | |
Table 7.Hwmn-Req
Table 7.Hwmn-Req

3.1.3.2 Minimum Software Requirement

The Minimum requirement for the application has been improvised to provide at minimum cost, whether these requirement are not recommend.

Reqr.code | Requirement | Description | Sw-Mn-101 | Operating system | Android Gingerbread | Sw-Mn-102 | | | Sw-Mn-103 | | | Sw-Mn-104 | | | Sw-Mn-105 | | | Sw-Mn-106 | | | Sw-Mn-107 | | |
Table 8.Swmn-Req
Table 8.Swmn-Req

3.1.3.3 Recommend Hardware Requirement

The Recommend requirement for the application has been improvised the application more efficient.

Reqr.code | Requirement | Description | Hw-Rc-101 | Processor | 1.33-GHz Dual core | Hw-Rc-102 | Internal Memory | 1 GB | Hw-Rc-103 | External Memory | 8 GB | Hw-Rc-104 | Device | Mobile with 3G/4G enable | Hw-Rc-105 | Display | 4.5 Inch Display screen | Hw-Rc-106 | Printer | An ink jet printer will also be required to print out reports for the managements | Hw-Rc-107 | Internet device | Wimax, Wi-Fi device with 1MB of speed |
Table 9.Hwrc-Req
Table 9.Hwrc-Req

3.1.3.4 Recommend Software Requirement

Reqr.code | Requirement | Description | Sw-Rc-101 | Operating system | Android Gingerbread | Sw-Rc-102 | Word Processor | A word processor will required to process and type in all documentation. Formatting text should be supported | Sw-Rc-103 | Antivirus Software | Antivirus software will provide the protection to the smartphone which prevent the unwanted virus from the phone infection and causing corruption of application. | Sw-Rc-104 | APK OR IPA required | APK FOR ANDROIDE and ipa for ios | Sw-Rc-105 | | | Sw-Rc-106 | | | Sw-Rc-107 | | |
Table 9.Hwrc-Req
Table 9.Hwrc-Req

3.1.4 Requirement Specification

This section includes the functional requirement, non-functional requirement for the application. Functional requirement describe that what the system must do and non-functional requirement how the system will do.

3.1.4.1 Functional Requirement

Functional requirement include all the specific actions of application Authorization Fun_Yorn_Req:01 | Description | After Installing the application the user will be asked login | Input | NULL | Processing | NULL | Output | NULL |

Fun_Yorn_Req:02 | Description | After Installing the application the user must be able to sign up or register. | Input | NULL | Processing | NULL | Output | NULL |

Fun_Yorn_Req:03 | Description | The application must be validate the User name and Password. | Input | Users enter the correct user name and password. | Processing | Check validation and if it is valid user name and password. | Output | A main panel will be open. |

Fun_Yorn_Req:04 | Description | Application must check the valid user name and password. | Input | Users enter the wrong user name and password. | Processing | Check validation and if it is not valid user name and password. | Output | Error message will be generated. |

Fun_Yorn_Req:05 | Description | User should be able to sign up. | Input | Press on sign up. | Processing | Bring the sign up panel | Output | Sign up panel will be open |

Fun_Yorn_Req:06 | Description | Sign up panel should be consist of GROUP, EMAIL, PASSWORD, FIRST NAME, LAST NAME field. | Input | Press on sign up. | Processing | Bring the sign up panel | Output | Sign up panel will be open |

Fun_Yorn_Req:07 | Description | Application must be validate the information that user entered in the sign up field | Input | Null | Processing | Null | Output | Null |

Fun_Yorn_Req:08 | Description | All sign up field of GROUP, EMAIL, PASSWORD, FIRST NAME, LAST NAME should be save in database | Input | Press on sign up. | Processing | Check data and store in database | Output | Successfully signup |

Fun_Yorn_Req:09 | Description | Users sign up request should go to admin for approval | Input | User sign up | Processing | Store in database | Output | Sign up successfully |

Fun_Yorn_Req:10 | Description | An confirmation email should be generated on users email | Input | User email received | Processing | Request approved | Output | User can login now |

Fun_Yorn_Req:11 | Description | Users request for shuttle member will be go on admin for approval | Input | User sign up | Processing | Request sent to admin | Output | Sign up success now you can login |

Fun_Yorn_Req:12 | Description | Super admin should be able to create groups delete groups | Input | SP create or delete group | Processing | Store in database | Output | - |

Fun_Yorn_Req:13 | Description | Admin user should be able to block or unblock the user | Input | Admin block or unblock the user | Processing | Store in database | Output | Update successfully |

Fun_Yorn_Req:14 | Description | Application must recognize the Super admin, admin and user with their email addresses. | Input | User enter email address | Processing | Check from database | Output | Panel open according with the users types |

Fun_Yorn_Req:15 | Description | User should type message | Input | User navigate left on own name and tap to select message status | Processing | Store in database | Output | Message has been sent |

Fun_Yorn_Req:16 | Description | User should set status on touch the specific icon. | Input | User touch on green or red icon to set status. | Processing | Store data for today in database. | Output | Red icon will be highlighted. |

Fun_Yorn_Req:17 | Description | User should be able to update profile information | Input | User touch on menu icon and update option will touched by user | Processing | Bring update panel | Output | - |

Fun_Yorn_Req:18 | Description | User should able to go previous or future date through navigation | Input | User touch on previous date or future date arrow. | Processing | Search from database using where date query | Output | Previous or future data shows of other users. |

Fun_Yorn_Req:19 | Description | User should be able to set status for future | Input | User touch on future date arrow and select the date | Processing | Store in database | Output | - |

Fun_Yorn_Req:20 | Description | User should be able to set other user contact number | Input | User navigate to right | Processing | - | Output | User contact number will show |

3.1.4.2 Non-Functional Requirement

Non-functional requirement are describe the system that don’t relate to system execution but to evolution over time.

3.1.4.2.1 Performance Requirements

3.1.4.2.1.1 Response times

NFPR-RS-REQ: 01 Application should not take to load more than 3-4 second with average speed of internet. While with low speed internet it should not take more than 1 min.

NFPR-RS-REQ: 02 Screen refresh time should be in less than 3 seconds.

3.1.4.2.1.2 Processing times

NFPR-PT-REQ: 01 Application should take less than 8-10 seconds to retrieve data from database whether it is login operation or data update operation.

3.1.4.2.1.3 Query times

NFPR-QY-REQ: 01 Query should be well designed which helps the processing time.

3.1.4.2.1.4 Availability

NFPR-AV-REQ: 01 Application should available for 24 hours 7 day week

3.1.4.2.1.5 Location of operation

NFPR-LO-REQ: 01 Application should be used in for each organization

3.1.4.2.2 Safety Requirements

There is no such requirement for safety with this application other than any risk of a mobile device. The only risk is with the user using the device when they should not driving

3.1.4.2.3 Security Requirements

NFPR-SCT-REQ: 01 Application must be connect with database in order for user to login properly and be identified

NFPR-SCT-REQ: 02 User should not be able to see other group’s user information

3.1.4.2.4 Easy use Requirements

NFPR-EUR-REQ: 01 Application should take less than 10 to 15 minutes for understanding features.

3.1.4.3 Inverse Requirement

INV-REQ: 01 Application interface color such as red, white pink should not be used as background.

INV-REQ: 02 Application fonts should not different in any panel, should follow only one style font.

INV-REQ: 03 Application size should not stretched for reasons of portability

3.1.4.4 Design and Implementation Constraints
DSG-REQ: 01 Application must run on the Android, iOS, and windows operating system.

DSG-REQ: 02 MySQL database should be used by application and same one that is used for desktop application.

DSG-REQ: 03 Application must also use the language supported by Android, iOS, and windows environment.

Chapter 5

Methodology of Solution

5.1 Screens
Screen panel with respect to smart phones

Panel Name: Main Screen
Purpose: To Login or signup the user

Signup
Signup
Login
Login
Logo
Logo

Screen Description

i. When users open the yorn application, Main screen will open. ii. User will allow to login or signup

Panel Name: Login Screen
Purpose: To Login the user with username and password
(Forget you Password)
(Forget you Password)
Text field
Text field
Password
Password
Email:
Email:
Text field
Text field
LOGIN
LOGIN
Logo
Logo

Screen Description

i. When user click/touch on login, login screen will open. ii. User will enter his/her email id iii. User will enter his/her password iv. The user will click/touch on login v. User will allow to click/touch on forget password if failed to attempt successfully login.

Panel Name: Signup Screen
Purpose: To Sign up the user with Group, email, password, first name, last name, phone number.Text field
Text field
Phone number:
Phone number:
Text field
Text field
Text field
Text field
Last name:
Last name:
First name:
First name:
Password:
Password:
Text field
Text field
Text field
Text field
Email:
Email:
Text field

Text field

Group:
Group:
Logo
Logo
Sign up
Sign up

Screen Description

I. If user is new in this app, by clicking/touching on signup this screen will open II. User will select his/her group name III. User will enter email address IV. User will enter password V. User will enter his name and last name VI. User will enter phone number VII. User information will store in database VIII. Now user can allowed to login IX. Message will pop-pop when user signup successfully. X. Message will be “Success Signup, go to your email for conformation”. XI. User will go to email and click the link for conformation. XII. Now users can successfully signup.

Panel Name: Retrieve Password Screen
Purpose: To Retrieve password if user forget his/her password
Email
Email
Phone Number
Phone Number

Logo
Logo
Text field

Text field

Text field

Text field

Retrieve Password
Retrieve Password

Screen Description

I. If user forget the password, it will recover easily with this screen II. User will touch/click on forget password III. This “forget password screen” will show to the user. IV. User will insert the email id V. User will insert the phone number VI. User will press the retrieve password button. VII. An automatic Email will generate and send to the user email id. VIII. Email contain new password. IX. Now user will insert new password. X. User can now change the password in the profile section after Login.

XI.

Panel Name: Login Screen
Purpose: Error Pop-pop when login button pressed without enter any fieldLogo
Logo
Text field

Text field

Text field

Text field

Email:
Email:
Password
Password
(Forget you Password)
(Forget you Password)

LOGIN
LOGIN
Please fill out the form properly
Please fill out the form properly

Screen Description

I. User will face the error if pressed login button without insert the data II. User do not insert email id III. User do not insert the password IV. User press the login button V. Error will be pop-pop that “Please fill the form properly”.

Panel Name: Login Screen
Purpose: Error Pop-pop when wrong email id or password entered.

Logo
Logo
Text field
Text field
Text field
Text field
Email:
Email:
Password
Password
(Forget you Password)
(Forget you Password)
LOGIN
LOGIN
Wrong ID OR Password
Wrong ID OR Password

Screen Description

I. User will face the error if user enter wrong email id or password II. User insert wrong email id III. User insert wrong password IV. Or user insert correct email id but wrong password V. Or user insert wrong email id but correct password. VI. Error will be pop-pop that “Wrong id or Password”.

Panel Name: Sign up Screen
Sign up
Sign up
Please fill out the form properly
Please fill out the form properly
Logo
Logo
Group:
Group:
Text field

Text field

Email:
Email:
Password:
Password:
Text field
Text field
First name:
First name:
Text field
Text field
Last name:
Last name:
Text field
Text field
Phone number:
Phone number:
Text field
Text field
Purpose: Error Pop-pop when Signup button pressed without enter dataText field
Text field

Screen Description

I. User will face the error if user enter do not insert the data in sign up field. II. User does not insert email id III. User insert do not insert password IV. User does not insert the first name V. User does not insert the last name VI. User does not insert the phone number. VII. Users press the signup. VIII. Error will be pop-pop that “Please fill out the form properly”.

Panel Name: User Main Screen
Purpose: When user successfully login this main screen should appear
Group name
Group name
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name

User’s name

Date
Date
Refresh button Refresh button
Menu
Menu

Screen Description

I. When user successfully login, main screen will be open to the user. II. User will see the group name at the top of application. III. User will see the current date. IV. User can click the menu icon at the right top of the application. V. User will see the other user name and their status. VI. User will see the user blink, that means user transmit the message. VII. Note that message will be public. VIII.

Panel Name: User number screen
Purpose: When user navigates to right by touching (user name) user’s contact number will show.

Menu
Menu
User’s name
User’s name
When Right Navigate
When Right Navigate
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name Refresh button Refresh button
User Contact Number

User Contact Number

Date
Date

Screen Description

I. Main screen will be open to the user. II. User can see the other users contact number III. User will click/touch on users’ name. IV. User navigate to the right side V. User will see number of other users. VI. To return user will navigate left to see the name. VII. Note that contact number will be public.

Panel Name: User type message screen.
Purpose: When user navigates left by touching the user name, types message will show.

Menu
Menu
Date
Date
Type Message

Type Message

Refresh button Refresh button
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
When Left Navigate
When Left Navigate

Screen Description

I. Main screen will be open to the user. II. User can see type the message III. User will click/touch on own name. IV. User navigate to the left side V. User will see message type options. VI. To return user will navigate left to see the name. VII. Note that message will be public.

Panel Name: User type screen message option.
Purpose: When user clicks on type message, message option will open.

Select Message Type
Select Message Type
On my Way
On my Way
Type other message
Type other message
No shuttle for me
No shuttle for me
I will be there by:6:30
I will be there by:6:30
Please wait for me
Please wait for me

Screen Description

I. Message screen will be open to the user
II. User can see type the message
III. User will click/touch on message option “Select type message”.
IV. User can select the template message VI. User select the message “On my way” or “Please wait for me” or “I will be there by 6:30”, “No shuttle for me”. VII. User can type his own message by click on “ Type other message”. VIII. Message delivered
VI. User can select message again. VIII. Note that message will be public. IX. Other user can see the message.

Panel Name: User Menu option screen
Purpose: When user touch on menu option, sub menu option will open.

Menu
Menu
Logout
Logout
Go to YORN
Go to YORN
Profile setting
Profile setting

Screen Description

I. User can go to menu option screen II. User clicks on the icon on the top right side of application. III. Menu option screen will open IV. Menu contains 3 sub menu options. Profile Setting, Go to Yorn, Logout V. If user click on “ Profile Setting”. VI. Profile setting option will allow the user to change or update his/her information. VII. If User click on “Go to YORN” option. VIII. Go to yorn will bring the user at main screen. IX. If user click on “Logout” option. X. Logout will allow the user to logout from the session.

Panel Name: Admin Menu option screen
Purpose: When Admin touch on menu option, sub menu option will open.

Admin Panel
Admin Panel
Logout
Logout
Go to YORN
Go to YORN
Profile setting
Profile setting
Menu
Menu

Screen Description

I. Admin user can go to menu option screen II. User clicks on the icon on the top right side of application. III. Menu option screen will open IV. Menu contains 4 sub menu options. Admin Panel, Profile Setting, Go to Yorn, Logout. V. If user click on Admin panel option. VI. Admin panel will show the main screen with additional features. VII. In admin panel, admin will enable to add user, accept users request or block request. VIII. If user click on “Profile Setting”. IX. Profile setting option will allow the user to change or update his/her information. X. If User click on “Go to YORN” option. XI. Go to yorn will bring the user at main screen. XII. If user click on “Logout” option. XIII. Logout will allow the user to logout from the session.

Panel Name: Admin group Screen
Purpose: When user touch on admin panel subs menu option this screen will open, where admin can allow user, block user and add users.

Group Name

Group Name

Menu
Menu
Refresh button Refresh button
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name

Screen Description

I. When admin user successfully login, admin main screen will be open. II. Admin will see the group name at the top of application. III. Admin will see the current date. IV. Admin will click the menu icon at the right top of the application. V. Admin will see the other user name and their status. VI. Admin will add, accept and block the user by clicking on the user name specifically. VII. Admin will see the user blink, that means user transmit the message. VIII. Admin will pass the message around the group

Panel Name: Admin group Screen.
Purpose: When user touch on admin panel subs menu option this screen will open, where admin can allow user, block user and add users.

Admin Setting

Admin Setting

This will block the users
This will block the users
This will allow the user if request come
This will allow the user if request come
This will add the user
This will add the user

Text field
Text field
Phone Number
Phone Number
Text field
Text field
Text field
Text field
Email
Email
Name
Name Refresh button Refresh button
Group Name

Group Name

User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
User’s name
Menu
Menu

Screen Description

I. Admin main screen will show to user. II. Admin can add, accept and block the user III. Admin will click on user name IV. Sub option will show to the user which contain add, accept and block icon. V. Admin will click the add icon VI. Admin add the information which required to the application VII. Admin click the accept icon. VIII. New user will add to the group. IX. Admin click block icon to the user request or existence user.

Panel Name:
Purpose:

Please fill out the form properly
Please fill out the form properly
Text field
Text field
Phone number:
Phone number:
Text field
Text field
Last name:
Last name:
Text field
Text field
First name:
First name:
Text field
Text field
Password:
Password:
Email:
Email:
Text field

Text field

Sign up
Sign up
Group:
Group:
Logo
Logo

Panel Name:
Purpose:

Logo
Logo
Group:
Group:
Sign up
Sign up
Text field

Text field

Email:
Email:
Password:
Password:
Text field
Text field
First name:
First name:
Text field
Text field
Last name:
Last name:
Text field
Text field
Phone number:
Phone number:
Text field
Text field
Please fill out the form properly
Please fill out the form properly

Panel Name:
Purpose:

Text field
Text field
Phone number:
Phone number:
Text field
Text field
Last name:
Last name:
Text field
Text field
First name:
First name:
Text field
Text field
Password:
Password:
Email:
Email:
Text field

Text field

Sign up
Sign up
Group:
Group:
Logo
Logo

Please fill out the form properly
Please fill out the form properly

Panel Name:
Purpose:

Logo
Logo
Group:
Group:
Sign up
Sign up
Text field

Text field

Email:
Email:
Password:
Password:
Text field
Text field
First name:
First name:
Text field
Text field
Last name:
Last name:
Text field
Text field
Phone number:
Phone number:
Text field
Text field

Please fill out the form properly
Please fill out the form properly

Panel Name:
Purpose:

Text field
Text field
Phone number:
Phone number:
Text field
Text field
Last name:
Last name:
Text field
Text field
First name:
First name:
Text field
Text field
Password:
Password:
Email:
Email:
Text field

Text field

Sign up
Sign up
Group:
Group:
Logo
Logo

Please fill out the form properly
Please fill out the form properly

Table Design

Table Name: Group | Primary Key: Group id | Field Name | Data type (Length) | Constraint | group_id | Varchar(255) | NOT NULL | group_title | Varchar(255) | NULL | group_created_on | Varchar(255) | NULL | group_created_by | Varchar(255) | NULL | group_deleted_on | Varchar(255) | NULL | group_deleted_by | Varchar(255) | NULL | group_updated_on | Varchar(255) | NULL | group_updated_by | Varchar(255) | NULL |
Table 10 database1
Table 10 database1

Table Name: messages | Primary Key: messages_id | Field Name | Data type (Length) | Constraint | message_id | bigint(20) | NOT NULL | msg_group_id | bigint(20) | NULL | msg_user_id | bigint(20) | NULL | msg_user_message | Varchar(255) | NULL | msg_date | Varchar(255) | NULL | seen_by | Varchar(255) | NULL | msg_created_on | Varchar(255) | NULL | msg_created_by | Varchar(255) | NULL | msg_updated_on | Varchar(255) | NULL | msg_updated_by | Varchar(255) | NULL | msg_deleted_on | Varchar(255) | NULL | msg_deleted_by | Varchar(255) | NULL |
Table 11 database2
Table 11 database2

Table Name: users_availability | Primary Key: user_avb_id | Field Name | Data type (Length) | Constraint | user_avb_id | bigint(20) | NOT NULL | avb_user_id | bigint(20) | NULL | avb_grp_id | bigint(20) | NULL | avb_type | enum('Day’, ‘Holiday') | NULL | avb_pick_status | enum('Yes’, ‘No') | NULL | avb_drop_status | enum('Yes’,’ No') | NULL | avb_date | date | NULL | avb_created_on | Varchar(255) | NULL | avb_created_by | Varchar(255) | NULL | avb_updated_on | Varchar(255) | NULL | avb_updated_by | Varchar(255) | NULL | avb_deleted_on | Varchar(255) | NULL |
Table 12 database3
Table 12 database3

Table Name: users | Primary Key: user_id | Field Name | Data type (Length) | Constraint | user_activation_code | text | None | user_cell | varchar(255) | NULL | user_created_by | varchar(255) | NULL | user_created_on | varchar(255) | NULL | user_deleted_by | varchar(255) | NULL | user_deleted_on | varchar(255) | NULL | user_device_id | bigint(20) | NULL | user_email | Varchar(255) | NULL | user_first_name | Varchar(255) | NULL | user_group_id | varchar(255) | NULL | user_id | bigint(20) | NULL | user_is_verified | enum('Yes', 'No') | None | user_last_name | Varchar(255) | None | user_password | Varchar(255) | NULL | user_status | enum('Active', 'Pending', 'Deleted') | NULL | user_type | enum('Admin', 'User', 'SAdmin') | NULL | user_updated_by | Varchar(255) | NULL | user_updated_on | Varchar(255) | NULL |

Relationships

Fig [3]
Fig [3]

Query Design

Query Name: Customer Login
Query Description: This query has been designed for customer login
Query: SELECT user_id, user_email, user_type from users where user_email and user_password AND user_status;

Field Name | Data Type | Criteria | User_id | bigint(20) | | User_email | Varchar(255) | | User_type | enum('Admin', 'User', 'SAdmin') | | User_password | Long Integer | | User_status | enum('Active', 'Pending', 'Deleted') | “Active” |

Query Name: User Info
Query Description: This query has been designed for customer Info
Query: SELECT users.user_id,users.user_first_name,users.user_last_name,users.user_cell, users_availability.avb_pick_status, users_availability.avb_type, users_availability.avb_drop_status, users_availability.avb_date, messages.message_id, messages.msg_user_message, messages.msg_date, messages.msg_created_on FROM users LEFT JOIN users_availability ON((users.user_id = users_availability.avb_user_id) AND (users_availability.avb_date = '$date')) LEFT JOIN messages ON((users.user_id = messages.msg_user_id) AND (messages.msg_date = '$date')) WHERE users.user_status != 'Deleted' AND users.user_status != 'Pending' AND users.user_type != 'SAdmin' ORDER BY (users.user_id='$user_id') DESC, (users.user_first_name) ASC";

Field Name | Data Type | Criteria | user_id | bigint(20) | Desc order | user_first_name | Varchar(255) | Asc Order | user_last_name | Varchar(255) | | user_cell | Varchar(255) | | avb_pick_status | enum('Yes', 'No') | | avb_type | enum('Day', 'Holiday') | | avb_drop_status | enum('Yes', 'No') | | avb_date | date | | message_id | bigint(20) | | msg_user_message | varchar(255) | | msg_date | date | | msg_created_on | varchar(255) | |

Query Name: User list item Admin.
Query Description: This query has been designed for list the admin user.
Query: "SELECT user_id, user_first_name,user_last_name,user_email,user_type,user_cell, user_status FROM users WHERE user_id != '$user_id' AND user_status != 'Deleted' AND user_type != 'SAdmin'";

Field Name | Data Type | Criteria | user_id | bigint(20) | Desc order | user_first_name | Varchar(255) | Asc Order | user_last_name | Varchar(255) | | user_email | Varchar(255) | | user_type | enum('Admin', 'User', 'SAdmin') | ‘SAdmin’ | user_cell | Varchar(255) | | user_status | enum('Active', 'Pending', 'Deleted') | Not 'Deleted' |

Query Name: user_profile_model.
Query Description: This query has been designed for show the user profile.
Query: SELECT user_id, user_first_name,user_last_name,user_email,user_type,user_cell FROM users WHERE user_id = ' ’ AND user_status != 'Deleted';

Field Name | Data Type | Criteria | user_id | bigint(20) | | user_first_name | Varchar(255) | | user_last_name | Varchar(255) | | user_email | Varchar(255) | | user_type | enum('Admin', 'User', 'SAdmin') | ‘SAdmin’ | user_cell | Varchar(255) | |

Query Name: retrieve_password
Query Description: This query has been designed password retrieve.
Query: SELECT * FROM users WHERE $field_name = '$value'";

Field Name | Data Type | Criteria | | | |

Menu Layout

Admin Panel
Admin Panel
Profile Setting
Profile Setting
Go to yorn
Go to yorn
Logout
Logout
Admin User
Admin User
General User
General User
Go to yorn
Go to yorn
Profile Setting
Profile Setting
Logout
Logout

Flowcharts

Yes
Yes
App login
App login
Enter ID password
Enter ID password
No
No
Main Menu
Main Menu
If ID and password is correct is correct
If ID and password is correct is correct
Display message “Incorrect ID or Password!”

Display message “Incorrect ID or Password!”

Login Panel

Signup flowchart
Display message “Incorrect data!”

Display message “Incorrect data!”

Yes
Yes
Login screen
Login screen
If data is correct
If data is correct
App signup
App signup
No
No
Enter data to required field
Enter data to required field

Main Screen

If Choice =
If Choice =
Yes
Yes
End
End
No
No
3. Date screen
3. Date screen

2. Message screen
2. Message screen

1. user number screen
1. user number screen
If Choice =
If Choice =

Choices to navigate on Main screen
1. Navigate right to see number
2. Navigate left to set message
3. Navigate left or right on date to …previous and future date.
Choices to navigate on Main screen
1. Navigate right to see number
2. Navigate left to set message
3. Navigate left or right on date to …previous and future date.
Display "Main Screen"
Display "Main Screen"
Exit (yes/no)
Exit (yes/no)

Main Menu
Main Menu
Main Screen
Main Screen

Main menu

2. Change group screen
2. Change group screen
3. Main screen

3. Main screen

4. Logout screen
4. Logout screen
If Choice =
If Choice =
Display Choices 1. Profile setting 2. Change group 3. Go to yorn 4. logout
Display Choices 5. Profile setting 6. Change group 7. Go to yorn 8. logout
Main Menu
Main Menu
1. Profile setting screen 1. Profile setting screen View Main menu icon
View Main menu icon

Back to main menu

Back to Main Menu
Back to Main Menu
Main Menu
Main Menu
Main Menu icon
Main Menu icon

Add Record Flowchart

Add Record in
Signup panel

Read field Table
Field Table
Enter Group
Enter Email
Enter Password
Enter First name
Enter Last name
Enter Phone number

Signup
Field Table
Add Record in
Signup panel

Read field Table
Field Table
Enter Group
Enter Email
Enter Password
Enter First name
Enter Last name
Enter Phone number

Signup
Field Table

Update Record Flowchart Update Record in
Profile setting

Read field Table
Field Table
Update
Field Table Update successfully Please fill form properly.
Yes
No
Edit record
Update Record in
Profile setting

Read field Table
Field Table
Update
Field Table Update successfully Please fill form properly.
Yes
No
Edit record

Admin panel delete Record Flowchart
Main screen
Read user from database

User’s Table
Select user name to delete
Delete
User’s Table Delete successfully
Main screen
Read user from database

User’s Table
Select user name to delete
Delete
User’s Table Delete successfully

To see user’s number flowchart
Main screen

Read data from database
User’s Table Navigate right on user name Number shown
Main screen

Read data from database
User’s Table Navigate right on user name Number shown

Navigate set message flow chart
Main screen
Store message on database by date and time
User’s Table Navigate left on user name Message updated
Message screen 1 .On my Way
2. Please wait for me.
3. I will be there by:6:30.
4. No shuttle for me
5.Type other message
1, 2, 3, 4,
Enter message
5
Main screen
Store message on database by date and time
User’s Table Navigate left on user name Message updated
Message screen 1 .On my Way
2. Please wait for me.
3. I will be there by:6:30.
4. No shuttle for me
5.Type other message
1, 2, 3, 4,
Enter message
5

Data Flow Diagram:-
Level 0: Data flow Diagram

Response from database Response from database
Request to the database
Request to the database
Database
Database
YORN
App
YORN
App
Input from User

Input from User

User User SS SS
Output to the User

Output to the User

Level 1: Data flow Diagram

Message from General user interface
Message from General user interface

YORN
App
YORN
App
G.User Interface
G.User Interface
Super Admin Interface
Super Admin Interface
Message to General user interface
Message to General user interface
Input from G.user
Input from G.user
Output to G.user
Output to G.user
Message to Super Admin
Message to Super Admin
Message from Super Admin
Message from Super Admin
Response from S.Admin
Response from S.Admin
Request to S.Admin
Request to S.Admin
Admin Interface
Admin Interface
Message to Admin interface
Message to Admin interface
Message from Admin interface
Message from Admin interface

Level 1: Data Flow Diagram: Interface with All User

Logout
Logout
User
User
Process User Inputs
Process User Inputs
Date wise status
Date wise status
Update info
Update info
Set Message status
Set Message status
Set YORN status
Set YORN status
YORN App
YORN App

Signup
Signup
Until correct
Until correct
Insert email id and password
Insert email id and password

Level 1: Data Flow Diagram: login

Database
Database
Login Password Login Password Login email id Login email id YORN App YORN App
User
User

Level 1: Data Flow Diagram: Signup
Request to App
Request to App
Response from App
Response from App
Response from database
Response from database
Request to database
Request to database
Invalid data
Invalid data
Database
Database YORN App YORN App Signup Signup
User
User

Level 1: Data Flow Diagram: Password recovery YORN App YORN App
User
User Recovery password Recovery password
Database
Database User email User email

Level 2: Data Flow Diagram: Signup User check for verification
User check for verification
User check for verification
User check for verification User email id User email id
Request from database
Request from database
Response to database
Response to database
Response from database
Response from database Admin User App Admin User App
Request to App
Request to App
Response from App
Response from App
Request to database
Request to database
Database
Database
Invalid data
Invalid data Signup Signup
User
User G.User App Interface G.User App Interface

Level 3: Data Flow Diagram: All Process
Database
Database
Create group
Create group User email id User email id
Process User Inputs
Process User Inputs
Date wise status
Date wise status
Set Message status
Set Message status
Update info
Update info
Set YORN status
Set YORN status login login
Invalid data
Invalid data
Try again
Try again Signup Signup YORN App YORN App
Super
Super
Admin
Admin
User
User

Use case Diagrams

signup signup Check number
Check number
Logout
Logout
Remove user
Remove user
Add user
Add user Database Database
Admin
Admin
User
User
Super admin
Super admin Group rights Group rights
Update information
Update information
Old and future status by Navigate date
Old and future status by Navigate date
Message status
Message status
YORN status
YORN status
Login
Login
Validation
Validation
Request rights
Request rights
High level Diagram:-YORN app

Low Level Diagram of Login:-
Super admin
Super admin
Admin
Admin
User
User
Insert email id
Insert email id
Insert Phone number
Insert Phone number
Forget password
Forget password
Insert Password
Insert Password
Insert email id
Insert email id database database

Low Level Diagram of Group change :-

User
User
User
User
User
User
Group owner change
Group owner change
Group accept request
Group accept request
Group delete
Group delete
Group add
Group add
Group change
Group change

Low Level Diagram of signup:-

User
User
Phone number
Phone number

Last name
Last name
First name
First name
Group select
Group select
Email id
Email id
Password
Password

Sequence Diagram

Login Sequence Diagram:-

Read id() and password ()
Read id() and password ()
Login ()
Login ()
Verify ()
Verify ()
Response ()
Response ()
Insert password ()
Insert password ()
Message ()
Message ()
Insert email id ()
Insert email id ()
Launch application
Launch application
Application
Application
Application user
Application user
Data Base
Data Base

User YORN status Sequence Diagram:-
Status 1 ()
Status 1 ()
Status 0 ()
Status 0 ()
Message ()
Message ()
Response ()
Response ()
Request ()
Request ()
Status Yes/no ()
Status Yes/no ()
Application
Application
Application user
Application user
Database
Database

User Message status Sequence Diagram:-
Message ()
Message ()
Message 1 ()
Message 1 ()
Response ()
Response ()
Request ()
Request ()
Message 1 ()
Message 1 ()
Navigate ()
Navigate ()
Message 0 ()
Message 0 ()
Application user
Application user
Application
Application
Database
Database

Signup Sequence Diagram:-
Message ()
Message ()
Verify user
Verify user
Email generated
Email generated
Message ()
Message ()
User-email
User-email
Database
Database
Response ()
Response ()
Read all fields ()
Read all fields ()
Verify ()
Verify ()
Application
Application
Insert First name ()
Insert First name ()
Insert Last name ()
Insert Last name ()
Insert Phone number ()
Insert Phone number ()
Insert password ()
Insert password ()
Insert Email id ()
Insert Email id ()
Insert Group ()
Insert Group ()
Signup ()
Signup ()
Launch application
Launch application
Application user
Application user

Forget Password Sequence Diagram:-

Get temporary password
Get temporary password
Message ()
Message ()
Email generated ()
Email generated ()
Request ()
Request ()
Response ()
Response ()
Insert email id () or phone number ()
Insert email id () or phone number ()
Forget password ()
Forget password ()
Database
Database
User-email
User-email
Application
Application
Application user
Application user

Deployment Diagram

This diagram gives the physical arrangement of system
PHONE GAP
PHONE GAP PHP (WEB SERVICE) PHP (WEB SERVICE)
Application
Application
AJAX (SERVER COMMUNICATION
AJAX (SERVER COMMUNICATION
JAVA SCRIPT
JAVA SCRIPT
JQUERY
JQUERY
XML
XML
CSS
CSS
HTML
HTML
All user related information
All user related information
< MySQL >
< MySQL >
Database Service
Database Service
< Client >
< Client >
< Client >
< Client >
Web Browser
Web Browser
Mobile
Mobile

Chapter 6

Results & Discussion
This Chapter can be separated with Discussion (Critical Discussion on your study) and Results.
Chapter 7

Conclusion

Chapter 8

Future Work / Recommendation (if any)

* References *
Index

Biblography
Author Name: XXXX
ID: BMS/000
Cell#: 0300XXXXXXX
Address:.
Supervisor Name: Mr./Mis
Completion year: 2013
Degree Program: MS(SE)

Glossary SaaS Software as a service IaaS Infrastructure as a Service PaaS Platform as a Service Inter-portability The ability of two or more systems or components to exchange information and to use the information that has been exchanged Fat client A user's computer that contains its own applications that are run in the machine. New programs are installed on the local hard disk. This is the typical way people use their computers. Thin client A client machine that relies on the server to perform the data processing. Outages A temporary suspension of operation, especially of electric power Vendor lock in Vendor lock-in is a situation in which a customer using a product or service cannot easily transition to a competitor’s product or service. Vendor lock-in is usually the result of proprietary technologies that are incompatible with those of competitors. SOA Service-Oriented Architecture