W. Wayt Gibbs. Software's chronic crisis. Scientific American 271(3), 86--95, September 1994.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....1983 1997 is 383. The years 1994, 1995, 1996 have 11 , 10 , and 9 of the software recalls. One possibility for this higher percentage in later years may be the rapid increase of software in medical devices. The amount of software in general consumer products is doubling every two to three years [3]. 21 19 10 7 30 3 Anesthesiology 10 Cardiology 21 Diagnostic 19 General Hospital 10 Other 7 Radiology 30 Surgery 3 Fig. 1. Failure distribution by device panel The medical devices can be grouped into classification panels according to the primary function of ....

W. Gibbs, "Software's Chronic Crisis," Sci. Am. (Int.Ed.) 271, 3 (sept.1994), 72-81.

....Software is everywhere. Computers are an integral part of our society and economy and their software becomes larger and more complex every day. Software development is a di#cult activity and many software projects take longer than expected, have large operational failures or are simply cancelled [39]. These problems are one of the main concerns of the software engineer community. It is proposed that one way to reduce the complexity of software development is to build software models. A model is a simplification of the reality that still retains the elements relevant to our problem. The ....

W. Wayt Gibbs. Software's chronic crisis. Scientific American, pages 72--81, September 1994.

....for existing component libraries. Keywords Automated Software Engineering, Containers, Component Software, Templates, Design Patterns 1. INTRODUCTION The size of modern software systems is increasing rapidly, with studies suggesting an order of magnitude growth every five to ten years [6, 8]. Development disciplines which accommodate the size of these modern architectures must address a number of issues. Of particular importance, and the focus of this paper, is the adoption of techniques which enable tractable reasoning. Our inability to do much is well recognized [3] The ....

....advanced separation of concerns in commercial software systems. We are aware, however, that the software industry has been remarkably slow in integrating the results of academic research, with results taking an average of eighteen years to find their way into standard programming practice [6]. This trend is in large part due to the inability of new development paradigms to coexist with existing technologies. Given the preponderance of legacy systems and the recent flood of commercially available COTS components, systems are increasingly composed, at least in part, of existing ....

W. W. Gibbs. Software's chronic crisis. Scientific American (International Edition), pages 72--81, Sept. 1994.

....tasks [9, 10] software specification [11] or GI Systems [12,13] 3. ALGEBRAIC SPECIFICATIONS Advanced specification techniques emerged from the need of better development tools. The process of designing correct software is a quite difficult task and bugs often result in financial losses [14]. Therefore, different methods for better specification methods have been produced. One of these methods is algebraic specification, which fulfills the following conditions [15] leads to adequate programs, i.e. programs that solve the customers problem, leads to correct programs, i.e. ....

Gibbs, W.W., Software's Chronic Crisis, Scientific American 271(3 (September 1994.

....for existing component libraries. Keywords Automated Software Engineering, Containers, Component Software, Templates, Design Patterns 1. INTRODUCTION The size of modern software systems is increasing rapidly, witit studies suggesting art order of magnitude grovth every five to ten years [6, 8]. Development disciplines which accommodate the size of these modern architec tures must address a number of issues. Of particular importance, and the focus of this paper, is the adoption of techniques which enable tractable reasoning. Our inability to do much is well recognized [3] The ....

....advanced separation of concerns in commercial software systems. VVe are aware, however, that the software industry has been remarkably slow in integrating the results of academic research, with results taking an average of eighteen years to find their xvay into stan dard programming practice [6]. This trend is in large part duc to the inability of new development paradigms to coexist with existing technologies. Given the preponderance of legacy systems and the recent flood of commercially available COTS components, systems are increasingly composed, at least in part, of existing ....

W. W. Gibbs. Software's chronic crisis. Scientific American (International Edition), pages 72 81, Sept. 1994.

....that are put into operation, two others are canceled. The average software development project overshoots its schedule by half; larger projects generally do worse. And some three quarters of all large systems are operating failures that either do not function as intended or are not used at all [Gibbs, 1994]. The essence of this so called softwere crisis is related to the limitations of the human mind to deal with complexity: When a system becomes so complex that no manager can comprehend its entirety, traditional development process breakdown. Gibbs, 1994] Associated to this limitation is the ....

....as intended or are not used at all [Gibbs, 1994] The essence of this so called softwere crisis is related to the limitations of the human mind to deal with complexity: When a system becomes so complex that no manager can comprehend its entirety, traditional development process breakdown. [Gibbs, 1994]. Associated to this limitation is the apparent inadequacy of currently available tools. Software development is a problem solving activity, and software engineering techniques and tools are used to assist humans in this activity. Software engineering has not traditionally focused on scientific ....

W.W. Gibbs. Software's chronic crisis. Scientific American, pages 86 95, September 1994.

....and hardware, which may be either analogue or digital. Even though many examples of products based on computer systems exist, the discipline for developing them is by no means mature or stable and their development presents a daunting and challenging task, sometimes leading to serious problems [3]. Although the design and implementation of hardware and software components is fairly well understood, relatively little progress has been made in development processes which consider the systems as a whole. The approach described delays the separate treatment of hardware and software until a ....

W. W. Gibbs, "Software's Chronic Crisis", Scientific American, pp. 72-81, September 1994

....management strengths and weaknesses. Index Terms Software project management, project simulation, project management education, software engineering INTRODUCTION Even in the late nineties software projects are still plagued by schedule and cost overruns, while product quality is often poor [2], 11] Improvement activities especially focus on process and technology issues, but investigations show that the success of software projects mainly depends on the quality of project management [5] Jones [3] states that successful projects are always characterized by effective project ....

