Change log:

14.06.2017 new 2017-18 page created / HSten

TIE-13106 (TIE-13100) Project Work on Pervasive Systems 2017-2018

Welcome to the course's customer web site! On this page:

Course basics, Schedule, Project proposals Customer instructions

Course basics

TUT ICT project course seeks good topics from the industry

The students, usually during their 4th year, attend a course to practice professional development project in teams of 5-7 students. This course has a long tradition of teaching future professionals about fundamentals of realistic software development projects. Many companies and other stakeholders have collaborated with us on this course in the past. In this way, the student teams have realistic topics to work on and they have produced useful products for the stakeholders.

Some key principles of the course:

  • We encourage cross-disciplinary projects. In addition to software engineering students, many teams will include students from other areas of expertise, e.g., security, user experience, and hardware design (e.g., FPGA, SoC).
  • Iterative/agile approach with active listening of the customer will be assumed.
  • Teaching material will be in English, but the language inside the project may also be Finnish.

We want to continue the long tradition of collaboration with the local industry on this project course. The teams have developed useful systems and the participating companies have learned to know new talents.

Schedule

Note: The schedule is planned for year 2017-2018. There might be some content and schedule changes coming.

15.06.-27.08. Project proposals to harri.sten(at)tut.fi (one A4-paper/proposal)

30.08. Course starts. First lecture for students

30.08-05.09. Groups/teams are formed by students.

06.09. Customer pitches. 16:15-18:00 TB109. Customers will/can tell shortly (~5 min) about their topics.

06.-13.09. Student teams are selecting projects to be implemented and taking first contact to customers (agreement with customer)

14.09.- Official start for projects, starting with gathering requirements and creating first version of product/project content (backlog)

10.10. Deadline for project teams. Sprint 0 ends. Project plan ready (sprint plan, product backlog, etc)

08.11. Mid-presentations. 16:15-18:00 TB109. Projects are presenting their achievements so far. (Customers welcome!)

15.01. Final sprint begins. (quality assurance, maintenance, documentation, prepation to delivery, etc.)

04.02. Product ready deadline and delivery to customer.

09.02. Final presentations. 10:00-18:00 SE203. Projects present their product & project related highlights. (Customers welcome!)

05.-16.02. Customer feedback needed. Separate inquiry via e-mail.

Project proposals

Would you have a project topic for one of the teams?

As previous years, we are seeking for good project topics. We assume that:

  • Topics are challenging but reasonable for teams of 5-7 members working during ~5 months (total ~1000 h).
  • Results of the projects should be complete and working systems - a demo is not enough. For example, testing is included. For creation of a new concept and demo, Demola Academy is an excellent platform.
  • Required tools and information should be available for the team when the project starts.
  • The topic should not include big secrets. The teams need to discuss their work with the teachers and other teams. By default the teachers will not sign NDAs.

What, when?

The course starts at the end of August 2017, so we would like to get your project topics by 27.08.2017.

Description of the topic (max one A4) should include:

  • Problem to be solved and essential high-level requirements, expected outcome of the project
  • Target platform and other constraints, such as programming language, operating system, etc.
  • Language to be used in the communication and user interface of the created system
  • Assumption towards the team: competences (e.g., SW, UX, or security experience), language skills, special knowledge of technologies, etc.
  • Additional essential information
  • Contact information.
  • See more on good project proposal from below (customer instructions).

There will be no guarantee that your topic will be selected by any team, but good topics are picked first. You will be given a chance to pitch for your topic at the second lecture time in early September.

To send your proposal or to ask for more information contact:

Harri Sten - harri.sten@tut.fi - 050 300 8284

Kari Systä - kari.systa@tut.fi - 050 483 5496 .

Customer instructions

It is all about collaboration

  • Any development project is collaboration between customer and the development organization, in this case a student team. The actions of customer will have great effect on the success of the project. That is why we here give some pointers that we think will help the customer achieve the desired results.
  • Good project proposal

    A good project proposal is usually like this:

  • It is a proper product / system development project that produces a defined and delivered end result. Just like you used a company to deliver something. We don't want technology studies or proof of concepts here.
  • Results of the projects should be complete and working systems - a demo is not enough. For example, testing is included. For creation of a new concept and demo, Demola Academy is an excellent platform.
  • It is reasonable for teams of 5-7 members working during ~5 months (total ~1000 h).
  • It has a suitable amount of challenge - people should need to use their collective intellect to solve a problem or technical challenge. This is really a success factor for the projects!
  • Don't think of students as implementers, give them things to design.
  • The topic should not include big secrets. The teams need to discuss their work with the teachers and other teams. By default the teachers will not sign NDAs.
  • At the start of the course you will be given an opportunity to pitch your project to students and win the hearts of the best student for your task - so do it well.

    Meeting the expectations

    It is very difficult to estimate how much a team can do during the course. That is why the projects should use an incremental development process that will enable you to assess the situation and re-think goals as needed. In all development it is important to select realistic goals that can be met.

    Examples:

  • If you think that the product will see further development after the course, resources must be allocated to proper documentation. The requirements specification should include any foreseen documentation as deliverables.
  • If you need a bullet-proof implementation, resources must be used for building test systems and doing good testing.
  • If the product will see dynamic development after the course, planning of versatile architecture must be a priority.
  • When the task is large, perhaps it can be split for two teams.

    Supporting the team

    Select a contact person who has time for the team(s). This is essential for the project's success. You should commit to meet the team and give feedback to the team at least after each iteration (~once a month), i.e., you will play the role of customer towards the team. This effort is the main "cost" for you, but through your active participation you get more and can ensure that the resulting system is useful and corresponds to your needs.

    Of course, a successful project will usually require other forms of interaction, for example:

  • Giving information and documents to the team.
  • Commenting on things. Remember, only you know the specifics of your business and your environment.
  • Perhaps participating in a design workshop.
  • Providing people for usability tests.
  • But the idea is not to tax you too much with all this.

    Note that the team will not need management from you. Each team has a project manager who handles that. But as a customer you are free to demand professional practices from the team. Feel free to advice the team in for example meeting practices, communication, deadlines, documentation.

    Tooling the team

  • Teams may need special tools or environments and it is usually your task to provide them.
  • Required tools and information should be available for the team when the project starts.
  • Licenses and contracts

    Licensing of the results is based on an agreement between you and the project team. We emphasize the students that customers are their friend and will form agreements that are good for both parties.

    Note that by default the team has all the rights to what they produce and under any agreements should have a possibility to showcase their developments.

    Support for you from TUT

    Each team has a named coach looking after its performance. The coach is also your main contact towards TUT's personnel during the course and you can raise any issues with her/him. Feel also free to contact other course personnel whenever you have something to discuss about anything.