The following report will give an introduction to WAP, its programming model, the architecture, services and peculiarities in comparison to the World Wide Web. WAP's features are evaluated and especially security, usability, performance and quality-of-service issues are reviewed. Based upon the WAP introduction and its major findings, an analysis and design has been made for a concrete WAP application. This application serves as an information system for transportation systems and allows users to be kept up-to-date on actual maintenance, breakdowns and malfunctions in a transportation network. Functional and non-functional requirements, use-cases, activities, the database scheme, deployment and realization requirements of the proposed project will be discussed. Finally, the report will conclude with an evaluation of the project and a discussion about possible extensions and further work.
Table of Contents
1 Introduction
2 WAP Review
2.1 WAP Programming Model
2.2 WAP Architecture
2.2.1 WAP Protocol Stack
2.2.2 Protocol Framework
2.2.3 Security
2.3 Performance
2.4 Usability
2.5 WAP 1.x
3 Project
3.1 Procedure
3.2 Requirement Analysis
3.2.1 Short Description
3.2.2 Functional Requirements
3.2.3 Non-Functional Requirements
3.2.4 Use-Cases
3.3 Architecture
3.3.1 Deployment Diagram
3.4 Persistent Data Storage
3.4.1 Entity Relationship Diagram
3.5 Activities
3.5.1 Standard User Activities
3.5.2 Service Employee Activities
3.5.3 Administrator User Activities
3.6 Realization
3.7 Results
4 Evaluation
5 Discussion and Further Work
6 Conclusion
Objectives and Topics
The primary objective of this project is the conceptual design and architectural planning of an information system for underground transportation networks, utilizing Wireless Application Protocol (WAP) technology. The research addresses how mobile devices can be leveraged to provide users with real-time updates on scheduled maintenance and unexpected service disruptions, ensuring high usability and performance despite the constraints of mobile environments.
- WAP architecture, protocol stacks, and security models.
- Functional and non-functional requirements for mobile information systems.
- System design using UML diagrams, including use-case, activity, and deployment diagrams.
- Database design through Entity-Relationship modeling for robust data storage.
- Evaluation of mobile usability and system scalability for mass transportation.
Excerpt from the Book
3.2.2 Functional Requirements
Unregistered User Requirements
• registration or login
• request tube line status information
• call customer service
additional Standard User Requirements
• manage underground line subscriptions
• manage custom route subscriptions
• receive push-back status update messages
additional Service Employee Requirements
• administer underground lines schedule
• report of breakdowns, maintenance and delays
additional Administrator User Requirements
• administer the network of underground lines and stations
• administer registered users and permissions
Summary of Chapters
1 Introduction: This chapter introduces WAP technology and the research aim to develop a mobile-based information system for transportation networks.
2 WAP Review: This section covers the theoretical foundations, including programming models, protocol stacks, architecture, performance considerations, and usability aspects of WAP.
3 Project: This chapter details the practical design of the information system, covering requirement analysis, system architecture, database modeling, and activity flows for various user roles.
4 Evaluation: This chapter evaluates the proposed system design against existing implementations, such as the Travel for London mobile services, to identify improvements.
5 Discussion and Further Work: This chapter reflects on the results and proposes future directions, such as social-centric networking and the convergence of WAP with broader Internet standards.
6 Conclusion: The final chapter summarizes the project's findings regarding the feasibility and design requirements for a successful mobile transportation information system.
Keywords
WAP, Wireless Application Protocol, Mobile Information System, Underground Transportation, System Architecture, UML, Use-Case Diagram, Entity-Relationship Model, Mobile Usability, XHTML Mobile Profile, Data Storage, WAP Gateway, Network Maintenance, Service Disruption, User Management
Frequently Asked Questions
What is the core focus of this research project?
The project focuses on designing an information system for underground railway networks that provides users with real-time updates via mobile devices using WAP technology.
Which specific areas are covered in the theoretical part?
The theoretical section addresses WAP programming models, protocol stacks, security mechanisms, and the constraints of mobile devices regarding screen size and bandwidth.
What is the primary goal of the proposed system?
The primary goal is to keep users informed about scheduled maintenance and unexpected service breakdowns in real-time, thereby improving the overall travel experience.
What methodology was applied to design the system?
The system was designed using the Rational Software Development Process, utilizing UML for system modeling (use-case, activity, and deployment diagrams) and Entity-Relationship diagrams for database design.
What does the main body of the report contain?
The main body includes a comprehensive WAP review, a detailed requirement analysis (functional and non-functional), architecture design, data storage modeling, and workflow activity diagrams.
Which keywords best describe this study?
Key terms include WAP, Mobile Information System, Transportation Network, System Architecture, Mobile Usability, and UML design.
How does this system differ from existing solutions like Travel for London (TfL)?
Unlike some existing services that rely on SMS notifications, the proposed system provides more granular control, such as specific line subscriptions and user-defined alerts, which can be managed through a structured mobile interface.
Why was the XHTML Mobile Profile chosen for this implementation?
The XHTML Mobile Profile was selected because it is a modern, widely accepted standard that allows web developers to use the same markup language for both standard Web and WAP applications.
How is the user security managed within the system?
Security is addressed by separating user and administrative interfaces, ensuring that administrative tasks require distinct authentication, and maintaining encrypted data transfers where necessary.
What is the conclusion regarding the future of WAP?
The report suggests that while mobile technology is evolving rapidly, specialized mobile interfaces remain necessary for optimal usability until screen sizes and mobile browsing capabilities reach a new standard of maturity.
- Quote paper
- Karl Tschetschonig (Author), 2008, Underground Information System, Munich, GRIN Verlag, https://www.grin.com/document/185045
