Print Email Download Reference This Send to Kindle Reddit This
submit to reddit

Sms Meeting Manager Project Computer Science Essay

SMS Meeting Manager Project is achieved using wireless PUSH technologies over GSM and SMPP enabled networks serving SMS and HTTP protocols. The Meeting Manager System is also tested using Multiple WAP simulators and mobile hardware. This project is not developed for a real client, and does not include an Administrator’s Access, yet it holds great tendency to be used as a commercial bespoke application that can be tailored to meet the specific individual or business requirements ranging from a single user to a group or a large organisation. I believe that using all these technologies in proposed fashion, makes this project meet requirements of my chosen Master’s Program under QCF guidelines.

Since I am doing Masters in Mobile Computing & Communications. The subjects that are learned and the skills I have earned, through out my educational tenure with University of Greenwich, have surely help nurture my aims to achieve this goal within due time. List of subject that contributed towards this achievement are Mobile Application Development, Mobile Technologies, Web Engineering (Enterprise), Software tools & techniques, Enterprise Software Engineering Development, Operating System & Application Server Security etc.

Project website URL:

Account login details for two default users are given in table below:

Business

Client

Admin

Login ID

jack.turner@gmail.com

romeo.watson@gmail.com

Not yet applicable

Password

jill123

juliet

Not yet applicable

Table A: Account login details

CHAPTER 1: INTRODUCTION

Introduction:

There are number of things that we can do these days with internet on mobile devices. We can book a flight, order dinner, car rental, purchase, and parking payments etc. But the customers who are used to booking these services everyday using mobile phones can not book a simple meeting sometimes. They have to call, when you are not there, they leave a message and you call back than they are not there. You are also assuming that they will call you in your business hours knowing that they are also working. Once you are connected, you still have to find that old schedule book to find a time slot to book them in especially all at the time when you should be doing something more productive

There is a range of desktop and web based solutions available in the market. But there are clears limitations for using such applications over mobile phones due to cross platform or downward incompatibility issues or the application is resource hungry and may be little too much for a certain mobile device. Current methods of booking or setting up meetings are still either too lazy or far more liberal to share important personal details among contributors.

SMS Meeting Manager is designed required particularly for mobile phones that can fit the business needs for a single user to a group or a large organisation. Meeting requests must be sent, granted or declined via Short Message Text (SMS) via SMPP/GSM and emails over HTTP protocol. Users can login to manage there availabilities or search other users to book meetings out of their availability slots all using any mobile phone with a WAP access and a phone number.

Aim:

The objective for this project is to build a simple meeting management system that can act as a platform independent, client/server web application for mobile phones. A meeting management system can allow people to search individuals and businesses to request meetings knowing each other’s profession profile rather than personal all from the ease of their own mobile phones.

Objectives:

Explore and compare already available solutions in the market for meeting management and booking systems and their usability over mobile phones.

Examine the online sources of information and proposals to improve the user experience of using Web on mobile devices.

Investigate available literature about SMS protocols, SMPP and GSM technologies, Push/Pull Services, mobile applications and developers references based on the exchange of SMS messages.

Evaluate findings based on a wide range of literature research either to implement existing concepts of similar market available SMS systems or to design a partially or fully new product for Meeting Manager that can provide scope for further scalability and future development.

To conduct a research comparing and analysing a range of industry standards for SMS communications including existing Mobile Aggregator, SMS services and techniques, third party API's, price plans, features, feasibility and back end technologies.

Examine legal, Social and ethical impacts of proposed application modal within an organisation and its individuals.

To perform a critical analysis to compare and contrast the technological feasibility of different programming languages, open source development tools and techniques to implement the model.

A Software application will be developed to arrange meetings amongst a number of people via their Mobile phones. It will be mainly developed using Visual .Net or Java technologies.

Chapter 2: Mobile Web Applications & Usability Issues.

While developing this Mobile based SMS Meeting Management system, I have tried to keep the simplicity and ease of use at utmost priority. I have also set a strict criterion to design every element of this system by keeping user needs and requirements for a complete meeting management system.

