2004
DOI: 10.1016/s0164-1212(03)00087-6
|View full text |Cite
|
Sign up to set email alerts
|

Changing perceptions of CASE technology

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
10
0

Year Published

2005
2005
2019
2019

Publication Types

Select...
6
1

Relationship

2
5

Authors

Journals

citations
Cited by 16 publications
(10 citation statements)
references
References 38 publications
0
10
0
Order By: Relevance
“…CASE technology encompasses a collection of automated tools and methods that assist software engineering in the phases of the software development life cycle [9]. Lundell and Lings [10] define CASE technology as an interoperable, computerised tool set designed to support stakeholder tasks and processes over the full information systems development lifecycle. CASE-tools are often based on the object-oriented approach to visual modelling of the unified modeling language (UML), content management systems and business process management systems [7].…”
Section: Context Analysismentioning
confidence: 99%
See 1 more Smart Citation
“…CASE technology encompasses a collection of automated tools and methods that assist software engineering in the phases of the software development life cycle [9]. Lundell and Lings [10] define CASE technology as an interoperable, computerised tool set designed to support stakeholder tasks and processes over the full information systems development lifecycle. CASE-tools are often based on the object-oriented approach to visual modelling of the unified modeling language (UML), content management systems and business process management systems [7].…”
Section: Context Analysismentioning
confidence: 99%
“…However, the adoption of CASE technology has been poor [10]. Troy and McQueen [15] developed a methodology for designing domain-specific CASE tools supporting model-based analysis and automatic code generation.…”
mentioning
confidence: 99%
“…Evaluative Baik et al (2002), Brown (1993), Budgen et al (1993), Budgen and Thomson (2003), Chen and Norman (1992), Damm et al (2000), Estublier et al (1992), Estublier and Garcia (2005), Flatscher (2002), Fuggetta (1996), Gautier et al (1995), Grundy et al (1998b), Grundy et al (1998a), Guo et al (2004), Harvey and Marlin (1996), Harvey and Marlin (1997), Jin et al (2002), Kienle (2001), Lundell and Lings (2004), Maguire et al (1999a), Maguire et al (1999b), Mens et al (2002), Michaels (1993), Rader et al (1993), Rover (1994), Sen (2004), Sim (2000), Sim and Koschke (2001), Singh (1993), St-Denis et al (2000), Stoeckle et al (2003), Urwiler et al (1995), Wuyts and Ducasse (2004), Yang et al (1993), Yang (1994), Yang (2000), Yang (2002), Yang and Han (1996), Zelkowitz and Cuthill (1997), Zelkowitz (1996) 40 Papers thelmess (2003). In contrast, Harrison et al (2000) have provided a thorough review of the area, describing the technical challenges that need to b...…”
Section: Descriptive Researchmentioning
confidence: 99%
“…Model interchange is important for two reasons. Firstly, it is widely acknowledged that systems outlive tools (see, for example, [2] [3]). Secondly, companies often use more than one tool in their development environments, as tools have different strength and weaknesses, perhaps at different stages in the tool chain.…”
Section: Introductionmentioning
confidence: 99%