Chapter 5 Software architecture for wearable and mobile system.

Chapter 5Chapter 5

Software architecture for Software architecture for wearable and mobile wearable and mobile

systemsystem

Software architecture for Software architecture for wearable and mobile systemwearable and mobile system

• Software Architecture and Wearable Software Architecture and Wearable ComputingComputing

• A Software Architecture for A Software Architecture for Interactive Wearable SystemsInteractive Wearable Systems

• The Mobile ArchitectureThe Mobile Architecture

Software Architecture and Software Architecture and Wearable ComputingWearable Computing

• Software architecture definitions:Software architecture definitions:– the structure of the components of a the structure of the components of a

program/system, their interrelationships, program/system, their interrelationships, and principles and guidelines governing and principles and guidelines governing their design and evolution over timetheir design and evolution over time

– refer to the coarse-gain structure of a refer to the coarse-gain structure of a software system, it is division into software system, it is division into components and how functionality is components and how functionality is assigned to these components.assigned to these components.

– a coherent set of abstract patterns guiding a coherent set of abstract patterns guiding the design of each aspect of a larger the design of each aspect of a larger software system. software system.


• Rapid prototyping approach has been Rapid prototyping approach has been investigated successfully for a investigated successfully for a wearable computer hardware.wearable computer hardware.

• However, there is no such approach However, there is no such approach ready available for software ready available for software components of a wearable systemcomponents of a wearable system

• With increasing size and complexity, With increasing size and complexity, software will become a critical factor software will become a critical factor in the development of wearable in the development of wearable computers.computers.


• The construction of reliable wearable The construction of reliable wearable systems that satisfy important quality systems that satisfy important quality requirement and evolve gracefully requirement and evolve gracefully requires a requires a design approachdesign approach with the with the following properties:following properties:

1.1. support systematic design variationssupport systematic design variations2.2. support reuse of design and support reuse of design and

software artifactssoftware artifacts3.3. support the early quality assessment support the early quality assessment

of a system designof a system design


1.1. Support systematic design Support systematic design variations:variations:

– this is important for:this is important for:• the construction of successive generations the construction of successive generations

of more advanced wearable computer of more advanced wearable computer systems systems

• the creation of customized solutions for the creation of customized solutions for different application areasdifferent application areas


2.2. Support reuse of design and Support reuse of design and software artifacts:software artifacts:

– standardization and reuse can help to standardization and reuse can help to reduce development time and overall reduce development time and overall costs.costs.


3.3. Support the early quality assessment Support the early quality assessment of a system design:of a system design:

– to avoid costly redesign in a later phase of to avoid costly redesign in a later phase of the developmentthe development

– software engineer should be able to software engineer should be able to predict how the final system will perform predict how the final system will perform in terms of:in terms of:• PerformancePerformance• Resource needsResource needs• ReliabilityReliability• CostCost• or any system aspect that is deemed importantor any system aspect that is deemed important


• Some of the goals of software Some of the goals of software architecture are:architecture are:

1.1. Codification of architectural knowledgeCodification of architectural knowledge• Knowledge codification Knowledge codification the representation

of knowledge such that it can be accessed by each member of an organization.

• Organize and visualize knowledge to be meaningful to searchers.

2.2. Support of higher level reuse through Support of higher level reuse through standardization of design elementsstandardization of design elements


• Some of the goals of software Some of the goals of software architecture are: (cont…)architecture are: (cont…)

3.3. Analysis of software system prior to their Analysis of software system prior to their implementation:implementation:

• includes checking if a system exhibits includes checking if a system exhibits properties are required by the specifications properties are required by the specifications well as selection among Software architecture well as selection among Software architecture promises a principled approach of component-promises a principled approach of component-based development of large scale software based development of large scale software [Garlan & Shaw 1993, Perry & Wolf 1992].[Garlan & Shaw 1993, Perry & Wolf 1992].

Software Architecture for Software Architecture for Interactive Wearable Interactive Wearable

SystemsSystems• The architecture proposed by Fagg, The architecture proposed by Fagg,

A. H. (1998) to support (in a A. H. (1998) to support (in a proactive manner) user interaction proactive manner) user interaction with a wide variety of applications.with a wide variety of applications.

• Refer diagram.Refer diagram.


SystemsSystems


SystemsSystems• Context box:Context box:– collecting together collecting together

various bits of various bits of possibly relevant possibly relevant contextual contextual informationinformation

– Each component of Each component of the context is the context is supplied by a supplied by a separate process separate process (most likely (most likely developed by developed by different different individuals).individuals).


