Effective Software Development for the Enterprise

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 Development for the Enterprise builds on advanced disciplines, methodologies, and techniques derived from domain-driven design, software architecture, and extreme programming. Its objective is to aid modern software engineers and solution architects in building and delivering high-quality solutions for an enterprise while meeting ambitious criteria:

* Meet users' expectations
* Deliver solutions on time with no defects
* Create products that can scale-out horizontally
* Solutions should not require a dedicated production support team
* Accelerate development pace
* Double ROI per developer, team, and software

You will learn how to achieve these objectives in any engineering environment by developing solid strategies based on the industry's well-known, recognized, and proven patterns and principles. After reading this book, you will be ready to effectively deal with any and all challenges posed by today’s hyper-competitive, globally-diverse, fast-moving enterprise environment.

WHO THIS BOOK IS FOR

Professional software engineers and solution architects, as well as those aspiring to become one. Additionally, software engineering leaders will benefit from reading it, as it will help them maximize their impact via successful software project deliveries.

TENGIZ TUTISANI has been in the software development industry for over 19 years. His experience ranges from startups to Fortune-500 corporations. He held roles with a mix of people and technology leadership (software engineer, technical lead, development manager, application architect, solutions architect, enterprise architect, and chief architect). Tengiz's broad experience and frequent recognition for outstanding quality and performance have convinced him to teach others unique engineering and architecture techniques. He authored this book to describe advanced techniques for professional software development and architecture disciplines.

Chapter 1: Introduction

CHAPTER 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