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

Arnon is a software architect with 16 years of experience building large, complex distributed systems on various platforms ranging from HP-UX and Solaris to AS400 and Windows. Arnon blogs at http://www.rgoarchitects.com/blog/ and also writes the Dr. Dobb's Portal blog on software architecture and design at http://www.ddj.com/dept/architect/. He can be contacted at arnon@rgoarchitects.com.

---

Congratulations! You have just been made lead architect for your company's next flagship project. The project, whose initial estimates range from 200-300 man years to complete, is both complicated and important—and under the C-level microscope. Where do you start?

Enter the SPAMMED Architecture Framework (SAF). SAF identifies the steps and activities you need to design, model, and build successful architectures. But designing software architectures is not just the modeling. There are all kinds of activities that help ensure that the model is usable and that the architecture is successful; hence, the acronym "SPAMMED," which:

• Identifies Stakeholders
• Lists Principles, goals, and constraints
• Discovers quality Attributes
• Models
• Maps to technology
• Evaluates
• Deploys

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 Next Page

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