The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.01 - Jan.-Feb. (2013 vol.30)
pp: 16-17
Neil Maiden , City University London
ABSTRACT
Most people think of requirements as things to manipulate at the start of a project. Others, more enlightened, recognize that requirements also have a role toward the end of projects to test compliance. But few people have recognized an active role for requirements during their system's use—to monitor whether the system continues to comply with its requirements during its lifetime.
INDEX TERMS
Project design, Project management, Contracts, Systems engineering and theory, satisfaction arguments, requirements, compliance
CITATION
Neil Maiden, "Monitoring Our Requirements", IEEE Software, vol.30, no. 1, pp. 16-17, Jan.-Feb. 2013, doi:10.1109/MS.2013.10
REFERENCES
1. R. Calinescu et al., “Self-Adaptive Software Needs Quantitative Verification at Runtime,” Comm. ACM, vol. 55, no. 9, 2012, pp. 69–77.
2. W. Robinson, “A Roadmap for Comprehensive Requirements Monitoring,” Computer, May 2010, pp. 64–72.
3. J. Hammond, R. Rawlings, and A. Hall, “Will It Work?,” Proc. 5th IEEE Int'l Symp. Requirements Engineering, IEEE CS, 2001, pp. 102–109.
4. A. Vickers, “Satisfying Business Problems,” IEEE Software, vol. 24, no. 3, 2007, pp. 18–20.
14 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool