• 沒有找到結果。

3.4 Scenario Demonstrations

3.4.2 Scenario Two

Figure 29. The end user steps of the transaction (screenshots)

3.4.2 Scenario Two

The second scenario is similar to the first with one difference. We demonstrate the integration of the Multimedia Visual Authoring Tool with the proposed system to create customized templates. In this scenario, we envision the following situation:

The system administrators and campus officers decided to add additional templates to facilitate

more choice. They open the Multimedia Visual Authoring Tool to design a few templates and import

them into the Template Management System. A campus officer on the field spots a speeding car. He

takes out his device, attaches his camera and records a video, takes a snapshot and makes a voice

recording. In addition, he writes down some comments about the violation. Satisfied, he decides to

see what other templates are available, so he connects to the server and previews some of the

templates. He selects a template, connects to the server, and transfers the files. He receives confirmation once his files have been uploaded. Because the user is a registered vehicle owner, the campus officer receives his contact details and violation number for reference, at the same time, the server automatically e-mails the vehicle’s owner to inform him or her that their vehicle is in violation. The owner then views his or her violation on the MobileCampus portal

Figure 30. Scenario Two

Figure 30 outlines this scenario. A detailed description of this transaction is elaborated as follows:

Table 6. The administrator steps of the transaction

Steps High-Level View Low-Level View

Launch the Multimedia Visual Authoring Tool

The campus officer or system administrator launches the

Multimedia Visual Authoring Tool

None

template and saves it saved into a script file that contains information about the template

Export Template Along with other types of exporting facilities, one functionality integrated into the Multimedia Visual Authoring Tool is support for XSLT, the user selects this format for device support

The script file is parsed and translated into XSLT.

The user accesses the Template Management Service

None Import Template The user imports the template into

the template library

The template is copied and stored in the template library

Table 6 (above) describes the administrator process.

Table 7. The first four steps of the transaction

Steps High-Level View Low-Level View

Launch MobileCampus The campus officer launches MobileCampus and accesses the Multimedia Capturing Service

None

Capture an Image The “still image” radio button is selected and the campus officer clicks the “capture” button

The image is stored locally as a JPEG image

Capture Video The “movie” radio button is selected and the campus officer clicks the

“record” button. When the officer has completed recording the video, he clicks the “stop” button. Any adjustments to lighting, brightness and size are made here

Because the current camera API does not support built-in video compression, images are saved as JPEGS at a rate of five images per second. Images are compressed and packed into ZIP format in the background

Record Voice The officer uses the voice recorder to record voice

The voice recording is stored locally as a wave file and

compressed and packed into ZIP format in the background

Table 7 and Table 8 describe the first five steps of the transaction which are both very similar to the first scenario. Figure 31 and Figure 32 illustrate these steps from a high level viewpoint.

Figure 31. The first four steps of the transaction (screenshots)

Table 8. The fifth step of the transaction

Steps High-Level View Low-Level View

Enter Information The officer enters the necessary information such as the time, location, nature of violation, comments and so forth

This information is stored locally as text

Figure 32. The fifth step of the transaction (screenshots)

Table 9. Steps six to nine of the transaction

Steps High-Level View Low-Level View

Download a New Template

The officer connects to the server to download new templates

The File Transfer Service is called which connects to the Server to check for new

downloaded and stored on the device

Preview Template The officer selects a template and previews it using the built-in web browser Transfer Files Once the officer has completed

acquiring the multimedia and is satisfied with his template selection, he connects to the server. The file transferring process is automatic

The client connects to the server via 802.11b/g using the File Transfer Protocol (FTP). The user is first authenticated and verified. If the verification is successful, a unique key is generated for the transaction.

All acquired compressed multimedia information is then transferred to the server. During this time, information about the transaction is stored in XML.

Acquired multimedia files are unpacked and stored on the server in the media library (via the Template Management Service). The server also connects to the vehicle register to check if the owner exists in the database. If the owner exists, an e-mail is generated and sent automatically to the owner

Receive Key and Other Information

When the transaction is complete, the officer will receive confirmation. All information about the owner, details about the transaction and the unique key are sent back to the officer for reference

If queries to the vehicle register are successful, this information is sent back to the officer

Table 9 describes steps six to nine. Figure 33 and Figure 34 illustrate steps six and seven and steps eight and nine respectively.

Figure 33. Steps six and seven of the transaction (screenshots)

Figure 34. Steps eight and nine of the transaction (screenshots)

The end user process is identical to the first scenario. The end user (vehicle owner) steps are described in Table 10 and depicted in Figure 35 respectively.

Table 10. The end user steps of the transaction

Steps High-Level View Low-Level View

Receive E-mail notification

The end user receives an e-mail on his or her pervasive computing device (or desktop PC)

The E-mail Service, when called by the File Transfer Service sends the e-mail to the recipient

Access Portal The end user accesses the MobileCampus portal

The Web Presentation Service loads the portal. Depending on

the device accessing the portal, the Web Presentation Service formats the portal accordingly using CSS and device profiling View Presentation The end user enters the key sent to

him or her via e-mail, and views the presentation

Once the server receives the key, the transformation process and device customization process takes place for presentation to the end user

Figure 35. The end user steps of the transaction (screenshots)

3.5 Summary

MobileCampus can be divided into six services that communicate dependently and independently of one another: The Multimedia Capturing Service, The File Transfer Service, The Template Management Service, The Template Creation Service, The Content Management Service and The Internet Service. This chapter discussed two important processes, the translation process and transformation process that facilitate the integration of the Multimedia Visual Authoring Tool and the delivery of presentations to devices respectively. Two scenarios were constructed to demonstrate the practicability of MobileCampus and support its applicability.

The following chapter presents an analysis and evaluation of the proposed system against the specific criteria set out in Chapter Two.

CHAPTER FOUR

Discussion and Evaluation

4.1 Introduction

The previous chapter discussed the proposed system, MobileCampus, in detail. This chapter presents a discussion and evaluation of the proposed system. We attempt to critically evaluate the system against the specific criteria identified earlier in Chapter Two, particularly addressing the application challenges, the characteristics of mobile users and the limitations imposed by devices as well as how the proposed system contributes towards the vision of pervasive computing and enhances the user experience. Based on this evaluation, some limitations are identified and discussed. This evaluation forms the basis for a discussion and major contributions of the project and opportunities for future work, which is handled in the following chapter.

相關文件