Fifth International Software Architecture Ph.D. The school (ISAPS 2023)
https://www.lorentzcenter.nl/international-software-architecture-phd-school-isaps.html
NOTES
(1) ISAPS is a vehicle triggered by a sequence of questions about Software Architectures
(2) The critical issues are related to the subject -- Existing cutting-edge software architecture and have nothing to do with Lorentz Center and the respectable lecturers.
(3) Many questions will be raised, and we will answer them all.
(4) Most of the existing research, development, education, and publications are harming the field of Software Architecture.
(5) This is a scientific critic.
First: The intro.
The International Software Architecture Ph.D. The school (ISAPS) is a five-day
an intensive workshop that will provide early career researchers following a
Ph.D. and practicing architects (issue (0)) from industry the opportunity to learn from
the leaders in the field, the most recent methods (Issue (1)), tools (Issue (2)), and theories produced by top research groups around the world and in industrial
environments (Issue (3)).
Looking at this intro, we have many questions, but we will come up with three for now.
Issue
(1): What are software architecture methods?
Hundreds of publications exist on software architecture models, patterns, types, processes, and others; each has many significant problems and pitfalls.
Issue (2): What are software architecture tools?
There are thousands of software architecture tools, each with significant problems and pitfalls.
Issue (3): What are software architecture theories?
Software architecture theories are about the why? Software architecture has nothing to do with what and the how-to.
Is something missing? A specific software architecture is about the How-To and has nothing to do with Why? Moreover, people have yet to learn about the What?
Second, The format of the workshop
The format combines lectures on cutting-edge software architecture topics
with hands-on sessions on industrial cases.
Software architecture exists but is not cutting-edge,
Is this can be proven? YES.
The preliminary program includes the following:
Day 1: Software architecture design decision-making.
First: All the existing software architectures are instance-oriented.
Second: Each concept or domain is a unified pattern. For example, each domain of knowledge consists of unified patterns.
Concepts: Software, Architecture, Design, Decision.
Questions for each of the concepts?
What is the ultimate goal?
What are the unified functional requirements?
What are the unified nonfunctional requirements?
What is the responsibility?
What are the roles?
What is the behavior?
And 100 more questions.
Domain Knowledge: Software Architecture, Decision-Making
Questions for each of the domain knowledge?
What is unified domain analysis?
What are the unified functional requirements?
What are the unified nonfunctional requirements?
What is the unified standard?
What is adaptability?
What are the reusability and usability?
What is dynamic scalability?
And 100 more questions
Day 2: Architecture-Implementation alignment and Architecting challenges in the era of microservices and agile.
Programming mentality which leads to reinventing the wheels and maintenance nightmare
Day 3: The role of architecture metrics and Continuous architecture.
What are the architecture metrics?
Quantitative metrics of exciting software architectures are useless because of the problems the system inherits from bad programming and erroneous data.
To have measurements and assessments, we must know the unified and executable nonfunctional of the system we architect, and unfortunately, architects do not know them.
Day 4: The C4 model for visualizing software architecture and Architecture Design Records in practice.
C4+1 Architectural View Model, UML, Graphical notation techniques!
What are the differences between techniques and tools?
We will address many questions about C4 Model & UML later.
Day 5: The role of the architect and Architecture by and with autonomous
teams.
We will address many questions later.