Skip to main content

Software Architectures and Design (5cr)

Code: 5G00DM00-3003

General information


Enrolment period
30.07.2022 - 28.08.2022
Registration for the implementation has ended.
Timing
29.08.2022 - 23.12.2022
Implementation has ended.
Credits
5 cr
Mode of delivery
Contact learning
Unit
ICT Engineering
Campus
TAMK Main Campus
Teaching languages
English
Degree programmes
Bachelor's Degree Programme in Software Engineering
Teachers
Petteri Jekunen
Person in charge
Erkki Hietalahti
Course
5G00DM00

Objectives (course unit)

1. Student understands the ideas and principles of all main topics of the course.
2. Student can apply the previous information in typical daily tasks of a software engineer.
3. Student develops to an attitude of continuous learning of Software Engineering topics and applying this new information in her/his tasks.
4. Student has the right attitude towards working in a project group as a responsible group member.
5. Student understands and adapts to the demands of customers, his/her own company and managers in it, market forces as well as demands of the society.

Content (course unit)

Software engineering overview and processes, software development life cycle, software project planning and management, software requirements management, system modeling, software architecture design, software detailed design, analysis & design tools, software design strategies, software user interface design, software design complexity

Prerequisites (course unit)

Basic knowledge of programming.

Assessment criteria, satisfactory (1-2) (course unit)

Student knows about software engineering and about its processes and about software development life cycle. Student is able to implement software project planning and management, software requirements management and system modelling with guidance. Student can implement simple software architecture designs and simple software detailed designs. Student is able to use some analysis & design tools and software design strategies. Student is able to implement software user interface designs with guidance and knows about software design complexity.

Assessment criteria, good (3-4) (course unit)

Student knows and understands software engineering and its processes and software development life cycle. Student is able to implement software project planning and management, software requirements management and system modelling. Student can implement software architecture designs and software detailed designs. Student is able to use analysis & design tools and software design strategies. Student is able to implement some software user interface designs and understands software design complexity.

Assessment criteria, excellent (5) (course unit)

Student knows and understands in depth software engineering overview and its processes and software development life cycle. Student is able to implement diversely software project planning and management, software requirements management and system modelling. Student can implement independently software architecture designs and software detailed designs in various situations. Student is able to use diversely and independently analysis & design tools and software design strategies. Student is able to implement various software user interface designs and understands in depth software design complexity.

Location and time

Contact learning on Wednesdays 11:15 to 14

Exam schedules

There are no exams in this course.

Assessment methods and criteria

Every phase (5) is graded between 0 - 5. The total grade of the course is an average of these weighted on their work amount; average is rounded up.

Assessment scale

0-5

Teaching methods

Lectures, exercises and going through the solutions, projects and their deliveries, discussions.

Learning materials

Fundamentals of Software Architecture by Mark Richards, Neal Ford
Head First Design Patterns, 2nd Edition by Eric Freeman, Elisabeth Robson
Additional materials in Moodle.

Student workload

You should study this course twice as much on your own time compared to the time used for lectures. To be more precise: for 1 op you should work 27 hours.

Content scheduling

Introduction to SW Engineering Processes
Software Design
Software Architecture

Completion alternatives

n/a

Practical training and working life cooperation

n/a

International connections

n/a

Further information

n/a

Go back to top of page