Author Joost Schalken-Pinkster

Author: Joost Schalken-Pinkster
Dr. Joost Schalken-Pinkster has obtained a Ph.D. in software engineering in 2007. Since then he has worked continuously in IT as architect management consultant and lecturer. Besides working at ICT Institute, Joost is lecturer at Utrecht Applied University where he focuses on code construction, software design and software architecture.
Embedded System PCB

Embedded systems development: Raspberry Pi or Arduino

During our reviews of IT projects and startups, we see more and more teams that create ’embedded software’: software intended not to run inside some other device. The development of such systems has become much easier since the introduction of two standard platforms:  Arduino and Raspberry Pi. These two platforms are quite different so it is…

Joost Schalken-Pinkster

Enabling two-factor authentication: highly recommended

Many websites, including giants such as google, Facebook and Dropbox, have implemented an additional security feature called two-factor authentication. Unfortunately this extra security feature is normally turned off. We recommend turning two-factor authentication on immediately, because it will protect your account from being hacked. What is two-factor authentication Most websites ask for a username and password when…

Joost Schalken-Pinkster

Using Microsoft Visual Studio code metrics for better code quality

Writing code that is easy to understand and maintain is important. Using code measuring tools makes this a whole lot easier. Microsoft’s IDE Visual Studio contains useful code quality analysis tools that can be easily enabled. This guide tells you how to get started.

Joost Schalken-Pinkster

Four methods for software effort estimation

Understanding the size and effort of a software project early on is a difficult problem. Several different methods exist, but no method is perfect. In this article we present an overview of the four methods most mentioned in literature: 1) expert opinion-based, 2) top-down estimation, 3) bottom-up estimation and 4) estimation using a parametric or algorithmic model.

Joost Schalken-Pinkster

Getting non-functional requirements right

Getting non-functional requirements right early on is an important success factor for successful projects. This is why, in the course on software project management, one of the practical assignments focused exactly on this topic. In this article we summarize the most important steps: discovering requirements, making them precise and making them flexible .

Joost Schalken-Pinkster