| dc.contributor.author | Kelly, Steven | |
| dc.contributor.author | Rossi, Matti | |
| dc.contributor.author | Tolvanen, Juha-Pekka | |
| dc.date.accessioned | 2017-08-28T18:52:48Z | |
| dc.date.available | 2017-08-28T18:52:48Z | |
| dc.date.issued | 2005 | |
| dc.identifier.issn | 1866-3621 | |
| dc.identifier.uri | http://dl.gi.de/handle/123456789/3475 | |
| dc.description.abstract | In this paper we look at ways of effectively implementing software development environments through metaCASE tools. MetaCASE tools offer fast and economical means of supporting tailored or homegrown systems development methods, yet they have not been taken into use widely due to their perceived complexity and the lack of development process maturity in most organisations. We offer a list of generic requirements for these tools and demonstrate their use through evaluating the MetaEdit+ tool against these requirements. The requirements are gathered from existing literature on method engineering. | en |
| dc.language.iso | en | |
| dc.publisher | Gesellschaft für Informatik e.V. | |
| dc.relation.ispartof | Enterprise Modelling and Information Systems Architectures - An International Journal: Vol. 1, Nr. 1 | |
| dc.title | What is Needed in a MetaCASE Environment? | en |
| dc.type | Text/Journal Article | |
| dc.pubPlace | Berlin | |
| mci.reference.pages | 25-35 | |
| dc.identifier.doi | 10.18417/emisa.1.1.3 | |
