Software Architect Role


Get Started. It's Free
or sign up with your email address
Software Architect Role by Mind Map: Software Architect Role

1. Technical Skills

1.1. create or select the most appropriate architecture for a system (or systems)

1.1.1. it should suit the business needs

1.1.2. satisfies stakeholder requirements

1.1.3. achieves the desired results under given constraints abstract the complexity of a system into a manageable model Describe the essence of a system significant constraints ? assumptions ? tradeoffs Design approach Test approach

1.2. maintains control over the architecture life-cycle

1.2.1. proactively monitor the adherence of the implementation to the chosen architecture during changes to the code

1.3. stays on course in line with the long term vision.

1.3.1. project scope creep causes pressure on software architecture to satisfy the desires of stakeholders Good judgement: must know when to say "NO" to select requests in order to say "YES" to others.

1.3.2. focus on actions that produce results early while staying on course for the long term

1.3.3. managing change When project variables outside of one’s control change, adjust the strategy given the resource available while maintaining the long term goal

2. Behavioural Skills

2.1. communication skills

2.1.1. verbal

2.1.2. written

2.1.3. presentational educate and convince stakeholders adjust to the audience

2.2. seek committment

2.2.1. stakeholders

2.2.2. team

2.3. follow industry trends, applicability to product/project/long term

2.3.1. new methodologies

2.3.2. technologies

2.3.3. interact with other architect peers

2.4. ability to traverse from grey to black & white

2.5. negotiation

2.5.1. diplomacy

2.5.2. "principled negotiation" seek mutual cooperation with stakeholders prioritisation conflict management resolution

2.6. convey

2.6.1. credibility through ability past experience training passion

2.6.2. trust

2.7. attitude

2.7.1. accountability

2.7.2. inspirational mentorship

2.7.3. "Stay with the problem" patience resilience

2.7.4. ownership

2.8. understanding SDLC