O Dublin Core Application Profile to Analysis Patterns (DC2AP) é um perfil de aplicação do padrão de metadados Dublin Core criado especificamente para descrever padrões de análise de maneira compatível com a proposta da APRI. Ele foi desenvolvido a partir da fusão dos elementos propostos pelo padrão de metadados Dublin Core com os elementos do template proposto no trabalho “Analysis Patterns Specifications: Filling the Gaps“ de Pantoquilho et al. (2003) para especificar padrões de análise. O DC2AP é um perfil de aplicação processável por máquina, possibilitando que os padrões de análise sejam descritos e publicados como Linked Data através de arquivos no formato Resource Description Framework (RDF).
O principal objetivo do DC2AP é melhorar a recuperação e reutilização dos padrões de análise por meio de uma descrição que permita um tratamento mais preciso realizado por um computador, oferecendo assim informações detalhadas sobre os padrões de análise que antes não eram recuperadas por ferramentas de busca.
Uma detalhada descrição técnica desse perfil de aplicação contendo a descrição semântica de cada um dos seus elementos, assim como detalhes das regras de aplicação dos mesmos pode ser obtida em:
** An detailed technical description about this application profile containing the semantic description of each one of its elements, just as application rules details can be obtained in:
|Elementos do DC2AP|
|2. Title||2.1. Alternative Title|
|5. Description||5.1. Problem|
|5.2. Motivation||5.2.1. Example|
|5.2.2. Known Uses **|
|8. Date||8.1. Created|
|9. Type||9.1. Notation|
|13. Relation||13.1. Is Version of|
|13.2. Is Replaced by *|
|13.3. Replaces *|
|13.4. Is Part of|
|13.5. Has Part|
|13.6. Is Designed with **|
|13.7. Should Avoid **|
|13.8. Complemented by **|
|16. History *||16.1. Event Date|
|17. Requirements||17.1. Functional Requirements|
|17.2. Non-functional Requirements|
|17.3. Dependencies and Contributions||17.3.1. DependencyGraph|
|17.4. Conflict identification and Guidance to Resolution|
|17.5. Priorities diagram|
|18. Modelling||18.1. Behaviour||18.1.1. Use Case Diagram|
|18.1.3. Activity/State Diagrams|
|18.2. Structure||18.2.1. Class Diagram|
|18.2.2. Class descriptions|
|18.2.3. Relationship descriptions|
|18.3. Solution Variants **|
|19. Resulting Context **|
|20. Design Guidelines **|
|21. Consequences||21.1. Positive|
* Elementos de controle de versão
** Elementos de colaboração de experiência de uso
Descrição semântica resumida dos elementos:
- Identifier: An unambiguous reference given to an analysis pattern (AP) to differentiate it from others.
- Title: Formal name by which an AP is widely known.
- Alternative Title: Alternative names used to substitute the formal name of an AP.
- Creator: Creator’s name of an AP.
- Subject: Are keywords related to the scope in which an AP is applied, thus providing a brief contextualization.
- Description: Agglutinating element of descriptions aimed in the contextualization of an AP over various aspects.
- Problem: Brief textual description of the problem solved by an AP.
- Motivation: Peculiarities of the problem which should be solved by the AP, regardless of application domain.
- Examples: Applications where the documented AP can be applied.
- Known Uses: Real systems where an AP was applied.
- Context: Description of contextual coverage of the documented AP.
- Publisher: Names of responsible for providing the AP for the public.
- Contributor: Names of responsible for changes made in the original version of the AP.
- Date: Agglutinating element of dates about the creation and modification of the documented AP.
- Created: Creation date of the version of the documented AP.
- Modified: Date of the last modification of the documented AP.
- Type: The nature of documented resource. It should always be Analysis Pattern.
- Notation: The notation used to create the diagrams during the documentation of an AP.
- Format: Digital formats of diagrams used in documentation of an AP.
- Source: Reference to the AP used as the main intellectual source in the creation of an AP.
- Language: Language used for documenting an AP.
- Relation: Agglutinating element of existing relationships between the documented AP and other patterns.
- Is Version Of: Reference to the first version of an AP.
- Is Replaced By: References for all the most current versions of an AP.
- Replaces: References for all previous versions of an AP.
- Is Part Of: References for APs that contain the documented AP as part of its composition.
- Has Part: References for APs which are contained as part of the composition of the documented AP.
- Is Designed With: Known design patterns that can be used during the implementation of the documented AP.
- Should Avoid: Anti-patterns important to avoid common errors identified during the application of the documented AP.
- Complemented By: Known APs that can be used to complement the documented AP.
- About: Description of details about relationships established among the documented AP and other patterns.
- Coverage: Spatial location or time period covered by the scope of an AP. It can compensate regionalisms that generate semantic ambiguities.
- Rights: Existing rights over the documented AP.
- History: Agglutinating element of historical data about the evolution of an AP.
- Event Date: Date of the historic event occurrence.
- Author: Names of responsible for the occurrence of the historic event.
- Reason: Reason for the occurrence of the historical event.
- Changes: Changes made in the AP during an event of changes.
- Requirements: Agglutinating element of data about the requirements of an AP.
- Functional Requirements: Responsibilities and restrictions for meet each functional requirement of an AP.
- Non-functional Requirements: Responsibilities and restrictions for meet each non-functional requirement of an AP.
- Dependencies and Contributions: Brief explanation about the identified relations of dependency and contributions among the requirements of an AP.
- Dependency Graph: Graph diagram used to represent the identified relations of dependency among the requirements of an AP.
- Contribution Graph: Graph diagram used to represent the identified relations of contribution among the requirements of an AP.
- Conflict Identification & Guidance to Resolution: Brief explanation about the identified conflicts among the requirements of an AP and possible manners to solve them.
- Priorities Diagram: It represents the order which AP requirements should be satisfied respecting their dependencies.
- Participants: Entities that interact with AP requirements.
- Modelling: Agglutinating element of diagrams and descriptions that represents part of the problem solution.
- Behaviour: Agglutinating element of diagrams that make up the behavioral model of an AP.
- Use Case Diagram: Is used to represent a system that meets requirements of an AP together with entities which interact with them.
- Collaboration/Sequence Diagrams: Are used to create scenarios that represent the execution of each use case of an AP.
- Activity/State Diagrams: Are used to represent the general behaviour of the system specified by an AP.
- Structure: Agglutinating element of the diagram and descriptions that make up the structural model of an AP.
- Class Diagram: Is the main part of the problem solution treated by an AP.
- Class Description: Brief description of each class of the class diagram.
- Relationship Descriptions: Brief description of the main relationships present in the class diagram.
- Solution Variants: Alternative models of behaviour and structure to solve the problem treated by an AP.
- Resulting Context: Adaptations realized in an AP when it is applied in specific systems.
- Design Guidelines: General tips for implementation of an AP.
- Consequences: Agglutinating element of descriptions of advantages and disadvantages of use the documented AP.
- Positive: Positive consequences of use of the documented AP.
- Negative: Negative consequences of use of the documented AP.