Software Generation. Prentice Hall, 1993.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....data management issues, to be held in Annecy in the second quarter of 1997. 34. A CORBA compliant Object Request Broker from Iona Technologies, Dublin. 35. The material presented in this course is largely covered in the books Software Engineering Standards [20] and Software Engineering Guides [21]. distributed for comments and corrections to both groups, was to provide information exchange regarding the various technologies being studied within RD45. It is clear that very close work with these groups will be needed in the future: to help in the generation of the computing technical ....

"Software Engineering Guides", C. Mazza, J. Fairclough, B. Melton, D. De Pablo, A. Scheffer, R. Stevens, M. Jones and G. Alvisi, Prentice Hall, ISBN 0-13-449281-1

.... in distributed and heterogeneous environments [4, 11, 13] These systems are already and will continue to severely influence and shape the structure of information systems in business and nonbusiness environments [14] While software development processes have been investigated for some time now [2], the specific properties of workflow application development processes (WADP) received little attention so far. This paper tries to remedy this situation by analyzing problems encountered during the conduction of real world workflow application development projects and by formalizing the ....

....to individualized solutions, reference models represent a class of application cases; hence, they intend to serve as patterns for solutions of specific real world problems. Examples of reference process models are the well known models of software engineering processes (e.g. waterfall model [2], fountain model [5] prototyping approach [3, 17] While the reference model presented in this paper belongs to this class of reference process models, we focus specifically on the issues encountered during workflow projects. Process models for the customization and implementation of ....

B. Boehm: Software-Engineering Economics. Prentice Hall, 1981

....our observations some proposals for extensions and changes to the UML are made. Because the example is complete and self contained and provides methodical guidelines and hints, it can also be used as a tutorial for UML 1.0 and for object oriented development in general. Keywords: Object Oriented Software Engineering, Modeling, Analysis, Design, UML, Java, RMI # This paper originated in the ForSoft project A1 on #Component Based Software Engineering and was supported by Siemens ZT. 1 Contents 1 Introduction 4 2 Techniques and Process 5 2.1 Uni#ed Modeling Language . ....

....methodical guidelines and hints, it can also be used as a tutorial for UML 1.0 and for object oriented development in general. Keywords: Object Oriented Software Engineering, Modeling, Analysis, Design, UML, Java, RMI # This paper originated in the ForSoft project A1 on #Component Based Software Engineering and was supported by Siemens ZT. 1 Contents 1 Introduction 4 2 Techniques and Process 5 2.1 Uni#ed Modeling Language . 5 2.2 Process . 6 2.3 Java, Object ....

[Article contains additional citation context not shown here]

Software. Prentice Hall, 1990.

....future plans for calibrating and validating the model. Copyright USC CSE 4 06 30 97 2. Background Model The Quality model is an extension to the existing COCOMO II [USC CSE 1997a, Boehm et al., 1994] model. It is based on The Software Defect Introduction and Removal Model described in SEE [Boehm, 1981] which is analogous to the tank and pipe model introduced by Capers Jones [Jones, 1975] This model shows that defects conceptually flow into a holding tank through various defect source pipes are drained off through various defect elimination pipes as shown in Figure 1. Figure 1 : Software ....

- Software Engineering Economics, Barry W. Boehm, 1981, Prentice-Hall

....of process algebras, in order to narrow the gap between formal specifications on the one hand and running programs on the other. The workbench adheres to existing standards such as the ECMA Reference Model, the Portable Common Tool Environment (PCTE) 10] CORBA [37] or COM [37, 6] and Motif [11]. It has been constructed from off the shelf public domain implementations of these standards, such as H PCTE [7] Tk [38] and daVinci [12] among others. These components have then been integrated, resulting in a framework that uses its own integration features in constructing itself, i.e. it has ....

Open Software Foundation. OSF/Motif Series. Prentice Hall, 1992.