The ambition is not about making just another meeting management application as there are quite a few available of the shelf. The aim is to make a system that is easy enough to be used by single user or a business, using any WAP or internet enabled mobile phones especially the old ones.

Importance of the Mobile Web Site

Few years ago businesses realised the immense importance of web presence, today it’s become more and more clear that targeting and addressing the new audience is become more and more crucial for these businesses.

“A picture is worth a thousand words, so I’ve collated and created graphs that demonstrate – whether you create software, sell services, or provide content – why mobile should be taken seriously.”

(Zambonini, D. 2009)

Zambonini, by showing following graphs in his article, clearly mentions an increasing trend for the exceeding number of People mobile web.

(Zambonini, D. 2009)

He further indicates that there are approximately 3 billions mobiles in the market that is 4 times more than the PCs sold and used. The number is growing everyday and more and more phones are arriving with unusual capabilities being introduced. Zambonini’s findings are vivid from the graphs below.

(Zambonini, D. 2009)

(Zambonini, D. 2009)

(Zambonini, D. 2009)

The above discussed trends evidently indicate that the rising pattern of people is reaching on to the internet on their mobile or handheld devices showing a growing need to have a website or web applications that can use the internet and WAP facilities efficiently.

(Zambonini 2009)

Most websites show no problem in rendering decently on latest handsets that have a sophisticated web browser like most desktop machines have, but they act as a nightmare when it comes to usability. On older phones these web browser are useless or probably don’t work at all due cross platform or downward device compatibility issues. While developing my project, I have paid special attention to the fact that there is a big audience with rather old or economical versions of mobile phones that do not have sophisticated mobile browsers and they shouldn’t be ignored.

Brief History of Mobile Internet

Few years before when cellphones were introduce with internet access technology they begin to use WAP as a combination of web standards that consisted of WML as its markup and some protocols like WTL and WTPS, to serve it. WML is based on XML and is widely accepted, despite the fact that it is to some extent out fashioned and it is not yet deprecated. So we should not ignore the importance of this technology being used in mole middle standard or cheaper mobile phones and should continue to code web applications that can mutually serve newer and alder mobile phones equally and smoothly.

WAP than evolved in to WAP 2.0 that adopted the implementation of XHTML Basic/MP along with the common TCP/IP and HTTP protocols to establish communication. XHTML-MP is also act very similar to XHTML in rendering with some additional features introduced specifically for Mobile Phones.

The initial version of WAP lacks the styling options when it comes to mobile websites but with evolution of WAP2.0 this problem was solved. WAP 2.0 introduced Wireless CSS (WCSS) which is a smaller version of CSS2.1 that opened a world of design and style to XHTML-MP. It is very similar but compact version to CSS 2.1as some attributes are not included to make a rather simple interface that is widely accepted among multiple browser environments. It surely doesn’t work with WAP 1.0.

Strategy for Web Application Design

SMS Meeting Manager is not just another web application that is made for iPhone or Android phones only to show a web presence or target only a certain area of audience. It is also an idea and process to develop a web application that fits most mobile devices rather than the latest and most sophisticated one. Michel asks very important questions regarding the purpose, use and audience for a website.

“Why you need a mobile site? Are you really offering something useful for a mobile user? Do you offer a specific service? Do you help a task?”

(Michel 2009)

During this project, it is cautiously asked examined as if what is the goal of application and why should it be on mobile. All options for available technologies and their limitations in planning an interaction design are also considered carefully. Significant time is spent in researching if what kind of audience is targeted and what handsets they use.

SMS Meeting Manager is a sober application that has a clear purpose and is a way forward both in mobile phones and meeting management software domains. Every option is necessarily consider in getting rid of all that is useless or inappropriate for this web applications in running over specific mobile devices. Heavy graphics, pages full of pictures as well as unnecessary and unintelligent use of form controls is also minimised.

Simplicity & Usefulness:

Architecturally, SMS Meeting Manager is designed and kept to be a simple but useful application, by minimising the amount of graphic content and by only providing functionalities that are necessarily needed to accomplish a job in arranging, requesting, adding, deleting or amending a meeting in a simple and easy way. Despite the pages are easy to load and do not test much of user patience over a WAP or internet enabled phones, User clicks are also minimised by providing a simplified main menu that offers a significant ease of simplicity in page navigation. Pages and links are well labelled and link levels are carefully categorised knowing its view on every available platform or browser.

