[PART 1 SOFTWARE ARCHITECTURE]

CHAPTER 1 Becoming a Software Architect

1.1 What a Software Architect Does
1.2 What is Software Architecture?
1.3 To become an architect in the team
1.4 Building Great Software
1.5 Case Study: The Lionheart Project
1.6 In conclusion

CHAPTER 2: Design Thinking Fundamentals

2.1 Four Principles of Design Thinking
2.2 Equipping a design mindset
2.3 Think-Do-Check
2.4 In conclusion

[PART 2: The Fundamentals of Architecture Design]

CHAPTER 3: DEVELOPING A DESIGN STRATEGY

3.1 Designing Satisfactorily
3.2 How Much Priority Should Design Be Given?
3.3 Using risk factors as a guide
3.4 Developing a Design Plan
3.5 Case Study: The Lionheart Project
3.6 In conclusion

CHAPTER 4 Empathizing with Stakeholders

4.1 Talk to the right people
4.2 Creating a Stakeholder Map
4.3 Exploring Business Goals
4.4 Case Study: The Lionheart Project
4.5 In conclusion

CHAPTER 5: Identifying Core Architecture Requirements

5.1 Reducing Design Choices with Constraints
5.2 Defining Quality Attributes
5.3 Identifying Functional Requirements
5.4 Identifying Other Factors Affecting the Architecture
5.5 Conway's Law
5.6 Digging deeper into the information you need
5.7 Creating an ASR Workbook
5.8 Case Study: The Lionheart Project
5.9 In conclusion

CHAPTER 6 Choosing an Architecture

6.1 Branching for alternatives, fusion for decisions
6.2 Accepting Constraints
6.3 Improving quality attributes
6.4 Assigning functional roles to components
6.5 Design for Change
6.6 Decisions are postponed until they can be postponed.
6.7 Case Study: The Lionheart Project
6.8 In conclusion

CHAPTER 7 Building a Foundation with Patterns

7.1 What are architectural patterns?
7.2 Layer Pattern
7.3 Port and Adapter Patterns
7.4 Pipe and Filter Patterns
7.5 Service-Oriented Architecture Patterns
7.6 Publish/Subscribe Pattern
7.7 Shared Data Patterns
7.8 Multi-layer pattern
7.9 Experienced Expert Pattern
7.10 Open Source Contribution Patterns
7.11 Large Mud Ball Pattern
7.12 Discovering New Patterns
7.13 Case Study: The Lionheart Project
7.14 In conclusion

CHAPTER 8: Managing Complexity with Meaningful Models

8.1 Understanding the Architecture
8.2 Designing a Metamodel
8.3 Implementing the Model in Code
8.4 Case Study: The Lionheart Project
8.5 In conclusion

CHAPTER 9: Running an Architecture Design Studio

9.1 Planning an Architecture Design Studio
9.2 Selecting Appropriate Design Activities
9.3 Inviting Appropriate Participants
9.4 Managing Groups
9.5 Collaborating Remotely
9.6 Case Study: The Lionheart Project
9.7 In conclusion

CHAPTER 10: Visualizing Your Design

10.1 Expressing Architecture from Different Perspectives
10.2 Drawing Cool Diagrams
10.3 Case Study: The Lionheart Project
10.4 In conclusion

CHAPTER 11 Documenting the Architecture

11.1 The Value of Documentation
11.2 How to describe the situation appropriately
11.3 Considering the Readers of the Specification
11.4 Understanding is important
11.5 Tailoring Views to Stakeholder Interests
11.6 Explaining the logical basis for a decision
11.7 Case Study: The Lionheart Project
11.8 In conclusion

CHAPTER 12 Evaluating Architecture

12.1 Learning through Evaluation
12.2 Testing the Design
12.3 Organizing an Evaluation Workshop
12.4 Evaluate quickly, frequently, and continuously
12.5 Case Study: The Lionheart Project
12.6 In conclusion

CHAPTER 13 Empowering Architects

