Hur hanterar man arkitektur när man utvecklar agilt? Detta är en av de frågor som vi möter hos många av våra kunder, speciellt de som utvecklar större, komplexa tekniska system. Jim Coplien är en av de tidiga pionjärerna på området.
Responsive kan nu erbjuda en halvdagskurs i ämnet med Jim Coplien.
- Datum: Fredag den 21 maj 2010
- Tid: 08.30-12.00, registrering från 8.00
- Plats: Scandic Frimurarhotellet, Linköping
- Pris: 3900SEK/person
- Anmälning: Den här e-postadressen skyddas mot spambots. Du måste tillåta JavaScript för att se den.
Modern Domain Analysis for Agile System Development
Architectural partitioning is so difficult because, in fact, there is no single best way. We want a good, clean, top-down partitioning of our system that supports comprehension, extension, and customization and evolution. Complex adaptive systems, however, have many tops, so a top-down approach rarely works. A bottom-up approach is a good way to build efficient parts with clumsy â and inefficient â connections between them.
This tutorial introduces the principle dimensions of architectural complexity: your business structures, your organizational structure, your market structure, and the nature of your enabling technologies. The course offers several models of how to organize the complexity of your system into modules that are as autonomous and maintainable as possible. What "autonomous" and "maintainable" mean are driven as much by your business structure as by any "computer science" consideration. The architecture must serve your business â and that means limits to perfection in the traditional technical measures of quality such as coupling and cohesion.
