1994
DOI: 10.1049/ise.1994.0003
|View full text |Cite
|
Sign up to set email alerts
|

Responsibility modelling as a technique for organisational requirements definition

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
7
0

Year Published

1996
1996
2015
2015

Publication Types

Select...
5
2
1

Relationship

1
7

Authors

Journals

citations
Cited by 16 publications
(8 citation statements)
references
References 1 publication
1
7
0
Order By: Relevance
“…Responsibilities and relationships are modeled rather than activities, and information is modeled from the point of view of the contracts involved. The process includes the identification of the requirements owners together with their positions and roles in the organization, and the identification of the user community, and others affected by the system together with their roles and responsibilities in the organization (Dobson, Blyth, Chudge and Strens, 1992;Strens and Dobson, 1994). Figure 5 shows the ORDIT methodology managed through a concept mapping tool.…”
Section: Figure 4 Catwoe Analysis Operationalized In a Concept Mappinmentioning
confidence: 99%
“…Responsibilities and relationships are modeled rather than activities, and information is modeled from the point of view of the contracts involved. The process includes the identification of the requirements owners together with their positions and roles in the organization, and the identification of the user community, and others affected by the system together with their roles and responsibilities in the organization (Dobson, Blyth, Chudge and Strens, 1992;Strens and Dobson, 1994). Figure 5 shows the ORDIT methodology managed through a concept mapping tool.…”
Section: Figure 4 Catwoe Analysis Operationalized In a Concept Mappinmentioning
confidence: 99%
“…Responsibility modeling has been used to analyze various aspects of a socio-teclmical system where the 'technical' part of the system is an Information System that is placed in a social setting [2][3][4][5][6]. It was developed as the basis of its modeling language by the ORDIT project [2,3,4], which aimed to develop a methodology that would enable systems designers to reason about organizational goals, policies and structures, and the work roles of intended end users in a way that would facilitate the identification and expression of organizational requirements for IT systems.…”
Section: Responsibility Modelingmentioning
confidence: 99%
“…It was developed as the basis of its modeling language by the ORDIT project [2,3,4], which aimed to develop a methodology that would enable systems designers to reason about organizational goals, policies and structures, and the work roles of intended end users in a way that would facilitate the identification and expression of organizational requirements for IT systems. Models based on responsibilities are used to discuss human requirements of socio-technical systems, and to demonstrate how these are linked to the technical features of the system design.…”
Section: Responsibility Modelingmentioning
confidence: 99%
See 1 more Smart Citation
“…However, the use of the notion of a role can vary: from the assignment of a task, as proposed by Yu [47], to a position within an organisational hierarchy [37]. Existing approaches to modelling requirements are inadequate for representing complex relationships between actors in large organisations, such as the lines of authority, the organisational structure, and the basis by which work is delegated [39] [28]. This can lead to misunderstandings about the precise meaning of actors, their roles, and, consequently, their access rights and privileges.…”
Section: Introductionmentioning
confidence: 99%