From WICSA Conference Wiki

Contents 1 WS4 - Architecture Documentation Frameworks 1.1 Contributions 1.2 Topics to consider 1.3 Summary Notes 1.3.1 Two breakout groups: 1.3.2 Updating IEEE 1471 (ISO/IEC 42010): 1.3.3 Extending the model:

WS4 - Architecture Documentation Frameworks

Session Chairs: John Klein and Rich Hilliard

Wednesday 20th February, 15:30 - 17:30.

Contributions

• 3+1 Views of Architecture (in 3D) - An Amplification of the 4+1 Viewpoint Framework. Mark Kennaley
• Updating IEEE 1471: Architecture Frameworks and Other Topics. David Emery, Rich Hilliard

Topics to consider

Please join the discussion and add to this list.

Software architecture description (AD) has used the paradigm of multiple views since Kruchten's 4+1 view model (1995).

• What's new in AD?
• Are there new documentation paradigms that can help Architects and system stakholders?
• What have we learned as a community since IEEE 1471 was standardized (in 2000)?
• Consider the paradigm:
  • Stakeholders have Architectural Concerns which drive selection of Viewpoints which are used to create Views (as embodied in IEEE 1471).
  • Are there dimensions to capture that do not fit this paradigm?
• Are there useful architectural viewpoints that are ready to be standardised?
• How do the practices of software architectural description, interact with and apply to Systems Architecture and Enterprise Architecture?

Summary Notes

This is my attempt to distill a summary. Please add, react and correct. User:Rh

Two breakout groups:

• architecture documentation in practice:
  • What do architects really do?
• beyond software-intensive systems
  • Trend: moving description practices from software architecture to systems (SA) and even enterprise architecture (EA)
    • need for new viewpoints
    • governance, planning

Updating IEEE 1471 (ISO/IEC 42010):

• keep it simple
• usable in agile, lean contexts
• sustainable documentation:
  • can we move beyond document-centric description practices to

repositories, reasoning frameworks as underlying paradigms

• keep it simple => plug ins rather than adding to standard:
  • 3+1(3D), ...

= good argument for introducing "architecture frameworks"

Extending the model:

• are business values (just) concerns or (something new) first-class entities?
• decisions and views: new viewpoint or overlay on other viewpoints?
  • enterprises need decisions too
• inter-view relations
• levels of realisation