Evaluating End User Development as a Requirements Engineering Technique for Communicating Across Social Worlds During Systems Development

Requirements engineering is a key activity in systems development. This paper examines six systems development projects that have used end user development (EUD) as a requirements engineering technique for communicating across social worlds. For this purpose, we employed the theoretical lens of design boundary object in order to focus on functional and political ecologies during the development process. Four features were investigated: (1) the capability for common representation, (2) the capability to transform design knowledge, (3) the capability to mobilise for design action, and (4) the capability to legitimise design knowledge across social worlds. We concluded that EUD means a high degree of end user involvement and takes advantage of end users’ know-how. It has the ability to capture requirements and transfer them into the final information system without the need to make an explicit design rationale available to the systems developers. However, systems developers have little or no influence on business requirements. Their role is mainly as technical experts rather than business developers. The systems developers took control and power of technical requirements, while requirements that relate to business logic remained with the end users. Consequently, the systems developers did not act as catalysts in the systems development process

A review of data visualization: opportunities in manufacturing sequence management.

Data visualization now benefits from developments in technologies that offer innovative ways of presenting complex data. Potentially these have widespread application in communicating the complex information domains typical of manufacturing sequence management environments for global enterprises. In this paper the authors review the visualization functionalities, techniques and applications reported in literature, map these to manufacturing sequence information presentation requirements and identify the opportunities available and likely development paths. Current leading-edge practice in dynamic updating and communication with suppliers is not being exploited in manufacturing sequence management; it could provide significant benefits to manufacturing business. In the context of global manufacturing operations and broad-based user communities with differing needs served by common data sets, tool functionality is generally ahead of user application

Peer mentoring in assisting retention – is a virtual form of support a viable alternative?

Support systems are vital for university entrants and one established means of support is peer mentoring, which has the potential to improve student engagement and retention. Peer mentoring models are generally based on face-to-face contact. However, given the increasing number of higher education institutions using social media, might online models be beneficial in a peer mentoring context? This article describes a literature review and case study that considers the advantages and disadvantages of three potential virtual models to facilitate a peer mentoring scheme. The case study, undertaken at Northumbria University, UK, involved an investigation of mentoring needs and current usage of electronic media where special attention is afforded to a diverse student body. The three models discussed are virtual learning environments (VLE), social networking sites and virtual worlds. We find that the VLE is established within institutions but lacks excitement; social networking is popular particularly with younger students but there may be resentment if this appears to be appropriated by the institution; whilst virtual worlds are unfamiliar to many students and require advanced skills to use successfully. Based on these findings the social networking model is now being run as a pilot study by business programmes at Northumbria University

Boundary Objects and their Use in Agile Systems Engineering

Agile methods are increasingly introduced in automotive companies in the attempt to become more efficient and flexible in the system development. The adoption of agile practices influences communication between stakeholders, but also makes companies rethink the management of artifacts and documentation like requirements, safety compliance documents, and architecture models. Practitioners aim to reduce irrelevant documentation, but face a lack of guidance to determine what artifacts are needed and how they should be managed. This paper presents artifacts, challenges, guidelines, and practices for the continuous management of systems engineering artifacts in automotive based on a theoretical and empirical understanding of the topic. In collaboration with 53 practitioners from six automotive companies, we conducted a design-science study involving interviews, a questionnaire, focus groups, and practical data analysis of a systems engineering tool. The guidelines suggest the distinction between artifacts that are shared among different actors in a company (boundary objects) and those that are used within a team (locally relevant artifacts). We propose an analysis approach to identify boundary objects and three practices to manage systems engineering artifacts in industry

Reverse Presentations - A Client-Driven Method for Requirements Engineering in Offshore Software Development

Reverse Presentations is a method for requirements validation in offshore software development. In this paper, the authors present and conceptually refine this method and carry out an initial evaluation. The method provides cross-phase support and is characterized by a structured and iterative validation process. In contrast to existing methods, it focuses on the client perspective and takes into account social distance challenges. The method aims at creating a common understanding of the future system by means of “reverse presentations”. This core element of the method facilitates the transfer of knowledge across social worlds for validation purposes. Case studies with clients confirm that the method fits well with the offshore software development context. The cases point to the method’s positive impact on the interorganizational interaction and control

Effective communication in requirements elicitation: A comparison of methodologies

The elicitation or communication of user requirements comprises an early and critical but highly error-prone stage in system development. Socially oriented methodologies provide more support for user involvement in design than the rigidity of more traditional methods, facilitating the degree of user-designer communication and the 'capture' of requirements. A more emergent and collaborative view of requirements elicitation and communication is required to encompass the user, contextual and organisational factors. From this accompanying literature in communication issues in requirements elicitation, a four-dimensional framework is outlined and used to appraise comparatively four different methodologies seeking to promote a closer working relationship between users and designers. The facilitation of communication between users and designers is subject to discussion of the ways in which communicative activities can be 'optimised' for successful requirements gathering, by making recommendations based on the four dimensions to provide fruitful considerations for system designers