.... practice in software project management not only reveals enormous deficiencies, but also shows that inadequate or inferior software project management is responsible for the serious problems of software development (software is late, over budget, and fails to meet the customer s requirements) [2]. The following statements reflect the results of two industrial case studies performed in the late nineties [5] Most of the interviewed project managers only did a part of the management functions necessary for successfully managing a software project. Being promoted into managerial positions ....

Gibbs, W.: Software's Chronic Crisis. Scientific American, 9 (1994), pp. 86-95.

....made intelligible and acceptable to non technical personnel [19] but only provided that they are augmented with sufficient amounts of informal explanation, diagrams, etc. 7. Maiandros 1 (M ff ff ffiaeo ) meandering Taking too long in the development of software is a widespread phenomenon [18]. Estimating the time for software projects is difficult since even given a specification, the complexity of the software to implement it is very hard to assess in any reliable and scientific way. In a typical project, natural language and diagrams are used to specify the desired system. These ....

W. W. Gibbs. Software's chronic crisis. Scientific American, 271(3):86--95, September 1994.

....which manage low level integration issues. Wright and Rapide abstract away most of the behavior of components and focus on interaction mechanisms. Practical experience has shown that these issues are not independent and changes to one often imply changes to the other, usually at great cost [6]. Thus, dcl abstractions represent an attempt at integrating both connection and deployment management policies within a single, uniform framework. 3. Specifying Distributed Software Architectures Distributed architectures are specified in terms of a set of components and their interconnection. ....

W. W. Gibbs. Software's chronic crisis. Scientific American, 271(3):86--95, September 1994.

....IT companies can no longer sustain ine#cient or ine#ectual CBR application development. What is required is a methodology for building CBR applications. Such a methodology should make CBR application developmentasystematic engineering activity rather than an art known by a few experts #Shaw, 1990; Gibbs, 1994#. A methodology usually combines a number of methods into a philosophy which addresses a number of phases of the software development life cycle #e.g. #Booch, 1994#, chapter 1#. It should give guidelines #recipes# about the activities that need to be performed in order to successfully develop a ....

Gibbs, W. W. #1994#. Software's chronic crisis. Scienti#c American, pages pp. 86#95.

....number (383) of software recalls from 1983 1997, 30 occurred in the years 1994 1996. One possibility for so high a percentage in three later years may be the rapid increase of software in medical devices. The amount of software in general consumer products is doubling every two to three years [2]. 10 21 19 10 7 30 3 Anesthesiology 10 Cardiology 21 Diagnostic 19 General Hospital 10 Other 7 Radiology 30 Surgery 3 Figure 2.1 Failure distribution by device panel The medical devices can be grouped into classification panels according to the primary ....

Gibbs, W., "Software's Chronic Crisis," Sci. Am. (Int.Ed.) 271, 3 (sept.1994), 72-81.

....the situation is the software crisis, although this has extended into a chronic problem. A high percentage of software projects are cancelled, and those which remain either fall behind schedule or have large cost overruns. On top of that, the resulting systems are often plagued by defects (Gibbs, 1994). Yet, as time goes by, systems contain an increasing proportion of software compared to hardware. Quality and reliability becomes more important than ever. Unfortunately, the majority of software development still remains an art rather than a science. Even as more development technologies are ....

Gibbs, W.W (1994). "Software's Chronic Crisis," Scientific American, Sep.

....justify a style of reasoning in which each application is developed independently. However, when migrating such systems to a shared network infrastructure, isolation is lost, compromising safety. A means of providing isolation to support and validate safety of NGI applications is urgently needed [Gibbs 1994, PCCIP 1997, Schneider 1998] Application designers depend upon isolation to rule out unanticipated interference. The interpretations of isolation and interference, however, vary among applications. For example, some critical applications will require security from intrusion, a property ....

Wayt Gibbs. Software's Chronic Crisis. Scientific American 276:3 (Sept. 1994).

....Introduction Only when the requirements are defined in conjunction with the characteristics that are relevant for quality, it is possible to measure software quality. We have learned from experience that it is neither possible to give a standard recipe to overcome software s chronic crisis [2], nor the deadlock can be broken easily that evolves in many projects because of short term and hectic activities of error correction to solve acute quality problems to the debit of long term and well panned methods to produce quality. Nevertheless, one main concept for quality can be presented ....

Gibbs, W.: Software's chronic crisis. Scientific American. 1994

No context found.

W. Wayt Gibbs. Software's chronic crisis. Scientific American 271(3), 86--95, September 1994.

No context found.

W. W. Gibbs. Software's chronic crisis. Scientific American, 271(3):72--81, September 1994.

No context found.

W. Wayt Gibbs, Software's chronic crisis, Scienti c American (1994), 86.

No context found.

W. Wayt Gibbs. Software's Chronic Crisis. Scientifc American, September 1994.

No context found.

Gibbs, W. W., "Software's Chronic Crisis" , Scientific American, Vol. 271, No. 3, September 1994, p.86

No context found.

Gibbs, W., Software's Chronic Crisis, Scientific American, September

No context found.

Gibbs, W.W., Software's Chronic Crisis. The Scientific American, pp. 86-95, September, 1994.

No context found.

Gibbs W., "Software's chronic crisis", Scientific American, 271:3, p86, (September 1994)

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