کتاب معیارهای معماری نرم‌افزار

چهار معیار کلیدی رها شده

Definition and Instrumentation • Refactoring Your Mental Model • Pipelines as Your First Port of Call • Locating Your Instrumentation Points • Capture and Calculation • Display and Understanding • Target Audience • Visualization • Front Page • Discussions and Understanding • Ownership and Improvement • Conclusion

هرم تست تابع تناسب: تمثیلی برای تست‌ها و معیارهای معماری

Fitness Functions and Metrics • Fitness Functions: Test Coverage • Fitness Functions: Integration Tests with Network Latency • Introduction to Fitness Function Categories • Mandatory Fitness Function Categories • Optional Fitness Function Categories • Fitness Function Categories: Catalog Overview • The Testing Pyramid • The Fitness Function Testing Pyramid • The Top Layer • The Middle Layer • The Bottom Layer • Examples and Their Full Categorization • Fully Categorizing Top-Layer Examples • Developing Your Fitness Functions and Metrics • Conclusion

معماری تکاملی: هدایت معماری با قابلیت تست و استقرار

The Importance of Learning and Discovery • The Tools of Sustainable Change • Testability: Creating High-Quality Systems • Deployability: Scaling Development of Our Systems • Conclusion

معماری خود را با شاخص بلوغ پیمانه‌پذیری بهبود بخشید

Technical Debt • Origination of Technical Debt • Assessment with the MMI • Modularity • Hierarchy • Pattern Consistency • Calculating the MMI • Architecture Review to Determine the MMI • Conclusion

بیلد‌های خصوصی و معیارها: ابزارهایی برای بقا در انتقال‌های DevOps

Key Terms • CI/CD • DevOps • The “Ownership Shift” • Empowering the Local Environment Again • The Private Build • Case Study: The Unstable Trunk • Bug A1 • Bug A2 • Bug A3 • Bug A4 • Case Study: The Blocked Consultant • Metrics • Time to Feedback • Evitable Integration Issues in the Deployed Application per Iteration • Time Spent Restoring Trunk Stability per Iteration • The Cost of Private Builds • Metrics in Practice • High Time to Feedback, High Evitable Integration Issues, Low Time to Trunk Stability • Low Time to Feedback, High Evitable Integration Issues, Low Time to Trunk Stability • High Time to Feedback, Low Evitable Integration Issues, Low Time to Trunk Stability • Low Evitable Integration Issues and High Time to Trunk Stability • Conclusion

مقیاس‌بندی یک سازمان: نقش مرکزی معماری نرم‌افزار

YourFinFreedom Breaks the Monolith • Implementing a Distributed Big Ball of Mud • Seeking Direction • From Best Effort to Intentional Effort • Increasing Software Architecture Intentionality, Guided by Metrics • Managing Expectations with Communication • Learning and Evolving the Architecture • And What About Anna? • Conclusion

نقش اندازه‌گیری در معماری نرم‌افزار

Adding Measurement to Software Architecture • Measurement Approaches • Runtime Measurement of Applications and Infrastructure • Software Analysis • Design Analysis • Estimates and Models • Fitness Functions • Measuring System Qualities • Performance • Scalability • Availability • Security • Getting Started • Hypothetical Case Study • Pitfalls • Conclusion

پیشرفت از معیارها به مهندسی

The Path to Fitness Functions • From Metrics to Engineering • Automation Operationalizes Metrics • Case Study: Coupling • Case Study: Zero-Day Security Check • Case Study: Fidelity Fitness Functions • Conclusion

استفاده از معیارهای نرم‌افزار برای تضمین قابلیت نگهداری

The Case for Using Metrics • Entropy Kills Software • The Toxicity of Cyclic Dependencies • How Metrics Can Help • Why Are Metrics Not More Widely Used? • Tools to Gather Metrics • Useful Metrics • Metrics to Measure Coupling and Structural Erosion • Metrics to Measure Size and Complexity • Change History Metrics • Other Useful Metrics • Architectural Fitness Functions • How to Track Metrics over Time • A Few Golden Rules for Better Software • Conclusion

اندازه‌گیری ناشناخته‌ها با رویکرد هدف-سوال-معیار

The Goal-Question-Metric Approach • Create a GQM Tree • Prioritize Metrics and Devise a Data Collection Strategy • Case Study: The Team That Learned to See the Future • System Context • Incident #1: Too Many Requests to the Foo Service • Incident #2: Seeing the Future • Reflection • Run a GQM Workshop • Workshop Summary • Workshop Steps • Facilitation Guidelines and Hints • Conclusion