I. Thomas. Pcte interfaces: Supporting tools in software engineering environments. IEEE Software, November 1989.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....support for precisely capturing the evolution of the artifacts it manages. This simple idea fostered a number of contributions of dedicated data and system models for SCM, models in which everything is versioned, including files, attributes, general relationships, configurations, and workspaces [Est85, Dit87, Bou88, Tho89, Gul91, Est94]. Commercial SCM systems improved their data model, but are still far from these research attempts for two reasons. First, no commercial database exists that can support these kinds of advanced models, and building such a database, either from scratch or on top of a commercial relational ....

Ian Thomas. PCTE interfaces: Supporting tools in software-engineering environments. IEEE Software, 6(6):15-23, November 1989.

....processing to generate dynamic content. While many web site analysis tools [14, 8] are available to analyze the structure of static HTML content, most of them completely ignore the applet code, which by its nature requires software analysis techniques. Traditional software repositories [29, 30, 7, 13, 3] apply reverse engineering [12] techniques on the source code to build a central information source for maintaining code in a software system. Repositories are useful to developers as they make it possible to efficiently examine the structure and interaction between components of a system without ....

I. Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software, 6(6):15--23, Nov. 1989. 12

.... Language based environments were a popular research topic [39,66] Later, the efforts around APSEs environments supporting Ada program developments gave new impetus and more generality to this field of research [73] PCTE was probably the richest and latest result of this research stream [72]. A similar trend could be observed in the business information systems field. Fourthgeneration languages and environments, which became popular in the 80s, are based on the assumption that several software development tasks can be automated by a suitable SDE. Report generation and input forms ....

I. Thomas, "PCTE Interfaces: Supporting Tools in Software Engineering Environments, IEEE Software, 6(6), November 1989.

....components, as well as individual tools. It is still unclear, however, how one can and should integrate SDE components (as opposed to tools) together to produce a coherent, useful, and usable system. Previous work on componentized SDEs, such as various systems constructed on top of PCTE [23], has generally adopted ad hoc solutions suitable for their particular integrated system rather than introducing a general architecture for a class of component integrations. We do not attempt to address the entirety of this very large problem here: this paper is concerned primarily with ....

Ian Thomas. PCTE interfaces: Supporting tools in software-engineering environments. IEEE Software, 6(6):15--23, November 1989.

....changes can often be implemented in a straightforward, repetitive manner, but nevertheless the source code must be available perhaps an insurmountable difficulty when integrating COTS tools from independent vendors. The White Box approach is followed by several commercial message buses. PCTE[19] and similar standards probably require more effort in tool adaptation, but enable a higher scale of integration. ffl Grey Box, where the source code is not modified but the tool provides its own extension language or application programming interface (API) in which functions can be written to ....

Ian Thomas. PCTE interfaces: Supporting tools in software-engineering environments. IEEE Software, 6(6):15--23, November 1989.

....This implies that the modelling of an IS must be treated as an engineering discipline with a proper semantic foundations. Recently, various approaches to formalise methods for systems were suggested. Well known are the so called meta models, originating in the context of tool integration (e.g. [9, 28, 30]) Within manufacturing systems, 1, 23] proposed a technique that avoids a Babel Tower to rise, where the different people at each stage of the design and operation can seldom communicate. For this they suggested the use of Petri net [21] In addition, the RAISE method [24, 25] was used to model ....

THOMAS, I., PCTE interfaces: Supporting tools in software engineering environments. IEEE Software, pp. 15-23, 1998.

....client side processing to generate dynamic content. While many web site analysis tools are available to analyze the structure of static HTML content, most of them completely ignore the applet code, which by its nature requires software analysis techniques. Traditional software repositories [2, 19, 20, 7, 11, 4] apply reverse engineering[10] techniques on the source code to build a central information source for maintaining code in a software system. Repositories are useful to developers as they make it possible to e#ciently examine the structure and interaction between components of a system without ....

I. Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software,

