English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Heterogeneity in software requirements has regularly been discussed as a challenging problem, especially in the areas of requirements traceability. In practice, requirements are fundamentally expressed by customers in terms of natural language which inevitably inherits ambiguity. Pieces of requirements may be expressed in such a way that is best suited the view of an individual. Vocabularies and terminologies used in requirements expression therefore can be varied, habitually depending on customer roles, their background knowledge, perspectives and levels of understanding on system problems. Often, system analysts may capture requirements expressed by using different vocabularies or terminologies, yet conveying similar meaning. Taking account of diversity of how software requirements can be expressed and who expresses the requirements, system analysts may use different techniques to elicit the requirements from customers. Requirements elicitation techniques range from typical ones like introspection, questionnaires, interviews, focus group and protocol analysis (Goguen & Linde, 1993) to modern one like scrum and agile requirements modeling (Paetsch et al., 2003). No matter which elicitation techniques are deployed, requirements from different customers often overlap, possibly are intertwined and inconsistent. As systems become more complex it becomes increasingly difficult for system analysts to resolve heterogeneity in software requirements so that the requirements can be verified and validated easily and effectively. The impact of heterogeneity is even more crucial in distributed and collaborative software development environment since the heterogeneity is an inherent characteristic in such environment. With the advents of outsourcing and offshoring software development, software specifications can be collaboratively constructed by a team of developers in multiple sites, possibly with various development methods and tools. It is therefore important that system analysts must understand and be able to resolve the analogy and 11

Ontological Knowledge Representation for Resolving Semantic Heterogeneity in Software Requirements Traceability