Reference Model for Frameworks of Software Engineering Environments (SEE)
Describes SEEs and assists the SEE architectural standardization process. Covers a set of services needed to describe environment frameworks. The particular services of the model are described to a degree that is complete enough for the model to be used to describe existing systems and proposals. Also adopted by the European Computer Manufacturers Assoc.
What people are saying - Write a review
We haven't found any reviews in the usual places.
Access Control application clause Communication Service composite objects Conceptual Concurrency Service create data model Data Storage Service Data Transaction Service database deﬁned delete Derivation Service descriptions Discretionary discussed ECMA enacting process environment framework Examples facilities ﬁle framework administration framework services future edition identiﬁed implementation instantiation integration interact Internal Location Service mandatory conformity mechanisms Metadata Service metrics modiﬁcation Monitoring and Triggering NIST notiﬁcation object management services operating system PCTE Policy Enforcement process architectures process control services process deﬁnition services process elements process enactment services process management services process programming language process state services process transaction proﬁle publication Query Service reference model Related Services Relationship Service Remote Procedure Call Rules schema Seeheim semantics Service This service software development Software Engineering Environment speciﬁc standards Sub-Environment Service surrogate TCSEC Tool Registration Service trusted computer base typically update user interface Version Service visibility and scoping X Window System
Page iii - Certain commercial equipment, instruments, or materials are identified in this paper in order to adequately specify the experimental procedure. Such identification does not imply recommendation or endorsement by the National Institute of Standards and Technology, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose.
Page 4 - ... model needs to recognise that a CASEE should support the development of a whole system. Systems are now being built which do not distinguish between the parts which are implemented via hardware and those via software. Secondly, the reference model should not be unduly influenced by existing CASEEs. There is very little experience of their application to real projects and thus there is no hard evidence that their designs are the most appropriate. However, existing products and the results of research...
Page 10 - We consider the subject of user interfaces to be an extremely complex issues which is far more general than integration frameworks. Nevertheless, a consistent user interface service may be adopted for a complete framework.
Page 13 - ... we think are the most interesting and important points. A full description of a system according to this reference model should check every aspect of each service in order to ensure completeness. Each point made in a service description rests at a point in the multi-dimensional space defined by our dimensions. The dimensions should be used at each level they are felt to be appropriate. For example, if the external dimension of a high-level service reveals that the service is being implemented...
Page 23 - surrogate' very neatly captures what is intended - every entity of the outside world is associated with a surrogate which stands for that object in the model.
Page 3 - ... found within a single organisation. Standards provide a way for environment users to buy facilities which meet their requirements from vendors who are not directly cooperating and may even be competitors. The reference model has to be able to be used to describe a wide range of CASEE designs, but must balance this against a requirement to be able to define points at which useful standards can be defined.
Page 14 - In addition to fully integrated tools that extensively use an environment framework's services, the tool slots in an environment framework may also provide an encapsulation service. This service is used when a tool exists (but was not written to make use of any of a particular environment framework's services) and is made to work in the environment framework by surrounding the tool with software that acts as a layer between the tool and the framework. The encapsulated tool fits into the framework...
Page iii - CASE environment frameworks. The particular services of the model are described to a degree of detail that is complete enough for the model to be used to describe existing systems and proposals.
Page 2 - ... the correct scope for addressing issues concerned with building environments. The area of software development environments is very young, even within the context of the youth of computer science. It is still developing some of its most basic premises and terminology. Much development effort can be wasted through misunderstandings and misinterpretations when different groups meet to discuss problems and potential solutions or new approaches to problems. The aim of the reference model is not to...
Page iii - SEE frameworks to assist the standardization process. A Task Group (TC33/TGRM) was formed in 1988 to develop a complete reference model. During 1989 the first full version of the reference model was created, and during 1990 the model was evaluated by using it to describe a number of SEE frameworks.