Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Exploiting style in architectural design environments
SIGSOFT '94 Proceedings of the 2nd ACM SIGSOFT symposium on Foundations of software engineering
Abstractions for Software Architecture and Tools to Support Them
IEEE Transactions on Software Engineering - Special issue on software architecture
Tool support for architecture analysis and design
ISAW '96 Joint proceedings of the second international software architecture workshop (ISAW-2) and international workshop on multiple perspectives in software development (Viewpoints '96) on SIGSOFT '96 workshops
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
Rapide: a language and toolset for simulation of distributed systems by partial orderings of events
POMIV '96 Proceedings of the DIMACS workshop on Partial order methods in verification
The unified software development process
The unified software development process
Doing hard time: developing real-time systems with UML, objects, frameworks, and patterns
Doing hard time: developing real-time systems with UML, objects, frameworks, and patterns
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
Scenario-Based Analysis of Software Architecture
IEEE Software
A Field Guide to Boxology: Preliminary Classification of Architectural Styles for Software Systems
COMPSAC '97 Proceedings of the 21st International Computer Software and Applications Conference
Software Architecture in Practice
Software Architecture in Practice
A formal approach to software architecture
A formal approach to software architecture
Hi-index | 0.00 |
When design software architecture for large systems, designers often face with the problem how to move from requirements to a coarse-grained abstract architecture, then gradually refine it into more concrete ones, and last to detail design and implementation. Steps involved to implement such a process remain vague. Designers usually implement this process intuitively and opportunistically. We propose a Gradually Proceeded Software Architecture Design Process called GADesign. GADesign divides software architecture design into several phases and provides a sequence of well-defined steps to make this process more transparent and easier to be implemented.