13.1 Improving Architectural Thinking
13.2 Improving Team Decision-Making and Capacity
13.3 Creating Opportunities Through Safe Training
13.4 Delegating Design Authority
13.5 Designing Architecture Together
13.6 Case Study: The Lionheart Project, a Grand Conclusion
13.7 In conclusion

[PART 3: The Architect's Silver Toolbox]

CHAPTER 14 When you want to understand the problem

Activity 1: Choose only one
Activity 2: Empathy Map
Activity 3: The GQM Approach
Activity 4: Stakeholder Interviews
Activity 5: Listing Assumptions
Activity 6 Quality Attribute Radar Chart
Activity 7 Mini Quality Attribute Workshop
Activity 8 Perspective Mad Lip
Activity 9 Scarecrow Reaction
Activity 10 Stakeholder Map

CHAPTER 15 When you want to find a solution

Activity 11: Architectural Personification
Activity 12 Architecture Flipbook
Activity 13 Component - Role Card
Activity 14 Concept Map
Activity 15: Divide and Conquer
Activity 16 Event Storming
Activity 17 Group Poster
Activity 18 Round Robin Design
Activity 19 Whiteboard Discussion

CHAPTER 16 When you want to create a design that is tangible

Activity 20 Architectural Decision Record (ADR)
Activity 21 Architecture Haiku
Activity 22 Context Diagram
Activity 23 Popular Reading List
Activity 24 Inception Deck
Activity 25 Modular Exploded Diagram
Activity 26 The Unexpected Path
Activity 27 Prototype
Activity 28 Sequence Diagram
Activity 29 System Metaphor

CHAPTER 17 When you want to evaluate design alternatives

Activity 30 Architecture Briefing
Activity 31 Code Review
Activity 32 Decision Matrix
Activity 33: Observing
Activity 34 Questions-Comments-Concerns
Activity 35 Risk Storming
Activity 36 Sanity Check
Activity 37 Scenario Overview
Activity 38: Sketch and Compare

Appendix: Contributors

Designing software architecture is always a confusing task.
This is because you need to understand business goals and understand the needs of multiple stakeholders, as well as overcome constraints to create a program that works 'right' and satisfies everyone.
Architects need to have a business-centric perspective on software, as well as the ability to see the entire system and understand the technical details.

This book is a practical introduction for those taking the first step toward transformation from developer to architect.
This book is perfect for those who are suddenly assigned to design work at their company, or for startup developers and CTOs who need to lead projects themselves.
Of course, it is also useful for developers who want to broadly understand software architecture.

This book provides essential knowledge about architecture and design, insights from experienced architects, and practical case studies from the field.
At the end of each chapter, we summarize what we've learned with a case study of a virtual city called 'Lionheart'.
By following examples of projects that have successfully completed despite challenges, you'll gain confidence that you can do it too.
I hope that everyone who reads this book will become an excellent architect who can lead projects and teams to success.

Key Contents

- What is software architecture and what do architects do?
- Architecture design strategy utilizing design thinking and design mindset
- Clearly identify and understand stakeholders and business goals
- Identify core architectural requirements and define quality attributes.
- Frequently used architectural patterns and their usage
- Managing system complexity using architectural models
- Running an architecture design studio
- Visualize the design and document the architecture.
- Evaluate the architecture and reflect feedback to improve it.
- Delegate design authority appropriately and enhance team capacity.
- 38 team activities that can be used immediately in the field

Target audience

- People who want to change their career from developer to architect
- People who want to improve their practical development skills by properly understanding software architecture.
- New developers who want to understand the overall structure and development process of the software.
- People who want to understand the perspectives of various stakeholders surrounding software

How to Use This Book by Development Experience

- New Developers: Go beyond simply writing code and broaden your horizons by seeing the forest that is software development and projects.
- Developers/Architects with less than 5 years of experience: Understand commonly used patterns, models, and design methods, and learn how to visualize and document your architecture.
If you're struggling to collaborate with others, find wisdom in case studies and articles from experienced architects.
Developers/Architects with 10+ years of experience: Do you need to lead projects or lead a development team as an architect? Learn how to effectively communicate with team members and stakeholders.
Find activities you can try to solve the problem and try the methods introduced in the book yourself.
We'll find a solution soon.