Professional Software Development (10 op)

Osaamistavoitteet (Opintojakso)

The student knows the requirements and practices for developing software in a long run, what different roles and responsibilities are involved in professional software development and production. The student is able to participate in software development in various roles.

Sisältö (Opintojakso)

Conducting software development work as part of a development team. Producing and maintaining production ready software. Deploying new versions of the software to different environments. Building and developing tools and practices for continuous delivery. Creating and updating documentation. Designing and refactoring the system for better quality by applying the common software architecture styles and design patterns. Implementing and maintaining tests at different levels, integrating the tests into the automated deployment.

Before taking the course, the student is assumed to possess decent understanding and some practical skills in the most common areas of professional software development including intermediate level programming experience in one or more modern programming language, implementing software in some modern context like web, mobile, or embedded systems, implementing pipelines for continuous development and delivery and software testing. The course is meant to be one of the last courses where earlier studies or skills gained elsewhere are put together to a comprehensive modern software development process.

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

The student knows the basics of requirements for professional software development work.
The student is able to operate in a professional software development team with guidance.

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

The student knows the basics of requirements for professional software development work.
The student is independently able to operate in a professional software development team. The student knows the tools and technologies required and know how to use them.

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

The student knows what is required and what different roles, responsibilities and activities exist in continuous high quality software development work. The student is successfully and independently able to operate in a professional software development team. The student knows the tools and technologies required and knows how to use them.

Aika ja paikka

Tuesdays 2 to 5 pm online using the Teams of the course.
Thursdays from 11 to 2 pm in TAMK campus. See the calendar for exact class room.

Tenttien ja uusintatenttien ajankohdat

No exam in the course.

Arviointimenetelmät ja arvioinnin perusteet

Course will be split to 3 parts each of which separately assessed.​

The purpose is to provide formative feedback to the students during the course rather than giving one final grade after which it is not any more possible to affect to the grade or take any corrective actions.​

Assessment will be transparently in Moodle and consists of ​
* Attendance​
* Results/Skills performance​
* Personal and project group "professionalism"​

Evaluation is based on deliverables and outcomes of the course and quality of the project and team work skills and commitment throughout the course. The final grade will be based on project teams performance but mainly on personal contribution including
* Tangible results and outcomes
* Performing results of work during the course
* Attendance
* Working hours - amount and quality of tracking records
* Technical, documentation, project tools artifacts
* Project Work (skills, attendance, commitment, contribution, sharing information and supporting team)

Exceptional performance in any of the areas mentioned may result in a better grade than induced from the default rubrics.

Arviointiasteikko

0-5

Opiskelumuodot ja opetusmenetelmät

Lectures, project meetings, project work both independently and in project teams. Visiting lectures.

Oppimateriaalit

Tools used will be: Atlassian Cloud project tools Jira and Confluence, TAMK Teams and Moodle.
For hours tracking some online tool like Clockify.

Further details will be announced during the course.

Opiskelijan ajankäyttö ja kuormitus

10 cp * 27cp = 270 hours of work - includes lectures, project meetings and independent project work.

Sisällön jaksotus

The course is split to three phases for assessment.
However the content will be phased according to the tasks given by the customer for this course that is the TAMK FieldLab.

Toteutuksen valinnaiset suoritustavat

Contact the instructors and ask for permission to the Moodle space containing instructions for alternative completion of the course.

Harjoittelu- ja työelämäyhteistyö

Visiting lectures from working life representatives.

Kansainvälisyys

Through the project partners of FieldLab.

Lisätietoja opiskelijoille

This course does not officially mandatory prerequisites. However recommendation is that following courses have been completed before joining this course:
* Web Software Production
* Full Stack Web Development
* Server Technologies
* Software Architectures and Design
* Software Implementation and Testing
* Software Requirements and Application Prototyping
* Software Project

This is the last course of the degree programme. Students are assumed to be equipped with the overall competence gained by completing the majority of the degree programme.

Arviointikriteerit - hylätty (0) (Ei käytössä, kts Opintojakson Arviointikriteerit ylempänä)

Performance in the evaluation criteria areas not in approved level.

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

Performance in the evaluation criteria areas in satisfactory level.

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

Performance in the evaluation criteria areas in good level.

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

Performance in the evaluation criteria areas in excellent level: The student produces professional level outcomes in the course. These can be technical results like code or configurations and setups or project work artifacts. Student participates actively to project meetings and to the work of the project teams and is committed to produce quality results in the course. Student records working hours as required and the amount of hours matches the size of the course. Students understands the versatile requirements for professional level software development and shows active attitude and concrete actions to support and improve both the results and working practices to reach high quality working standard.