Screen Size & Resolution:

There are quite a few things to keep in mind before developing a web application for mobile phones. And one of the most important is to screen size as they vary based on width, height and resolution in dot per inch (dpi). Hight is not a big issue as user can scroll down or up easily using navigation control. What adds to the problem is the width and Mobile websites must avoid wider looking websites. The best practice would be to use width as percentage rather than pixels that can create a fluid layout for the website to expand or decrease width its width according to screen measurements. It’s always a better approach for using fluid layout in designing and ordering content of a web application, mainly for the older mobile phone screens that are mostly portrait. It will significantly help extend viewing experience to iPhones or other devices with similar 90°orientation feature without any problem. It can be decide if how the information can be displayed and how the text can be broken in to many smaller chunks. Navigating menus is bit of a discomfit using multi-touch devices and surely is not les challenging using phones with a limited touch pad. Therefore navigation menus should be carefully considered as they should not increase in length or width out of screen size. Following is a graph conducted by Zambonini that clearly mentions 3 of the most used screen resolutions between year 2005 and 2008.

(Zambonini, D. 2009)

Navigation Menus & Links:

An excellent idea is to use lists not exceeding a number of 10 links per page adding the access keys. Adding access key may not be helpful using multisource devices. Links must be small and shouldn’t be multi levelled as they wouldn’t show properly on smaller screens. It’s always a better approach to use links for “Next” section and “Back” to previous page and if the user is lost in the menu its better provide a “Home” link to escape the menu where ever needed. These links must be added to the bottom of pages for ease of navigation as user will not have to scroll back to the top of page to move to next or previous section.

Two of the other biggest limitations of mobile devices are bandwidth and resources. It is wise to avoid use of objects and JavaScript when ever possible as they are not supported on older versions of phones and even for the new versions they consume huge amount of battery power due to memory usage and the processing speed required for them.

Web Pages Design & Size:

When it comes to the page size it is advisable to not exceed from 10kb to 25kb for the sake of feasibility relating old and basic mobile devices, where as some middleclass mobile phones can work very well with 50kb, 100kb for some touchphones and up to 300kb for latest smart phones. It’s always better to keep the page size as low as possible to facilitate user with fast browsing options depending on the limitations and quality of his network connection. Another way to help user with page loading time is by adding “Caching” in to the pages of web application. It can significantly avoid common pages to be downloaded over and over again. Caching can be controlled by adding the following string in the web pages of the application.

<meta http-equiv="Cache-Control" content="max-age=300"/>

Images & Graphics:

It is also a always a good approach to limit the use of images because they add extra weight to the page as well as it is difficult to decide what size may be suitable for most mobile phone screens. If it is really necessary the safest way is to stick to the minimum size that is supposedly 120px wide. Using the bigger image in your website and than resizing within the website using image float may not be a good practice for mobile applications as the browser will anyway download the full picture that will significantly slow down the browsing speed. What if the image doesn’t load, or is not supported by a phone, It’s always advisable to use “alt text” while using images in website.

Fonts & Colours Schemes:

When styling fonts, it is suggested to use sizes in “small, medium or large” rather than in pixels because that’s a generic way to help device decide itself for what font is suitable for it. It is always wise to use a suitable colour scheme for the fonts in contrast to the background colour for the proper viewing. Using basic colour schemes via colour names or numeric names is always a best approach for mobile web applications. Navigation menus or links should be clearly distinctive from the other text.

Web Page Rendering:

Zambonini talks about one of important rules for proper rendering of web application on mobile devices is to use the correct doctype (XHTML MP), MIME Type (application/html+xml) and character encoding (utf-8). Following is the example he devise in his article.

<?xml version="1.0" encoding="UTF-8" ?>

<!DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN"

"http://www.wapforum.org/DTD/xhtml-mobile10.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<title>Site Name</title>

<meta http-equiv="content-type" content="application/xhtml+xml" />

