Software Architecture Methodology
Description
This course defines the foundations of software architecture, examines the role of a software architect in developing projects, follows project initiation and requirements identification, plus implements practices related to the design, documentation, and analysis of software architecture.
These practices can be used by software architects, project managers, developers, and business analysts in their activities in projects of various problem domains and technologies.
Theoretical material is supported with examples from contemporary tools, frameworks, environments, and also the instructor’s experience. The course includes both short exercises and comprehensive practice, carried out in groups of 3-4 people, starting from the problem’s background up to actual design of a software system. The training ends with a presentation of the results of each team activity and their examination in front of all other teams.
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
- Context, main concepts, analysis and design discipline overview, role of an architect
- Project initiation: identifying stakeholders and business goals
- Identifying, formalizing and prioritizing the requirements to system quality (main: performance and scalability, accessibility, security, changeability and other quality attributes)
- Architectural design: decision-making, tactics, patterns, approaches and styles; typical tactics applied to achieve 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 system quality; using simplified description in pre-sale activities
- Architectural analysis: formal process of architecture analysis and assessment involving stakeholders, identification of compromise solutions and architectural risks, further work with risks