Digital Library[ Search Result ]
Successful Win-Win Requirements Negotiation Method using Game Theoretic Approach
With changing software industry structure, the emerging concept called Software Ecosystems (SECO) has various challenges that software engineers have to overcome. In marketdriven software product development, they should have the capability to offer high value products to their own business and their customers in order to being competitive. Each stakeholder’s perspectives and interests should be reconciled in terms of requirements so that engineers can offer high value products through requirements selection. Existing works have just mentioned the need of requirements negotiation between stakeholders without proposing detailed guidelines or practice. In this work, a systematic Requirements Negotiation process is proposed to resolve conflicts of interests of stakeholders in SECO. The interests of stakeholders are analyzed based on goal-based requirements engineering. The rationale of requirements conflict is structured for management. A stepwise requirements negotiation process aims at resolving requirements conflict by applying game theory concepts based on self-interested behaviors of stakeholders.
Agent-Based Modeling and Simulation Methodology using Social-Level Characteristics: A Case Study on Self-Adaptive Smart Grid and Military Domain Systems using Tropos
Agent-based modeling and simulation (ABMS) is used to model of market and social phenomena by utilizing agents’ fine-grained behaviors and interactions that cannot be implemented in a conventional simulation. However, ABMS represents irrational agents and hinders the achievement of individual or overall goals since ABMS is based on agent-based software, which follows the principle of rationality at the knowledge level [1]. This problem was solved in the agent-based software engineering (ABSE) field by using behavior laws for the social level [2]. However, they still do not propose the specific development methodology for how to develop the social level in a systematic way. Therefore, in order to propose agent-based modeling and simulation methods that reflect the behavior laws of social level characteristics, our study used the Tropos that can combine ABSE and social behavior laws for the presentation of concrete tasks and deliverables for each development step by step. In addition, the proposed method will be specified through experiments with specific application examples and case studies on the self-adaptive smart grid and the military domain system.
Service-Dependability-Case based Self-Adaptation in Service-Oriented Environment
In a distributed system environment based on a service-oriented architecture, separate systems collaborate to achieve the goals of the entire system by using services provided other systems. A service quality violation from using one service can cause runtime system failure in the environment. The existing self-adaptation methods follow fault tolerance mechanism that responds to a failure after a service quality violation. In other words, these methods are limited to responsive action. Therefore, a service-dependability-case based self-adaptation mechanism is necessary to preserve the dependability of the self-adaptive system. This paper demonstrates that the service-dependability-case based self-adaptation mechanism is better than QoS(quality of service)-based self-adaptation with fault tolerance to preserve the dependability of the self-adaptive system. Additionally, this paper suggests a method to present and analyze service dependability by using GSN(Goal Structuring Notation) which is the existing modeling method for the presentation of assurance cases, an action mechanism adapted using an analysis result of service-dependability-cases, a methods of leveraging the service-dependability - case based self-adaptation mechanism by following the service’s life cycle, and the framework architecture including the major components and the interactions between the components in the control loop of the self-adaptation process.
Running a SCRUM project within a Document Driven Process
This paper examines how a Computer Engineering Graduate student team ran their Advanced Software Engineering Capstone project using SCRUM. The environment provided contextual challenges in terms of the on-site customer and upfront requirements document, not uncommon in a document driven single-step methodology. The paper details the methodology and practices used to run the project, and reflects on some of the challenges faced by the members of a typical software team when transitioning to a SCRUM process. The paper concludes by evaluating the success of the techniques and practices compared to the Agile Manifesto and Henrik Kniberg’s Scrum checklist. The project was undertaken at South Korea’s Ajou University.
Search
Journal of KIISE
- ISSN : 2383-630X(Print)
- ISSN : 2383-6296(Electronic)
- KCI Accredited Journal
Editorial Office
- Tel. +82-2-588-9240
- Fax. +82-2-521-1352
- E-mail. chwoo@kiise.or.kr