【正文】
站類的請附網址及原文 】 Requirements engineering practices A precise requirements engineering process— a main driver for successful software development — is even more important for product line engineering. Usually, the product line’s scope addresses various domains simultaneously. This makes requirements engineering more plex. Furthermore, SPL development involves more tasks than singleproduct development. Many product line requirements are plex, interlinked, and divided into mon and productspecific requirements. So, several requirements engineering practices are important specifically in SPL development: ?? Domain identification and modeling, as well as monalities and variations across product instances Separate specification and verification for platform and product requirements ?? Management of integrating future requirements into the platform and products ?? Identification, modeling, and management of requirement dependencies The first two practices are specific to SPL engineering. The latter two are mon to software development but have much higher importance for SPLs. Issues with performing these additional activities can severely affect the product line’s longterm success. During the investigation, we found that most anizations today apply anizational and procedural measures to master these chal