G. E. Kaiser, P. H. Feiller and S. Popovich, "Intelligent assistance for software development and maintenance". IEEE Software, 5(3), 1988.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....flowchart like diagrams. The software process modeling community started its work by developing a set of PMLs and associated supporting tools. The first generation software process modeling research projects defined PMLs with the goal of supporting process enactment and then partial automation [13]. Later, researchers concentrated their efforts into two main directions. The first research direction is the development of more high level PMLs, which address the managerial goals of elicitation and assessment. The second one deals with validating existing PMLs for the purpose of modeling in ....

G. E. Kaiser, P. H. Feiler, and S. S. Popovich, "Intelligent assistance for software development and maintenance," IEEE Software, vol. 5, pp. 40-49, 1988.

....learning as well as the actual basis for the coordination and the management of the software engineering activities. Software process modeling and enactment is one of the main areas in software engineering research. Several frameworks have been developed (e.g. procedural [11] rule based [10, 12], Petri net based [2] object oriented [5] Process modeling and enactment approaches usually are used to rigorously define heavy weight processes. They are weak concerning light weight approaches like XP and do not directly support key XP practices. They also are not good at providing a good ....

Kaiser, G. E., Feiler, P. H., and Popovich, S. S. (1988). Intelligent Assistance for Software Development and Maintenance, IEEE Software.

....Darryl Gates Sebastien Martel paired up for a couple of hours over the Internet while developing MILOS source code. Software process modeling and enactment is one of the main areas in software engineering research. Several frameworks have been developed (e.g. procedural [17] rulebased [11][18] Petri net based [2] object oriented [5] Process modeling and enactment approaches usually are used to rigorously define heavy weight processes. They are weak concerning light weight approaches like XP and do not directly support key XP practices. They also are not good at providing a ....

Kaiser, G. E., Feiler, P. H., and Popovich, S. S. (1988). Intelligent Assistance for Software Development and Maintenance, IEEE Software.

....engineering en vironments such as Process Weaver [9] or SPADE [1] are based on populated copies, i.e. a template of a Petri net is copied, populated with tokens, and enacted. This implies that the net structure is already determined at modeling time. Rule based systems such as e.g. Marvel [14] or MERLIN [22] are more flexible in that respect. Such systems may dynamically generate plans from facts and rules, e.g. for compiling and linking program modules. While plans are maintained automatically and are normally hidden from the users, task nets are manipulated by the project manager. ....

G. E. Kaiser, P. H. Feiler, and S. Popovich. Intelligent assistance for software development and maintenance. IEEE Software, 5(3):40-49, May 1988.

....and encapsulation of existing tools such as the static analyzer mentioned earlier. 6.3 Process Integration We are investigating various process modeling and work flow tools. One such tool is the Marvel system, a rule based software engineering environment developed at Columbia University [11]. Within this system it is possible to encode the rules that describe the Software Development Process and use these rules to control the execution of the tools that perform the process steps. We are investigating integration of Marvel and CB and are experimenting wlth Scrutiny in this merged ....

Gall E. Kaiser, Peter H. Feller, and Steven S. Popovich. Intelligent assistance for software development and maintenance. In: IEEE Software, 5(3) - 40-49 (May 1988)

....as well as the actual basis for the coordination and the management of the software engineering activities. Software process modeling and enactment is one of the main areas in software engineering research. Several frameworks have been developed (e.g. procedural [Osterweil 1987] rule based [Kaiser Feiler 1988 , Peuschel et al. 1992] Petri net based [Band inelli et al. 1993] object oriented [Conradi et al. 1994] Managing software process knowledge is also the goal of the experience factory approach [Basili et al. 1994] They distinguish between the organizational structure to manage the software ....

Kaiser, G. E., Feiler, P. H., and Popovich, S. S. (1988). Intelligent Assistance for Software Development and Maintenance, IEEE Software.

....f) software process evaluation standard or model based methods. The automated prescriptive models perform activities related to assistance, support, management and or computer assisted software production techniques. The models belonging to this category include: ALF [13] IPSE 2. 5 [58] Marvel [39]; PMDB [48] SOCCA [24] SPADE [7] 8] TRIAD [50] These models are computerised specifications of software process standards. Their main aim is to act as a guide for the software modelling process; that is, they are directed at aiding process agents by mechanically interpreting software process ....

G. E. Kaiser, P. H. Feiler, S. S. Popovich, "Intelligent assistance for software development and maintenance". IEEE Software (May 1988) 40-49.

....learning as well as the actual basis for the coordination and the management of the software engineering activities. Software process modeling and enactment is one of the main areas in software engineering research. Several frameworks have been developed (e.g. procedural [15] rule based ([11], 16] Petri net based [3] object oriented [5] Managing software process knowledge is also the goal of the experience factory approach [4] They distinguish between the organizational structure to manage the software knowledge (the experience factory department) and the activities that have to ....

Kaiser, G. E., Feiler, P. H., and Popovich, S. S. (1988). Intelligent Assistance for Software Development and Maintenance, IEEE Software.

....architecture. Most of the PSEEs developed during the last years adopts a standard client server architecture. Process enactment is centralized and tools communicate with the engine through point to point connections. Examples of such PSEEs are Adele [8] Arcadia [26] EPOS [11] JIL [25] Marvel [21], Merlin [23] Oikos [1] Process Weaver [19] Provence [7] SENTINEL [15] and SPADE [6, 5] Endeavors [9] adopts a complex architecture to distribute process enactment. Several process engines may coexist. They communicate with standard point to point connections. As mentioned, this approach ....

G. Kaiser, P. Feiler, and S. Popovich. Intelligent assistance for software development and maintenance. IEEE Software, May 1988.

....model: the activities, junctions, and inputs, outputs, controls, and mechanisms (ICOMs) The glossary contains text definitions of all activities and ICOMs. The ATL team plans to further develop PML and its associated toolsets, and to leverage related process ontology efforts, such as the Marvel [5] environment developed at Columbia University, to provide a more complete process interpretability package. In addition to identifying the activities and precedence relationships, the IDEF3 models also include logical identifiers on the ICOMs. which enable users to manage the product data relevant ....

....system. The logical identifier or business item name represents the place holder for instances of objects that will flow through the workflow. For product data and reusable element information objects that are managed in the system, RASSP information models represented in EXPRESS and EXPRESS G [5, 6, 7] (graphical form) describe the file configuration metadata about the product and domain specific metadata class hierarchies. 2] The information model includes configuration management constructs derived from the STEP [8] models, constructs specific to PDM system implementations, and ....

Kaiser, G., Feiler, P., and Poporuch, S.; "Intelligent Assistance for Software Development and Maintenance", IEEE Software, May 1988, p. 40-49.

....Crl. We first briefly summarize the Marvel system and then present problems with the Crl implementation in Marvel and problems to the Crl approach in general. 2.2. 3 Marvel Marvel is a RBDE developed by the Programming Systems Laboratory at Columbia University over the course of several years [65, 60, 18, 64]. Marvel is built on top of an object management system (OMS) that abstracts the components of the project under development as objects and stores them in an objectbase. The software development process of the project is modeled in terms of rules, each of which encapsulates a development activity. ....

Gail E. Kaiser, Peter H. Feiler, and Steven S. Popovich. Intelligent assistance for software development and maintenance. IEEE Software, 5(3):40--49, May 1988.

....process in terms of the events that occur during the development effort rather than changes to the product. Metrics should be based on analysis of these events. WISE addresses this by logging events in order to track issues throughout their lifecycle. Other software process tools, like Marvel [8], define processes from the top down: they help in defining the detailed software configuration process by informing users which components are potentially affected before performing subsequent editing, compiling, and other coding activities. Tools such as Marvel assist in development and ....

G. Kaiser and P. Feiler. Intelligent assistance for software development and maintenance. IEEE Software, pages 40-49, May 1988.

....the need for expansion to new software activities will arise and carry along the need to accommodate new tools and to expand the set of envelopes. This is the approach followed also in the case of our PCE, Oz, which has been equipped with a protocol for envelopes inherited from the Marvel system [27] (also a project by the PSL of Columbia University) to which it is intended to be the successor. While the original protocol (named Shell Envelope Protocol, or SEL [20] adequately services in a rather simple and elegant way a wide range of conventional Unix utilities (as explained in the ....

Gail E. Kaiser, Peter H. Feiler, and Steven S. Popovich. Intelligent assistance for software development and maintenance. IEEE Software, 5(3):40--49, May 1988.

....the users to learn how to use the system. Initially viewed as a process centered environment based on PCTE Emeraude [Thomas 88] the ALF project resulted in a platform that enables the definition and the instantiation of process centered Software Engineering Environments [Warboys 89, Taylor 88, Kaiser 88, Cerino 90] Indeed, the ALF system encompasses support for describing process models and for instantiating an environment that conforms to a given process model. It also provides support for enacting process models in instantiated environments. This presentation offers a general view of the ....

G.E. Kaiser, P.H. Feller and S.S. Popovitch. Intelligent Assistance for software development and maintenance. In IEEE - Software, 1988.

....of conventional Unix tools into the tailored PSDE rather than building specialized tools; and (3) supporting cooperation and coordination among multiple developers within a single software process. Many of the details of the first two aspects of Marvel have been presented in previous papers [KFP88, KBFS88] In this paper, I concentrate on the third aspect. I present the design and implementation of the concurrency control mechanism in Marvel, which significantly improve on our initial ideas regarding concurrency control [BK90] I also describe the constructs of the Marvel process modeling ....

Gail E. Kaiser, P. H. Feiler, and S. S. Popovich. Intelligent Assistance for Software Development and Maintenance. IEEE Software, 5(3):40--49, May 1988.

....Automation might be explicitly specified by the process model, or it can be inferred by the system. Note that automation can be used for enforcement. On the other hand, enforcement can be supported independently from automation. SDEs known for their automation support include CLF [89] and Marvel [59]. 3. Guidance The environment builder might choose to guide users in performing tasks in the process, without actually forcing them to do any of them. For example, the process might maintain a to do list of pending tasks. SDEs known for guidance support include ProcessWEAVER [32] and 4 In ....

....First, to introduce concepts and terms which will be used throughout the thesis, since large portions of Marvel were (re)used in Oz. Second, to clearly distinguish the work that was done in this thesis from the work that was done earlier in the context of the Marvel project. In a nutshell, Marvel [59, 17, 50] is a highly tailorable rule based PCE that supports project specific definitions for the data model, process model, tool envelopes, and coordination model. The runtime environment (i.e. the process engine) has a client server architecture that supports multiple users and enacts a centralized ....

[Article contains additional citation context not shown here]

Gail E. Kaiser, Peter H. Feiler, and Steven S. Popovich. Intelligent assistance for software development and maintenance. IEEE Software, 5(3):40--49, May 1988.

....tools and the interface between the process engine and the tool. We describe only those constructs of PAL relevant to the rule execution model, i.e. the rule sublanguage. PAL is based in part on the Marvel Strategy Language (MSL) first developed for the Marvel process centered environment [19] and later used in Oz [24] The steps making up a project specific software development process are modeled as three part rules similar to those used in AI planning systems. These rules (mainly) consist of: ffl A condition, which specifies a complex first order predicate logic precondition to be ....

Gail E. Kaiser, Peter H. Feiler, and Steven S. Popovich. Intelligent assistance for software development and maintenance. IEEE Software, 5(3):40--49, May 1988.

....and there are no separate environment commands or workflow that control tools. The Forest extension of Field manages the propagation of event 9 notifications among tools according to policies [26] analogous to Oz s process management services, and Provence is implemented on top of Marvel [36], 34] the predecessor of Oz, but neither has any means for requiring satisfaction of task prerequisites. These systems also do not address one of our foremost requirements, to integrate multi user tools, and few message buses are concerned with groupware or even support multiple users per bus. ....

Gail E. Kaiser, Peter H. Feiler, and Steven S. Popovich. Intelligent assistance for software development and maintenance. IEEE Software, 5(3):40--49, May 1988.

No context found.

G. E. Kaiser, P. H. Feiller and S. Popovich, "Intelligent assistance for software development and maintenance". IEEE Software, 5(3), 1988.

No context found.

Gail E. Kaiser, Peter H. Feiler, and Steven S. Popovich. "Intelligent Assistance for Software Development and Maintenance." In IEEE Software, May 1988.

No context found.

Gail E. Kaiser, Peter H. Feiler, and Steven S. Popovich. "Intelligent Assistance for Software Development and Maintenance." In IEEE Software, May 1988.

No context found.

Gail E. Kaiser, Peter H. Feiler, and Steven S. Popovich. Intelligent Assistance for Software Development and Maintenance. IEEE Software, pages 40--49, May 1988.

No context found.

G. Kaiser, P.H.Feiler, and S. S. Popovich. Intelligent assistance for software development and maintenance. IEEE Software,May 1988.

No context found.

G. E. Kaiser, P. H. Feiller and S. Popovich, "Intelligent assistance for software development and maintenance". IEEE Software, 5(3), 1988.

No context found.

[Kaiser 88] Gail E. Kaiser, Peter H. Feiler, and Steven S. Popovich. "Intelligent Assistance for Software Development and Maintenance." In 1EEE Software, May 1988, 40-49.

First 50 documents  Next 50

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