|
|
|
Pushing requirements changes through to changes
in specifications |
| LIN Lan, POORE Jesse |
| Department of Electrical Engineering and Computer Science, University of Tennessee |
|
|
|
|
Abstract Requirements changes can occur both during and after a phase of development for a variety of reasons, including error correction and feature changes. It is difficult and intensive work to integrate requirements changes made after specification is completed. Sequence-based specification was developed to convert ordinary functional software requirements into complete, consistent, and traceably correct specifications through a constructive process. Algorithms for managing requirements changes meet a very great need in field application of the sequence-based specification method. In this paper we propose to capture requirements changes as a series of atomic changes in specifications, and present polynomial-time algorithms for managing these changes. The algorithms are built into the tool support with which users are able to push requirements changes through to changes in specifications, maintain old specifications over time and evolve them into new specifications with the least amount of human interaction and rework. All our change algorithms are supported by rigorous mathematical formulation and proof of correctness. The application example is a safe controller.
|
|
Issue Date: 05 December 2008
|
|
| 1 |
Prowell S J, Poore J H . Sequence-based software specificationof deterministic systems. Software –Practice and Experience, 1998, 28(3): 329–344.
doi:10.1002/(SICI)1097-024X(199803)28:3<329::AID-SPE157>3.0.CO;2-H
|
| 2 |
Prowell S J, Poore J H . Foundations of sequence-basedsoftware specification. IEEE Transactionson Software Engineering, 2003, 29(5): 417–429.
doi:10.1109/TSE.2003.1199071
|
| 3 |
Mills H D . The new math of computer programming. Communications of the ACM, 1975, 18(1): 43–48.
doi:10.1145/360569.360659
|
| 4 |
Mills H D . Stepwise refinement and verification in box-structured systems. IEEE Computer, 1988, 21(6): 23–36
|
| 5 |
Prowell S J, Trammell C J, Linger R C, et al.. Cleanroom Software Engineering: Technology andProcess. Addison-Wesley-Longman, 1999
|
| 6 |
Bauer T, Beletski T, Boehr F, et al.. From requirements to automated testing of quasaraussenspiegeleinstellung. Technical Report007.07E, Fraunhofer Institute for Experimental Engineering, 2007
|
| 7 |
Lin L . Managementof Requirements Changes in Sequence-Based Software Specifications. Dissertation for the Doctoral Degree. Universityof Tennessee, 2006 . http://sqrl.cs.utk.edu/btw/files/lin.pdf
|
| 8 |
Hopcroft J E, Ullman J D . Introduction to AutomataTheory, Languages, and Computation. Addison-Wesley, 1979
|
| 9 |
Lin L, Prowell S J, Poore J H . Management of requirements changes in sequence-basedspecifications. Technical Report ut-cs-07-588,University of Tennessee, 2007
|
| 10 |
Buren J, Cook D . Experiences in the adoptionof requirements engineering technologies. Crosstalk: The Journal of Defense Software Engineering, 1998, December : 3–10
|
| 11 |
Davis A . SoftwareRequirements: Analysis and Specification. Prentice-Hall, 1989
|
| 12 |
Harker S, Eason K, Dobson J . The change and evolution of requirements as a challengeto the practice of software engineering. In: Proceedings of the IEEE International Symposium on Requirements Engineering, 1993, 266–272
|
| 13 |
Jones C . Strategiesfor managing requirements creep. IEEE Computer, 1996, 29(6): 92–94
|
| 14 |
Lavazza L, Valetto G . Enhancing requirements andchange management through process modeling and measurement. In: Proceedings of the Fourth International Conferenceon Requirements Engineering, 2000, 106–115
|
| 15 |
Nurmuliani N, Zowghi D, Williams S . Requirements volatility and its impact on change effort:Evidence-based research in software development projects. In: Proceedings of the Eleventh Australian Workshopon Requirements Engineering, 2006
|
| 16 |
Kobayashi A, Maekawa M . Need-based requirements changemanagement. In: Proceedings of the EighthAnnual IEEE International Conference and Workshop on Engineering ofComputer-Based Systems, 2001, 171–178
|
| 17 |
Ajila S . Softwaremaintenance: An approach to impact analysis of objects change. Software – Practice and Experience, 1995, 25(10): 1155–1181.
doi:10.1002/spe.4380251006
|
| 18 |
Lee M, Offutt A, Alexander R . Algorithmic analysis of the impacts of changes to object-orientedsoftware. In: Proceedings of the Thirty-FourthInternational Conference on Technology of Object-Oriented Languagesand Systems, 2000, 61–70
|
| 19 |
Moriconi M, Winkley T . Approximate reasoning aboutthe effects of program changes. IEEE Transactionson Software Engineering, 1990, 16(9): 980–992.
doi:10.1109/32.58785
|
| 20 |
Ren X, Barbara G, Maximilian S, et al.. Chianti: A change impact analysis tool for Javaprograms. In: Proceedings of the Twenty-SeventhInternational Conference on Software Engineering, 2005, 61–70
|
| 21 |
Lock S, Kotonya G . An integrated, probabilisticframework for requirements change impact analysis. Australian Journal of Information Systems, 1999, 6(2): 38–63
|
| 22 |
Korel B, Tahat L H . Understanding modificationsin state-based models. In: Proceedingsof the Twelfth IEEE International Workshop on Program Comprehension.IEEE Computer Society Press, 2004 .
|
| 23 |
Seawright A, Brewer F . Clairvoyant: A synthesissystem for production-based specification. IEEE Transactions on VLSI Systems, 1994, 2(2): 172–185.
doi:10.1109/92.285744
|
|
Viewed |
|
|
|
Full text
|
|
|
|
|
Abstract
|
|
|
|
|
Cited |
|
|
|
|
| |
Shared |
|
|
|
|
| |
Discussed |
|
|
|
|
