It''s a jungle out there.
Delivering software solutions with predictable costs, time, scope, and quality has become more complicated than ever. Developers need to account for multiple moving targets, including often avoided but always relevant factors such as culture, people, and leadership. To effectively deal with these challenges, it''s necessary to rethink the entire delivery chain of modern software development.
This book addresses all these topics, putting everything in perspective, from the potential awkwardness created by cultural differences to connecting code with business outcomes to make delivering quality solutions possible. As a software engineer who strives to be his best and challenge the status quo when building IT systems, author Tengiz Tutisani always wanted a book that would cover all of these elements from a developer''s perspective - so he wrote one.
Effective Software D
Table of Contents
Chapter 1: IntroductionChapter Goal: Give users
the overview of current challenges in software development; prepare mindset to
develop better software and learn how to.
No of pages 11
Sub -Topics
0.
History Behind Inefficient Monoliths
1.
Why People Avoid Building Effective Software
2.
Software Development Perfectionism As A State Of
Mind
3.
Six Pillars Of Effective Software
Chapter 2: Crosscutting Concerns
Chapter Goal: Overview of
software development-related but non-technical challenges, such as leadership,
forming organizations, etc. The goal is broaden the readers’ view and
understand that software development cannot succeed in silo – it needs support
from outside as well.
No of pages: 36
Sub - Topics
0.
Execution, Leadership, Management
1.
Organizational Structure
2.
Processes, Ongoing Efforts, Teams
3.
Culture
4.
Recruitment
Chapter 3: From Customer Insights To InternalRequirements
Chapter Goal: Connecting
the dots between customers’ expectations and the requirements that the software
engineers fulfill; This chapter will enhance the readers with external view to
the requirements – the business value behind deliveries
No of pages: 35
Sub - Topics:
0.
Understanding Customers' Needs
1.
Organization's Response To Customers' Needs
2.
Requirements And Story Writing
3.
Planning Work
4.
Carrying Out Work
Chapter 4: Design and Architecture
Chapter Goal:
Architecture knowledge and work related to building effective software
solutions; Learn how architecture supports all other aspects of software
delivery process
No of pages: 61
Sub - Topics:
1.
Architecture As A Crosscutting Concern
2.
Architecture In Analysis And Requirements Gathering
3.
Architecture Body Of Knowledge
4.
Architecture And Implementation
5.
Architecture For Testable Systems
6.
Architecture For Deployable Systems
7.
Architecture For Maintainable Systems
Chapter 5: Implementation and Coding
Chapter Goal: Dive deep
into the implementation side of things; not much code here but instead
connecting the coding activities back to the architecture’s guardrails, and
forward with quality engineering
No of pages: 52
Sub - Topics:
1.
Crosscutting Concerns Related To Coding
2.
Designing Code
3.
Implementing Code
4.
Testing Code
5.
Code Deployment And Maintenance
Chapter 6: Testing and Quality Assurance
Chapter Goal: Often
overlooked but a vital aspect of software delivery – quality assurance is
discussed in this topic; how to optimize value by combining the architecture
and development with testing, and apply the best of these worlds for quality
software delivery – that is what the readers will learn
No of pages: 30
Sub - Topics:
1.
Testing Processes And Principles
2.
Test Design And Architecture
3.
Implementing Automated Tests
4.
Enhancing Deployments With Test Automation
Chapter 7: Deployment
Chapter Goal: How to
effectively deploy modern, effective software solutions? How these questions
impact architecture, development, or other phases? We will find out in this
chapter.
No of pages: 8
Sub - Topics:
1.
Culture Of Releases
2.
CI/CD - Deployment Foundation
3.
Building Deployment-Ready Applications
Chapter 7: Maintenance and Support
Chapter Goal: Maintenance
seems to be on the other side of the fence from the development. This chapter
will help the readers connect it back to development for decreasing costs and
eliminating the need for dedicated production support teams.
No of pages: 5
Sub - Topics:
1.
Maintenance-Free Mindset
2.
Maintenance-Aware Mindset
