Lyytinen, K.S., Rossi, M.: METAEDIT+ - a fully configurable multi user and multi tool CASE and CAME environment. Springer Verlag LGNS 1080 (1999)  Home/Search   Document Not in Database   Summary   Related Articles   Check

....that the tool will support. It specifies the things that can appear on a diagram, data model notation model function model generic tool specific tool parameterise the relationships between them and their appearance. That description can be textual (as in systems such as TBK[10] and MetaEdit [12]) but an interesting possibility is the use of a diagram to provide the description. By building a tool which supports this Metamodelling notation, and combining it with a suitable set of software components to provide the generic editing capabilities, the construction of diagramming tools can be ....

....of building diagrammers have been attempted. This sections reviews some of the most influential systems. 4. 1 Other MetaCASE systems MetaBuilder (described in section 5) is part of a tradition in MetaCASE which includes tools such as Ipsys TBK[10] Lincoln Software s Toolbuilder[11] MetaEdit[12], and KOGGE[4] The common approach to MetaCASE taken by these tools is characterised by the MetaCASE system consisting of one or more generic editors which are customised (into specific tools) by the addition of a tool description. The tool description contains a model of the underlying data ....

Kelly, S., Lyytinen, K., Rossi, M. (1996) MetaEdit+ A Fully Configurable MultiUser and Multi-Tool CASE and CAME Environment, Lecture Notes in Computer Science, Vol. 1080, pp. 1-21

.... MAS) opposite to most formalisms, can be detailed partially and refined through successive steps (similarly to UML, where class diagrams do not need to be complete from the beginning, but can grow in details during the development) Furthermore, the use of meta modeling tools, such as METAEDIT [5] in our experimentation, makes possible to perform analysis and design as in object oriented applications using Rational Rose or TogetherJ, but instead of using UML, with MAS specific notation. Though meta models help as a notation for the specification of a MAS, they are not yet the complete ....

Lyytinen, K. S. and Rossi, M. METAEDIT+ --- A Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment. LGNS#1080. 1999. Springer-Verlag.

.... referred to as meta CASE tools, tool builders or tool generators [42] These meta tools typically support the definition of tool data structures and views on tool data structures, provide input output specification techniques, and generate some or all of the code to implement the specified tool [30, 59, 37]. Many meta CASE tools have been developed, but there are a number of testing tool generators, programming environment tool generators and some very general purpose application generators applied to building software tools. Examples of tool building systems include the Synthesizer Generator [88] ....

