Abstract
Software architecture always exists in the target system although agile methodology (AM) weakens the design documents of the software architecture, and it will be improved continually as iteration process. The changes of business process and customer requirements should be dealt with in time. Therefore, it is essential that the stages of architecture evolution are explored in each release plan. The main hierarchy of architecture evolution is shown, the relationship between user stories and components is presented, and a method to support architecture evolution is given.
Full Text
Published Version
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call