Software Engineering Project

(Redirected from software project)
Jump to: navigation, search

A Software Engineering Project is an engineering project to deliver a software system.



  • (Akgün, 2020) ⇒ Ali E. Akgün. (2020). “Team Wisdom in Software Development Projects and Its Impact on Project Performance.” International Journal of Information Management, 50.
    • ABSTRACT: While the concept of wisdom, which refers to how people make right use of their knowledge through their practical actions, judgments, and ethical decisions, in general attracts researcher interest in a variety of disciplines, such as philosophy, psychology and management studies, little is known about how wisdom is conceptualized and then operationalized in the software development project team context. Based on the frameworks for philosophical, group and organizational wisdom, this paper identifies software development project team wisdom as a process for how team members best use the stock and flow of their knowledge through collective judgment, virtue-ethics, emotions/feelings, and effective decision-making during their project-related efforts. Adapting the efforts and functional similarities of both group and organizational wisdom practices, this effort determines that wisdom-related mechanisms (e.g., team diversity, networking with other teams and people, and their past experiences), joint epistemic actions (e.g., team reasoning, intuition, and aesthetic capacity), and team virtue and prudence become the different faces of the software development team wisdom process. We then propose how these different faces interrelate and how they also relate to project process effectiveness, such as team learning and speed-to-users, both of which have been rarely addressed empirically in the context of software development project teamwork.

      By examining 210 in-house software development project teams in a field study and using structural equation modeling analysis, our results empirically show the following: (a) software development wisdom-related mechanisms positively relate to software development team prudence and virtue and their joint epistemic actions, (b) software development team prudence and virtue are positively associated with software development team joint epistemic actions, and further (d) software development team joint epistemic actions are positively associated with software development project process effectiveness. We conclude by discussing our findings as they relate to the wisdom framework of software development project teams and suggest the key managerial implications for different types of software development projects.


  • (Abdelrafe et al., 2016) ⇒ Elzamly Abdelrafe, Burairah Hussin, and Norhaziah Salleh. (2016). “Top Fifty Software Risk Factors and the Best Thirty Risk Management Techniques in Software Development Lifecycle for Successful Software Projects.” International Journal of Hybrid Information Technology 9, no. 6
    • QUOTE: … the values, principles and practices for modelling software in SDLC as well as used to identify and maintain a clear and correct understanding of the software development project being built [19], [20]. Furthermore, it don‟t contain any risk management techniques because it is …


  • (Bullard et al., 1988) ⇒ Catherine L. Bullard, Inez Caldwell, James Harrell, Cis Hinkle, and A. Jefferson Offutt. (1988). “Anatomy of a Software Engineering Project.” In: Proceedings of the nineteenth SIGCSE technical symposium on Computer science education, pp. 129-133.
    • ABSTRACT: This paper discusses a complete software development project carried out in a one quarter undergraduate software engineering course. The project was the design and implementation of a complete system by 25 students. They worked in smaller groups on four functionally separate subsystems that were successfully integrated into a complete system. This was accomplished by using five advanced students to manage the groups, real users to criticize each step of the process, and UNIX tools to implement the subsystems. This paper describes the project, presents the methodologies used, and discusses both the positive and negative aspects of this course. It concludes by presenting a set of recommendations based on our experience with this project.