....and co ordination of use of parts of software development methods. These often combine software process definition and software artifact repository management facilities with support for specifying analysis, design and testing tools. Examples of CAME tools include Decamerone [49] and MetaEDIT [59]. Software Tool Structure Some software tools are relatively simple programs or suites of programs that read input software artefact definitions (e.g. source code, design encodings or test plans) apply various operations to this input data, and generate an appropriate output structure (e.g. ....

[Article contains additional citation context not shown here]

Kelly, S., Lyytinen, K., and Rossi, M., Meta Edit+: A Fully configurable Multi-User and Multi-Tool CASE Environment, In Proceedings of CAiSE'96, Lecture Notes in Computer Science 1080, Springer-Verlag, Heraklion, Crete, Greece, May 1996, pp. 1-21.

....formalisms are Category Theory [11] in which formalisms are cast as categories and their relationships as functors. See also [24] and [18] for other approaches. 3 There are other visual tools to describe formalisms using meta modelling, among them DOME [6] Multigraph [22] MetaEdit [17] or KOGGE [8] Some of them allow to express formalism semantics by means of a textual language (KOGGE for example uses a language similar to Modula 2) Our approach is quite different, as we express such semantics by means of graph grammars. We believe that graph grammars are a natural, ....

Kelly, S., Lyytinen, K., Rossi, M. MetaEdit+: A fully configurable Multi-User and Multi-Tool CASE and CAME Environment In Constantopoulos, P., Mylopoulos, J., Vassiliou, Y: Advanced Information System Engineering; LNCS 1080. Berlin: Springer 1996. See MetaEdit+ Home page at: http://www.MetaCase.com/

.... the research group tried to describe a part of method chunks with SGML, and combined meta modeling with scenario based analysis for method engineers to support enhancing the existing methods[46] MetaEdit or MetaEdit is based on entity relationship model for meta modeling technique and meta CASE[35], and it has several tools for CAME. It also focuses on the usage of generated CASE tools for multi users. This direction, i.e. howto support group work in method engineering technology is one of the most significant ones for the application of CAME. MethodBase[54] was developed by Saeki, et. ....

S. Kelly, K. Lyytinen, and M. Rossi. MetaEdit+ : A Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment. In Lecture Notes in Computer Science (CAiSE'96),Vol. 1080, pp. 1--21, 1996.

....How to represent and classify components thereby becomes essential to create facilities that support component reuse. In this paper, we focus particularly on the strategies of component classification and search in a metaCASE repository, and take an industry strength environment, MetaEdit (Kelly, Lyytinen et al. 1996), as an example. Different search techniques have advanced for information retrieval. When proposing strategies to search component in a metaCASE environment, we must take into account unique demands of such an environment. These demands come from the distinct characteristics of the metaCASE ....

Kelly, S., K. Lyytinen, et al. (1996). MetaEdit+: a Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment. Advanced Information Systems Engineering, Proceedings of the 8th International Conference CAISE'96, Springer- Verlag.

....of a method. However, a metamodelling language may become complicated to use when different method aspects (concepts, notations, agents, tasks, decisions, goals etc. need to be supported widely. Metamodelling languages in metaCASE seem to be directed towards focused languages such as GOPRR (Kelly et al. 1996) and PSM (ter Hostedte and van der Weide, 1993) for techniques, or ELT (Boloix et al. 1991) for consistency rules and transformations, instead of wide and general ones such as MEL (Harmsen, 1997) Comparisons of metamodelling languages are presented in (Marttiin et al. 1993; Harmsen and Saeki, ....

....(Smolander et al. 1991) Graphical Designer by ASTI, and ObjectMaker by Mark V Systems. The use of modelling notations in a definition of a method i.e. metamodelling by example is a fascinating idea. Another issue is related to building methods from reusable components. As an example MetaEdit (Kelly et al. 1996) uses abstraction mechanisms such as aggregation (aggregation of concepts into a technique and techniques into a project) and specialisation (property inheritance) Such mechanisms make also method integration (composing techniques originated from different methods) easier. More discussion of ....

Kelly, S., Lyytinen, K. & Rossi, M. 1996. METAEDIT+ --- A Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment. In: P. Constantopoulos, J. Mylopoulos, Y. Vassiliou (Eds.) Advanced Information Systems Engineering (LGNS#1080), Berlin: Springer-Verlag, 1-21.

.... To get an overview of design rationale research in general, see the special journal numbers edited by Carroll and Moran (1991) or Borgida and Jarke (1992) Technical background MetaEdit is a fully configurable multiuser and multitool computer assisted systems and method engineering environment (Kelly et al. 1996). From the end user viewpoint, it is based on two levels of abstraction: the software engineering level, on which software descriptions are developed by a development group, and the method engineering level, on which methods are specified by a method engineering group. The MetaEdit software ....

Kelly S., Lyytinen K., & Rossi M. (1996) MetaEdit+: A Fully Configurable Multiuser and Multitool CASE Environment, Proceedings of the 8th Conference on Advanced Information Systems Engineering (CAiSE '96), Crete, Greece, May 20-24, 1996.

....is a CASE shell that allows SDMs to be customised or developed from scratch. Customisation includes the ability to define different representations for a single concept, e.g. a different shape for each diagram type by which the concept can be represented. A later version of MetaEdit, MetaEdit (Kelly 1996), supports three representation paradigms : graphical diagrams, matrices (Kelly 1994) and tables. But different notations or different paradigms are still representing the same abstractions, albeit in different ways; SDM independence is in representational terms only. As it is unlikely that the ....

....involved in a development project, integration should allow knowledge to be independent of a particular set of abstractions. TIM: A Prototype Tool for Integrating System Development Methods The issue of integrating SDMs which use different modelling abstractions is partially addressed in (Kelly 1996), which describes how MetaEdit allows properties to be shared by abstractions of different SDMs. Property sharing is a powerful mechanism, e.g. it allows the attributes belonging to a class in an OOpopulated model to be shared with an entity type in a structured populated model. This mechanism ....

[Article contains additional citation context not shown here]

Kelly S., Lyytinen K., Rossi M. (1996). MetaEdit+ A Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment. Proceedings, Eighth International Conference CAiSE 1996. Lecture Notes in Computer Science 996.

....The first type offers a predefined set of supported notations which can be used. System like this are e.g. Toolframe [DK95] and Paradigm [P94] Generators of CASE tools fit into the second category. They offer the possibility to produce completely new CASE tools. Metaview [Fi94] and MetaEdit [KLR96] are examples of this approach. In Koblenz, the meta CASE system KOGGE [EC94] Me94] KOblenz Generator for Graphical design Environments) has been developed to generate CASE tools which support visual languages and methods. Main objectives are adaptability and flexibility based on a declarative ....

Kelly, S.; Lyytinen, K.; Rossi, M.; MetaEdit+: A Fully Configurable MultiUser and Multi-Tool CASE and CAME Environment. In: Constantopoulos, P.; Mylopoulos, J.; Vassiliou, Y. [Eds.]; Advanced Information System Engineering, LNCS 1080. Berlin: Springer, 1996.

....use of components in Section 2.3. CASE The demands emerging from the use of the Internet as well as the use of components have strong influence on the production and use of CASE and meta CASE tools. Traditional meta CASE tools and the CASE tools, which are built by them (e.g. ESU96] DK95] [KLR96], JJQ98] are more or less large monolithic systems. These systems follow a client server approach but their focus is on processing local documents. The user interface is also a traditional one. But with the Internet in mind the requirements of the users lead to CASE tools which act and look ....

Kelly, S.; Lyytinen, K.; Rossi, M.; MetaEdit+: A Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment. In: Constantopoulos, P.; Mylopoulos, J.; Vassiliou, Y. [Eds.]; Advanced Information System Engineering, Lecture Notes in Computer Science, 1080. Berlin: Springer, 1996.

....1995) Another issue is how to provide links into different types of representation forms used in CASE. Previous research into hypertext functionality has not addressed other representation forms than diagrams, although matrices and tables are also considered as necessary in systems design (Kelly, Lyytinen et al. 1996)) In this paper we outline the role of hypertext functionality in CASE and discuss the issues concerning its actual use i.e. linking and navigation. The paper is structured as follows. First, the ISD process and general hypertext technology is reviewed after which the role hypertext technology as ....

