Transforming an HCI Model to a Software Design Model

Author(s):  
Andrew M. Olson

The software engineering and human factors communities are seeking ways to integrate their methodologies. This paper outlines an amplified, software engineering methodology that extends beyond requirements gathering to encompass human factors analyses. The methodology employs an object model that is uniform throughout the software project. It involves a procedure that seamlessly transforms a task action grammar model, from HCI theory, directly into a specification model based on user/machine dialog and, thence, into a software design model. The model's object-oriented structure makes it feasible to trace the effects of the user's needs throughout the amplified project life cycle to the final code. A case study documents evidence concerning how effectively the procedure supports the software engineering process. An examination of the extent of metamorphosis the model undergoes in the case study indicates that the transition through the amplified life history is well controlled; in particular, the transition from the software specification to the design model is more controlled than that under traditional methodologies.

2017 ◽  
Vol 21 (1) ◽  
pp. 71-79
Author(s):  
Jai Vigneshwar Alavandhar ◽  
Oksana Ņikiforova

Abstract In order to develop and deliver a software project successfully, any software development organisation has to follow a well-known and recognised software engineering process for successful delivery and maintenance of the software. However, when the organisation is willing to follow a new software development process, the success rate of adopting a new software engineering process is a question mark. In the paper, we aim at studying and comparing two software engineering processes, which are based on different paradigms or models, and proposing a hybrid methodology, which integrates advantages of both compared methods. They are Microsoft Solutions Framework as a representative for an iterative methodology and SCRUM for agile software development. The comparative analysis will help a software development company to make the transition easier from Microsoft Solutions Framework to SCRUM or vice versa.


2011 ◽  
pp. 277-316 ◽  
Author(s):  
Kuldar Taveter

This chapter proposes a new agent-oriented software engineering process called RAP, which follows the Rational Unified Process (RUP) in many ways, but is based on Agent-Object-Relationship (AOR) modelling instead of object-oriented modelling. The chapter briefly presents the foundational ontology that supports the methodology and introduces the RAP/AOR viewpoint modelling framework. It then describes the modelling from the interaction, information, and behavior aspects of the framework by using a case study of business-to-business electronic commerce. Finally, the chapter describes an implementation approach based on the Model Driven


2014 ◽  
Vol 644-650 ◽  
pp. 2821-2825
Author(s):  
Zhong Lin He ◽  
Xiao Hong Xiao ◽  
Yu Hua He

Big data is mainly for analytic applications, which puts high requirements on data processing ability instead of computational accuracy. In this environment, software engineering-based methods should be carried out with the goal of data processing and computation. To adapt to the development of various analytic applications in big data era, this paper provides a software design model based on big data, and at the same time, analyzes compiler mechanism of big data programming language.


Author(s):  
Kurt Schneider

This paper introduces an approach to modeling software project dynamics using an attributed graph grammar formalism. A project situation is modeled and presented to a "player" who is supposed to act as project manager of a simulated project. Events and internal processes of the simulated project are modeled using a custom-designed formalism that integrates attributed graph grammar concepts with a quantitative simulation mechanism resembling System Dynamics. Both ingredients were pragmatically selected and blended based on (1) their comparative simplicity, (2) their expressive power, and (3) their intuitive appeal for bridging the cognitive gap between real-world software engineering experiences and an executable simulation model. This modeling formalism was applied in the SESAM educational software engineering game. The modeling formalism was supported by a family of graphical SESAM editors. Resulting models could be animated and served as simulated projects in the game runs. SESAM was applied in graduate courses on software project management at the University of Stuttgart. Experiences with the modeling approach are reported. The design history and design rationale that led to using graph grammars as the underlying formalism are described and discussed. The design of the SESAM modeling formalism is presented as an (involuntary) case study in adopting a graph grammar approach.


2003 ◽  
Vol 42 (01) ◽  
pp. 37-44 ◽  
Author(s):  
R. Lenz ◽  
T. Elstner ◽  
H. Siegele ◽  
R. Moll ◽  
K.A. Kuhn

