Software Product-Line Engineering: A Family-Based Software Development Process / Edition 1

Paperback (Print)
Used and New from Other Sellers
Used and New from Other Sellers
from $1.99
Usually ships in 1-2 business days
(Save 96%)
Other sellers (Paperback)
  • All (11) from $1.99   
  • New (6) from $38.67   
  • Used (5) from $1.99   

Overview

It is in the "how to do it" part that this book excels, because it illustrates a process that has been successfully applied to reduce costs for organizations that develop large programming systems. With the help of this book, many more can learn how to exploit the idea of program families and bring about a substantial improvement in the state of practice in the software industry.
--David Lorge Parnas

Many organizations have mastered the practice of software development, yet few have become truly efficient at software production. With the adoption of an efficient, systematic software production method, organizations can gain significant competitive advantages, including reduced time to market, better schedule predictability, more reliable code, and decreased costs. Software Product-Line Engineering provides the actionable information and proven tactics necessary to effect organizational change and make your future software projects more successful.

The authors outline a systematic method for rapid software production through the FAST (Family-Oriented Abstraction, Specification, and Translation) process, a revolutionary commercial product developed at AT&T that continues to evolve at Lucent Technologies. FAST uses practical domain engineering to decrease the time and effort necessary to develop, deliver, and maintain software. Any software development projects currently using C, C++, or Java can easily incorporate the FAST model and quickly reap the benefits of a more efficient software methodology.

0201694387B04062001

Read More Show Less

Editorial Reviews

Booknews
The authors outline a systematic method for rapid software production through the family-oriented abstraction, specification, and translation (FAST) process. FAST uses practical domain engineering to decrease the time and effort necessary to develop, deliver, and maintain software. Any software development projects using C, C++, or Java can incorporate the FAST model. The CD-ROM contains a FAST PASTA browser and a simulator for a floating weather station. Annotation c. Book News, Inc., Portland, OR (booknews.com)
Read More Show Less

Product Details

  • ISBN-13: 9780201694383
  • Publisher: Addison-Wesley
  • Publication date: 8/4/1999
  • Edition description: BK&CD ROM
  • Edition number: 1
  • Pages: 448
  • Product dimensions: 7.49 (w) x 8.98 (h) x 0.91 (d)

Meet the Author

David M. Weiss is the Director of the Software Production Research Department at Avaya Laboratories. His technical work has evolved into the invention of processes that incorporate ideas from families, design for change, measurement, precise specification, and technology transfer. The result has been a software production process based on family-oriented abstraction, specification, and translation, known as FAST.

Chi Tau Robert Lai is founder of the International Software Process Constellation, Inc., which is an industry leader in process engineering and software automation.

Read More Show Less

Read an Excerpt

Industries and marketplaces often suffer radical changes in seemingly brief periods of time. The software development industry, in all 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 develop-ing 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, and in redesign, recoding, and retesting. Creating product lines and families, on the other hand, invests in support for understanding new requirements and rapidly cre-ating 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 both 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 soft-ware 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%n70%. 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 productiv-ity 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 and is enabled by an investment in tools and pro-cesses 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 useosuch as abstraction, separation of concerns, information hiding, formal specification, and model buildingohave permeated the research lit-erature 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 appropri-ate 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 organiza-tionis 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 pro-cesses 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 sup-porting tools help us to understand the possible effects of a change to FAST and make 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 configu-ration management process is usually highly specialized for an organization.1 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.

