{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

27_People_Roles_and_Teams

27_People_Roles_and_Teams - People,Roles,and Teams...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
Copyright  ©  Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. People, Roles, and  Teams Software Architecture Lecture 27
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
2 Foundations, Theory, and Practice Software Architecture Software Architecture The Need The greatest architectures are the product of  A single mind or A very small, carefully structured team Rechtin,  Systems Architecting: Creating & Building  Complex Systems , 1991, p21 Every project should have exactly 1 identifiable architect  For larger projects, principal architect should be  backed up by architect team of modest size Booch,  Object Solutions , 1996
Background image of page 2
3 Foundations, Theory, and Practice Software Architecture Software Architecture Software Architects Architect is “jack of all trades” Maintainer of system’s conceptual integrity Part of team Set of people with complementary skills Committed to common Purpose Performance goals Approach Hold each other accountable Life of architect is long series of locally suboptimal decisions made  partly in the dark Sometimes painful
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
4 Foundations, Theory, and Practice Software Architecture Software Architecture Desired Skill Set Software development expertise Domain expertise Communicator Strategist Consultant Leader Technologist Cost estimator Cheerleader Politician Salesperson
Background image of page 4
5 Foundations, Theory, and Practice Software Architecture Software Architecture Blending the Skill Set May need different people & skills based on  Characteristics of project & domain Lifecycle “phase” Type of architecture  Enterprise vs. product-line vs. product Distinction between junior & senior architects Each architect should possess some subset of above skills What architects are usually  not  in a project  Developers – though they may prototype their ideas Managers – except in small organizations
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
6 Foundations, Theory, and Practice Software Architecture Software Architecture Architects As Software Development Experts Must understand nuances of software development Principles Methods & techniques Methodologies Tools Need not be world-class software programmers Should understand ramifications of architectural choices Do not live in ivory tower Some architectural choices constrain implementation  options Some implementation-level techniques & tools constrain  architectural choices
Background image of page 6
7 Foundations, Theory, and Practice Software Architecture Software Architecture Architects As Domain Experts Software engineering expertise is not enough Problem domain nuances Maturity Stability System user profile May greatly affect selected & developed architectural 
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}