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.
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.
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.
Esa Kujansuu
Wiegers, Beatty: Software requirements
https://andor.tuni.fi/permalink/358FIN_TAMPO/1kfmqvo/alma998941114205973
Leffingwell: Agile Software Requirements
https://andor.tuni.fi/permalink/358FIN_TAMPO/1kfmqvo/alma9910687415505973
Heath: 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.
Contact sessions and activities: exercises, reports, group work, case studies
Grading of the course is a weighted average of
- Attendance - 20%
- Period 3 - 40%
- Period 4 - 40%
Max 100 points. Min points for the grades:
5 - 88.0
4 - 71.0
3 - 54.0
2 - 37.0
1 - 20.0
English
14.01.2022 - 26.04.2022
15.11.2021 - 09.01.2022
5 cr
19I260E
0 - 62
Outi Tuisku, Petteri Jekunen
ICT Engineering
Bachelor's Degree Programme in Software Engineering
TAMK Main Campus
0-5
Report of a project study and exam. Consult the instructor for details.
The course does not have an exam by default.
For completion options consult the instructor.
Lecture attendance, weekly exercises, project work.
Altogether about 80-120 hours.
Effort distributed evenly to the time of the implementation.
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.
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.
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.