Travelled to:1 × Australia
1 × Croatia
1 × Finland
1 × France
1 × Ireland
1 × USA
1 × United Kingdom
2 × Belgium
2 × Canada
2 × Germany
3 × Italy
Collaborated with:J.Knodel D.Rost D.Muthig J.Stammel ∅ T.Lenhart R.Carbon H.Abukwaik H.D.Rombach J.Lee E.Bouwers J.Visser C.Lima C.v.F.G.Chavez T.Keuler G.Johann M.Lindvall D.Zeckzer S.Hess S.Braun F.Kiefer D.Magin B.Weitzel H.Schmitt S.Duszynski D.Hein C.Schitter A.Eitel J.Feldhaus M.Hack D.Richter M.Trapp
Talks about:architectur (14) softwar (14) develop (6) practic (5) system (5) experi (4) evalu (4) ecosystem (3) industri (3) document (3)
Person: Matthias Naab
DBLP: Naab:Matthias
Contributed to:
2015
2015
2015
2015201420142013
2012
20122011
2008
2008
2008
2006
200620062016
2018Wrote 19 papers:
- ECSA-2015-RostWNLS #agile #architecture #case study #development #experience #industrial
- Distilling Best Practices for Agile Development from Architecture Methodology — Experiences from Industrial Application (DR, BW, MN, TL, HS), pp. 259–267.
- HCI-UC-2015-HessBFHKMNRLT #approach #ecosystem #mobile
- Building Mobile Software Ecosystems — A Practical Approach (SH, SB, JF, MH, FK, DM, MN, DR, TL, MT), pp. 165–177.
- SANER-2015-KnodelNBV #risk management
- Software risk management in practice: Shed light on your software product (JK, MN, EB, JV), pp. 592–594.
- WICSA-2015-AbukwaikNR #analysis #concept
- A Proactive Support for Conceptual Interoperability Analysis in Software Systems (HA, MN, HDR), pp. 119–122.
- WICSA-2015-NaabBLHEMCK #architecture #case study #design #ecosystem #experience #mobile #prototype #scalability #why
- Why Data Needs more Attention in Architecture Design — Experiences from Prototyping a Large-Scale Mobile App Ecosystem (MN, SB, TL, SH, AE, DM, RC, FK), pp. 75–84.
- CSMR-WCRE-2014-KnodelN #architecture #industrial
- Mitigating the Risk of software change in practice: Retrospective on more than 50 architecture evaluations in industry (JK, MN), pp. 2–17.
- WICSA-2014-KnodelN #architecture #evaluation #industrial
- Software Architecture Evaluation in Practice: Retrospective on More Than 50 Architecture Evaluations in Industry (JK, MN), pp. 115–124.
- ECSA-2013-RostNLC #architecture #developer #documentation #overview
- Software Architecture Documentation for Developers: A Survey (DR, MN, CL, CvFGC), pp. 72–88.
- QoSA-2012-NaabS #architecture #flexibility #lifecycle
- Architectural flexibility in a software-system’s life-cycle: systematic construction and exploitation of flexibility (MN, JS), pp. 13–22.
- WICSA-ECSA-2012-KeulerKNR #architecture #framework #re-engineering #towards
- Architecture Engagement Purposes: Towards a Framework for Planning “Just Enough”-Architecting in Software Engineering (TK, JK, MN, DR), pp. 234–238.
- ECSA-2011-Naab #architecture #design #flexibility #information management
- Enhancing Architecture Design Methods for Improved Flexibility in Long-Living Information Systems (MN), pp. 194–198.
- EDOC-2008-CarbonJMN #collaboration #development
- A Method for Collaborative Development of Systems of Systems in the Office Domain (RC, GJ, DM, MN), pp. 339–345.
- SPLC-2008-LeeMN #approach #product line
- An Approach for Developing Service Oriented Product Lines (JL, DM, MN), pp. 275–284.
- WCRE-2008-DuszynskiKNHS #comparison #visualisation
- Variant Comparison — A Technique for Visualizing Software Variants (SD, JK, MN, DH, CS), pp. 229–233.
- CSMR-2006-KnodelMNL #architecture #evaluation
- Static Evaluation of Software Architectures (JK, DM, MN, ML), pp. 279–294.
- SOFTVIS-2006-KnodelMNZ #architecture #empirical #towards #visualisation
- Towards empirically validated software architecture visualization (JK, DM, MN, DZ), pp. 187–188.
- WCRE-2006-KnodelMN #architecture #comprehension #empirical #visual notation #visualisation
- Understanding Software Architectures by Visualization — An Experiment with Graphical Elements (JK, DM, MN), pp. 39–50.
- ECSA-2016-RostN #architecture #developer #documentation #effectiveness #why
- Task-Specific Architecture Documentation for Developers - Why Separation of Concerns in Architecture Documentation is Counterproductive for Developers (DR, MN), pp. 102–110.
- ICSA-2018-NaabRK #architecture #case study #ecosystem #experience
- Architecting a Software-Based Ecosystem for the Automotive Aftermarket: An Experience Report (MN, DR, JK), pp. 57–64.