Behavior Engineering Based Software Change Case Studies |
|
|
Software ChangeAbstractThe ideal we seek when responding to a change in the functional requirements for a system is that we can quickly determine (1) where to make the change (2) how the change affects the architecture of the existing system (3) which components of the system are affected by the change (4) and, what behavioral changes will need to be made to the components (and their interfaces) that are affected by the change. Because a system is likely to undergo many changes over time, there is also need to record, manage and optimize the impact of such evolutionary changes. A traceability model, which uses behavior trees as a formal notation to represent functional requirements, is proposed to reveal change impacts on different types of design constructs (documents) caused by the functional requirements changes. This model introduces the concept of evolutionary design documents that record the change history of the design. From these documents, any version of a design document as well as the difference between any two versions can be retrieved. An important advantage of this model is that the major part of the procedure to generate these evolutionary design documents from the different versions of functional requirements can be performed by automated tools. Read more details, please download the paper Formalizing the Transition from Requirements Change to Design Change. To know the most recent result, please contact Dr. Larry Wen |