Alternatives to Overcome the Communications Problem of Formal Requirements Analysis.

Mittermeir, Roland T.; Hsia, Pei; Yeh, Raymond T.

doi:10.21236/ada125650

Cited by 21 publications

(15 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There has been increasing awareness of the impact of the early stages of the systems development process on the quality of the information systems that are ultimately delivered. A critical early activity is requirements definition, when the requirements for an information system are determined and expressed as a requirements specification (Mittermeir et al, 1987;Greenspan et al, 1994). Significant difficulties can arise during subsequent development activities if requirements specifications are incomplete, unclear or incorrect (Roman, 1985;Curtis et al, 1988), and difficulties and inadequacies in requirements have been identified as a major factor in information systems failures (Boehm, 1981;Lyytinen & Hirschheim, 1987).…”

Section: Abstract: Requirements Analysis Requirements Definition VImentioning

confidence: 99%

User viewpoint modelling: understanding and representing user viewpoints during requirements definition

Darke

Shanks

1997

Information Systems Journal

View full text Add to dashboard Cite

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.

show abstract

Section: Abstract: Requirements Analysis Requirements Definition VImentioning

confidence: 99%

User viewpoint modelling: understanding and representing user viewpoints during requirements definition

Darke

Shanks

1997

Information Systems Journal

View full text Add to dashboard Cite

show abstract

“…The requirements identification involves the user in a communication process. Effective communication is needed to support the collaborative behaviors necessary for requirements elicitation (Mittermeir, Hsia, & Yeh, 1987; Bostrom, 1989; Newman & Robey, 1992).…”

Section: Literature Review and Hypotheses Developmentmentioning

confidence: 99%

Reducing Requirement Incorrectness and Coping with Its Negative Impact in Information System Development Projects

Hsu¹,

Lin²,

Cheng³

et al. 2012

Decision Sciences

View full text Add to dashboard Cite

The negative impact of incorrect requirements on information system development (ISD) project performance has long been acknowledged. This study addresses the problem of incorrect requirements by proposing a model that combines the error reduction and coping concepts proposed by Field, Ritzman, Safizadeh, and Downing (2006) with the view that ISD is a knowledge‐intensive process. The model hypothesizes that when developers and users possess an understanding of each other's primary domain of knowledge, the prevention of incorrect requirements and the mitigation of the negative consequences of incorrect requirements tend to improve project performance. Data collected from 250 ISD professionals on the basis of their experiences of recently completed ISD projects confirmed all of our hypotheses. The results demonstrate that the eliciting of incorrect requirements can be reduced when users and developers possess cross‐domain understanding and when requirement analysis methodologies and techniques are available. Furthermore, the negative impact of incorrect requirements on project performance can be mitigated when developers have sufficient ISD knowledge and behavioral knowledge.

show abstract

“…Models in information systems development attempt to overcome the ambiguity of natural language. However, Mittermeir et al (1982) point out that although notation is an important element for efficient communication, both the communicator and the recipient must understand the notation used. Proponents of systems development models hold the view that the notation adopted is intuitive, requiring little explanation.…”

Section: Languagementioning

confidence: 99%

“…The members of the community entered have a subjective view of their environment and consider the holistic impact of changes, they are only interested in technology to the extent of its impact on their work. Mittermeir et al (1982) describe this distinction between views as users and systems developers holding different frames of reference. The users perceive a holistic system to adopt in the environment in which they are submerged while analysts decompose the system into objects, data, processes, volumes and time constraints.…”

Section: Cognitionmentioning

confidence: 99%

Tribes of Users and System Developers

Dingley¹,

Shah²,

Colder³

2000

AJIS

View full text Add to dashboard Cite

Effective communication is essential for information systems development crossing functional, organisational and national boundaries. As organisations attempt to overcome cultural barriers to communication across the world, communication with colleagues across the corridor remains problematic; cultural barriers between departments remain unchallenged. This paper introduces the concepts of 'culture' and 'tribe' into the discussion of the relationship between business users and information systems developers. Previous research has focused on identifying specific barriers to user-systems developer communication and on ways of eliminating these barriers. In contrast, this paper suggests that much can be learnt through the recognition of cultural differences inherent to the differing roles of user and systems developer. Maintenance of cultural identity is essential to the individual if he/she is to function effectively as a member of his/her tribe, whether it is the 'tribe' of developers or the 'tribe' of users. Communication problems within the systems development process may be addressed by a mutual understanding of cultural differences between the 'tribes' of users and systems developers. This degree of understanding cannot be achieved by attempting to change, persuade or convert the other tribe. The problems of user-systems developer communication need to be addressed through effective communication which acknowledges the differing cultures.

show abstract

Alternatives to Overcome the Communications Problem of Formal Requirements Analysis.

Cited by 21 publications

References 0 publications

User viewpoint modelling: understanding and representing user viewpoints during requirements definition

User viewpoint modelling: understanding and representing user viewpoints during requirements definition

Reducing Requirement Incorrectness and Coping with Its Negative Impact in Information System Development Projects

Tribes of Users and System Developers

Contact Info

Product

Resources

About