CS499 01 Introduction

A later translation (2015) of the article in Russian published in 1990. The article proposes an approach to defining a set of basic notions for subject area of software engineering discipline. The set of notions is intended to serve as a basis for detection and correction of some widespread conceptual mistakes in the efforts aimed at improving the quality and work productivity in creation and operation of software.

Advances in Software Engineering, 2008

The nature of software engineering is discussed with particular reference to softwareintensive application systems-those whose fundamental purpose is to bring about desired effects in a physical and human problem world by interaction with a programmed machine. Such systems bring together a problem world-which is typically composed of heterogeneous domains, most of which are non-formal-and the formal or semi-formal domain of the machine. A clean engineering separation of the two is rarely, if ever, possible; and attempts to treat the application problem world as an extension of the formal machine are obstructed by its non-formal nature. Software engineers have much to learn from the structure and practices of the established branches of engineering. We must learn from their treatment of formal analysis and reasoning, from their practice of intense specialisation, from their attention to particular instances no less than to general concerns, and-above all-from their reliance on normal artifact design and on normal design disciplines: both are the golden fruit of specialisation.

Software engineering is the area of energizing where an engineer collects the physical fundamentals of a given concept through a scientist and perform practical on it, to check its overall processing and to verify it. In software engineering, researchers have given the physical fundamentals for performing something and these fundamental concepts are verified by an engineer. After this process an engineer has a heavy bundle of experimental data. They use few proposal models & techniques to analysis the overall work. Finally the team of technologists develop the product for people. Therefore we can say that range of work for these three people are bound to each other but not common. This paper has three different phases of current analysis to enlighten the mind of employees and researchers. In the first phase of the paper we clear the concept of scientist, engineer and technologist. In the second phase we analyse the age of software and prove that software does not have age limit and last phase of the paper shows graphical results of the survey to distinguish between techniques, method and approach. In this paper we have also highlighted the impact of v& v on software engineering.

2000

There are however, two main facets through which these interests can be viewed Ć process and product. Process is concerned with the organised set of tasks that a software engineer must carry out in order to develop a system. It is concerned with the nature of the tasks, how they are configured into an overall coherent workflow, the means by which these tasks are coordinated and environments that are necessary to support this process.

Communications of the ACM, 1997

Although the first of many conferences on "Software Engineering" was held in Munich nearly three decades ago, communication between those who study the problem of building software and those who teach Engineering or work as Engineers has not been effective. Today, the majority of Engineers understand very little of the "science of programming". On the other side, the scientists who study programming understand very little about what "Engineer" means, why we have a self-regulating profession, how the profession is organized, and how engineers are educated. In spite of this mutual ignorance, today's engineers spend much of their time writing and using software, and an increasing number of people trained in computer science or mathematics are doing what work that meets the legal definition of Engineering.

Q: Prove that software engineering is a layered technology with proper diagram. A: Software engineering is a layered technology. Referring to the above figure, any engineering approach (including software engineering) must rest on an organizational commitment to quality. Total quality management, Six Sigma, and similar philosophies foster a continuous process improvement culture, and it is this culture that ultimately leads to the development of increasingly more effective approaches to software engineering. The bedrock that supports software engineering is a quality focus. The foundation for software engineering is the process layer. The software engineering process is the glue that holds the technology layers together and enables rational and timely development of computer software. Process defines a framework that must be established for effective delivery of software engineering technology. The software process forms the basis for management control of software projects and establishes the context in which technical methods are applied, work products (models, documents, data, reports, forms, etc.) are produced, milestones are established, quality is ensured, and change is properly managed. Software engineering methods provide the technical how-to's for building software. Methods encompass a broad array of tasks that include communication, requirements analysis, design modeling, program construction, testing, and support. Software engineering methods rely on a set of basic principles that govern each area of the technology and include modeling activities and other descriptive techniques. Software engineering tools provide automated or semi-automated support for the process and the methods. When tools are integrated so that information created by one tool can be used by another, a system for the support of software development, called computer-aided software engineering, is established. Q: State and discuss various process models with their applications. A: A generic process model for software engineering encompasses a set of framework and umbrella activities, actions, and work tasks. Each of a variety of process models can be described by a different process flow—a description of how the framework activities, actions, and tasks are organized sequentially

Wirtschaftsinformatik / Angewandte Informatik - WI, 1982

Abstract: It is hoped that software development can become a branch of engineering, but there are important differences. Software is intangible, complex, and capable of being transformed by a computer. Much effort has been devoted to overcoming the difficulties due to intangibilityand complexity, but too little has been devoted to exploiting the third characteristic. A processoriented view of software may lead to substantial improvements,in this and other respects. Stichworte: Entwurf, Entwicklungsmethoden, Implementation, Software Engineering, Standardisierung. Zusammenfassung: Es wird allgemein erwartet, dass sich die Softwareentwicklung zu einer ingenieurmässigen Disziplin