Tags: 1997, conceptual modeling
There has been increasing awareness of the impact of the early stages of systems development on the quality of information systems. A critical early activity is requirements definition, when the requirements for an information system are determined. Traditional requirements capture techniques do not support the collaborative nature of requirements definition or the emergent nature of requirements themselves. This paper focuses on viewpoint development as a means of resolving some of the difficulties of requirements definition. It proposes a user viewpoint model for capturing and representing the viewpoints of users during requirements acquisition. The model can facilitate communication and interaction between analysts and users and help build a shared understanding of requirements. It can be used to structure the requirements acquisition process. The model provides for evaluation of requirements acquisition techniques to guide the selection of appropriate techniques for developing user viewpoint models. The paper reports a multiple‐case study of requirements definition efforts that examined user viewpoint development in practice and used the cases to validate empirically the concepts of the user viewpoint model. The implications of the case study findings for requirements definition practice are discussed, and some areas for future research are identified.Read the full paper here: https://www.journals.elsevier.com/information-systems
