Software Architectures and Design (5op)
Toteutuksen tunnus: 5G00DM00-3001
Toteutuksen perustiedot
- Ilmoittautumisaika
- 10.06.2020 - 20.09.2020
- Ilmoittautuminen toteutukselle on päättynyt.
- Ajoitus
- 31.08.2020 - 20.12.2020
- Toteutus on päättynyt.
- Laajuus
- 5 op
- Toteutustapa
- Lähiopetus
- Yksikkö
- Tietotekniikka
- Toimipiste
- TAMK Pääkampus
- Opetuskielet
- englanti
- Paikat
- 0 - 40
- Koulutus
- Bachelor's Degree Programme in Software Engineering
Osaamistavoitteet (Opintojakso)
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.
Sisältö (Opintojakso)
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
Esitietovaatimukset (Opintojakso)
Basic knowledge of programming.
Arviointikriteerit, tyydyttävä (1-2) (Opintojakso)
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.
Arviointikriteerit, hyvä (3-4) (Opintojakso)
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.
Arviointikriteerit, kiitettävä (5) (Opintojakso)
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.
Aika ja paikka
A block of two hours weekly on computer class. Bring your own devices along! Timing and place is on TAMK student schedules.
Tenttien ja uusintatenttien ajankohdat
There are no exams in this course.
Arviointimenetelmät ja arvioinnin perusteet
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.
Arviointiasteikko
0-5
Opiskelumuodot ja opetusmenetelmät
Lectures, exercises and going through the solutions, projects and their deliveries, discussions.
Oppimateriaalit
Links to good materials are given in the lectures / to moodle.
Main book: Len Bass, Paul Clements, Rick Kazman: Software Architecture in Practice. Third Edition. Pearson Education.
Opiskelijan ajankäyttö ja kuormitus
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.
Sisällön jaksotus
This is preliminary:
3 weeks general stuff
2 weeks for ways to visualize SW architectures
3 weeks for architecture documentation
3 weeks for studying and using design patters
4 - 5 weeks for designing and using a chosen SW architecture for a small implementation project.
Toteutuksen valinnaiset suoritustavat
-
Arviointikriteerit - hylätty (0) (Ei käytössä, kts Opintojakson Arviointikriteerit ylempänä)
Don't know nearly nothing of SW architectures and design.
Arviointikriteerit - tyydyttävä (1-2) (Ei käytössä, kts Opintojakson Arviointikriteerit ylempänä)
Understands some parts of SW architectures and design and can apply learned knowledge with the help of others.
Arviointikriteerit - hyvä (3-4) (Ei käytössä, kts Opintojakson Arviointikriteerit ylempänä)
Understands the whole area of SW architectures and design handled in the course. Can apply that information in her/his own projects.
Arviointikriteerit - kiitettävä (5) (Ei käytössä, kts Opintojakson Arviointikriteerit ylempänä)
Understands the whole area of SW architectures and design handled in the course in excellent level. Can apply that information creatively and innovately in her/his own projects. Can invent new ways of doing SW architectures and design solutions.