China
Africa
Explore chapters and articles related to this topic
Requirements Elicitation Techniques as Communication Channels
Published in Roger H.L. Chiang, Keng Siau, Bill C. Hardgrave, Systems Analysis and Design, 2017
Robert M. Fuller, Christopher J. Davis
For requirements elicitation, a primary indicator of success is that requirements meet end-user needs. However, this outcome has proved difficult to achieve because users frequently experience difficulty in fully articulating their needs—they either cannot explain them in a manner that is readily intelligible by the analyst, or they have not been directly addressed by the analysts’ inquiries (Moores, Change, and Smith, 2004; Siau, 2004).
Model-driven data-intensive Enterprise Information Systems
Published in Enterprise Information Systems, 2018
Milan Zdravković, Ricardo Jardim-Gonçalves
Requirements engineering plays important role and has large impact to the effectiveness of data-intensive systems design. Requirements elicitation is considered as one of the critical factors for successful systems design as it is expected to facilitate reconciliation of the functional and implementation visions of one system, from two quite different and sometimes contradicting viewpoints – customers and developers. Formal representation of those requirements reduces or completely removes bias and ambiguity from their definition and even facilitates reasoning and effective mining over the systems representation, thus enabling detection of incomplete or contradicting definitions (Diamantopoulos and Symeonidis 2018). However, the effectiveness of well-formed requirements can be preserved only if they are continuously maintained throughout whole system engineering process. This is particularly difficult in data-intensive systems due to the dynamics of their environment, often unstructured data, etc. One of the proposed solutions to maintenance related problems is based on data-driven software systems, associated with user interfaces corresponding to used data structures, a software change request service and initial change impact set (Stojanov, Dobrilović, and Stojanov 2018).
A method for identifying customer orientations and requirements for product–service systems design
Published in International Journal of Production Research, 2018
Yoshiki Shimomura, Yutaro Nemoto, Takatoshi Ishii, Toshiyuki Nakamura
For requirement elicitation, there are generally several techniques and approaches, such as interviews, questionnaires, ethnography and scenarios (Zowghi and Coulin 2005). For example, scenarios are narrative and specific descriptions of product/service delivery processes and are effective for identifying not only obvious requirements but also latent requirements. This is because customers are not always aware of their own requirements. Some authors apply a scenario-based approach in requirement elicitation for PSS design (Shimomura and Akasaka 2013; Amaya, Lelah, and Zwolinski 2014). On the other hand, in engineering research, more technical approaches for requirement elicitation have been proposed. For instance, Shimomura et al. proposed a set of forms and glossaries for supporting scenario analysis in PSS design (Kimita et al. 2009; Shimomura and Akasaka 2013).