1. See R. E. Grinter, "Recomposition: Putting It All Back Together Again," ACM Conference on Computer Supported Cooperative Work (CSCW '98) (Seattle: November 14-18, 1998), for an interesting view of how configuration management varies among software development organizations. Acknowledgments

This book was in the planning, creating, and re-creating process for an agonizingly long time. We thank our wives—Joanne Glazer Weiss and Ya Chien Chuang—for their patience and willingness to delay other projects in favor of the book. We also thank Deborah Lafferty for her patience and encouragement through many missed deadlines. Many people helped to shape the ideas that underlie FAST and PASTA and worked to polish them enough so that they were ready for use. Prominent among them are David Parnas, Grady Campbell, Stuart Faulk, Rich McCabe, James Kirby, Jr., James O. Coplien, Omer Aiken, and Steve Yau. We would never have had the con-fidence to write this book without the assistance and support of many people who were willing to experiment with FAST and PASTA and who helped to shape them into their current working form. Prominent among these people are David Cuka, Mark Ardis, Lloyd Nakatani, Bob Olsen, Lynn Paulter, Paul Pontrelli, Doug Stoneman, Richard Braatz, Lizette Velazquez, Jan Sharpless, Ivy Mackowiak, Steven Nolle, Carl Chang, Wei Tek Tsai, Tom Case, Ken D. Shere, Lina-Na Hwa, Martha Lin, Chu-San Sam Shen, C. W. Chen, Ya-Chien Chuang, and Herman Chuan-Ming Hsiung. Art Pyster, Eric Sumner, Jan Sharpless, and Mary Zajac provided management support and encouragement. Deserving of special mention are David Cuka, who did much of the development work on the SPEC example and who has been an early and tireless advocate of FAST within Lucent, and Dan Hoffman, who did much of the develop-ment work on the Floating Weather Station example. James O. Coplien occupies a special niche in our thoughts, first for his encouragement to us to write this book and second for his explorations of the ideas of commonality and variability and how to use them to create a multiparadigm approach to software development. These explorations are captured in his own book, which we commend to your attention. Special thanks to Tina Murthy for helping to create the FAST PASTA model and to Ching-Peng Chu, Chung Hong Chien, Ting-Shun Cuang, Jimmy Truong, Tong-Gao Tang, and Wei-Li Johnson Liu for helping to implement the PASTA toolset, which we used to create the FAST PASTA model. Joanne Glazer Weiss helped with the tedious task of verifying table formats.

David dedicates this book to Jack and Bertha Weiss. Robert dedicates this book to Tsung-Yen and Chiu-Lan Lai. David Weiss Lucent Technologies Naperville, IL

Chi Tau Robert Lai International Software Process Constellation Reston, VA

Read More Show Less

Table of Contents

(Each chapter concludes with a Summary, Nomenclature Introduced, and Readings.

Foreword.

Preface.

1. Introduction: The Need for Families.

The Dilemma of Careful Engineering and Rapid Production.

Problems FAST Addresses.

Applications of FAST.

Benefits of FAST.

What Can Readers Expect?

2. Family-Oriented Software Production.

Basic Assumptions.

FAST Strategies.

Foundations for Engineering Families.

The Role of Abstractions in Identifying and Designing Families.

The Role of Information Hiding and Separation of Concerns.

Predicting Change.

Organizational Considerations.

3. AN EXAMPLE: FAST Applied to Commands and Reports.

The Commands and Reports Family.

Defining the C&R Family.

Using the C&R Application Engineering Environment.

The SPEC Language and Its Translators.

Designing the Translators.

4. An Overview of FAST.

The Structure of FAST.

The Economics of FAST.

Case 1: No Domain Engineering.

Case 2: Domain Engineering.

The Fundamental Law of Family Production.

Risk Versus Automation.

Application Engineering.

Application Engineering Artifacts.

Application Production Activities.

Domain Engineering.

Domain Engineering Artifacts.

Domain Engineering Activities.

Organizational Roles.

Variability in the FAST Process.

5. AN EXAMPLE: The Floating Weather Station Family.

The Floating Weather Station Family.

Qualify the FWS Domain.

Engineer the FWS Domain.

Analyze the FWS Domain.

Implement the FWS Domain.

Addendum A: The Floating Weather Station Commonality Analysis.

Introduction.

Overview.

Dictionary of Terms.

Commonalities.

Variabilities.

Parameters of Variation.

Issues.

Message Formats.

Sensor Driver Identifiers.

Addendum B: The Floating Weather Station Module Guide.

Behavior-Hiding Modules.

Device Interface Modules.

Software-Design-Hiding Modules.

Issues.

Addendum C: The Floating Weather Station Application Generation Environment.

Family Member Generator.

Addendum D: A Generated Floating Weather Station Family Member.

Addendum E: The Floating Weather Station Environment Simulator.

6. Process Modeling.

Motivations for Process Modeling.

A PASTA Model as a Communications Medium.

Elements of a PASTA Model.

Process Activities as State Machines.

Artifacts as State Machines.

Prescribing the Order of Events.

Prescribing a Methodology.

The Role of Process Modeling in FAST.

PASTA Abstractions

Creating PASTA Process Models.

The Process User’s Concerns.

PASTA Models as Used by Process Environment Developers.

Process Measurement Using PASTA.

Measuring a Process Model.

Measuring Process Performance.

7. Representing a PASTA Model.

Representations of PASTA Elements.

PASTA Forms.

Notational Considerations.

Artifact Definition Form.

A-State Machine Diagrams.

Process State Definition Form.

P-State Machines.

Relation Definition Form.

Role Definition Form.

Operation Definition Form.

Analysis Definition Form.

8. An Overview of the FAST PASTA Model.

FAST Model Hierarchies.

FAST Artifacts.

Environment Artifacts.

Application Artifacts.

Change_Report.

FAST Activities.

Qualify_Domain

Engineer_Domain.

Implement_Domain.

Engineer_Application.

Manage_Project.

Change_Family.

FAST Roles.

FAST Manager.

Gluing the Elements Together: The State Transition Diagrams.

Typical Questions Answered by the Model.

First Steps in Applying the Model.

Identifying Starting Activities and Roles.

Other Scenarios.

9. Artifact Definitions.

Family_Artifact.

Environment.

Domain_Model.

Domain_Implementation.

Application.

Application_Model.

Application_Documentation.

Application_Code.

Change_Report.

10. Activity Definitions.

FAST.

Qualify_Domain.

Gather_Data.

Analyze_Data.

Reject.

Accept.

Engineer_Domain.

Analyze_Domain.

Implement_Domain.

Engineer_Application.

Model Application.

Produce_Application.

Delivery_And_Operation_Support.

Manage_Project.

Change_Family.

Request_Family_Change.

Evaluate_Implementation_Change.

Evaluate_Domain_Change.

Library_Activities

Review_Internally.

Review.

Iterate_Or_Refine.

11. Role Definitions.

Project_Manager.

Domain_Manager.

12. FAST Analyses.

Application_Engineering_Process_To_Decision_Trace_Analysis.

Application_Engineering_Process_To_Tool_Trace_Analysis.

Application_Engineering_Support_Analysis.

Application_Modeling_Language_Editor_Assurance_Analysis.

Application_Modeling_Language_Parser_Assurance_Analysis.

Application_Modeling_Language_To_Family_Design_Trace_Analysis.

Artifact_Implementation_Assurance_Analysis.

Commonality_To_Module_Trace_Analysis.

Composition_Mapping_To_Family_Design.

Composition_Mapping_To_Language_Construct_Mapping_Analysis.

Composition_Mapping_To_Module_Trace_Analysis.

Customer_Satisfaction.

Decision_To_Tool_Trace_Analysis.

Defect_Analysis.

Final_Product_Documentation_Assurance_Analysis.

Final_Product_Validation_Analysis.

Module_Documentation_Assurance_Analysis.

Module_Implementation_Assurance_Analysis.

Parameter_Of_Variation_To_Decision_Trace_Analysis.

Parameter_Of_Variation_To_Language_Trace_Analysis.

Parameter_Of_Variation_To_Module_Trace_Analysis.

Progress_Analysis.

Resource_Analysis.

Risk_Analysis.

Terminology_Analysis.

Tool_Documentation_Assurance_Analysis.

Tool_Implementation_Assurance_Analysis.

Variability_To_Variation_Parameter_Trace_Analysis.

Variation_Parameter_To_Variability_Trace_Analysis.

13. FAST Relations.

Application_Model_Module.

Commonality_Module.

Composition_Mapping_AML.

Decision_Process.

Decision_Tool.

Module_Document.

Module_Implement.

Parameter_Decision.

Parameter_Module.

Product_Document.

Tool_Document.

Tool_Implement

Variability_Parameter.

Patterns of Thought and Work.

FAST and Reuse.

FAST as a Multiparadigm Process.

FAST and Object Orientation.

Applicability of FAST.

Finding Domains Where FAST Is Worth Applying.

The Single-Customer, Single-Product-Family Situation.

The Many-Customers, Single-Product-Family Situation.

The Many-Customers, Many-Product-Families Situation.

Applying FAST Incrementally.

Patterns of a FAST Organization.

Applying PASTA.

Transitioning to a FAST Process.

Glossary.

Bibliography.

Index. 0201694387T04062001

Read More Show Less

Preface

Industries and marketplaces often suffer radical changes in seemingly brief periods of time. The software development industry, in all 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 develop-ing 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, and in redesign, recoding, and retesting. Creating product lines and families, on the other hand, invests in support for understanding new requirements and rapidly cre-ating 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 both 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 soft-ware 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%n70%. 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 productiv-ity 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 and is enabled by an investment in tools and pro-cesses 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 useosuch as abstraction, separation of concerns, information hiding, formal specification, and model buildingohave permeated the research lit-erature 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 appropri-ate 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 organiza-tionis 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 pro-cesses 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 sup-porting tools help us to understand the possible effects of a change to FAST and make 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 configu-ration management process is usually highly specialized for an organization.1 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.

1. See R. E. Grinter, "Recomposition: Putting It All Back Together Again," ACM Conference on Computer Supported Cooperative Work (CSCW '98) (Seattle: November 14-18, 1998), for an interesting view of how configuration management varies among software development organizations.

Acknowledgments

This book was in the planning, creating, and re-creating process for an agonizingly long time. We thank our wives--Joanne Glazer Weiss and Ya Chien Chuang--for their patience and willingness to delay other projects in favor of the book. We also thank Deborah Lafferty for her patience and encouragement through many missed deadlines. Many people helped to shape the ideas that underlie FAST and PASTA and worked to polish them enough so that they were ready for use. Prominent among them are David Parnas, Grady Campbell, Stuart Faulk, Rich McCabe, James Kirby, Jr., James O. Coplien, Omer Aiken, and Steve Yau. We would never have had the con-fidence to write this book without the assistance and support of many people who were willing to experiment with FAST and PASTA and who helped to shape them into their current working form. Prominent among these people are David Cuka, Mark Ardis, Lloyd Nakatani, Bob Olsen, Lynn Paulter, Paul Pontrelli, Doug Stoneman, Richard Braatz, Lizette Velazquez, Jan Sharpless, Ivy Mackowiak, Steven Nolle, Carl Chang, Wei Tek Tsai, Tom Case, Ken D. Shere, Lina-Na Hwa, Martha Lin, Chu-San Sam Shen, C. W. Chen, Ya-Chien Chuang, and Herman Chuan-Ming Hsiung. Art Pyster, Eric Sumner, Jan Sharpless, and Mary Zajac provided management support and encouragement. Deserving of special mention are David Cuka, who did much of the development work on the SPEC example and who has been an early and tireless advocate of FAST within Lucent, and Dan Hoffman, who did much of the develop-ment work on the Floating Weather Station example. James O. Coplien occupies a special niche in our thoughts, first for his encouragement to us to write this book and second for his explorations of the ideas of commonality and variability and how to use them to create a multiparadigm approach to software development. These explorations are captured in his own book, which we commend to your attention. Special thanks to Tina Murthy for helping to create the FAST PASTA model and to Ching-Peng Chu, Chung Hong Chien, Ting-Shun Cuang, Jimmy Truong, Tong-Gao Tang, and Wei-Li Johnson Liu for helping to implement the PASTA toolset, which we used to create the FAST PASTA model. Joanne Glazer Weiss helped with the tedious task of verifying table formats.

David dedicates this book to Jack and Bertha Weiss.
Robert dedicates this book to Tsung-Yen and Chiu-Lan Lai.
David Weiss
Lucent Technologies
Naperville, IL

Chi Tau Robert Lai
International Software Process Constellation
Reston, VA

0201694387P04062001

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)