Sparx Systems Enterprise Architect's typical usage scenarios comprise the capturing of business requirements, of more detailed use cases and scenarios that mimic required business situations and processes in a comprehensive way that is understood by business stakeholders as well as IT analysts. Business requirements can be then further translated to business logic (models, algorithms, process flows/workflows, business data objects, and other artifacts) that are linked to a high level as well as low-level ICT design (application logic, integration models, data models, etc.). The main reason and advantage for putting all the above into one IT solution (Enterprise Architect) is to provide a set of business and IT models, that are interrelated and any change to components such as process, data entity, integration service, business requirement, etc., can be traced to all other components. This would be the best practice - to have a tool that keeps track of any change you plan to do to your systems and helps indicates impacted components and relations. In practice, there are several obstacles to reaching this best usage practice.