Kelly, S., K. Lyytinen, et al. (1996). MetaEdit+: A fully configurable multi-user and multi-tool CASE and CAME environment. Advanced Information Systems Engineering, proceedings of the 8th International Conference CAISE'96. P.

....like to distinguish checked entities from nonchecked ones. This calls for the definition of special symbols for checked entities. 3 Support for Adaptability We now present two adaptable environments that provide partial solutions to the adaptability problems presented in section 2. MetaEdit [11] is a notation and ontology oriented metaCASE tool, which provides tools for specifying an ontology and a related notation and generating automatically (on the fly) a set of modeling tools to support the method. PRIME 1 [18] focuses on process driven metamodeling. It allows to specify processes, ....

....side, MetaEdit provides metamodeling tools for defining concepts and associated notations, which can be graphical, matrix and tabular ones. The metamodeling tools have been applied to model tens of methods in terms of their ontology and notation. An ontology is defined by using the GOPRR [11] (Graph, Object, Property, Role and Relationship 2 ) metamodeling formalism (see Fig. 2) Graph specifies a technique (graph type) Object, Role and Relationship specify elements of a graph type and Property specifies property types to describe these elements as well as graph types. The ....

Kelly, S., Lyytinen, K. and Rossi, M. (1996) METAEDIT+ --- A Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment. In: Advanced Information Systems Engineering, LNCS#1080, Springer, pp. 1-21.

No context found.

Lyytinen, K.S., Rossi, M.: METAEDIT+ - a fully configurable multi user and multi tool CASE and CAME environment. Springer Verlag LGNS 1080 (1999)

No context found.

S. Kelly, K. Lyytinen, and M. Ross. MetaEdit+: A fully configurable multiuser and multi-tool CASE and CAME environment. In P. Constantopoulos, J. Mylopoulos, and Y. Vassiliou, editors, Proc. of the 8th Intl. Conf. an Advanced Information Systems Engineering (CAiSE'96), pages 1-21, Heraklion, Creta, Griechenland, May 1996. Springer-Verlag, LNCS 1080.

No context found.

S. Kelly, K. Lyytinen, and M. Rossi. MetaEdit+: A fully configurable multi--user and multi--tool CASE and CAME environment. In P. Constantopoulos, J. Mylopoulos, and Y. Vassiliou, editors, Advanced Information Systems Engineering, CAISE'96, volume 1080 of Lecture Notes in Computer Science, pages 1--21. Springer, 1996.

No context found.

Kelly, S., Lyytinen, K., Rossi, M.: MetaEdit+ -- a fully configurable multi-user and multi-tool CASE and CAME environment. Proc. CAiSE 96, Heraklion, Greece, 1996, 1-21.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC