2005
DOI: 10.1109/ms.2005.26
|View full text |Cite
|
Sign up to set email alerts
|

An Ontology for Microarchitectural Design Knowledge

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
13
0
1

Year Published

2007
2007
2023
2023

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 19 publications
(14 citation statements)
references
References 2 publications
0
13
0
1
Order By: Relevance
“…Principles, heuristics, bad smells, and so on have the same common structure, there being no substantial difference between them, as they all have the structure and form of a rule -they posit a condition and offer a recommendation [4] . Hence, in the context of the present work we use two terms: rule (to group elements such as principles, heuristics, bad smells, best practices, etc.)…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…Principles, heuristics, bad smells, and so on have the same common structure, there being no substantial difference between them, as they all have the structure and form of a rule -they posit a condition and offer a recommendation [4] . Hence, in the context of the present work we use two terms: rule (to group elements such as principles, heuristics, bad smells, best practices, etc.)…”
Section: Introductionmentioning
confidence: 99%
“…The main differences between these concepts are that patterns are more formalized than rules and pattern descriptions are always broader. Patterns propose solutions to problems whereas rules are recommendations which are, to a great extent, based on the use of natural language [4,5] . Maintainability and rules and patterns are popularly synonymous with well-designed software.…”
Section: Introductionmentioning
confidence: 99%
“…Esta abordagem permite que o fluxo e a transmissão de uma determinada informação ou conhecimento ocorram consistentemente durante todo o ciclo de comunicação entre pessoa-pessoa, pessoa-computador e computar-computador. Assim, esse método pode ser utilizado para facilitar a aquisição, especificação e representação formal do conhecimento em Engenharia de Software, necessário para o bom andamento e execução de projetos de desenvolvimento de sistemas [16].…”
Section: A Primeiro Desafio -De Desenvolvimento Orientado à Processounclassified
“…[14] provides a catalog of rules that every software application must comply with. Whenever a design rule is violated, there is a possibility of improvement.…”
Section: Finding Change Candidatesmentioning
confidence: 99%