SystemsSystems• Context box:(cont)Context box:(cont)– Different wearable Different wearable

configurations will configurations will make use of various make use of various subsets of these subsets of these modulesmodules

– Even on a single Even on a single wearable, different wearable, different subsets of these subsets of these modules may be modules may be available to provide available to provide context at any one context at any one timetime


SystemsSystems• Producer:Producer:– the sources of the sources of

information that information that may be useful to may be useful to the userthe user

– A.k.a event A.k.a event generatorgenerator

– Event Event the the appearance of a bit appearance of a bit of information.of information.


SystemsSystems• Producer (cont..):Producer (cont..):– Event:Event:

• Some events Some events originate elsewhere, originate elsewhere, others originate others originate from applications from applications executing locally on executing locally on behalf of the userbehalf of the user

• Some events only Some events only indicate the indicate the possibility of a more possibility of a more detailed interaction detailed interaction with the userwith the user


SystemsSystems• Evaluator:Evaluator:– makes context-makes context-

dependent dependent decisions about the decisions about the priority of the priority of the information that is information that is coming into the coming into the systemsystem

– These priority These priority assignments may assignments may change as the change as the current user current user context shiftscontext shifts


SystemsSystems• Presentation Presentation Manager:Manager:• Assess:Assess:

• user's current user's current ability/desire to ability/desire to accept more accept more informationinformation

• the form which that the form which that information may information may take (audio @ visual take (audio @ visual @ both).@ both).

Telematics 2.5G

Voice POTS

WML GPRS

SMS GSM

Database

Firewall

Markup Language

Web Server

NetworkProtocol & Gateway

Mail ServerPSTN Network

Content Application

XML

Application Server

Application Server

GPRS Network

WAP Gateway

SMS Center

Offline Devices

Wireless Devices

The Mobile ArchitectureThe Mobile Architecture


• Devices:Devices:– Support many types Support many types

of wireless and of wireless and mobile devices.mobile devices.

– E.g.: E.g.: WAP phones, WAP phones, smart phones, smart phones, Pocket PCs, Palm Pocket PCs, Palm PDAs, and PDAs, and telematicstelematics

Telematics 2.5G

Voice POTS

WML GPRS

SMS GSM

Database

Firewall

Markup Language

Web Server

Network

Protocol & Gateway

Mail Server

PSTN Network

Content

Application

XML

Application

Server

Application

Server

GPRS Network

WAP Gateway

SMS Center

Offline Devices

Wireless Devices


• Markup language:Markup language:– With various With various

devices came many devices came many different markup different markup languages.languages.

– Each required to Each required to “mark up” or “mark up” or format the pages format the pages for presentation on for presentation on particular devicesparticular devices

Telematics 2.5G

Voice POTS

WML GPRS

SMS GSM

Database

Firewall

Markup Language

Web Server

Network

Protocol & Gateway

Mail Server

PSTN Network

Content

Application

XML

Application

Server

Application

Server

GPRS Network

WAP Gateway

SMS Center

Offline Devices

Wireless Devices


• Protocols (802.11):Protocols (802.11):– Wireless Wireless

networking networking protocols are protocols are needed to:needed to:• exchange exchange

information (in the information (in the form of radio form of radio frequency signals, frequency signals, and so on)and so on)

• deliver and receive deliver and receive messages and page messages and page requests.requests.

Telematics 2.5G

Voice POTS

WML GPRS

SMS GSM

Database

Firewall

Markup Language

Web Server

Network

Protocol & Gateway

Mail Server

PSTN Network

Content

Application

XML

Application

Server

Application

Server

GPRS Network

WAP Gateway

SMS Center

Offline Devices

Wireless Devices


• Network and gateways:Network and gateways:– Different wireless Different wireless

networks both WAN and networks both WAN and LAN, can be set up to LAN, can be set up to support mobile devicessupport mobile devices

– Besides switching Besides switching stations and antennae, stations and antennae, what matters most to what matters most to developers are the many developers are the many gateways and different gateways and different protocols intended for protocols intended for packet switching and packet switching and page rendering, including page rendering, including the support for e-mail, the support for e-mail, short messaging, and short messaging, and voice communications.voice communications.

Telematics 2.5G

Voice POTS

WML GPRS

SMS GSM

Database

Firewall

Markup Language

Web Server

Network

Protocol & Gateway

Mail Server

PSTN Network

Content

Application

XML

Application

Server

Application

Server

GPRS Network

WAP Gateway

SMS Center

Offline Devices

Wireless Devices