Summary Objectives: To elaborate main system characteristics and relevant deployment experiences for the health information system (HIS) Orbis®/ OpenMed, which is in widespread use in Germany, Austria, and Switzerland. Methods: In a deployment phase of 3 years in a 1.200 bed university hospital, where the system underwent significant improvements, the system’s functionality and its software design have been analyzed in detail. We focus on an integrated CASE tool for generating embedded clinical applications and for incremental system evolution. We present a participatory and iterative software engineering process developed for efficient utilization of such a tool. Results: The system’s functionality is comparable to other commercial products’ functionality; its components are embedded in a vendor-specific application framework, and standard interfaces are being used for connecting subsystems. The integrated generator tool is a remarkable feature; it became a key factor of our project. Tool generated applications are workflow enabled and embedded into the overall data base schema. Rapid prototyping and iterative refinement are supported, so application modules can be adapted to the users’ work practice. Conclusions: We consider tools supporting an iterative and participatory software engineering process highly relevant for health information system architects. The potential of a system to continuously evolve and to be effectively adapted to changing needs may be more important than sophisticated but hard-coded HIS functionality. More work will focus on HIS software design and on software engineering. Methods and tools are needed for quick and robust adaptation of systems to health care processes and changing requirements.


Author(s):  
Mirette Dubé ◽  
Jason Laberge ◽  
Elaine Sigalet ◽  
Jonas Shultz ◽  
Christine Vis ◽  
...  

Purpose: The aim of this article is to provide a case study example of the preopening phase of an interventional trauma operating room (ITOR) using systems-focused simulation and human factor evaluations for healthcare environment commissioning. Background: Systems-focused simulation, underpinned by human factors science, is increasingly being used as a quality improvement tool to test and evaluate healthcare spaces with the stakeholders that use them. Purposeful real-to-life simulated events are rehearsed to allow healthcare teams opportunity to identify what is working well and what needs improvement within the work system such as tasks, environments, and processes that support the delivery of healthcare services. This project highlights salient evaluation objectives and methods used within the clinical commissioning phase of one of the first ITORs in Canada. Methods: A multistaged evaluation project to support clinical commissioning was facilitated engaging 24 stakeholder groups. Key evaluation objectives highlighted include the evaluation of two transport routes, switching of operating room (OR) tabletops, the use of the C-arm, and timely access to lead in the OR. Multiple evaluation methods were used including observation, debriefing, time-based metrics, distance wheel metrics, equipment adjustment counts, and other transport route considerations. Results: The evaluation resulted in several types of data that allowed for informed decision making for the most effective, efficient, and safest transport route for an exsanguinating trauma patient and healthcare team; improved efficiencies in use of the C-arm, significantly reduced the time to access lead; and uncovered a new process for switching OR tabletop due to safety threats identified.


2021 ◽  
Vol 1 ◽  
pp. 1887-1896
Author(s):  
Vahid Salehi

AbstractCurrently, inconsistent software versions lead to massive challenges for many car manufacturers. This is partly because within the product lifecycle management and the software engineering process, there is no correct handling of software versions for the “data entry” (installation of software on the ECU) of the vehicles. Furthermore, there are currently major challenges for many vehicle manufacturers to ensure transparency, integrity and full traceability of SW data status vis-à-vis the legislator. To counteract these challenges, new solutions in the field of vehicle engineering are to be developed based on a new platform called “CarEngChainNet” and Blockchain technology. On the basis of the “CarEngChainNet” platform, new main and sub-chain chains will be developed that allow tamper-proof SW data management (Peer to Peer and crypto technology) across the entire PLM chain with new methods such as model-based systems engineering of the requirement, function and integration of the SW components in different areas of vehicle development. The aim is to develop new transmission chains of vehicles with individually packaged software artefacts (e.g. ECU software) that can be securely transmitted from server to server into the vehicle.


Sign in / Sign up

Export Citation Format

Share Document