....CM repository. The next question is, what is an appropriate way to realize the model and interface There are some obvious candidates, including a distributed le system (e.g. Jade [19] or Prospero [16] a distributed database [20] or an advanced operating system environment (e.g. PCTE [23]) One could even consider building something from scratch. Our approach was to experiment with a rather di erent alternative, namely the CORBA standard for distributed object programming [7] using the Orbeline CORBA engine [18] The resulting architecture of our implementation of NUCM is shown ....

I. Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software, pages 15-23, November 1989.

....oriented data repository has been employed quite widely, for example also by several of the projects aimed to define standards for building generic tools with a high degree of portability and interoperability, and therefore widely reusable, even if only under the standard s specifications. PCTE [50] [17] is probably the most representative and generally accepted example of such standards. The goal of PCTE is to create a set of services and facilities, called a public tool interface, complete enough to support tool writers in very different situations and domains; many SDE prototypes and ....

Ian Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software, 6(6):15--23, November 1989.

....of tools is mostly purely restricted to document editing and managing functions. Recently, various approaches for formalizing methods of systems and software development were given. Well known are the so called meta models , originating in the context of tool integration, see [CDI92] Tho89] and [HL93] However, by this models almost only the abstract syntax of the description techniques is captured. An overview of several projects concerning the integration of structured methods with techniques of formal specification can be found in [SFD92] In [Hus94] the British standard ....

I. Thomas. PCTE interfaces: Supporting tools in softwareengineering environments. IEEE Software, pages 15--23, November 1989. 42

....The views and conclusions contained in this document are those of the authors and should not be interpreted as representing the official policies, either expressed or implied, of the US or NYS governments, ARPA, Air Force, NSF, NYSSTF, AT T, Bull, IBM or Xerox. 2 Polylith software bus [51] PCTE [62] and similar framework standards probably require more effort in tool adaptation, or a priori adherence to the standard by vendors, but enable a higher scale of integration. The CORBA interoperability standard [45] is not specifically directed to environment frameworks, and seems best suited to ....

Ian Thomas. PCTE interfaces: Supporting tools in software-engineering environments. IEEE Software, 6(6):15--23, November 1989.

....a straightforward, repetitive manner, but nevertheless the source code must be available perhaps an insurmountable difficulty when integrating COTS tools from independent vendors. The White Box approach is followed by several commercial message buses, most based ultimately on Field [19] PCTE [22] and similar framework standards probably require more effort in tool adaptation, but enable a higher scale of integration. ffl Grey Box, where the source code is not modified but the tool provides its own extension language or application programming interface (API) to interact with the ....

Ian Thomas. PCTE interfaces: Supporting tools in software-engineering environments. IEEE Software, 6(6):15--23, November 1989.

....frameworks. User interface services for example are used for presentation integration, task management services and message services are used for control integration and data repository and data integration services focus on data integration. The project Portable Common Tool Environment (PCTE) [Tho89] for example was aimed to implement the reference model and to produce a public tool interface to be used as a portability interface and to provide support for the integration of software engineering tools. Additionally, Sharon and Bell [SB95] give a nice overview about commercial SEE frameworks ....

Thomas, I.: "PCTE Interfaces: Supporting Tools in SoftwareEngineering Environments", IEEE Software, November 1989, pp. 15--23

....example also shows that a rigid tool support is inevitable for larger example. 5 RELATED WORK Recently, various approaches for formalizing methods of systems and software development were given. Well known are the so called meta models , originating in the context of tool integration, see [T89] and [HL93] However, by this models almost only the abstract syntax of the description techniques is captured. An overview of several projects concerning the integration of struc 280 Chapter 16 tured methods with techniques of formal specification can be found in [SFD92] In [H94] the ....

I. Thomas. PCTE interfaces: Supporting tools in software-engineering environments. IEEE Software, pages 15--23, November 1989.

....the possibility that the very structure of the archive will evolve over time. Instructors may alter the way they choose to organize their materials, or may move to new host technologies for course delivery, e.g. moving from native files and directories to a course management package such as WebCT [22]. In this paper we concentrate on one aspect of UDLF: the representation of course objects and tools necessary to manipulate them. The reference implementation of UDLF builds on NCSTRL [19] which is based upon digital objects called buckets. Buckets are programmable objects that can aggregate ....

.... It is, however, reminiscent of the similar evolution undergone in the transition from conventional to object oriented data bases (OODBs) from supporting tuples of simple data to supporting rich abstract data types [3] and in the design of large software engineering repositories (SERs) [21,22]. The predominant approach taken in these other public Instructor TA Instructor only private 1sr,then public Instructor s Model CS 451 Figure 1. A course structure Spring 97 description files files solution files grade Student1 Student2. Subm issions compile script inputs ....