• Web and application Web and application servers:servers:– the servers that act the servers that act

as a bridge between as a bridge between intranets, content, intranets, content, web applications, and web applications, and datadata

– Enterprise Enterprise applications and m-applications and m-commerce sites are commerce sites are just two examples of just two examples of what could be hosted what could be hosted there.there.

Telematics 2.5G

Voice POTS

WML GPRS

SMS GSM

Database

Firewall

Markup Language

Web Server

Network

Protocol & Gateway

Mail Server

PSTN Network

Content

Application

XML

Application

Server

Application

Server

GPRS Network

WAP Gateway

SMS Center

Offline Devices

Wireless Devices


• Databases:Databases:– Relational database can Relational database can

be used for storage of be used for storage of enterprise data, as well enterprise data, as well as credit card as credit card informationinformation

– In a mobile In a mobile architecture, you will architecture, you will need the database back need the database back end to support sessions, end to support sessions, personalization, personalization, location-based services location-based services (LBS), and mobile (LBS), and mobile commercecommerce

Telematics 2.5G

Voice POTS

WML GPRS

SMS GSM

Database

Firewall

Markup Language

Web Server

Network

Protocol & Gateway

Mail Server

PSTN Network

Content

Application

XML

Application

Server

Application

Server

GPRS Network

WAP Gateway

SMS Center

Offline Devices

Wireless Devices

The Mobile ArchitectureThe Mobile Architecture• Applications & content:Applications & content:

– E-commerce site and E-commerce site and offline applications are offline applications are just two of many just two of many examples where Web examples where Web solutions can be solutions can be deployed to the wireless deployed to the wireless webweb

– E-commerce web sites E-commerce web sites hosted within the firewall hosted within the firewall can be enable to become can be enable to become mobile commerce sitesmobile commerce sites

– Offline applications that Offline applications that reside in a Palm PDA or a reside in a Palm PDA or a Pocket PC can be Pocket PC can be provisioned, with the provisioned, with the data synchronized and data synchronized and replicated when a replicated when a connection is made to the connection is made to the back-end databases.back-end databases.

Telematics 2.5G

Voice POTS

WML GPRS

SMS GSM

Database

Firewall

Markup Language

Web Server

Network

Protocol & Gateway

Mail Server

PSTN Network

Content

Application

XML

Application

Server

Application

Server

GPRS Network

WAP Gateway

SMS Center

Offline Devices

Wireless Devices


Telematics 2.5G

Voice POTS

WML GPRS

SMS GSM

Database

Firewall

Markup Language

Web Server

NetworkProtocol & Gateway

Mail ServerPSTN Network

Content Application

XML

Application Server

Application Server

GPRS Network

WAP Gateway

SMS Center

Offline Devices

Wireless Devices


• A typical logic flow for a wireless A typical logic flow for a wireless phone using the Wireless Application phone using the Wireless Application Protocol (WAP):Protocol (WAP):1.1. A request for a Wireless Markup Language A request for a Wireless Markup Language

(WML) pages is issued by a WAP phone(WML) pages is issued by a WAP phone

2.2. The request is transported through the air The request is transported through the air interface into the WAP gateway.interface into the WAP gateway.

3.3. The request is translated into the requisite The request is translated into the requisite markup/protocol for the Internet (binary encoding markup/protocol for the Internet (binary encoding and decoding between gateway and server).and decoding between gateway and server).

4.4. The request is then relayed to the web server in The request is then relayed to the web server in accordance with the URL the gateway has accordance with the URL the gateway has resolvedresolved


• A typical logic flow for a wireless A typical logic flow for a wireless phone using the Wireless Application phone using the Wireless Application Protocol (WAP): (cont…)Protocol (WAP): (cont…)5.5. The application server, upon receiving the The application server, upon receiving the

request through the web server, is now running request through the web server, is now running the web application by retrieving and executing the web application by retrieving and executing the server site pagethe server site page

6.6. TThe data store, in the form of a RDBMS, will he data store, in the form of a RDBMS, will provide dynamic data, and the page is provide dynamic data, and the page is constructed in the right formatconstructed in the right format

7.7. Through the Internet, a markup page is then Through the Internet, a markup page is then delivered to the gateway, which in turn relays delivered to the gateway, which in turn relays back to the device, using the same protocol and back to the device, using the same protocol and markup as before.markup as before.

Date post:	01-Jan-2016
Category:	Documents
Upload:	felicity-gibson
View:	218 times
Download:	2 times

Chapter 5 Software architecture for wearable and mobile system.

Documents