Object Oriented Reengineering Patterns
Object Oriented Reengineering Patterns
The 4+1 View Model of Architecture
IEEE Software
Guest Editors' Introduction: Global Software Development
IEEE Software
Risks Involved in Reengineering Projects
WCRE '99 Proceedings of the Sixth Working Conference on Reverse Engineering
Reverse Engineering Tools as Media for Imperfect Knowledge
WCRE '00 Proceedings of the Seventh Working Conference on Reverse Engineering (WCRE'00)
An Empirical Study of Speed and Communication in Globally Distributed Software Development
IEEE Transactions on Software Engineering
| Hi-index | 0.00 |
In order to quicken the building of large business system, the design of the system and modules are always implemented in an evolving model, but there are many requirement changes in evolving software development, and the consistency of t requirement comprehension should be ensured so as to fulfill the enhanced business request correctly and appropriately. When all the design work is collocated together, the stockholders may have regular face-to-face meetings to transfer business requests, business knowledge and the specification, and to verify whether the design is coherent with the original request. Unfortunately, such regular meetings are costly in global cooperative software design due to the time zone difference, language and culture barrier, and the travel expenditure. Furthermore, the cost for the regular face-to-face meetings turn out to be unaffordable in evolving global cooperative software design because the business requirement transition is more frequent and lasts longer. On the basis of Kruchten's "4+1" view model, the author propose a central layered knowledge management framework to facilitate the requirement comprehension and to reduce the possible requirement conflicts among different business units and different releases. The case study shows a drastic decrease of requirement defects and efforts demands.