You are on page 1of 9

T-76.

5150 Software Architecture

SoberIT / Tomi Mnnist

Todays agenda Course practicalities Problem domain modelling and exercise

SoberIT / Tomi Mnnist

T-76.5150 Software Architecture


Course Practicalities Spring 2012

SoberIT Tomi Mnnist

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

Software Architecture (SA) provides the big picture


SA is a link between problem and solution In SA design the first design decision are being made Decisions need to incorporate views of different stakeholders Architecturally significant design decisions are hard to change It is the responsibility of the software architect to decide what is architecturally significant and seek for answers

SoberIT / Tomi Mnnist

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

All special cases need a separate approval


Email us and explain why you should be approved
SoberIT / Tomi Mnnist

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

Goal is to provide students with a learning environment for such a topic


The point is not to pour knowledge on you and hope it sticks
Goal of being more student-centred than teacher-centred

Teaching methods are selected and developed to match a tough topic


We are putting some effort in the course and your feedback is valued Course is (being) designed for those who want to learn

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,

Who is responsible for the success of your learning?

SoberIT / Tomi Mnnist

Expected learning outcomes


Students will
Learn about addressing an open problem Understand the basic architectural concepts and apply them in software architecture design Model and document architecture and architectural decisions consistently and rigorously Experience architecture design in an iterative manner, learning on the way Learn to present architectural design decisions and justify and evaluate them

SoberIT / Tomi Mnnist

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, ...

Group (internal) meetings


Expose rather abstract concepts to your own thinking Discuss, ask, think aloud, explain to others, take responsibility, help others

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

SoberIT / Tomi Mnnist

Passing the course


Passing the exercise
Return all assignments in time
Deadlines are strict!

Pass the oral exam for the course Fill in and return the feedback
Instructions will be available close to the end of course

Final grade (max. 100 p) =


50 from exam, 30 from final delivery, 10 from participation on regular sessions (mainly own presentations), 10 from final evaluation session

A group or an individual may be dismissed from the course


Failure to present when needed, unacceptable intermediate work, poor performance, complaint from other group members, etc. A warning will be given and a hearing organised

SoberIT / Tomi Mnnist

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.

Additional reading material available online


More information in Noppa
SoberIT / Tomi Mnnist

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!

Special kind of group(s): Stakeholders


Complete the exercise differently working as stakeholders to the others
Volunteers for this tasks are asked for

Will be coached separately and graded slightly differently Perhaps not easier way through the course but most probably an interesting one

Discuss, think what is important


In real life, customer requirements, business case etc. information may often be nonexistent, incomplete, incorrect and contradictory There may not be a clearly defined problem to which seek a solution It is more about understanding what are the aims and make suggestions and decisions towards them

The work on exercise starts already today!


SoberIT / Tomi Mnnist

13

Exercise phases (Assignments in Noppa) Deadlines are strict!

Click

SoberIT / Tomi Mnnist

People and additional info Lecturers:


Prof. Tomi Mnnist and Varvana Myllrniemi
<t765150-teacher@soberit.hut.fi> <t765150@soberit.hut.fi>

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

Oral examination, general


Content
Lectures, book, additional material as described in Noppa

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

Students as a group (the exercise group)

Q&A / Discussion kind of session Grading


Each student gets individual grade Grading is based on the students demonstration of his/her knowledge during the exam The exam will be graded right after the session by the examiners and results told the students

Exams will be organised on on May 711

SoberIT / Tomi Mnnist

16

The next steps


Find a group of 3
The same group is used throughout the course (also in the oral exams) Contact course staff if you have trouble finding a group

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!)

SoberIT / Tomi Mnnist

Our journey to Software Architecture is about to begin

Have a Safe Trip, Good Luck and

Have Fun!

You might also like