Swedish web site
TDDD83 Computer Engineering - Bachelor Project
FAQ
Below are questions that have arisen in previous years. We will post the most common questions we receive along with their answers. The list is continuously updated.
- Which method should be used to determine customer/user needs?
A thorough target group analysis is a prerequisite for developing a product that meets customer and user needs. Surveys, interviews, focus groups, and workshops are examples of methods that can be used. The key is to ensure that the information gathered is relevant to the target group, regardless of the method employed. Relying solely on surveys for target group analysis is not recommended. A major drawback of surveys is the inability to delve deeper into the responses. For instance, if the product to be developed is a health application for middle-aged mothers, sending a survey to first-year students at Linköping University is inappropriate; the responses would lack relevance regardless of the response rate, as the participants do not represent the target group. Good tips on methods can be found at usability.gov and in chapters 7–9 of the book Designing for the Digital Age (available via the university's UniSearch).
- What should actually be included in the Experience Summary (individual part) of the report?
Here, you should focus on your own experiences from the project regarding both process-related and technical aspects, for example:
-- If you divided the work among yourselves during the project, you can discuss experiences related to the areas you focused on more heavily: e.g., the Scrum Master role or experiences with Ajax or Python.
-- Reflect on how your individual skills have developed during the work, addressing both technical and process-related experiences.
-- Reflect on the execution of the bachelor's thesis from your perspective. Did you achieve the individual goals you set for yourself at the beginning of the work? Why or why not?
- Is it a requirement that the web application be mobile-responsive?
Using Bootstrap is a requirement. Bootstrap provides responsive design and adapts the web application to various screen sizes, including mobile devices. We do not have a requirement for the web application to be adapted for mobile touch interaction. The focus should be on adapting screen sizes to different devices via Bootstrap.
- Should the E-shop function as a web application?
The E-shop must function as a web application, meaning that whenever a request is made, only the difference (the additional information/data) should be fetched (rather than an entire web page) and presented on the page. To achieve this, the jQuery AJAX get() and/or post() methods should be used (as you have done in the labs). AJAX stands for Asynchronous JavaScript And XML and is a collective term for various techniques used to create web applications where only parts of the user interface are updated as needed. Ajax enables web pages to respond immediately to user input without the browser needing to wait for new pages from the web server.
- Can PHP be used?
No, PHP should not be used in this course.
- If the group has completed all items in the sprint backlog, what should the group do?
If all items in the sprint backlog are complete, meaning they have all been moved to Done, and there is still time remaining in the sprint, new items should be pulled from the prioritized product backlog. This can happen if the estimation was too high, meaning items were completed faster than estimated. If the product backlog is empty, it should be replenished with new stories.
- Must Ajax be used?
Ajax must be used as it simplifies and speeds up the interaction between the user, the web page, and the underlying system. The main point of Ajax is that pages do not need to reload constantly when information is sent or fetched. For example, Ajax is used when managing the shopping cart; as customers add items, they appear in the cart, allowing the customer to see a summary of the items they are about to purchase.
---------------------------------------------------------------
Page responsible: Martin Sjölund
Last updated: 2026-03-12
