1. Software Architectural Assumptions in Software Architecting Chen Yang a,b, Peng Liang a, Paris Avgeriou b a State Key Lab of Software Engineering, Wuhan University, China b Department of Computing Science, University of Groningen, The Netherlands

2. Outline 2  Concept  Motivation  Questions  Related work  Our work  Future work

3. What is Architectural Assumption (AA)? 3  A type of architectural knowledge A type of Architectural Design Decision as well as the reasons for making the decisions Explicit documentation of the unknowns or the expectations to provide a context to decision making Typically assumptions about the structure of the system under development

4. What is AA? 4  The AA concept is not new  No widely accepted definition of this concept! Academia Industry

5. Why should we manage AAs? 5  Uncertain things (e.g., requirements)  Numerous AAs exist in projects  Usually implicit and undocumented  Originally invalid AAs Personal experience and knowledge  Valid AAs turn to be invalid Changed requirements, architecture, and project context  Different understanding Different stakeholders Researchers vs. Practitioners

6. Why should we manage AAs? 6  Problems of not managing AAs Architectural mismatch Misunderstanding of architecture Considerable time and effort

7. What, When, and How 7  What kinds of projects are suitable for introducing AA management?  What AAs should be managed?  When to manage AAs?  How to manage AAs? Context dependent

8. Related work 8  AA definition  AA classification  AA activities  Methods and tools for AA management (e.g., identification, recording, and recovering)  Lessons learned for AA management

9. Our work 9  Chen Yang, Peng Liang. Identifying and Recording Software Architectural Assumptions in Agile Development. In: Proceedings of the 26th International Conference on Software Engineering and Knowledge Engineering (SEKE), pp. 308- 313, 2014.  Chen Yang, Peng Liang, Paris Avgeriou. A Systematic Mapping Study on the Combination of Software Architecture and Agile Development. Journal of Systems and Software, 2015. (under review)  Chen Yang, Peng Liang, Paris Avgeriou. A Survey of Software Architectural Assumptions. Information and Software Technology, 2015. (under submission)

10. Future work 10  The state of the art of AA management from the practitioners’ perspective?  How to identify and record AAs in software development?  What is the process of AA management?  How to trace AAs in software development?  How to combine AA management and agile development?

11. 11 Thanks!