The BMS lab offers access to its team of technical experts and developers as one of its services. They can help you navigate the process of software development when this is needed for a research or educational project. If you have a project registered with the lab and approved, then you can make use of this service. Development time can be used for a variety of projects. It includes (but is not limited to): app development, adding functionality to existing BMS lab software, building connectors or scripts, creating VR and AR environments and building software. This page can be used to reserve time with our team for your project. Please read and follow the information on this page carefully. It saves the development team time and this time can then be used to develop your project. The lab discerns two types of projects:

  • An 80 hour project: Students and researchers tied to the University of TWente can request the use of 80 hours of time from the development team free of charge.
  • Funded projects: Projects that are estimated to take more than 80 hours of time from the development team need to have their own funding. The lab will charge the researcher or student for the usage of the development team.

Conditions and requirements

We can only evaluate proposals that are adequately detailed and concrete.

  • Projects should associated with the BMS faculty of the University of Twente.
  • Realistic scheduling and time management are needed. Our development team is busy throughout the year. Thus, your schedule should account for this. Moreover, requesters should include time needed to follow procedures in their schedules (e.g. 1 week to check the request).
  • The project will need to fit with the overall scope, mission, priorities and ambitions of the lab.
  • Development is a co-creation process. Thus, the requester is willing to be actively involved in the development process. This includes time for testing, writing specifications and making design decisions. The requester is responsible at all times for the end result and the project. The lab helps the requester translate their wishes and ambitions into requirements and a scope that is expected to fit within the budget. Smaller projects might be developed within the lab. Other projects are send to an external development team. The lab then serves as a go between for communication and project management.
  • Testing the delivered software is a collaborative effort and dependent upon the scope of the project and individual arrangements that are to be made. In general, the lab tries to identify and have bugs repaired before delivering it to the client. Moreover, the lab does an initial check whether the delivered software meets the specifications. The requester is then responsible for the final check of the software and for reporting back bugs in a timely manner. This method ensures that the expertise of the lab is used where possible and the requester can check whether the software meets the requirements in practice.

An employee of the lab will be assigned as main point of contact and project leader for most of the projects that are send to us. They help you navigate the process. For more information on the process, conditions or requirements, please contact the BMS Lab.

Procedure

The procedure consists 5 phases from the moment that you navigate to this very page. Please note that the process might not always be linear and might be iterative (repeating various steps).

  • Phase 0. Registration and fundamentals: The project is registered through the sign-up procedure and the researcher fills out the form for development time (the form found below). This serves as input for phase 1. Projects might be deferred or rejected at this stage.
  • Phase 1. Scope evaluation: The lab evaluates your request and reviews main information to determine the scope for the project and the basic architecture. Your request (in the form below) should therefore be complete, clear and thorough.
  • Phase 2. Specification: Requester provides the lab the methodology and requirements and works with the lab to form a full-fledged specification. It is important that the requester delivers use cases and scenarios that help establish the scope and requirements of the project. The final specification includes all the functional and technical requirements and a schedule.
  • Phase 3. Building: The development team of the lab will work on realizing the project or will set the contracted external development team in motion. Requester must take part and bear responsibility for testing and the next steps in the processes.
  • Phase 4. First delivery and testing: An initial version of the product is delivered to the requester for testing and verification of it meeting the project’s scope and requirements. The requester will help create user documentation for the delivered product. This phase might be repeated multiple times until a final product is delivered.

Request the use of development time

The form below can be used to request time from the development team. Filling in this form and meeting the conditions set out above are however no guarantee that your request will be honored. The time of the lab’s development team is quite scarce. Thus, prioritizing projects and rejecting some is a necessity. Moreover, the schedule of a researcher might simply not fit with the lab’s schedule. Lastly, the terms and conditions for development support apply to any and all development activities. They can be found here.

Do you have questions?

Are you not sure how to proceed? Or, are you not sure that the project fits with the lab? Then please contact us and provide us with information we can use to evaluate your proposal. More importantly, please include as many of the information from the form as possible.