T1101

Architecture Fundamentals

Have you recently come in to a role as an architect in your company and want to understand more about what your role is and how to actually be an architect? Or do you already work as an architect and feel that you need more structure around how you work?

This course will teach you how to work methodically in designing and building architecture, as well as give you an introduction to the broad spectrum of architecture roles in the workforce.  The course will open with a brief overview of why architecture exists and how the different roles relate to each other, continue to how architecture fits in to the process of building applications and solutions, and then run through a complete example of how to create a Software Architecture Description, including building up a design from requirements through deployment.  At the end of the course you will have a much deeper understanding of how to work as an architect and what the fundamentals are in architecture work.

Audience:

  • Developers who want to understand how to think in terms of the bigger picture
  • Architects new to the role who want to get a basic understanding of how to work as an architect
  • Experienced architects who want to get more methodology around how they work

Objectives:

This course will:

  • Teach you about what an architects role is and what they should know
  • Teach you how to produce a complete design from requirements
  • Show you how to build up a Software Architecture Design document

The course will not talk about how to build solutions tied to a particular programming language, it is technology independent.  

Course Outline: 

Day 1

Introduction

  • What is architecture?

Enterprise, Solution, Software, Integration Architect

  • What is an Architect and what do they do?

What an architect needs to know

  • Basic process of architecture

Company strategy

  • Enterprise architect, SOA, ESB, platform, TOGAF, Zachmann, etc

Project prestudy

  • Solution architect, functional requirements to quality attributes, rankingquality attributes, architecture proposals, help guide in buy-rent-build decision point

Project definition

  • Software/System architect, use case realization, component definitions, interfaces, sequence diagrams, first-cut SAD, developer guidelines

Project implementation

  • Lead developer/System-Software Architect/Configuration Manager, development environment, continuous build setup, developer guidelines, unit test strategy, Scrum Master, source repo strategy, practical aspects

Testing

  • All roles, acceptance testing, changing requirements, interpret test results, interactive testing/debugging

Deploy

  • All roles, deployment strategy, environment, physical setup, load balancing, caching, etc.

Day 2 - Start creating a SAD

Step 1 - Architecturally significant requirements

  • Start with high level functional requirements

Comes from workshops, generated by business side

  • Find quality attributes. QAW, Furps+, find and interview stakeholders
  • Rank quality attributes
  • Exercise - from HFR, build system quality requirements, with sample stakeholder feedback

Step 2 - Solution Architecture

  • From step 1, how should system be designed
  • Information modeling (Exercise: model based on step 1)
  • Basic components and use cases (Exercise: create use case realization, high-level components)

Step 3 - System Architecture

  • Developer guidelines, package/ns structure, basic how-to's
  • 4+1
  • Highlevel class diagram within components and subcomponents, based on loose coupling or high cohesion (Exercise)
  • Some detailed use case diagrams
  • Package/Layer diagram (Exercise)
  • Sequence diagrams (Exercise)
  • Interface definitions
  • Logical model

Step 4 - Implementation

  • Scrum Master
  • Code reviews
  • Solve issues
  • Update docs
  • Help code !?

Step 5 - Deploy

  • Physical model
  • Hardware diagram
  • Deploy strategy

End of the course

Fakta

Kurs
T1101
Längd
2 dagar
Pris
14.500 kr (exkl. moms)

Just nu finns det inga kurstillfällen. Kontakta oss för mer information.
Bookmark and Share

Förkunskaper

• It is preferred, but not required, to have some UML experience, as the design parts of the course will use UML • Preferrably have several years experience working as a developer, or have had several years experience in the IT field • Optional to have experience as architect, but even experienced architects will get useful information from this class

Kursmaterial

Course material is in English

Kontakta oss
för mer information:

08 - 587 116 10 (Stockholm)
031 - 773 07 90 (Göteborg)
040-662 20 60 (Malmö)
info@informator.se