Vanligvis vil CTRL + + tastene kunne brukes for å øke størrelsen, og CTRL + - for å redusere den.
Har du hjul på musen, kan du bruke CTRL sammen med hjulet for å justere størrelsen. På Mac kan du bruke CMD + + og CMD + -.
Dette kurset har ingen fremtidige kursdato(er) oppført. Bruk skjemaet for å kontakte kursholderen for mer informasjon.
Is this the course for you?
Designing software given a vague set of requirements and a blank sheet of paper is a good skill to have, although not many people get to do this on a daily basis. However, with agile methods encouraging collective ownership of the code, it’s really important that everybody on the team understands the big picture. In order to do this, you need to understand why you’ve arrived at the design that you have.
In a nutshell, everybody on the team needs to be a software architect.
This is a two-day training course about pragmatic software architecture, designed by software architects that code. It will show you what “just enough” up front design is, how it can be applied to your software projects and how to communicate the big picture through a collection of simple, effective sketches. Aimed at software developers, it fills the gap between software development and high-level architecture that probably seems a little “enterprisey” for most developers.
Our Approach to Training
The course is interactive, with a combination of presentation, group discussion and group working. Throughout the course you’ll solidify everything you learn by defining the architecture for a small software system through a series of exercises focused around a software design exercise and case study.
Is there a practical element?
Yes, you’ll be broken up into groups and asked to design a small software system from nothing but a set of requirements and a whiteboard. This includes:
•Introductions and setting the scene
•What is software architecture?
◦Architecture and software architecture
◦Design versus architecture
◦The importance of software architecture
•The software architect role
◦Software architects in the development team
◦Software architecture role versus lead developer role
◦The role and responsibilities
◦Avoiding “ivory towers”: collaboration and coaching
◦Designing software given a blank sheet of paper
•Software design exercise (iteration one)
◦Reviewing the diagrams from the software design exercise
◦UML versus informal sketches
◦A lightweight approach for effective NoUML sketches
•Software design exercise (iteration two)
◦The importance of documentation
◦Project and documentation stakeholders
◦A lightweight approach for software documentation
◦Alternative approaches for documenting software
•Software architecture in the development lifecycle
◦Software architecture in waterfall, iterative and agile approaches
◦“Just enough” up front design
◦Evaluating software architecture and prototypes
◦Guidance for doing “just enough” in the real world