Hi Khan,

There are some research work about deriving requirements based on pre existent ontologies and the other way around, although not specifically in a agile context. You may search digital libraries on the topic, because I don not have the references right now.

However, I am not sure what you mean by "...using semantics in global software development".

I hope it helps, EG

First, be careful to build on pre-existing domain knowledge and build a vocabulary together with each of your customer segments — in their own language. The vocabulary may serve you well in communicating.

Then, listen to your customers, socialise prototypes with them, and structure the resulting understanding using use cases. Then elicit their feedback on the result and iterate because, in spite of best intents, we usually mis something.

There is no formulaic approach in a complex domain.

Hello Muhammed

We have some papers on this topic based on the application of User Stories in a Scrum setting: 

Garm Lucassen, Fabiano Dalpiaz, Jan Martijn E. M. van der Werf, Sjaak Brinkkemper: Improving agile requirements: the Quality User Story framework and tool. Requir. Eng. 21(3): 383-403 (2016) 

Garm Lucassen, Fabiano Dalpiaz, Jan Martijn E. M. van der Werf, Sjaak Brinkkemper: Visualizing User Story Requirements at Multiple Granularity Levels via Semantic Relatedness. ER 2016: 463-478 

Kevin Vlaanderen, Slinger Jansen, Sjaak Brinkkemper, Erik Jaspers: The agile requirements refinery: Applying SCRUM principles to software product management. Information & Software Technology 53(1): 58-70 (2011) 

All the best with your research work. And drop me a note through the regular email if you have additional questions.

--Sjaak