Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Ful
DOI: 10.1109/hicss.1999.772814
|View full text |Cite
|
Sign up to set email alerts
|

Building an evaluation instrument for OO CASE tool assessment for Unified Modelling Language support

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
5
0

Publication Types

Select...
2
2
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(5 citation statements)
references
References 16 publications
0
5
0
Order By: Relevance
“…For a comprehensive and upto-date overview on currently available UML tools, please refer to M. Jeckle's Web site 1 . Juric and Kuljis [6] present evaluation criteria to assess the extent to which CASE tools support the range of UML language features. A general introduction to software development tools is given in [4]-it puts UML tools in the wider context of the software development environment.…”
Section: Design Considerations For Uml Tool Supportmentioning
confidence: 99%
See 1 more Smart Citation
“…For a comprehensive and upto-date overview on currently available UML tools, please refer to M. Jeckle's Web site 1 . Juric and Kuljis [6] present evaluation criteria to assess the extent to which CASE tools support the range of UML language features. A general introduction to software development tools is given in [4]-it puts UML tools in the wider context of the software development environment.…”
Section: Design Considerations For Uml Tool Supportmentioning
confidence: 99%
“…Batik is a toolset to handle scalable vector graphics (xml.apache.org/batik) 6. FOP (formatting objects processor) is a framework to support output independent formatting (xml.apache.org/fop).…”
mentioning
confidence: 99%
“…We have observed that methods proposed for pre‐usage evaluation 1 are primarily CASE tool centred (Zucconi, 1989; Sodi, 1991; Topper, 1991; Dixon, 1992; IEEE, 1992; 1998; Le Blanc & Korn, 1992; 1994; Mosley, 1992; Huff et al ., 1992; Skramstad & Khan, 1992; Beckworth, 1993; du Plessis, 1993; Shafer & Shafer, 1993; Bell, 1994; Antonakopoulos et al ., 1995; ISO, 1995; Jankowski, 1995; 1997; Daneva & Terzieva, 1996; Daneva, 1997; Kitchenham & Jones, 1997a,b; 2 Powell et al ., 1997; Juric & Kuljis, 1999). They are systematic , in that they embody a systematic way of working during an evaluation.…”
Section: Related Workmentioning
confidence: 99%
“…For example, there are those designed for analysis of: support for customisability of a CASE tool (Goldkuhl et al ., 1992); CASE‐tool support for planning and design activities (Henderson & Cooprider, 1990); support for structured systems analysis and design techniques (Vessey et al ., 1992); hypertext functionality in CASE tools (Kaipala, 1997); reverse engineering tools (Skramstad & Khan, 1992); data modelling tools (Moriarty, 1998); database design tools (Reiner, 1992); testing tools (Poston & Sexton, 1992); software engineering environments (Palvia, 1992); collaborative work (Vessey & Sravanapudi, 1995); conformance to a specific modelling notation (e.g. UML –Juric & Kuljis, 1999); conformance to method rules in structured analysis (Jankowski, 1997); usability of CASE tools (Cronholm, 1998); and quality assurance of ER Models (Barker, 1990, chapter 10).…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation