Académique Documents
Professionnel Documents
Culture Documents
Brief Motivation
Complexity in software development is increasing The level of abstraction is rising
Lower level jobs become a routine, more skills are needed to handle the bigger picture
General
Course targeted for 45 participants Prerequisites must be met
T-76.3601 AND T-76.4602
T-76.3601 Introduction to Software Engineering T-76.4602 Software development methods If you do not have completed those courses (and there are > 45 of you), we may need to drop out some of you please be prepared
Learning Principles
The subject matter is abstract, hard to master
To a question there hardly is a right answer! Typically, you do not even have the questions!!! You will not become experienced architects by taking the course however, the course should help you if you want to become or need to talk to one
To think about
What is your contribution in this process of learning?
Preparing for the sessions, making the group discussions fruitful, seeking for answers when confused,
Teaching methods
Active discussion on session (= class room meetings are NOT about lecturing only) Group work around the case example
To foster discussion on course topics Tool for concretising course content Not a real architectural design task process is more important than resulting design Thinking of a complex problem, means for addressing it, making decisions, ...
Feedback
Feedback discussions during presentation sessions In addition, special evaluation sessions are organised
Oral exam
An exam with direct feedback what and how students have learned Feedback to students about misconceptions and vaguely understood issues
Pass the oral exam for the course Fill in and return the feedback
Instructions will be available close to the end of course
11
Sessions
Course language is English, you may ask in Finnish if needed On Wednesdays 1618, lecture room A136 Lecture slides will show up in Noppa Course book
Rozanski, Nick and Woods, Eoin: Software Systems Architecture. Addison-Wesley, 2005.
12
Exercise
Idea
To be done in groups of 3 To address central architectural issues in group discussions around the case product All groups work on the same case individually you are not expected to produce the same architecture design! Justify your decisions and retain the consistency in your design documentation Whys are important!
Will be coached separately and graded slightly differently Perhaps not easier way through the course but most probably an interesting one
13
Click
More info
Course uses Noppa: https://noppa.tkk.fi/noppa/kurssi/t-76.5150/
Dropbox
Used for the returns By invitation (for groups)
SoberIT / Tomi Mnnist
Minimal requirements
To pass the exam the student needs to show that he/she masters at least half of the course material by explaining selected topics and answering questions
Setting
Examiners
Selects the discussion topics and asks questions
16
Register your group (or your own info even if you do not have a group!) via e-mail by sending the following information to t765150@soberit.hut.fi
Your names Your e-mail addresses Your student numbers Whether you want to volunteer as a Stakeholder group Preferred time slots for the oral (full hours, see Noppa), give multiple possibilities Time slots for the feedback session (see Noppa for details) Deadline 25.1.2012 at 18:15 (NB: different time as for the other deadlines!)
Have Fun!