The life of a software architect is a long (and sometimes painful) succession of suboptimal decisions made partly in the dark. Philippe Kructhen
Motivasjon
Hvordan takler man wicked design problemer?
Hva gjør du når systemet av systemer er så komplekse at det er umulig for en person å få en detaljert oversikt?
Vi ønsker dine innspill om ulike teknikker som kan hjelpe.
De kan være teknikker som du bruker i praksis eller bare nye ideer som du tror viser potensial og at iasa.no medlemmer bør være informert om.
Vi forventer ikke "svaret" så alle innspill rundt problemstillinger, mulige løsninger, og interessante ideer i bransjen som kan føre til løsninger er velkomne
For eksempel:
- Systems Thinking
- Complexity Theory (Cynefin framework)
- Organisation Theory
- System of Systems Design
- Viable Systems Model (VSM)
- Self-organizing systems
- osv
Sende ditt forslag for 10-15 min lyntale til: iasa-styret krøllalfa iasa dot no
Praktisk
- Tid: kl 18:00
- Sted: Scotsman, 2. etg.
- Påmelding: TODO
- Trådløst nett
- SID: kontor
- Passord: blir opplyst på møtet
Ressurser
All complex systems fail, by some measure of the word "fail," with consequences ranging from benign to catastrophic. This article examines the process of to triage in the face of a failing system. Software-intensive systems bring their own wickedness to the world because they have an essential complexity. They bring fundamental challenges to discrete systems, since they exhibit noncontinuous behavior, often embody a combinatorial explosion of state space, and may be corrupted by unexpected external events. Furthermore, as a discipline we lack the mathematical tools and as humans we fall short of the intellectual capacity to model the behavior of ultralarge discrete systems. Furthermore, discrete software-intensive systems often exhibit nonlinearity, broken symmetry, and, due to nonholonomic constraints, what is called localized transient anarchy.
