This module covers all the typical stages of the software development life cycle, including cross-cutting.

Software Development Methodologies

In this module, we’ll learn how to implement effective software practically through tried and tested approaches. By going through a comprehensive compilation of key concepts in software development methodology, we will learn about essential techniques for becoming better software craftsmen. This module starts with an introduction to effective software development and discusses cross-cutting concerns. After going through these, we’ll move on to design, architecture, implementation, and coding concepts. Ultimately, we'll learn about testing, quality assurance, deployment, and maintenance.

Effective Software Development for Enterprise Applications

The concept of Evolving Design allows relaxing software architecture and upfront design needs since the design will evolve naturally and organically.


The concept of Evolving Design allows relaxing software architecture and upfront design needs since the design will evolve naturally and organically.

 Agile methodologies repeat steps of Waterfall #key# SDLC: Software Development Lifecycle #key# in each Agile iteration.

Agile methodologies repeat steps of Waterfall <keyword><word>SDLC</word><meaning>Software Development Lifecycle</meaning></keyword> in each Agile iteration.

Who is responsible for recommending the split of software solutions if there is a need to split engineering teams?

Who is responsible for recommending the split of software solutions if there is a need to split engineering teams?

Which knowledge exploration exercise correlates with effectively finding events for Event-Driven Architecture?

Which knowledge exploration exercise correlates with effectively finding events for Event-Driven Architecture?

Assuming that a technical solution is a combination of two layers (technical domain and shared understanding), software architects need to protect and increase the technical domain's size, which comprises the solution.

Assuming that a technical solution is a combination of two layers (technical domain and shared understanding), software architects need to protect and increase the technical domain’s size, which comprises the solution.

The real value of the software system is based on its usefulness and its development and maintenance costs.

The real value of the software system is based on its usefulness and its development and maintenance costs.

The technology used in software solutions is more important and essential to success and competitive advantage than the solution's domain and business logic.

The technology used in software solutions is more important and essential to success and competitive advantage than the solution’s domain and business logic.

Which kind of domain is considered an anti-pattern?

Select all that apply.

Which kind of domain is considered an anti-pattern?
Select all that apply.

Microservice always means a small-size Web API.

Microservice always means a small-size Web API.

It is recommended that microservices integrate through their APIs or messaging layers only.


It is recommended that microservices integrate through their APIs or messaging layers only.

Event-Driven Architecture connects distributed systems via exchanging events between these systems.

Event-Driven Architecture connects distributed systems via exchanging events between these systems.

Which technology platform is an example of containerization?

Select all that apply.

Which technology platform is an example of containerization?
Select all that apply.

Tactical DDD solves high-level problems spanning an entire enterprise.

Tactical DDD solves high-level problems spanning an entire enterprise.

It is harder to build high-quality, maintainable systems, as it requires mastering and adhering to more advanced patterns and practices.


It is harder to build high-quality, maintainable systems, as it requires mastering and adhering to more advanced patterns and practices.

An acronym for five principles to write testable code


An acronym for five principles to write a testable application


 What does SOLID represent in software engineering?


What does SOLID represent in software engineering?

Check your understanding with the quiz questions below!

Fundamentals

Part I: Introducation

Part II: Crosscutting Concerns

Part III: From Customer Insights to Internal Requirements

Part IV: Design and Architecture

Part V: Implementation and Coding

Part VI: Testing and Quality Assurance

Part VII: Deployment

Part VIII: Maintenance and Support

Conclusion

Chapter Quiz