Showing papers on "User story published in 2015"
01 Aug 2015
TL;DR: The Quality User Story Framework is proposed, consisting of 14 quality criteria that user story writers should strive to conform to, and the conceptual model of a user story is introduced, which is relied on to design the AQUSA software tool.
Abstract: User stories are a widely used notation for formulating requirements in agile development projects. Despite their popularity in industry, little to no academic work is available on assessing their quality. The few existing approaches are too generic or employ highly qualitative metrics. We propose the Quality User Story Framework, consisting of 14 quality criteria that user story writers should strive to conform to. Additionally, we introduce the conceptual model of a user story, which we rely on to design the AQUSA software tool. AQUSA aids requirements engineers in turning raw user stories into higher-quality ones by exposing defects and deviations from good practice in user stories. We evaluate our work by applying the framework and a prototype implementation to three user story sets from industry.
95 citations
TL;DR: There is still room for improvements in terms of support for various agile RE practices within a specific agile process, and qualitative analysis of user reviews has demonstrated that practitioners prefer tools that are easy to set up, easy to learn,easy to use, and easy to customize, over more sophisticated but simultaneously more demanding tools.
Abstract: Context User stories have become widely accepted in agile software development. Consequently, a great number of software tools that provide, inter alia, support for practices based on user stories have emerged in recent years. These tools may have different features and focus in terms of support for agile requirements engineering (RE) concepts and practices. Objective The present study aims to provide a deep insight into the current capabilities and future trends of software support for agile RE practices based on user stories. Method A comparative qualitative study of a set of agile software tools has been conducted according to the following criteria: coverage of the key functional requirements, support for basic agile RE concepts and practices, and user satisfaction with the tool. The criteria for tool selection were: diversity of software tools, high rating on the user-stories community Web site ( http://www.userstories.com ), and availability for review. Results The results show a generally good coverage of key functional requirements related to management of user stories and epics, high-level release planning and low-level iteration planning. On the other hand, user-role modeling and persona support have not been addressed at all, and it has been found that requirements for acceptance testing support were completely covered by only one tool. More importantly, the study has revealed significant differences in the way different tools support agile RE concepts and practices (if at all). Finally, qualitative analysis of user reviews has demonstrated that practitioners prefer tools that are easy to set up, easy to learn, easy to use, and easy to customize, over more sophisticated but simultaneously more demanding tools. Conclusion Although the progress that has been made since the inception of these tools is quite clear, there is still room for improvements in terms of support for various agile RE practices within a specific agile process.
47 citations
23 Mar 2015
TL;DR: The findings can support software developers in planning and improving their processes with regard to better requirements communication and researchers in making mapping methods more applicable in industry.
Abstract: [Context & motivation] Requirements artifacts, like specifications, diagrams, or user stories, are often used to support various activities related to requirements. How well an artifact can support a specific activity depends on the artifact’s nature. For example, a plain text document can be adequate to provide contextual information, but is not well suited in terms of documenting changes. [Questions / problem] We wanted to understand how practitioners in various roles use requirements artifacts, how they manage to work with multiple artifacts at a time, and whether they use current practices for linking related artifacts. [Principal ideas / results] We have conducted an interview study with 21 practitioners from 6 companies. The interviews indicate that often a variety of artifact types is needed to successfully conduct a project. At the same time, using multiple artifacts causes problems like manual translation effort and inconsistencies. Mapping mechanisms that explicitly relate different artifacts are needed. However, existing methods are often not used. We investigate why these methods challenge developers in practice. [Contribution] We show challenges and chances of requirements artifacts. Our findings are grounded on true experiences from the industry. These experiences can support software developers in planning and improving their processes with regard to better requirements communication and researchers in making mapping methods more applicable in industry.
34 citations
TL;DR: This work proposes a UAT process model which adapts the generic agile process model and is able to encompass every agile methodology, and aims at generation of exhaustive acceptance test cases in natural language, based on acceptance criteria.
Abstract: User Acceptance Testing (UAT) has widespread implications in the software community. It involves not only the end-user, but the Quality Assurance (QA) team, developers, business analysts and top level management. UAT is conducted with the aim of developing confidence of the user in the software product. UAT is generally performed manually and not preferred to be automated. UAT frameworks exist for Agile methodologies such as Scrum. We propose a UAT process model which adapts the generic agile process model. Hence, it is able to encompass every agile methodology. AgileUAT, aims at generation of exhaustive acceptance test cases in natural language, based on acceptance criteria. It indicates whether the acceptance criteria is fulfilled or not, as a percentage value. The tool illustrates traceability among epics, user stories, acceptance criteria and acceptance test cases. We explore several different templates for user stories and acceptance criteria. In the future, we aim to provide a direct mapping between the acceptance criteria and acceptance test cases based on permutations and combinations using decision tables. General Terms Software Engineering -> Software Creation and Management -> Software Verification and Validation -> Process Validation -> Acceptance Testing
33 citations
16 May 2015
TL;DR: It is found that students over time learned to better self-select tasks with less inter-team dependencies, to communicate more, and to work better in teams, suggesting that Scrum helps alleviate many GSE problems.
Abstract: We describe an experience in teaching global software engineering (GSE) using distributed Scrum augmented with industrial best practices. Our unique instructional technique had students work in both same-site and cross-site teams to contrast the two modes of working. The course was a collaboration between Aalto University, Finland and University of Victoria, Canada. Fifteen Canadian and eight Finnish students worked on a single large project, divided into four teams, working on interdependent user stories as negotiated with the industrial product owner located in Finland. Half way through the course, we changed the teams so each student worked in both a local and a distributed team. We studied student learning using a mixed-method approach including 14 post-course interviews, pre-course and Sprint questionnaires, observations, meeting recordings, and repository data from git and Flow dock, the primary communication tool. Our results show no significant differences between working in distributed vs. Non-distributed teams, suggesting that Scrum helps alleviate many GSE problems. Our post-course interviews and survey data allows us to explain this effect, we found that students over time learned to better self-select tasks with less inter-team dependencies, to communicate more, and to work better in teams.
30 citations
23 Mar 2015
TL;DR: It is concluded that the Value Story workshop is a promising method for embedding values in the Requirements Engineering process, but that value-based user stories need to be translated to use cases to make them suitable for planning and organizing implementation activities.
Abstract: Software has become an integral part of our daily lives and should therefore account for human values such as trust, autonomy and privacy. Human values have received increased attention in the field of Requirements Engineering over the last few years, but existing work offers no systematic way to use elicited values in requirements engineering and evaluation processes. In earlier work we proposed the Value Story workshop, a domain-independent method that connects value elicitation techniques from the field of Human-Computer Interaction to the identification of user stories, a common requirements specification format in Requirements Engineering. This paper studies whether user stories obtained in a Value Story workshop 1) adequately account for values, and 2) are usable by developers. The results of an empirical evaluation show that values are significantly better incorporated in user stories obtained in a Value Story workshop than through user stories obtained in regular requirements elicitation workshops. The results also show that value-based user stories are deemed valuable to the end-user, but rated less well on their size, estimableness and testability. This paper concludes that the Value Story workshop is a promising method for embedding values in the Requirements Engineering process, but that value-based user stories need to be translated to use cases to make them suitable for planning and organizing implementation activities. © Springer International Publishing Switzerland 2015.
28 citations
01 Oct 2015
TL;DR: An algorithm for automating the transformation of user stories into sequence diagrams in the Scrum process is presented, which can easily use to generate test cases.
Abstract: The creation of UML models from user stories can be inconsistent, incomplete and incorrect task, which also requires an expertise, effort and time. In this paper, we present an algorithm for automating the transformation of user stories into sequence diagrams in the Scrum process, which can easily use to generate test cases. For automating transformation, we have implemented an algorithm that read a text file, which contains a set of user stories, then generates an XMI file for each user stories. The resulting XMI file then transformed into a sequence diagram using UML2 tool SDK plugin for Eclipse.
26 citations
13 Apr 2015
TL;DR: The results from both studies allowed to identify a list of causes that can lead the development team to incur documentation debt when working with agile requirements, an important step in order to manage the technical debt from a preventive perspective.
Abstract: Technical debt is a metaphor that describes the effect of immature artefacts in software development. One of its types is documentation debt, which can be identified by locating missing, inadequate or incomplete artefacts in software projects. Nowadays, we can observe more organizations using agile methods to support their activities. In particular, the use of user stories reduces the focus on requirement specification tasks and, as a consequence, creates difficulties that need to be overcame by the development team. In order to investigate these difficulties and assess whether they create a favourable scenario for incurring documentation debt, this paper presents the results of a literature review and an exploratory study. The results from both studies allowed us to identify a list of causes that can lead the development team to incur documentation debt when working with agile requirements. This is an important step in order to manage the technical debt from a preventive perspective.
23 citations
25 May 2015
TL;DR: This comparative case study of three companies from the Nordic region systematically investigates expectations and challenges from scaling Agile in organizations dealing with mechatronics development by conducting on-site workshops and surveys.
Abstract: Agile software development is increasingly adopted by companies evolving and maintaining software products to support better planning and tracking the realization of user stories and features. While convincing success stories help to further spread the adoption of Agile, mechatronics-driven companies need guidance to implement Agile for non-software teams. In this comparative case study of three companies from the Nordic region, we systematically investigate expectations and challenges from scaling Agile in organizations dealing with mechatronics development by conducting on-site workshops and surveys. Our findings show that all companies have already successfully implemented Agile in their software teams. The expected main benefit of successfully scaling agile development is a faster time-to-market product development; however, the two main challenges are: (a) An inflexible test environment that inhibits fast feedback to changed or added features, and (b) the existing organizational structure including the company’s mind-set that needs to be opened-up for agile principles.
19 citations
01 Dec 2015
TL;DR: This paper proposes a novel automated approach to generate test cases from requirements using text mining and symbolic execution methodology for test data generation and validation, where a knowledge base is developed for multi-disciplinary domains.
Abstract: Requirements-based testing is a testing approach in which test cases are derived from requirements. Requirements represent the initial phase in software developments life cycle. Requirements are considered the basis of any software project. Therefore, any ambiguity in natural language requirements leads to major errors in the coming phases. Moreover, poorly defined requirements may cause software project failure. There exist many software development models as waterfall model, agile model, etc. In this paper, we propose a novel automated approach to generate test cases from requirements. Requirements can be gathered from different models either waterfall model (functional and non-functional) or agile model. SRS documents, non-functional requirements and user stories are parsed and used by the proposed approach to generate test cases in which requirements with different types are covered. The proposed approach uses text mining and symbolic execution methodology for test data generation and validation, where a knowledge base is developed for multi-disciplinary domains.
18 citations
01 Jan 2015
TL;DR: An implementation of an automated solution as a tool to mapping user stories into i* models, US2StarTool, is presented, adding a support for agile develop- ment environment.
Abstract: In agile methods, the requirements are represented by user stories. However, this model does not allow a good visualization of context in which a story is inserted, reducing the understanding of the system as a whole. On the other hand, the i* model presents dependencies among organizational actors, and the understanding of the context in which a requirement is inserted. This paper presents an implementation of an automated solution as a tool to mapping user stories into i* models, US2StarTool, adding a support for agile develop- ment environment. US2StarTool can help requirements engineer in agile devel- opment environments contextualizing the environment in which user stories are inserted and showing relationships between the actors and the system.
Journal Article•
TL;DR: In this paper, a capstone course in software engineering is described that exposes students to lean principles advocated by Kanban, and students are required to work in teams responsible for the implementation of a set of user stories defined by a project domain expert playing the role of Product Owner.
Abstract: In this paper, a capstone course in software engineering is described that exposes students to lean principles advocated byKanban. While retaining the main characteristics of its predecessor course, which concentrated on teaching agile softwaredevelopment using Scrum, the new course also introduces the most important Kanban concepts, i.e., visualization of theworkflow and limitation of the work in progress. Kanban concepts are introduced in two ways: in combination with Scrum(as Scrumban) or as a ‘‘pure’’ Kanban (omitting some of the Scrum activities considered waste). Students are required towork in teams responsible for the implementation of a set of user stories defined by a project domain expert playing the roleof the Product Owner. During the course, they must maintain a Kanban board and measure lead time. The paper discussesthe use of different Kanban boards and work in progress limits, and analyzes the students’ progress in reducing lead time. Asummary of the lessons learned and recommendations is given reflecting the issues to be considered when teaching similarcourses. A survey among students has shown that they liked both approaches and were overwhelmingly positive about thecourse.
22 Jun 2015
TL;DR: This work introduces an approach based both on the clustering of textual requirements and on a data dictionary to organize them, as well as suggest a sequence for their implementation.
Abstract: Natural language is often used to write software systems requirements. However, it may be prone to misunderstandings due to its ambiguities. Moreover, it is not easy to modularize these requirements and then find all related ones. In order to find out the impact of requirements in one another, it is necessary to look at every requirement rather than just a group of related requirements. When presented in large numbers, the understanding, organization and sequencing of requirements requires substantial time and effort. In this work, we introduce an approach based both on the clustering of textual requirements and on a data dictionary to organize them, as well as suggest a sequence for their implementation. A case study based on User Stories from Agile processes is introduced to illustrate the approach.
03 Aug 2015
TL;DR: This work conducted field studies of 8 Agile teams using digital Cardwall, and performed qualitative data analysis to understand patterns of usages and user needs, and identifies issues to address in the design of digital Cardwalls.
Abstract: In Agile software development, key artefacts used to support the process are the User Story (usually recorded on a Storycard) and Story Cardwall (usually a dedicated portion of a wall). These low-fidelity tools work together to help teams stay focused and self-manage their projects. The need to support distributed teams and team members makes the physical Cardwall impractical and teams are therefore migrating towards digital story management tools. We conducted field studies of 8 Agile teams using digital Cardwalls, and performed qualitative data analysis to understand patterns of usages and user needs. We identify issues to address in the design of digital Cardwalls.
22 Jun 2015
TL;DR: Experiments evidence that BPMN models improve quality and quantity of information collected during requirements elicitation and ease that clients specify clearly their needs and business goals.
Abstract: Many communication problems may appear during requirements elicitation causing that final products do not accomplish client expectations. This paper analyzes the impact of using business processes management notation (BPMN) instead of user stories during requirements analysis in agile methodologies. For analyzing the effectiveness of our approach, we compare the use of user stories vs. BP models in eleven software projects during requirements elicitation phase. Experiments evidence that BPMN models improve quality and quantity of information collected during requirements elicitation and ease that clients specify clearly their needs and business goals.
Dissertation•
19 Aug 2015
TL;DR: In this paper, the authors evaluate the effectiveness of gamification in requirements engineering in order to improve stakeholder engagement and propose an online digital platform for scenariobased RE supported with gamification.
Abstract: The purpose of this paper is to evaluate the effectiveness of gamification in requirements engineering in order to improve stakeholder engagement. We developed an online digital platform for scenariobased RE supported with gamification. Derived from an in-depth literature study, we selected user stories complemented with scenarios from behavior-driven development (BDD) as a method to express stakeholder requirements. Points, badges and leaderboards (PBL) are very common game elements in terms of gamification and are used as a starting point for the gamified platform. In total, the RE eliciation system consists of 17 different game mechanics and elements, which intension is to positively affect intrinsic and extrinsic stakeholder motivation. Subsequently, the gamified platform is tested in a controlled experiment. The findings demonstrate that it is possible to effectively change stakeholder’s behavior with gamification. Stakeholders who are influenced by gamification produce more requirements, with better quality and more creativity. The majority of their user stories consist of attractive requirements that enhance customer satisfaction. Derived from the results we agree that competitive game elements are advantageous for RE elicitation to mitigate collaboration and therefore, prevent production blocking. In sharp contrast, social game elements are favorable for RE analysis, specification and validation where cooperation is demanded.
TL;DR: The concept of end-user programming and Advancement of UCP are discussed by adding end- user development/programming as an additional Effort Estimation Factor (EEF) in the Use Case Point (UCP) method.
Abstract: Computer literacy and competitive pressures among end users is increasing day by day due to whichthe need for End-User Programming in software packages is also increasing for rapid, flexible, and user driven information processing solutions. End User Development out-sources development effort to the end user by enabling softwaredevelopers to create information systems that can even be adapted by technically inexperienced endusers and hence are in great demand. If end user decides to pay the price and add significant programmability to their system, there are additional costs to consider before end user can start to enjoy the payoff. It is important to calculate accurateand early estimation of software size forcalculating effort and cost estimation of software systems incorporating EUD features. With the evolution of object orientation, use cases emerged as a dominant method for structuring requirements. Use cases were integrated into the Unified Modeling Language (UML) and Unified Process and became the standard for Software Engineering requirements modelling. The Use Case Point (UCP)methodestimates project size by assigning points to use cases in the same way that Function Point Analysis (FPA) assigns points to functions. This paper discusses the concept of end-user programming and Advancement of UCP by adding end-user development/programming as an additional Effort Estimation Factor (EEF).
Book•
19 Mar 2015
TL;DR: HP Agile Manager as mentioned in this paper is a SaaS-based agile planning tool that provides a simpler, smarter way to manage collaborative development, and it can work for small startups, mid-sized teams, as well as scale up for bigger organizations as a cost-effective and flexible tool to apply agile techniques to improve software development process.
Abstract: Agile development practices have been widely adopted in a variety of organizations, yet only a few tools are available to help make the practical process of managing agile teams less painful and more successful. HP Agile Manager is a purpose-built SaaS-based Agile planning tool. HP Agile Manager provides a simpler, smarter way to manage collaborative development. Liran Tal provides a practical, concise approach to using Agile Manager in a variety of settings to better plan, conduct, and manage software releases within development teams. His step-by-step approach will show you how to plan your products features, streamline the agile sprint process, work with user stories, and track defects throughout the development process. Agile Manager can work for small startups, mid-sized teams, as well as scale up for bigger organizations as a cost-effective and flexible tool to apply agile techniques to improve your software development process. What youll learnHow to apply the concepts of agile management in software development teams to better execute and increase performance and delivery How a software release cycle works, how to manage sprints, set timelines, build a products backlog, and manage day to day team tasks How to leverage agile best practices to guide your team through effective release planning and team collaboration Understand and apply agile software delivery concepts such, estimating and prioritizing user stories. Streamlining sprints planning, execution, and retrospective How to setup, and use HP Agile Manager to effectively manage software lifecycle through agile methodology, and learn how to leverage Agile Manager's flexible workflow to meet your team requirements and processes Using Agile Manager's dashboards for real-time view into the current status of releases, and sprints to gain insights and pro-actively respond to changes, as well as tracking your team progress, work-load, and keeping an eye on tasks burn-down, or cumulative flow Who this book is for Developers, quality engineers, development team leaders and new managers will find this book to serve them well in learning and applying agile methodologies in their teams.
16 Jul 2015
TL;DR: A case study of blog responses that detailed user experiences with the 2013 launch of MNsure.org demonstrated the potential value of UGC content analysis as a complement to traditional usability testing.
Abstract: This paper examines the potential of User-Generated Content (UGC) as a site of research for web usability. Specifically, this paper shares a case study of blog responses that detailed user experiences with the 2013 launch of MNsure.org, a high-stakes website created to facilitate the online purchase of health insurance in response to the 2010 Affordable Care Act (ACA). A content analysis of blog responses, informed by qualitative content analysis [1], revealed poor usability of the site, including a low effectiveness rate, several critical errors, and low satisfaction. User stories were remarkably detailed, offering valuable information for website repairs. Connections between UGC and traditional web usability methods such as usability testing were explored in terms of "community," "participation," and "metrics." Overall, the case demonstrated the potential value of UGC content analysis as a complement to traditional usability testing.
02 Aug 2015
TL;DR: This paper explores the future evolution of software quality management, testing, and global user acceptance approaches keeping in mind the evolution in software and technology quality management in general, including new technologies and the increasing adoption of new software development life cycle methodologies such as Agile and Scaled Agile.
Abstract: This paper explores the future evolution of software quality management (SQM), testing, and global user acceptance approaches keeping in mind the evolution in software and technology quality management in general, including new technologies and the increasing adoption of new software development life cycle methodologies such as Agile and Scaled Agile. These evolutions are forcing quality organizations to change the way they approach software quality processes, including increased outsourcing of development, and the need to update traditional testing and user acceptance testing approaches which lag behind with manual and invasive techniques. User acceptance as we know it today must evolve.
22 Oct 2015
TL;DR: The User Stories technique within the Behaviour-Driven Development process by example of the famous Russian bylina "Three trips of Ilya Muromets" written in Gherkin language, which reflects a more complex and changeable behaviour than in static trivial examples, which are usually used.
Abstract: In this paper is presented the User Stories technique within the Behaviour-Driven Development process by example of the famous Russian bylina (epic poem) "Three trips of Ilya Muromets" written in Gherkin language In the first part are given explanations about the choice of the bylina as a good example for presentation of this technique and about the choice of GitHub as a good environment for this presentation In the second part is placed the text of the presentation divided by the stages of the Story development and fitted with the links to the corresponding commits and file versions in the educational repository A distinct advantage of this presentation is that it reflects a Story in its evolution, as a process It reflects a more complex and changeable behaviour than in static trivial examples, which are usually used Also, there are presented the main features of using the User Stories technique in Russian language, which have not been previously covered nowhere Besides that, the using of the educational repository can significantly increase the possibilities for further spreading and development of the example
13 Apr 2015
TL;DR: This paper proposes a conceptual framework, motivated by personas and composed of certain interrelated artifacts, to provide a better support for the goals included in the contents of structured user story statements.
Abstract: This paper proposes a conceptual framework, motivated by personas and composed of certain interrelated artifacts, to provide a better support for the goals included in the contents of structured user story statements.
01 Jan 2015
TL;DR: This work offers a novel evolutionary approach to revolutionise RE process for MAS by presenting bilateral concepts-type of dependency and degree of dependency that assist the developers in reducing the trivial dependencies and thereby unnecessary communication overheads.
Abstract: The intensification of ubiquitous computing has revitalised distributed multi-agent systems. Business and product requirements often change as development proceeds, making a straight-line path to requirement engineering (RE) impracticable. To cope up with the adaptability in the requirements, this work offers a novel evolutionary approach to revolutionise RE process for MAS. The proposed framework bridges the gap between users and developers by facilitating user-oriented view using user story cards and developer-oriented view using agent cards. To address inter-agent coordination issues, this work presents bilateral concepts-type of dependency and degree of dependency that assist the developers in reducing the trivial dependencies and thereby unnecessary communication overheads. An integrated approach for requirements prioritisation enables a large number of stakeholders to resolve their conflicts in deciding which agents are viable to achieve. In addition, a fuzzy traceability vector model and a coding scheme to specify the requirements of agents are the distinguished features of this work.
26 Sep 2015
TL;DR: This paper describes a new semi-formalized, constrained natural language format for user stories that uses variables to correlate precisely various parts of the story and mixfix format to express strictly defined operators in an almost natural language form.
Abstract: There are two established techniques for describing user requirements: User Stories and Use Cases. In this paper we describe a new semi-formalized, constrained natural language format for user stories. The format uses variables to correlate precisely various parts of the story and mixfix format to express strictly defined operators in an almost natural language form. We demonstrate how to extract from this format access control information for role based access control.
20 May 2015
TL;DR: It is worthwhile to develop aspects oriented software development approaches to handle properly the concerns and ensure their separation.
Abstract: Separation of concerns is an important principle that helps to improve reusability and simplify evolution. The crosscutting concerns like security, and many others, often exist before implementation, in both the analysis and design phases, it is therefore worthwhile to develop aspects oriented software development approaches to handle properly the concerns and ensure their separation.
27 Apr 2015
TL;DR: This paper presents an approach to map user stories to i* models and vice versa, aiming at providing a bigger picture of the system as a whole, suggesting the viability of the approach.
Abstract: User stories are a common way to describe requirements in Agile methods. However, the use of user stories is restricted, since they offer only a limited view of the whole system. In contrast, one of the features of the i* framework is provides a visual representation of the actors involved in a system and the goals that are to be met. This allows for a better understanding of the problem as well as for a better overview and evaluation of alternative solutions. In addition, i* models consider the early phases of requirements engineering, while user stories cover the later phases. In this context, this paper presents an approach to map user stories to i* models and vice versa, aiming at providing a bigger picture of the system as a whole. A case study to evaluate this work is also presented, suggesting the viability of the approach.
21 Aug 2015
TL;DR: Recognizing the importance of some actual and anticipated ethical problems, two storytelling user experiments attempted to address the issue in their experiments using purpose-built technical features and a specifically designed consent form as the code of conduct.
Abstract: Collaborative storytelling using user generated audio-visual narratives is becoming a popular medium for creative social sharing, hyper-local TV, and collective awareness. Through two storytelling user experiments, we recognized that the challenges around ethics and copyrights in managing user data are far more pressing than the simple technical feasibilities of a storytelling platform. Recognizing the importance of some actual and anticipated ethical problems we attempted to address the issue in our experiments using purpose-built technical features and a specifically designed consent form as the code of conduct. The resultant platform effectively maintains the life-cycle and dependencies of the narratives and composite user stories.
30 Aug 2015
TL;DR: This paper reflects the experiences encountered in a large-scale mission critical information system – ERICA, an information system for the emergency services in Finland – regarding design, implementation, and deployment and proposes more dynamic ways of system specification.
Abstract: Public tender processes typically start with a comprehensive specification phase, where representatives of the eventual owner of the system, usually together with a hired group of consultants, spend a considerable amount of time to determine the needs of the owner. For the company that implements the system, this setup introduces two major challenges: (1) the written down requirements can never truly describe to a person, at least to one external to the specification process, the true intent behind the requirement; (2) the vision of the future system, stemming from the original idea, will change during the specification process – over time simultaneously invalidating at least some of the requirements. This paper reflects the experiences encountered in a large-scale mission critical information system – ERICA, an information system for the emergency services in Finland – regarding design, implementation, and deployment. Based on the experiences we propose more dynamic ways of system specification, leading to simpler design, implementation, and deployment phases and finally to a better perceived quality.
01 Jan 2015
TL;DR: In this article, the authors show that when the possibilities for businesses to engage in face-to-face interactions decrease, relationship build-i cation is less likely to take place.
Abstract: To a large extent, business-customer interactions are acted out on digital meeting places. When the possibilities for businesses to engage in face-to-face interactions decrease, relationship buildi ...