Close
'Software architecture: between rigid process and "somehow I manage" approach', byJasmin Jahi膰 - Director of Studies in Computer Science at Queens鈥� College, University of Cambridge
Speaker Bio
Jasmin Jahi膰 is a Director of Studies in Computer Science at Queens鈥� College, University of Cambridge. He is also a visiting researcher at the Department of Computer Science, University of Cambridge. He completed his PhD with the topic "Supervised Testing of Embedded Concurrent Software" at University of Kaiserslautern in October 2020. For 7 and a half years, he worked as a researcher and a project manager in Embedded Software department at Fraunhofer Institute for Experimental Software Engineering, Kaiserslautern, Germany.
His main research interests are software system architectures, application of AI in software engineering, and concurrency in software systems. He is running a course 鈥淢anaging software architecture鈥� over the Cambridge Advance Online platform. He also teaches a course 鈥淪oftware Architectures for Embedded Software Systems鈥� at the University of Kaiserslautern. Besides his academic engagements, he works in industry as a solution architect.
Abstract
There are several definitions and understandings of what software architecture should truly cover. What all these definitions eventually aim to communicate is that there should be practices and processes that will make success in software projects reproducible and ensure desired quality properties in software systems. However, they differ in focus and rigidity with which those practices and processes should be applied. Consequently, engineers and architects are not sure how much software architecture is enough, what are the benefits of software architecture, how to avoid unnecessary overheads, and at the end what a software architect should be really responsible for.
In the first part of this talk, we will make a brief overview of architectural processes and their desired outcomes. We will also discuss what happens if there is no explicit software architecture in projects (known as 鈥渟omehow I manage鈥�).
In the second part of this talk, we will discuss the overhead that software architecture processes introduce.
Finally, in the third part, we will make an overview of the idea of customisation. Instead of applying software architecture by book and always in every situation, we will discuss how to reason what are the priorities 鈥� what are the problems that we aim to solve. In summary, how to maximise our benefits and minimise the overhead resulting from applying software architecture.
Archived Media
听触 厂濒颈诲别听诲别肠办
听