Model-Driven HMI Development: Can Meta-CASE Tools do the Job?

Bock, Carsten

doi:10.1109/hicss.2007.385

Cited by 7 publications

(3 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Coordinating such a multi-peered development process makes detailed specifications in advance of the development work necessary which stretches the time necessary for the requirement engineering process. As the development of the IC relies on the data provided by the ECUs, changes in the requirements raise the need of iterative development throughout the whole engineering and development process [2]. Figure 1 documents a basic development process for an IC.…”

Section: Instrument Cluster Objects and Structurementioning

confidence: 99%

“…These cycles involve multiple iterations of requirements and changes, most often carried out by suppliers [2] as the majority of devices are not developed by the vehicle original equipment manufacturer (OEM ) itself. The iterations are time consuming and resource-intensive [10] as different tools and varying simulation-based environments are used during the development phases of an interface.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Hardware-in-the-loop-based evaluation platform for automotive instrument cluster development (EPIC)

Osswald¹,

Sheth²,

Tscheligi

2013

Proceedings of the 5th ACM SIGCHI Symposium on Engineering Interactive Computing Systems

View full text Add to dashboard Cite

This paper offers a contribution for platform-based evaluation techniques by proposing a hardware-in-the-loop-based approach for automotive instrument cluster (IC) development. An automotive IC interface requires for special attention as it provides the driver with safety-relevant information like speed or state of charge that is critical for the driving situation. As state of the art in-vehicle Human-MachineInterfaces (HMI) are mostly embedded systems that make time-consuming research and development processes necessary, we propose a development platform that allows for a more rapid interface implementation and analysis. The evaluation platform for ICs (EPIC) is targeted at supporting engineers and researchers during the development phase of novel interface solutions that are reliable regarding their hardware connectivity and signal communication. It consists of a model-based vehicle simulation combined with automotive hardware to enable a real-time vehicle structure through a controller area network (CAN). Interchangeable, Androidbased interfaces illustrate the flexibility of the approach and show the operability of the evaluation platform. To illustrate the applicability of the approach, the platform was embedded in an engineering process for an electric vehicle to address the challenge of user interface development.

show abstract

Section: Instrument Cluster Objects and Structurementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Hardware-in-the-loop-based evaluation platform for automotive instrument cluster development (EPIC)

Osswald¹,

Sheth²,

Tscheligi

2013

Proceedings of the 5th ACM SIGCHI Symposium on Engineering Interactive Computing Systems

View full text Add to dashboard Cite

show abstract

“…Our experience from a comparison of different specification tools and interviews with developers reveals that especially these individual, domain-specific symbols lead to a very small semantic distance between the specification language and real-word objects of the driver-information system domain. Most notably this strongly increases developers' acceptance of tailor-made CASE tool [33].…”

Section: Developing a Model-driven Tool Chain For Ui Specificationmentioning

confidence: 99%

Model-Driven Prototyping for Corporate Software Specification

Memmel

Bock²,

Reiterer

2008

Engineering Interactive Systems

Self Cite

View full text Add to dashboard Cite

Abstract. Corporate software development faces very demanding challenges, especially concerning the design of user interfaces. Collaborative design with stakeholders demands modeling methods that everybody can understand and apply. But when using traditional, paper-based methods to gather and document requirements, an IT organization often experiences frustrating communication issues between the business and development teams. We present ways of implementing model-driven prototyping for corporate software development. Without harming agile principles and practice, detailed prototypes can be employed for collaborative design. Model-driven prototyping beats a new path towards visual specifications and the substitution of paper-based artifacts.

show abstract