1. introduction
1.1 Writing
This document provides plans to develop the project's application conversion gateway, describe the starting point, target, and explain the general scale and progress of the project.
1.2 project background
no
1.3 definition
no.
1.4 Reference
no
2. Project Overview
2.1 Work content
In today's web application, the most successful application should be HTML, which is a well-deserved killer application in the Internet. Most of the information on the network is published by HTML, and a wide variety of technologies are also expanded around HTML, such as JSP, ASP, and more.
And mobile phones, as the most compelling embedded mobile development in the past two years, of course, will not give up this resource using the Internet. So some browsers developed for mobile phones or ported to mobile platforms. In this field, a more famous is an Opera browser, such as NOKIA9500, is embedded. At recent recently, Firefox has opened a territory on the desktop PC, Mozilla has also launched mini browser project minimo, which is competing with OPEAR.
However, in this special environment, for example, the display area is smaller, but the button is too small, most of which do not have a coordinate positioning device (only some touch screens to solve), the current HTML page is still not suitable for direct display.
First, most of the HTML pages are suitable for 800 * 600, which is only used for mobile phone small screens, only using scroll bars can be displayed. This may be the main factor for restricting the development of mobile browsers. However, this problem Opera has recently launched Small-Screen Rendering (SSR) technology. The technology adapts to the small screen of the mobile device by changing the web page structure, so there is no need to scroll in the horizontal direction, but it believes that its effect will be very limited. After all, it is not every mobile phone can have a Nokia9500. 640x200 pixels large screen, and in a small screen, such as 200 * 200, no matter how change, it is not good to layout.
Second, there are many other additional elements in the HTML page, the most common, such as flash, as well as some scripting languages, such as JavaScript, and so on, these elements are in the mobile phone, and they cannot be displayed in the short term (current mobile phone) Software that has already appeared Flash, Opera supports JavaScript and VBScript to a certain extent. And there are many information that are useless to users, such as advertisements, such as advertising, which takes a lot of space, and for the valuable display area of mobile phones, they should not appear.
For most users, more practical, but also to access the WML web page in the most widely used, or using GPRS. This limits the access to many resources of the Internet. Because not all pages have corresponding WML pages, and users can only wait for web maintainers to develop corresponding XMLs, one is very passive for users. .
So we envision, if a conversion gateway can be established, this descriptive language of HTML is converted, keeping its necessary semantic information constant, and extracts content that requires users to interact (such as: form), and Some formats that are suitable for mobile phones are transferred to your phone without changing your mobile phone hardware and changing web pages, while making your phone will access the web resources. And this conversion should be customizable, that is, the user can choose which information is reserved, which information is removed, so that users have more power to choose, or customize web services. In this regard, some attempts have already appeared, http: //www.rss2wap.com has implemented RSS to WAP, which is relative because it is to convert an XML to a mobile phone. It is more simple. However, there are also some parts that can be borrowed, such as the application of XML format in this conversion.
The project also tries to extend this service to other ways, such as SMS, although it is expected to be not implemented in this release, but should be considered, so that the conversion service has a good external interface, which should be separated from a specific connection. Become a relatively independent server.
At the same time, a set of auxiliary tools is required. He should be able to configure the conversion service itself through some way, which can determine which page is converted. Which part in this page needs to be converted, and which part needs to delete (such as advertising). To do this, you need to customize a set of description languages, which can use XML format to facilitate analysis management. This auxiliary tool is preferably a graphical interface that allows a user that does not understand the HTML format can customize the conversion service.
In order to connect the phone to the conversion server, a server used to handle the phone, ie the mobile phone connection server, this server will cooperate with the application conversion server to achieve the entire business, and he will isolate the conversion server as an outside.
At the same time, it is supported, and a client program is also required to be used as the terminal of this conversion service.
2.2 Conditions and Restrictions
The project itself is a set of application conversion systems, which will include two parts of the server side and client. During the development process, you can use the developer's own PC as a temporary operating environment of the server, while the mobile phone is first using Sun's Standard Simulator as the development platform, and then requires a real machine to test, which is not available.
2.3 products
2.3.1
program
Application Conversion Server Program: Application Conversion Server is the core part of the project, its functionality to implement HTML to mobile phone display format conversion function. Mobile phone connection server: Connecting the server to handle various connection transactions, responsible for direct communication with your mobile phone. Application Conversion Configuration: Users can customize the conversion service through this user. Mobile client program: System client.
2.3.2
Documentation
Develop documents, control project progress, and conduct preliminary design and demand analysis. Realize documentation, describe the specific implementation of the project. Each otherwise manual, the function, use of various parts, method, error handling, etc. of the achievements, so that the end user can use the system through the instruction manual.
2.4 Operating Environment
It is expected that the environment is a Java environment, JVM is
1.5.0
. The server-side runs the hardware platform to be determined. Database is to be determined. The mobile phone running environment is MIDP 2.0, and mobile phones that support MIDP2.0 should be used normally. If necessary, if necessary, you can develop products for a factory SDK, but will try our best to use standard APIs.
2.5 service
Includes two servers configuration, debug, test. And the configuration, debugging, testing of the mobile phone.
2.6 Acceptance Standard
The final system should be completed, and the specific requirements are given by the demand analysis document. 3. Implementation Plan
3.1 Task Decomposition
The project will be divided into four parts:
The first part: Analyze the overall structure of the system, formulates part of the data structure, and develops a preliminary server-client interaction agreement. The overall design requirements of the system are designated and related to the relevant UML maps. Note that the design is designed for the overall architecture and does not design the specific implementation.
Part II: Fast iterative development, each iteration will release an executable version, and based on this version as the next set of demand features and development targets, the first version iterative development implementation system core function, That is, the files of the HTML format are formatted, and the interactions such as forms and the like are extracted. It is expected that the total six iterations are performed, using test drivers, due to few developers, reduce document requirements, each iteration requires only test cases and test instructions. Each iterative average duration is 2 weeks, and the progress will be reported at the end and the next version iteration is started.
Part III: Pass the test personnel to perform overall testing, while developing instructions, and organizing documents.
Part IV: Real deployment, and continue testing during deployment, and design the next version of the work.
3.2 progress
The first part is expected to take a workload of one month. The second part is expected to be three months, this process is due to few developers, and the testing written and code construct cannot be conducted in parallel, so progress is slow. At the same time, I think about the interference (exam) of other things in July, and the progress will be delayed. The third part is expected to take a month. The fourth part cannot be expected.
3.3 budget
no
3.4 Key questions
For now, the configuration problem of the mobile phone is a difficult point, that is, what kind of way the user is customized to the service. It is the user through the PC to connect to the server, or the user directly uses the mobile phone to configure, no matter which program is implemented. Very complicated. In addition, the custom part of the conversion service is taken to take the drag and drop configuration of the graphical interface. Since the experience has not been developed similar programs before, this project will be in the exploration state in this regard, which may become the largest in the project. difficulty.
4. People's organization and division of labor
5. No time limit
6. Special plan
No