.... Issues in Software Reuse: It s Not Just the Functionality, It s the Packaging Mary Shaw School of Computer Science Software Engineering Institute Carnegie Mellon University Pittsburgh PA 15213 Proc IEEE Symosium on Software Reusability, April 1995 Abstract Effective reuse depends not only on finding and reusing components, but also on the ways those components are combined. The informal folklore of software engineering provides a number of diverse styles for organizing software systems. These styles, or architectures, show how to ....

Software Architecture: Perspectives on an Emerging Discipline. Prentice Hall, 1995, to appear.

....Consistent best performance (minimal bias and highest precision) can be obtained by using hot deck imputation with Euclidean distance and a z score standardisation. 1 Introduction There exists a vast literature on the construction of software cost estimation models, for example [60] 17] 1] 2][12][25] 42] 28] 49] 82] 88] 79] 87] The basic premise is that one can develop accurate quantitative models that predict development effort using historical project data. The predictors typically constitute a measure of size, whether measured in terms of LOC or a functional size measure, and a number ....

....such economies. The concept of economies of scale states that average productivity increases as the system size increases. This has been attributed, for example, to software development tools whereby the initial tool institutionalisation investment may preclude their use on small projects [12]. Furthermore, there may be fixed overhead costs, such as project management, that do not increase directly with system size, hence affording the larger projects economies of scale. On the other hand, it has been noted that some overhead activities, such as documentation, grow at a faster rate ....

[Article contains additional citation context not shown here]

B. Boehm: Software Engineering Economics. Prentice-Hall, 1981.

....comprise a host of details which make it difficult to quickly grasp the more general context. It is for this reason logic to provide models for visualisation of specific conditions, which have specifically been abstracted for this particular purpose. In compliance with the spiral models [9], this procedure was extended to comprise the aspects of quality assurance. Fig. 3: Extended model of system development With each step, the results are checked for compliance with the targets. Should this check up produce any differences, it is inevitable to return to an earlier phase. In this ....

B. Boehm: Software Engineering Economics. Prentice Hall, 1981.

....environment is to save applications and services designers from knowing about those mechanisms. Therefore it is worth presenting the distribution framework as well as equipments used in the purpose of this work. The Distribution Framework The platform chosen for this work is OSF DCE version 1. 0 [OSF92]. Based on industrial standards, DCE supports the development and execution of distributed applications on networked computer systems (fig. 6) Ros93] In addition to providing a consistent programming environment, DCE is independent of operating systems and protocols and offers a wide range of ....

Open Software Fundation: Introduction to OSF DCE, Prentice Hall, 1992

....to the repository itself through the version and configuration graphs (see Fig. 2) The user can invoke services of the workbench using application menus associated with the graph. The UniForM Workbench obeys established industry standards such as the ECMA Reference Model, PCTE and Motif [7]. It has been implemented on the basis of public domain, off the shelf components supporting these standards. The repository manager for example is based on H PCTE [4] whereas the user interaction manager integrates Tk [25] and the graph visualisation system daVinci. Moreover, the workbench ....

Open Software Foundation. OSF/Motif Series. Prentice Hall, 1992.

....of fixing defects during inspections to fixing them during formal testing at JPL was found to range from 1:10 to 1:34 [21] At the IBM Santa Teresa Lab the cost ratio was 1:20 [31] at the IBM Rochester Lab it was 1:13 [20] and the cost ratio for design inspections to testing at TRW was 1:6. 25 [3]. The business case is even more impressive when one considers the cost of fixing defects postrelease. Other nonquantifiable benefits of inspections have been reported, such as promoting team spirit, the transfer of skills and facilitating on the job training [8] As with the introduction of any ....

B. Boehm: Software Engineering Economics. Prentice-Hall, 1981.