I. Thomas, "PCTE Interfaces: Supporting Tools in Software-Engineering Environments," IEEE Software, 6(6), 1989, pp. 15-23.

....client side processing to generate dynamic content. While many web site analysis tools[13] 8] are available to analyze the structure of static HTML content, most of them completely ignore the applet code, which by its nature requires software analysis techniques. Traditional software repositories [27, 28, 7, 12, 3] apply reverse engineering[11] techniques on the source code to build a central information source for maintaining code in a software system. Repositories are useful to developers as they make it possible to efficiently examine the structure and interaction between components of a system without ....

I. Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software, 6(6):15--23, Nov. 1989.

....be more indicative of its framework architecture. The basic approach to this mapping is given by Figure 1. The grid represents the set of services in 1 For example, the original TGRM framework model grew out of the ECMA development of the PCTE (A Portable Common Tool Environment) specification [7]. 2 Well, almost strict. B B B B B B B B B B B B B B B BB B B B B B B B B B B B B B B BB B B B B B B B B B B B B B B BN ffl ffl A A A A A A A A A A A Delta Delta Delta Delta Delta Delta Delta Delta Delta Delta Delta Theta Theta ....

Thomas I., PCTE Interfaces: Supporting Tools in Software Engineering Environments, IEEE Software 6(6):15-23 (1989).

....must be available perhaps an insurmountable difficulty when integrating off the shelf tools from independent vendors. The White Box approach is followed by several commercial message buses, most based on either the Field broadcast message server [29] or the Polylith software bus [28] PCTE [34] and similar framework standards probably require more effort in tool adaptation, or a priori adherence to the standard by vendors, but enable a higher scale of integration. The CORBA interoperability standard [24] is not specifically directed to environment frameworks, and seems best suited to ....

Ian Thomas. PCTE interfaces: Supporting tools in software-engineering environments. IEEE Software, 6(6):15--23, November 1989.

....to illustrate how our model also supports variants of reachability analysis: impact analysis, class visibility analysis, and dead code detection. Finally, we discuss the implementation and experience of our analysis tools on a C software project. 1 INTRODUCTION There has been a growing trend [25][1] 24] in building software repositories to help maintain structure information of existing legacy code. A software repository provides a central information source for understanding and reengineering code in a software project. While many variants of repository based systems have been ....

I. Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software, 6(6):15--23, Nov. 1989.

....data base or persistent object base as one of the important features distinguishing an Integrated Project Support Environment (IPSE) from a collection of ad hoc tools. The need for a uniform, homogeneous object storage facility is also identified by the Portable Common Tools Environment (PCTE) [16] and the Ada Apse designers [14] Programming languages normally have little support for the maintenance of long term data. The only concession usually made is the provision of a file data type. Therefore, the programmer is faced with the task of mapping data onto long term storage which is ....

Thomas, I. "PCTE Interfaces: Supporting Tools in Software-Engineering Environments", IEEE Software, pp. 15-23, 1989.

....Control services (9.3 and 9.4) The use of DDL for data exchange relates to the Data Interchange service. Note that data about other services (e.g. processes, rules, or tools) is not necessarily metadata. 4.1. 8 Examples Examples of data models from real systems include the node model of PCTE [85] [35] and CAIS A [30] the E R model of Aspect [44] 32] 12] the class hierarchy of ATIS [26] and elements of the following models and systems: Damokles [28] the relational model [19] Taxis [63] SDM( 78] and Iris [40] Examples of Metadata services are: data dictionaries, schema ....

Thomas I. PCTE Interfaces: Supporting Tools in Software Engineering Environments, IEEE Software, 6(6):15-23, November 1989.

....coordinate their operations. Here, the message server and the interfaces constitute the subsystem in charge of tool integration. This component is often referred to as a message bus. Such an approach is used, among others, by Field [22] Conversation Builder [17] 7] and SoftBench [6] 13] PCTE [27] [11] is one of the most representative examples of efforts directed to define a widely recognized and accepted public standard for building tools with better portability. The aim is to create a set of services and facilities, called a public tool interface, complete enough to support tool writers ....

Ian Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software, 6(6):15--23, November 1989.

