Using protocol analysis to explore the creative requirements engineering process

Protocol analysis is an empirical method applied by researchers in cognitive psychology and behavioural analysis. Protocol analysis can be used to collect, document and analyse thought processes by an individual problem solver. In general, research subjects are asked to think aloud when performing a given task. Their verbal reports are transcribed and represent a sequence of their thoughts and cognitive activities. These verbal reports are analysed to identify relevant segments of cognitive behaviours by the research subjects. The analysis results may be cross-examined (or validated through retrospective interviews with the research subjects). This paper offers a critical analysis of this research method, its approaches to data collection and analysis, strengths and limitations, and discusses its use in information systems research. The aim is to explore the use of protocol analysis in studying the creative requirements engineering process.<br /

Evaluating Software Architectures: Development Stability and Evolution

We survey seminal work on software architecture evaluationmethods. We then look at an emerging class of methodsthat explicates evaluating software architectures forstability and evolution. We define architectural stabilityand formulate the problem of evaluating software architecturesfor stability and evolution. We draw the attention onthe use of Architectures Description Languages (ADLs) forsupporting the evaluation of software architectures in generaland for architectural stability in specific

Autodocumentation

Automated documentation systems with expanded capabilities for reusing existing programs are considered by allowing a relatively inexpensive determination of program capabilities. A theoretical approach to such a system is proposed. Tree structure variations are examined, along with assignment statements, conditional branches, loops, and an automated analyzer

The ABCD of usability testing

We introduce a methodology for tracking and auditing feedback, errors and suggestions for software packages. This short paper describes how we innovate on the evaluation mechanism, introducing an (Antecedent, Barrier, Consequence and Development) ABCD form, embedded within an eParticipation platform to enable end users to easily report on any usability issues. This methodology will be utilised to improve the STEP cloud eParticipation platform (part of the current STEP Horizon2020 project http://step4youth.eu. The platform is currently being piloted in real life contexts, with the participation of public authorities that are integrating the eParticipation platform into their regular decision-making practices. The project is involving young people, through engagement and motivation strategies and giving them a voice in Environmental decision making at the local level. The pilot evaluation aims to demonstrate how open engagement needs to be embedded within public sector processes and the usability methodology reported here will help to identify the key barriers for wide scale deployment of the platform

Identifying Agile Requirements Engineering Patterns in Industry

Agile Software Development (ASD) is gaining in popularity in today´s business world. Industry is adopting agile methodologies both to accelerate value delivery and to enhance the ability to deal with changing requirements. However, ASD has a great impact on how Requirements Engineering (RE) is carried out in agile environments. The integration of Human-Centered Design (HCD) plays an important role due to the focus on user and stakeholder involvement. To this end, we aim to introduce agile RE patterns as main objective of this paper. On the one hand, we will describe our pattern mining process based on empirical research in literature and industry. On the other hand, we will discuss our results and provide two examples of agile RE patterns. In sum, the pattern mining process identifies 41 agile RE patterns. The accumulated knowledge will be shared by means of a web application.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2016-76956-C3-2-RMinisterio de Economía y Competitividad TIN2015-71938-RED

A Novel Method for Assessing Medication-Related Adverse Outcomes in a Community Hospital

The use of medications for hospitalized patients is universal, and unfortunately medication-related adverse outcomes are common. The accurate assessment of medication-related harm in hospitalized patients is foundational to the development of an effective hospital medication safety program. Every hospital has its own unique fingerprint of harm, accurate determination of the nature of medication-related harm specific to each hospital is necessary to facilitate prevention of that harm with specific and effective interventions. This project has provided a community hospital with its first systematic methodology for assessing medication-related harm. The methodology is adapted from that used in a recent national-level study. Several commonly accepted methods of assessment of medication-related adverse events are in use, but no single method is capable of giving a complete picture of harm at the hospital level. Using a method nearly identical to one employed in large national studies the author examined rates and types of medication-related adverse outcomes in a California community hospital. The hospital had about one-third the national rate of adverse events. An incidental finding was a 4-year pattern of increasing incidence of adverse outcomes followed by 2 years of declining incidence of adverse outcomes. The information gained from the novel assessment method provided a clearer picture of patient harm, a basis for a more effective medication safety plan, and promoted interprofessional collaboration

Enhancing security incident response follow-up efforts with lightweight agile retrospectives

Security incidents detected by organizations are escalating in both scale and complexity. As a result, security incident response has become a critical mechanism for organizations in an effort to minimize the damage from security incidents. The final phase within many security incident response approaches is the feedback/follow-up phase. It is within this phase that an organization is expected to use information collected during an investigation in order to learn from an incident, improve its security incident response process and positively impact the wider security environment. However, recent research and security incident reports argue that organizations find it difficult to learn from incidents. A contributing factor to this learning deficiency is that industry focused security incident response approaches, typically, provide very little practical information about tools or techniques that can be used to extract lessons learned from an investigation. As a result, organizations focus on improving technical security controls and not examining or reassessing the effectiveness or efficiency of internal policies and procedures. An additional hindrance, to encouraging improvement assessments, is the absence of tools and/or techniques that organizations can implement to evaluate the impact of implemented enhancements in the wider organization. Hence, this research investigates the integration of lightweight agile retrospectives and meta-retrospectives, in a security incident response process, to enhance feedback and/or follow-up efforts. The research contribution of this paper is twofold. First, it presents an approach based on lightweight retrospectives as a means of enhancing security incident response follow-up efforts. Second, it presents an empirical evaluation of this lightweight approach in a Fortune 500 Financial organization's security incident response team