Branding/Logomark minus Citation Combined Shape Icon/Bookmark-empty Icon/Copy Icon/Collection Icon/Close Copy 7 no author result Created with Sketch. Icon/Back Created with Sketch. Match!

Special issue on just-in-time requirements engineering for software integration

Published on Jan 1, 2019in Journal of Industrial Information Integration
· DOI :10.1016/j.jii.2019.01.003
Nan Niu (UC: University of Cincinnati), Daniel Méndez Fernández14
Estimated H-index: 14
(TUM: Technische Universität München)
Cite
Abstract
Abstract This special issue tackles specific challenges of requirements engineering (RE) in agile and interconnected settings. Compared to traditional upfront RE, the practices in agile or open-source software projects tend to be just-in-time, characterized by lightweight representation and continuous refinement of requirements. The special issue features six articles, ranging from conceptual views through analytic reasonings to empirical studies. Altogether, the collection offers important and timely contributions toward advancing our understanding of RE in industrial information integration and Industry 4.0.
  • References (10)
  • Citations (0)
Cite
References10
Newest
Dirk van der Linden5
Estimated H-index: 5
(UoB: University of Bristol),
Anna Zamansky11
Estimated H-index: 11
(University of Haifa)
+ 1 AuthorsBarnaby Craggs2
Estimated H-index: 2
(UoB: University of Bristol)
Abstract Advances in modern technology, such as the Internet of Things (IoT) and ubiquitous computing, open up new exciting opportunities for technology for animals. This is evidenced by the explosion of products and gadgets available for pets, digital enrichment for captive animals in zoos, sensor based smart farming, etc. At the same time, the emerging discipline of Animal-Computer Interaction (ACI) marks a new era in the design and development of animal technologies, promoting a more animal-c...
Wentao Wang4
Estimated H-index: 4
(UC: University of Cincinnati),
Kavya Reddy Mahakala1
Estimated H-index: 1
(UC: University of Cincinnati)
+ 2 AuthorsYinglin Wang1
Estimated H-index: 1
(SUFE: Shanghai University of Finance and Economics)
Abstract There are several security requirements identification methods proposed by researchers in up-front requirements engineering (RE). However, in open source software (OSS) projects, developers use lightweight representation and refine requirements frequently by writing comments. They also tend to discuss security aspect in comments by providing code snippets, attachments, and external resource links. Since most security requirements identification methods in up-front RE are based on textua...
Woogon Shim1
Estimated H-index: 1
(LG Electronics),
Seok-Won Lee12
Estimated H-index: 12
(Ajou University)
Abstract Nowadays agile development has become a mainstream development methodology. Yet agile is still lacking in how in-depth it deals with Requirement Engineering (RE) compared to the other development stages. There have been attempts to apply agile RE techniques to traditional development and conversely to apply traditional RE techniques to agile development. But the biggest problem is that it is difficult to maintain the essence of agile which is to “ collaborate ”, “ (iterative and frequen...
Anne Hess2
Estimated H-index: 2
(Fraunhofer Society),
Philipp Diebold10
Estimated H-index: 10
(Fraunhofer Society),
Norbert Seyff16
Estimated H-index: 16
(UZH: University of Zurich)
Abstract For traditional software development processes, we have detailed empirical knowledge about role-specific information needs that have to be satisfied in requirements documents. Particularly, we gained detailed knowledge about priorities of a set of traditional requirements artifacts in a series of empirical studies from the viewpoint of software architects, usability engineers, and testers. However, little is known about such information needs from the viewpoint of agile team members. Mo...
Tanmay Bhowmik6
Estimated H-index: 6
(MSU: Mississippi State University),
Anh Quoc Do2
Estimated H-index: 2
(MSU: Mississippi State University)
Abstract Just-in-time (JIT) requirements are characterized as not following the traditional requirement engineering approach, instead focusing on elaboration when the implementation begins. In this experience report, which is an invited extension of a recently published work [1], we first analyze both functional and non-functional JIT requirements from three successful open source software (OSS) projects, including Firefox, Lucene, and Mylyn, to explore the common activities that shaped those re...
Sandeep Reddivari5
Estimated H-index: 5
(UNF: University of North Florida),
Tanmay Bhowmik6
Estimated H-index: 6
(MSU: Mississippi State University),
Corey Hollis1
Estimated H-index: 1
Abstract Being able to quickly and accurately capture requirements is crucial when using agile methodologies. Requirements, to that end, are often captured in an as-needed and informal manner, with continuous stakeholder interaction. Techniques such as interviews, user stories, rapid feedback, and text mining are commonly used in the industry to gather such informal requirements, which are often congruent with the concept of ‘just-in-time’ (JIT)—informally represented and continuously refined—re...
Published on Nov 22, 2016 in PROFES (Product Focused Software Process Improvement)
Jonas Eckhardt7
Estimated H-index: 7
(TUM: Technische Universität München),
Andreas Vogelsang6
Estimated H-index: 6
(Technical University of Berlin),
Daniel Méndez Fernández14
Estimated H-index: 14
(TUM: Technische Universität München)
Requirements are often divided into functional requirements (FRs) and quality requirements (QRs). However, we still have little knowledge about to which extent this distinction makes sense from a practical perspective. In this paper, we report on a survey we conducted with 103 practitioners to explore whether and, if so, why they handle requirements labeled as FRs differently from those labeled as QRs. We additionally asked for consequences of this distinction w.r.t. the development process. Our...
Published on Aug 1, 2014 in RE (IEEE International Conference on Requirements Engineering)
Nan Niu20
Estimated H-index: 20
(UC: University of Cincinnati),
Tanmay Bhowmik6
Estimated H-index: 6
(MSU: Mississippi State University)
+ 1 AuthorsZhendong Niu7
Estimated H-index: 7
(BIT: Beijing Institute of Technology)
Just-in-time requirements management, character- ized by lightweight representation and continuous refinement of requirements, fits many iterative and incremental development projects. Being lightweight and flexible, however, can cause wasteful and procrastinated implementation, leaving certain stakeholder goals not satisfied. This paper proposes traceability- enabled refactoring aimed at fulfilling more requirements fully. We make a novel use of requirements traceability to accurately locate wh...
Published on Oct 1, 2007
Martin Glinz21
Estimated H-index: 21
(UZH: University of Zurich)
Although the term 'non-functional requirement' has been in use for more than 20 years, there is still no consensus in the requirements engineering community what non-functional requirements are and how we should elicit, document, and validate them. On the other hand, there is a unanimous consensus that non-functional requirements are important and can be critical for the success of a project. This paper surveys the existing definitions of the term, highlights and discusses the problems with the ...
Published on Apr 23, 1995 in ICSE (International Conference on Software Engineering)
Lawrence Chung23
Estimated H-index: 23
(UTD: University of Texas at Dallas),
Brian A. Nixon12
Estimated H-index: 12
(U of T: University of Toronto)
Quality characteristics are vital for the success of software systems. To remedy the problems inherent in ad hoc development, a framework has been developed to deal with non-functional requirements (quality requirements or NFRs). Taking the premise that the quality of a product depends on the quality of the process that leads from high-Ievel NFRs to the product, the framework's objectives are to represent NFR-specific requirements, consider design tradeoffs, relate design decisions to IYFRs, jus...
Cited By0
Newest