....type Sctx) and their executions (at runtime) are managed as PCTE client processes. These processes are not stored objects because they are purely dynamic. PCTE provides facilities that are similar to Unix to manage the start, stop, suspension, communication and synchronization of PCTE processes [15]. On the other hand, Unix tools that are interfaced to a PCTE environment need to be linked with the PCTE Unix libraries, and their executions (which are standard Unix processes) are alien processes to PCTE. In our case study, we modified Oz and linked it with the PCTE libraries instead of ....

Ian Thomas. PCTE interfaces: Supporting tools in softwareengineering environments. IEEE Software, 6(6):15--23, November 1989.

....the logical repository. 5. 2 NUCM Implementation To implement NUCM according to the architecture of Figure 6, some obvious candidates exist, including a distributed file system (e.g. Jade [39] or Prospero [35] a distributed database [41] or an advanced operating system environment (e.g. PCTE [46]) Our initial approach was to experiment with a rather di#erent alternative, namely the CORBA standard for distributed object programming [12] For a variety of reasons, we implemented NUCM twice, first with the Orbeline CORBA engine [38] and subsequently with a CORBA implementation called Q ....

I. Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software, pages 15--23, November 1989.

....the application often outlives its individual components and even its implementation technology. Typical examples of such PASs are: CAD CAM systems, office automation, CASE tools, software engineering environments [Teitelbaum Reps, 1981, Akima Ooi, 1989, Bott, 1989, Sommerville et al. 1989, Thomas, 1989], integrated hospital administration and medical systems, large scientific databases and programs that analyse them, geographic information systems, environmental modelling systems, object oriented databases [Bancilhon et al. 1988, Bretl et al. 1989] and process modelling systems [Bruynooghe et ....

Thomas, I., 1989. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software pp 15-23.

....functionality of tools is mostly restricted to document editing and managing functions. Recently, various approaches for formalizing methods of systems and software development were given. Well known are the so called meta models , originating in the context of tool integration, see [CDI92] Tho89] and [HL93] However, by this models almost only the abstract syntax of the description techniques is captured. An overview of several projects concerning the integration of structured methods with techniques of formal specification can be found in [SFD92] In [Hus94] the British standard ....

I. Thomas. PCTE interfaces: Supporting tools in softwareengineering environments. IEEE Software, pages 15--23, November 1989.

....we discuss the implementation and experience of our analysis tools on a C software project. Keywords reachability analysis, dead code detection, software maintenance, reverse engineering, software visualization, software repository, data model. INTRODUCTION There has been a growing trend [25][1] 24] in building software repositories to help maintain structure information of existing legacy code. A software repository provides a central information source for understanding and reengineering code in a software project. While many variants of repository based systems have been ....

I. Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software, 6(6):15--23, Nov. 1989.

....inheritance. The node model is used to formalize the structures and capabilities of the OMS. Processes in CAIS A form a tree of parentchild processes. All process information is kept in the OMS. Processes can communicate through special OMS based queues. The Portable Common Tool Environment (PCTE) [89] is a Public Tool Interface (PTI) which can be used as a basis for integrating tools as part of the development of an SPE. The PCTE PTI consists of software interfaces to services of an OMS, LCPMS, and UIMS. The Object Management System is a distributed database based on an ERA model with multiple ....

I. Thomas. PCTE interfaces: supporting tools in software engineering environments. IEEE Software, 6(11):15--23, November 1989.

....CM repository. The next question is, what is an appropriate way to realize the model and interface There are some obvious candidates, including a distributed file system (e.g. Jade [19] or Prospero [16] a distributed database [20] or an advanced operating system environment (e.g. PCTE [23]) One could even consider building something from scratch. Our approach was to experiment with a rather different alternative, namely the CORBA standard for distributed object programming [7] using the Orbeline CORBA engine [18] The resulting architecture of our implementation of NUCM is shown ....

I. Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software, pages 15--23, November 1989.

....perform client side processing to generate dynamic content. While many web site analysis tools are available to analyze the structure of static HTML content, most of them completely ignore the applet code, which by its nature requires software analysis techniques. Traditional software repositories [2, 19, 20, 7, 11, 4] apply reverse engineering[10] techniques on the source code to build a central information source for maintaining code in a software system. Repositories are useful to developers as they make it possible to efficiently examine the structure and interaction between components of a system without ....

I. Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software,

.... of strategies: developing a new standard tool for building common user interfaces, such as X windows; standardizing on a small number of languages, such as Ada [1] Common Lisp [75] or C , for all projects; establishing a uniform development environment such as UNIX, CAIS [48] or PCTE [80] for all projects; and . establishing a common methodology or set of standards to be used on all its projects. It is easy to understand the rationale behind these decisions: reduction in cost and improvement in productivity. If there is a uniform environment used by several projects, programmers ....

Ian Thomas. "PCTE Interfaces: Supporting Tools in Software-Engineering Environments," IEEE Software, 6:6 (November 1989). pp 15-23.

....the implementation and experience of our analysis tools on a few C software projects. Keywords C , Conceptual Modeling, Dead Code Detection, Program Database, Software Repository, Reachablity Analysis, Reverse Engineering, Static Analysis. I. INTRODUCTION There has been a growing trend [27][1] 26] in building software repositories to help maintain structure information of existing legacy code. A software repository provides a central information source for understanding and reengineering code in a software project. While many variants of repository based systems have been ....

