Implementing faceted classification for software reuse
Communications of the ACM - Special issue on software engineering
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Mainstream objects: an analysis and design approach for business
Mainstream objects: an analysis and design approach for business
Pattern languages of program design
Pattern languages of program design
Pattern languages of program design 2
Pattern languages of program design 2
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
Software reuse: architecture, process and organization for business success
Software reuse: architecture, process and organization for business success
Object-oriented software construction (2nd ed.)
Object-oriented software construction (2nd ed.)
Pattern languages of program design 3
Pattern languages of program design 3
Objects, components, and frameworks with UML: the catalysis approach
Objects, components, and frameworks with UML: the catalysis approach
Lessons learned through six years of component-based development
Communications of the ACM
Software engineering (6th ed.)
Software engineering (6th ed.)
Business Components Factory: A Comprehensive Overview of Component-Based Development for the Enterprise
Software Engineering in the Academy
Computer
Object-Oriented Software Engineering: A Use Case Driven Approach
Object-Oriented Software Engineering: A Use Case Driven Approach
A mathematical reusability model for quantifying the reduction in development effort
ACM SIGSOFT Software Engineering Notes
Hi-index | 0.00 |
This work concentrates on reuse-oriented software development. We propose an approach in which we incorporate reuse components in the initial phases of the software development process, that is to say, requirements specifications. These components, use case in the pattern form, reused during the requirements capture, allow a visualization of the system to be implemented. On the other hand, they also facilitate some normalization in the requirements process and, further, can be reused in several applications; this is obtained more easily with patterns. The primary motivation of this study derives from the fact that system requirements represent abstract knowledge of which a great part can be reused in other systems.