Sepm Unit 3
Published:
Learning Outcomes Achieved
- Identify and apply appropriate software engineering and project management methodologies, tools and techniques for the development of solutions to real-world problems
- Explore the implications of computer and network architectures for system-level design and development, as appropriate for risk and quality management
Summary Post
This week, students were tasked with writing a summary post to conclude the discussion on software engineering project failures. In my post, I briefly discussed what the general consensus on what the most common causes of failure were (which were poor leadership and governance, poor communication, and a lack of focus on quality assurance). I thereafter briefly discussed a counterpoint I received, which was that perhaps software failure is influenced more by complexity and scale than anything else, and this point does have an academic backing.
Throughout this discussion, I’ve learned about problems related to software development, specifically within the realm of project management. I’ve also learned a lot from the case studies presented- they have shown me how these different project management issues can manifest in the real world, and what their consequences are. Lastly, I’ve also discovered how academic schools of thought can help me detect risk areas in the real world, when it comes to project management, and how different SDLC methodologies can be applied to solve these issues. As a result, I have overall achieved learning outcome 2 from this exercise.
Data Structures Reflection
As an activity for this week, students are required to do a reflection on an online system and which data structures it might use in the backend. By completing this activity, I have achieved learning outcome 2, because I have learned how implications of computer design (i.e., memory and lookup times) can influence development and solutions that can be chosen.