Expert level Software Engineering and Quality

Software Architecture and Engineering Leadership

Learn to make and defend the decisions that shape software systems: architectural styles and trade-offs, domain-driven design, enforcing architecture with code, evolving and modernising systems, delivery metrics, incident reviews and the written communication that leads teams.

  • 41hours of work
  • 18parts
  • Reviewedcapstone
  • Lifetimeaccess
  • Software architecture
  • Domain-driven design
  • Architecture decision records
  • Fitness functions
  • Legacy modernisation
  • Technical leadership

At a glance

Who it is for

Experienced developers who are becoming tech leads and architects, and engineers who want to understand why systems are shaped as they are and how to change them safely over years.

Before you start

Several years of practical development or the content of the intermediate programme in this track (SOLID, patterns, testing and refactoring), plus familiarity with web services, databases and deployment. You should have worked in a team on a code base that changed over time.

How you finish

Pass the quizzes and labs, then submit a capstone project. The NIBVEDA team reviews it and either accepts it or sends it back with comments you can act on.

What you will be able to do

  1. 01Identify quality attributes and constraints, and choose and justify an architectural style with explicit trade-offs
  2. 02Model a domain with bounded contexts and aggregates and map it to modules and services
  3. 03Document architecture with C4 diagrams and decision records, and enforce rules automatically with fitness functions
  4. 04Plan the evolution and modernisation of a legacy system with strangler, expand-contract and feature-flag techniques
  5. 05Measure delivery performance, run blameless incident reviews and lead technical decisions with clear written proposals

Curriculum 41 hours in 18 parts

Select a kind to highlight its parts.

Stage 1An architecture document with decision records7 parts · 13 h
  1. 1
    What software architecture is, and what architects doLesson · Short, focused reading with questions to check yourself.
    1 hFree
  2. 2
    Architectural styles and when to use themWorkshop · Follow along and build, with the steps and the traps written out.
    2 h
  3. 3
    Architect a system and record the decisionsWorkshop · Follow along and build, with the steps and the traps written out.
    2 h
  4. 4
    Domain-driven designWorkshop · Follow along and build, with the steps and the traps written out.
    2 h
  5. 5
    From event storming to aggregates in codeWorkshop · Follow along and build, with the steps and the traps written out.
    2 h
  6. 6
    Check yourself: architecture, styles and domain-driven designQuiz · Twelve questions, marked at once, with the reason behind each answer.
    1 h
  7. 7
    An architecture document with decision recordsLab · Hands-on work. Many labs are checked automatically against what must exist.
    3 h
Stage 2A modular monolith whose architecture is enforced by the build6 parts · 11 h
  1. 8
    Distributed system realities, APIs and contractsWorkshop · Follow along and build, with the steps and the traps written out.
    2 h
  2. 9
    A modular monolith with enforced boundariesWorkshop · Follow along and build, with the steps and the traps written out.
    2 h
  3. 10
    Quality attributes in depth, threat modelling and fitness functionsLesson · Short, focused reading with questions to check yourself.
    1 h
  4. 11
    Write fitness functions and a threat modelWorkshop · Follow along and build, with the steps and the traps written out.
    2 h
  5. 12
    Check yourself: distributed systems, APIs and quality attributesQuiz · Twelve questions, marked at once, with the reason behind each answer.
    1 h
  6. 13
    A modular monolith whose architecture is enforced by the buildLab · Hands-on work. Many labs are checked automatically against what must exist.
    3 h
Stage 3A modernisation plan with working prototypes3 parts · 6 h
  1. 14
    Technical debt, migration strategies and zero-downtime changeWorkshop · Follow along and build, with the steps and the traps written out.
    2 h
  2. 15
    Check yourself: technical debt, migration and modernisationQuiz · Twelve questions, marked at once, with the reason behind each answer.
    1 h
  3. 16
    A modernisation plan with working prototypesLab · Hands-on work. Many labs are checked automatically against what must exist.
    3 h
Stage 4Delivery metrics, incident review and a technical proposal1 part · 3 h
  1. 17
    Delivery metrics, incident review and a technical proposalLab · Hands-on work. Many labs are checked automatically against what must exist.
    3 h
FinishCapstone project1 part · 8 h
  1. 18
    An architecture, a working reference system and the leadership artefactsCapstone · A full project for your portfolio.
    8 h
Free lessonWhat software architecture is, and what architects do
What you take away

An internship certificate with your skills on it.

Made for you automatically when you finish the last part, it names the internship programme, the level and the 41 hours, lists what you showed, and carries a number and a QR code. Anyone can check it on the NIBVEDA verification page, and it shows as withdrawn there if it is ever revoked.

  • Proof you completed all 41 hours of this internship programme
  • An Internship badge for your profile, CV or portfolio
  • Not a job, a stipend or an academic degree, and it says so
More in Software Engineering and Quality

Keep building.

3 programmes in this track, from beginner to expert. Buy the learning path and save 15%.

IntermediateIntermediate40 h Design Patterns, Refactoring and Test-Driven Development

Design software that is easy to change: test-driven development, SOLID design, the patterns that solve recurring problems, taming legacy code, and property-based and mutation testing, finishing with a well-designed, thoroughly tested application.

  • Test-driven development
  • SOLID design
  • Design patterns
Rs. 599 + GST
BeginnerBeginner40 h Professional Habits for New Developers

Learn the habits of professional developers: Git and pull requests, readable code, automated tests with pytest, debugging, working with others and continuous integration, finishing with a small project released like real software.

  • Git and GitHub
  • Clean code
  • Unit testing with pytest
Rs. 249 + GST

See all 3 programmes in Software Engineering and Quality Take the placement test

Before you enrol

Quick answers.

The policies have the full detail.

Is this a real internship?

It is a virtual internship programme: a structured, self-paced course built around a real project, with checked assessments and a certificate. It is not employment, it does not carry a stipend and it is not an academic or AICTE-approved qualification. What it gives you is verified, project-based evidence of skills.

How does self-paced work?

You start when you like and move at your own speed. Each part unlocks when you finish the one before it. There are no live classes and no deadlines. Your access is shown on each programme page.

How is my work checked?

Quizzes are marked as soon as you submit them. Labs use a tick-list of tasks. Intermediate and Expert programmes finish with a capstone that the NIBVEDA team reviews and either accepts or sends back with comments.

Can I get a refund?

Please read the refund policy before you buy. It explains when a refund is possible.

Ready to start?

Rs. 1,178.82 including GST. Lifetime access. Read the first lesson free before you decide.