Software Architecture Methodology

Software Architecture Methodology
Duration
24 hours
Course type
Online
Language
English
Duration
24 hours
Location
Online
Language
English
Code
ARC-001
Training for 7-8 or more people? Customize trainings for your specific needs
Software Architecture Methodology
Duration
24 hours
Location
Online
Language
English
Code
ARC-001
€ 700 *
Training for 7-8 or more people? Customize trainings for your specific needs

Description

certificate
After completing the course, a certificate
is issued on the Luxoft Training form

Objectives


Train architects, system analysts, and technical leaders in software architecture design and analysis skills that can be used:

• In current projects to ensure quality of the system under development, solve problems, and manage customer’s expectations;

• In the design of new projects to start with an efficient and easy to evolve architecture;

• In pre-sale activities as a trigger for conducting analysis, elaborating preliminary design, and making estimates to decrease risks of a commercial offer.

Target Audience

Main:

  • Architects
  • Technical leaders and senior developers
  • System analysts and designers

Other:

  • Project managers, quality managers, pre-delivery preparation managers
  • Business analysts

Prerequisites

  • At least three years of (any) experience in software engineering.
  • More than 1 year experience in projects on software development in any role from the Target Audience list (see above).
  • The technology and area of expertise do not matter.

Roadmap

  1. Context, main concepts, analysis and design discipline overview, role of an architect
  2. Project initiation: identifying stakeholders and business goals
  3. Identifying, formalizing and prioritizing the requirements to system quality (main: performance and scalability, accessibility, security, changeability and other quality attributes)
  4. Architectural design: decision-making, tactics, patterns, approaches and styles; typical tactics applied to achieve main quality characteristics
  5. Documenting software architecture: the purpose and structure of architectural description; viewpoint-based approach and architectural views; detailed overview of the most popular viewpoints (4+1 and Rozansky&Woods), using modeling techniques in documenting; the prospects of applied tactics for achieving the desired system quality; using simplified description in pre-sale activities
  6. Architectural analysis: formal process of architecture analysis and assessment involving stakeholders, identification of compromise solutions and architectural risks, further work with risks
Trainers
Florin-Catalin Tudose

Catalin is an experienced and dedicated software engineer with expertise in a variety of areas such as requirements analysis, project management (Waterfall and Agile), people management, Java technologies, database design, software archi

Still have questions?
Connect with us