This paper aims to present an ontology model of software engineering to represent its knowledge. The fundamental knowledge relating to software engineering is well described in the textbook entitled software Engineeri...
详细信息
This paper aims to present an ontology model of software engineering to represent its knowledge. The fundamental knowledge relating to software engineering is well described in the textbook entitled software Engineering by Sommerville that is now in its eighth edition [1] and the white paper, software Engineering Body of Knowledge (SWEBOK), by the IEEE [2] upon which software engineering ontology is based. This paper gives an analysis of what software engineering ontology is, what it consists of, and what it is used for in the form of usage example scenarios. The usage scenarios presented in this paper highlight the characteristics of the software engineering ontology. The software engineering ontology assists in defining information for the exchange of semantic project information and is used as a communication framework. Its users are software engineers sharing domain knowledge as well as instance knowledge of software engineering.
In softwaredevelopment organizations, large-scale distributed projects pose many challenges, such as hierarchical requirements, large team size, and managing workflow. Agile methods, like Scrum, seem to have limitati...
详细信息
ISBN:
(纸本)9783319186122;9783319186115
In softwaredevelopment organizations, large-scale distributed projects pose many challenges, such as hierarchical requirements, large team size, and managing workflow. Agile methods, like Scrum, seem to have limitations in addressing those issues. Kanban offers an interesting alternative in this concern by setting work-in-progress (WIP) limits to manage flow and establishing visibility of requirements using a visual signaling system. However, only few empirical studies have investigated scaling Kanban for large organizations. To address this concern, a case study was conducted in a large multisite company to identify the challenges and possible solutions in scaling Kanban. During the study, defining WIP limits, coordinating with distributed teams, and dividing features between teams were found as major challenges. Setting WIP limits by common agreement between teams and visualizing product backlogs and teams on electronic board, with teams pulling features from the board, were found as possible solutions for overcoming the mentioned challenges.
暂无评论