Software product-line engineering can provide significant gains inquality and productivity through systematic reuse of software'sconceptual structures. For embedded safety- or mission-critical systems,much of the development effort goes into understanding, specifying, andvalidating the requirements. If developers can reuse rather than re-dorequirements for families of similar systems, we can improveproductivity while significantly reducing the opportunity forrequirements errors. The paper describes a systematic approach todeveloping a Product-line Requirements Specification (PRS) for suchsystems. The PRS explicitly represents the family's common requirementsas well as the allowed variations that distinguish family members. Whencompleted, the PRS definition also supports generation of well-formedsoftware requirements specifications (SRS) for members of the productline. We describe a process for developing a PRS starting from ananalysis of a program family's commonalities and variabilities. Theapproach is illustrated with examples from a case study of a real familyof systems, the Rockwell Collins Commercial Flight Control Systemproduct-line
展开▼
