Software Requirements and Application Prototyping (5 op)

Osaamistavoitteet (Opintojakso)

-The student knows the basic principles of software requirements affecting software design and implementation.
-The student is able to design and implement software with fulfilling the regulations and requirements -The student manages the processes of software regulations, requirements and can design software within the context.

Sisältö (Opintojakso)

Software requirements and requlations. Functional and non-functional requirements and analysis. Prototyping

Arviointikriteerit, tyydyttävä (1-2) (Opintojakso)

Student knows about software requirements and regulations and student is able to implement a project according to the software requirements and regulations with guidance. Student is able to implement functional and non-functional requirements and analysis in a project with guidance. Student is able to implement prototyping for a given case with guidance.

Arviointikriteerit, hyvä (3-4) (Opintojakso)

Student knows and understands software requirements and regulations and student is able to implement a project according to the software requirements and regulations. Student is able to use functional and non-functional requirements and analysis in a project. Student is able to implement prototyping for a given case.

Arviointikriteerit, kiitettävä (5) (Opintojakso)

Student knows and understands in depth software requirements and regulations and student is able to implement projects diversely according to the software requirements and regulations. Student is able to exploit functional and non-functional requirements and analysis in various projects. Student is able independently to implement prototyping for various cases.

Aika ja paikka

Online - see https://lukkarit.tamk.fi for details.

Tenttien ja uusintatenttien ajankohdat

The course does not have an exam by default.
For completion options consult the instructor.

Arviointimenetelmät ja arvioinnin perusteet

Grading of the course is a weighted average of
- Attendance - notice the activity in Moodle - 20%
- Course portfolio - 30 %
- Exercises (homework assignments, group work, projects, labs) - 50%

Max 100 points. Min points for the grades:
5 - 88.0
4 - 71.0
3 - 54.0
2 - 37.0
1 - 20.0

Arviointiasteikko

0-5

Opiskelumuodot ja opetusmenetelmät

Contact sessions and activities: exercises, reports, group work, case studies

Oppimateriaalit

Dean Leffingwell: Agile Software Requirements (saatavana myös verkkoversiona)
https://andor.tuni.fi/permalink/358FIN_TAMPO/1kfmqvo/alma9910687415505973

Managing Software Requirements the Agile Way
https://andor.tuni.fi/permalink/358FIN_TAMPO/1j3mh4m/alma9911196181005973

Reference to online materials and tools provided during the course in Moodle.

Opiskelijan ajankäyttö ja kuormitus

Lecture attendance, weekly exercises, project work.
Altogether about 80-120 hours.
Effort distributed evenly to the time of the implementation.

Toteutuksen valinnaiset suoritustavat

Report of a project study and exam. Consult the instructor for details.

Arviointikriteerit - tyydyttävä (1-2) (Ei käytössä, kts Opintojakson Arviointikriteerit ylempänä)

Student knows about software requirements and regulations and student is able to implement a project according to the software requirements and regulations with guidance. Student is able to implement functional and non-functional requirements and analysis in a project with guidance. Student is able to implement prototyping for a given case with guidance.

Arviointikriteerit - hyvä (3-4) (Ei käytössä, kts Opintojakson Arviointikriteerit ylempänä)

Student knows and understands software requirements and regulations and student is able to implement a project according to the software requirements and regulations. Student is able to use functional and non-functional requirements and analysis in a project. Student is able to implement prototyping for a given case.

Arviointikriteerit - kiitettävä (5) (Ei käytössä, kts Opintojakson Arviointikriteerit ylempänä)

Student knows and understands in depth software requirements and regulations and student is able to implement projects diversely according to the software requirements and regulations. Student is able to exploit functional and non-functional requirements and analysis in various projects. Student is able independently to implement prototyping for various cases.