CASE tool construction for a parallel software development methodology

Gray, Jonathan

doi:10.1016/s0950-5849(96)01145-7

Cited by 11 publications

(10 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Lack of powerful type system. Taylor et al (1988), Miguel et al (1990), Emmerich et al (1992), Liu et al (1996), Gray (1997). Poor support to data that represents graph structures.…”

Section: Problemmentioning

confidence: 99%

“…Lack of facilities for making queries based on such data including finding transitive closure. Hardwick (1984), Miguel et al (1990), Katz (1990), Emmerich et al (1992), Gray (1997), Lange et al (2001).…”

Section: Problemmentioning

confidence: 99%

“…Engle (2003) Lack of possibility to preserve semantics of the relationships. Zhang et al (2001) Fragmentation increases complexity to the user of database according to Gray (1997). Virtual relvars (views) help to overcome this problem in the system that follows the rules of the Third Manifesto.…”

Section: Problemmentioning

confidence: 99%

“…It can have relation-valued attributes which values are calculated using relational operator GROUP that provides relation "nest" capability (Date & Darwen, 2000). Gray (1997) writes that fragmentation may cause performance problems. But "performance is fundamentally an implementation issue, not a model issue."…”

Section: Problemmentioning

confidence: 99%

“…System Arcadia (Taylor et al, 1988) is an example of the system that uses custombuilt object manager. Omega (Linton, 1984), The C Information Abstraction System (Chen et al, 1990), PARSE (Gray, 1997) and CommonKADS repository (Allsop et al, 2002) are examples of the repository systems that use a Relational DBMS (RDBMS). RDBMS in this case is a system which uses a database language that conforms to SQL:1992 standard or is even earlier relational database language.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Using Relational Databases in the Engineering Repository Systems

2006

Proceedings of the Eighth International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

Abstract:Repository system can be built on top of the database management system (DBMS). DBMSs that use relational data model are usually not considered powerful enough for this purpose.In this paper, we analyze these claims and conclude that they are caused by the shortages of SQL standard and inadequate implementations of the relational model in the current DBMSs. Problems that are presented in the paper make usage of the DBMSs in the repository systems more difficult. This paper also explains that relational system that follows the rules of the Third Manifesto is suitable for creating repository system and presents possible design alternatives.

show abstract

“…Lack of powerful type system. Taylor et al (1988), Miguel et al (1990), Emmerich et al (1992), Liu et al (1996), Gray (1997). Poor support to data that represents graph structures.…”

Section: Problemmentioning

confidence: 99%

Section: Problemmentioning

confidence: 99%

Section: Problemmentioning

confidence: 99%

Section: Problemmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Using Relational Databases in the Engineering Repository Systems

2006

Proceedings of the Eighth International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

show abstract

The Design and Implementation of a Repository for the Management of Spatial Data Integrity Constraints

Cockcroft

2004

GeoInformatica

View full text Add to dashboard Cite

Method in Action and Method in Tool: A Stakeholder Perspective

Lundell

Lings

2004

Journal of Information Technology

View full text Add to dashboard Cite

Tool support for information systems (IS) development can be considered from many perspectives, and it is not surprising that different stakeholders perceive such tools very differently. This can contribute on one side to poor selection processes and ineffective deployment of CASE, and on another to inappropriate tool development. In this paper, the relationship between CASE-tools and IS development methods is considered from three stakeholder perspectives: concept developer, IS developer and product developer. These perspectives, and the tensions between them, are characterised within a ‘stakeholder triangle’. Some of the major issues related to each tension are highlighted, and the triangle is then used to consider the importance, and implications for all stakeholders, of considering all tensions together. In particular, we suggest that the concept of ‘method in action’ be complemented by that of ‘method in tool’. We believe that these insights will contribute to the continuing debate on how to reduce adoption failures.

show abstract

CASE tool construction for a parallel software development methodology

Cited by 11 publications

References 17 publications

Using Relational Databases in the Engineering Repository Systems

Using Relational Databases in the Engineering Repository Systems

The Design and Implementation of a Repository for the Management of Spatial Data Integrity Constraints

Method in Action and Method in Tool: A Stakeholder Perspective

Contact Info

Product

Resources

About