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!
Journal of Industrial Information Integration
Papers
97
Papers 97
1 page of 10 pages (97 results)
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...
1 Citations Source Cite
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...
2 Citations Source Cite
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...
1 Citations Source Cite
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...
2 Citations Source Cite
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...
2 Citations Source Cite
Nan Niu (UC: University of Cincinnati), Daniel Méndez Fernández14
Estimated H-index: 14
(TUM: Technische Universität München)
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 ...
Source Cite
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...
1 Citations Source Cite
12345678910