Spoiled patterns: how to extend the GoF
Abstract Design patterns were popularized by the GoF catalog in 1995. This catalog contains 23 design patterns which concern 23 design problems. Each pattern is detailed with its structure, its intent, and some information including applicability conditions and some possible variations which enable...
Ausführliche Beschreibung
Gespeichert in:
| Autor*in: |
Bouhours, Cédric [verfasserIn] |
|---|
| Format: |
Artikel |
|---|---|
| Sprache: |
Englisch |
| Erschienen: |
2014 |
|---|
| Schlagwörter: |
|---|
| Anmerkung: |
© Springer Science+Business Media New York 2014 |
|---|
| Übergeordnetes Werk: |
Enthalten in: Software quality journal - Springer US, 1992, 23(2014), 4 vom: 26. Aug., Seite 661-694 |
|---|---|
| Übergeordnetes Werk: |
volume:23 ; year:2014 ; number:4 ; day:26 ; month:08 ; pages:661-694 |
| Links: |
|---|
| DOI / URN: |
10.1007/s11219-014-9249-z |
|---|
| Katalog-ID: |
OLC2033732673 |
|---|
| LEADER | 01000caa a22002652 4500 | ||
|---|---|---|---|
| 001 | OLC2033732673 | ||
| 003 | DE-627 | ||
| 005 | 20230504051256.0 | ||
| 007 | tu | ||
| 008 | 200819s2014 xx ||||| 00| ||eng c | ||
| 024 | 7 | |a 10.1007/s11219-014-9249-z |2 doi | |
| 035 | |a (DE-627)OLC2033732673 | ||
| 035 | |a (DE-He213)s11219-014-9249-z-p | ||
| 040 | |a DE-627 |b ger |c DE-627 |e rakwb | ||
| 041 | |a eng | ||
| 082 | 0 | 4 | |a 004 |q VZ |
| 100 | 1 | |a Bouhours, Cédric |e verfasserin |4 aut | |
| 245 | 1 | 0 | |a Spoiled patterns: how to extend the GoF |
| 264 | 1 | |c 2014 | |
| 336 | |a Text |b txt |2 rdacontent | ||
| 337 | |a ohne Hilfsmittel zu benutzen |b n |2 rdamedia | ||
| 338 | |a Band |b nc |2 rdacarrier | ||
| 500 | |a © Springer Science+Business Media New York 2014 | ||
| 520 | |a Abstract Design patterns were popularized by the GoF catalog in 1995. This catalog contains 23 design patterns which concern 23 design problems. Each pattern is detailed with its structure, its intent, and some information including applicability conditions and some possible variations which enable it to be re-used. In 1995, they were the cutting edge thought processes. We consider that design patterns have two major features. First, they are the result of emergent conceptions validated by a community through a well-defined acceptance process. They are a field of expert knowledge. Secondly, they must be as abstract as needed to be able to maximize their reusability. They constitute a compilation of best practices concerning object codes and designs. We propose to extend the GoF with a new concept that we have named “spoiled patterns”. They are midway between bad smells in design necessary to go ahead with a refactoring and a necessary learned lesson in order to explain anti-patterns. Each design pattern corresponds to some spoiled patterns. In this paper, we present how we have compiled the first spoiled patterns catalog, by carrying out several experiments with a lot of young inexperienced designers. | ||
| 650 | 4 | |a Design patterns | |
| 650 | 4 | |a Spoiled patterns | |
| 650 | 4 | |a Best practices | |
| 650 | 4 | |a Bad smells | |
| 650 | 4 | |a Anti-patterns | |
| 650 | 4 | |a Pattern teaching | |
| 700 | 1 | |a Leblanc, Hervé |4 aut | |
| 700 | 1 | |a Percebois, Christian |4 aut | |
| 773 | 0 | 8 | |i Enthalten in |t Software quality journal |d Springer US, 1992 |g 23(2014), 4 vom: 26. Aug., Seite 661-694 |w (DE-627)131154087 |w (DE-600)1131702-4 |w (DE-576)04308236X |x 0963-9314 |7 nnns |
| 773 | 1 | 8 | |g volume:23 |g year:2014 |g number:4 |g day:26 |g month:08 |g pages:661-694 |
| 856 | 4 | 1 | |u https://doi.org/10.1007/s11219-014-9249-z |z lizenzpflichtig |3 Volltext |
| 912 | |a GBV_USEFLAG_A | ||
| 912 | |a SYSFLAG_A | ||
| 912 | |a GBV_OLC | ||
| 912 | |a SSG-OLC-MAT | ||
| 912 | |a GBV_ILN_70 | ||
| 912 | |a GBV_ILN_170 | ||
| 912 | |a GBV_ILN_4046 | ||
| 951 | |a AR | ||
| 952 | |d 23 |j 2014 |e 4 |b 26 |c 08 |h 661-694 | ||
| author_variant |
c b cb h l hl c p cp |
|---|---|
| matchkey_str |
article:09639314:2014----::pieptenhwoxe |
| hierarchy_sort_str |
2014 |
| publishDate |
2014 |
| allfields |
10.1007/s11219-014-9249-z doi (DE-627)OLC2033732673 (DE-He213)s11219-014-9249-z-p DE-627 ger DE-627 rakwb eng 004 VZ Bouhours, Cédric verfasserin aut Spoiled patterns: how to extend the GoF 2014 Text txt rdacontent ohne Hilfsmittel zu benutzen n rdamedia Band nc rdacarrier © Springer Science+Business Media New York 2014 Abstract Design patterns were popularized by the GoF catalog in 1995. This catalog contains 23 design patterns which concern 23 design problems. Each pattern is detailed with its structure, its intent, and some information including applicability conditions and some possible variations which enable it to be re-used. In 1995, they were the cutting edge thought processes. We consider that design patterns have two major features. First, they are the result of emergent conceptions validated by a community through a well-defined acceptance process. They are a field of expert knowledge. Secondly, they must be as abstract as needed to be able to maximize their reusability. They constitute a compilation of best practices concerning object codes and designs. We propose to extend the GoF with a new concept that we have named “spoiled patterns”. They are midway between bad smells in design necessary to go ahead with a refactoring and a necessary learned lesson in order to explain anti-patterns. Each design pattern corresponds to some spoiled patterns. In this paper, we present how we have compiled the first spoiled patterns catalog, by carrying out several experiments with a lot of young inexperienced designers. Design patterns Spoiled patterns Best practices Bad smells Anti-patterns Pattern teaching Leblanc, Hervé aut Percebois, Christian aut Enthalten in Software quality journal Springer US, 1992 23(2014), 4 vom: 26. Aug., Seite 661-694 (DE-627)131154087 (DE-600)1131702-4 (DE-576)04308236X 0963-9314 nnns volume:23 year:2014 number:4 day:26 month:08 pages:661-694 https://doi.org/10.1007/s11219-014-9249-z lizenzpflichtig Volltext GBV_USEFLAG_A SYSFLAG_A GBV_OLC SSG-OLC-MAT GBV_ILN_70 GBV_ILN_170 GBV_ILN_4046 AR 23 2014 4 26 08 661-694 |
| spelling |
10.1007/s11219-014-9249-z doi (DE-627)OLC2033732673 (DE-He213)s11219-014-9249-z-p DE-627 ger DE-627 rakwb eng 004 VZ Bouhours, Cédric verfasserin aut Spoiled patterns: how to extend the GoF 2014 Text txt rdacontent ohne Hilfsmittel zu benutzen n rdamedia Band nc rdacarrier © Springer Science+Business Media New York 2014 Abstract Design patterns were popularized by the GoF catalog in 1995. This catalog contains 23 design patterns which concern 23 design problems. Each pattern is detailed with its structure, its intent, and some information including applicability conditions and some possible variations which enable it to be re-used. In 1995, they were the cutting edge thought processes. We consider that design patterns have two major features. First, they are the result of emergent conceptions validated by a community through a well-defined acceptance process. They are a field of expert knowledge. Secondly, they must be as abstract as needed to be able to maximize their reusability. They constitute a compilation of best practices concerning object codes and designs. We propose to extend the GoF with a new concept that we have named “spoiled patterns”. They are midway between bad smells in design necessary to go ahead with a refactoring and a necessary learned lesson in order to explain anti-patterns. Each design pattern corresponds to some spoiled patterns. In this paper, we present how we have compiled the first spoiled patterns catalog, by carrying out several experiments with a lot of young inexperienced designers. Design patterns Spoiled patterns Best practices Bad smells Anti-patterns Pattern teaching Leblanc, Hervé aut Percebois, Christian aut Enthalten in Software quality journal Springer US, 1992 23(2014), 4 vom: 26. Aug., Seite 661-694 (DE-627)131154087 (DE-600)1131702-4 (DE-576)04308236X 0963-9314 nnns volume:23 year:2014 number:4 day:26 month:08 pages:661-694 https://doi.org/10.1007/s11219-014-9249-z lizenzpflichtig Volltext GBV_USEFLAG_A SYSFLAG_A GBV_OLC SSG-OLC-MAT GBV_ILN_70 GBV_ILN_170 GBV_ILN_4046 AR 23 2014 4 26 08 661-694 |
| allfields_unstemmed |
10.1007/s11219-014-9249-z doi (DE-627)OLC2033732673 (DE-He213)s11219-014-9249-z-p DE-627 ger DE-627 rakwb eng 004 VZ Bouhours, Cédric verfasserin aut Spoiled patterns: how to extend the GoF 2014 Text txt rdacontent ohne Hilfsmittel zu benutzen n rdamedia Band nc rdacarrier © Springer Science+Business Media New York 2014 Abstract Design patterns were popularized by the GoF catalog in 1995. This catalog contains 23 design patterns which concern 23 design problems. Each pattern is detailed with its structure, its intent, and some information including applicability conditions and some possible variations which enable it to be re-used. In 1995, they were the cutting edge thought processes. We consider that design patterns have two major features. First, they are the result of emergent conceptions validated by a community through a well-defined acceptance process. They are a field of expert knowledge. Secondly, they must be as abstract as needed to be able to maximize their reusability. They constitute a compilation of best practices concerning object codes and designs. We propose to extend the GoF with a new concept that we have named “spoiled patterns”. They are midway between bad smells in design necessary to go ahead with a refactoring and a necessary learned lesson in order to explain anti-patterns. Each design pattern corresponds to some spoiled patterns. In this paper, we present how we have compiled the first spoiled patterns catalog, by carrying out several experiments with a lot of young inexperienced designers. Design patterns Spoiled patterns Best practices Bad smells Anti-patterns Pattern teaching Leblanc, Hervé aut Percebois, Christian aut Enthalten in Software quality journal Springer US, 1992 23(2014), 4 vom: 26. Aug., Seite 661-694 (DE-627)131154087 (DE-600)1131702-4 (DE-576)04308236X 0963-9314 nnns volume:23 year:2014 number:4 day:26 month:08 pages:661-694 https://doi.org/10.1007/s11219-014-9249-z lizenzpflichtig Volltext GBV_USEFLAG_A SYSFLAG_A GBV_OLC SSG-OLC-MAT GBV_ILN_70 GBV_ILN_170 GBV_ILN_4046 AR 23 2014 4 26 08 661-694 |
| allfieldsGer |
10.1007/s11219-014-9249-z doi (DE-627)OLC2033732673 (DE-He213)s11219-014-9249-z-p DE-627 ger DE-627 rakwb eng 004 VZ Bouhours, Cédric verfasserin aut Spoiled patterns: how to extend the GoF 2014 Text txt rdacontent ohne Hilfsmittel zu benutzen n rdamedia Band nc rdacarrier © Springer Science+Business Media New York 2014 Abstract Design patterns were popularized by the GoF catalog in 1995. This catalog contains 23 design patterns which concern 23 design problems. Each pattern is detailed with its structure, its intent, and some information including applicability conditions and some possible variations which enable it to be re-used. In 1995, they were the cutting edge thought processes. We consider that design patterns have two major features. First, they are the result of emergent conceptions validated by a community through a well-defined acceptance process. They are a field of expert knowledge. Secondly, they must be as abstract as needed to be able to maximize their reusability. They constitute a compilation of best practices concerning object codes and designs. We propose to extend the GoF with a new concept that we have named “spoiled patterns”. They are midway between bad smells in design necessary to go ahead with a refactoring and a necessary learned lesson in order to explain anti-patterns. Each design pattern corresponds to some spoiled patterns. In this paper, we present how we have compiled the first spoiled patterns catalog, by carrying out several experiments with a lot of young inexperienced designers. Design patterns Spoiled patterns Best practices Bad smells Anti-patterns Pattern teaching Leblanc, Hervé aut Percebois, Christian aut Enthalten in Software quality journal Springer US, 1992 23(2014), 4 vom: 26. Aug., Seite 661-694 (DE-627)131154087 (DE-600)1131702-4 (DE-576)04308236X 0963-9314 nnns volume:23 year:2014 number:4 day:26 month:08 pages:661-694 https://doi.org/10.1007/s11219-014-9249-z lizenzpflichtig Volltext GBV_USEFLAG_A SYSFLAG_A GBV_OLC SSG-OLC-MAT GBV_ILN_70 GBV_ILN_170 GBV_ILN_4046 AR 23 2014 4 26 08 661-694 |
| allfieldsSound |
10.1007/s11219-014-9249-z doi (DE-627)OLC2033732673 (DE-He213)s11219-014-9249-z-p DE-627 ger DE-627 rakwb eng 004 VZ Bouhours, Cédric verfasserin aut Spoiled patterns: how to extend the GoF 2014 Text txt rdacontent ohne Hilfsmittel zu benutzen n rdamedia Band nc rdacarrier © Springer Science+Business Media New York 2014 Abstract Design patterns were popularized by the GoF catalog in 1995. This catalog contains 23 design patterns which concern 23 design problems. Each pattern is detailed with its structure, its intent, and some information including applicability conditions and some possible variations which enable it to be re-used. In 1995, they were the cutting edge thought processes. We consider that design patterns have two major features. First, they are the result of emergent conceptions validated by a community through a well-defined acceptance process. They are a field of expert knowledge. Secondly, they must be as abstract as needed to be able to maximize their reusability. They constitute a compilation of best practices concerning object codes and designs. We propose to extend the GoF with a new concept that we have named “spoiled patterns”. They are midway between bad smells in design necessary to go ahead with a refactoring and a necessary learned lesson in order to explain anti-patterns. Each design pattern corresponds to some spoiled patterns. In this paper, we present how we have compiled the first spoiled patterns catalog, by carrying out several experiments with a lot of young inexperienced designers. Design patterns Spoiled patterns Best practices Bad smells Anti-patterns Pattern teaching Leblanc, Hervé aut Percebois, Christian aut Enthalten in Software quality journal Springer US, 1992 23(2014), 4 vom: 26. Aug., Seite 661-694 (DE-627)131154087 (DE-600)1131702-4 (DE-576)04308236X 0963-9314 nnns volume:23 year:2014 number:4 day:26 month:08 pages:661-694 https://doi.org/10.1007/s11219-014-9249-z lizenzpflichtig Volltext GBV_USEFLAG_A SYSFLAG_A GBV_OLC SSG-OLC-MAT GBV_ILN_70 GBV_ILN_170 GBV_ILN_4046 AR 23 2014 4 26 08 661-694 |
| language |
English |
| source |
Enthalten in Software quality journal 23(2014), 4 vom: 26. Aug., Seite 661-694 volume:23 year:2014 number:4 day:26 month:08 pages:661-694 |
| sourceStr |
Enthalten in Software quality journal 23(2014), 4 vom: 26. Aug., Seite 661-694 volume:23 year:2014 number:4 day:26 month:08 pages:661-694 |
| format_phy_str_mv |
Article |
| institution |
findex.gbv.de |
| topic_facet |
Design patterns Spoiled patterns Best practices Bad smells Anti-patterns Pattern teaching |
| dewey-raw |
004 |
| isfreeaccess_bool |
false |
| container_title |
Software quality journal |
| authorswithroles_txt_mv |
Bouhours, Cédric @@aut@@ Leblanc, Hervé @@aut@@ Percebois, Christian @@aut@@ |
| publishDateDaySort_date |
2014-08-26T00:00:00Z |
| hierarchy_top_id |
131154087 |
| dewey-sort |
14 |
| id |
OLC2033732673 |
| language_de |
englisch |
| fullrecord |
<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01000caa a22002652 4500</leader><controlfield tag="001">OLC2033732673</controlfield><controlfield tag="003">DE-627</controlfield><controlfield tag="005">20230504051256.0</controlfield><controlfield tag="007">tu</controlfield><controlfield tag="008">200819s2014 xx ||||| 00| ||eng c</controlfield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.1007/s11219-014-9249-z</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627)OLC2033732673</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-He213)s11219-014-9249-z-p</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="082" ind1="0" ind2="4"><subfield code="a">004</subfield><subfield code="q">VZ</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Bouhours, Cédric</subfield><subfield code="e">verfasserin</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Spoiled patterns: how to extend the GoF</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="c">2014</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">Text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">ohne Hilfsmittel zu benutzen</subfield><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Band</subfield><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">© Springer Science+Business Media New York 2014</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">Abstract Design patterns were popularized by the GoF catalog in 1995. This catalog contains 23 design patterns which concern 23 design problems. Each pattern is detailed with its structure, its intent, and some information including applicability conditions and some possible variations which enable it to be re-used. In 1995, they were the cutting edge thought processes. We consider that design patterns have two major features. First, they are the result of emergent conceptions validated by a community through a well-defined acceptance process. They are a field of expert knowledge. Secondly, they must be as abstract as needed to be able to maximize their reusability. They constitute a compilation of best practices concerning object codes and designs. We propose to extend the GoF with a new concept that we have named “spoiled patterns”. They are midway between bad smells in design necessary to go ahead with a refactoring and a necessary learned lesson in order to explain anti-patterns. Each design pattern corresponds to some spoiled patterns. In this paper, we present how we have compiled the first spoiled patterns catalog, by carrying out several experiments with a lot of young inexperienced designers.</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Design patterns</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Spoiled patterns</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Best practices</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Bad smells</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Anti-patterns</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Pattern teaching</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Leblanc, Hervé</subfield><subfield code="4">aut</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Percebois, Christian</subfield><subfield code="4">aut</subfield></datafield><datafield tag="773" ind1="0" ind2="8"><subfield code="i">Enthalten in</subfield><subfield code="t">Software quality journal</subfield><subfield code="d">Springer US, 1992</subfield><subfield code="g">23(2014), 4 vom: 26. Aug., Seite 661-694</subfield><subfield code="w">(DE-627)131154087</subfield><subfield code="w">(DE-600)1131702-4</subfield><subfield code="w">(DE-576)04308236X</subfield><subfield code="x">0963-9314</subfield><subfield code="7">nnns</subfield></datafield><datafield tag="773" ind1="1" ind2="8"><subfield code="g">volume:23</subfield><subfield code="g">year:2014</subfield><subfield code="g">number:4</subfield><subfield code="g">day:26</subfield><subfield code="g">month:08</subfield><subfield code="g">pages:661-694</subfield></datafield><datafield tag="856" ind1="4" ind2="1"><subfield code="u">https://doi.org/10.1007/s11219-014-9249-z</subfield><subfield code="z">lizenzpflichtig</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_USEFLAG_A</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SYSFLAG_A</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_OLC</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SSG-OLC-MAT</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_70</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_170</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4046</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">AR</subfield></datafield><datafield tag="952" ind1=" " ind2=" "><subfield code="d">23</subfield><subfield code="j">2014</subfield><subfield code="e">4</subfield><subfield code="b">26</subfield><subfield code="c">08</subfield><subfield code="h">661-694</subfield></datafield></record></collection>
|
| author |
Bouhours, Cédric |
| spellingShingle |
Bouhours, Cédric ddc 004 misc Design patterns misc Spoiled patterns misc Best practices misc Bad smells misc Anti-patterns misc Pattern teaching Spoiled patterns: how to extend the GoF |
| authorStr |
Bouhours, Cédric |
| ppnlink_with_tag_str_mv |
@@773@@(DE-627)131154087 |
| format |
Article |
| dewey-ones |
004 - Data processing & computer science |
| delete_txt_mv |
keep |
| author_role |
aut aut aut |
| collection |
OLC |
| remote_str |
false |
| illustrated |
Not Illustrated |
| issn |
0963-9314 |
| topic_title |
004 VZ Spoiled patterns: how to extend the GoF Design patterns Spoiled patterns Best practices Bad smells Anti-patterns Pattern teaching |
| topic |
ddc 004 misc Design patterns misc Spoiled patterns misc Best practices misc Bad smells misc Anti-patterns misc Pattern teaching |
| topic_unstemmed |
ddc 004 misc Design patterns misc Spoiled patterns misc Best practices misc Bad smells misc Anti-patterns misc Pattern teaching |
| topic_browse |
ddc 004 misc Design patterns misc Spoiled patterns misc Best practices misc Bad smells misc Anti-patterns misc Pattern teaching |
| format_facet |
Aufsätze Gedruckte Aufsätze |
| format_main_str_mv |
Text Zeitschrift/Artikel |
| carriertype_str_mv |
nc |
| hierarchy_parent_title |
Software quality journal |
| hierarchy_parent_id |
131154087 |
| dewey-tens |
000 - Computer science, knowledge & systems |
| hierarchy_top_title |
Software quality journal |
| isfreeaccess_txt |
false |
| familylinks_str_mv |
(DE-627)131154087 (DE-600)1131702-4 (DE-576)04308236X |
| title |
Spoiled patterns: how to extend the GoF |
| ctrlnum |
(DE-627)OLC2033732673 (DE-He213)s11219-014-9249-z-p |
| title_full |
Spoiled patterns: how to extend the GoF |
| author_sort |
Bouhours, Cédric |
| journal |
Software quality journal |
| journalStr |
Software quality journal |
| lang_code |
eng |
| isOA_bool |
false |
| dewey-hundreds |
000 - Computer science, information & general works |
| recordtype |
marc |
| publishDateSort |
2014 |
| contenttype_str_mv |
txt |
| container_start_page |
661 |
| author_browse |
Bouhours, Cédric Leblanc, Hervé Percebois, Christian |
| container_volume |
23 |
| class |
004 VZ |
| format_se |
Aufsätze |
| author-letter |
Bouhours, Cédric |
| doi_str_mv |
10.1007/s11219-014-9249-z |
| dewey-full |
004 |
| title_sort |
spoiled patterns: how to extend the gof |
| title_auth |
Spoiled patterns: how to extend the GoF |
| abstract |
Abstract Design patterns were popularized by the GoF catalog in 1995. This catalog contains 23 design patterns which concern 23 design problems. Each pattern is detailed with its structure, its intent, and some information including applicability conditions and some possible variations which enable it to be re-used. In 1995, they were the cutting edge thought processes. We consider that design patterns have two major features. First, they are the result of emergent conceptions validated by a community through a well-defined acceptance process. They are a field of expert knowledge. Secondly, they must be as abstract as needed to be able to maximize their reusability. They constitute a compilation of best practices concerning object codes and designs. We propose to extend the GoF with a new concept that we have named “spoiled patterns”. They are midway between bad smells in design necessary to go ahead with a refactoring and a necessary learned lesson in order to explain anti-patterns. Each design pattern corresponds to some spoiled patterns. In this paper, we present how we have compiled the first spoiled patterns catalog, by carrying out several experiments with a lot of young inexperienced designers. © Springer Science+Business Media New York 2014 |
| abstractGer |
Abstract Design patterns were popularized by the GoF catalog in 1995. This catalog contains 23 design patterns which concern 23 design problems. Each pattern is detailed with its structure, its intent, and some information including applicability conditions and some possible variations which enable it to be re-used. In 1995, they were the cutting edge thought processes. We consider that design patterns have two major features. First, they are the result of emergent conceptions validated by a community through a well-defined acceptance process. They are a field of expert knowledge. Secondly, they must be as abstract as needed to be able to maximize their reusability. They constitute a compilation of best practices concerning object codes and designs. We propose to extend the GoF with a new concept that we have named “spoiled patterns”. They are midway between bad smells in design necessary to go ahead with a refactoring and a necessary learned lesson in order to explain anti-patterns. Each design pattern corresponds to some spoiled patterns. In this paper, we present how we have compiled the first spoiled patterns catalog, by carrying out several experiments with a lot of young inexperienced designers. © Springer Science+Business Media New York 2014 |
| abstract_unstemmed |
Abstract Design patterns were popularized by the GoF catalog in 1995. This catalog contains 23 design patterns which concern 23 design problems. Each pattern is detailed with its structure, its intent, and some information including applicability conditions and some possible variations which enable it to be re-used. In 1995, they were the cutting edge thought processes. We consider that design patterns have two major features. First, they are the result of emergent conceptions validated by a community through a well-defined acceptance process. They are a field of expert knowledge. Secondly, they must be as abstract as needed to be able to maximize their reusability. They constitute a compilation of best practices concerning object codes and designs. We propose to extend the GoF with a new concept that we have named “spoiled patterns”. They are midway between bad smells in design necessary to go ahead with a refactoring and a necessary learned lesson in order to explain anti-patterns. Each design pattern corresponds to some spoiled patterns. In this paper, we present how we have compiled the first spoiled patterns catalog, by carrying out several experiments with a lot of young inexperienced designers. © Springer Science+Business Media New York 2014 |
| collection_details |
GBV_USEFLAG_A SYSFLAG_A GBV_OLC SSG-OLC-MAT GBV_ILN_70 GBV_ILN_170 GBV_ILN_4046 |
| container_issue |
4 |
| title_short |
Spoiled patterns: how to extend the GoF |
| url |
https://doi.org/10.1007/s11219-014-9249-z |
| remote_bool |
false |
| author2 |
Leblanc, Hervé Percebois, Christian |
| author2Str |
Leblanc, Hervé Percebois, Christian |
| ppnlink |
131154087 |
| mediatype_str_mv |
n |
| isOA_txt |
false |
| hochschulschrift_bool |
false |
| doi_str |
10.1007/s11219-014-9249-z |
| up_date |
2024-07-03T18:13:13.207Z |
| _version_ |
1803582589587423232 |
| fullrecord_marcxml |
<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01000caa a22002652 4500</leader><controlfield tag="001">OLC2033732673</controlfield><controlfield tag="003">DE-627</controlfield><controlfield tag="005">20230504051256.0</controlfield><controlfield tag="007">tu</controlfield><controlfield tag="008">200819s2014 xx ||||| 00| ||eng c</controlfield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.1007/s11219-014-9249-z</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627)OLC2033732673</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-He213)s11219-014-9249-z-p</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="082" ind1="0" ind2="4"><subfield code="a">004</subfield><subfield code="q">VZ</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Bouhours, Cédric</subfield><subfield code="e">verfasserin</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Spoiled patterns: how to extend the GoF</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="c">2014</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">Text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">ohne Hilfsmittel zu benutzen</subfield><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Band</subfield><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">© Springer Science+Business Media New York 2014</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">Abstract Design patterns were popularized by the GoF catalog in 1995. This catalog contains 23 design patterns which concern 23 design problems. Each pattern is detailed with its structure, its intent, and some information including applicability conditions and some possible variations which enable it to be re-used. In 1995, they were the cutting edge thought processes. We consider that design patterns have two major features. First, they are the result of emergent conceptions validated by a community through a well-defined acceptance process. They are a field of expert knowledge. Secondly, they must be as abstract as needed to be able to maximize their reusability. They constitute a compilation of best practices concerning object codes and designs. We propose to extend the GoF with a new concept that we have named “spoiled patterns”. They are midway between bad smells in design necessary to go ahead with a refactoring and a necessary learned lesson in order to explain anti-patterns. Each design pattern corresponds to some spoiled patterns. In this paper, we present how we have compiled the first spoiled patterns catalog, by carrying out several experiments with a lot of young inexperienced designers.</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Design patterns</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Spoiled patterns</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Best practices</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Bad smells</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Anti-patterns</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Pattern teaching</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Leblanc, Hervé</subfield><subfield code="4">aut</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Percebois, Christian</subfield><subfield code="4">aut</subfield></datafield><datafield tag="773" ind1="0" ind2="8"><subfield code="i">Enthalten in</subfield><subfield code="t">Software quality journal</subfield><subfield code="d">Springer US, 1992</subfield><subfield code="g">23(2014), 4 vom: 26. Aug., Seite 661-694</subfield><subfield code="w">(DE-627)131154087</subfield><subfield code="w">(DE-600)1131702-4</subfield><subfield code="w">(DE-576)04308236X</subfield><subfield code="x">0963-9314</subfield><subfield code="7">nnns</subfield></datafield><datafield tag="773" ind1="1" ind2="8"><subfield code="g">volume:23</subfield><subfield code="g">year:2014</subfield><subfield code="g">number:4</subfield><subfield code="g">day:26</subfield><subfield code="g">month:08</subfield><subfield code="g">pages:661-694</subfield></datafield><datafield tag="856" ind1="4" ind2="1"><subfield code="u">https://doi.org/10.1007/s11219-014-9249-z</subfield><subfield code="z">lizenzpflichtig</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_USEFLAG_A</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SYSFLAG_A</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_OLC</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SSG-OLC-MAT</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_70</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_170</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4046</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">AR</subfield></datafield><datafield tag="952" ind1=" " ind2=" "><subfield code="d">23</subfield><subfield code="j">2014</subfield><subfield code="e">4</subfield><subfield code="b">26</subfield><subfield code="c">08</subfield><subfield code="h">661-694</subfield></datafield></record></collection>
|
| score |
7.3996735 |