....20 Mbits s transfer rate. The machine is totally reconfigurable. 3.1. The Helios system We choose the Helios operating system available on the Multicluster II for the following reasons: it allows the C programming, manages the message routing between the nodes and suggests a mapping tool. Helios [10] is a distributed UNIX like operating system [11] It allows the underlying machine concurrency to be used and also its communication possibilities too. We used the C ANSI compiler of the Helios system. Let us detail the tools of Helios for concurrency and communication. Concurrency expression in ....

Perihelion Software The HELIOS Operating System, Prentice-Hall, 1989

....to an enterprise s business processes. But a common point in the former cited methodologies is a focus on enterprise modeling. Therefore one focus for a methodology for building knowledge management systems is surely enterprise modeling. For building such a model guidance is needed, see e. g [Dav93] 2 . Furthermore, as building the enterprise model according to an appropriate knowledge structure is surely knowledge intensive wicked problem (see e.g. Buc97] and also important to improve the self awareness of an enterprise. So the enterprise model is often useful as a content of an ....

....and Technology) under grant number 01HS014 2. Because there are so many relationships that can exist between items under analysis and so many levels of possible detail, analysts need [ a knowledge structure, which is just a structured collection of concepts and their interrelationships. [Dav93] to be a representative overview, there are many other approaches, however, ARIS is one of the most prominent business process reengineering approaches and CommonKADS is the most popular approach for building knowledge based systems. 2 Existing Approaches 2.1 ARIS A modeling approach ....

A.M. Davis: Software requirements: objects, functions, and states, Prentice Hall, 1993

....comparable difficulty with previous, typical projects in an organization (benchmarking) Such analyses may lead to the redefinition of the project s requirements or to the definition of appropriate contingency plans. Different techniques for cost estimation have been discussed in the literature [3][9] 10] for example: algorithmic and parametric models, expert judgment, formal and informal reasoning by analogy, price to win, top down, bottom up, rules of thumb, and available capacity. More recently, analogical and machine learning models [5] 23] have also been developed. Despite extensive ....

.... been found to be related to increases in the number of large projects that overrun their estimates [17] In addition, more structured bottom up experiential approaches can potentially suffer from an optimistic bias due to estimators extrapolating from an estimate of only a portion of the system [3][9] In one study that evaluated experiential estimates, optimism was demonstrated [10] However, another study showed that experiential estimates are pessimistic, with the estimators estimating more than the actual [16] In any case, both over and underestimation, as noted in [17] can have ....

[Article contains additional citation context not shown here]

B. Boehm: Software Engineering Economics. Prentice-Hall, 1981.

....we define the main terms used in this paper. Second, we present the theoretical model that is being empirically tested in our study. 2.1 Definitions RE Process The definition of the RE process that will be used here is based on the kinds of activities that are performed during that process. In [26], Davis makes a distinction between two types of such activities: problem analysis and product description. During problem analysis the objective is to gain the most knowledge about the problem at hand. During product description, the objective is to construct the specification for the software ....

A. Davis: Software Requirements: Objects, Functions, and States, Prentice-Hall, 1993.

....engineering was the development of so called life cycle models which were aimed to describe the activities occurring during the software development process, their results, and their dependencies. Many of them have been published so far, mostly differing only in their granularity (cf. e.g. [Boehm82]) The rise of new programming paradigms though has introduced a new kind of life cycle models in the past years (cf. e.g. Agresti86] They can be called continuous models in contrast to the discrete models, because they do not consider the activities during software development as separated ....

B.W. Boehm: Software Engineering Economics, Prentice Hall, 1982.

....be used for reading as usual. 6 Experimental Results In order to compare the efficiency of the (implementations of the) different parallel languages, we have measured the runtimes of matrix multiplication on a p p Theta p p torus of T800 transputers (20 MHz) The programs in Occam, Helios C [15], and our data parallel functional language (DPFL) are based on Gentleman s algorithm [4] shown above. The implicitly parallel functional program (IPF) is based on the program shown in the beginning of Section 2. Occam, Helios C, and DPFL provide a linear speedup, while the implicitly parallel ....

