Introduction To Model-Based User Interfaces

1/12/2017 IntroductiontoModelBasedUserInterfaces
IntroductiontoModelBasedUserInterfaces
W3CWorkingGroupNote07January2014
Thisversion:
http://www.w3.org/TR/2014/NOTEmbuiintro20140107/
mbui
Latestpublishedversion:
http://www.w3.org/TR/mbuiintro/
mbui
Latesteditor'sdraft:
http://www.w3.org/2011/mbui/drafts/mbuiintro/
mbui mbui
Editors:
GerritMeixner(HeilbronnUniversity)
GalleCalvary,JolleCoutaz(UniversityofGrenoble)
Copyright2013W3C(MIT,ERCIM,Keio,Beihang),AllRightsReserved.W3Cliability,trademarkanddocumentuserulesapply.
Abstract
ThisisanintroductiontoModelBasedUserInterfacescoveringthebenefitsandshortcomingsofthemodel
basedapproach,acollectionofusecases,andterminology.
StatusofThisDocument
Thissectiondescribesthestatusofthisdocumentatthetimeofitspublication.Otherdocumentsmay
supersedethisdocument.AlistofcurrentW3Cpublicationsandthelatestrevisionofthistechnicalreport
canbefoundintheW3Ctechnicalreportsindexathttp://www.w3.org/TR/.
ThisdocumentwaspublishedbytheMBUIworkinggroup
MBUI andisbeingpublishedtocomplementthe
specificationsonTaskModelsandAbstractUserInterfaces,whichseektodefineabasisforinteroperable
interchangeofuserinterfacedesignsbetweendifferenttoolsatdesigntimeandatruntime.Ifyouwishto
makecommentsregardingthisdocument,pleasesendthemtopublicmbui@w3.org
mbui (subscribe,archives).
Allcommentsarewelcome.
PublicationasaWorkingGroupNotedoesnotimplyendorsementbytheW3CMembership.Thisisadraft
documentandmaybeupdated,replacedorobsoletedbyotherdocumentsatanytime.Itisinappropriateto
citethisdocumentasotherthanworkinprogress.
Thisdocumentwasproducedbyagroupoperatingunderthe5February2004W3CPatentPolicy.W3C
maintainsapubliclistofanypatentdisclosuresmadeinconnectionwiththedeliverablesofthegroupthat
pagealsoincludesinstructionsfordisclosingapatent.Anindividualwhohasactualknowledgeofapatent
whichtheindividualbelievescontainsEssentialClaim(s)mustdisclosetheinformationinaccordancewith
section6oftheW3CPatentPolicy.
TableofContents
Introduction
BenefitsfromusingModelBasedUIDevelopment
UseCasesforModelBasedUIDesign
1.CarRentalSystem
2.DigitalHome
3.OmittingminimalisticUIsthroughtheuseofanuniversalinteractiondeviceinproduction
environments
4.StoryEditor
5.PostWIMPWidgets
6.UIdevelopmentintheautomotiveindustrytohandleUIvarietiesandtoincreaseefficiencyofUI
developmentprocesses
7.PhotoBrowser
https://www.w3.org/TR/mbuiintro/ 1/29
8.TouristWebSite(TWS):MigratoryUIunderHumanControl
CommonGenericRequirements
ExamplesofTools
GlossaryofTerms
References
Acknowledgements
Introduction
Thedevelopmentofuserinterfaces(UIs),rangingfromearlyrequirementstosoftwareobsolescence,has
becomeatimeconsumingandcostlyprocess.Typically,thegraphicaluserinterface(GUI)ofaninteractive
systemrepresentsabout48%ofthesourcecode,requiresabout45%ofthedevelopmenttimeand50%of
theimplementationtime,andcovers37%ofthemaintenancetime(MyersandRosson,1992).These
figures,evaluatedintheearlynineties,areincreasingdramaticallywiththespreadofnewinteraction
techniquessuchasvocalandgesturalmodalities,resultinginadditionalrequirements(Petrasch,2007).
Figure1.DistributionofUIdevelopmenteffortinawaterfalldevelopmentlifecycle.
Today,developersofUIforinteractivesystemshavetoaddressmultiplesourcesofheterogeneity:
1.Heterogeneityofendusers:aninteractivesystemisnormallyusedbyseveraldifferentendusers.End
usersdifferwithrespecttotheirpreferences,capabilities,culture(e.g.,speakingdifferentlanguages)
andlevelofexperience.
2.Heterogeneityofcomputingplatforms,interactionmodalities,input/outputcapabilities:thereisalarge
diversityofcomputingplatforms(e.g.,smartphone,desktopPC,tablet,embeddeddevices)using
differentinputcapabilities(e.g.,keyboard,mouse,(multi)touch,datagloves,motionsensors,monitors,
headmounteddisplays)withdifferentinteractionmodalities(e.g.,graphics,speech,haptics,gesture,
BrainComputerInteraction).
3.Heterogeneityofprogramming/markuplanguagesandwidgettoolkits:fordevelopingaUI,developers
usedifferentprogramming/markuplanguages(e.g.,Java,C++,HTML)withdifferentwidgetlibraries
(e.g.,Swing,Qt,GTK+).
4.Heterogeneityofworkingenvironments:manyworkflowsintherealworldaresupportedbyinteractive
systemsthroughthepervasivenessofcomputingdevices.Asaresult,developershavetoconsider
differentcontextualconstraints(e.g.,noisyenvironments,mobility).
5.Variabilityofthecontextofuse(<user,platform,environment>).Inadditiontobeingheterogeneous,
thecontextofusedynamicallyevolves,callingforplasticUIs,i.e.UIscapableofadaptationwhile
preservinghumanvalues(TheveninandCoutaz,1999).ThedimensionsthatcharacterizeUIplasticity
arepresentedinTheProblemSpaceofUIadaptation,UIPlasticity.
ModelBasedUserInterfaceDevelopment(MBUID)isoneapproachthataimsatcopingwiththeabove
mentionedchallengesandatdecreasingtheeffortneededtodevelopUIswhileensuringUIquality.The
purposeofModelBasedDesignistoidentifyhighlevelmodelsthatallowdesignerstospecifyandanalyse
interactivesoftwareapplicationsfromamoresemanticorientedlevelratherthanstartingimmediatelyto
addresstheimplementationlevel.Thisallowsthemtoconcentrateonmoreimportantaspectswithoutbeing
immediatelyconfusedbymanyimplementationdetailsandthentohavetoolswhichupdatethe
implementationinordertobeconsistentwithhighlevelchoices.
ForacomprehensiveoverviewofthehistoryandevolutionofMBUID,wereferto(Meixner,Patern,and
Vanderdonckt,2011).Differentframeworkshavebeendevelopedtoconceptuallycapturetheimportant
aspectsofaMBUIDprocess.Asearlyas1996,SzekelyintroducedagenericarchitectureforMBUID
(Szekely,1996).In2000,DaSilvadescribedanarchitectureforUIdevelopmentusingaMBUIDapproach
(DaSilva,2000).ThefirstversionofareferenceframeworkformultiplecontextsofuseUIsinhistoryusinga
modelbasedapproach,appearedin(Calvaryetal.,2001).Thisversionwasthenextendedwithadditional
relationshipsanddefinitionstogiverisetoarevisedreferenceframeworkpublishedforthefirsttimeinJuly
2002(Calvaryetal.,2002)andin(Calvaryetal.,2003).ItwasthennamedtheCameleonReference
Framework(CRF)whenacceptedasanewdeliverableoftheEUfundedFP5CAMELEONproject,
publishedinSeptember2002(Calvaryetal.,2002b).CRFhasnowbecomewidelyacceptedintheHCI
Engineeringcommunityasareferenceforstructuringandclassifyingmodelbaseddevelopmentprocesses
ofUIsthatsupportmultiplecontextsofuse.CRFcoversboththedesigntimeandruntimephases.In
(Calvaryetal.,2003)metamodelsandtheuseofmodelsatruntimeareproposedforsupportingUIplasticity.
Figure2.AsimplifiedversionoftheCameleonReferenceFramework(CRF).Mappingsandtransformations
betweenlevelsofabstractiondependonthecontextofuse.
AsdepictedinFigure2,theCRFmakesexplicitasetofUImodels(e.g.,Tasks,AbstractUI,ConcreteUI,
FinalUI)andtheirrelationships,toserveasacommonvocabularywithintheHCIEngineeringcommunityto
discussandexpressdifferentperspectivesonaUI.
TheTaskandDomainmodelscorrespondtothehierarchiesoftasksthatneedtobeperformedon/with
domainobjects(ordomainconcepts)inaspecifictemporallogicalorderforachievingusersgoals
(duringtheinteractionwiththeUI).UsingthewordingoftheOMGModelDrivenArchitecture(MDA)in
SoftwareEngineering(http://www.omg.org/mda/),theTaskandDomainleveliseitheraComputing
IndependentModel(CIM)oraPlatformIndependentModel(PIM).
TheAbstractUI(AUI)modelexpressestheUIintermsofAbstractInteractionUnits(AIU)(orAbstract
InteractionObjects(AIOs)(VanderdoncktandBodart,1993)),aswellastherelationshipsamongthem.
TheseAIUsareindependentofanyimplementationtechnologyormodality(e.g.,graphical,vocal,
gestural).Theycanbegroupedlogicallytomaplogicallyconnectedtasksordomainobjects.
TheConcreteUI(CUI)modelexpressestheUIintermsofConcreteInteractionUnits(CIU)(or
ConcreteInteractionObjects(CIOs)(VanderdoncktandBodart,1993)).TheseCIUsaremodality
dependent,butimplementationtechnologyindependent,thusplatformspecific(PSM).TheCUI
concretelydefineshowtheUIisperceivedandcanbemanipulatedbyendusers.
TheFinalUI(FUI)modelexpressestheUIintermsofimplementationtechnologydependentsource
code.AFUIcanberepresentedinanyUIprogramminglanguage(e.g.,JavaUItoolkit)ormarkup
language(e.g.,HTML).AFUIcanthenbecompiledorinterpreted.
TherelationshipsbetweentheCRFmodelsinclude(BouillonandVanderdonckt,2002):concretization,
abstraction,translation,andreflexion.
Concretizationisanoperationthattransformsaparticularmodelintoanotheroneofalowerlevelof
abstraction,untilexecutable/interpretablecodeisreached.CRFshowsafourstepconcretization
process:theTaskandDomainlevel(taskmodeland/orthedomainmodel)isconcretizedintoan
AbstractUImodel,whichinturnleadstoaConcreteUI.AConcreteUIisthenturnedintoaFinalUI,
typicallybymeansofcodegenerationtechniques.
AbstractionisanoperationthattransformsaUIrepresentationfromanylevelofabstractiontoahigher
levelofabstraction.Reverseengineeringofuserinterfacesisatypicalexampleofabstraction.
Translationisanoperationthattransformsadescriptionintendedforaparticularcontextofuseintoa
descriptionatthesamelevelofabstraction,butaimedatadifferentcontextofuse.
Reflexionisanoperationthattransformsamodelintoanotheroneatthesamelevelofabstractionfor
thesamecontextofuse(asopposedtodifferentcontextsofuseasfortranslation).
Theaforementionedrelationshipsalwayspreservesomedimension,eithervertically(i.e.,concretizationand
abstraction)orhorizontally(i.e.,translation,reflexion).Inordertoaddressnonhorizontal/vertical
transformations,Crosscutting(LimbourgandVanderdonckt,2009)isatransformationofamodelinto
anotheroneatadifferentlevelofabstraction(higherorlower),whilechangingthecontextofuse.
OrthogonaltotheTaskDomain,AUI,CUIandFUImodels,CRFmakesexplicitthecontextofusethatmay
haveanimpactonthenatureofthetransformationsusedinthetransformationprocess.Thetermcontextof
usedenotesaninformationspacestructuredintothreemainmodels(seerightsideofFigure2):
Theusermodelincludesattributesandfunctionsthatdescribethearchetypalpersonwhoisintended
touse,orisactuallyusing,theinteractivesystem(e.g.,profile,idiosyncrasies,currenttasksand
activities).
Theplatformmodelincludesanintegratedcollectionofsoftwareand/orhardwaretechnologiesand/or
resourcespecificationsthatbindtogetherthephysicalenvironmentwiththedigitalworld.
Theenvironmentmodelincludesspatiotemporalattributes,rules,andfunctionsthatcharacterizethe
physicalandsocialplaceswhen/wheretheinteractionwilltakeplace,orisactuallytakingplace.This
includesnumericand/orsymbolictimesandlocations(e.g.,inthemorning,at4oclock,athome,ina
publicspace,onthemoveinthestreet,inthetrainorcar),lightandsoundconditions,socialrulesand
activities(e.g.,hierarchicalsocialorganization,roles,spatialandtemporalrelationships).
Althoughcontextofuseismainlydefinedbasedoninformationaboutusers,platforms,andenvironments,
therearealsootherdimensionsthatcanberelevanttocharacterizecontextandtoproperlyadaptan
interactivesystem.Theapplicationdomain,forinstance,canalsoaddrelevantinformationthatcompletethe
characteristicsofthecontextofuse.Forexample,inasafetycriticalenvironment,knowingthatthe
interactivesystemsupportsairtrafficcontroloranuclearpowerplantprovidesusefulinformationaboutthe
levelofattentionthatisrequiredfromendusers.
Unliketheprocessinitiatedinthe1980s,whichcontainedoneentrypointonlyatahighlevelofabstraction,
CRFenablesentryandexitpointsatanylevelofabstractionfromwhichanycombinationofhorizontaland
verticalbottomupandtopdowntransformationscanbeapplied.Thistheoreticalflexibilitymeansthatthe
stakeholdersinvolvedinthedevelopmentofaninteractivesystemcanusethedevelopmentprocess(e.g.,
humancentereddevelopmentprocessesaccordingtoISO9241210)thatbestsuitstheirpracticeorthe
caseathand.Evenwhenusingatopdownapproach,developerscanexploremultipledevelopmentpathsin
parallelasillustratedinFigure3.However,duetothishighflexibility,developershavetoensurethatmodels
arenotmanipulatedbyhandafteratransformationhasbeendone.Ifso,developershavetoensuremodel
consistencybye.g.,usingreversetransformationsfromamoreconcreteleveltoamoreabstractlevel.
Figure3.OneexampleofpossibletransformationsacrossthelevelsofCRFaccordingtodifferentcontexts
ofuse,startingfromauniqueTaskandDomainModel.
BenefitsfromusingModelBasedUIDevelopment
Thissectionprovidesalistofpotentialbenefitsthatareusuallydiscussedformodelbaseddevelopmentand
ModelDrivenEngineering(MDE)ingeneral.EachpotentialbenefitisthenrefinedinthecontextofUI
development.GeneralMDEbenefitsarereportedin(Hutchinsonetal.,2011).
1.Benefitsresultingfromtheexistenceofastepwisedevelopmentlifecycle:
Reducingthegapbetweenrequirementsandimplementation:amodellingphaseaimstoensurein
advancethattheimplementationaddressestheusercenteredrequirements.MBUIDcontributestothis
byexplicitlydefiningmodelsrelatedtotheUIthatarecapturedandupdatedthroughoutthe
developmentlifecycle.Theoutputofadevelopmentstepcouldserveasaninputforanext
developmentstep.Amongtypicalmodelsarethetaskmodel,thedomainmodel,thecontextofuse
model,thuspromotingausercentereddevelopmentlifecycle(asrecommendedbyISO9241210).
Thesemodelsareoften,butnotalways,specifiedaccordingtodeclarativeprogramming,a
programmingparadigminwhichthelogicoftheUIisdescribedwithoutdescribingitscontrolflow.
Otherprogrammingparadigms(e.g.,logicprogramming,functionalprogramming,
imperative/proceduralprogramming)arealsousedindividuallyormixedtogether(Grolaux,VanRoy,
Vanderdonckt,2001).
Coordinatingtheinvolvementofmultiplestakeholders:previousplanningofthedevelopmentlifecycle
enablesvariousstakeholders(e.g.,projectleaders,designers,developers,testers,endusers,
psychologists,marketingpeople)tocoordinatetheirwork,e.g.,bydividingtheinteractivesysteminto
severalpartsanddefiningmappingsbetweenthem.Separationofconcernssupportscapturingvarious
UIaspectsinindependent,butpossiblycorrelated,modelsthusenablingthesedifferentstakeholders
tofulfilltheirrespectiveroles.
Producingwellstructuredsystems:thestepwisedevelopmentlifecycletogetherwiththeseparationof
concernsprovideagoodbasisforproducingawellstructuredsystem,thusfacilitatingimplementation
itselfaswellasmaintenance.
2.Benefitsresultingfromtheuseofexplicitabstractmodels:
Planninganadequatelevelofabstraction:modelinglanguagesprovidethedeveloperwithconceptsfor
planningandreasoningaboutthedevelopedsystemattheappropriatelevelofabstraction.MBUID
contributestothisbenefitbydefiningthelevelsofabstractiondescribedinCRF.
Improvingcommunicationbyexplicitmodels:theexplicitnessofmodelinglanguages,inparticulartheir
visualrepresentation,canleadtoincreasedquality(e.g.,understanding,perceiving,exploring,
explaining,justifying,comparing,etc.,)ofdesigndocumentsforallstakeholders.Forinstance,MBUID
contributestothisbenefitbyexplicitlydefiningsemantics,syntax,andstylisticsforeachmodel.
SupportingUIquality:(semi)formalmodelinglanguagesexplicitlysupportUIcompliancewithrespect
torequirements(e.g.,UIqualityfactors,usabilityguidelines(Fernandezetal.,2012),accessibility
guidelines(e.g.,WCAG),validationrulesforcompleteness,consistency,correctness).
3.Benefitsfromexploringalternativedesigns:
Supportingcreation&creativity:MBUIDefficientlyproducesalternativemodelswithdifferentdesign
options,parameters,thusfosteringtheexplorationofthedesignspace(Masson,2010).
Enablingtheproductionandcomparisonofalternativedesignsformultiplecontextsofusewhile
preservingquality(e.g.,consistency):whenUIsneedtobeproducedformultiplecontextsofuse,
MBUIDfacilitatestherapidproductionandcomparisonofalternativedesigns(e.g.,factoringout
commonpartsthatarecontextindependentfromspecificcontextdependentparts),whichis
particularlyusefulinchangemanagement(Pilemalmetal.,2012).
4.Benefitsresultingfromcodegeneration:thebenefitsassociatedwiththisappearwhenthemethodis
enacted.
Enhancingdevelopmentproductivity:codegenerationfromasetofmodelsoftenrequiresonlyasmall
fractionoftimecomparedtothemanualproductionofcode.Consequently,MBUIDfavorsUIrapid,
iterative,agiledevelopment,includingUImockupsandprototypesatdifferentlevelsoffidelity(Coyette,
Kieffer,Vanderdonckt,2007).
CapturingandreusingexpertknowledgethroughoutUIdevelopmentlifecycle:expertknowledge
e.g.,aboutuserinterfacedesign,usabilityengineering,codestructuring,codeoptimizations,or
platformspecificvsplatformindependentfeaturesonceincorporatedinvariousdevelopmentsteps,
expertknowledgecanthenbereusedbyallstakeholders(especiallydevelopersanddesigners).
Reducingerrors:automatictransformationavoidsmanualerrors.Integranovacreatescustomised
solutionsinhalfthetime,personalisedsolutionsforhalftheprice,andtopquality,errorfreesoftware.
(Integranova,2012).
5.Benefitsfromusingmodelsatruntime:
Consideringcontextsofusethatwerenotenvisionedatdesigntime:whenanewcontextofuseneeds
tobeconsidered(e.g.,opportunisticendusersneeds),thenmodelscanbeexploitedatruntimeto
supportontheflyadaptation(GarciaFrey,2012).
ExplainingandjustifyingtheUItotheenduser:theUIisabletoexplainandtojustifyitselftotheend
userthankstothemodelsthatcapturethedesignrationaleandthatareembeddedatruntime(Garcia
Frey,2013).
Goingbeyondlowleveladaptation:adaptationcanspanfromthehighestlevelofabstraction(e.g.,the
taskandthedomainmodels)tothelowestlevel(e.g.,thefinalUI).
EnablingUIevolution.Whenrequirementscontinuouslyevolveatruntime,theUIshouldberepeatedly
modified,andsodoitsmodels,aswellasthedesignknowledgeusedtoproduceit.Thisevolution
couldbegovernedbytheuser(i.e.,manuallybythewayofametauserinterface(Coutaz,2006)),by
thesystem(i.e.,autonomouslyasinautonomiccomputing(IBM,2001))orbyboth(i.e.,mixedinitiative
(Models@runtime,2009EisensteinandPuerta,2000Mitrovicetal.,2007)).
6.Benefitsforsupportingmethodengineering:
DefiningandenactingmethodforUIdevelopmentprocess:oncedefined,amethodcouldbeenacted
andanydeviationwithrespecttothedefinitioncouldbepointedout.
Knowledgeaboutcreationofmodelinglanguages:MDEconceptsanddefinitionsreflectexisting
knowledgeaboutmodeling,modelinglanguages,andcodegeneration.MBUIDcontributestothis
benefitbybringingexpertiseaboutmodelsforuserinterfacedevelopment.
Usageofframeworksandtools:varioussoftwaretools,suchasIntegratedDevelopmentEnvironments
(IDEs),couldsupportMBUID.InmoreadvancedmodeldrivenengineeringofUIs,toolsexistthat
supportMDEsteps,suchascreatingandprocessingmetamodels,creatingmodelingeditors,and
definingandexecutingtransformations(e.g.,transformationengines).
7.Maintenanceofmodelinglanguageandtransformations:
Systematicandexplicitdefinitionofmetamodelsandtransformations:whenallmodelsand
transformationsaredefinedaccordingtoacommonsetofmetamodels,theirusagebecomes
systematic.ThisalsoworksforMBUID.
Maintenanceofmodelinglanguagesandcodegenerators:modelinglanguages,associatedmodelto
modeltransformationsandmodeltocodecompilationcanbemaintainedatalevelofexpressiveness
thatishigherthanatraditionalprogrammingormarkuplanguage.
Reuseofmodels,metamodels,andtransformations:MDEcompliantmetamodelsandtransformations
canbeunderstoodandreusedbyothers.Modelsormodelfragmentscouldbereusedfromoneuse
casetoanotherorfromonecontextofusetoanother,onlyaffectingtheportionthatissubjectto
change(Pilemalmetal.,2012).Thisreusefacilitatesthedevelopmentofplasticuserinterfaces(Seffah
andJavahery,2004).
UseCasesforModelBasedUIDesign
ThissectionprovidesalistofimplementedusecasestoillustratedifferentCRFcompliantdevelopment
processes.Table1providesasyntheticviewofthedifferentiatingcharacteristicsoftheseexemplarswhere
linesrefertothelevelofabstractionusedastheentrypointfromwhichtransformationsareperformed,and
wherecolumnsindicatewhetherthesetransformationsareperformedatdesigntimeoratruntime.The
documentComplementaryListofUseCasesprovidesadditionalexamples.
EntryPoint/SoftwareLife
DesignTime RunTime
CyclePhase
UC1CarRental
Task&Domain UC3MinimalisticUIs
UC2DigitalHome
UC5PostWIMP
AbstractUI UC4StoryEditor
Widgets
ConcreteUI UC6AutomotiveIndustry(Infotainment UC7PhotoBrowser
systemdesign)
UC8TourismWebSite
FinalUI
(TWS)
1.CarRentalSystem
Responsible:
UniversitcatholiquedeLouvain(JeanVanderdonckt,VivianGenaroMotti,PascalBeaujeant,Nesrine
Mezhoudi)
1.1IntroductoryDescription
Thecarrentalexampleconsistsofascenarioinwhichtheinteractivesystempermitsuserstorentacar.In
thissense,variouscontextualinformationcanbeusedtoadaptapplicationaspects,andtoproperlydisplay
thelistofcarstorent,enablinguserstomakechoicesandtoaccomplishthemaintask.
Thekeyfunctionalrequirementstosupportthistaskincludethecapacityto:
specifythepickupandreturnlocationsofthecar
specifytheperiodforthecarrental
accessasetofpossiblecarsandselectone
accessandselectadditionalcarfeatures(e.g.GPS)
providepersonalinformationbeforerentingthecar
accessdetailsaboutthecarrentalbeforemakingthefinaldecision.
Twocontextsofusearetargeted:
1)Context1:Physicalenvironmentisthatofahome,platformisaDesktopPC,andtheuserisanEnglish
speakerwhodoesnotknowthecitywherethecarhastoberented.
2)Context2:Physicalenvironmentisabusystreet,platformisasmartphone,andtheuseriswalkingfast
(busyeyes).
FiguresUC1.1andUC1.2showscreenshotsforthetwotargetedcontextsofuse.
FigureUC1.1.AConcreteUserInterfaceforContext1Home,PC,Englishspeakerfamiliarwiththe
location.
FigureUC1.2.AConcreteUserInterfaceforContext2Noisystreet,SmartPhone,Englishspeakerwalking
fast,notfamiliarwiththelocation.
1.2DiagramandDiscussion
FigureUC1.3illustrateshowaMBUIapproachcanbeappliedusingsuccessiveconcretization
transformationsstartingfromasingleTaskandDomainModeltodifferentAbstractUserInterfaces(each
onecorrespondingtoaspecificcontextofuse)anditerativelydowntoFinalUserInterfaces.
FigureUC1.3.Modelsinvolvedinthecarrentalusecaseandtheprocess.
FigureUC1.4.Taskmodelsforthetwotargetedcontextsofuse.
2.DigitalHome
Responsible:
CNRISTI(FabioPatern,CarmenSantoro,LucioDavideSpano)
Digitalhomereferstoaresidencewithdevicesthatareconnectedthroughacomputernetwork.Adigital
homehasanetworkofconsumerelectronics,mobile,andPCdevicesthatcooperatetransparently.All
computingdevicesandhomeappliancesconformtoasetofinteroperablestandardssothateverythingcan
becontrolledbymeansofaninteractivesystem.Differentelectronicservicescanbeofferedbyadigital
homesystem,includingbutnotlimitedtoe.g.,manage,synchronizeandstorepersonalcontent,family
calendarsandfilesupload,playandshowmusic,videosandpicturesonahomescreen(e.g.,aTV)usinga
mobilephoneasaremotecontroluseamobilephoneasaremotecontrolfortheotherdevices,forexample
athermostat.
Thesefunctionalitiesaremadeavailablethroughcontextsensitiveuserinterfaces.Infact,suchUIsare
capableofadaptingtodifferentcomputingplatforms(touchbaseddevices,web,mobile,TV,PDA,DECT
handset,voiceportal),users(children,teenagers,adults,elderly,disabledpeople,)andenvironments
orsituations(athome,away,atnight,whilemusicisplaying,).Thefinalaimistoprovideaseamlessand
unifieduserexperience,whichiscriticalinthedigitalhomedomain.Tothisregard,differentautomaticUI
adaptationscanbepossible:e.g.,zoomingtheUIiftheuserhasvisualproblemsenablingmultimodal
interactions(ex.voiceinteraction)becausetheuserisdoinganothertaskatthesametime.
Thekeyfunctionalrequirementsforthisapplicationarethefollowing:
authenticateauserinordertoenableremoteaccesstohomedevices
selectaroom
selectadeviceinsidetheroom
inspectandmodifythestatusofaselecteddevice
Thisapplicationmaybeusedindifferentcontextsofuse:
1)Context1:Physicalenvironmentisthatofahome,platformisaDesktopPC,andtheusercontrolsthe
homedeviceswithoutaccessingdirectlythephysicalcontrols.
2)Context2:Physicalenvironmentisastreet,andtheuserismoving.Theusercontrolsthehomedevices
remotely,inordertoe.g.startheatingthehomebeforecomingback.
Inthisusecase,thecontextdimensionconsideredislimitedtotheplatformaspect.
FiguresUC2.1andUC2.2showscreenshotsoftheDigitalHomefortwotargetedcontextsofuse.
FigureUC2.1:ThedesktopversionoftheDigitalHomeapplication.
FigureUC2.2:ThemobileversionoftheDigitalHomeapplication.
ThemodelsinvolvedintheDigitalHomeusecaseaswellastheprocessinvolvingthemaredepictedin
FigureUC2.3.
FigureUC2.3.ModelsinvolvedintheDigitalHomeusecaseandtheprocess.
TheusecaseconsideredintheDigitalHomeexemplar(Morietal.,2008)startsfromthetaskmodelshown
inFigureUC2.4.Becauseweconsidertheplatformastheonlydimensionofthecontextofuse,theother
contextaspectshavebeengreyedoutinFigureUC2.3.Fromthetaskmodel,itispossibletoderivean
AbstractUIforeachtargetedcontextofuse.LetsconsideradesktopPC.Ontheonehand,thisAUIwillbe
expressedusingamodalityandplatformindependentvocabulary(alsosharedbyotherAUIsaddressing
differentcomputingplatforms),ontheotherhand,thisAUIwillincludeonlytheabstractinteractionunitsthat
makesenseinthatconsideredcomputingplatform(adesktopPC).FromthisAUI,itispossibletoobtaina
ConcreteUIandthenaFinalUIinaspecificimplementationlanguagesuitableforthatcomputingplatform.
AsimilarprocessisfollowedtoobtainaFinalUIforadifferentplatform(e.g.,themobileone).Fromthe
filteredCTTtaskmodel,anAbstractUIisderivedandthenaCUIandfinallyanimplementedUIexpressed
inalanguagesupportedbythemobileplatformisbuilt.
FigureUC2.4.TheTaskModelfortheDigitalHome.
3.OmittingminimalisticUIsthroughtheuseofanuniversalinteractiondevicein
productionenvironments
Responsible:
HeilbronnUniversity(GerritMeixner)
DFKI(MarcSeissler):
TheSmartFactoryKL(seeFigureUC3.1)isanarbitrarilymodifiableandexpandable(flexible)intelligent
productionenvironment,connectingcomponentsfrommultiplemanufacturers(networked),enablingits
componentstoperformcontextrelatedtasksautonomously(selforganizing),andemphasizinguser
friendliness(useroriented).TheSmartFactoryKListhefirstambientintelligentproductionenvironmentfor
demonstrationanddevelopmentpurposesworldwide.Developmentofuserinterfacesisasecondaryfieldin
theproductionindustry,buttheimpactofuserinterfacequalityisincreasinglyindependentoftheapplication
domain,whichisasignificantfactorofsuccessfortheentireproduct.Afterthreeyearsofresearch,afirst
prototypehasbeenfinishedthatallowsforcontrollingtheproductionlineusingasingleuniversalinteraction
deviceabletoadapttovaryingfielddevicesaccordingtotheactualcontextofuse,inacomplex,model
basedapproach.Tohandletheresultingdiversityofuserinterfaces,wedevelopedauniversalinteraction
devicetheSmartMotewhichiscapableofprovidingcontrolovervariousdevicesintheseenvironments.
Dependingonthecontextofuse,thevisualizationoftheSmartMoteisgeneratedandadaptedduringrun
timeinordertoprovideahomogeneousintradeviceuserexperience.
FigureUC3.1.TheSmartFactoryKL
Thekeyfunctionalrequirementsforthisapplicationarethefollowing:
authenticateauserinordertoenableremoteaccesstomodulesorfielddevices
selectamoduleorafielddevice
inspectandinteract(e.g.modifyparameters)withaselectedmoduleorfielddevice
TheSmartMotemaybeusedinonecontext
1)Context1:Physicalenvironmentisthatofaproductionenvironment(industrialfactory),platformisatablet
PC(+modulesorfielddevicesfromdifferentvendors),onesingleuser
FigureUC3.2.Screenshotofarendered(final)UIwiththeSmartMote(Seissler,2013)
ForthespecificationofthecontextsensitiveUIamodelbasedarchitecturehasbeendevelopedthat
consistsoftwocoremodels(AUImodelandCUImodel).TheAUImodelisspecifiedusingtheUseware
DialogModelingLanguage(useDM)thatenablestheabstract,modalityindependentspecificationofthe
userinterface.ThismodelisrefinedviaaCUImodelthatusestheUserInterfaceMarkupLanguage(UIML)
4.0fortheplatformindependentdescriptionofthegraphicaluserinterface.Adaptationrulesarefurtherused
tospecifytheadaptationthatcanbeappliedonthosemodelsatruntime.Togeneratethefinaluser
interface(FUI)ajavabasedRendererSmartMotehasbeendeveloped.
FigureUC3.2.ModelsinvolvedintheMinimalistUIusecaseandtheprocess.
4.StoryEditor
Responsible:
UniversityLaSapienzaofRome(PaoloBottoni)
Theproductionofelearningtoolsfordeafpeoplemeetswithseveraldifficulties,connectedtotheneedto
resortonlytothevisualchannel,withoutsaturatingit,andtotheadoptionofdifferentcognitivestrategies
developedwithinthecommunity.Fromafieldstudyconductedwithdeafpeopleinthecontextofanational
projectinvolvingcognitivescientists,linguists,andcomputerscientists,weadoptedthemetaphorofa
learningstoryasthebasisfororganisingdifferenttypesoflearningmaterial:videos,pictures,texts,
accompaniedbytranslationintheItalianSignLanguage.Wereportontheuseofauserinterfaceabstract
modelinthedevelopmentoftheinteractivestoryeditor,tobeusedbytutorsandteacherstoorganisethe
coursematerialandpath,andwhichgeneratesinteractivepagesforthestudents.
Thekeyfunctionalrequirementstosupportdevelopersofcourseinclude:
specifytheactivitiesinvolvedinalearningmodule
specifythelogicalpathsaccordingtowhichtheseactivitiescanbeperformed
specifytheconditionsforprogressingalongthesepaths.
Thecontextofuseisthatofthegenerationofacoursebyateacher,possiblyinvolvingintheprocesstutors
whowillthenhavetoassistthelearners.Learnersandtutorswilltheninteractwiththegeneratedwebpages
(Bottonietal.,2012).
Thedevelopmentreliesonanabstractmodelofthelearningdomain,inwhichstoriesareseenasworkflows:
(learning)processesinwhichtasksareassignedtoactors(e.g.,studentsandtutors).Storiescanbe
recursivelycomposedbysubstories,pathsdefinesequencesoralternativesforexplorationofstories,with
transitionsconnectingsubstories,andtaskseitheraredefinedassimplestoriestobeexploredindividually
orinalaboratory,orrequiretheexplorationofsubstories.Eachstoryhasasingleentrypointandasingle
exitpoint,signallingcompletionbythestudent.
Storiesareclassifiedwithrespecttotheexplorationstrategyandassociatedwithabstractpatterns.For
example,inastartopologytaskscanbeperformedinanyorder.Foreachtype,thestoryeditorprovidesa
specialisedformofinteraction,guidingtheteachertodefinethestoryaccordingtothattype,andatemplate
isusedtogeneratetheappropriatemainpageforthestoryaccordingly.FigureUC4.1(left)presentsthe
workflowforastorywiththreesubstoriesorganisedinastartopology.FigureUC4.1(right)showsthe
generatedpageforastorywithstartopologyprovidingaccesstofivesubstories.Thelateralbarsare
generatedaccordingtoageneraltemplate.
FigureUC4.1:Theworkflowforastarstory(left)andageneratedpageforastarstory(right).
ThemodelsinvolvedintheDigitalHomeusecaseaswellastheprocessinvolvingthemaredepictedin
FigureUC4.2.
ThedesignoftheinteractionwiththeStoryEditorandofthetemplatesforthegeneratedpagesderivesfrom
therepresentationoftasksintheformofpatternscomposedbyspecifictasktrees.Foreachpattern,the
storyeditorwillconstraintheinteractiontocreateinstancesofthatpattern,andwillgeneratethespecific
workflowtobefollowedwhileinteractingwiththegeneratedpage.Moreoveracorrespondingpatternof
interactionelementstobeincludedinthegeneratedpageisprovidedasanabstractuserinterfacemodel.
ThetargetplatformisthatofWebpageswithassociatedJavaScriptcomponentsfortheinteractionwiththe
specificlearningcontent.
FigureUC4.2.ModelsinvolvedintheStoryEditorusecaseandtheprocess.
AsshowninFigureUC4.3,aStoryContainerwillpresentseveralindividualcomponents,providingcontext
fortheinteraction,andaPresentationContainer,composedofseveraldifferentpagecontentsinamutual
emphasisrelationsothattheycannotbeshowntogether).Thespecificcompositionofthepresentation
containerwilldependonthetypeofstorytobepresented,asprescribedbytheTaskModel,whereeitheran
individualcomponentoracontainerisassociatedwitheachtask.
FigureUC4.3:Theoverallabstractstructureofstorycontainers.
5.PostWIMPWidgets
Responsible:
OFFISe.V.(SebastianFeuerstack)
WiththeintroductionoftechnologieslikeHTML5,CSS3,andSVG,thewaypeoplecaninteractwiththeweb
hasbeenfundamentallyenhanced.Designersarenolongerrequiredtouseapredefinedsetofbasic
widgets.Instead,interactioncannowadaysbedrivenbyselfdesignedwidgetsspecificallytargetedatsome
specificuserneedsorspecificapplicationrequirements.ThesePostWIMPwidgetsaredesignedtosupport
differentcombinationsofmodesandmediaandcanguaranteeacertainqualityinuseuponcontext
changes.BasedonubiquitousavailabilityofbrowsersandcorrespondingstandardizedW3Ctechnologies
PostWIMPwidgetscanbeeasilydesignedandmanipulated(e.g.SCXML,ECMA),instantlyreflect
continuouscontextchanges(e.g.byWebSockets)andconsiderdifferentmultimodalsetups(e.g.
XHTML+Voice,SMIL,andtheMMIArchitecture).
ThefactthatthecontrolandappearanceofPostWIMPwidgetsisdesignedwithahighdegreeoffreedom
hasanimpactonMBUIDapproaches:thetoolkitandthereforethetargetofamodeltransformationcanno
longerbeenassumedasstatic(afixedsetofwidgets).Thesamemodels(taskmodel,AUImodel,CUI
model)knownfromMBUIDcanbeappliedtodesignindividualPostWIMPinteractors.Additionally,a
statechartbasedbehaviordescriptioncapturestheenhancedinteractioncapabilitiesofaPostWIMP
interactor.AsanexampleweconsidertwousecasesofPostWIMPinteractorsrunninginsideaweb
application:Amixedrealityfurnitureonlineshopthatcanbecontrolledbygesturesandsupportsinterreality
migrationofinteractorsandaninteractivemusicsheetthatcanbecontrolledbyheadmovements.
WebFurnitureShop
Inthewebfurnitureshop,acustomercanchoosebetweendifferentfurnitureandfillupashoppingcart.Bya
draganddropgestureusingbothhandsonecandragfurnitureinteractorsvirtuallyoutofthemonitor
displayingthewebshopanddropthemintoanaugmentedrealitytoseeifthefurniturereallymatchesin
spaceandcolortotheusersenvironment.Anaugmentedrealityframethatsurroundstheshoppingcart
allowstoseamlesslyswitchbetweenrealitieswhilecrossingitduringthedraganddropgesture.
FigureUC5.1:Shoppingcartwebapplicationwithrealityframe.
FigureUC5.1showstheactualshoppingcartthatispartofatypicalonlineshopandhasbeenenhancedby
aRealityFrame.ToenablearealitycrossingDragandDrop,theRealityFrameneedstobeactivated,which
triggersacalibrationofthesystemthatidentifiesthemonitorsphysicallocationintheenvironmentofthe
userusingacameraandavisualmarker.
FiguresUC5.2a(left)andUC5.2b(right):Twohandedgesturetopickanddropfurniture.
FiguresUC5.2aandUC5.2bdepictauserdraggingfurnitureusingthelefthandforpointingandtheright
handforpickingupanobjectinthebrowser.Aftertheusershascrossedtherealityframeoftheshopping
cartinthebrowser,thewebpagechangestotheaugmentedsceneenablinghertopositionthefurniturein
herownenvironment.
FigureUC5.3:Usingamousetodraganddropfurnitureintotheenvironmentoftheuser.
FigureUC5.3showsanadaptationoftheinteractorsthatsupportthesameinteractionusingaclassical
mouseandkeyboardsetup.
Thekeyfunctionalrequirementsforsupporttheuseroftheonlinefurnitureshopinclude:
chooseandaddfurnituretoshoppingcart
dragfurnitureitemsoutofthewebsite
dropfurnitureitemsintotheaugmentedenvironmentoftheuser
Threecontextsofusearetargeted:
1.Physicalenvironmentisthehomeoftheuser,platformisadesktopPCtobecontrolledbyamouse,
anduseristheonlineshopcustomer
2.Physicalenvironmentisthehomeoftheuser,platformisadesktopPCtobecontrolledbyan
interactiontechniquethatrequireshandgestureswithbothhands.
interactiontechniquethatrequireshandgesturesusingjustonehand.
InteractiveMusicSheet
Whenlearningtoplayamusicalinstrument,orwhenplayingone,amusicsheetisusedtogiveguidanceas
tohowtoperformthemusicalpiece.However,assongsbecomelongerandmoreintricatetheymayspan
acrossseveralsheets,forcingtheplayertostopplayingtoturnthepage.Althoughthismaybecomeeasier
asonebecomesmoreexperiencedwiththeinstrument,itisabarrierforinexperiencedplayersthatcanbe
tackledeasilyusingadifferentmodetoturnthepagesotherthanyourhand.
FigureUC5.4(left):MusicsheetcontrolsetupFigureUC5.5(right):Musicsheetwebapplication
WeproposeaUItoturnmusicsheetswithsimpleheadmovementsthatcanbecapturedbyabasicVGA
webcam,acommonpartofmodernnotebooks.TheconsideredsetupisshowninFigureUC5.4anda
screenshotofthewebbrowserdisplayingthemusicsheetisdepictedinFigureUC5.5.
FigureUC5.6:HeadTrackingInteractor
Aheadmovementmodeinteractorsupportsdetectingtiltingtheheadtotheside,rightandleft,asthe
controllertopasstothenextpageorreturntothepreviouspage,respectively.FigureUC5.6showsa
screenshotoftheheadtracker.Theleftsideofthefigureshowsthedebugginguserinterfaceinthata
movingarrowrepresentsthedirectionoftheheadmovement(mirrored).
Thekeyfunctionalrequirementsforsupporttheuseroftheonlinefurnitureshopinclude:
Turnmusicsheetpagestriggeredbyvariousheadmovements
Threecontextsofusearetargeted:
interactiontechniquethatinvolvestiltingtheheadtotheleftandtotheright.
interactiontechniquethatinvolvesturningtheheadtotheleftandtotheright.
interactiontechniquethatrequiresnodding.
Theprocessstartsatthefinaluserinterfaceandidentifiesinterfaceelements(widgets)thatshouldbe
enhancedtobecontrollableviavariousmodalities,e.g.,gesturesorbodymovements.ForeachFUI
element,amappingisthendefinedthatidentifiestheabstractInterfaceinteractor(fromapreexisting
abstractinteractormodelhttp://www.multiaccess.de/mint/aim)thatmatchesbestthebehavioroftheFUI
element.Then,concreteuserinterfaceinteractorsarespecifiedthatrepresenttheFUIelementsbehavioras
amodel(byastatechart).Finally,themodeledbehaviorispreciselymappedtotheFinalUIelement
(http://www.multiaccess.de/mint/mim).
FurthercontrolmodesorinteractorrepresentingmediathathavebeenderivedfromthesameAUIinteractor
andforthatalreadyCUImodelinteractorshavebeendefinedcanthenbeusedasanadditionalcontrol
modeorrepresentationforthenewFUIelement(http://www.multiaccess.de/mint/irm)(Feuerstack,2012a).
Differenttotheotherapproachesthemainintentionoftheprocessistoidentifyandspecifyinteractorson
theabstract,concreteandfinaluserinterfaceleveltoformaninteractorrepositoryofreusableinterface
elementsthatsynchronizethemselvesovervariouscontrolmodesandmediarepresentations
(http://www.multiaccess.de/mint2012framework/)(Feuerstack2012b)
FigureUC5.7.ModelsusedforthePostWIMPwidgetsusecase,andtheprocess.
6.UIdevelopmentintheautomotiveindustrytohandleUIvarietiesandtoincrease
efficiencyofUIdevelopmentprocesses
Responsible:
CERTH/ITI(NikolaosKaklanis)
DFKI(MariusOrfgen)
HeilbronnUniversity(GerritMeixner)
RobertBoschGmbH(RanZhang)
Carinfotainmentsystemsarecurrentlydevelopedusinghugetextualspecificationsthatarerefined
iterativelywhileparallelbeingimplemented.Thisapproachischaracterizedbydivergingspecificationsand
implementationversions,changerequestnegotiationsandverylateprototypingwithcostintensivebug
fixing.Numberandvarietyofinvolvedactorsandrolesleadtoahugegapbetweenwhatthedesignersand
ergonomistsenvisionasthefinalversion,whattheydescribeinthesystemspecificationandhowthe
specificationisunderstoodandimplementedbythedevelopers.
Modelbaseduserinterfacedevelopmentcouldspeeduptheiterativeimplementationwhilereducing
implementationeffortsduetoautomaticgenerationofprototypeinterfaces.Differentmodelscouldbeusedto
establishaformalandefficientcommunicationbetweendesigners,functionalityspecialists(e.g.Navigation,
TelephoneandMedia),developersandotherstakeholders.Theresultingreductionofdevelopmenttime
wouldmakecarinfotainmentsystemsmorecompetitiveandwouldnarrowthegaptoinnovationcyclesinthe
fieldofconsumerelectronics.
Anotherlargeaspectofmoderncarinfotainmentsystemsisthequalityassurancethatisperformedbythe
vendors.Thecomplexityofmoderninfotainmentsystems(morethan1000differentscreensanddifferent
modalities)requireslargeeffortstodevelopformaltestmodelsonthebasisofthesystemspecification.The
testmodelsarethenusedbythevendortotesttheimplementationcomingfromthesupplier.Thisprocedure
resultsinanothertimeandcostintensivegapthatcouldbebridgedbyperformingconsistencychecksonthe
modelsusedtogeneratetheinfotainmentsysteminsteadoftestingtheimplementation.
Moreover,vehiclesandtheirinfotainmentsystemshavetobeaccessible.Eventhoughmodelbaseduser
interfacedevelopmentcouldspeeduptheiterativeimplementation,afurtherstepisneededtoenforcethe
accessibilityofthecars:thedescriptionoftheuser.Ifuserinterfacedescriptionlanguagescanalsodescribe
theuserefficiently,includingelderlyandpeoplewithdisabilities,thenthetwodefinitions(UI&user)couldbe
usedinframeworksperformingautomatic/simulatedaccessibilityevaluationoftheprototypeinterfacesofa
car.
ThekeyfunctionalrequirementstosupportUIdevelopmentintheautomotiveindustryincludethecapacity
to:
createaprototypeUIofacarinfotainmentsystem
viewtheprototypeUI
edittheprototypeUI
performautomaticfunctionaltestingoftheprototypeUI
performautomaticaccessibilitytestingoftheprototypeUIusingusermodels(representingvarious
populationgroupswithorwithoutdisabilities)
1)Context1:Physicalenvironmentisthatofanautomotivecompanyoffice,platformisadesktopPCand
userisadeveloper.
2)Context2:Physicalenvironmentisthatofanautomotivecompanyoffice,platformisaVirtualReality
CAVEanduserisadesigner.
Themodelsinvolvedintheautomotiveindustryscenario,aswellastheprocessinvolvingthem,aredepicted
inFigureUC6.1.
FigureUC6.1.ModelsusedintheAutomotiveIndustryusecase,andtheprocess
IntheautomotiveindustryUIsaredevelopedstartingattheCUIlevel.Normallydevelopersstartwith
sketches,mockupsorpaperprototypesanditerate.Onthebasisofmockupsinteractionandgraphical
designersrefinethemockupstowireframesandfinallydevelopthegraphicaldesigne.g.,withAdobe
Photoshop.IntheendtheprototypesaremanuallytransferredintoafinalUIforaspecificinfotainment
system.TheprojectautomotiveHMI(http://www.automotivehmi.org/)isdevelopingaprocessandaUIDLto
integratetheworkingartifactsoftheinvolveddeveloperstogeneratetheFUIautomatically.
7.PhotoBrowser
Contributors:
UniversityofGrenoble(JoelleCoutaz,GalleCalvary)
PhotoBrowsersupportsphotobrowsinginacentralizedordistributingwaydependingontheavailabilityofa
dynamicsetofinteractivedevices(http://iihm.imag.fr/demo/photobrowser/).Theseincludeamultitouch
interactivetable,aprojecteddisplayonawall,anAndroidSmartPhone,andakinecttotrackgestures.As
showninFigureUC7.1,theUIofPhotoBrowserisdynamicallycomposedofthefollowingcomponents:a
TclTkcomponentrunningonthemultipointinteractivesurface(Fig.UC7.1d),acomponentthattransforms
anHTLMlikeCUIintoHTMLcodetoserveasinputtoaWebbrowser(thiscodesupportsthetask
sequentialnavigationthroughtheimageportfolio)(Fig.UC7.1c),aJavacomponentthatprovidesalistof
thephotonames(Fig.UC7.1b),andaJavacomponentrunningontheSmartPhonetonavigatethroughthe
photossequentiallyusingtheNextandPreviousbuttons.
FigureUC7.1.Photobrowser:adynamiccompositionofexecutableandtransformablecomponents
managedbyadynamicsetofinterconnectedfactories(a)runningondifferentplatforms(Windows,MacOS
X,andAndroid).
Whentheuser,sayAlice,enterstheroom,theinteractivetablestartsautomaticallyandshowsBobslast
openedphotoportfolio.Byperformingawipegesturefromthetabletothewall,thecurrentselectedphoto
ofthetableisreplicatedonthewall.AsAlicebringsherSmartPhoneincontactwiththetable,thephonecan
beusedasaremotecontroller(FigureUC7.2).Usingawipegestureoverthetableprovokesthetableto
shutdown.AlicecancarryonhertaskusingthewallasalargedisplayandtheSmartPhoneasaremote
controller.Here,ametaUIhas(Coutaz,2006)beendevelopedtosupporttwoclassesoffunctions:(a)
Dynamicsoftwaredeploymentintheambientinteractivespace,and(b)UIredistributionacrossinteractive
devicesincludingontheflygenerationfromaCUIHTMLliketonativeHTMLcode.
ThekeyfunctionalrequirementstosupportUImigrationforphotobrowserincludethecapacityto:
specifythesourcepicture,
specifythetargetdevicewheretodisplaythesourcecontent,
addadevice(e.g.,SmartPhone)
suppressadevice(e.g.,interactivetable).
Fourcontextsofusearetargeted:
1)Context1:Physicalenvironmentisthatofanoffice,platformisaninteractivetablePC,onesingleuser.
2)Context2:Physicalenvironmentunchanged,platformiscomposedofaninteractivetableandofaPC
equippedwithabeamer,onesingleuser.
3)Context3:Physicalenvironmentunchanged,platformiscomposedofaninteractivetable,aPCequipped
withabeamer,andaSmartPhone,andasingleuser
4)Context4:Physicalenvironmentunchanged,platformiscomposedofaPCequippedwithabeamer,and
aSmartPhone,andasingleuser.
FigureUC7.2.(Left)ConnectingaSmartPhonetotheinteractivespacebylayingitdownontheinteractive
table.(Right)UsingtheSmartPhoneasaremotecontrollertobrowsephotosdisplayedbytheHTMLbased
UIcomponentofFigureUC7.1candvideoprojectedonthewall.
Inthisscenario,AliceenteringtheroomcorrespondstoasituationthattheContextManagerisableto
recognize:itisUserAliceandAlicehasenteredRoomAmbientSpace.TheactionthattheContext
ManagermustperformhasbeenspecifiedearlierbyAliceusinganenduserdevelopmenttool(orhasbeen
learntautomaticallybytheambientspaceandconfirmedbyAlice).Forexample,usingapseudonatural
languageprogramminglanguage,AlicehasinstructedthecontextmanagerthatwhenIenterRoom
AmbientSpace,pleasestartthetablewithmylastopenedphotoroll.Thissentenceisthentranslatedinto
anArchitecturalDescriptionLanguage(ADL)whoseinterpretationbyamiddlewareatruntimeautomatically
deploysorstopstheappropriatesoftwarecomponents.
TheUIofthemetaUIincludestherecognitionofthreegestures:(1)awipegesturethatallowstheuserto
commandthemigrationofthecurrentselectedphotofromthetabletothewall,(2)awipegesturethat
commandsthesystemtoshutdownthetable,and(3)thecontactoftheSmartPhonewiththeinteractive
table.
ThediagramofFigureUC7.3makesexplicittheuseofmodelsatruntime:fullcoverageofthecontextof
use,andremoldingperformedbyontheflytransformationofonesinglecomponent:thatoftheHTMLlike
CUItothenativeHTMLcodeofthetargetbrowserrunningonthePC.Theothercomponentsarenot
transformedbutaremetadescribedanddynamicallyrecruitedasresourcesoftheplatform.
UImodels
FigureUC7.3.ModelsusedinthePhotoBrowserusecase,andtheprocess.
8.TouristWebSite(TWS):MigratoryUIunderHumanControl
Contributors:
UniversityofGrenoble(GalleCalvary,JolleCoutaz)
TheTouristWebSite(TWS)providestouristswithinformationforvisitingandsojourningintheSedan
Bouillonarea,includingaselectionofhotels,camping,andrestaurants.TheUIofTWSiscentralizedwhen
usedfromaPCworkstation.Preparingatripforvacationisanexcitingexperiencewhensharedbyagroup
ofpeople(FigureUC8.1left).However,onesinglePCscreendoesnotnecessarilyfavorcollaborative
exploration.BydynamicallyloggingtothesamewebsitewithaSmartPhone,usersareinformedonthe
SmartPhonethattheycandistributetheUIcomponentsofthesiteacrosstheinteractionresourcescurrently
available.Usingaform,theuserasksforthefollowingconfiguration:thetitleofWebpagesmustappearon
theSmartPhoneaswellasonthePC(thetitleslotsaretickedforthetwobrowsersavailable),whereasthe
contentshouldstayonthePCwhosescreenisprojectedonthewall,andthenavigationbarshouldmigrate
totheSmartPhone(FigureUC8.1right).Thisform,whichallowuserstoreconfiguretheUIofTWSisthe
userinterfaceofthemetaUIofthesystem(Coutaz,2006).
ThekeyfunctionalrequirementstosupportUImigrationforTWSincludethecapacityto:
specifytheintentiontoredistributetheUI,
specifythesourcecontentelementsofwebpages,
specifythetargetdevicewheretodisplaythesourcecontent.
1)Context1:Physicalenvironmentisthatofahome,platformisaDesktopPC,onefamilymemberasa
singleuser.
2)Context2:Physicalenvironmentisthatofahome,platformiscomposedofaDesktopPCandofa
SmartPhone,familymembersasusers.
FigureUC8.1.TheTWSwebsite.UIcentralizedonaPCscreen(left).ThecontrolpanelofthemetaUIto
distributethepresentationunitsacrosstheresourcesoftheinteractiveambientspace(right).Thelinesof
thematrixcorrespondtothepiecesofcontentthatcanberedistributed,andthecolumnsdenotethe
browserscurrentlyusedbythesameuser.
Atanytime,theusercanaskforareconfigurationoftheUIbyselectingthemetaUIlinkinthenavigation
bar(FigureUC8.2).TheUIwillbereconfiguredaccordingly.Inthisexample,thefunctionsupportedbythe
metaUIisUIredistributionusingatypicalformbasedinteractiontechnique.
FigureUC8.2.TheTWSwebsitewhendistributedacrosstheresourcesoftheambientinteractivespace.
TheMetaUIlinkallowsuserstoreturntotheconfigurationpanelshownontherightofFigureUC8.1.
AsshowninFigureUC8.3fortheTWSexample,theFinalUIisabstractedawayatruntimeuptotheAUI
level.Inturn,thisAUIservesasinputforretargetingandredistributionusingacombinationoftheusers
requestproducedbythewayofthemetaUIandoftheplatformmodelmaintainedinthecontextofuse.The
diagramshowsthetransformationprocessgoingfromthePCcentralizedversiontothedistributedversion.
Thereverseprocessholdswhenmovingfromdistributedtocentralizeduse.
FigureUC8.3.ModelsusedintheTWSusecase,andtheprocess.
CommonGenericRequirements
Thissectionpresentsalistofnonfunctionalrequirementsthatmustdrivetheprocessofproducingvarious
modelsdefinedatdifferentabstractionlevelsfoundintheCRFandthatareapplicabletoanymetamodelling
approach.Theywereidentifiedbasedontheaforementionedusecases.Theserequirementsarenot
assumedtobeexhaustive,butratherareintendedtobeconstructiveinordertoensurethequalityofmeta
modelsandmodelsproducedaccordingtothesemetamodels.Eachrespectivemetamodelmayrefineany
genericrequirementintoaspecificrequirementthatpreciseshowtoaddresseachrequirementineach
specificcase.
GR1:Completeness.
Referstotheabilityofa(meta)modeltoabstractallrealworldaspectsofinterestviaappropriateconcepts,
attributes,andrelationships.Intheory,completenessisaimedatproducinga(meta)modelthatcoversall
realworldaspectsofinterest.Inpracticehowever,itmayturnoutthatnotallaspectsofinterestedcouldbe
capturedina(meta)model.Forthisreason,completenessissometimesreducedtoexpressiveness,which
referstotheabilityofa(meta)modelmodelstoabstractasignificantsubsetofrealworldaspectsofinterest
thatisconsideredenoughforthepurposeofitsusage.Asubpropertyofcompleteness,respectively
expressiveness,isthegraphicalcompleteness,respectivelygraphicalexpressiveness.Bothrefertothe
abilityofa(meta)modeltorepresentabstractionsrelevantforthis(meta)modelthroughappropriate
graphicalrepresentationsoftheconcepts,attributes,andrelationships.Notethatitisnotnecessarythatall
theconcepts,attributes,andrelationshipsofa(meta)modelshouldberepresentedgraphically.Therefore,
graphicalcompletenessisoftensubstitutedbygraphicalexpressiveness.
GR2:Consistency.
Consistencyisoftendecomposedintotwosubproperties:externalconsistencyandinternalconsistency.
Externalconsistencyreferstotheabilityofa(meta)modeltoproduceabstractionsoftherealworldthat
reproducethebehavioursoftherealworldaspectsofinterestinthesamewayandthatpreservesthis
behaviourthroughoutanymanipulationofthe(meta)model.Internalconsistencyreferstotheabilityoftwo
ormore(meta)modelstoproduceabstractionsaccordingtothesamemethodologicalapproach.This
includes:defineacommonvocabulary(e.g.,theglossary),usethisvocabularyinasystematicwayinevery
(meta)modellingactivitysoastoproduceabstractionsinthesameway,avoidnonuniquenames.Rulesfor
ensuringinternalconsistencycouldbedefinedinthisway.
GR3:SeparationofConcerns.
Referstotheabilityofa(meta)modeltoabstractanyrealworldaspectofinterestintoonesingleabstraction
belongingtoonesingle(meta)modelwithaslittleoverlappingaspossiblewithotherabstractionsbelonging
toother(meta)models.
GR4:Extensibility.
Referstotheabilityofa(meta)modeltoextendthedefinitionofexistingabstractionsformorespecific
purposeswithoutaffectingthestabilityoftheoveralldefinition.
GR5:Concision
Referstotheabilityofa(meta)modeltoproduceabstractionsofrealworldaspectsofinterestinawaythat
isascompactaspossiblewithrespecttotherealworld.ArelatedprincipletoconcisionistheDontrepeat
yourself(DRY)principle,whichreferstotheabilityofa(meta)modeltoproduceabstractionsofrealworld
aspectsofinterestinasingle,unambiguous,andauthoritativerepresentation.
GR6:Correlability.
Referstotheabilityofoneormore(meta)modelstoestablishrelationshipsbetweenthemselvesinorderto
representarealworldaspectofinterest.Therefore,correlabilityisoftendecomposedintointernalversus
externalcorrelabilitydependingonthetypeofrelationshipinvolved(intramodelversusintermodel).There
areseveralwaystoestablishrelationshipswithina(meta)modeloracross(meta)modelssuchas,butnot
limitedto:mapping,transformation,mathematicalrelationships.
ExamplesofTools
AnumberofmodelbasedUItoolsareavailablefordownload.Althoughmostofthemadheretothe
principlesoftheCameleonframework,noneofthem,sofar,implementstheMBUIDstandard.Table2below
presentthesetoolsinasyntheticmanner.Theinterestedreadercanaccessadetaileddescriptionofthetool
fromitsURL.
Table2.Examplesoftools
Design
CRF time/
Name Authors URL Levels Run Implementation
coverage time
tool
ConcurTaskTrees CNRISTI,
Design
Environment HIIS http://giove.isti.cnr.it/tools/CTTE/home Task Javaapplication
time
(CTTE) Laboratory
Modelbased
lAnguagefoR
Interactive CNRISTI, Task,
Design
Applications HIIS http://giove.isti.cnr.it/tools/MARIAE/home AUI,CUI, Javaapplication
time
Environment Laboratory FUI
(MARIAE)
Table2.Examplesoftools(continued).
Name FunctionalcoverageSpecificfeatures
ModellingandanalysisofsingleuserandcooperativeCTTtask
models.Indetail:
Visualise/Edittaskmodels
Interactivelysimulatetaskmodels
Automaticcheckthevalidity/completenessoftaskmodels
Savetaskmodelsinvariousformats
Supporttheuseofinformaldescriptionsfortaskmodelling
ConcurTaskTreesEnvironment Filternomadictaskmodelsaccordingtoplatform
(CTTE)
SupportmultipleinteractiveviewsofCTTtaskmodelspecification
SupportthegenerationofCTTtaskmodelsfromWSDL
SupportthegenerationofMariaAUIsfromCTTtaskmodels
SupportthegenerationofMariaCUIsforvariousplatforms(e.g.,
desktop,mobile,vocal,multimodal,..)
SupportthegenerationofMariaFUIsforvariousimplementation
languages(e.g.DesktopHTML,MobileHTML,X+VDesktop,X+V
Mobile,..)
ModellingandanalysisofvarioustypesofUImodels.
Indetail:
Visualise/EditTask/AUI/CUImodels
Editandapplymodeltransformations
ModelbasedlAnguagefoR SupportWebServicebaseddevelopmentofinteractiveapplications
InteractiveApplications
Environment SupportthesimulationofCTTtaskmodels
(MARIAE) SupportthegenerationofMariaAUIsfromCTTtaskmodels
SupportthegenerationofMariaCUIsforvariousplatforms(desktop,
mobile,vocal,multimodal,..)
SupportthegenerationofMariaFUIsforvariousimplementation
languages(e.g.DesktopHTML,MobileHTML,X+VDesktop,X+V
Mobile,..)
GlossaryofTerms
AseparateglossaryoftermsfortheModelBasedUserInterfacedomainhasbeenprovided.Itcontains
informal,commonlyagreeddefinitionsofrelevanttermsandexplanatoryresources(examples,linksetc.)
References
1.Ayatsuka,Y.,andRekimoto,J.:TranSticks:PhysicallyManipulatableVirtualConnections.In
ProceedingsoftheSIGCHIconferenceonHumanfactorsincomputingsystems(CHI2005),ACM
Press,NewYork,NY,pp.251260,2005.
2.BellottiV.,BackM.,EdwardsK.,GrinterR.,HendersonA.,andLopesC.MakingSenseofSensing
Systems:FiveQuestionsforDesignersandResearchers.InProceedingsoftheSIGCHIconferenceon
Humanfactorsincomputingsystems(CHI2002),ACMPress,NewYork,NY,2002,pp.415422,
2002.
3.Bodart,F.,Hennebert,A.M.,Leheureux,J.M.,Provot,I.,Vanderdonckt,J.,Modelbaseduser
interfacedesigninTridentwithDynamicSpecificationLanguage(DSL),IFIPWG2.7Workingconf.
(Namur,September1989).
4.Bodart,F.,Hennebert,A.M.,Leheureux,J.M.,Provot,I.,Vanderdonckt,J.,AModelbasedApproach
toPresentation:AContinuumfromTaskAnalysistoPrototype,Proc.of1stEurographicsWorkshopon
Design,Specification,VerificationofInteractiveSystemsDSVIS'94(BoccadiMagra,810June1994),
F.Patern(ed.),EurographicsSeries,Berlin,1994,pp.2539.
5.Bodart,F.,Hennebert,A.M.,Leheureux,J.M.,Vanderdonckt,J.,ComputerAidedWindow
IdentificationinTRIDENT,Proc.of5thIFIPTC13Int.Conf.onHumanComputerInteraction
INTERACT95(Lillehammer,2729June1995),K.Nordbyn,P.H.Helmersen,D.J.Gilmore,S.A.
Arnesen(eds.),Chapman&Hall,Loon,1995,pp.331336.
6.Bottoni,P.,Borgia,F.,Buccarella,D.,Capuano,D.,DeMarsico,M.,Labella,A.,Storiesandsignsinan
elearningenvironmentfordeafpeople,InternationalJournalofUniversalAccessintheInformation
Society,2012,10.1007/s102090120283y
7.Bouillon,L.,Vanderdonckt,J.,RetargetingWebPagestootherComputingPlatformswithVaquita,
Proc.ofIEEEWorkingConf.onReverseEngineeringWCRE2002(Richmond,28October1
November2002),A.vanDeursen,E.Burd(eds.),IEEEComputerSocietyPress,LosAlamitos,2002,
pp.339348.
8.Calvary,G.,Coutaz,J.,Thevenin,D.,AUnifyingReferenceFrameworkfortheDevelopmentofPlastic
UserInterfaces.Proc.ofEHCI2001,pp.173192.
9.Calvary,G.,Coutaz,J.,Thevenin,D.,Limbourg,Q.,Souchon,N.,Bouillon,L.,Florins,M.,
Vanderdonckt,J.,PlasticityofUserInterfaces:ARevisedReferenceFramework,Proc.of1stInt.
WorkshoponTaskModelsandDiagramsforuserinterfacedesignTamodia2002(Bucharest,1819
July2002),AcademyofEconomicStudiesofBucharest,INFORECPrintingHouse,Bucharest,2002,
pp.127134.
10.Calvary,G.etal.:TheCAMELEONReferenceFramework,CAMELEONProject,September2002,
availableathttp://giove.isti.cnr.it/projects/cameleon/pdf/CAMELEON%20D1.1RefFramework.pdf,2002.
11.Calvary,G.,Coutaz,J.,Thevenin,D.,Limbourg,Q.,Bouillon,L.,Vanderdonckt,J.,AUnifying
ReferenceFrameworkforMultiTargetUserInterfaces,InteractingwithComputers,Vol.15,No.3,
June2003,pp.289308.
12.Cantera,J.M.,W3CMBUIIncubatorGroupReport,2010,see
http://www.w3.org/2005/Incubator/modelbasedui/XGRmbui20100504/
mbui
13.Coleman,R.,Lebbon,C.,Clarkson,J.,&Keates,S.(2003).FromMarginstoMainstream,in:Inclusive
Design,DesignfortheWholePopulation,J.Clarksonetal.,eds,SpringerVerlag,pp.125.
14.Coutaz,J.,andCalvary,G.HCIandSoftwareEngineeringforUserInterfacePlasticity.InHuman
ComputerHandbook:Fundamentals,Evolvingtechnologies,andEmergingApplications,3rdedition,
JulieJackoEd.,TaylorandFrancisGroupLtdPubl.,May2012.
15.Coutaz,J.:MetaUserInterfaceforambientspaces.InProc.TAMODIA2006,5thinternational
workshoponTaskModelsandDiagramsforUserInterfaceDesign,TAMODIA2006,Coninx,Luyte,
SchneiderEds.,SpringerVerlagBerlin,pp.115,2006.
16.Coyette,A.,Kieffer,S.,Vanderdonckt,J.,MultiFidelityPrototypingofUserInterfaces,Proc.of11th
IFIPTC13Int.Conf.onHumanComputerInteractionInteract2007(RiodeJaneiro,September1014,
2007),LectureNotesinComputerScience,Vol.4662,SpringerVerlag,Berlin,2007,pp.149162.
BrianShackelAward2007forOutstandingContributionwithinternationalimpactinthefieldofHCI.
17.DaSilva,P.P.:UserInterfaceDeclarativeModelsandDevelopmentEnvironments:ASurvey.Proc.of
the7thInternationalConferenceonDesign,Specification,andVerificationofInteractiveSystems,pp.
207226,2000.
18.Eisenstein,J.andPuerta,A.R.(2000)Adaptationinautomateduserinterfacedesign.Proceedingsof
ACMInt.Conf.onIntelligentUserInterfacesIUI,ACMPress,NewYork,pp.7481.
19.EriksHoogland,I.E,deGroot,S.,Post,M.W.,&vanderWoude,L.H.(2009).Passiveshoulderrange
ofmotionimpairmentinspinalcordinjuryduringandoneyearafterrehabilitation.JRehabilMed.,May
2009,41(6):43844.
20.FernandezA.,AbrahoS.,andInsfranE.,Empiricalvalidationofausabilityinspectionmethodfor
modeldrivenWebdevelopment.JournalofSystemsandSoftware.Volume86Issue1January2013
Pages161186(2012).
21.SebastianFeuerstackandEdnaldoPizzolatoEngineeringDevicespanning,MultimodalWeb
ApplicationsusingaModelbasedDesignApproach,WebMedia2012,the18thBrazilianSymposium
onMultimediaandtheWeb,October1518,2012,SoPaulo/SP,Brazil.(Feuerstack2012a)
22.SebastianFeuerstackMINTComposerAToolchainfortheModelbasedSpecificationofPostWIMP
Interactors,acceptedforXIWorkshoponToolsandApplications,WebMedia2012,the18thBrazilian
SymposiumonMultimediaandtheWeb,October1518,2012,SoPaulo/SP,Brazil.
(Feuerstack2012b)
23.GarcaFrey,A.,Ceret,E.,DupuyChessa,S.,Calvary,G.,Gabillon,Y.UsiCOMP:anExtensibleModel
DrivenComposer,InProceedingsofthe4thACMSIGCHISymposiumonEngineeringInteractive
ComputingSystems(EICS2012).2012.
24.GarciaFrey,A.,Calvary,G.,DupuyChessa,S.,Mandran,N.ModelBasedSelfExplanatoryUIsfor
free,butaretheyvaluable?,14thIFIPTC13ConferenceonHumanComputerInteraction(Interact13),
LectureNotesinComputerScience(LNCS),Springer,September26,2013,CapeTown,SouthAfrica
25.Garlan,D.,Siewiorek,D.,Smailagic,A.andSteenkiste,P.ProjectAura:TowardsDistractionFree
PervasiveComputing.IEEEPervasiveComputing.Volume21,Number2,AprilJune,pp.2231,2002.
26.Ghiani,G.,Patern,F.,Santoro,C.(2011)UserInterfaceMigrationbasedontheuseoflogical
descriptions.MigratoryInteractiveapplicationsforubiquitousenvironments,pp.4559.
27.Grolaux,D.,VanRoy,P.,Vanderdonckt,J.,QTk:AMixedModelBasedApproachtoDesigning
ExecutableUserInterfaces,Proc.of8thIFIPWorkingConf.onEngineeringforHumanComputer
InteractionEHCI'01(Toronto,1113May2001),LectureNotesinComputerScience,Vol.2254,
SpringerVerlag,Berlin,2001,pp.109110
28.Grolaux,D.,VanRoy,P.,Vanderdonckt,J.,MigratableUserInterfaces:BeyondMigratoryUser
Interfaces,Proc.of1stIEEEACMAnnualInternationalConferenceonMobileandUbiquitous
Systems:NetworkingandServicesMobiquitous04(Boston,August2225,2004),IEEEComputer
SocietyPress,LosAlamitos,2004,pp.422430.
29.Grolaux,D.,Vanderdonckt,J.,VanRoy,P.,Attachme,Detachme,AssemblemelikeYouWork,Proc.
of10thIFIPTC13Int.Conf.onHumanComputerInteractionInteract2005(Rome,1216September
2005),LectureNotesinComputerScience,Vol.3585,SpringerVerlag,Berlin,2005,pp.198212.
30.Grolaux,D.(2007)TransparentMigrationandAdaptationinaGraphicalUserInterfaceToolkit,PhD
thesis,UniversitcatholiquedeLouvain,LouvainlaNeuve,2007.Availableat:
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.139.6201&rep=rep1&type=pdf
31.Hutchinson,J.,Whittle,J.,Rouncefield,M.,andKristoffersen,S.(2011)EmpiricalassessmentofMDE
inindustry,Proceedingsofthe33rdInternationalConferenceonSoftwareEngineeringICSE'2011,
ACMPress,NewYork,pp.471480.
32.IBM(2001)AutonomicComputing:IBMsPerspectiveontheStateofInformationTechnology.Seealso
TheVisionofAutonomicComputing,JeffreyO.Kephart,DavidM.Chess,IBMThomasJ.Watson
ResearchCenter.
33.Integranova,2012.(IntranovaModelExecutionSystem)
34.Izadi,S.,Brignull,H.,Rodden,T.,Rogers,Y.,andUnderwood,M.2003.Dynamo:apublicinteractive
surfacesupportingthecooperativesharingandexchangeofmedia.ProceedingsofUserInterface
SoftwareandTechnologyUIST2003)(Vancouver,Canada),ACMPress,NewYork,pp.159168.
35.JohansonB.,FoxA.,andWinogradT.:TheInteractiveWorkspaceProject:Experienceswith
UbiquitousComputingRooms.IEEEPervasiveComputingMagazine1(2),AprilJune2002.
36.Kaklanis,N.,Moschonas,P.,Moustakas,K.,andTzovaras.D.(2010)Enforcingaccessibledesignof
productsandservicesthroughsimulatedaccessibilityevaluation",InternationalConferenceonICTfor
ageingandeInclusion,CONFIDENCE2010,Jyvaskyla,Finland.
37.M.Manca,F.Patern,C.Santoro,L.D.Spano,GenerationofMultiDeviceAdaptiveMultiModalWeb
Applications,ProceedingsMobiWIS2013,LNCSN.8093,pp.218232,SpringerVerlag,August2013
38.Masson,D.,Demeure,A.,Calvary,G.Magellan,anevolutionarysystemtofosteruserinterfacedesign
creativity.InProceedingsofthe2ndACMSIGCHIsymposiumonEngineeringinteractivecomputing
systems(EICS'10).ACM,NewYork,NY,USA,8792.
39.Meixner,G.,Patern,F.,andVanderdonckt,J.:Past,Present,andFutureofModelBasedUser
InterfaceDevelopment.icom,10,3(2011),211.
40.Mitrovic,N.,Royo,J.A.,andMena,E.(2007)PerformanceAnalysisofanAdaptiveUserInterface
SystemBasedonMobileAgents,Proc.ofEHCI/DSVIS2007,pp.117.
41.Models@runtime(2009).Specialissueonmodelsatruntime.IEEEComputerSpecialIssues,Vol.42,
No.10.Availableat:http://www.computer.org/csdl/mags/co/2009/10/index.html
42.Mori,G.,Patern,F.,Spano,L.D.(2008)ExploitingWebServicesandModelBasedUserInterfacesfor
MultideviceaccesstoHomeapplications.DSVIS2008,pp.181193.
43.Myers,B.Rosson,M.B.:SurveyonUserInterfaceProgramming.Proc.ofthe10thAnnualCHI
ConferenceonHumanFactorsinComputingSystems,pp.195202,2000.
44.PeaGuevara,J.C.,BerumenNafarrete,E.,AguirreMadrid,A.,VallejoPonce,J.,DelaRivaMuoz,
I.,&NezValdez,J.A.(2005).Anatomicallydesignedshoulderhemiarthroplastymadeafter3D
modelsandimplantedinachildwithrheumatoidarthritis.Acasereport.ActaOrtopdicaMexicana,
vol.19,MayJune2005.
45.Pilemalm,S.,Hallberg,N.,Sparf,M.,andNiclason,T.(Dec.2012)Practicalexperiencesofmodel
baseddevelopment:CasestudiesfromtheSwedishArmedForces,SystemsEngineering,Volume15
Issue4,pp.407421.
46.StreitzN.,TandlerP.,MllerTomfeldeC.,andKonomiS.Roomware:TowardstheNextGenerationof
HumanComputerInteractionbasedonanIntegratedDesignofRealandVirtualWorlds.InHuman
ComputerInteractionintheNewMillenium,CarrollJ.(Ed.),AddisonWesley,pp.553578,2001.
47.Rodden,T.,Crabtree,A.,Hemmings,T.,Koleva,B.,Humble,J.,Akesson,K.P.,andHansson,P.
ConfiguringtheUbiquitousHome.InProceedingsofthe2004ACMSymposiumonDesigning
InteractiveSystems(DIS04)(Cambridge,Massachusetts),ACMPress,2004.
48.Seffah,A.,&Javahery,H.MultipleuserInterfaces:CrossPlatformApplicationsandContextAware
Interfaces.InA.Seffah&H.Javahery(Eds.),MultipleUserInterfaces:EngineeringandApplication
Framework(pp.1126).Chichester(GB):WileyandSons,2004.
49.Seissler,M.ModellbasierteEntwicklungkontextsensitiverBenutzungsschnittstellenzurUntersttzung
dermobilenInstandhaltung,PhDthesis,FortschrittBerichtepak,Band24,Universityof
Kaiserslautern,2013.
50.Steenbekkers,L.P.A.,&vanBeijsterveldt,C.E.M.(Eds.)(1998).Designrelevantcharacteristicsof
ageingusers.Delft,theNetherlands:DelftUniversityPress.
51.Szekely,P.:RetrospectiveandChallengesforModelBasedInterfaceDevelopment.Proc.ofthe3rd
InternationalEurographicsWorkshop,pp.127,1996.
52.Thevenin,D.,andCoutaz,J.:PlasticityofUserInterfaces:FrameworkandResearchAgenda.InProc.
Interact99,Edinburgh,A.Sasse&C.JohnsonEds,IFIPIOSPressPubl.,pp.110117,1999.
53.Vanderdonckt,J.,Priseencomptedesfacteursergonomiquesdanslaconceptiondesinterfaces
hommemachine,ActesdesjournesdetravaildeBeaune'91(Beaune,57March1991),M.Adiba,F.
Bodart,M.Lonard,Y.Pigneur(eds.),LesditionsSystmesetInformation,Genve,1991.
54.Vanderdonckt,J.Bodart,F.:EncapsulatingKnowledgeforIntelligentAutomaticInteractionObjects
Selection.Proc.oftheACMConf.onHumanFactorsinComputingSystems.ACMPress,NewYork,
pp.424429,1993.
55.WHO,WorldHeathOrganisation:Theworldisfastageinghavewenoticed?
http://www.who.int/ageing/en/,2007.
56.Zackowski,K.M.,Dromerick,A.W.,Sahrmann,S.A.,Thach,W.T.,&Bastian,A.J.(2004).Howdo
strength,sensation,spasticityandjointindividuationrelatetothereachingdeficitsofpeoplewith
chronichemiparesis?.Brain(2004),127,10351046.
57.Petrasch,R.:Modelbaseduserinterfacedesign:modeldrivenarchitectureundHCIpatterns.GI
SoftwaretechnikTrends,MittGesInform27(3):510.
58.Pilemalm,S,Hallberg,N,Sparf,MandNiclasson,T.(2012)PracticalExperiencesofModelbased
Development:CasestudiesfromtheSwedishArmedForces,toappearinJournalofSystems
Engineering,Vol.15,No.3.
Acknowledgements
Inadditiontotheeditors,thefollowingpeoplecontributedtothisspecification:
FranoisBeuvens,LILab,UCL
PaoloBottoni,DipartimentodiInformatica,SapienzaUniversitdiRoma
CristinaG.Cachn,FundacionCTIC
JavierR.Escolar,FundacionCTIC
SebastianFeuerstack,OFFISe.V.
NikolaosKaklanis,CENTREFORRESEARCHANDTECHNOLOGYHELLAS
IgnacioMarn,FundacionCTIC
VivianMotti,LILab,UCL
MariusOrfgen,DFKI
FabioPatern,ISTICNR
JaroslavPullmann,FraunhoferGesellschaft
LucioDavideSpano,ISTICNR
CarmenSantoro,ISTICNR
JeanVanderdonckt,LILab,UCL

Introduction To Model-Based User Interfaces

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Introduction To Model-Based User Interfaces

Încărcat de

Drepturi de autor:

Formate disponibile

1/12/2017 IntroductiontoModelBasedUserInterfaces

S-ar putea să vă placă și