Email	Print Reprint
	add to:
	Del.icio.us Digg Google Furl	Slashdot Y! MyWeb Blink
	TABLE OF CONTENTS The SPAMMED Architecture Framework Identify Stakeholders List Principles, Goals, and Constraints Discover Quality Attributes Model & Map to Technology Evaluate & Deploy Conclusion

Conclusion

Designing a software architecture is not just the modeling itself. There are other activities, identified by SAF, that help ensure that the model is usable and that the architecture is successful. But SAF is not a process. When you perform one activity, you should go back over and over to adjust/rethink some of the other ones. The obvious example is that once you evaluate your model, you need to fix it according to the results of the evaluation. Figure 2 illustrates some of the common transitions.

In short, SAF is not the end result—it is the starting point. Your role as an architect is to fill each of these activities with meaningful substance relevant to the project at hand.

DDJ

Previous Page | 1 The SPAMMED Architecture Framework | 2 Identify Stakeholders | 3 List Principles, Goals, and Constraints | 4 Discover Quality Attributes | 5 Model & Map to Technology | 6 Evaluate & Deploy | 7 Conclusion

RELATED ARTICLES No Related Articles		TOP 5 ARTICLES No Top Articles.