Abstract: No wonder you activities are, reading will be always needed. It is not only to fulfil the duties that you need to finish in deadline time. Reading will encourage your mind and thoughts. Of course, reading will greatly develop your experiences about everything. Reading formal specification and software development is also a way as one of the collective books that gives many advantages. The advantages are not only for you, but for the other peoples with those meaningful benefits.

Abstract: The nature of programming is changing. These changes will accelerate as improved software development practices and more sophisticated development tools and environments are produced. This paper surveys the most likely changes in the programming task and in the nature of software over the short term, the medium term, and the long term.In the short term, the focus is on gains in programmer productivity through improved tools and integrated development environments. In the medium term, programmers will be able to take advantage of libraries of software components and to make use of packages that generate programs automatically for certain kinds of common systems. Over the longer term, the nature of programming will change even more significantly as programmers become able to describe desired functions in a nonprocedural way, perhaps through a set of rules or formal specification languages. As these changes occur, the job of the application programmer will become increasingly analysis-oriented and software developers will be able to attack a large number of application areas which could not previously be addressed effectively.

Abstract: There are a wide variety of software development tools and methods currently available or which could be built using current research and technology. These tools and methods can be organized into four software development environments, ranging in complexity from a simple environment containing few automated tools or expensive methods to a complete one including many automated tools and built around a software engineering database. The environments were designed by considering the life-cycle products generated during two classes of software development projects. Relative cost figures for the environments are offered and related issues, such as standardization, effectiveness, and impact, then addressed.

Abstract: There has been a very rapid increase in the use of psychological experimentation as a method for addressing problems in the area of software engineering. However, there is a total lack of understanding on how to use this technique effectively so that the results of the experiment will have both validity and wide applicability. This paper describes what we feel is a major new research area which aims at formalizing the use of controlled group experimentation in programming language design and software engineering. The paper describes the growth of the problem, the critical need for this new research area and finally categorizes the problems that must be addressed as part of the research into these problems. An annotated bibliography contains literature references (through 1978) to the use of controlled group experimentation in software engineering and related areas of Computer Science.

Abstract: DIRECT is a multiprocessor database machine designed and implemented at the University of Wisconsin. This paper describes our experiences with the implementation of DIRECT. We start with a brief overview of the original machine proposal and how it differs from what was actually implemented. We then describe the structure of the DIRECT software. This includes software on host computers that interfaces with the database machine; software on the back-end controller of DIRECT; and software executed by the query processors. In addition to describing the structure of the software we will attempt to motivate and justify its design and implementation. We also discuss a number of implementation issues (e.g., debugging of the code across several machines). We conclude the paper with a list of the "lessons" we have learned from this experience.

Abstract: This paper describes a research project aimed at building and studying prototype environments for Mathematical Software. The project is aimed at gaining actual measurements and experiences that should help solidify knowledge about how to build effective environments. Towards this end some speculative ideas about environment file systems and command languages are presented, along with research plans for effectively evaluating these and other design notions.

Abstract: Software performance engineering (SPE) is a method for constructing software systems to meet performance objectives. The process begins early in the software life cycle and uses quantitative methods to identify satisfactory combinations of requirements and designs, and to eliminate those that are likely to have unacceptable performance, before developers begin implementation. SPE continues through the detailed design, coding, and testing stages to predict and manage the performance of the evolving software, and to monitor and report actual performance against specifications and predictions. SPE methods cover performance data collection, quantitative analysis techniques, prediction strategies, management of uncertainties, data presentation and tracking, model verification and validation, critical success factors, and performance design principles. In this article, performance refers to the response time or throughput as seen by the users. For real-time, or reactive, systems, this is the time required to respond to events. Reactive systems must meet performance objectives to be correct. Other software has less stringent requirements, but responsiveness limits the amount of work processed, so it determines a system's effectiveness and the productivity of its users. This article first covers the evolution of SPE then it gives an overview of the SPE process and the SPE methods. It presents the general principles for performance-oriented design, then it introduces the quantitative techniques for predicting and analyzing performance. The SPE techniques used throughout the software life cycle follow. Finally, the conclusion reviews the status and future of SPE. Keywords: evaluation; modeling; methods; development; principles; early life cycle; quantitative method; software performance engineering life cycle

Abstract: This paper summarizes the concepts of performance engineering in large software systems and illustrates the application of performance engineering techniques to the early design phase of a large database system.Performance engineering is a methodology for evaluating the performance of software systems throughout their life cycles. The case study given here demonstrates that it is possible to predict resource usage patterns of complex software systems even in early design phases of the system, although detailed predictions of resource usage are not likely to be validated. The results presented here show the leverage of considering performance implications in the early design phases of a software project.

Abstract: In this paper a sequence of software engineering courses based upon the software life cycle and integrated by a single, medium-size project will be described in detail. The courses will be presented from an educational point of view, emphasizing the topics covered as well as the logistics of teaching the courses. A comparison of these courses to other software engineering courses existing in university curricula will also be presented. The potential advantages for faculty, students, and the research community of this type of course sequence will also be enumerated.

Abstract: This paper describes the software and the software structure used in a family of high-capacity digital telephone switches. The call processing task is complex, and has great diversity. It must support existing and future features, including some not yet envisioned. The software must also provide man-machine interfaces, maintain the office database, and offer automatic recovery from hardware and software errors. It must also meet critical real-time performance specifications. The techniques adopted to meet these requirements include the use of a strongly typed high-level language, independent design and compilation of software modules, and the provision of an automated program library system and problem reporting system. Considerable experience in the development and support of large software systems has been accumulated, and is described in the paper.

