Excerpt
Preface Industries and marketplaces often suffer radical changes in seemingly brief periods of time. The software development industry, in all of its forms, has the opportunity to undergo such a change now. The hallmark will be a conversion from software development processes that are characterized by developing an individual system and then creating variations of it, to software development processes that create product lines and families of systems. Creating variations on individual systems takes continual investment in understanding new requirements, rand in edesign, recoding, and retesting. Creating product lines and families, on the other hand, invests in support for understanding new requirements and rapidly creating new family members with little or no redesign and recoding and with reduced retesting. Changing from the first strategy to the second means changing the software development techniques that you use and changing your organization. Fortunately, you can make changes incrementally if you know what you are trying to achieve.
We wrote this book to show you what we think your target in improving your software development process should be: a software development process focused on building families. The process we describe is based on our experience with creating software families, experience that extends back to the middle 1970s. Most recently we have seen improvements from applying family-based processes at Lucent Technologies, showing decreases in development time and costs for family members of 60%-70%. Our comparison is based on measuring the time and effort to create variations on a product before a family-based process is introduced and again after it is used.
Our intent is to identify the key ideas whose combination can radically alter the way software developers do their jobs, with attendant major gains in their productivity and in the quality of their products. By focusing software developers on building software families, these ideas can be woven into a process for software development that is much more effective than the processes in common use today. The result is a paradigm shift in software development that involves creating two new types of organizations: one devoted to defining families of programs and creating facilities needed for rapidly producing family members and a second one devoted to rapidly producing family members by using those facilities. Creation of members of a family is akin to a production process ansd is enabled by an investment in tools and processes for the entire family. The result is to make it possible to create high-quality software applications much faster than with current processes.
Most of the ideas we use-such as abstraction, separation of concerns, information hiding, formal specification, and model building-have permeated the research literature in software engineering for many years but have not been widely applied in engineering practice. A process that incorporates these ideas into a practical, family-oriented software production process was introduced at AT&T in 1992 by David Weiss; its roots can easily be traced back through 30 years of research in software engineering conducted by a variety of people. Called the Family-Oriented Abstraction, Specification, and Translation (FAST) process," it is now in use at Lucent Technologies, where its evolution is continuing. Because of its focus on producing family members, we often refer to FAST as a software production process rather than a software development process.
This book introduces the ideas that software development organizations need to know to evolve into software production organizations. Such an evolution is easiest if an organization can create for itself a software production process. Accordingly, the FAST process is really a pattern for doing so, and we think of any process that conforms to that pattern as a FAST process. Put another way, FAST processes form a family. Within Lucent we have created several members of the FAST family of processes using variations on the basic pattern as people and circumstances demand. With the help of this book we hope that you can begin to create your own FAST processes.
Planning and structuring for change is a central theme of FAST processes. It has also been a key theme in software engineering for many years. Characteristic of this theme is a continuing search for better abstractions. Finding and applying appropriate abstractions in software design and in programming languages has been a major tool for software engineers. FAST processes further develop the theme of abstraction by asking software engineers to find, for each family, abstractions that are useful in defining the family and describing its members. For each family we incorporate such abstractions into a language for specifying and modeling family members. The description of a family member in the language can be analyzed for completeness, consistency, and other properties, and, with a sufficient investment, engineers can build tools that generate the software for the family member from its description. The ability to perform each of these steps represents a further step in an organization's evolution from a software development organization to a software production organization. The ability to do all of them represents a step in the evolution of the software engineering community to use abstractions to better advantage.
As an organization evolves from software development to software production, so will its FAST processes evolve. We have started this evolution within Lucent Technologies. To understand and track our progress, we need a way of precisely describing the processes we are using and have used. Our mechanism for doing so is the Process and Artifact State Transition Abstraction (PASTA) process description method.
PASTA allows us to describe the artifacts that we use in our process, the activities that are performed during the process, the operations that we use to manipulate the artifacts, and the roles played by people during the process. It allows us to describe activities that may proceed concurrently and activities that must be performed sequentially as well as situations when backtracking may occur. A PASTA model of a process is also a good basis for developing automated support for the process.
This book contains a PASTA reference model for FAST processes. Having such models gives us a record of the evolution of FAST. The nature of PASTA and its supporting tools helps us to understand the possible effects of a change to FAST and makes it easier for us to make changes to the model. PASTA thereby facilitates changes to the FAST process. We have left certain aspects of the model incomplete because they vary considerably from one organization to another. For example, the configuration management process is usually highly specialized for an organization. We have done no more than sketch how change reporting might be handled for a family. We hope that you will use the model in this book as a starting point for creating your own reference model for your own FAST process.
We live in a time when business enterprises of all sorts appear to be undergoing continuous change. Such change usually relies on altering the processes that the enterprise uses. In manufacturing industries, the idea of redesigning product lines and processes so that a product is easy to produce using its production process is known as concurrent engineering. Both product and process are designed together. FAST and PASTA together can be viewed as concurrent engineering for software: FAST processes help software engineers to design both a family whose members are based on predicted changes and a process for producing those members based on the predictions. PASTA helps a software development organization to deploy and enact FAST as a production process, providing a way to create guidebooks and toolsets to support the process.
A variety of industries have adopted the notion of continuous change in the interest of gaining a competitive advantage-namely, to be able to produce customized products rapidly. The software development industry is no different. Competitive demands are pushing software developers to create products in greater variety faster than ever before. FAST is designed to help software engineers respond to this trend and, by appropriate investment and planning, to take advantage of it.