Joker
extra
Why?
This set of cards gives you an overview of methods you can use, but there are many others that might fit your goals better.
Methods
As an ICT student or professional, you need to solve all kind of ICT challenges. Answering the questions and tackling the problems or opportunities of your ICT project requires research and often a combination of various ICT research methods. The toolkit on this website offers you a set of possible research methods and a framework to select the appropriate (combination of) methods
A/B testing
lab
Why?
A minor change in a design may alter user behaviour in ways that are hard to detect in a usability test. An A/B test allows you to compare real-world user behaviour across different versions of a product.
Component test
lab
Why?
Test a subsystem or component in isolation to ensure its correctness before integrating it with other components or modules.
Computer simulation
lab
Why?
Computer simulations are used when a real-world process, system or event situation is not available or feasible.
Hardware validation
lab
Why?
Hardware does not always perform according to its specifications. Hardware validation ensures that the hardware performs as expected and excludes hardware as a source of errors.
Non-functional test
lab
Why?
Test the operating conditions under which the system delivers its intended functions.
Security test
lab
System test
lab
Why?
Solve problems before your system goes into production and demonstrate that the system operates according to its requirements.
Unit test
lab
Why?
Find certain types of bugs as early as possible and ensure your code keeps running after a change.
Usability testing
lab
Why?
Detect problems users have with your solution and correct them before the system goes live.
Community research
library
Why?
Have others already tackled the problem? Incorporating your peers’ knowledge can seriously speed things up.
Design pattern research
library
Why?
Applying well-known design patterns improves the quality (and structure) of the designed software.
Literature study
library
Why?
Find general information, guidance and best practices.
Benchmark test
showroom
Why?
A standardised set allows you to compare your product to similar products.
Guideline conformity analysis
showroom
Why?
Conforming to guidelines and standards helps ensure the credibility of the quality of your product and prevents reliability, privacy and security issues.
Peer review
showroom
Why?
Colleagues and experts can help improve your work, especially if they need to reuse it.
Pitch
showroom
Why?
Get an idea of the unique selling points of the opportunity you have found, or of the idea you have to tackle a problem, and practice concise communication about them.
Product review
showroom
Why?
Ensure that the product is perfect before it is released to the client or users.
Static program analysis
showroom
Why?
Get an impression of how well your code is written and quickly find vulnerabilities, weak spots and bad smells.
Brainstorm
workshop
Why?
Generate and develop new ideas.
Code review
workshop
Why?
With many eyeballs on the code, all bugs are shallow. Colleagues can help you find bugs and improve the quality of your source code.
Prototyping
workshop
Why?
Develop, evaluate or communicate a concept, design or problem solution to make your ideas concrete, to learn whether they work and to discover the technical limitations or possibilities.
