Use of Architecture Description to Maintain Consistency in Agile Processes

Aurélien Chichignoud, Florian Noyrit, Laurent Maillet-Contoz, François Terrier

Abstract

The development of highly complex products requires the maintenance of a huge set of inter-dependent documents, in various formats, developed concurrently according to agile methods. Unfortunately, no tool or methodology is available today to systematically maintain consistency between all these documents. Therefore, according to observations made in STMicroelectronics, when a document changes, stakeholders must manually propagate the changes to the impacted set of dependent documents. For various reasons, they may not well propagate the change, or even may not propagate it at all. Related documents thereby diverge more and more over time. This is a source of bugs that are difficult to identify and fix; potentially jeopardizing product reliability and quality. This paper proposes a methodology to help stakeholders to systematically maintain consistency between documents, based on the Architecture Description concept introduced by ISO42010. First, a model is defined to describe completely correspondences between Architecture Description Elements of documents. This model is designed to be independent of documents formats, selected system development lifecycle and the working methods of the industry. Second, these correspondences are analyzed in case of document modification in order to help stakeholders maintaining corpus consistency. A tool has been prototyped to evaluate the approach.

References

  1. Avanthi, R., Sreenivasan, P., 2010. Managing requirements across analysis and design phases using IBM rational system architect & IBM rational DOORS. Technical report, IBM.
  2. Beck, K., Beedle, M., Van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., others, 2001. Manifesto for agile software development.
  3. Bézivin, J., Paige, R.F., smann, U.A., Rumpe, B., Schmidt, D., 2014. Manifesto - Model Engineering for Complex Systems. CoRR abs/1409.6591.
  4. Birman, K., Joseph, T., 1987. Exploiting virtual synchrony in distributed systems. ACM.
  5. Blanc, X., Mounier, I., Mougenot, A., Mens, T., 2008. Detecting model inconsistency through operationbased model construction, in: Software Engineering, 2008. ICSE'08. ACM/IEEE 30th International Conference on. IEEE, pp. 511-520.
  6. Cleland-Huang, J., Chang, C.K., Christensen, M., 2003. Event-based traceability for managing evolutionary change. Softw. Eng. IEEE Trans. On 29, 796-810.
  7. Dejours, C., Dessors, D., Molinier, P., 1994. Comprendre la résistance au changement. Doc. Médecin Trav. 58, 112-117.
  8. Egyed, A., 2011. Automatically detecting and tracking inconsistencies in software design models. Softw. Eng. IEEE Trans. On 37, 188-204.
  9. Girba, T., Kuhn, A., Seeberger, M., Ducasse, S., 2005. How developers drive software evolution, in: Principles of Software Evolution, Eighth International Workshop on. IEEE, pp. 113-122.
  10. IEEE Recommended Practice for Architectural Description of Software-Intensive Systems, 2000. . IEEE Std 1471- 2000 i-23. doi:10.1109/IEEESTD.2000.91944.
  11. ISO/IEC/IEEE Systems and software engineering - Architecture description, 2011. doi:10.1109/IEEESTD.2011.6129467.
  12. Kitchenham, B., 2004. Procedures for performing systematic reviews. Keele UK Keele Univ. 33, 1-26.
  13. Leachman, R.C., Ding, S., 2007. Integration of speed economics into decision-making for manufacturing management. Int. J. Prod. Econ. 107, 39-55.
  14. Mäder, P., Philippow, I., Riebisch, M., 2007. Customizing traceability links for the unified process, in: International Conference on the Quality of Software Architectures. Springer, pp. 53-71.
  15. Nentwich, C., 2005. Managing the consistency of distributed documents. University of London.
  16. Skaf-Molli, H., Naja-Jazzar, H., Molli, P., 2006. Inconsistency of xml documents during cooperative editing.
  17. Systèmes, D., 2013. Reqtify-Dassault Systèmes. www.reqtify.com/.
  18. Turk, D., France, R., Rumpe, B., 2014. Limitations of agile software processes. ArXiv Prepr. ArXiv14096600.
Download


Paper Citation


in Harvard Style

Chichignoud A., Noyrit F., Maillet-Contoz L. and Terrier F. (2017). Use of Architecture Description to Maintain Consistency in Agile Processes . In Proceedings of the 5th International Conference on Model-Driven Engineering and Software Development - Volume 1: MODELSWARD, ISBN 978-989-758-210-3, pages 459-466. DOI: 10.5220/0006207804590466


in Bibtex Style

@conference{modelsward17,
author={Aurélien Chichignoud and Florian Noyrit and Laurent Maillet-Contoz and François Terrier},
title={Use of Architecture Description to Maintain Consistency in Agile Processes},
booktitle={Proceedings of the 5th International Conference on Model-Driven Engineering and Software Development - Volume 1: MODELSWARD,},
year={2017},
pages={459-466},
publisher={SciTePress},
organization={INSTICC},
doi={10.5220/0006207804590466},
isbn={978-989-758-210-3},
}


in EndNote Style

TY - CONF
JO - Proceedings of the 5th International Conference on Model-Driven Engineering and Software Development - Volume 1: MODELSWARD,
TI - Use of Architecture Description to Maintain Consistency in Agile Processes
SN - 978-989-758-210-3
AU - Chichignoud A.
AU - Noyrit F.
AU - Maillet-Contoz L.
AU - Terrier F.
PY - 2017
SP - 459
EP - 466
DO - 10.5220/0006207804590466