TDDD83 Computer Engineering - Bachelor Project
FAQ
Below are questions that have arisen in previous years. Here we will post the most common questions we receive and their answers. The list is continuously updated.
- Which method should be used to determine the needs of customers/users?
A thorough target audience analysis is essential for developing a product that meets the needs of customers and users. Surveys, interviews, focus groups, and workshops are examples of methods that can be employed. What is crucial is to ensure that the information collected is relevant for the target group, regardless of the method. Relying solely on surveys for target audience analysis is not recommended. A major drawback of surveys is the inability to delve deeper into the answers. If the product to be developed is a health application for middle-aged mothers, surveys should not be sent to LiU computer science students, as the responses will not be relevant, regardless of the response rate, because the participants are not representative of the target group. For excellent tips on methods, consult usability.gov and chapters 7–9 in the book *Designing for the Digital Age* (accessible via the university’s UniSearch).
- What specifically should be covered in the Experience Summary (individual section) of the report?
Here, you should focus on your personal experiences from the project regarding both process-related and technical aspects, for example:
-- If you divided the work during the project, you might discuss experiences from the areas you focused on more: e.g., the Scrum Master role or insights gained from working with Ajax or Python.
-- Reflect on how your individual skills have developed during the work and include both technical and process-related experiences.
-- Reflect on the execution of the bachelor thesis from your own 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?
It is required to use Bootstrap. Bootstrap provides responsive design and adapts the web application to varying screen sizes, where mobile is one such device. We do not have requirements mandating adaptation to mobile touch interactions. The focus should be on adapting screen sizes across different devices via Bootstrap.
- Should the online store function as a web application?
The online store must function as a web application, meaning that whenever a request is made, only the differing data (the additional information) should be fetched (rather than an entire web page) and presented on the page. For this, jQuery's AJAX `get()` and/or `post()` methods should be utilized (as you have practiced in 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 directly 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 completes all items in the sprint backlog, what should the group do?
If all items in the sprint backlog are completed—meaning all have been moved to "Done"—and there is remaining time in the sprint, the group should pull in new items from the prioritized product backlog. This may occur if the initial estimation was too high, resulting in items being completed faster than anticipated. Should the product backlog be empty, it must be replenished with new stories.
- Must Ajax be used?
Ajax is mandatory because it simplifies and accelerates interaction between users, the web page, and the underlying system. The core purpose of Ajax is that pages do not need to reload constantly when information is sent or retrieved. For instance, Ajax is utilized in shopping cart management, where purchased items are added to the cart, allowing the customer to view a summary of items they are about to purchase.
---------------------------------------------------------------
Page responsible: Martin Sjölund
Last updated: 2026-03-09
