role-architect

Apply SOLID principles to system design by using structured criteria and reference patterns to evaluate maintainability, testability, and performance during large refactoring efforts. This approach ensures decoupled components and scalable software architecture.

Design patterns like MVC, Repository, Factory, Strategy, Observer, and Dependency Injection work best for improving software scalability and modularity. These patterns provide structured guidance for layered architectures and decoupled system components.

You need an architecture review when planning major subsystem designs, analyzing scalability, or undertaking large refactoring efforts. Reviews evaluate maintainability, testability, performance, and component decoupling using SOLID principles and reference patterns.

Yes, this architectural guidance supports analyzing trade-offs for layered architectures. It provides a structured framework documenting reasoning for design pattern selection and architectural trade-offs to help teams produce maintainable software.

The best way to document architectural reasoning is by applying SOLID principles and design patterns within a structured framework. This documents trade-offs and rationale for maintainability, testability, and scalability decisions for future engineers.

Yes, you can use design patterns like Strategy, Observer, Factory, and Dependency Injection to plan decoupled component architectures. These patterns guide structured decisions for modularity and decoupled system design.