Bring domain specific needs into the requirement

These days, domain experts always communicate with business analysts or programmers through documents, expressed in some notations, which represent their needs, business process, business rules, constraints,or the artifacts on the abstract or concrete concepts. As business analysts, we are challenged to understand and translate their concepts and needs into developer familiar languages without losing track of the business detail, domain specific elements, their relationships,constraints and rules.

This is a very hard challenge, most of the time the constraints and rules between the business artifacts are lost in translation or hidden in detail. The main reason is because domain expert communities develop in time from experiencing different notations, which reflect particular technical methods, languages, goals, tasks, ways of thinking, and documentation styles. Also, business elements and their relationships are too habitual to be mentioned. Often, dialects arise in a community, because the notationis applied in different practical situations and environments. The gap in experience and domain knowledge difference between the domain expert and the business analyst is always wide. It is just out of the question for the business analyst to catch up a 20-year-long-experience over night.

Matching a domain to the requirements is not an easy thing... but for the success of an application system, it is everything! Cameo Requirements+ considers itself as a 4th generation requirement management tool with MDA (Model Driven Architecture) and MDE (Model Driven Engineering) concepts in mind. Cameo Requirements+ provides a flexible schema for the domain experts to define the domain specific structure, the business elements and their relationships.

The Cameo Requirements+ schema is based on the Eclipse eCore implementation (OMG’s MOF standard), which ensures the business elements, their relationships, constraints, and rules can be embedded into the schema. This domain specific schema is without doubt the drive of the requirement engineering process to ensure the requirement data integrity and correctness is captured during the requirement gathering state and transformed into platform independent model (PIM) or domain specific language (DSL) within MagicDraw.

Cameo Requirement+ also provides the standard requirement management capabilities to help the business analysts cope with the fast changing business environment of enterprises.