- Research Article
- 10.1145/75111.75128
Some reservations on software process programming
- Apr 01, 1988
- ACM SIGSOFT Software Engineering Notes
- M M Lehman
Some reservations on software process programming
In what follows the term `process programs` is used as shorthand for the stated intended workshop focus `executable and interpretable (surely `interpretable and executable`?) models of the software (`development?`) process and their prescriptive application to directly controlling software project activities`.
Some reservations on software process programming
Some reservations on software process programming
Guest editors' introduction
Guest editors' introduction
The role of process models in software and systems development and evolution
In seeking to maximise opportunity for achieving common understanding and real progress on specific issues, the announcement for the 5th Process Workshop adopts a somewhat narrow view of the role of Process Models. By so focussing the discussion, the fact that desirable characteristics of models will vary with the purpose for which they are to be used, the benefit one hopes to derive from their development or use and the value attached to benefit to gained from such activity has had to be disregarded. Yet process models can serve many purposes as summarised, for example, in the introduction to the Proceedings of the 4th workshop [SPW88] and also on the attached table. Though the roles included in that table are neither newly identified nor controversial they are listed so that they may be kept in the back of our minds as the Workshop discussion progresses.The individual importance of these roles can clearly not be ordered or even quantified. Their relative significance will depend on the goals of the work during which they are developed or used. The primary motivation underlying my work with process models over the past years has been the search for a better understanding of the software development and evolution process. This has led to conclusions which are, perhaps, self evident to many Computer Scientists, [DEM79], [FET88], [VAR79, 89] (as extreme examples) and others [BON77]. They are, however, not widely understood by the general public and, more importantly, by those involved in the definition and acquisition of computer systems for specific applications. In view of the increasing dependence of mankind on computers and, hence, on software it appears important to bring these, explicitly, into the open and to also examine their implications in the narrower confines of the topics discussed in the process workshop series.In the first instance my studies concentrated on an examination of models of program evolution in recognition of the fact that understanding and controlling that phenomenon demanded understanding and control of the programming process [LEH69, 85a]. This investigation led directly to the SPE classification scheme in which E-type programs, in particular, are defined as programs that implement applications or solve problems from and in the real world. In developing this schema process models played a fundamental role [LEH80b]. These models had no direct or immediate relationship to development practice but, nevertheless, led to the insight that is reflected in the LST process model [LEH84] that later formed the conceptual underpinning of a working environment [LEH85b].The work led to the view that an E-Type program is a model of a model of a … model of an application in the real world [LEH80b]. This abstract total-process model was enriched by Turski's view [TUR81] which regarded successive model pairs as a theory and a model of that theory or, equally, as a specification and an implementation of that specification. At the First Process Workshop [SPW84] Turski's interpretation of the “three-legged” model was, in fact, to see both the real world application (concept) and the final implementation as models of a specification that forms the bridge between concept and realisation. Equally, the source and target representations at the core of each step of the LST process, for example, may be viewed as a theory and a model of that theory.From Turski's view it follows that each implementation is Godel incomplete. Its properties, including functional properties, cannot be completely known from within the system. By their involvement in the development process and through system usage humans become an integral part of the system. It is their insights, viewpoints, theories, algorithms, definitions, formalisations, reactions, interpretations and so on that drive and direct the abstraction, refinement and evolution processes. They determine the degree of satisfaction that the final solution system yields. Hence it may be observed that for any software system implementing a solution to a real world problem, modelling some aspect of the real world, there exists a degree of Godel-type uncertainty about its properties [LEH89]. The definition, specification and development process must seek to limit this uncertainty so that it is of no practical significance; reflecting only abstract representational incompleteness.This is not the only type of uncertainty related to program behaviour under execution relative to the operational environment. A primary property of E-type programs is the fact that installation and operation of a system change the application and its operational domain. Implicitly if not explicitly, the system includes a model of itself. Also the acts of conceiving, developing, installing, using and adapting a software system change understanding of the application and its needs, methods of solution, the relative value of specific features of system functionality, opportunities for enhancement and human perception of all these. This leads to declining satisfaction with the system unless the system is adapted to the new reality. Because of the many feedback paths the system displays Heisenberg-type uncertainty [LEH77]. The more precise the knowledge of the application, of system properties and of their respective domains the less satisfaction does the solution system deliver in terms of what are, at the time of usage, the system properties perceived to be desirable. Mismatch between system properties and human needs and desires cannot be removed, except momentarily. Development, adaptation and evolution processes and their management are key to minimisation of the consequences of this inherent uncertainty.There is also a third type of uncertainty. The domain of an E-type application is, in general, unbounded and, effectively, continuous. The solution system is finite and discrete. The process of deriving one from the other involves a variety of abstractions on the basis of assumptions, about the application, its domain, perceived needs and opportunities, human responses to real world and solution system events, computational algorithms, theories about all these and so on. Some assumptions will be explicitly stated, others will be implicit. All will be built into the final system. But the real world is essentially dynamic, forever changing. Even without feedback effects as discussed above, exogenous changes in the real world will change the facts on which the assumption set is based. However careful and complete the control on the validity of assumptions is at the time they are built into the system some, at least, will, at best, be less than fully valid when the program is executed, or better, when the results of execution are applied. That is when, to be fully satisfactory, a program needs to be correct. Initial correctness at the time of implementation is merely a means to an end. The assumption set must be maintained correct without significant delay by appropriate changes to program or documentation texts, an impossible task even if assumptions could be precisely pinpointed. Pragmatic uncertainty in system behaviour is inevitable.This analysis leads to the following Uncertainty Principle for Computer Application: The outcome of software system operation in the real world is inherently uncertain with the precise area of uncertainty also not knowable.This position paper is not the place to explore this assertion in detail. Some aspects have been discussed elsewhere [LEH77, 89]. More immediately the principle throws a new light on the expectations to be associated with Software Engineering, the system and software development process and the models constructed to represent that process. One may have many views of the process. The new one that emerges from the above discussion is of software engineering in general and the software development and evolution (maintenance) process in particular as the means to minimise uncertainty, the consequences of uncertainty and the maintenance of user satisfaction. Project models must reflect this responsibility
Read moreThe Role Of Process Models In Software And Systems Development And Evolution
The Role Of Process Models In Software And Systems Development And Evolution
Service-Oriented Software Development Value Chain and Process
SOA provides a new method to optimiz software development process with value chain. A formalized definition and a meta-model about value chain were introduced for analysing the difference between traditional software development process and service-oriented reusable software process. Furthermore, some metrics in software development value chain was proposed and compared in value matrix. The results show that the service-oriented reusable development process has more value improvement than traditional software process, which collaborate all the resources and roles in software process together under an open environment.
Read moreProcess mining application in software process assessment
Nowadays, our daily life heavily depends on software. Software is everywhere, from appliances in our homes, to safety-critical systems such as medical equipment. The failure of these software-intensive systems results in high financial losses, environmental or property damages, or even loss of life. Therefore the quality of software is recognized as a critical factor in software development. In order to achieve high quality of software products, reduce the costs of their development and deliver the product within specified time, activities for creating these products must be specified and executed. This set of activities is called the software development process. The software development process aims at creating complex and quality software products. Based on the premise that good quality software development process leads to good quality software products, the need for continuous software process improvement is recognized. Software process improvement is a cyclic activity involving assessing the current software development process in an organization, setting improvement goals, planning and executing improvements, analyzing and evaluating improvement results. A starting point for the software process improvement is software process assessment, which creates a baseline for improvement. The information gathered during the software process assessment must be objective and provide a realistic picture of the software development process. Currently, such process assessment is based on the information that is gathered based on interviews, brainstorm sessions, presentations, questionnaires and document reviews. These information gathering techniques are suitable in a stable environment with a limited problem space. However, software processes are complex entities, involving heterogeneous resources. Furthermore, software processes are often not explicitly modeled, and manuals to support the development work contain abstract guidelines and procedures. The differences between the actual executed (i.e. real) process and the documented process were already recognized by the research community. Therefore, another approach to gather process information for software process assessment is needed. In this thesis, we present a structural approach for choosing a more suitable information gathering strategy based on taking the characteristics of software processes into account. We performed a structured literature review in order to identify characteristics of software processes. Based on these characteristics, we identified the strategies 1) synthesis from characteristics of software processes and 2) experimentation with a discovered software process as more appropriate. Furthermore, we identified process mining as a set of techniques associated with these strategies and therefore suitable for software process assessment. In order to investigate the feasibility of process mining and its added value for software process assessment, we performed series of case studies on the practical application of software process mining on data from an industrial company. The case studies showed that process mining can provide useful and non-trivial process insights. Based on an in-depth study of a widely used software process improvement framework, namely the Capability Maturity Model Integration (CMMI), and its assessment method, a structured approach to use process mining for software process assessment was designed. First, we identified processes to be analyzed by process mining techniques. CMMI describes process areas to which an organization should map its software development. These process areas are satisfied by applying practices specific to a given process area. We identified specific practices, which can characterize software development processes and we proposed criteria to identify the practices for which process mining is feasible. These criteria are based on the notion of uncertainty. Next, we identified process aspects (such as compliance to the specified process model or timeliness of a software development process) essential for software process improvement as defined by CMMI. These process aspects determine which process information must be collected for the software process assessment and subsequent improvement. After that, we identified process-mining techniques that can provide this process information. As a result, we identified the parts of CMMI where collecting an objective evidence for process assessment by means of asking and deriving can be replaced by an application of identified process mining techniques. Although we applied process mining in the context of CMMI, our approach can also be applied to other software process improvement frameworks. Subsequently, the availability of the data required for process mining was studied. First, we identified data requirements for process mining techniques. Based on this, an approach to evaluate the suitability of software development support tools as data sources for process mining was developed. To test this approach, we considered software configuration management tools as possible data sources for process mining and selected the data logs of four commonly used software configuration tools for further study. We compared these data logs to the process mining data requirements and evaluated the suitability of a given tool as a data source for process mining.
Read moreProceedings of the 2015 International Conference on Software and System Process
Welcome to the International Conference on Software and Systems Process (ICSSP) held in Zurich, Switzerland, on June 2nd and 3rd, 2012. Having grown from a Software Process Workshop in 2005 to the International Conference on Software Process (ICSP) in 2007, and finally to the International Conference on Software and Systems Process (ICSSP) in 2011, this conference series has established its place in the software engineering community as a respected conference focusing on research and practice related to software and systems development process. Software and software systems development use processes as one major means for achieving and ensuring the quality of the final product. This leads to specific challenges regarding software processes such as simplicity, adaptability, standard conformance, the coordination of multiple domains and lifecycles, etc. Processes from other domains (e.g., health care, manufacturing, business, aerospace, automotive systems, and others) face similar challenges. Yet, they share interesting similarities with and differences to software processes. The question is: How can we in the software domain learn from other domains to meet our software process engineering challenges? The ICSSP conferences hence connect the traditional software and systems process community with outside views and insights, broadening its scope of software development processes to system development and explicitly including processes of other domains such as health care, business, and manufacturing. By sharing process development theories and practices from such domains, ICSSP 2012 is investigating novel solutions to today's process challenges. Correspondingly, the main theme of ICSSP 2012 is Beyond Software and Software Systems Processes, signaling our goal of learning from domains other than the traditional software process community.
Read moreA constraint-driven human resource scheduling method in software development and maintenance process
Software processes are highly people-dependent and knowledge transfer-centric compared to traditional manufacturing processes. Different people are responsible for different types of knowledge transformation according to the skill set and expertise they master. This adds a great deal of complicated factors in resolving the scheduling problem in software development and maintenance process planning. The existing human resource scheduling methods do not take into account the differences between human resource capabilities and capacities in processes execution. This paper presents a constraint-driven human resource scheduling method in software development and maintenance process. A constraint model is set up based on the software process model and human resource model. A constraint-driven scheduling method is provided to realize the optimal human resource scheduling in software development and maintenance process. The method can be used in the mature organizations whose human resources have the determinate capabilities. It provides the excellent decision support to the project manager.
Read moreKeynote on “Thirty years in software process”
The results of a 1968 study of IBM's programming process triggered little interest in IBM, but initiated my later software process studies. The IBM study lead to four main results: recognition of the software process as a feedback system, system evolution encompassed both development and maintenance, recognition of the disciplined nature of the evolution process, and formulation of three laws of software evolution. The laws reflected forces outside the direct technical process of software development and evolution, and must therefore be accepted as laws. Subsequent studies of several non-IBM, systems largely confirmed the observations. These studies also led to: development of the Software Process Evolution program classification scheme, phenomenological models of the software process, five more laws, a series of International Software Process Workshop, a Principle of Software Uncertainty and, above all, deeper understanding of the process of software evolution. The studies in 1969-84 were summarised in the book Program Evolution - Processes of Software Change by Lehman and Belady. In the 80s and early 90s, research interest in the software process was confined to a small community, focusing on process models and their formal representation and enactment. Since then, a growing interest is primarlily due to an increased concern for business process improvement, the search for disciplined methods of software process improvement, and emerging awareness of the relationship between the two. Development and successful marketing of models and procedures such as CMM and SPICE played a major role in this growth. It did not, however, generate a wider understanding of the process or how it could be improved based on that understanding. Major process improvement is difficult, since the software process is a feedback system - cf. the 1971 observation and the recent FEAST hypothesis. Following three FEAST workshops at Imperial College, the UK EPSRC supported the FEAST/1 and FEAST/2 projects in 1996 and 1999 (http://www-dse.doc.ic.ac.uk/-mml/feast/). Findings in several systems have supported the FEAST hypothesis and provided confirmation of six of the eight laws of software evolution. The FEAST work also suggested that outer loops of the total process - including influences from management, marketing and user sources - dominated system evolution trends. The long-term implications of this insight and continuing studies include practical guidelines for software evolution planning and management. They also provide basis for an initial, formal Theory of Software Process and Evolution. Such a theory will focus future process studies and guide practical application of advanced software technology.
Read moreThe Role of Machine Learning in Software Development
In today's rapidly evolving technological era, the role of machine learning in software development has become increasingly vital and influential. Machine learning has revolutionized various aspects of software development, from code analysis and optimization to prediction and decision-making. Moreover, machine learning algorithms have the potential to significantly enhance the software development process by automating repetitive tasks, improving code quality, and reducing the time and effort required for software testing and debugging. By gaining lots of data and powerful computing resources, machine learning algorithms can be able to analyse patterns and make accurate predictions about software performance, identify potential bugs or security issues, and assist in improving software design and development processes. Furthermore, machine learning can facilitate software maintenance and debugging by detecting anomalies and identifying potential causes of software failures. Albeit, using machine learning techniques into the software development process can greatly improve efficiency, productivity, and overall software quality. In this paper it is presenting the tools, techniques and the application of Machine Learning (ML) in different phases of Software Development Life Cycle (SDLC) for enhancing and improving the software development process.
Read moreIntegrating Concept Selection in a Software Development Process
Although a similarity between software and product development processes exists, concept selection is not treated as a core stage in software development whereas it is an important stage in product development. In this paper, we propose to apply concept selection methodologies in design engineering (modularized Quality Function Deployment (QFD) and perceptual concept evaluation methodologies) to software development. In particular, we demonstrate how these methods may be used for software architecture and software module concept selections. Modularized QFD matrices help software developers relate customer requirements to software requirements, and then to software module requirements. At the same time, importance of customer requirements is allocated to software requirements and then to software module requirements. These requirements and normalized worth serve as concept evaluation criteria and their weights. The proposed approach is illustrated using image search software as an example.
Read moreAligning security objectives with agile software development
Success of software development process is defined by its ability to transform the business objectives into requirements, and further into features and functionality. In addition to business objectives, software development also has security objectives requiring security engineering activities. In contrast to the iterative and incremental software development process, software security engineering is defined by sequential life cycle models: security and business objectives are thus implemented using conflicting approaches. To identify the incompatibilities between the methodologies, in this study the security engineering activities are mapped into common agile software development practises, processes and artifacts. Security engineering activities from Microsoft SDL, the ISO Common Criteria and OWASP SAMM security development lifecycle models are mapped into common agile processes, practises and artifacts. The organizational and technical aspects of the mapping are considered primarily from the point of view of achieving the security objectives set for the software engineering process: setting security requirements for design, their implementation and verification, and releasing secure software through efficient software security development process.
Read moreEvolution of software development strategies
The development of discipline-specific cognitive and meta-cognitive skills is fundamental to the successful mastery of software development skills and processes. This development happens over time and is influenced by many factors, however its understanding by teachers is crucial in order to develop activities and materials to transform students from novice to expert software engineers. In this paper, we analyse the evolution of learning strategies of novice, first year students, to expert, final year students. We analyse reflections on software development processes from students in an introductory software development course, and compare them to those of final year students, in a distributed systems development course. Our study shows that computer science - specific strategies evolve as expected, with the majority of final year students including design before coding in their software development process, but that several areas still require scaffolding activities to assist in learning development.
Read moreThe Software Process - What It Is, And HowTo Improve It
work of W. Edwards Deming has convinced industry that must first measure quality and then emphasise process to improve quality. In response to Deming's arguments and in light of perception that software industry is unable to produce quality products on schedule, and within budget, more software development organisations are now emphasising process measurement, monitoring, and assessment. This paper describes what is meant by software process and discusses an approach for its measurement and improvement. INTRODUCTION Unreliable software makes big news, from emergency services disasters to social security payment blunders. Improved software quality is essential to ensure reliable products and services, and gain customer satisfaction. While software development has existed for more than four decades, we failed so far to make as an industry and as an engineering discipline rather than craft. Developing reliable and usable software that is delivered on and within budget still represents difficult endeavour for many organisations. As role of software becomes increasingly critical for businesses as well as for human lives, problems caused by software products that are late, over budget, or that do not work, become magnified. If lives are lost or people inconvenienced due to incapable computer software, news media is there to make big stories. Organisations are realising that their fundamental problems is immaturity of their software process. Robert Lai (1993) proposes that process improvement is second maturity wave of software industry. He states that the first wave of software was developed using waterfall model in 1970's. Today we are Transactions on Information and Communications Technologies vol 8, © 1994 WIT Press, www.witpress.com, ISSN 1743-3517 216 Software Management in midst of second wave maturity movement as we attempt to formally define development process and best ways to continuously improve it (Lai 1993). Taking lead in this area has been Watts Humphrey (Humphrey 1989, 1990, 1991), and Software Engineering Institute (SEI) at Carnegie Mellon University. SEI started in 1986 to develop process maturity framework to help organisations appraise maturity of their software process, and to provide guidance for organisations to improve their software process capability. A brief description of framework was released in September 1987, including maturity questionnaire. SEI evolved model and questionnaire into 5 -Level Capability Maturity Model (CMM) in 1991. In February 1993, released CMM version 1.1 (Paulk et al 1993). This paper discusses software process and describes capability maturity model (CMM). It also shows how CMM can be used as basis to measure maturity of software process of an organisation and plan its improvement. SOFTWARE QUALITY AND PROCESS IMPROVEMENT In his book Quality is Free Phil Crosby states that: Quality is free. It is not gift, is free. What cost money are unqualify of things all actions that involve not doing jobs right first time (Crosby 1980). If such statement is true for many disciplines, is particularly true for evidence is abundant in number of software products which exceeded their budget, were produced late, failed to satisfy user requirements, and are full of bugs. demand for improved software quality is increasing to ensure reliable products and services. benefits of improved quality comes in form of reduction in failure costs. For software projects failure costs include (DTI 1992): • costs of correcting defects, both before and after delivery • overruns against and budget • unnecessary high maintenance costs • indirect costs which users incur due to poor quality software link between process maturity and software quality is expressed in premise that The quality of software system is governed by quality of process used to develop and maintain it. One stumbling block to improving software quality seems to be that not enough attention is paid to overall development process itself. While software professionals typically devote their to developing, testing or documenting software products, no one has prime responsibility for improving software process. Experience has shown that if Transactions on Information and Communications Technologies vol 8, © 1994 WIT Press, www.witpress.com, ISSN 1743-3517 Managing Systems 217 no one is working on software process, orderly improvement is unlikely. process certainly won't improve itself, rather, most likely, will deteriorate over time. Continuous improvement can occur only if process infrastructure is in place. Watts Humphrey argues in an early article published in Datamation, April 1989 that: Without work on process, there will be little or no progress in improving software. THE SOFTWARE PROCESS Adopting process view of software development represents revolutionary change in perspective. A process orientation to software development involves elements of structure, focus, measurement, ownership, skills, and supporting technology. In this section we investigate what is meant by software process. What Is Software Process According to Webster's dictionary, process is a system of operations in producing something .. series of actions, changes, or functions that achieve an end result. Chambers Concise Dictionary defines process as a series of actions or events .. sequence of operations or changes undergone. IEEE defines process as a sequence of steps performed for given purpose. In general business context, process is defined as a structured, measured set of activities designed to produce specified output for particular customer or market (Davenport 1993). These definitions put strong emphasis on HOW work is done, in contrast to product focus's emphasis on WHAT. Accordingly, process can be considered as a specific ordering of work activities across and place, with beginning, an end, and clearly identified inputs and outputs: structure for action. In this paper we will adopt following definitions quoted in (Humphrey 1990, Paulk et al 1993) are intended to encompass software throughout its life, which covers new development, enhancement, and repair. software process is The set of activities, methods, and practices used in production and evolution of software. software engineering process is The total set of software engineering activities needed to transform user's requirements into software. Transactions on Information and Communications Technologies vol 8, © 1994 WIT Press, www.witpress.com, ISSN 1743-3517 218 Software Management People and Software Process Software development is still people-intensive activity. Talented people are most important element in any software organisation. Even if you get best people available, if they do not follow common process, if everyone wrote in different programming languages, used different conventions, or didn't co-ordinate their design and code changes with their peers, results will be chaos. Successful software organisations have learned that even best professionals need structured and disciplined environment in which to do cooperative work. Software organisations that do not establish such disciplines condemn their people to endless hours of repetitively solving technically trivial problems. obvious fact is that attracting best people is vital, but is also essential to support them with an effectively managed software process. Technology and Software Process Another myth is widespread belief that some technologically advanced tool or method will provide magic answer to software crisis. This is not only wrong, but is dangerous. Organisations which jumped on bandwagon of CASE tools, and ended up in failure and wasted and effort have learned their lesson hard way. Just ask yourself before introducing technology: What do I want to automate? In absence of defined, practised, and managed process, introducing automation can lead to increased chaos. There are several factors which limit effective use of software technology: an illdefined process, inconsistent process implementation, and poor process management. Software technology cannot be fully effective until these problems have been properly addressed. Need for Defined Process If no effort is made to define and enhance software development process across whole organisation, each software development project latches on to its own tools, methods, and practices with little guidance available on how to use them. This ad hoc approach will not be sufficient to tackle task of developing complex software systems. goal of software process management is to enable organisations to produce software that meets cost, schedules, and quality objectives. principles are same that underpins statistical process control-principles that have been successfully used in controlling scientific experiments and in high -volume manufacturing operations. Statistical concepts have been found to be just as applicable to software development as they are to production of manufactured goods such as motor cars. Applying such concepts will only be possible if there is defined and managed process. Software Process Models Transactions on Information and Communications Technologies vol 8, © 1994 WIT Press, www.witpress.com, ISSN 1743-3517
Read moreEvolution of Software Development Strategies
The development of discipline-specific cognitive and meta-cognitive skills is fundamental to the successful mastery of software development skills and processes. This development happens over time and is influenced by many factors, however its understanding by teachers is crucial in order to develop activities and materials to transform students from novice to expert software engineers. In this paper, we analyse the evolution of learning strategies of novice, first year students, to expert, final year students. We analyse reflections on software development processes from students in an introductory software development course, and compare them to those of final year students, in a distributed systems development course. Our study shows that computer science - specific strategies evolve as expected, with the majority of final year students including design before coding in their software development process, but that several areas still require scaffolding activities to assist in learning development.
Read more