diff --git a/src/app.html b/src/app.html index 78566b2..bd456a1 100644 --- a/src/app.html +++ b/src/app.html @@ -13,21 +13,21 @@ - - + + - + - + @@ -73,18 +73,11 @@ >. :)

- -
+
%sveltekit.body%
+ diff --git a/src/content/methods/text/library/community-research.md b/src/content/methods/text/library/community-research.md index 03aca4a..116456e 100644 --- a/src/content/methods/text/library/community-research.md +++ b/src/content/methods/text/library/community-research.md @@ -1,14 +1,16 @@ --- name: "Community research" -why: "Placeholder text. Needs to be updated" -how: "Edit this text" -practice: "Add the correct copy" +why: "Have others already tackled the problem? Incorporating your peers’ knowledge can seriously speed things up." +how: "Search for the problem you are wrestling with in an online community you know you can trust. Start your quest as specifically as possible. Ask questions if you appear to be the first to present this problem." +practice: "Using community input is standard practice for developers. Even if others have been creating things that differ greatly from what you are doing, they still may have encountered problems that you are dealing with. It can save you a lot of time and annoyance." ingredients: [ -"Ingredient 1", -"Ingredient 2" +"Input into an online community of peers, like Stack Overflow.", +"A critical view: even if many people point you in the same direction, it may not be the ideal solution for your specific situation.", +"A thorough understanding about the proposed solution (do not just copy/paste).", +"A sharing attitude: do not hesitate to share your findings with the community." ] category: "library" phases: [ -"needs update" +"design" ] --- diff --git a/src/content/methods/text/library/design-pattern-research.md b/src/content/methods/text/library/design-pattern-research.md index db2988f..54452e1 100644 --- a/src/content/methods/text/library/design-pattern-research.md +++ b/src/content/methods/text/library/design-pattern-research.md @@ -1,14 +1,15 @@ --- name: "Design pattern research" -why: "Placeholder text. Needs to be updated" -how: "Edit this text" -practice: "Add the correct copy" +why: "Applying well-known design patterns improves the quality (and structure) of the designed software." +how: "Design patterns are documented solutions to frequently encountered problems or challenges in software engineering; they incorporate good software engineering principles. You should have an overview and active knowledge of the available patterns." +practice: "The book Design Patterns: Elements of Reusable Object- Oriented Software is regarded as the ‘bible’ of design patterns and is still widely used in corporate software engineering practice. However, there are many other, more up-to-date, books and online resources on the topic." ingredients: [ -"Ingredient 1", -"Ingredient 2" +"An overview of patterns (book or websites).", +"Time to absorb and understand patterns.", +"A willingness to improve the quality of the designed software." ] category: "library" phases: [ -"needs update" +"design" ] --- diff --git a/src/content/methods/text/library/expert-interview.md b/src/content/methods/text/library/expert-interview.md index c35fbbf..5646894 100644 --- a/src/content/methods/text/library/expert-interview.md +++ b/src/content/methods/text/library/expert-interview.md @@ -1,14 +1,17 @@ --- name: "Expert interview" -why: "Placeholder text. Needs to be updated" -how: "Edit this text" -practice: "Add the correct copy" +why: "A domain expert can put you on the right track when you enter a new domain or field of expertise. The expert can recommend sources, give you a sense of direction or point out common pitfalls." +how: "Find an expert who is willing to talk to you about the problem and arrange an interview." +practice: "Expert interviews are a common method for getting a grip on a new problem area that you are not familiar with. Because experts can draw on their own experience, the information they provide may be more relevant than information you can gather from literature." ingredients: [ -"Ingredient 1", -"Ingredient 2" +"An expert in your problem domain.", +"A realistic sense about what experts can and cannot offer.", +"The right questions to ask.", +"An open mind, so the expert can also bring in their own topics.", +"Interviewing techniques." ] category: "library" phases: [ -"needs update" +"analysis" ] --- diff --git a/src/content/methods/text/library/literature-study.md b/src/content/methods/text/library/literature-study.md index 5e3f45a..5e6f296 100644 --- a/src/content/methods/text/library/literature-study.md +++ b/src/content/methods/text/library/literature-study.md @@ -1,14 +1,17 @@ --- name: "Literature study" -why: "Placeholder text. Needs to be updated" -how: "Edit this text" -practice: "Add the correct copy" +why: "Find general information, guidance and best practices." +how: "Make a search plan and identify relevant keywords. Find and judge material. Within the sources, look for interesting references and repeat the search process with keywords you found in the texts. Finally, select which materials to read in detail, plan the reading and summarise your findings during reading." +practice: "A company that is focusing on user experience in the medical domain conducts a literature study to identify best practices to use when informing patients about health issues." ingredients: [ -"Ingredient 1", -"Ingredient 2" +"A willingness to read.", +"Search engines (e.g. Google Scholar, your library’s search engines).", +"The ability to select what is really important for you case and to leave the rest unread.", +"Identifying the ‘gatekeepers’ (parties who guarantee the quality of certain information).", +"Knowing when to stop." ] category: "library" phases: [ -"needs update" +"design" ] --- diff --git a/src/content/methods/text/library/swot-analysis.md b/src/content/methods/text/library/swot-analysis.md index 272d56b..55087bd 100644 --- a/src/content/methods/text/library/swot-analysis.md +++ b/src/content/methods/text/library/swot-analysis.md @@ -1,14 +1,15 @@ --- name: "SWOT analysis" -why: "Placeholder text. Needs to be updated" -how: "Edit this text" -practice: "Add the correct copy" +why: "A SWOT analysis supports decision makers in identifying relevant factors for achieving certain goals." +how: "The project team identifies several Strengths, Weaknesses, Opportunities and Threats related to a project. The results are typically presented in a 2 x 2 matrix. You need to understand the community that a particular organisation is working with; this can be done via public forums, listening campaigns or informational interviews." +practice: "A SWOT analysis is typically used as a strategic tool in an early phase of a project, after the outline of the project is developed. The SWOT is often a basis for a go–no go decision." ingredients: [ -"Ingredient 1", -"Ingredient 2" +"Basic knowledge about the project plans.", +"A sense of who the competition is.", +"Critical colleagues to review and update your initial SWOT." ] category: "library" phases: [ -"needs update" +"analysis" ] --- diff --git a/src/content/methods/text/showroom/benchmark-test.md b/src/content/methods/text/showroom/benchmark-test.md index dd0d2a7..5e2c164 100644 --- a/src/content/methods/text/showroom/benchmark-test.md +++ b/src/content/methods/text/showroom/benchmark-test.md @@ -1,13 +1,12 @@ --- name: "Benchmark test" -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." -how: "Code reviews can be done in many ways. The code can be presented on a big screen, so the entire team can do the review together. You can also ask one or two peers to simply sit behind your desk while you talk them through your code. Code analysis can also be a part of the workflow (e.g. every commit must be reviewed by someone else)." -practice: "Code review sessions are often incorporated into software development projects. In Scrum, code reviews can be part of the ‘definition of done’. Pair programming can also be an effective way to let your work be continuously reviewed by a peer." +why: "A standardised set allows you to compare your product to similar products." +how: "Search for standardised tests in your problem domain and run them on your solution. Compare your results to those achieved by similar products on this same test." +practice: "Benchmark tests are regularly used to test pattern recognition software. If a standard set of data is recognised with the software, the results can be compared to that of other software. Benchmarks are also used to compare hardware or software in which performance plays an important role (e.g. how many forms can automatically be processed per minute, in comparison to other software)." ingredients: [ -"Peers with a critical view.", -"A willingness to improve weak points in your code.", -"Code standards, a code style guide, checklists, etc.", -"Use a tool or template like Business Model Canvas." +"A standardised test.", +"A need to compare your product to similar products.", +"A way to evaluate your test results.", ] category: "showroom" phases: [ diff --git a/src/lib/components/SiteDescription.svelte b/src/lib/components/SiteDescription.svelte index 0a950c6..f651389 100644 --- a/src/lib/components/SiteDescription.svelte +++ b/src/lib/components/SiteDescription.svelte @@ -1 +1,15 @@ -

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.

+ + +

+ Welcome to the new website, released in October 2023. Please let us know if you have any feedback + by creating an issue on GitHub. +

+ +

+ You can still access the old website, by visiting this url. +