The Experts below are selected from a list of 34926 Experts worldwide ranked by ideXlab platform
Jan Gulliksen - One of the best experts on this subject based on the ideXlab platform.
-
human centered software engineering integrating usability in the software Development Lifecycle
2011Co-Authors: Ahmed Seffah, Jan Gulliksen, Michel C DesmaraisAbstract:The fields of HCI and Software Engineering have evolved almost independently of each other until the last decade, when it became apparent that an integrated and combined perspective would benefit the Development of interactive software applications. The chapters in this book are written by prominent researchers who bring to light the major integration issues and challenges, and offer a variety of solutions to bridging the HCI and SE gap, including: Extending software engineering artifacts for UI specification, such as annotating use cases with task descriptions, Enhancing object-oriented software engineering notations and models Possible extensions of HCI methods for requirements gathering through field observations and interviews, deriving a conceptual design model from scenario, task models and use cases and using personae as a way to understand and model end-users, New methodologies for interactive systems design, as well as approaches complementing existing methodologies.
-
usability design extending rational unified process with a new discipline
Lecture Notes in Computer Science, 2003Co-Authors: Bengt Goransson, Jan GulliksenAbstract:A new discipline, Usability Design, is proposed as an extension to Rational Unified Process (RUP). The aim is to make RUP more user-centred. The discipline springs out of best practices for user-centred design and contains activities that have been carefully tested. Five new roles are introduced to take responsibility for the different activities. An example is given to show the content of the workflow, the workflow details and the activities. The Usability Design discipline help projects to focus on usability and the users throughout the system Development Lifecycle.
-
usability throughout the entire software Development Lifecycle a summary of the interact 2001 workshop
2001Co-Authors: Jan Gulliksen, Inger BoivieAbstract:Usability Throughout the Entire Software Development Lifecycle - A Summary of the INTERACT 2001 Workshop
Bengt Goransson - One of the best experts on this subject based on the ideXlab platform.
-
usability design extending rational unified process with a new discipline
Lecture Notes in Computer Science, 2003Co-Authors: Bengt Goransson, Jan GulliksenAbstract:A new discipline, Usability Design, is proposed as an extension to Rational Unified Process (RUP). The aim is to make RUP more user-centred. The discipline springs out of best practices for user-centred design and contains activities that have been carefully tested. Five new roles are introduced to take responsibility for the different activities. An example is given to show the content of the workflow, the workflow details and the activities. The Usability Design discipline help projects to focus on usability and the users throughout the system Development Lifecycle.
Barrie Thompson - One of the best experts on this subject based on the ideXlab platform.
-
iterative design and testing within the software Development life cycle
Software Quality Journal, 1997Co-Authors: Boryuan Tsai, Simon Stobart, Norman Parrington, Barrie ThompsonAbstract:The activity of testing begins during system Development and spans all subsequent phases. Some system Development Lifecycles describe testing which is performed after the coding phase, but this may cause the software to be delivered without sufficient testing. In this paper, we present a software system Development Lifecycle model, called the Test design Stages Processed model (TSP model), in which we emphasize that iterative test design stages should be incorporated at each phase of the software Development Lifecycle. When a phase is completed, testing of the phase should also be completed at that time. Within this paper we have added unit, integration and system testing processes into BoochOs micro–design process to generate a new designs and test model. This shows the process of iterative and incremental software Development. Comparing this with our model, we explain how the TSP model can be used for developing and testing an object-oriented software system.
Boryuan Tsai - One of the best experts on this subject based on the ideXlab platform.
-
iterative design and testing within the software Development life cycle
Software Quality Journal, 1997Co-Authors: Boryuan Tsai, Simon Stobart, Norman Parrington, Barrie ThompsonAbstract:The activity of testing begins during system Development and spans all subsequent phases. Some system Development Lifecycles describe testing which is performed after the coding phase, but this may cause the software to be delivered without sufficient testing. In this paper, we present a software system Development Lifecycle model, called the Test design Stages Processed model (TSP model), in which we emphasize that iterative test design stages should be incorporated at each phase of the software Development Lifecycle. When a phase is completed, testing of the phase should also be completed at that time. Within this paper we have added unit, integration and system testing processes into BoochOs micro–design process to generate a new designs and test model. This shows the process of iterative and incremental software Development. Comparing this with our model, we explain how the TSP model can be used for developing and testing an object-oriented software system.
Kevin Mc Daid - One of the best experts on this subject based on the ideXlab platform.
-
a traceability process assessment model for the medical device domain
European conference on Software Process Improvement, 2014Co-Authors: Gilbert Regan, Miklos Biro, Kevin Mc DaidAbstract:Traceability of requirements through the software Development Lifecycle (including supporting processes such as risk management and change management) is a difficult and expensive task. The implementation of effective traceability allows organizations to leverage its many advantages, such as impact analysis, product verification and validation, and facilitation of code maintenance. Traceability is conducive to producing quality software.
-
medical device standards requirements for traceability during the software Development Lifecycle and implementation of a traceability assessment model
Computer Standards & Interfaces, 2013Co-Authors: Gilbert Regan, Kevin Mc Daid, Fergal Mc Caffery, Derek FloodAbstract:Developing safety critical software is a complex process. Due to the fact that medical device software failure can lead to catastrophic consequences, numerous standards have been developed which govern software Development in the medical device domain. Risk management has an important role in medical device software Development as it is important to ensure that safe software is developed. Demonstrating traceability of requirements right throughout the medical device software Development and maintenance Lifecycles is an important part of demonstrating that 'safe' software has been produced through adopting defined processes. Consequently, medical device standards and guidelines emphasise the need for traceability. This paper outlines the extent and diversity of traceability requirements within medical device standards and guidelines, and identifies the requirements for traceability through each phase of the software Development Lifecycle. The paper also summarises the findings obtained when a lightweight assessment method (Med-Trace), which we created, based upon the traceability practices within these standards, was implemented in two SME organisations. Finally we highlight how the findings indicate a lack of guidance as to what is required when implementing and maintaining a traceability process.
-
implementation of traceability best practices within the medical device domain
2013Co-Authors: Gilbert Regan, Kevin Mc DaidAbstract:Requirements validation, compliance verification and impact analysis are important activities that are performed during the software Development Lifecycle. Traceability of requirements through the software Development Lifecycle (SDLC) is essential in the Development of safety critical software. Organisations such as the Food and Drug Administration and the Federal Aviation Authority in the United States require traceability as part of their approval process. However, despite its criticality there is extensive digression in the practices and usefulness of traceability across Development projects. Many projects’ traceability efforts are simply focused on satisfying regulations and do not leverage the many benefits of traceability. Traceability, if fully implemented is an important tool for managing system Development and there are a number of published best practices to help companies with this implementation. By means of a literature review we record a list of the commonly accepted best practices for traceability implementation. Furthermore, through interviews with two medical device companies we report that a number of these practices are unfamiliar to these companies and why an even greater number of these practices are not applied.
