Domain Model Driven Approach to Change Impact Assessment

Information system development is a highly iterative process in which developers seek to capture the needs and desires of all stakeholders. The goal is to transform the requirements into a complete system consisting of both manual and computerized parts. The product of such a development project undergoes changes because of its iterative nature. Extensive attention is given to traceability as a means to relate different different system descriptions and to allow changes in one of the system descriptions — requirements specification, design, code, documentation, or test scenarios — to be predicted and traced to the corresponding fragments of the other descriptions.1 Such correspondence relationships should be maintained throughout the lifetime of a system in order to manage the artifact.

[1]  Nenad Medvidovic,et al.  Reconciling software requirements and architectures: the CBSP approach , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[2]  Joseph A. Goguen,et al.  An Object-Oriented Tool for Tracing Requirements , 1996, IEEE Softw..

[3]  Jon Atle Gulla,et al.  Natural Language Analysis for Semantic Document Modeling , 2000, NLDB.

[4]  Sol J. Greenspan,et al.  Structuring software development for reliability , 1978 .

[5]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[6]  Judea Pearl,et al.  Probabilistic reasoning in intelligent systems - networks of plausible inference , 1991, Morgan Kaufmann series in representation and reasoning.

[7]  Klaus Pohl,et al.  Integrating Requirement and Architecture Information: A Scenario and Meta-Model Based Approach , 2001 .

[8]  Steven P. Levitan,et al.  Linking requirements and design data for automated functional evaluation , 1996 .

[9]  Babak A. Farshchian,et al.  A Framework for Supporting Shared Interaction in Distributed Product Development Projects , 2001 .

[10]  Mark Neal,et al.  Why and how of requirements tracing , 1994, IEEE Software.

[11]  Patricio Letelier.  A Framework for Requirements Traceability in UML-based Projects , 2002 .

[12]  Klaus Pohl,et al.  PRO-ART: enabling requirements pre-traceability , 1996, Proceedings of the Second International Conference on Requirements Engineering.