Saturday, July 31, 2010
Firebrand Architect® Blog
Minimize

"The firebrand is the person who recognizes what is natural, what is organic, what is alive and vital in life ... the firebrand chooses to be different when being different represents a truth, when being different guides the fulfillment of basic human values ..." This blog is an application of this philosophy to the software architecture discipline. undefined

Recent Noteworthy Topics

  • In Software Engineering we’ll never reach a plateau
  • Follow the money
  • You can take off, but can you land?
  • Wiki as a shared design space
  • Software Engineers as architecture stakeholders
  • Your leadership style
  • You can't rely on patterns alone
  • Solutions not fit for purpose
  • Role of organizational politics in software architecture design
  • Cloud Computing
  • The Bus Problem
  • Architecture Evaluation Attitude
  • Evolving Opportunistic Solutions
  • Globalization and Architecture

 

This site provides software architecture discipline practitioners and apprentices with vendor and technology neutral guidance, resources, and unique insight. The site's focus is on responsible software architecture. Read more.
> In 2005 the Firebrand Architect
® software engineering think tank was created and spun off as a separate entity. Its mantra is to enable people create software that's fit for purpose™. This site and the Firebrand Architect® blog address the Human Aspects of Software Architecture.

Share |
Essentials
Minimize

Architect's Responsibilities | Quality Attributes | Responsible Architecture | Architecture Explained

♦ Updated 04/2010: all articles and pages refreshed to reflect the rapidly changing nature of the software architecture practice.

♦ Writing good quality attribute scenarios is hard, but it's an important skills. Quality attribute scenarios is where the desired vague software behaviors are turned into tangible and measurable goals. Buy and download a catalog of over 100 well defined quality attribute scenarios.

♦ A roadmap for apprentice software architects. An individual matures into this prestigious role through solid computer science education, software engineering experience, business domain experience, and by learning software architecture patterns, styles, documentation approaches, altered requirements elicitation methods, and design analysis techniques.

♦ Updated 03/2010: a library of usable architecture documents is available to registered users under the Essential Selection section.

Please Visit our Sponsors
Minimize

 

Please Visit our Sponsors
Minimize

 

Print  
Privacy Statement  |  Terms Of Use
Copyright 2002 - 2010 by SoftwareArchitectures.com