157,057 research outputs found

    An analysis of the requirements traceability problem

    Get PDF
    In this paper1, we investigate and discuss the underlying nature of the requirements traceability problem. Our work is based on empirical studies, involving over 100 practitioners, and an evaluation of current support. We introduce the distinction between pre-requirements specification (pre-RS) traceability and post-requirements specification (post-RS) traceability, to demonstrate why an all-encompassing solution to the problem is unlikely, and to provide a framework through which to understand its multifaceted nature. We report how the majority of the problems attributed to poor requirements traceability are due to inadequate pre-RS traceability and show the fundamental need for improvements here. In the remainder of the paper, we present an analysis of the main barriers confronting such improvements in practice, identify relevant areas in which advances have been (or can be) made, and make recommendations for research

    Culture-based artefacts to inform ICT design: foundations and practice

    Get PDF
    Cultural aspects frame our perception of the world and direct the many different ways people interact with things in it. For this reason, these aspects should be considered when designing technology with the purpose to positively impact people in a community. In this paper, we revisit the foundations of culture aiming to bring this concept in dialogue with design. To inform design with cultural aspects, we model reality in three levels of formality: informal, formal, and technical, and subscribe to a systemic vision that considers the technical solution as part of a more complex social system in which people live and interact. In this paper, we instantiate this theoretical and methodological view by presenting two case studies of technology design in which culture-based artefacts were employed to inform the design process. We claim that as important as including issues related to culture in the ICT design agenda—from the conception to the development, evaluation, and adoption of a technology—is the need to support the design process with adequate artefacts that help identifying cultural aspects within communities and translating them into sociotechnical requirements. We argue that a culturally informed perspective on design can go beyond an informative analysis, and can be integrated with the theoretical and methodological framework used to support design, throughout the entire design process

    Rationale in Development Chat Messages: An Exploratory Study

    Full text link
    Chat messages of development teams play an increasingly significant role in software development, having replaced emails in some cases. Chat messages contain information about discussed issues, considered alternatives and argumentation leading to the decisions made during software development. These elements, defined as rationale, are invaluable during software evolution for documenting and reusing development knowledge. Rationale is also essential for coping with changes and for effective maintenance of the software system. However, exploiting the rationale hidden in the chat messages is challenging due to the high volume of unstructured messages covering a wide range of topics. This work presents the results of an exploratory study examining the frequency of rationale in chat messages, the completeness of the available rationale and the potential of automatic techniques for rationale extraction. For this purpose, we apply content analysis and machine learning techniques on more than 8,700 chat messages from three software development projects. Our results show that chat messages are a rich source of rationale and that machine learning is a promising technique for detecting rationale and identifying different rationale elements.Comment: 11 pages, 6 figures. The 14th International Conference on Mining Software Repositories (MSR'17

    Assessment of the NASA Flight Assurance Review Program

    Get PDF
    The NASA flight assurance review program to develop minimum standard guidelines for flight assurance reviews was assessed. Documents from NASA centers and NASA headquarters to determine current design review practices and procedures were evaluated. Six reviews were identified for the recommended minimum. The practices and procedures used at the different centers to incorporate the most effective ones into the minimum standard review guidelines were analyzed and guidelines for procedures, personnel and responsibilies, review items/data checklist, and feedback and closeout were defined. The six recommended reviews and the minimum standards guidelines developed for flight assurance reviews are presented. Observations and conclusions for further improving the NASA review and quality assurance process are outlined

    The role of earth observation in an integrated deprived area mapping “system” for low-to-middle income countries

    Get PDF
    Urbanization in the global South has been accompanied by the proliferation of vast informal and marginalized urban areas that lack access to essential services and infrastructure. UN-Habitat estimates that close to a billion people currently live in these deprived and informal urban settlements, generally grouped under the term of urban slums. Two major knowledge gaps undermine the efforts to monitor progress towards the corresponding sustainable development goal (i.e., SDG 11—Sustainable Cities and Communities). First, the data available for cities worldwide is patchy and insufficient to differentiate between the diversity of urban areas with respect to their access to essential services and their specific infrastructure needs. Second, existing approaches used to map deprived areas (i.e., aggregated household data, Earth observation (EO), and community-driven data collection) are mostly siloed, and, individually, they often lack transferability and scalability and fail to include the opinions of different interest groups. In particular, EO-based-deprived area mapping approaches are mostly top-down, with very little attention given to ground information and interaction with urban communities and stakeholders. Existing top-down methods should be complemented with bottom-up approaches to produce routinely updated, accurate, and timely deprived area maps. In this review, we first assess the strengths and limitations of existing deprived area mapping methods. We then propose an Integrated Deprived Area Mapping System (IDeAMapS) framework that leverages the strengths of EO- and community-based approaches. The proposed framework offers a way forward to map deprived areas globally, routinely, and with maximum accuracy to support SDG 11 monitoring and the needs of different interest groups

    Information Technology as Coordination Infrastructure

    Get PDF
    Business information technology is traditionally viewed as information provision technology. In this view, organizations use their IT to implement databases that provide people with information when they want it. This view is persistent even though information provision is never an end in itself but always has the further purpose to support the coordination of activities of people. The role if IT as coordination technology became more prominent in the 1980s with the advent of network technology, that allowed activities across different businesses to be coordinated. This trend has accellerated since the growth of Internet usage, and today IT is used to support an increasingly varied range of processes performed by a variety of partners that do not all have a hierarchical relation to each other. This makes it difficult to analyze requirements for IT support and specify IT solutions: Business processes may not be well-defined, and interests of different businesses may clash. This report argues that to deal with this in requirements engineering and IT solution specification, business information technology should not be viewed as IT support for business processes but as IT support for the coordination of activities in one or more businesses. We will identify three basic coordination mechanisms, namely coordination by price, by management, and by shared norms, and for each of these mechanisms, we will identify requirements for IT support. The advent of flexible and standardized networking technology has facilitated the creation of novel coordination mechanisms within these three general paradigms, and we will give an inventory of generalized coordination mechanisms made possible by current IT. Finally, we will draw conclusions for requirements engineering methods for IT support for each of the coordination mechanisms identified by the framework
    corecore