Student is able to use most of the software engineering skills needed in solving the real customer problem. She/he is able to understand and document customer’s needs and to propose appropriate software solutions. Student is able to independently acquire unknown technology knowledge and skills. She/he learns to evaluate and choose between technologies and methods. She/he is able to take personal responsibility over a certain part of the commonly created solution. Student is able to share acquired knowledge to other members of the team or course.

Student can, as a member of the team, implement a valid and ready-to-use solution to the customer’s problem.

This course will be implemented as a project, with project management methods. Student will sign a project contract with Haaga-Helia at the start of the course. Students will be assigned to certain teams based on prior knowledge, available projects, required and mastered language (Finnish and/or English) and needs of each project.

Students will implement and demonstrate ready-to-use solutions to the customer. Students will learn the needs of the customer, specify and plan the solution and agree with the customer upon the used technologies, that are the best-suited ones for this problem, considering also the team’s initial skill level and learning goals.
1. Project assigned by the commissioner (customer company or organization)
2. Project work management, change management and contract principles
3. Project goal related development tools, environment and documentation practices provided by the commissioner.
4. Software development process models and methods 5. Interaction, tutoring and presentation skills

This course can be completed in following three ways:
a. Active participation in the project with mandatory presence in the project work lab room.
b. Participating large software project in student’s employer’s organization (s.c. Educationalisation)
c. Recognizing and validating prior learning (RPL)

Recognizing and validating prior learning (RPL)
Student will devise a teaching plan and teaching material about a technology or method that is topical. Student will give an expert lecture about a large software project that he/she has actively participated, describing its development method, practices, principles and technical solutions. The lecture and its material will be assessed.

Participation in this course requires signing a separate agreement.

Working life connections:
The software projects on this course will be commissioned by a customer company or organization.

Internationality:
Teams consist of both Finnish and multinational students. All used materials, technologies and methods are international.

Before attending this course, students must have completed the courses Server Programming, Data Management and Databases, and Software Project. Or student has obtained corresponding skills. Front End Development and Mobile Development course skills are also needed.

Note: This course is meant only for software development oriented students. Furthermore, students cannot take this course and other big 5. semester project course (Digital Service, Business, Infra) at the same semester as the course schedules for all these are put on the same times on purpose, and attendance is mandatory.

Accepted grades 1-5

Assessment will be based on student’s skills and efforts in the above-mentioned course contents. The emphasis of the grade will be the following:
- Researching new technology and tutoring others 15%
o Student will take responsibility of studying one or more technologies needed in the project and teaching it/them to the others e.g. in a workshop.
- Project management and project final essay 35 %
o Student has many role- or competence-based tasks and responsibilities in the project. Students devise and maintain appropriate project management and progress monitoring documentation and take care of project trackability and traceability both from internal and external controls’ points-of-view. Student reflects his/her as well as the team’s actions in the final essay.
- Appropriate documentation of the results and the technical solution that fulfills customer’s needs 50 %
o Often most of the costs of an information system come from maintenance and changes. Also, the future developers of the system are different from the original developers. Thus, we put a big emphasis on the quality of the documentation, source etc. code, and automated testing and continuous integration – the professional development pipeline.
o Quality of the documentation does not mean lengthy or all-covering documentation, but that needed and most valuable information is available and only that. Also, high-quality code is often self-explanatory.

Examples of results and tasks that will be evaluated per project team
- Software requirements: defined, audited, and accepted by the customer
- Technical requirements: defined, well-argued, and accepted by the customer
- Source etc. code: in common version control system
- Testing: testing planned, plan accepted by the customer, corresponding tests run, and test report published
- Project and work management: appropriate project management (external control) and agreed practice (internal control) documentation, following the agreed timelines, and sound communication.

The Commissioner gives evaluation of each of these parts or results

Examples of results and tasks that will be evaluated per each student
- Integrity and trustworthiness. Taking responsibility for oneself and of the team.
- Research and tutoring: The technology that was the responsibility of the student has been taken into use in the team appropriately. Technology was taught to others based on the need. Student has been able to reflect his/her own responsibility area.
- Development tasks: The student’s completion of the responsibilities in planned timeframe (implementation days, sprint, …) and the quality awareness and assurance (e.g. definition of done).
- Project final essay.

Grade-wise criteria
Discussed in the beginning of the course. Each grade adds more requirements in both quantity and quality.