Object oriented design with applications
Object oriented design with applications
Lessons from the design of the Eiffel libraries
Communications of the ACM
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Software engineering (5th ed.)
Software engineering (5th ed.)
Subject-oriented composition rules
Proceedings of the tenth annual conference on Object-oriented programming systems, languages, and applications
IEEE Transactions on Software Engineering - Special issue on formal methods in software practice
Using application understanding to support impact analysis
Journal of Software Maintenance: Research and Practice
XML specification guide
Software Quality Management and ISO 9001: How to Make Them Work for You
Software Quality Management and ISO 9001: How to Make Them Work for You
C#: How to Program
XML Seen as Integral to Application Integration
IT Professional
A Reference Model for Requirements and Specifications
IEEE Software
Software Reflexion Models: Bridging the Gap between Design and Implementation
IEEE Transactions on Software Engineering
A Framework for Source Code Search Using Program Patterns
IEEE Transactions on Software Engineering
The Impact Analysis Task in Software Maintenance: A Model and a Case Study
ICSM '94 Proceedings of the International Conference on Software Maintenance
Enabling Automated Analysis through the Formalization of Object-Oriented Modeling Diagrams
DSN '00 Proceedings of the 2000 International Conference on Dependable Systems and Networks (formerly FTCS-30 and DCCA-8)
Reengineering Legacy Applications using Design Patterns
STEP '97 Proceedings of the 8th International Workshop on Software Technology and Engineering Practice (STEP '97) (including CASE '97)
An Integrated Software Development Environment with XML Internal Representation
COMPSAC '04 Proceedings of the 28th Annual International Computer Software and Applications Conference - Volume 01
Journal of Systems and Software
Hi-index | 0.00 |
Many disparate software analysis/design methods and tools (called paradigms in this paper) individually offer faster and more efficient software design/evolution, yet they are generally partially incompatible. Therefore, when they are used together, they suffer from a lack of communication and integration. Unanticipated and inadvertent inconsistencies arising from the implicit incompatibilities result in significantly increased costs and errors during software maintenance. To improve both software evolution and maintenance, we propose an XML-based model that effectively unifies and integrates current software paradigms while helping reduce ripple effects and related software maintenance difficulties.