Module 4
Software Engineering Project Management
Unit 3
Estimating, Planning and Risk
Learning Outcomes
- Select and utilise an appropriate tool for planning.
- Select and utilise an appropriate tool for estimating.
- Select and utilise an appropriate tool for risk assessment.
e-Portfolio Component: Collaborative Discussion 1: Project Failures Study
- The discussion that started in Unit 1 was continued. Link to the discussion forum: here
e-Portfolio Activity: Data Structures Reflection
Read Wang et al (2023). Think about an online system which you use on a daily basis. Consider how it might operate at the back-end using data structures. This will inform our discussion during next week’s seminar.
Response:An online food delivery application can be understood by examining its back-end data structures. We will focus on a surface-level view of placing an order using these data structures (Munjal, 2025).
When a customer opens the app to place an order, the system retrieves a list of restaurants using a hash table. In this case, the restaurant ID serves as the key, while the details such as the menu and metadata are the values. Hash tables allow quick lookups, improving search speed.
Once a restaurant is selected, the system displays the menu, which can be stored in an array or linked list. An array is suitable for fixed menus, while a linked list is better for dynamic menus with items added or removed based on availability. Each menu item includes attributes like name, price, and ingredients, and the list structure helps manage these items efficiently.
When a customer orders, the system uses a queue to process the order in the sequence it is received, following the first-in, first-out (FIFO) principle. The queue ensures orders are handled in the correct order.
Munjal, H. (2025) 8 basic data structures plus a guide to algorithms. Available at: https://www.godaddy.com/resources/in/web-pro-in/8-basic-data-structures-every-programmer-should-know (Accessed: 16 February 2025).
Meeting Notes
- Date: 13 February 2025
- Attendees: Craig Bourne, Georgia Hird, and Shraddha Gore
-
Agenda:
- The team held brief introductions and discussed the idea of forming a team contract.
- Each member was tasked with individually noting down key points they felt should be included.
-
Next steps:
- The ideas will be shared and discussed in the next meeting.
- Date: 17 February 2025
- Attendees: Craig Bourne, and Georgia Hird
-
Agenda:
- Reviewed the completed sections of the team contract.
-
Next steps:
- Send the draft contract to Shraddha for proofreading.
Reflection
- Unit 3 provided an opportunity to focus on team collaboration, including the development of our team contract and discussions regarding the Unit 6 assessment, in addition to the ongoing e-portfolio work.