Formalizing the transition from requirements’ change to design change using an evolutionary traceability model
- 24 April 2014
- journal article
- Published by Springer Nature in Innovations in Systems and Software Engineering
- Vol. 10 (3) , 181-202
Abstract
No abstract availableKeywords
This publication has 40 references indexed in Scilit:
- Test Case Design Using Slicing of UML Interaction DiagramProcedia Technology, 2012
- Architecture Normalization for Component-based SystemsElectronic Notes in Theoretical Computer Science, 2006
- Change impact analysis to support architectural evolutionJournal of Software Maintenance and Evolution: Research and Practice, 2002
- ARCHITECTURE-LEVEL DEPENDENCE ANALYSIS FOR SOFTWARE SYSTEMSInternational Journal of Software Engineering and Knowledge Engineering, 2001
- Types of software evolution and software maintenanceJournal of Software Maintenance and Evolution: Research and Practice, 2001
- Achieving convergence, causality preservation, and intention preservation in real-time cooperative editing systemsACM Transactions on Computer-Human Interaction, 1998
- DSSA (Domain-Specific Software Architecture)ACM SIGSOFT Software Engineering Notes, 1995
- Specification and analysis of system architecture using RapideIEEE Transactions on Software Engineering, 1995
- Abstractions for software architecture and tools to support themIEEE Transactions on Software Engineering, 1995
- Using program slicing in software maintenanceIEEE Transactions on Software Engineering, 1991