<meta http-equiv="cache-control" content="max-age=300" />

<link rel="stylesheet" type="text/css" href="style.css"/>

</head>

It is also discussed in the article that a webpage should be built in semantic way based on how the body of the page is structured and what’s loading first. It is an awful practice to use tables and frames on WebPages meant for Mobile viewing where as a good practice is to limit links to the external WebPages, evade popups and validate the markup.

Styling Web Pages:

Above sections neatly discuss different options to create websites that are both suitable for desktop or handheld devices from basic to the latest versions. Where as in an other scenarios the intention is to make a well styled and graphic website for desktop machines using pictures and controls along with other features but if viewed on a mobile device that should be able to drop off all the unnecessary graphics and content which can hinder in smooth mobile viewing or can cause the user navigation to be a complicated.

Zambonini further advise to distinguish a Mobile website from a desktop version by using another advance styling approach called Cascading Style Sheets (CSS). Different style sheets can be designed for Mobile or desktop version and can be referenced with in the same page. Below is a typical example for the case described:

<link href="screen.css" rel="stylesheet" type="text/css"

media="screen" />

<link href="mobile.css" rel="stylesheet" type="text/css"

media="handheld" />

Unique stylesheet can be created by adding specific styles.

@media handheld {#image1 {display: none}}

In the example above we decide not to display the image with that has a media identification set to “handheld” if intention is to adapt a website designed for desktop.

The same techniques can be adopted to address a specific device based on their screen resolution such as:

@media only screen and (max-device-width: 480px) {}

User Security:

A sufficient amount of security is involved to insure user privacy. The main page has a user registration page users can set their login and password to secure their account. A standard for choosing six character passwords is adopted. User should be allowed to set a longer password up to 30 for a better security. Users should additionally be also allowed to login once to change their user profile including their user login email, mobile number and passwords etc. by adding this feature If mobile device is lost user can access the web account using any other phone or desktop to access their account and change their user name and password. Changing username and passwords will surely not effect their meeting commitments as all the operations are being regardless of user emails and phone numbers and generally via their login and other shareable professional profiles such as Profession, Industry, Country, Name etc.

Chapter 3: Research Analysis of Existing Meeting Booking Systems:

Following Systems have been evaluated and their ideas are appreciated before perusing the development for SMS Mobile Manager.

- Diarised:

Claims: “Enter the details of your proposed meeting into Diarised, including the meeting invitees and the possible times and dates for the meeting. Diarised sends out emails to all invitees. The invitees choose the times that suit them best. Once the invitees have chosen their preferred meeting dates. Diarised will give you a summary of the best dates for you to choose from. All meeting invitees will be sent an email confirming the chosen date and time.”

Link: http://www.diarised.com

- When is good:

Claims: “An easy way to find out when everyone is free for your next meeting or event. Click the grid for all the times that are good for you - you get a link to email to your invitees. They see your proposed times and click on when they are free. You visit your results page and see when everyone can do. No sign-up form. No password to choose. No fuss at all.”

Link: http://www.whenisgood.net

- Doodle:

Claims: “Schedule an event such as a board meeting, business lunch, conference call, family reunion, film night, or any other group event.”

Link: http://www.doodle.com

- MeetingWithApproval:

Claims: “Arrange a meeting or event. Work out which day is good for everyone and keep track of who is coming. Access anywhere, Brandable, Iphone Compatible and auto save address book.”

Link: http://meetwithapproval.com

- Jiffle:

Claims: “Jiffle™ makes scheduling appointments and meetings quick and simple. Reduce the hassle of coordinating meetings, Selectively and securely share your online 'Available' calendar, Eliminate the back and forth of emails and phone tag to schedule appointments, Synchronize with MS Outlook, Google Calendar or use our Jiffle Calendar, Automatically Cc others on all meeting requests and confirmations, Use Jiffle to schedule Webex Meetings”

Link: http://www.jifflenow.com

- MEET-O-MATIC:

Claims: “Select possible dates, press 'Book now!', Email participants, Monitor progress.”

Link: http://www.meetomatic.com

- Presdo:

Claims: “Create an invitation-only network around your event for attendees and exhibitors containing rich profiles created from LinkedIn and registration information, Attendees use Presdo Match to discover contacts of interest to target their networking, They can communicate securely, make meeting requests, and schedule one-on-one meetings easily.”

Link: http://www.presdo.com

- Appointment Manager:

Claims: “Add an activity for any day, for any contact person. Easy to modify or reschedule an existing appointment. Easily navigate by date to view appointments. It comes with a Today Kind of Interface which lists the appointments for the next 7 days. User friendly interface

Export to HTML and Word Format”

Problems Encountered in Evaluation:

Following problems were encountered while evaluating already existing online Meeting management systems:

- Few of these online companies provide free trial or demo versions of their product but the full version is not offered unless the product is fully purchased.

- Due to the reason that most trial and demos do not provide full view of the product including system and customer view, it was hard to evaluate certain applications completely.

- Most of these desktop versions of online meeting and appointment systems are focused for bigger businesses and not for a small business requiring a yearly fee and or subscriptions.

Observation & Findings:

A verity of complex yet sophisticated off-the-shelf software applications are available and are widely used to establish such communications for meeting management & booking using audio, video or text messaging. There are many disadvantages of using such applications:

- Despite the fact that different web versions of Meeting and appointment management system are available in the market, there are hardly any meeting management applications made specific to mobile phones, especially covering all major makes and modals.

- Some of the meeting management Apps for Mobile phones are just the other meeting organisers that have no connectivity to the outside world or are not part of any meeting booking and request systems.

- These meeting management software applications are for general use to fit requirements for all kind of businesses thus carry complex setups and functionalities that will hardly ever or never be used by its users.

-Critical personal details such as contact number, home address, work address, email id and employment details etc are shared willingly or innocently while communicating, setting or requesting these meetings, events and venues. Such information can be mishandled and can act as a key access to participant’s personal life, if in wrong hands. Consider a scenario with a celebrity, news reporter, bureaucrat, scientist, doctor, software developer or a professor, who just wants to share his/her professional services rather than access to personal life and data.

- Such software applications either need Installation setup or must be synchronised with other desktop computers to keep all the details updated and in order making it hard to use these applications over Mobile phones unlike their desktop counterparts especially when you are abroad on a business trip or simply on holidays.

- These meeting management applications are mostly installed on mobile phones and host all the important data and meeting schedules on the mobile device itself. User of these devices are always vulnerable to loose this important data if mobile phone is lost, stolen, broken, water damaged or the battery is drained out. All the important meetings communications and schedules will be permanently lost.

- Such applications are also resource hungry and need great processing power in Mobile devices. They are not widely supported on all brands of mobile phones especially older versions with monochrome screens.

- In order to communicate and arrange meetings effectively, all the members of an organisation or group must use similar platform or models for their choice of mobile devices. Such a problem can isolate the possible expansion of business especially when dealing with clients who own a different mobile device that does not support these application features.

Justification for SMS Meeting Manager:

Recommendation for SMS Meeting Manager:

It is a web based meeting scheduling and booking system principally designed for mobile phones. It has distinctive advantages over traditional uses and means of meeting management systems such as post, phone call and emails. Despite a long and pain staking research in finding any other online meeting manager application for Mobile phones It has been concluded that SMS Meeting Manager is the only complete meeting management application for mobile devices. We’ll discuss later in later sections the possible future enhancements for the application

Unlike many online and desktop meeting management and booking solutions in the market, SMS Meeting Manager allow celebrities, professors, teachers, doctors, vets, Therapists, dentists, fitness trainers, sales managers, Small to medium sized businesses, clients, individuals or groups to manage their diary by creating their availability slots for other users or businesses to request meetings during these slots all from their mobile phones. Meeting slots can be searched or requested using professional information such as their Name, Company, Country, Sector and Company Position rather than their key personal contact details such as phone number, email or home addresses. Users will be searched and booked without sharing their key contact details.

System is supposed to be a client/server application rather than just a Mobile application. It is important to host all the activity online via a web server knowing the immense importance of events or venues. In case of device disaster such as damaged, lost, stolen, broken, water damaged or power drained mobile phone, user can quickly access the system via a web browser. User can also go online via any other WAP enabled mobile phone that has an active SIM card number, to update his/her contact information under profile link before continuing the usual business back again.

Meeting request and grant process is pushed via email and SMS gateway and a internet/WAP enabled phone for sending and receiving of SMS and email requests/alerts regardless of what ever the make and model of the mobile phone. All that needed is a SIM Card and a WAP enabled mobile phone.

As the system is based on bespoke application software, unlike off the shelf software it can be tailored and embed with in any website or portal to facilitate individual or organisations ongoing business activities. Next chapters will demonstrate the outcomes of my research in to available online meeting managers and will describe all the development and testing process involved in completion of this project.

Chapter 4: System Modelling & Designing

Application Planning & Requirements:

An SMS Meeting Manager is a bespoke group meeting manager that can be tailored or altered to embed with in any existing portal or website to arrange meetings between any high profile personality, Celebrities, Professionals and a common user looking for particular services via that web portal or a any mobile phone.

It has always been difficult to arrange, rearrange and maintain events due to unfortunate events such as VIP’s get stuck in a traffic jam, flight delays or may forget the time of meeting at all due to workload, business, domestic or personal issues. Usual rearrangement or maintenance methods are to call, text or email to the administration, for their late arrivals and than the administration or the absentee will have to inform every one of the new meeting schedule, with little or wider delay for the meeting to all these people. The organiser will also have to access the vital organisational staff database, to reschedule meetings again. This open access to important personal database of organisational members and staff can leads to functional venerability to fraud and mishandling or a breach to organisational policy under data protection law.

Requirement Specifications

Following components and their functionalities are to be attempted in SMS Meeting Manager Application.

1. Shared Functionality before Login:

a. User Login: This page will request Username as email address, Password and a Login button to navigate towards home page. A redirect to login page will occur in case of incorrect login or password. Login page will also include to links:

i. “Register” will navigate to new user registration page.

ii. “Download VIP Diary App” for smart phone diary organiser interface.

b. User Registration: This page will show general edit boxes requesting First Name, Last Name, Email, Password, Web, Company and Mobile. Mobile number and emails are being taken to be used by system for sending and receiving automatic SMS and email alerts and will be hidden from other application users or meeting requisites to protect their privacy. Link to Next page will request Country Name, Industry and Position using List boxes once the registration is complete user is redirected to Login Page.

2. Shared Functionality After Login:

a. Home Page: This page after login will show a main navigation menu Links to Diary, Profile, Request Meeting, Manage Availability, Search and Logout pages.

b. Diary Page: This page will provide an editable view of all the meeting venue, event times and list of attendees against assigned timeslots. VIP can edit the events at this page. Note: This must be done under sever circumstances only, SMS usage will be doubled. Due to usual request procedure along with additional SMS containing comments.

c. Profile Page: This page will provide an editable view of User Registration Page. Logged in user can individually amend any of his/her personal details including First Name, Surname, Email, Password, Web, Mobile, Country, Company, Position and Industry.

d. Request Meeting: This page will include links to individual pages in order to search and request meetings to listed VIP’s using either search by Name, Company, Country, Sector, Company Position criteria. Every found result will have a link “Book a meeting”. Note: At this point user can not see other users or VIP’s contact phone or email and are put on to use SMS Meeting Manager to request meetings rather than calling or sending emails directly for security reasons.

e. Manage Availability: This Page will navigate to a submenu of further two links:

i. Add Availability: This Page will help user or VIP to setup her availability slots for certain dates and day times for other users to request meetings under any of the available timeslots. At this point it doesn’t matter how many slots a user or VIP sets up as meeting or event requests can be accepted or rejected by VIP based on day to day schedule.

ii. Update Availability: This page will allow user to select and delete any unassigned timeslots that were set up via Add Availability page.

f. Search Page: This page will include links to individual pages in order to search and request meetings to listed VIP’s using either search by Name, Company, Country, Sector, Company Position criteria. A Back link is also included in order to return to previous Page. Note: At this point user can not see other users or VIP’s contact phone or email and are put on to use SMS Meeting Manager to request meetings rather than calling or sending emails directly for security reasons.

3. Meeting/Venue Organiser (VIP):

a. Calendar function is to be added in the diary page using web or WAP browser.

i. Time will be set by the VIP to send SMS and email message reminders automatically 15, 30, 45, 60 or 90 minuets before the event beings.

ii. VIP will also set the checkbox on or off to add or block the facility in meeting request page for requisites to add comments while requesting a meeting: There will be two SMS messages sent rather than one.

• First SMS will including the two meeting request links to accept or reject meeting.

• The second SMS will carry the other half of the message carrying the appended comments.

b. At the time of setting up the Diary events following two functions to be added.

i. VIP should be able to add or edit event times and designate places as well.

ii. VIP will also set the checkbox on or off to add or edit important note of another 160 character set.

4. J2ME Mobile Diary Client:

a. This mobile application is a J2ME client that can be downloaded from the website link on Login page. It will enable following functions via visual interface.

b. Login and Password to diary database (without opening browser).

c. Provide real-time screen view of upcoming diary events and a system alert (SMS, Ring or Popup) based on 15, 30, 45, 60 or 90 min before event.

d. Add or Edit Diary function to add new availabilities or events same as web view but using system calendar.

e. When any event or venue is amended using system calendar an SMS will automatically be sent to meeting requisites again informing about the necessary changes giving them a chance to accept or reject the new timings according to their availabilities.

Presentation & Analysis (Data Modal, ERD)

Chapter 5: Application Development:

Chapter 5: System Coding & Algorithms

Chapter 6: Summary, Conclusion (Test result analysis, Problems, Future enhancements)

Chapter 7: Problems & Issues

Chapter 8: Future enhancements & recommendations for Improvement.

Chapter 9: List of References:

Following are the references available for the overall inspiration and resolution of proposed project.

Zambonini, D. (May 2009), “Mobile: Graphs and Statistics”, Mobile the Business case, BoxUK, http://www.boxuk.com/blog/mobile-the-business-case

Michel (October 2009), “Create a Mobile Site”, Designer Break, http://eng.designerbreak.com/2009/tutorial/create-a-mobile-site/

Snell, S. (January 2009), “Mobile Web Design Trends For 2009”, Smashing Magazine, http://www.smashingmagazine.com/2009/01/13/mobile-web-design-trends-2009/

Rabin,J. and McCathieNevile, C. (July 2008), "Mobile Web Best Practices 1.0", Basic Guidelines, W3C Recommendation, http://www.w3.org/TR/mobile-bp/

- Churcher, C. (2007), “Beginning Database Design From Novice to Professional”, Apress: USA.

- Clay Richardson, W. (2004), “Professional Portal Development with Open Source Tools: Java™ Portlet API, Lucene, James, Slide”, Wiley Publishing: Indianapolis.

- Elliott, G. and Phillips, N. (2004), “Mobile Commerce and Wireless Computing Systems”, Pearson Education Limited: England.

- Gibson , Jerry D. (1999), “The Mobile Communications Handbook, Second Edition”, University of California: Santa Barbara.

- Le Bodic, G. (2005), "MOBILE MESSAGING TECHNOLOGIES AND SERVICES: SMS, EMS and MMS" Second Edition, John Wiley & Sons Ltd: England.

- Myatt, A. (2008), “Pro NetBeans™ IDE 6 Rich Client Platform Edition”, Apress: USA.

- Parnas, D.L. and Clements, P.C. (February 1986), “A Rational Design Process: How and Why to fake It,”, IEEE Transactions on Software Engineering, vol. SE-12, Number 2, pp. 251-257.

- Retford, B. and Schwartz, J. (2007), "How to Build an SMS Service", O'Reilly: Sebastopol.

Print Email Download Reference This Send to Kindle Reddit This

Share This Essay

To share this essay on Reddit, Facebook, Twitter, or Google+ just click on the buttons below:

Request Removal

If you are the original writer of this essay and no longer wish to have the essay published on the UK Essays website then please click on the link below to request removal:

Request the removal of this essay.


More from UK Essays

Doing your resits? We can help!