Creating system designs that efficiently satisfy an evolving set of needs is critical for improving program lifecycle properties such as cost, development time, and risk; properties that are often in conflict with near-term system requirements. This paper proposes that system evolution can be viewed as a family of sequentially developed systems and that existing work in the platforming domain serves as a useful foundation.
Members-Only Content
This content is restricted to members only.
You must be logged in with an active membership to access this page.
Please click the link below to log in. If you do not have an account or your membership is inactive, you may need to register or renew it.