addressing organisational issues in requirements engineering practice: lessons from action cases
Clicks: 125
ID: 241947
1999
Article Quality & Performance Metrics
Overall Quality
Not rated
Combines reader engagement with the AI quality analysis. This
article has not been analysed, so there is no overall score —
reader engagement is measured and shown alongside.
Reader Engagement
Popular Article
30.0
/100
125 views
29 readers
AI Quality Assessment
Not analyzed
Readership in this journal
PopularRanked #62 of 68 articles by views in expert review of clinical pharmacology
Most read
Least read
Bar heights use a square-root scale.
Mint this article as an NFT
Not yet mintedCreate a permanent, verifiable on-chain record of this article on the Scimatic Network. The NFT is held in your Journament account, and you can withdraw it to your own wallet at any time.
5
SUSD
one-off · no wallet required
Abstract
The requirements phase of information systems development is arguably the most organizationally dependent phase and as such it could be contended that the methods used in this phase ought to explicitly address organizational issues. However the authors would maintain that there is a weakness in many of the methods that are employed in requirements engineering in that they arc not explicitly embedded within any social scientific perspective. We argue that such a perspective would enable the systems developer to address organizational contexts and to engage with users (social actors) in such a way that it may be possible to find out about their social situations and as a consequence better inform the systems development process. In this paper we present the arguments for an explicit organizational perspective in the requirements phase of information systems development. We illustrate the argument through the presentation of action case studies in which one of the authors intervened in two situations with an explicit sociological perspective and analysis methods more commonly associated with qualitative social science methods. We conclude that there is an imperative need for those involved in the requirements phase to be explicit in their assumptions about organizations and critically reflective about the methods they use if they wish to understand the domain in which they operate.
| Reference Key |
hughes1999australasianaddressing
Use this key to autocite in the manuscript while using
SciMatic Manuscript Manager or Thesis Manager
|
|---|---|
| Authors | ;Jim Hughes;Trevor Wood-Harper |
| Journal | expert review of clinical pharmacology |
| Year | 1999 |
| DOI |
10.3127/ajis.v6i2.293
|
| URL | |
| Keywords |
Citations
No citations found. To add a citation, contact the admin at info@scimatic.org
Comments
No comments yet. Be the first to comment on this article.