Abstract: Twvo validation activities should take place during each phase of the software life cycle: analysis and test data generation. There are many ways to approach these tasks. The software life cycle can be divided into requirements , design, programming, and maintenance. Validation has also been considered a phase of the life cycle and is sometimes inserted between programming and maintenance. Recent experience, however, indicates that validation should be integrated into all phases rather than isolated in a separate stage that takes place long after requirements and design have been completed. Studies show that the later validation is carried out, the more expensive it becomes to find errors made early in the development process. I In the integrated approach described in this article, validation is a part of each phase of the life cycle. Two validation activities-analysis and test data generation-take place during each phase. The programming and maintenance phases also include actual execution of program tests. Analysis involves the direct examination of specifications and code for errors or erroneous properties. Test data generation involves the construction of test cases that are based on the important functional properties of specifications and code. Requirements Validation and requirements specifications. It is difficult to discuss the details of specification-based validation activities outside the context of a particular specification method. Of the different specification methods that have been developed (SADT, PDL, PSA/PSL, etc.), structured analysis2 is among the most general, and its use is assumed in the following discussion. Structured analysis specifications include data flow diagrams, data dictionaries, structured English and decision-table process descriptions, and file and database schemata. Various aspects of the method can be emphasized to suit various areas of application. The data flow diagram is often the most important part of the specification for a data processing application. The specification for a scientific program might consist entirely of a complex process description and data dictionary entries for describing input and output data. Figure 1 contains a typical data flow diagram of the type used in structured analysis. The circles, or \"bub-Figure 1. Data flow diagram for dating service database builder.

Abstract: This paper presents an overview of the TRW Software Productivity System (SPS), an integrated software support environment based on the Unix operating system, a wide range of TRW software tools, and a wideband local network. Section 2 summarizes the quantitative and qualitative requirements analysis upon which the system is based. Section 3 describes the key architectural features and system components. Finally, section 4 discusses our conclusions and experience to date.

Abstract: Software has a life cycle. It is conceived, matures, and dies. If uncontrolled during this life cycle, software, when executed, can produce undesirable results. Auditing is one process that should be performed periodically during the life cycle to reduce the likelihood of aberrant software behavior. Unfortunately, the trend in current practice is to perform auditing sporadically, cursorily, and inconsistently if at all. Perhaps a closer look at this function will illuminate its importance throughout the software life cycle and lead to its more frequent and consistent application in software development. There are two good reasons for examining software auditing: (1) The presence of software in our daily affairs is increasing , as evidenced by the burgeoning use of microcomputers for industrial, commercial, and personal applications. (2) Software development and maintenance have always been labor-intensive activities, and the wage spiral of recent years, coupled with declining hardware costs, has pushed increasing software costs into prominence.

Abstract: Due to modern technology, software will to an increasing extent be frozen into hardware. This is just one example for situations where bugs in the software are absolutely intolerable. Therefore programming must soon become a safe process of program Construction; that is, it has to be organized as a sequence of steps of rational reasoning. Starting from an elaborate formal problem specification using elements of predicate logic, set theory and primitives from some algebras, the application of formal rules leads to algorithmic versions and finally to programs oriented towards the instruction repertoire of particular concrete machines.A genuine program construction process needs strict formalization throughout. All versions including the specifications can conveniently be represented by one programming language comprising the complete spectrum of descriptive, applicative and procedural styles. Such a language includes the concept of nondeterminism, which makes the development process transparent and extremely flexible, and it is to be interpreted by some model of the underlying abstract data types. The use of formally proved transformation rules guarantees this correctness.In addition, the transformational approach is universal in the sense that the collection of rules can be adapted to the application in question: Although initially envisaged and mainly used now for the construction of software for classical sequential stored-program machines, the approach can be extended to other computational models corresponding to the often cited innovative hardware architectures.

Abstract: Basic hardware and software components of computers are described and related concepts are defined using examples related to the hospital pharmacy department. Hardware components described include the central processing unit, storage devices, and input and output devices. System software, application software, computer language, and computer characteristics for hospital pharmacy systems are identified. Trends toward computer miniaturization, increased processing capacity at reduced costs, and new software technologies will enable an accelerated pace of new system development and implementation. Applications that are now difficult to justify because of high development cost or low benefit to the hospital will become more easily cost justified.

Abstract: Within a production programming environment, a software quality assurance program (QAP) was instituted to produce standards, conventions, and methodologies for all phases of the software development process Software language standards and several support processors, in turn, developed The authors offer a plan which may help others avoid some of the pitfalls they experienced while attempting to construct a meaningful software QAP

Abstract: In August of 1980, we wrote an articlel in which we hypothesized 20 major software engineering project management problems. (To avoid later confusion, we define a \"software engineering project\" as a software development task that has a prescribed starting point, a specific budget and resources, established responsibilities, and a completion schedule.) We also conducted an opinion survey on a sample of the data processing industry to verify these hypothesized SEPM issues. Our sample consisted primarily of senior computer scientists, authors and lecturers on software engineering and project management, software development project managers, and highly visible individuals who, because of their position in industry, government, and universities, influence the opinion of the computing community. Below is a listing of the twenty problems used in our survey.

Abstract: A distributed system is a computing system in which a number of components cooperate by communicating over a network. The explosive growth of the Internet and the World Wide Web in the mid-1990s moved distributed systems beyond their traditional application areas, such as industrial automation, defense, and telecommunication, and into nearly all domains, including ecommerce, financial services, health care, government, and entertainment. Developing highquality software for distributed systems is hard; successfully developing and applying high-quality reusable software is even harder. The principles, methods, and skills required to develop and apply reusable distributed systems software cannot be learned by generalities and concepts alone. Instead, researchers, developers, and educators must learn through hands-on experience how reusable software components, frameworks, and applications can be designed, implemented, optimized, validated, maintained, and enhanced by applying good development practices, patterns, tools, and platforms.