<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title></title>
	<atom:link href="http://pattern.ijop.org/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://pattern.ijop.org</link>
	<description></description>
	<lastBuildDate>Sun, 25 Oct 2009 07:19:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Pitfalls in Traditional Software Patterns</title>
		<link>http://pattern.ijop.org/?p=36</link>
		<comments>http://pattern.ijop.org/?p=36#comments</comments>
		<pubDate>Mon, 02 Jul 2007 18:44:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Pitfalls of Traditional Software Patterns]]></category>

		<guid isPermaLink="false">http://pattern.ijop.org/?p=36</guid>
		<description><![CDATA[Analyzing Pitfalls to Seek a Permanent SolutionM.E. Fayad, PhD &#038; &#038; G. K. Srikanth, IJOP, IJSA, IJSR Sr. Editor

In the above columns we highlighted fourteen of the major problems that are believed to diminish the strength of the role of patterns in developing software systems.

CONCLUSIONS

Pattern development poses several unique challenges to the pattern developers, like [...]]]></description>
		<wfw:commentRss>http://pattern.ijop.org/?feed=rss2&amp;p=36</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title></title>
		<link>http://pattern.ijop.org/?p=35</link>
		<comments>http://pattern.ijop.org/?p=35#comments</comments>
		<pubDate>Mon, 02 Jul 2007 18:25:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Pitfalls of Traditional Software Patterns]]></category>

		<guid isPermaLink="false">http://pattern.ijop.org/?p=35</guid>
		<description><![CDATA[Reinventing the Wheel: An Undesirable and Dangerous Development
M.E. Fayad, Ph.D &#038; Shasha Wu, PhD

“A pattern is a plan, rather than a specific implementation.’’ [1]. Pattern developers never directly use design patterns to guide programming. They are guides for modeling purposes. A pattern is “an attempt to describe successful solutions to common software problems.” [2]. “Design [...]]]></description>
		<wfw:commentRss>http://pattern.ijop.org/?feed=rss2&amp;p=35</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title></title>
		<link>http://pattern.ijop.org/?p=34</link>
		<comments>http://pattern.ijop.org/?p=34#comments</comments>
		<pubDate>Mon, 25 Jun 2007 17:21:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Pitfalls of Traditional Software Patterns]]></category>

		<guid isPermaLink="false">http://pattern.ijop.org/?p=34</guid>
		<description><![CDATA[Modeling Problems are Nagging Obstacles to Creating Meaningful Patterns
M.E. Fayad, Ph.D

It is a common fact that the solution for any pattern consists of two different models: static, mainly class diagrams, and dynamic, by using sequence diagrams or state transition diagrams.



Let us visit Figure 1, in Pitfall #9, the model of the Resource Rental pattern [1, [...]]]></description>
		<wfw:commentRss>http://pattern.ijop.org/?feed=rss2&amp;p=34</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title></title>
		<link>http://pattern.ijop.org/?p=33</link>
		<comments>http://pattern.ijop.org/?p=33#comments</comments>
		<pubDate>Fri, 22 Jun 2007 21:05:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Pitfalls of Traditional Software Patterns]]></category>

		<guid isPermaLink="false">http://pattern.ijop.org/?p=33</guid>
		<description><![CDATA[Outdated and Jaded Patterns or Fresh and Everlasting Patterns:  Choose your Pick!
M.E. Fayad, Ph.D


As these reasons might provide a useful insight into why patterns die or become outdated, they also provide many ideas and clues about the critical question: why have not patterns fulfilled the expectation of playing a crucial role in software development?


Even [...]]]></description>
		<wfw:commentRss>http://pattern.ijop.org/?feed=rss2&amp;p=33</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title></title>
		<link>http://pattern.ijop.org/?p=32</link>
		<comments>http://pattern.ijop.org/?p=32#comments</comments>
		<pubDate>Wed, 20 Jun 2007 19:45:23 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Pitfalls of Traditional Software Patterns]]></category>

		<guid isPermaLink="false">http://pattern.ijop.org/?p=32</guid>
		<description><![CDATA[Chasing an Elusive Vocabulary: Importance of Vocabulary in Pattern Development
M.E. Fayad, Ph.D

One of the specific benefits of using patterns resides in developing a common vocabulary by which software and pattern developers, in any development phase, can easily communicate and discuss their project concepts. Such a common vocabulary simplifies the basic description of complex systems.  [...]]]></description>
		<wfw:commentRss>http://pattern.ijop.org/?feed=rss2&amp;p=32</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title></title>
		<link>http://pattern.ijop.org/?p=31</link>
		<comments>http://pattern.ijop.org/?p=31#comments</comments>
		<pubDate>Tue, 19 Jun 2007 21:32:33 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Pitfalls of Traditional Software Patterns]]></category>

		<guid isPermaLink="false">http://pattern.ijop.org/?p=31</guid>
		<description><![CDATA[No Guidelines for Extracting Patterns
M.E. Fayad, Ph.D

Another major challenge that confronts pattern designers while designing today’s patterns is the absence of a clear guidance or methodology for already extracting patterns. GOF [1] has stated explicitly in their book on page 355:”…that finding patterns is much easier than describing them.” Creating and documenting patterns that everyone [...]]]></description>
		<wfw:commentRss>http://pattern.ijop.org/?feed=rss2&amp;p=31</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title></title>
		<link>http://pattern.ijop.org/?p=30</link>
		<comments>http://pattern.ijop.org/?p=30#comments</comments>
		<pubDate>Sun, 10 Jun 2007 17:24:03 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Pitfalls of Traditional Software Patterns]]></category>

		<guid isPermaLink="false">http://pattern.ijop.org/?p=30</guid>
		<description><![CDATA[Untraceable Patterns-The Pitfall of the Pattern Systems
M.E. Fayad, Ph.D

Today, developers consider many software patterns, especially those in the area of analysis, as templates. In [1], Peter Code has defined patterns in briefly as following: “A pattern is a template of interacting objects, one that may be used again and again by analogy”. Simply speaking, the [...]]]></description>
		<wfw:commentRss>http://pattern.ijop.org/?feed=rss2&amp;p=30</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title></title>
		<link>http://pattern.ijop.org/?p=28</link>
		<comments>http://pattern.ijop.org/?p=28#comments</comments>
		<pubDate>Sat, 09 Jun 2007 16:10:04 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Pitfalls of Traditional Software Patterns]]></category>

		<guid isPermaLink="false">http://pattern.ijop.org/?p=28</guid>
		<description><![CDATA[Lack of Patterns Connectivity across Development Phases
M.E. Fayad, Ph.D &#038; G. K. Srikanth, IJOP, Sr.Editor

The point highlighted in the previous pitfall illustrated the challenge of integrating patterns within the same developmental phase. Integrating a given pattern is often a major challenge and a strenuous task for any developer of patterns. However, a different set of [...]]]></description>
		<wfw:commentRss>http://pattern.ijop.org/?feed=rss2&amp;p=28</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title></title>
		<link>http://pattern.ijop.org/?p=27</link>
		<comments>http://pattern.ijop.org/?p=27#comments</comments>
		<pubDate>Sat, 09 Jun 2007 15:52:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Pitfalls of Traditional Software Patterns]]></category>

		<guid isPermaLink="false">http://pattern.ijop.org/?p=27</guid>
		<description><![CDATA[A Brief Summary of Pattern Compositions:Understanding the Insider’s Secrets
M.E. Fayad, Ph.D &#038; G. K. Srikanth, IJOP, Sr.Editor

Pattern composition is the intimate process of integrating and hemming different patterns of the similar type (i.e. design patterns, analysis patterns, etc) to build and design larger components or different types of patterns that also include process patterns, managerial [...]]]></description>
		<wfw:commentRss>http://pattern.ijop.org/?feed=rss2&amp;p=27</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title></title>
		<link>http://pattern.ijop.org/?p=25</link>
		<comments>http://pattern.ijop.org/?p=25#comments</comments>
		<pubDate>Wed, 18 Apr 2007 04:36:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Pitfalls of Traditional Software Patterns]]></category>

		<guid isPermaLink="false">http://pattern.ijop.org/?p=25</guid>
		<description><![CDATA[Focus! Focus! Focus! Golden Words for Developing Meaningful Patterns
M.E. Fayad, Ph.D.

If a developer wishes to develop meaningful patterns, he or she will need to identify the perimeter of the problems that these patterns model or solve. In many cases, it is quite difficult and cumbersome to identify the boundary of the problems. In absence of [...]]]></description>
		<wfw:commentRss>http://pattern.ijop.org/?feed=rss2&amp;p=25</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
