Figure 8 - uploaded by Davide Bolchini
Content may be subject to copyright.
Citations
... They can quickly brainstorm, evaluate and discuss the design issues. 33 Thus, the IDM design technique has received much acceptance for interactive and content-intensive applications and multichannel features. ...
... IDM is a dialogue-based design technique that includes the phases of IDM: C-IDM, L-IDM, and P-IDM. 33 Bolchini and Garzotto 33 discuss the various features and functions of the IDM techniques for designing multichannel web systems. Similarly, Bolchini and Polini 8 addressed how IDM can be used to design multichannel applications. ...
The design and info‐architecture of the web content contribute significantly to achieving better usability and user experience as well as to adopting a website to its intended end‐users. Although several design techniques exist, choosing a suitable one for designing a particular type of website is difficult and needs further investigation. Thus, the objective of this research is to explore the impact of a design technique on web usability and to find out the best suitable design technique for a particular type of website. To achieve these objectives, two separate websites for providing electronic health services named Citizen Health Service portal were developed using the two mostly used design techniques, namely card sorting and interactive dialogue model (IDM). The usability of both websites was evaluated through a laboratory‐based usability testing approach with 20 participants. The study result showed that the IDM performs better in designing such an information‐intensive website.
... All ranks thus needed to traverse such environment multidimensionally that highlight the importance of developing multichannel applications to satisfy the needs of military forces. A multichannel application is referred to the application that is versatile in multiple platforms and provides same services through various channels/devices like mobile, web, and desktops [17,18]. Thus, a unique set of challenges are required to address to achieve the key quality (usability) of a military application. ...
... The web application was designed and developed following the interactive dialog model (IDM) approach [17]. The IDM is a novel design model specifically tailored for multichannel (e.g., web and mobile channel/platforms) applications that helps firstly to design the channel-independent "conceptual" design and then design the channel-dependent "logical" design [17,18]. The IDM-based logical design (L-IDM) of the web and mobile application is shown in Fig. 2. ...
Usability is the key quality attribute of any software system. Military forces are designed to deal with unexpected situations in the battlefield, thus the military applications are used in a specific context like war, minor operations, special operations (counter terrorism, natural disaster), etc. by the specific group of users/soldiers. The existing usability factors are mainly used to evaluate the general-purpose applications like e-commerce, e-governance, etc. but may not be suitable for the design and evaluation of military applications. Moreover, no specific set of usability factors or metrices were suggested in existing literature to design and evaluate military applications. Therefore, the objectives of this research were firstly, to reveal the all possible usability factors that would be suitable for designing, developing and evaluating any military application and secondly, to show the applicability of these factors to evaluate a military application from HCI perspective. As such, an "Advanced Battlefield Communication System" was developed to support the command structure for enabling the higher commanders by establishing an audio-video communication link with the front-line troops. An explorative study was conducted following the Focused Group Discussion (FGD) with 20 participants to reveal the all possible usability factors for developing and evaluating any military application; while an evaluation study was conducted through field study with 30 participants to assess the applicability of the revealed usability factors. As outcomes, (a) an advanced battlefield communication system was developed for military; and (b) a total of fourteen usability factors were revealed and validated for designing and evaluating military applications, where most of the factors were new and innovative like chain-of-command supportive, placement and integration of system accessories, lightness/weight of accessories, and health hazard.
... Previously, different hypertext applications used to be designed using the "page by page" design approach (Bolchini & Garzotto, 2008), that means an application containing several interconnected links were developed by designing a particular page and then moving on to the next hyper-linked page. This approach is usually unable to reflect the user requirements completely as designing an individual page successively results in a partial content representation of an application. ...
... As a result, to fulfill the user requirements for interactive hypertext applications, HDM (hypertext design model) has been introduced (Garzotto et al., 1993), where the authors have presented a design and browsing schema that help to understand how the user requirements can be organized in a user interactive way by classifying the requirements into different entities and structural links from different perspectives. Next, to deal with the increasing and complex user requirements, the IDM has been proposed in (Bolchini & Paolini, 2006;Bolchini & Garzotto, 2008). Bolchini and Paolini (2006) highlighted the usage of IDM for designing multi-channel applications. ...
At present, web applications are one of the most widely used software applications in different organizations. A website is a virtual representation of the structure of any organization. Good user experience of a website is highly dependent on the content organization or design of a website. Thus, the design is a very important factor to develop a high usability standard website. Different types of design techniques are used to develop different types of websites. It is a very challenging task to develop information-intensive websites using a suitable design technique so that the website can serve its intended purpose with enhanced usability and user experience. Therefore, the objective of this research is to compare the performance of two alternate design techniques for developing an information-intensive website. To achieve this objective, the existing design techniques were explored; and selected the Card Sorting and Interactive Dialogue Model (IDM) techniques to design two websites for an orphanage system. Later, the developed orphanage web systems were evaluated with ten participants through a user study;and found that the IDM design technique performs better than the Card Sorting technique in terms of the system’s usability and user experience.
... Our model, called IDM++, is a revision of IDM -Interactive Dialogue Model, which has been developed in the web engineering community as a tools to represent design decisions for content-intensive web applications delivered on desktop or mobile platforms [3]. As in IDM, the IDM++ design process comprises three main activities: Conceptual Design, Logical Design, and Presentation Design. ...
... The IDM++ extensions to IDM mainly concern Presentation Design and are originated by the need of modelling the specifics of the interaction paradigms available in different devices, including TMI. The rest of this section provides a brief mention of the primitives for Conceptual and Logical Design (the reader is referred to [3] for details) and offers a more extensive discussion of IDM++ features for Presentation design. ...
With the increasingly low cost of motion-sensing technology, touchless interactive interfaces may become a new ingredient in the evolution of content intensive web applications from single-platform (desktop) to multi-platforms use. While the migration from desktop to mobile devices has been widely studied, there is limited understanding on how to include touchless interfaces in this "going multi-channel" evolution. The paper focuses on the design issues that are induced by this process. We propose a model-based design approach that supports information reuse and exploits a systematic mapping from content structures to interaction tasks and touchless gestures. We then describe a case study in the cultural heritage domain to exemplify our method.
... Existing web modelling languages have rarely discussed the issue of form validation. During our literature review of OOWS [6], OOHDM [7], UWE [8], IDM [9], WebML [10], Hera [11], and WSDM [12], we did not find references addressing form validation. Additionally, the code generators UWE4JSF [13] for UWE, OOHDMDA [14] for OOHDM, and HPG [15] for Hera, do not have form validation included. WebRatio [16] for WebML includes form validation by adding validation rules to entry units that are part of its domain-specific language (DSL). ...
Form validation is an integral part of a web application. Web developers must ensure that data input by the user is validated for correctness. Given the importance of form validation it must be considered as part of a model-driven solution to web development. Existing model-driven approaches typically have not addressed form validation as part of the model. In this paper, we present an approach that allows validation constraints to be captured within a model using UML and OCL. Our approach covers three common types of validation: single element, multiple element, and entity association. We provide an example to illustrate an architecture-centric approach.
Software development is a complex and difficult task that requires the investment of significant resources and carries major risk of failure. For decades now, researchers have proposed “model-driven” approaches to improve the state of the art in software engineering. Software models are intended to improve communication among stakeholders and aid in the overall understanding both of a problem space and a proposed software solution that satisfies given requirements. As with architectural blueprints or miniature 3D models, software models make it possible to explore and test a design and its ramifications before investing in the actual build-out. The traditional approach to software development involves a modeling process – analysis, requirements specification, design – followed by an implementation process. In the traditional approach, programmers manually write software that conforms (more or less) to specifications described in software models; this process involves transformations that are often incomplete, awkward, and informal. The essence of model-driven software development is the idea that software models can go further than being mere blueprints, and constitute the basis for automatically or semiautomatically generating the software system itself. In this chapter, we survey various major approaches to model-driven software construction and illustrate how model-driven development works in practice.
To be adopted by architects, modelling approaches must provide a means to leverage the software patterns and architectural styles that are relevant to development practice, instead of those proscribed by black-box CASE tools. Architecture-Centric Model-Driven Software Development (AC-MDSD) is a modelling approach that provides architectural control of the generated application. However, AC-MDSD primarily focuses on generating infrastructure code. We apply AC-MDSD to web engineering and contribute a technique to define and generate system behaviour that goes beyond the create/read/update/delete infrastructure functionality. We use UML profiles augmented with OCL to specify the behaviour. We provide an example to illustrate the approach and outcomes.
