Hello, this is the start for the third part of the lecture and it's intended to be in
parallel to part two.
In this part we will discuss the life cycles, the elements of the life cycle and this is
done in parallel to the quality attributes and their tactics to resolve them, to implement
them and part two and part three, this order, the sequence is the sequence of the book.
However in this lecture we will consider them in parallel and this is the prequel to do
the introduction.
In the lecture it's structured in this way as you see here.
So we start with analysis and then go through design documenting assessment evaluation.
I always will show you this structure here and this shows the embedding in the oval sequence
of activities.
Either if you go agile or in waterfall it's always this sequence of activities.
First you have the idea of what to do, for example for business system, business modeling
and then you find out what is required from the software development for a software system
and then you do the actual design and this is what software architecting is about and
next step is you implement something and you integrate the parts together to a hole and
then you deploy it, put it into operation and then it's operated.
Even if you do this in operation, in iteration sorry, in an incremental way it will be always
this way because before you can design something you need requirements and the design is not
the end, it has to be implemented.
So if we look in more detail what is performed in architecture or the blue things are considered
in this lecture, in this module, in this course.
So we start, the input is threefold, the input are architecture significant requirements,
this is what we call architecture analysis, go to the previous slides here, this is 3.1
so I just notice it here, 3.1, lecture 3.1, then we do architectural design, this is here
lecture 3.2, this is lecture 3.3, then architecture evaluation is lecture 3.4 and usually this
is not the end, it's done in an incremental way, you do the next decisions, you do the
next level of refinement and again you do some decisions, you have to write it up, you
have to be able to show it to someone and then it says and as long as you aren't ready
it will be performed this way.
For doing the decisions we reuse things and the things for reuse are somehow in a collection
in a repository, I call this repository because of its heterogeneous structure, I call it
architect's toolbox and this is considered in section 2 where the elements of all the
tactics, design patterns are discussed there.
I think it's 2.3, hopefully this is right, okay and then we go to implementation, this
is 3.5 and what is architectural depth, what is architectural erosion that's discussed
in lecture 3.5 as well, so this is so far this will be the structure, the sequence of
the elements in part 3, however part 2 will be somehow in parallel because we always consider
things for example for performance, we have some tactics here, we have specific architectural
requirements and we have certain ways of assessing the architecture if it's quick enough, if
the management of resources is appropriate.
I want to show you, this picture will be shown again with the start of each section of part
3, I want to show you and discuss the same issues from a different perspective.
I use this drawing from the paper of Hofmeister and colleagues where you had the factor tables
from which we will discuss today and they show it quite differently or somehow differently.
So it starts with some requirements, we already know, we have three types of requirements,
so one is the constraints of the quality and the functional requirements but they have
them here with a different wording, so they split it up into context of the things around,
we usually have them as constraints because you have to fulfill them, you have to meet
the requirements and you have some goals, functional and quality ones and they are analyzed,
this is in our lecture, this is in the lecture, it's 3.1, we know that.
In the seminar we have different seminar groups, we will go through them later.
So in the lecture the outcome of the analysis are architectural specific requirements and
we have them twofold here, two times, one is the ordinary way of doing the architecture,
architecting this as it's shown in the other, in this spiral drawing and here architectural
synthesis, this is regarding the lecture, this is design documenting, lecture 3.2, 3.3
and then we have architectural evaluation, this is if we go back to the list here, this
is 3, let's make this notation here, lecture 3.4 and then all the other things are done later,
3.5 is here. Let's align this with the seminars, we have two different seminars,
the seminar, I do a small legend here, green lecture,
I use blue for that.
So the seminar groups by Jan Christian Daman will deal with documentation of an architecture,
so it's more or less here, this is here in this block, it's documentation
and of course it's somehow related even with the analysis what has to be described
and which goals have to be met so when it is good so it's somehow evaluation is covered
and if we go for the blue ones then we have different seminars for the groups for here
for the blue ones we have seminar task one and three they are in the architectural analysis
and seminar about design, if you look at the seminar schedule, let me release,
it's hard for me to switch to this, let's switch, so if you look at this seminar schedule of seminar
groups two, three and four you notice okay in topic three this is analysis topic two
architecture resources that's somehow part of the of the analysis of the synthesis and then
we have three and four and five in the other thing let's switch again and make
I add them to our slide, let's switch here
so here we have number two, number four, number five and architectural evaluation
is here, seminar number six, so this is just again for the mapping of both
and now let's start with the first step of the life cycle which is architectural analysis
and architectural analysis is about significant architectural requirements
so far let's switch to the next video