I. Thomas. PCTE Interfaces: Supporting Tools in SoftwareEngineering Environments. IEEE Software, 6(6):15--23, Nov. 1989.

.... of independently developed, pre existing components, in contrast to work on (1) construction of systems based on one (or a small number of) pre existing components, with the rest of the system implemented mostly from scratch to take advantage of these components (the approach taken for PCTE [19] and many systems in other domains, such as Mach [9] Camelot [8] and database applications) or (2) building block kits, where sets of components that can be mixed and matched are designed and implemented together (e.g. Genesis and Avoca [3] The most significant difference compared to the ....

Ian Thomas. PCTE interfaces: Supporting tools in software-engineering environments. IEEE Software, 6(6):15--23, November 1989.

.... ProcessWEAVER processcentered environment framework [8] and University of Wisconsin s Exodus database management system [7] and replacing portions of Oz with externally developed components (notably the object management system from GIE Emeraude s PCTE industry standard environment framework [18]) these experiments are discussed in [11, 16, 12, 15] The OzMarvel data schema structures the objectbase into two main parts. One part consists of a set of teams, each consisting in turn of a group of private programmer workspaces. We used only two teams, representing current and past project ....

Ian Thomas. PCTE interfaces: Supporting tools in software-engineering environments. IEEE Software, 6(6):15--23, November 1989.

....to examine program structure differences. It also discusses how the information can be linked to modification request (MR) databases to establish connections between MRs and program entities. Integrating software tools with an underlying repository has been recognized as a promising approach[30][31]. However, there has been a lack of experience reports on applying repository based reverse engineering tools to large legacy code, where the tools are needed most. Section 5 describes our experience in applying ciao to several software projects. Some of these projects involve millions of lines of ....

Ian Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software, 6(6):15--23, November 1989.

....seems to be widely recognized. For instance, various proposals for architectures for object oriented database systems acknowledge the need for name management services, though only a few details are provided [OMG92] WBT92] Similarly, emerging standards for interfaces to software object bases [Tho89] and reference architectures for software engineering environments [ECM91] also allude to name management services as necessary components while offering few specifics. Thus the prospects for future developments in the area of name management and object technology for advanced software seem quite ....

Ian Thomas. PCTE interfaces: Supporting tools in software-engineering environments. IEEE Software, 6:15--23, November 1989.

....as objects (of type Sctx) and their executions are managed as PCTE client processes. These processes are not objects because they are purely dynamic. PCTE provides facilities that are similar to Unix to manage the start, stop, suspension, communication and synchronization of PCTE processes [14]. Unix tools that are interfaced to a PCTE environment need to be linked with the PCTE Unix libraries and their executions (standard Unix processes) are alien processes to PCTE. Within an Emeraude PCTE environment, there is one object server process for each host that has objectbase volumes (a ....

Ian Thomas. PCTE interfaces: Supporting tools in software-engineering environments. IEEE Software, 6(6):15--23, November 1989.

No context found.

I. Thomas. Pcte interfaces: Supporting tools in software engineering environments. IEEE Software, November 1989.

No context found.

Ian Thomas. PCTE Interfaces: Supporting Tools in Software-Engineering Environments. IEEE Software 6(6):15-23, November, 1989.

No context found.

Ian Thomas, 1989. "PCTE Interfaces: Supporting Tools in Software-Engineering Environments, " IEEE Software, November 1989, pp. 15-23.

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