What This Document Is
This report details research conducted within the Computer Animation and Simulation (CSCI 520) course at the University of Southern California. Specifically, it presents an analysis of stakeholder value dependencies in software development projects. The study employs an experimental approach to investigate how different individuals involved in a software project – such as clients, users, and maintainers – prioritize various aspects of the system. It delves into the complexities of aligning expectations and understanding the core values driving each stakeholder group.
Why This Document Matters
This report is valuable for students and professionals involved in software engineering, systems analysis, and project management. It’s particularly relevant for those seeking to improve requirements gathering, reduce project failures stemming from misaligned expectations, and enhance overall stakeholder satisfaction. Individuals studying human-computer interaction or software dependability will also find the research insightful. Understanding the principles discussed can be applied to a wide range of software development scenarios, from small team projects to large-scale enterprise systems.
Common Limitations or Challenges
This report focuses on a specific set of projects – graduate-level software engineering course projects – and may not directly translate to all software development contexts. The findings are based on a controlled experiment and, while statistically analyzed, represent a specific sample. It does not offer a universal solution for stakeholder management, nor does it provide a step-by-step guide to implementing the discussed concepts. The research explores theoretical frameworks and empirical results, but doesn’t detail specific software tools or coding techniques.
What This Document Provides
* An examination of the relationship between stakeholders and the values they prioritize in software systems.
* Findings from a controlled experiment involving real-world client projects.
* Analysis of the effectiveness of role-playing as a method for understanding stakeholder perspectives.
* Discussion of potential implications for software development processes.
* A structured framework for reasoning about stakeholder needs and dependencies.
