Study Guide

Objectives (course unit)

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

Content (course unit)

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

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

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.

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

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.

Assessment criteria, excellent (5) (course unit)

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.

Location and time

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

Exam schedules

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

Assessment methods and criteria

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 - 90
4 - 74
3 - 58
2 - 41
1 - 25

----
For second part (prototyping) each student is graded between 0 - 5 and this constitutes half of the grade for this course. Second half comes from requirements part. For prototyping part half of the grade comes from activity in individual learning tasks and half comes from project work.

Assessment scale

0-5

Teaching methods

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

Learning materials

Primary Material for the 1st part of the course:
* Wiegers, Beatty: Software requirements
https://andor.tuni.fi/permalink/358FIN_TAMPO/1kfmqvo/alma998941114205973

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

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

Student workload

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

Content scheduling

----
1. period handles requirement specifications, 2. period prototyping.

Completion alternatives

Relevant personal or working life related projects can be used to compensate either for individual tasks or larger parts of the course depending on the case.
Contact the relevant teacher about this.

Practical training and working life cooperation

Sharing experiences and best practices in concurrent IT setting projects in concurrent working life environment.

Assessment criteria - satisfactory (1-2) (Not in use, Look at the Assessment criteria above)

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.

Assessment criteria - good (3-4) (Not in use, Look at the Assessment criteria above)

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.

Assessment criteria - excellent (5) (Not in use, Look at the Assessment criteria above)

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.

Objectives (course unit)

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

Content (course unit)

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

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

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.

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

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.

Assessment criteria, excellent (5) (course unit)

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.

Location and time

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

Exam schedules

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

Assessment methods and criteria

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

Assessment scale

0-5

Teaching methods

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

Learning materials

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.

Student workload

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

Completion alternatives

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

Assessment criteria - satisfactory (1-2) (Not in use, Look at the Assessment criteria above)

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.

Assessment criteria - good (3-4) (Not in use, Look at the Assessment criteria above)

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.

Assessment criteria - excellent (5) (Not in use, Look at the Assessment criteria above)

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.