View
219
Download
0
Category
Preview:
Citation preview
Stanford University 1 CADUI'96 - 5-7 June 1996 - FUNDP Namur
The Mecano ProjectThe Mecano Project
Angel R. Puerta
Knowledge Systems LaboratoryStanford University
Stanford (USA)
Stanford University 2 CADUI'96 - 5-7 June 1996 - FUNDP Namur
OutlineOutline
• Mecano• The Mecano Project• Phase I: Modeling Language• Phase II: Software Environment
Stanford University 3 CADUI'96 - 5-7 June 1996 - FUNDP Namur
Mecano (1992-1994)Mecano (1992-1994)
• Environment to automate interface design for knowledge-acquisition tools
• Domain-driven interface generation• Target interfaces:
– Form and graph-based interfaces
• Current Uses:– Medical and educational applications
Stanford University 4 CADUI'96 - 5-7 June 1996 - FUNDP Namur
Mecano Target Interfaces (1)Mecano Target Interfaces (1)
Entry forms for medical treatment specification interface (over 60 windows total)
Entry forms for medical treatment specification interface (over 60 windows total)
Stanford University 5 CADUI'96 - 5-7 June 1996 - FUNDP Namur
Mecano Target Interfaces (2)Mecano Target Interfaces (2)
Domain-specific graphical editor
Domain-specific graphical editor
Stanford University 6 CADUI'96 - 5-7 June 1996 - FUNDP Namur
Mecano ParadigmMecano Paradigm
Domain model provides information needed to build an application-specific design from the generic interface model
Domain model provides information needed to build an application-specific design from the generic interface model
DomainModel
DomainModel
Generic Interface
Model
Generic Interface
Model
Automatic Designer
Automatic Designer
Application-SpecificInterfaceDesign
Application-SpecificInterfaceDesign
Stanford University 7 CADUI'96 - 5-7 June 1996 - FUNDP Namur
The Mecano ProjectThe Mecano Project
• A model-based approach to:– Define a comprehensive ontology of user interfaces
– Develop an open architecture supporting interface development for the interface ontology
– Provide a standard resource to the HCI community
Stanford University 8 CADUI'96 - 5-7 June 1996 - FUNDP Namur
The Mecano Project ParadigmThe Mecano Project Paradigm
Editors
DesignExploration
Critics
AutomaticDesign
DesignAssistants
Workplace
User
Platform
Behavior
Dialogue
Tasks
Application
Presentation
Workplace
User
Platform
Behavior
Dialogue
Tasks
Application
Presentation
Refinements
GeneratedInterface
RuntimeSystem
Generic
Design Tools Interface Model
Stanford University 9 CADUI'96 - 5-7 June 1996 - FUNDP Namur
Phase I: Interface Ontology StrategyPhase I: Interface Ontology Strategy
• Examination of existing MB systems• Definition of a modeling language• Definition of interface ontology
Stanford University 10 CADUI'96 - 5-7 June 1996 - FUNDP Namur
Problems with Existing SystemsProblems with Existing Systems
• Partial interface models• Insufficient underlying modeling paradigm• System-dependent models• Inflexible models• Private models
Stanford University 11 CADUI'96 - 5-7 June 1996 - FUNDP Namur
The MIMIC Modeling LanguageThe MIMIC Modeling Language– A metalevel approach to modeling
– Is NOT an interface modeling language
– Defines structure and organization for interface models
– Offers component-based view
– Assigns explicit roles to interface components
– Discards the idea of single generic interface models
– Allows the definition of Mecano Interface Models (MIMs)
Stanford University 12 CADUI'96 - 5-7 June 1996 - FUNDP Namur
MIMIC & MIMMIMIC & MIMMeta-Level Modeling:
MIMIC
Generic Models:MIM
Application-SpecificModels
Organization andStructure
Vocabulary
InterfaceSpecifications
define
refine into
Stanford University 13 CADUI'96 - 5-7 June 1996 - FUNDP Namur
Key MIMIC Underlying ConceptsKey MIMIC Underlying Concepts
• Interface:– A set of objects belonging to the interface model
components
• Interface Design:– The relationships among the objects in an interface
Stanford University 14 CADUI'96 - 5-7 June 1996 - FUNDP Namur
MIMIC Interface ComponentsMIMIC Interface Components
• Object Components– User task, domain, presentation, dialog, user...
• Design Component
<interface> ::= <interface-definition>*<model-component>+
<model-component> ::= <user-task-model>+ | <domain-model>+ | <presentation-model>+ | <dialog-model>+ | <user-model>+ | <design-model>+
<interface> ::= <interface-definition>*<model-component>+
<model-component> ::= <user-task-model>+ | <domain-model>+ | <presentation-model>+ | <dialog-model>+ | <user-model>+ | <design-model>+
Stanford University 15 CADUI'96 - 5-7 June 1996 - FUNDP Namur
Validation of MIM ModelsValidation of MIM Models
• Paper-based validation– Developers wrote interfaces using MIMIC & MIM
• Interfaces of various complexities– Toy-level
– Geometry editor
– Portions of a web browser
Stanford University 16 CADUI'96 - 5-7 June 1996 - FUNDP Namur
Phase Two: Tool SupportPhase Two: Tool Support
• Model-Based Interface Designer (Mobi-D)• Integrated environment/ Open architecture• Interactive tools for each model component• No automatic generation of interfaces• Developer-driven interface generation
Stanford University 17 CADUI'96 - 5-7 June 1996 - FUNDP Namur
MIMIC interface componentsMIMIC interface componentsand Mobi-D toolsand Mobi-D tools
• Each interface component requires one (or more) Mobi-D tools
• MIMIC does not limit the representation of interface components
<user-task-model> ::= <user-task-model> ::= <name> <user-task-definition>*<name> <user-task-definition>*
<user-task>+<user-task>+
<user-task> ::=<user-task> ::= <name> <task-relation>* <goal><name> <task-relation>* <goal>
<subtask>* <execution-order><subtask>* <execution-order>
<condition>* <task-attribute>**<condition>* <task-attribute>**
<user-task-model> ::= <user-task-model> ::= <name> <user-task-definition>*<name> <user-task-definition>*
<user-task>+<user-task>+
<user-task> ::=<user-task> ::= <name> <task-relation>* <goal><name> <task-relation>* <goal>
<subtask>* <execution-order><subtask>* <execution-order>
<condition>* <task-attribute>**<condition>* <task-attribute>**
Stanford University 18 CADUI'96 - 5-7 June 1996 - FUNDP Namur
MOBI-D: Model Component EditorMOBI-D: Model Component Editor
Generic model area provides ready-made objects for interface model construction
Generic model area provides ready-made objects for interface model construction
Properties area allow editing of attributes
Properties area allow editing of attributes
Stanford University 19 CADUI'96 - 5-7 June 1996 - FUNDP Namur
MOBI-D: Creating a User-Task ModelMOBI-D: Creating a User-Task Model
1 1
1. Developer drags generic task object into current model
2. Developer modifies default attributes as needed
3. Optionally, developer adds new task to generic area for potential future use
1. Developer drags generic task object into current model
2. Developer modifies default attributes as needed
3. Optionally, developer adds new task to generic area for potential future use
3 3
2
2
Stanford University 20 CADUI'96 - 5-7 June 1996 - FUNDP Namur
MOBI-D: Creating a Domain ModelMOBI-D: Creating a Domain Model
Interaction is similar to that of the user task editor Developers benefit from a common interaction paradigm for all model components
Interaction is similar to that of the user task editor Developers benefit from a common interaction paradigm for all model components
Stanford University 21 CADUI'96 - 5-7 June 1996 - FUNDP Namur
MOBI-D: Putting It all TogetherMOBI-D: Putting It all Together with Design Views with Design Views
Developer has switched pane from generic to design viewAll interface model elements related to ‘loading the cannon’ are displayedAdditional related elements can be dragged-and-dropped from other model component editors
Developer has switched pane from generic to design viewAll interface model elements related to ‘loading the cannon’ are displayedAdditional related elements can be dragged-and-dropped from other model component editors
These items were recommended by MOBI-D and accepted by developer
These items were recommended by MOBI-D and accepted by developer
Stanford University 22 CADUI'96 - 5-7 June 1996 - FUNDP Namur
SummarySummary
• Metalevel approach to modeling • Multiple generic models• Multiple interface components allowed• Component-based tool support• Developer-driven interface generation
Stanford University 23 CADUI'96 - 5-7 June 1996 - FUNDP Namur
Vision for MecanoVision for Mecano
• MIMIC & MIM available to HCI community• Developers build many additional generic models• Mobi-D available• Developers add tools to open architecture• Integration with application development
environments
Recommended