Requirements reuse and requirement patterns: a state of the practice survey

Context. Requirements engineering is a discipline with numerous challenges to overcome. One of these challenges is the implementation of requirements reuse approaches. Although several theoretical proposals exist, little is known about the practices that are currently adopted in industry. Objective. Our goal is to contribute to the investigation of the state of the practice in the reuse of requirements, eliciting current practices from practitioners, and their opinions whenever appropriate. Besides reuse in general, we focus on requirement patterns as a particular strategy to reuse. Method. We conducted an exploratory survey based on an online questionnaire. We received 71 responses from requirements engineers with industrial experience in the field, which were analyzed in order to derive observations. Results. Although we found that a high majority of respondents declared some level of reuse in their projects (in particular, non-functional requirements were identified as the most similar and recurrent among projects), it is true that only a minority of them declared such reuse as a regular practice. Larger IT organizations and IT organizations with well-established software processes and methods present higher levels of reuse. Ignorance of reuse techniques and processes is the main reason preventing wider adoption. From the different existing reuse techniques, the simplest ones based on textual copy and subsequent tailoring of former requirements are the most adopted techniques. However, participants who apply reuse more often tend to use more elaborate techniques. Opinions of respondents about the use of requirement patterns show that they can be expected to mitigate problems related to the quality of the resulting requirements, such as lack of uniformity, inconsistency, or ambiguity. The main reasons behind the lack of adoption of requirement patterns by practitioners (in spite of the increasing research approaches proposed in the community) are related to the lack of a well-defined reuse method and involvement of requirement engineers.Peer ReviewedPostprint (author's final draft

A requirements-based software process maturity model

The requirements phase of software development is an on-going problem for the software engineering community. The many disparate recommendations and best practices found in the literature make it difficult for software organisations to recognise which practices apply to their individual needs. The aim of this thesis is to pull together key solutions into a framework that allows practitioners to assess where their requirements process needs strengthening and to provide a means in which improvements can be achieved. In this thesis I show how I design, develop and validate a model of requirements engineering processes. This requirements capability maturity model (R-CMM) adheres to the characteristics of the Software Engineering Institute's Software Capability Maturity Model (SW-CMM) and is designed to take practitioners from an immature process capability through to an advanced capability. I contribute to the body of knowledge in both software process improvement and requirements engineering (RE) by providing rigorous detail of how a process maturity framework is developed to support RE practices. The model is generic and should apply to many software development organisations. The R-CMM guides users towards a view of RE that is based on goals and is problem driven. The SW-CMM framework is transformed into a simplified model that relates goals and problems to individual RE practises

Defining the role of the business analyst: the business analysis service framework

This thesis reports on an empirical study into business analysis (BA), a professional IS discipline. This subject is deemed relevant for investigation for three reasons: the volume of BA practitioners employed worldwide; the continuing problems reported regarding IS project outcomes; and the lack of empirical research that has been conducted into BA. A key area of concern for IS projects is the definition of requirements, an area that falls within the BA remit. However, there is limited extant literature concerning BA and there is ambiguity with regard to the business analyst role. Role theory (Solomon et al. 1985) suggests that a lack of role clarity can diminish performance and cause uncertainty on the part of practitioners and customers. Therefore, the aim of this research is to clarify the role of the IS business analyst and offer a service definition that will support the effective conduct of BA work. A conceptual framework for this study, adapted from the work of Pettigrew et al (2001), is used to examine the business analyst role from four dimensions: the organisational and personal context for BA; the content of IS projects; the process standards, skills and techniques for performing BA; and the outcomes from BA. Case study research has been carried out to explore perspectives on BA. The case is the Business Analysis Manager Forum (BAMF), a professional organisation for managerial-level business analysts. Selected BAMF representatives, all designated BA specialists, shared their experiences and observations regarding the business analyst role, activities and work practices. The data provided by the BA specialists was analysed using template analysis in order to identify themes within the data. Service science provided a theoretical basis for examining the activities performed by business analysts, the skills and techniques used, and the potential for value co-creation with business stakeholders. This enabled the identification and definition of the core services offered by business analysts. The study resulted in the development of two artefacts that are intended to support understanding and recognition of BA: the Business Analysis Service Framework, which defines six services and their corresponding activities, techniques and value proposition; and the business analyst T-shape, which has applied the T-shaped professional concept (Spohrer and Maglio, 2010) to define the skills and techniques required of professional business analysts. These artefacts are proposed as a means of clarifying the business analyst role for practitioners, their business stakeholders and future researchers and, as such, offer a positive contribution to BA theory and practice

Improving Customer Value Co-creation through Customer Engagement and Requirements Engineering Practices in a Small Software Company

A small software company has startup thinking which is often short-term. This may negate requiring planning for long-term growth, and sustainability, which could have its impact on customer value. Customer engagement (CE) and requirements engineering (RE) practices are customer satisfaction and growth oriented; helping a small software company earn competitive edge, increase productivity, and grow while delivering on customer value. To address the stated problem, the research problem is stated thus: How do CE and RE practices impact customer value (CV) co-creation? An action research study was carried out to understand better CE and RE practices at the case company. For data collection triangulation of semi-structured interviews, informal conversations, participant observation, and work experience were used. Data analysis did use some grounded theory features — interpretative statements in gathering and organizing the data got. CE practices such as having dedicated customer co-creation platform, constantly learning from users, customer segmentation, and broadened view of customer were observed to have positive influence on customer value co-creation. RE practices that advance customer value included customer participation, face-to-face-communication, continuous planning, and requirements management. The level of success of these practices was influenced by differences in customer participation level, elicitation techniques scope, and selection of the techniques. Also, lack of dedicated user environment hinders user interaction and user-centered co-creation. Customer engagement strengthens RE practices through active interaction between provider and customer to positively influence CV co-creation. Such interaction could be amongst provider, customer and end-users. There are four CE practices and seven RE practices established at the case company. Understanding CE significantly, and some of its practices, coupled with RE practices that yield high- perceived value may significantly help improve customer CV co-creation. Practices like detailed documentation, use of prototype, change and requirements management, co-creation platform, and participation in the platform can be improved upon

AMAN-DA : Une approche basée sur la réutilisation de la connaissance pour l'ingénierie des exigences de sécurité

In recent years, security in Information Systems (IS) has become an important issue that needs to be taken into account in all stages of IS development, including the early phase of Requirement Engineering (RE). Considering security during early stages of IS development allows IS developers to envisage threats, their consequences and countermeasures before a system is in place. Security requirements are known to be “the most difficult of requirements types”, and potentially the ones causing the greatest risk if they are not correct. Moreover, requirements engineers are not primarily interested in, or knowledgeable about, security. Their tacit knowledge about security and their primitive knowledge about the domain for which they elicit security requirements make the resulting security requirements poor and too generic.This thesis explores the approach of eliciting requirements based on the reuse of explicit knowledge. First, the thesis proposes an extensive systematic mapping study of the literature on the reuse of knowledge in security requirements engineering identifying the diferent knowledge forms. This is followed by a review and classification of security ontologies as the main reuse form.In the second part, AMAN-DA is presented. AMAN-DA is the method developed in this thesis. It allows the elicitation of domain-specific security requirements of an information system by reusing knowledge encapsulated in domain and security ontologies. Besides that, the thesis presents the different elements of AMANDA: (i) a core security ontology, (ii) a multi-level domain ontology, (iii) security goals and requirements’s syntactic models, (iv) a set of rules and mechanisms necessary to explore and reuse the encapsulated knowledge of the ontologies and produce security requirements specifications.The last part reports the evaluation of the method. AMAN-DA was implemented in a prototype tool. Its feasibility was evaluated and applied in case studies of three different domains (maritime, web applications, and sales). The ease of use and the usability of the method and its tool were also evaluated in a controlled experiment. The experiment revealed that the method is beneficial for the elicitation of domain specific security requirements, and that the tool is friendly and easy to use.Au cours de ces dernières années, la sécurité des Systèmes d'Information (SI) est devenue une préoccupation importante, qui doit être prise en compte dans toutes les phases du développement du SI, y compris dans la phase initiale de l'ingénierie des exigences (IE). Prendre en considération la sécurité durant les premieres phases du dévelopment des SI permet aux développeurs d'envisager les menaces, leurs conséquences et les contre-mesures avant qu'un système soit mis en place. Les exigences de sécurité sont connues pour être "les plus difficiles des types d’exigences", et potentiellement celles qui causent le plus de risque si elles ne sont pas correctes. De plus, les ingénieurs en exigences ne sont pas principalement intéressés à, ou formés sur la sécurité. Leur connaissance tacite de la sécurité et leur connaissance primitive sur le domaine pour lequel ils élucident des exigences de sécurité rendent les exigences de sécurité résultantes pauvres et trop génériques.Cette thèse explore l'approche de l’élucidation des exigences fondée sur la réutilisation de connaissances explicites. Tout d'abord, la thèse propose une étude cartographique systématique et exhaustive de la littérature sur la réutilisation des connaissances dans l'ingénierie des exigences de sécurité identifiant les diférentes formes de connaissances. Suivi par un examen et une classification des ontologies de sécurité comme étant la principale forme de réutilisation.Dans la deuxième partie, AMAN-DA est présentée. AMAN-DA est la méthode développée dans cette thèse. Elle permet l’élucidation des exigences de sécurité d'un système d'information spécifique à un domaine particulier en réutilisant des connaissances encapsulées dans des ontologies de domaine et de sécurité. En outre, la thèse présente les différents éléments d'AMAN-DA : (i) une ontologie de sécurité noyau, (ii) une ontologie de domaine multi-niveau, (iii) des modèles syntaxique de buts et d’exigences de sécurité, (iv) un ensemble de règles et de mécanismes nécessaires d'explorer et de réutiliser la connaissance encapsulée dans les ontologies et de produire des spécifications d’exigences de sécurité.La dernière partie rapporte l'évaluation de la méthode. AMAN-DA a été implémenté dans un prototype d'outil. Sa faisabilité a été évaluée et appliquée dans les études de cas de trois domaines différents (maritimes, applications web, et de vente). La facilité d'utilisation et l’utilisabilité de la méthode et de son outil ont également été évaluées dans une expérience contrôlée. L'expérience a révélé que la méthode est bénéfique pour l’élucidation des exigences de sécurité spécifiques aux domaines, et l'outil convivial et facile à utiliser

Definition and use of software requirement patterns in requirements engineering

The final quality of software products and services depends on the requirements stated in the Software Requirements Specifications (SRSs). However, some problems like ambiguity, incompleteness and inconsistency have been reported in the writing of SRSs, especially when natural language is used. Requirements reuse has been proposed as a key asset for requirements engineers to efficiently elicit, validate and document software requirements and, as a consequence, obtain SRSs of better quality through more effective engineering processes. Among all the possible techniques to achieve reuse, patterns hold a prominent position. In their most classical form, patterns describe problems that occur over and over again, and then describe the core of the solution to these problems. Software engineering practitioners have adopted the notion of pattern in several contexts, remarkably related to software design (e.g., design patterns and software architectural patterns), but also in other software development phases, both earlier and later. Following this strategy, requirement patterns emerge as a natural way to reuse knowledge during the Requirements Engineering (RE) stage. Although there have been several techniques proposed to reuse requirements, it has been observed that no concrete proposal has achieved a wide acceptance, neither any covered all the necessary elements to encourage organizations to adopt requirements reuse. As a consequence, this thesis proposes the use of Software Requirement Patterns (SRPs) as a means to capture and reuse requirements knowledge in the context of information technology projects. Following the typical context-problem-solution structure of patterns, an SRP mainly consists of: a template (solution) that may generate one or more requirements when applied in a certain project, and some information (context-problem) to identify its applicability in that project. To facilitate their use, SRPs are encapsulated inside the PABRE (PAttern-Based Requirements Elicitation) framework. The framework covers all the elements that could be critical for the adoption of a requirements reuse technique. Specifically, the framework includes: - A metamodel that describes the structure and semantics of SRPs and their organization inside a catalogue. - An SRP catalogue composed by non-functional, non-technical and functional SRPs, the functional ones being specific for the content management system domain. - A method for guiding the use of an SRP catalogue during requirements elicitation and specification, as well as another one for constructing and updating it. - An economic model to perform cost-benefit analysis on the adoption of SRPs based on return-on-investment. - The PABRE system as technological support. In order to analyse the benefits and drawbacks of the SRPs proposed in this thesis, two empirical studies have been carried out to investigate the perception of participants about requirement patterns in general and SRPs in particular. The first one is an exploratory survey addressed to information technology people with industrial experience in RE, which analyses the current state of the practice of requirement patterns approaches. The second one corresponds to a set of semi-structured interviews, focussed on the SRP approach, conducted to requirements engineers of Swedish organizations. Moreover, as it has been discovered that there are few empirical studies showing the state of the practice of requirements reuse in industry, the first study also explores the current situation of requirements reuse practices in organizations.La qualitat final dels productes i serveis de software depèn del requisits definits en l’especificació de Requisits Software (ERS). Tot i així, alguns problemes com la ambigüitat, incompletesa i inconsistència han sigut detectats en la escriptura dels ERS, especialment quan el llenguatge natural és usat per escriure’ls. La reutilització de requisits ha sigut proposada com un recurs clau pels enginyers de requisits per tal d’obtenir, validar i documentar requisits software i, com a conseqüència, obtenir ERS de millor qualitat usant processos d’enginyeria més efectius. Entre totes les tècniques possibles per aconseguir la reutilització, els patrons tenen una posició destacada. En la seva forma més clàssica, els patrons descriuen problemes que ocorren sovint, i després descriuen la part central de la solució a aquests problemes. Els professionals de la enginyeria del software han adoptat la noció de patró en diferents àmbits, especialment en els relacionats amb el disseny del software (per exemple, els patrons de disseny i els patrons d’arquitectura del software), però també en altres etapes del desenvolupament del software, tant abans com després del seu disseny. Seguint aquesta estratègia, els patrons de requisits emergeixen com una manera natural de reutilitzar coneixement durant l’etapa d’enginyeria de requisits. Tot i que hi ha hagut varies tècniques proposades per reutilitzar requisits, s’ha observat que no hi ha cap proposta concreta que hagi aconseguit una àmplia acceptació, ni cap proposta completa que cobreixi tots els elements necessaris per animar a les organitzacions a adoptar la reutilització de requisits. Com a conseqüència, aquesta tesis proposa l’ús de Patrons de Requisits Software (en anglès Software Requirement Patterns o SRPs) com un medi per capturar i reutilitzar coneixement de requisits en l’àmbit de projectes de tecnologia de la informació. Seguint la estructura típica dels patrons de context-problema-solució, un SRP consisteix en: una plantilla (solució) que pot generar un o més requisits quan és aplicat en un projecte específic, i informació relacionada (context-problema) per identificar la seva aplicabilitat en un projecte. Per facilitar el seu ús, els SRP han sigut encapsulats dintre del framework PABRE (de l’anglès PAttern-Based Requirements Elicitation). El framework cobreix tots els elements que podrien ser crítics per adoptar una tècnica de reutilització de requisits. Més detalladament, el framework inclou: - Un meta model que descriu la estructura i semàntica dels SRPs i la seva organització dintre d’un catàleg.Postprint (published version

Social Technologies and Informal Knowledge Sharing within and across Organizations

This doctoral dissertation is focused on both empirical and conceptual contributions relative to the roles social technologies play in informal knowledge sharing practices, both within and across organizations. Social technologies include (a) traditional social technologies (e.g., email, phone and instant messengers), (b) emerging social networking technologies commonly known as social media, such as blogs, wikis, major public social networking sites (e.g., Facebook, Twitter and LinkedIn), and (c) enterprise social networking technologies controlled by a host organization ( e.g., SocialText). The rapid uptake of social technologies, combined with growing interest in their broader social implications, raises pertinent questions about uses for knowledge sharing in organizations. The work reported in this thesis is motivated by two broad phenomena: (1) the importance of informal knowledge-sharing in organizations and (2) the rapid rise in the variety and prevalence of social technologies. The empirical basis of this research is a field study focused on the uses of social technologies by knowledge workers, specifically those in consulting firms. Building from the theoretical lenses of sociomateriality, structuration, and technological frames, the findings from this work advances our understanding of: (1) the ways social technologies are used in combination as a suite of tools, (2) the ways in which organizational norms, policies, and arrangements shape the uses of social technologies for knowledge practices, and (3) the variations in uses of social technologies by different groups of knowledge workers. The theoretical contribution of this work is to conceptualize the suite of social technologies used to support and enable knowledge workers is a more useful approach than the single-technological-tool-in-isolation approach, which is the norm in studies of computing. A second contribution of this work is to situate social technologies-in-use through incorporating complementary theoretical concepts: technology-mediated knowledge practices, social structures of organizations, and workers\u27 distinct interpretations of social technologies (technological frames). Practical implications arising from this study both inform the ways social technologies can be collectively integrated in work practices and inform the design and implementation of social technologies for accommodating different needs and preferences of knowledge workers. This research also generates insight into how organizations can craft policies that realistically regulate the use of social technologies, while empowering individual workers to optimize their knowledge sharing capacity by supporting informal engagement via social technologies

Evaluation and development models for business processes

Most organisations are working hard to improve their performance and to achieve competitive advantage over their rivals. They may accomplish these ambitions through carrying out their business processes more effectively. Hence it is important to consider such processes and look for ways in which they can be improved. Any organisational business process encompasses several elements that interact and collaborate with each other to achieve the required objectives. These elements can be classified into hard aspects, which deal with tangible issues related to the software system or the technology in general, and soft aspects, which deal with issues related to the human part of the business process. If the business process needs to be analysed and redesigned to improve its performance, it is important to use a suitable approach or intervention that takes into account all of these elements. This thesis proposes an approach to investigate organisational business processes by considering both soft and hard aspects. The approach, Soft Workflow Modelling (SWfM), is developed as a result of reviewing several workflow products and models using a developed workflow perspectives framework which involves several perspectives covering the soft and hard aspects of the workflow system. The SWfM approach models the organisational business process as a workflow system by handling the various perspectives of the workflow perspectives framework. This approach combines the Soft Systems Methodology (SSM) with the Unified Modelling Language (UML), as a standard modelling language of the object-oriented paradigm. The basic framework adopted is that of SSM with the inclusion of UML diagrams and techniques to deal with the aspects that SSM cannot handle. The approach also supports SSM by providing a developed tool to assist in constructing a conceptual model which is considered as the basis to model the workflow system. A case study is developed for illustrative purposes.EThOS - Electronic Theses Online ServiceGBUnited Kingdo

'Wi Run Tings, Tings Nuh Run Wi':Black Humanity and the Nonhuman World in Anglophone Caribbean Neo-slave Narratives, 1983-2020

Anti-Black stereotypes have been scrutinised in cross- and inter-disciplinary studies, but as Anthony Layng states, ‘there has been no cross-cultural functional analysis of the [a]etiology of ethnic images in the [Caribbean] region’ (Layng, 1975, p. 130). Several decades have passed since Layng addressed this critical gap. However, his words remain true in literary studies. While attending to this gap, this thesis brings attention to another. The neo-slave narrative, which has become a powerful tool for writing back, has been praised in critical writings predominantly for its rehumanising adeptness. Largely disregarded is how the genre represents the nonhuman world and modes of interspecies bonds that informed enslaved people’s survival and resistance. Completely overlooked is how the genre reveals the historical role the nonhuman was made to play in constructing and perpetuating the degrading anti-Black images that justified violence. The analysis of the selected neo-slave narratives reveals how Caribbean writers depict the bio-political control of Black bodies as reflected in and perpetuated by controlling images that depict the nonhuman world as open to invasion. Framed as exotic and erotic, enslaved people are also being rewritten in these texts in ways that uncover hidden histories of human-and-nonhuman engagements and oppression. This study brings ecocriticism and decolonial scholarship together in one sustained dialogue to argue that the responses to, and demythologisation of, Western stereotypes by Anglophone Caribbean writers is an attempt to reclaim Black humanity and promote positive ecological practices. Emerging in the analysis are examples of the power of the neo-slave narrative genre to look backwards to recuperate a suppressed history and forward to attentive responses to Black humanity and the nonhuman world. My fictional corpus includes The Book of Night Women (2009) by Marlon James, I is a Long Memoried Woman (1983) by Grace Nichols, Slave Song (1984) by David Dabydeen and Cane Warriors (2020) by Alex Wheatle