Intangible trust requirements - how to fill the requirements trust "gap"?

Previous research efforts have been expended in terms of the capture and subsequent instantiation of "soft" trust requirements that relate to HCI usability concerns or in relation to "hard" tangible security requirements that primarily relate to security a ssurance and security protocols. Little direct focus has been paid to managing intangible trust related requirements per se. This 'gap' is perhaps most evident in the public B2C (Business to Consumer) E- Systems we all use on a daily basis. Some speculative suggestions are made as to how to fill the 'gap'. Visual card sorting is suggested as a suitable evaluative tool; whilst deontic logic trust norms and UML extended notation are the suggested (methodologically invariant) means by which software development teams can perhaps more fully capture hence visualize intangible trust requirements

Estimating, planning and managing Agile Web development projects under a value-based perspective

Context: The processes of estimating, planning and managing are crucial for software development projects, since the results must be related to several business strategies. The broad expansion of the Internet and the global and interconnected economy make Web development projects be often characterized by expressions like delivering as soon as possible, reducing time to market and adapting to undefined requirements. In this kind of environment, traditional methodologies based on predictive techniques sometimes do not offer very satisfactory results. The rise of Agile methodologies and practices has provided some useful tools that, combined with Web Engineering techniques, can help to establish a framework to estimate, manage and plan Web development projects. Objective: This paper presents a proposal for estimating, planning and managing Web projects, by combining some existing Agile techniques with Web Engineering principles, presenting them as an unified framework which uses the business value to guide the delivery of features. Method: The proposal is analyzed by means of a case study, including a real-life project, in order to obtain relevant conclusions. Results: The results achieved after using the framework in a development project are presented, including interesting results on project planning and estimation, as well as on team productivity throughout the project. Conclusion: It is concluded that the framework can be useful in order to better manage Web-based projects, through a continuous value-based estimation and management process.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-

Naming the Pain in Requirements Engineering: A Design for a Global Family of Surveys and First Results from Germany

For many years, we have observed industry struggling in defining a high quality requirements engineering (RE) and researchers trying to understand industrial expectations and problems. Although we are investigating the discipline with a plethora of empirical studies, they still do not allow for empirical generalisations. To lay an empirical and externally valid foundation about the state of the practice in RE, we aim at a series of open and reproducible surveys that allow us to steer future research in a problem-driven manner. We designed a globally distributed family of surveys in joint collaborations with different researchers and completed the first run in Germany. The instrument is based on a theory in the form of a set of hypotheses inferred from our experiences and available studies. We test each hypothesis in our theory and identify further candidates to extend the theory by correlation and Grounded Theory analysis. In this article, we report on the design of the family of surveys, its underlying theory, and the full results obtained from Germany with participants from 58 companies. The results reveal, for example, a tendency to improve RE via internally defined qualitative methods rather than relying on normative approaches like CMMI. We also discovered various RE problems that are statistically significant in practice. For instance, we could corroborate communication flaws or moving targets as problems in practice. Our results are not yet fully representative but already give first insights into current practices and problems in RE, and they allow us to draw lessons learnt for future replications. Our results obtained from this first run in Germany make us confident that the survey design and instrument are well-suited to be replicated and, thereby, to create a generalisable empirical basis of RE in practice

A Review on Software Architecture Documentation in Agile Development

With the growing development of world every software product demands extra features to compete with competitors. To solve this problem, we have required Agile with defined and clear architecture to avoid the failure of project. But you do not know how it is possible and how we can stable our architecture and Agile model…? To ease the solution of problem we divided our product development models into two sections. 1. Traditional Models and 2. Agile Models The traditionally models are highly time consuming with dense documentation as compared to agile with frivolous documentation and intercommunications to satisfy customer. There are different methodologies available for starting products and complex systems development consisting the simple requirement with well-structured architecture objects. But we choose the agile process to make our architecture slim and least documentation which can easily review, update and conversate. There are also problems in our documentation and architecture design but we propose solutions with problems for the easiness of reader. We also propose different solutions in documentation problems

Gender Equality With Agile In Software Engineering

Women are under-represented in information technology careers in general and in the profession of software development in particular and their numbers are declining. Previous studies on this topic have investigated whether the reason for this is due to a difference in capability arising out of their gender, or whether the reason arises from social factors. A software development methodology called “Agile†has arisen in recent years which focus on collaboration, working software, and a sustainable workweek. Studies have shown that adopting Agile techniques in the classroom helps to retain women in computer information academic curricula and that adopting them in workplace teams improves communication across gender and ethnic diversity. This study invited women to speak for themselves as to whether they find Agile engineering techniques helpful in the workplace through the use of an online survey and follow-up interviews. The results revealed that women feel positively about these practices but have encountered some resistance to adopting them. Future studies discerning whether there are differences in the attitudes of men and women to these practices or whether there is a correlation between adoption of these practices and the number of women practicing as software developers in varying environments are logical future research topics to extend understanding in this are

Application of System Engineering Leading Indicators to SCRUM Agile Projects

SCRUM Agile metrics and System Engineering Leading Indicators (SE LIs) are measures used to evaluate the effectiveness and performance of a project across its lifecycle. The application of metrics can provide information on both internal resources and external project stakeholder requirements and constraints, showing past changes, trends, and potential future impacts. Both SCRUM Agile and SE LIs are designed to give a systems engineer/project manager insight into development progress allowing for progress to be checked at regular intervals as well as early corrective actions to be taken if necessary. This research applied SE LIs to a SCRUM Agile project to demonstrate if it was possible to integrate and utilize the two different sets of performance metrics to enhance a SCRUM Agile project. This thesis identified 16 of the 18 SE LIs could be integrated and utilized in an SCRUM Agile project. Those 16 identified leading indicators were applied to a representative software development scenario in order to demonstrate how it is possible to integrate SE LIs into a SCRUM Agile project

Revealing the Vicious Circle of Disengaged User Acceptance: A SaaS Provider's Perspective

User acceptance tests (UAT) are an integral part of many different software engineering methodologies. In this paper, we examine the influence of UATs on the relationship between users and Software-as-a-Service (SaaS) applications, which are continuously delivered rather than rolled out during a one-off signoff process. Based on an exploratory qualitative field study at a multinational SaaS provider in Denmark, we show that UATs often address the wrong problem in that positive user acceptance may actually indicate a negative user experience. Hence, SaaS providers should be careful not to rest on what we term disengaged user acceptance. Instead, we outline an approach that purposefully queries users for ambivalent emotions that evoke constructive criticism, in order to facilitate a discourse that favors the continuous innovation of a SaaS system. We discuss theoretical and practical implications of our approach for the study of user engagement in testing SaaS applications

When Agile Means Staying: A Moderated Mediated Model

The design of software development methods focuses on improving task processes, including accommodating changing user requirements and accelerating product delivery. However, there is limited research on how the use of different software development methods impacts IT professionals’ perceptions of organizational mobility. Drawing on concepts from the agile development literature and job characteristics theory, we formulate a moderated mediation model explicating the mechanism and the condition under which agile development use exerts an influence on IT professionals’ intention to stay with their current employer. Specifically, we examine job satisfaction as mediating the effect of using agile development on the intention to stay as well as how the strength of the mediated relationship differs across firms. We test our hypotheses using a sample of 32,389 software developers. We find that job satisfaction fully mediates the effect of using agile development on the intention to stay. The strength of the mediation effect is significantly different for large and small firms