Knowledge-Assisted Ontology-Based Requirements Evolution

Ghaisas, Smita; Ajmeri, Nirav

doi:10.1007/978-3-642-34419-0_7

Cited by 18 publications

(23 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For example, Figure 1 shows the partial Product Knowledge Ontology. The technical details pertinent to the semantic guidance and interactions amongst the ontologies are explained in detail in our previous work [3,4]. The working of the configurator is illustrated next.…”

Section: A the Ontological Modelmentioning

confidence: 99%

“…In this paper we do not discuss the process of creating the knowledge repository using the ontological framework. The reader is referred to our previous work [3,4] for details of the process.…”

Section: B Knowledge -Assisted Product Requirements Configuration Anmentioning

confidence: 99%

“…The Environmental Context Ontology and the Business Domain Ontology are reused from our previous work [3,4] whereas the Product Knowledge Ontology is a new addition.…”

Section: A the Ontological Modelmentioning

confidence: 99%

“…Our previous work [3,4] on knowledge-assisted requirements framework facilitates reuse of requirements knowledge in typical service-oriented developments. We build upon this work to bring in the products perspective and to cater to the needs of productoriented business.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Knowledge-assisted product requirements configurator

Anish

Sharma

Motwani

et al. 2013

2013 4th International Workshop on Product LinE Approaches in Software Engineering (PLEASE)

View full text Add to dashboard Cite

Producing timely and customer oriented products is a key determinant for the success of any product-based business. Product requirement elicitation and configuration practices therefore play a major role in taking products to market efficiently. Knowledge of the existing generic product is crucially important while creating its variants. In this paper, we discuss an ontological representation of product primitives for a knowledge-assisted requirements configurator and illustrate its use for a financial product suite.

show abstract

Section: A the Ontological Modelmentioning

confidence: 99%

Section: B Knowledge -Assisted Product Requirements Configuration Anmentioning

confidence: 99%

“…The Environmental Context Ontology and the Business Domain Ontology are reused from our previous work [3,4] whereas the Product Knowledge Ontology is a new addition.…”

Section: A the Ontological Modelmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Knowledge-assisted product requirements configurator

Anish

Sharma

Motwani

et al. 2013

2013 4th International Workshop on Product LinE Approaches in Software Engineering (PLEASE)

View full text Add to dashboard Cite

show abstract

“…Second, we observed that many rules are domain, region, or company specific rather than application specific. Automatically identifying and extracting the rules and tracing them to related project artifacts would increase reuse when developing a new application for the same domain, region, or company [7]. This is the long-term goal of this research.…”

Section: Introductionmentioning

confidence: 97%

Capturing and sharing domain knowledge with business rules lessons learned from a global software vendor

Maalej

Ghaisas

2014

2014 IEEE 22nd International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

Business rules represent constraints in a domain, which need to be taken into account either during the development or the usage of a system. Motivated by the knowledge reuse potentials when developing systems within the same domain, we studied business rules in a large software company. We interviewed 11 experienced practitioners on how they understand, capture, and use business rules. We also studied the role of business rules in requirements engineering in the host organization. We found that practitioners have a very broad perception for this term, ranging from flows of business processes to directives for calling external system interfaces. We identified 27 types of rules, which are typically captured as a free text in requirements documents and other project documentation. Practitioners stated the need to capture this tacit form of domain knowledge and to trace it to other artifacts as it impacts all activities in a software engineering project. We distill our results in 17 findings and discuss the implications for researchers and practitioners.

show abstract

Theoretical Background and State-of-the-Art

Diamantopoulos¹,

Symeonidis²

2020

Advanced Information and Knowledge Processing

View full text Add to dashboard Cite

Knowledge-Assisted Ontology-Based Requirements Evolution

Cited by 18 publications

References 17 publications

Knowledge-assisted product requirements configurator

Knowledge-assisted product requirements configurator

Capturing and sharing domain knowledge with business rules lessons learned from a global software vendor

Theoretical Background and State-of-the-Art

Contact Info

Product

Resources

About