Software Architecture Methodology and Concepts

Code: ARC-001
Duration: 24 hours

Description

The course introduces the main concepts and context of software architecture. Participants will learn about practices such as essential requirements identification, design, documentation, and analysis, in other words about rather general all-around methodology not bound to specific technological base or area of expertise.

Theoretical material is corroborated by cases from trainer’s experience and reinforced with the help of small exercises. Every day, in the afternoon students will participate in team games and will try to apply these practices in some cases related with business issues of software development.

Roadmap

Context, main concepts, software design and architecture analysis, role of architect
Project initiation: identifying stakeholders and business goals
Identifying, formalizing and prioritizing the requirements to quality system characteristics (main: performance and scalability, accessibility, security, changeability and other quality attributes)
Architectural design: decision-making, concepts of tactics, patterns, approaches and styles; typical tactics applied for achieving main quality characteristics
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 quality system characteristics; using simplified description in pre-sale activities
Architectural analysis: formal process of architecture analysis and assessment involving stakeholders, identifying compromise solutions and architectural risks, further working with risks

Objectives

Provide architects, system analysts, and technical leaders with design and software architecture skills that can be applied:

in current projects as means of quality maintenance of the delivery system, problem solving and customer expectations management,
in pre-delivery inspection as means of analysis, preliminary design, and estimate for reducing risks related to 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

More than three years of experience in software engineering (any role).
More than one year of experience in software development projects in any role from the Target Audience list (see above).

Trainer in Krakow

Andrey Gordienkov Software Architecture and Development Consultant

Andrey has been involved in financial software development with .NET technologies for more than 7 years. He has extensive experience in building middle-ware systems and providing expert technology solutions. His main area of focus is integrating multiple separate systems into a single information system with high response levels.

For the last 3 years, Andrey has kept a blog on development technologies regularly posting articles and video lessons. He is a constant participant of Microsoft’s Debating Club for Development Directors and the author of the MSDeveloper.ru magazine.

Andrey takes an interest in new technologies that reduce the amount of routine manual work separating them from human impact: Continuous Integration, Testing, Deployment.

Testimonials:

Mike

The training was very powerful and plenty of tehnic information present. The explanations were very usefull, i noticed the understanding the phenomenon behind the optical communications. I was impressed by the the large amount of technical documentation.

Courses you may be interested in:

ARC-004

Patterns of Enterprise Application Architecture

24 hours

ARC-005

Analysis Patterns in software development

24 hours

PM-007

Risk Management

20 hours