Decisions Required vs. Decisions Made: Connecting Enterprise Architects and Solution Architects via Guidance Models

[1]  Alexander Ran,et al.  Design decision trees , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[2]  Olaf Zimmermann,et al.  Compliance by design - Bridging the chasm between auditors and IT architects , 2011, Comput. Secur..

[3]  Schahram Dustdar,et al.  Modeling process-driven and service-oriented architectures using patterns and pattern primitives , 2007, TWEB.

[4]  Harald Rønneberg,et al.  Using domain-driven design to evaluate commercial off-the-shelf software , 2006, OOPSLA '06.

[5]  Philippe Kruchten,et al.  Building Up and Reasoning About Architectural Knowledge , 2006, QoSA.

[6]  Hans van Vliet,et al.  Software Architecture Knowledge Management , 2008, 19th Australian Conference on Software Engineering (aswec 2008).

[7]  Olaf Zimmermann,et al.  Architectural Decisions as Reusable Design Assets , 2011, IEEE Software.

[8]  Olaf Zimmermann,et al.  Reference architecture, metamodel, and modeling principles for architectural knowledge management in information technology services , 2012, J. Syst. Softw..

[9]  Harald Rønneberg,et al.  Architectural improvement by use of strategic level domain-driven design , 2006, OOPSLA '06.

[10]  Frank Leymann,et al.  Managing architectural decision models with dependency relations, integrity constraints, and production rules , 2009, J. Syst. Softw..

[11]  Frank Leymann,et al.  Production Workflow: Concepts and Techniques , 1999 .

[12]  Robert L. Nord,et al.  Analysis and Management of Architectural Dependencies in Iterative Release Planning , 2011, 2011 Ninth Working IEEE/IFIP Conference on Software Architecture.

[13]  Olaf Zimmermann,et al.  An architectural decision modeling framework for service-oriented architecture design , 2009 .

[14]  Cesare Pautasso,et al.  Restful web services vs. "big"' web services: making the right architectural decision , 2008, WWW.

[15]  Ken Schwaber,et al.  SCRUM Development Process , 1997 .

[16]  John F. Sowa,et al.  Extending and Formalizing the Framework for Information Systems Architecture , 1992, IBM Syst. J..

[17]  Martin Fowler.  Design - Who needs an architect? , 2003, IEEE Software.

[18]  Olaf Zimmermann,et al.  Managing Artifacts with a Viewpoint-Realization Level Matrix , 2011, Relating Software Requirements and Architectures.

[19]  Jeff Tyree,et al.  Architecture decisions: demystifying architecture , 2005, IEEE Software.

[20]  Frank Buschmann,et al.  Pattern-Oriented Software Architecture, a Pattern Language for Distributed Computing , 2007 .

[21]  Robert L. Nord,et al.  A general model of software architecture design derived from five industrial approaches , 2007, J. Syst. Softw..