Ontology-Based Requirements Conflicts Analysis in Activity Diagrams

Liu, Chi-Lun

doi:10.1007/978-3-642-02457-3_1

Cited by 9 publications

(6 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…3. Analysis results based on type of requirements [13], [18]; structural model if graphical analysis is used like [20], [19], [8], [29]; or formalization methods which are different from schematic version in [3], structure requirements in [6], two canonical forms in [16], semi-formal ontology driven domain-special requirement language in [17], DSL in [20] and [19], OWL in [27], and EBNF in [21]. While some proposed techniques used more than one type of representation like [20], [19] which used ontology and DSL as formalization method, [27] used ontology, OWL as formalization method and goal graph as a structural model.…”

Section: B Comparing Between Exciting Workmentioning

confidence: 99%

Software Requirements Conflict Identification: Review and Recommendations

Aldekhail¹,

Chikh²,

Ziani³

2016

ijacsa

View full text Add to dashboard Cite

Abstract-Successful development of software systems requires a set of complete, consistent and clear requirements. A wide range of different stakeholders with various needs and backgrounds participate in the requirements engineering process. Accordingly, it is difficult to completely satisfy the requirements of each and every stakeholder. It is the requirements engineer's job to trade-off stakeholders' needs with the project resources and constraints. Many studies assert that failure in understanding and managing requirements in general, and requirement conflicts in particular, are one of the main problems of exceeding cost and allocated time which in turn results in project failure. This paper aims at investigating the different reasons of requirements conflicts and the different types of requirements conflicts. It providing an overview of existing research works on identifying conflicts; and discussing their limitations in order to yield suggestions for improvement. Objective: To provide an overview of existing research studies on identifying software requirements conflict and identifying limitations and areas for improvement. Method: A comparative literature was conducted by assessing 20 studies dated from 2001 to 2014.

show abstract

Section: B Comparing Between Exciting Workmentioning

confidence: 99%

Software Requirements Conflict Identification: Review and Recommendations

Aldekhail¹,

Chikh²,

Ziani³

2016

ijacsa

View full text Add to dashboard Cite

show abstract

“…Ontology can be used in information systems, such as enabling communication among software agents (Guarino, 1998). Recently, ontology has been used to detect requirement conflicts in information systems development (Liu, 2009). Therefore ontology is useful for conflict detection in access control policies.…”

Section: Literature Reviewmentioning

confidence: 99%

“…kind, composition, and antonym relationships). Using ontologies is a feasible and effective strategy for conflict detection (Liu, 2009). Social and tag setting includes users' social relations and web content tags.…”

Section: Introductionmentioning

confidence: 99%

Sharing and hiding online secrets

Liu

2010

Online Information Review

View full text Add to dashboard Cite

PurposeThis paper aims to manage access control tasks to satisfy the user privacy needs of online information resources according to social relations and tags.Design/methodology/approachThe study proposes a method for access control management in the online social context. The proposed method includes the access control policy management process, metadata of access control policies, the data of ontologies, tags, and social relations, and conflict detection rules.FindingsOnline information sharing and hiding, which needs to consider social relations and mentioned topics, is a unique context and needs a novel access control mechanism. Ontologies are powerful and expressive enough to identify conflicts in access control policies. The paper provides a method using ontologies to control the access control activities based on social relations and tags on web content. The effectiveness of the method's conflict detection rules is validated through several scenarios.Research limitations/implicationsTo make the proposed method suitable for widespread usage, further work is required to develop an access control policy specification and conflict detection tool. The proposed method introduces relatively novel usage scenarios, which consider social relationships, and tags compared with existing access control methods for online information sharing.Practical implicationsThe proposed access control mechanism can be integrated into existing web sites. Online users can use this method to share information more easily than at present.Originality/valueThe method enables flexible access control in social contexts and handles unavoidable conflicts. It also opens the way to new access control scenarios in online social activities. The method can be used to keep secrets hidden from selected people.

show abstract

“…A requirements engineer's goal is to keep the set of requirements consistent and up-to-date in the project duration [1]. Successful requirements engineering involves: understanding the needs of stakeholders, understanding the problem domain, providing specification templates and examples to ensure a high level of quality, maintaining a good relationship between stakeholders to fulfill user needs, validating that the documenting requirements match the collected requirements; managing requirements development, and assigning requirements engineering activities to skilled software engineers and team members for better performance [2][3][4]. A number of research studies have indicated that conflict resolution in requirements is a critical factor in project success [5].…”

Section: Introductionmentioning

confidence: 99%

Intelligent Identification and Resolution of Software Requirement Conflicts: Assessment and Evaluation

Aldekhail¹,

Almasri²

2022

Computer Systems Science and Engineering

View full text Add to dashboard Cite

Considerable research has demonstrated how effective requirements engineering is critical for the success of software projects. Requirements engineering has been established and recognized as one of the most important aspects of software engineering as of late. It is noteworthy to mention that requirement consistency is a critical factor in project success, and conflicts in requirements lead to waste of cost, time, and effort. A considerable number of research studies have shown the risks and problems caused by working with requirements that are in conflict with other requirements. These risks include running overtime or over budget, which may lead to project failure. At the very least, it would result in the extra expended effort. Various studies have also stated that failure in managing requirement conflicts is one of the main reasons for unsuccessful software projects due to high cost and insufficient time. Many prior research studies have proposed manual techniques to detect conflicts, whereas other research recommends automated approaches based on human analysis. Moreover, there are different resolutions for conflicting requirements. Our previous work proposed a scheme for dealing with this problem using a novel intelligent method to detect conflicts and resolve them. A rule-based system was proposed to identify conflicts in requirements, and a genetic algorithm (GA) was used to resolve conflicts. The objective of this work is to assess and evaluate the implementation of the method of minimizing the number of conflicts in the requirements. The methodology implemented comprises two different stages. The first stage, detecting conflicts using a rule-based system, demonstrated a correct result with 100% accuracy. The evaluation of using the GA to resolve and reduce conflicts in the second stage also displayed a good result and achieved the desired goal as well as the main objective of the research.

show abstract

Ontology-Based Requirements Conflicts Analysis in Activity Diagrams

Cited by 9 publications

References 12 publications

Software Requirements Conflict Identification: Review and Recommendations

Software Requirements Conflict Identification: Review and Recommendations

Sharing and hiding online secrets

Intelligent Identification and Resolution of Software Requirement Conflicts: Assessment and Evaluation

Contact Info

Product

Resources

About