Perihelion Software: The Helios Parallel Operating System, Prentice Hall, 1991.

No context found.

Reusable Software. Prentice Hall. Osmond, R. (1994a).

....requirements are more demanding, a process for architecting these new systems is now essential. No longer can systems be simply assembled from components without consideration of the whole [Foot97] Architecture is not the creation of boxes, circles, and lines, laid out in slide presentation [Shaw96], Shaw96a] Architecture imposes decisions The term architecture is so overused in the software business, that it has become a clich. There are official descriptions of software architecture and architects. Much of the architecture work has taken place inside development organizations and ....

....change to business critical documents and delivery these document to the proper user at the proper time. CHARACTERISTICS OF MANUFACTURING TECHNOLOGIES There are several characteristics of manufacturing systems that are shared by all systems with good architectural foundations. Witt94] Rech97] [Shaw96], Garl95] These properties may appear abstract and not very useful at first. However, they are measurable attributes of a system that can be used to evaluate how well the architecture meets the needs of the user community. n Openness enables portability and internetworking between components ....

[Article contains additional citation context not shown here]

Software Architecture: Perspectives on an Emerging Discipline, M. Shaw, and D. Garlan, Prentice--Hall, 1996.

No context found.

Software Requirements: Analysis & Specification, A. M. Davis, prentice Hall, 1990.

....work has taken place inside development organizations and academia. In this paper, the description of architecture is taken from a variety of reliable sources. Niwot Ridge Consulting, September 2000 2 Architecture is not the creation of boxes, circles, and lines, laid out in presentation slides [Shaw96], Shaw96a] Architecture imposes decisions and constraints on the process of designing, developing, and deploying information systems. Adow95] Alle94] Kazm96] Perr92] Architecture must define the parts, the essential external characteristics of each part, and the relationships between ....

....these document to the proper user at the proper time. Niwot Ridge Consulting, September 2000 5 CHARACTERISTICS OF MANUFACTURING TECHNOLOGIES There are several characteristics of manufacturing systems that are shared by all systems with good architectural foundations. Witt94] Rech97] [Shaw96], Garl95] These properties may appear abstract and not very useful at first. However, they are measurable attributes of a system that can be used to evaluate how well the architecture meets the needs of the user community. n Openness enables portability and internetworking between components ....

[Article contains additional citation context not shown here]

Software Architecture: Perspectives on an Emerging Discipline, M. Shaw, and D. Garlan, Prentice--Hall, 1996.

No context found.

Software Requirements: Analysis & Specification, A. M. Davis, prentice Hall, 1990.

....gained is being channelled back into evolving the standard through the SESUG [1] of which CERN is an active member. The PSS 05 standard has been published as Software Engineering Standards [2] The ten associated guides have been collected into a book and published as Software Engineering Guides [3]. The structure of the PSS 05 standard is based around a software life cycle reference model that defines the activities for each phase as well as identifying the inputs and outputs to from each phase. The following phases are defined: User Requirements (UR) or problem definition phase. ....

Software Engineering Guides, C. Mazza, J. Fairclough, B. Melton, D de Pablo, A. Scheffer, R. Stevens, M. Jones, G. Alvisi, Prentice-Hall, 1995. ISBN 0-13-449281-1.

No context found.

Software Engineering, pages 1#49. Prentice-Hall, New York, 1992.

No context found.

Boehm81 - Software Engineering Economics, Barry W. Boehm, Prentice-Hall, 1981.

No context found.

Boehm81 - Software Engineering Economics, Barry W. Boehm, Prentice-Hall, 1981.

No context found.

Software Generation. Prentice Hall, 1993.

No context found.

Open Software Foundation OSF/Motif Programmer's Reference. Prentice Hall, (1991)

No context found.

Open Software Foundation: OSF/Mot if Programmer's Guide. Prentice-Hall, c.1990.

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