<?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>Linux Future</title>
	<atom:link href="http://www.linuxfuture.org/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.linuxfuture.org</link>
	<description>Shorthanding Technology</description>
	<lastBuildDate>Thu, 08 Dec 2011 21:08:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>الخط الأميري</title>
		<link>http://www.linuxfuture.org/2011/12/%d8%a7%d9%84%d8%ae%d8%b7-%d8%a7%d9%84%d8%a3%d9%85%d9%8a%d8%b1%d9%8a/</link>
		<comments>http://www.linuxfuture.org/2011/12/%d8%a7%d9%84%d8%ae%d8%b7-%d8%a7%d9%84%d8%a3%d9%85%d9%8a%d8%b1%d9%8a/#comments</comments>
		<pubDate>Sun, 04 Dec 2011 18:33:39 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[Arabesque]]></category>
		<category><![CDATA[Localization]]></category>

		<guid isPermaLink="false">http://www.linuxfuture.org/?p=467</guid>
		<description><![CDATA[أخيراً أنجب عالم المصادر المفتوحة على يد الدكتور خالد حسني الخط العربي الذي طالما افتقده المستخدم العربي في واحة لينكس. فعلى الرغم من توفر نموذجين في بيئة لينكس حتى الآن للخط النسخي الطباعي الذي لا غنى عنه لكل (طابعة عربية)، وهما خط KacstBook من تطوير مدينة الملك عبد العزيز للعلوم والتقنية، وشهرزاد من معهد SIL، [...]]]></description>
			<content:encoded><![CDATA[<div dir="rtl" lang="ar" style="text-align: right;">
<p>أخيراً أنجب عالم المصادر المفتوحة على يد الدكتور خالد حسني الخط العربي الذي طالما افتقده المستخدم العربي في واحة لينكس. فعلى الرغم من توفر نموذجين في بيئة لينكس حتى الآن للخط النسخي الطباعي الذي لا غنى عنه لكل (طابعة عربية)، وهما خط KacstBook من تطوير مدينة الملك عبد العزيز للعلوم والتقنية، وشهرزاد من معهد SIL، إلا أنهما ظلا دون طموحات رواد الطباعة والخط العربي، نظراً لافتقارهما للتراكبات الغنية التي طالما تغنت بها يد الخطاط العربي.</p>
<p>فيما يلي مقارنة بين الخطوط الثلاثة إلى جانب خط Traditional Arabic المعروف من مايكروسوفت فيما يتعلق بالتراكبات.</p>
<div id="attachment_468" class="wp-caption aligncenter" style="width: 236px"><a rel="attachment wp-att-468" href="http://www.linuxfuture.org/2011/12/%d8%a7%d9%84%d8%ae%d8%b7-%d8%a7%d9%84%d8%a3%d9%85%d9%8a%d8%b1%d9%8a/amiri/"><img class="size-medium wp-image-468" title="Amiri" src="http://www.linuxfuture.org/wp-content/uploads/2011/12/Amiri-226x300.png" alt="تراكبات الخط الأميري" width="226" height="300" /></a><p class="wp-caption-text">تراكبات الخط الأميري</p></div>
<p>بقي أن أشير إلى أن هذا الخط لا ينطوي على أي محارف لاتينية، وهو ما يقد يربك المستخدم عند إدراج نصوص لاتينية في سياق نص عربي كتب بالخط الأميري.</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.linuxfuture.org/2011/12/%d8%a7%d9%84%d8%ae%d8%b7-%d8%a7%d9%84%d8%a3%d9%85%d9%8a%d8%b1%d9%8a/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>نقاط على الحروف العربية، واقع الخط العربي في ظل عصر الحوسبة</title>
		<link>http://www.linuxfuture.org/2011/11/%d9%86%d9%82%d8%a7%d8%b7-%d8%b9%d9%84%d9%89-%d8%a7%d9%84%d8%ad%d8%b1%d9%88%d9%81-%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9%d8%8c-%d9%88%d8%a7%d9%82%d8%b9-%d8%a7%d9%84%d8%ae%d8%b7-%d8%a7%d9%84%d8%b9/</link>
		<comments>http://www.linuxfuture.org/2011/11/%d9%86%d9%82%d8%a7%d8%b7-%d8%b9%d9%84%d9%89-%d8%a7%d9%84%d8%ad%d8%b1%d9%88%d9%81-%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9%d8%8c-%d9%88%d8%a7%d9%82%d8%b9-%d8%a7%d9%84%d8%ae%d8%b7-%d8%a7%d9%84%d8%b9/#comments</comments>
		<pubDate>Thu, 24 Nov 2011 10:32:52 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[Arabesque]]></category>
		<category><![CDATA[Localization]]></category>

		<guid isPermaLink="false">http://www.linuxfuture.org/?p=450</guid>
		<description><![CDATA[لوحة فنية هادئة، متناسقة العناصر والألوان، صادفتني في مكتب أحد العاملين في حقل التصميم الفني والإعلاني، ردت إلي &#8211; على تواضعها &#8211; شيئاً من الإحساس برونق الخط العربي البديع وسحره، والذي تبدد أو كاد مع زخم التيار التقني الجارف الذي حصد فيما حصد روح الفن البشري في كثير من مناحي الحياة. الخط العربي&#8230; فن خلدته [...]]]></description>
			<content:encoded><![CDATA[<div dir="rtl" lang="ar" style="text-align:right">
<p>لوحة فنية هادئة، متناسقة العناصر والألوان، صادفتني في مكتب أحد العاملين في حقل التصميم الفني والإعلاني، ردت إلي &#8211; على تواضعها &#8211; شيئاً من الإحساس برونق الخط العربي البديع وسحره، والذي تبدد أو كاد مع زخم التيار التقني الجارف الذي حصد فيما حصد روح الفن البشري في كثير من مناحي الحياة.</p>
<p>الخط العربي&#8230;</p>
<p>فن خلدته أوابد الحضارة الإسلامية، وازينت به جنبات المتاحف الغربية، لينتهي به المطاف أسير قوالب تقنية صماء لا روح فيها ولا حياة، تصلبت فيها شرايينه وتيبست فيها أوصاله، فغدا هو الآخر عليلاً بدائها&#8230; صورة ميتة لا نبض فيها ولا حياة!<span id="more-450"></span></p>
<p>لكن صاحبنا استدرك مشيراً إلى أن هذه اللوحة ليست نتاج عمل يدوي أبدعته ريشة خطاط ماهر كما ظننت، بل هو برنامج حاسوبي متخصص بمعالجة الخط العربي.</p>
<p>إذن دعوني أوضح أمراً. لست هنا بصدد تجريم التقنية بذاتها، وهي التي كانت ولا تزال صنيعة الإنسان وأداته في ذات الوقت أولاً وأخيراً، وإنما أعتقد أننا أمام مشكلة تتعلق بالتوظيف السليم والحكيم للتقنية وأدواتها.</p>
<h2>الخط العربي، ريشة في مهب الريح!</h2>
<p>بداية، ومن واقع ما يبديه الحاسوب من قدرة في التعاطي مع الخط العربي بأشكاله التقليدية، أعتقد أنه يمكن فرز الخطوط العربية التقليدية إلى فئتين:</p>
<ul>
<li>خطوط ثابتة الأبعاد والتراكيب، يتخذ الحرف فيها شكلاً ثابتاً أو أشكالاً محدودة لا يحيد عنها،</li>
<li>وأخرى غنية بالتراكيب المتغيرة والمتباينة، يمكن للحرف فيها أن يخضع للكثير من التصرف والتغيير وفقاً لموضعه في السياق وماهية الأحرف السابقة واللاحقة، فضلاً عن اللمسات الفنية التي يمكن ابتكارها وإضافتها من قبل هذا الخطاط أو ذاك.</li>
</ul>
<p>وفقاً لهذا التصنيف يندرج في الفئة الأولى كل من الكوفي والنسخي الطباعي، ويندرج في الفئة الثانية كل من الثلث والديواني والفارسي. ويبقى كل من النسخي القديم (اليدوي) والرقعة في حالةٍ وسط بين الفئتين.</p>
<p>تشير التجارب حتى الآن إلى أن ملفات خطوط الحاسب (كـ <span lang="en-us">TTF</span> وغيرها)، أعطت نتائج طيبة فيما يتعلق بالفئة الأولى من الخطوط، في حين لم تبدِ مرونة كافية في التعامل مع الفئة الثانية، أي أن صلاحية هذه الملفات حتى الآن لا تزال محصورة في كل من الكوفي والنسخي فقط، ولا يمكن التعويل عليها في الخطوط ذات التراكيب الغنية والمتنوعة.</p>
<p>وقد حاولت مايكروسوفت بمجموعة خطوطها &#8220;آرابيسك&#8221; الالتفاف على هذه المشكلة ، حيث احتلت كلََّ (خانة حرفية) فيها جملةٌ شائعة الاستخدام في عناوين الكتب والمطبوعات &#8211; بدلاً من حرف واحد، كالبسملة و (تمهيد) و (مقدمة) و (كل عام وأنتم يخير)، (مرسومة) بأعلى درجات الإتقان. إلا أن حلاً كهذا سيبقى محدوداً بنصوص معينة وجاهزة.</p>
<p>ويقدم برنامج (كلك) التجاري حلاً في هذا الميدان، حيث يتيح لك الكتابة بكل من الفارسي والثلث بصورة رئيسية. يعامل البرنامج كل مقطع من الكلمة الواحدة كوحدة مستقلة، يمكن تغييرها وانتقاء أشكال أخرى منها. حيث تجد طيفاً واسعاً من الأشكال والأنماط المتنوعة لكل من (بر) و (نا) و (مج) على حدة في كلمة (برنامج) على سبيل المثال. إلا أن الذوق الرفيع والخبرة المعمقة بالخط العربي لدى المستخدم هنا تلعب دوراً حيوياً في تكوين نص ناجح فنياً، وذلك من خلال الانتقاء الحكيم للتراكيب المتاحة لكل مقطع من هذه المقاطع من جهة، وإزاحة هذه المقاطع وتحريكها، ورصها ورصفها جنباً إلى جنب بدقة وعناية من جهة أخرى، وهو ما لا يتعهد لك البرنامج بالقيام به عنك من تلقاء نفسه.</p>
<div id="attachment_451" class="wp-caption aligncenter" style="width: 310px"><a rel="attachment wp-att-451" href="http://www.linuxfuture.org/2011/11/%d9%86%d9%82%d8%a7%d8%b7-%d8%b9%d9%84%d9%89-%d8%a7%d9%84%d8%ad%d8%b1%d9%88%d9%81-%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9%d8%8c-%d9%88%d8%a7%d9%82%d8%b9-%d8%a7%d9%84%d8%ae%d8%b7-%d8%a7%d9%84%d8%b9/kelk/"><img class="size-medium wp-image-451" title="kelk" src="http://www.linuxfuture.org/wp-content/uploads/2011/11/Kelk-300x183.png" alt="الخط الفارسي نتاج جهد بشري وحاسوبي" width="300" height="183" /></a><p class="wp-caption-text">الخط الفارسي نتاج جهد بشري وحاسوبي</p></div>
<p>بعبارة موجزة، بقدر ما تتسع دائرة متطلبات الخط من مرونة وخيال، بقدر ما تضيق الخطوط الحاسوبية عن استيعابها والإحاطة بكل متطلباتها.</p>
<p>هذا فيما يتعلق بميدان الطباعة، أما&#8230;</p>
<h2>على شاشة الحاسوب</h2>
<p>فعلى الرغم من أن الحاسوب لم يبد حتى الآن قدرة على احتواء الخط العربي بكل ثرائه وغناه، إلا أن العكس يبدو صحيحاً، إذ يبدو أن تقنيات الحوسبة ومتطلباتها ستشكل دافعاً ملهماً لإثراء الخط العربي بخطوط جديدة.</p>
<p>فقد كان الخط Tahoma على سبيل المثال، منذ فجر ظهوره مع مجموعة تطبيقات أوفيس 95 من مايكروسوفت، وليد الحاجة إلى خط عالمي جديد واضح المعالم على شاشة الحاسوب، يحقق مستوىً من التناغم والانسجام بين أطقم الأحرف لمختلف اللغات فيه، على تباينها الشديد أصلاً.</p>
<p>وتسعى عائلة خطوط أوبونتو Ubuntu Font Family لسد هذه الثغرة في عالم لينكس حالياً.</p>
<p>وظيفياً، يمكن تقسيم خطوط الحاسوب عموماً إلى:</p>
<ol>
<li>خطوط لبيئة سطر الأوامر</li>
<li>خطوط للواجهة الرسومية</li>
<li>خطوط ثابتة العرض Monospace (للنصوص البرمجية)</li>
<li>خطوط طباعية</li>
</ol>
<h3>خطوط بيئة سطر الأوامر</h3>
<p>الخط المستخدم في بيئة الأوامر في مختلف أنظمة التشغيل هو عادة خط البيوس نفسه، إلا أن أنظمة التشغيل الحالية دأبت على استبداله بخط ثابت العرض من خطوطها، وهو ما أعتقد أنه يفسد بيئة الأوامر وسحرها الخاص!</p>
<p>أما إقدام أنظمة التشغيل على هذه الخطوة فمرده فيما أحسب إلى افتقار خط البيوس عادة إلى المحارف غير اللاتينية، إلا أن فكرة غزو نواة لينكس للبيوس التي يعد بها مشروع CoreBoot ـ (LinuxBIOS سابقاً) قد تكون كفيلةً بحل هذه المشكلة مستقبلاً.</p>
<h3>خطوط الواجهة الرسومية <span lang="en-us">GUI</span>:</h3>
<p>هي الأكثر أهمية نظراً لارتباطها الوثيق والدائم بنشاط المستخدم اليومي على الحاسوب.</p>
<p>وقد كان لإحلال خط Tahoma محل خط MS Sans Serif في إصدارات ويندوز 2000/XP دور ملحوظ في صقل واجهة الاستخدام العربية في بيئة ويندوز مقارنة بإصداراته السابقة.</p>
<p>في حين لا تزال بيئة سطح المكتب في لينكس مفتقرة لخط عربي من هذا القبيل يوازي خط Tahoma في ويندوز، إلا أن شركة كانونيكال Canonical التي تقف وراء إصدارة أوبونتو الشهيرة تعكف الآن على تطوير الحرف العربي لعائلة خطوطها Ubuntu Font Family التي صممت خصيصاً لهذا الغرض.</p>
<p>كل ما تقدم ينطبق على خطوط صفحات الوب أيضاً، خاصة إذا علمت أن تقنية CSS المستخدمة في تنسيق صفحات وب تسمح بتخصيص خط معين لكل وسط من أوساط النشر على حدة، فخط للشاشة وآخر للطباعة وثالث لجهاز العرض projector&#8230; الخ.</p>
<h3>خطوط ثابتة العرض Monospace</h3>
<p>هي الخطوط المستخدمة في كتابة النصوص البرمجية، والمحبذة أيضاً في محررات النصوص البسيطة. تتخذ كافة الأحرف في هذا الخط عرضاً ثابتاً موحداً،</p>
<p>يمثله في بيئة ويندوز Courier New، وفي بيئة لينكس كل من Ubuntu Mono الذي تعكف شركة Canonical على تطوير أحرفه العربية حالياً كما أسلفنا و Libration Mono وهو من عائلة خطوط Liberation من إنتاج RedHat والتي لا يبدو أنها معنية حالياً بتطوير طقم المحارف العربية فيه.</p>
<h3>خطوط طباعية</h3>
<p>وهي الخطوط الأكثر وفرةً وتداولاً، ولا تعاني أنظمة التشغيل نقصاً منها عربياً أو لاتينياً. يعد هذا النمط من الخطوط غنياً نسبياً بالزخارف والزوائد Serifs والمنحنيات، ولا يمكن تكوين معالمه بنقاط محددة وبسيطة على الشاشة، الأمر الذي يتطلب إخضاعه افتراضياً لخاصية التنعيم Smoothing.</p>
<p>عربياً، تتوزع الخطوط الطباعية المقبولة بين النسخ والكوفي كما أسلفنا، إضافة لبعض الخطوط المستحدثة. فيما يلي قائمة بأهم تلك الخطوط في عالم لينكس مقارنة بالخطوط العربية المعهودة في ويندوز.</p>
<div id="attachment_452" class="wp-caption aligncenter" style="width: 310px"><a rel="attachment wp-att-452" href="http://www.linuxfuture.org/2011/11/%d9%86%d9%82%d8%a7%d8%b7-%d8%b9%d9%84%d9%89-%d8%a7%d9%84%d8%ad%d8%b1%d9%88%d9%81-%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9%d8%8c-%d9%88%d8%a7%d9%82%d8%b9-%d8%a7%d9%84%d8%ae%d8%b7-%d8%a7%d9%84%d8%b9/arabic-fonts/"><img class="size-medium wp-image-452" title="Arabic-Fonts" src="http://www.linuxfuture.org/wp-content/uploads/2011/11/Arabic-Fonts-300x170.png" alt="الخطوط العربية في لينكس" width="300" height="170" /></a><p class="wp-caption-text">الخطوط العربية في لينكس</p></div>
<p>إلا أن فئة النسخ التقليدي في بيئة لينكس، ممثلة بخط KacstBook من مدينة الملك عبد العزيز للعلوم والتقنية، وشهرزاد من المعهد الصيفي للغويات SIL، تفتقر، مقارنة بخط Traditional Arabic من مايكروسوفت، إلى التراكبات المدعومة من قبل Unicode.</p>
<div id="attachment_453" class="wp-caption aligncenter" style="width: 198px"><a rel="attachment wp-att-453" href="http://www.linuxfuture.org/2011/11/%d9%86%d9%82%d8%a7%d8%b7-%d8%b9%d9%84%d9%89-%d8%a7%d9%84%d8%ad%d8%b1%d9%88%d9%81-%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9%d8%8c-%d9%88%d8%a7%d9%82%d8%b9-%d8%a7%d9%84%d8%ae%d8%b7-%d8%a7%d9%84%d8%b9/arabic-combination/"><img class="size-medium wp-image-453" title="Arabic-Combination" src="http://www.linuxfuture.org/wp-content/uploads/2011/11/Arabic-Combination-188x300.png" alt="تراكبات خط النسخ" width="188" height="300" /></a><p class="wp-caption-text">تراكبات خط النسخ</p></div>
<p>هذه القراءة الأولية لتجربة الخط العربي على الحاسوب، تضعني أمام صورة مفادها، أنه وعلى الرغم من أن الإفراط في استخدام وتوظيف الخطوط الحاسوبية وحلولها البسيطة والمتقدمة حالياً يوحي بأن الخط العربي بات واحداً من ضحايا التقنية المعاصرة، إلا أن غياب الإحساس بجماليات الخط العربي والافتقار إلى ذوق سليم أولاً، وتغليب الخيارات الاقتصادية ذات النتائج المتواضعة على اللجوء ليد خطاط ماهر وهو الخيار الأكثر تكلفة والأفضل جودة ثانياً، هما العاملان الحقيقيان اللذان يقفا وراء الحالة المؤسفة التي انتهى إليها الخط العربي هذه الأيام.</p>
<p>فالعمل الفني ليس نتاج عملية حسابية أو صناعية بسيطة، بمدخلات ومخرجات مادية صماء، يسري عليها كل ما يسري على صناعة المنتجات المادية، بل هي نتاج خيال بشري خصب، وحس إنساني مرهف، وما ينبغي للعاملين في هذا الميدان التضحية بمبدأ الاحتكام إلى معايير الفن والذوق السليم، والانجراف أمام مغريات الكفاية الإنتاجية العالية التي تعد بها الوسائل التقنية، والتعويل عليها بهذه البساطة لإخراج مواد فنية وإعلانية تفتقر في نهاية المطاف للكثير من معالم الإبداع الإنساني الحر.</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.linuxfuture.org/2011/11/%d9%86%d9%82%d8%a7%d8%b7-%d8%b9%d9%84%d9%89-%d8%a7%d9%84%d8%ad%d8%b1%d9%88%d9%81-%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9%d8%8c-%d9%88%d8%a7%d9%82%d8%b9-%d8%a7%d9%84%d8%ae%d8%b7-%d8%a7%d9%84%d8%b9/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Ideas for HTML5</title>
		<link>http://www.linuxfuture.org/2011/11/ideas-for-html5/</link>
		<comments>http://www.linuxfuture.org/2011/11/ideas-for-html5/#comments</comments>
		<pubDate>Mon, 14 Nov 2011 17:46:19 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[Web Applications]]></category>

		<guid isPermaLink="false">http://www.linuxfuture.org/?p=445</guid>
		<description><![CDATA[These ideas are outcome of my experience in developing my project RichStyle. A Unified Label Attribute Think of using label="" as a unified naming attribute; as an alternative to all naming tags and attribute: &#60;caption&#62; , &#60;label&#62;, &#60;legend&#62;, alt="", for="", title="", summary="". Tile text (the mouseover-text) could be displayed using a CSS rule like this: [...]]]></description>
			<content:encoded><![CDATA[<p>
These ideas are outcome of my experience in developing my project <a href="http://richstyle.org">RichStyle</a>.
</p>
<h3>A Unified Label Attribute</h3>
<p>
Think of using <code>label=""</code> as a unified naming attribute; as an alternative to all naming tags and attribute:<br />
<br /><code>&lt;caption&gt;</code> , <code>&lt;label&gt;</code>, <code>&lt;legend&gt;</code>, <code>alt=""</code>, <code>for=""</code>, <code>title=""</code>, <code>summary=""</code>.
</p>
<p>
Tile text (the mouseover-text) could be displayed using a CSS rule like this:
</p>
<pre>{ title: attr(label) | attr(accesskey) | attr(label) attr(accesskey) | none }
</pre>
<p>
The standard way for label presentation is to use <code>:before</code> and <code>:after</code> pseudo elements.
</p>
<h3>Command Representation</h3>
<p>
<code>&lt;command&gt;</code> should have an <code>href=""</code> attribute (link attribute) as an optional attribute, since a command could be simply a link.
</p>
<p>
<code>icon=""</code> attribute should be deprecated in favor of CSS <code>icon</code> attribute, which , in turn, should have an additional value called glyph(), e.g.:
</p>
<pre>command.go_up {icon: glyph(↑)}
</pre>
<p>
And just like <code>&lt;input&gt;</code>, <code>command</code> should accept <code>text</code> as a type beside &#8220;command&#8221;, &#8220;checkbox&#8221;, and &#8220;radio&#8221;:
</p>
<pre>&lt;command type="text"&gt;</pre>
<p>
Think of &#8220;search&#8221; and &#8220;zoom&#8221; fields in a toolbar.
</p>
<h3>Time Representation</h3>
<p>
Time, as a tag, should be used as a part of a context in an article or so on, the purpose here is to give the developer enough flexibility in time presentation (time-zone, time format) using CSS.
</p>
<p>
For articles&#8217; time-stamp, and any other embedded content like<br />
audio, video, or image, there should be two attributes: published, and<br />
modified (last-modification date).
</p>
<pre>time,
article:time {
	time-format: dd-mm-yyyy;
	time-zone: +5;
}</pre>
<h3>A &#8220;Window&#8221; Tag</h3>
<p>
Unlike Window object used in JavaScript, such a tag might be easily maintained and customized using CSS like this:
</p>
<pre>window {
	position: fixed;
	left: 50%;
	top: 50%;
	buttons: close || maximize || minimize;
}</pre>
<h3>Standardizing jQuery</h3>
<p>jQuery is the most popular alternative to JavaScript, it&#8217;s a powerful &#8220;meta-language&#8221; tries to circumvent the raw-javascript limitations. I think this language should be standardized.
</p>
<p>
Isolating events from the the HTML code the way CSS does regarding presentation attributes should be enough reason for W3C to adopt it.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.linuxfuture.org/2011/11/ideas-for-html5/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RichStyle Software Process</title>
		<link>http://www.linuxfuture.org/2011/10/richstyle-software-process/</link>
		<comments>http://www.linuxfuture.org/2011/10/richstyle-software-process/#comments</comments>
		<pubDate>Mon, 03 Oct 2011 18:09:45 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[RichStyle]]></category>
		<category><![CDATA[Web Applications]]></category>
		<category><![CDATA[ASP]]></category>
		<category><![CDATA[CMMI]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[DEB]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[Debian Package]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[ISO]]></category>
		<category><![CDATA[PAD file]]></category>
		<category><![CDATA[Software Engineering]]></category>
		<category><![CDATA[Software Process]]></category>
		<category><![CDATA[UML]]></category>
		<category><![CDATA[XHTML]]></category>
		<category><![CDATA[XML]]></category>

		<guid isPermaLink="false">http://www.linuxfuture.org/?p=385</guid>
		<description><![CDATA[This is a revision of a paper submitted on 27-06-2010 to the Arab Academy for Banking and Financial Sciences. Abstract According to ISO, in order to produce a high quality product, organization needs a high quality producing process, which means a well defined and organized process. Generally speaking, this is true in variant industries, but [...]]]></description>
			<content:encoded><![CDATA[<p>This is a revision of a paper submitted on 27-06-2010 to the Arab Academy for Banking and Financial Sciences.</p>
<h1>Abstract</h1>
<p>According to ISO, in order to produce a high quality product, organization needs a high quality producing process, which means a well defined and organized process. Generally speaking, this is true in variant industries, but not in software industry, since production process in software industry is a <em>creative process</em>, not an <em>industrial process</em>, so that one can&#8217;t imagine that there are a list of input items from one side, that could produce a software product out of the other one, automatically, without any human factor involvement.</p>
<p>Software Engineering tries to convert software process from a creative process to an industrial process.</p>
<p>As a solution, an ISO-alternative standard emerged for software industry, called CMM, developed by Carnegie Mellon Software Engineering Institute (SEI). Later on it has developed and expanded its scope and cover other industries, it is called now CMMI.</p>
<p>Since 1987, when CMM emerged, CMM/CMMI has been always focusing on <em>documentation</em>. The reason is that organization doesn’t have an automated process, so, all it can do is to <em>organize</em> process using documents.</p>
<p>In fact, as one can see, CMM emerged before web era; the era in which database systems weren’t mature enough and used widely like nowadays, client/server architecture wasn’t common in business world. That&#8217;s why CMM/CMMI was always focusing on <em>documents</em>.</p>
<p>The objective of this paper is to <em>build a software process using database</em>, rather than <em>document a software process using documents</em>.<span id="more-385"></span></p>
<h2>Keywords</h2>
<p>Software Engineering, Software Process, ISO, CMMI, UML, XML, HTML, XHTML, CSS, RichStyle, PAD file, ASP, Debian, Debian Package, DEB.</p>
<h2>Methodology</h2>
<p>Modeling configuration management process area in a database model using UML.</p>
<p>The Association of Software Professionals (ASP) provides a standard XML-based document called PAD file, the Portable Application Description. ASP represents the best practice in software industry regarding software publishing.</p>
<p>I’ll compare this standard to Debian control file, the file stored in the Debian package file (DEB), and stores in turn the package&#8217;s meta-data.</p>
<p>Debian package system represents also the best practice in open source community regarding software publishing, and Debian and Debian-based Linux distributions are the most popular distributions in open source community according to DistroWatch.com.</p>
<h1>Introduction</h1>
<p>The following table illustrates the main CMMI concepts, including <em>Process Areas</em>, <em>Capability Levels</em> and <em>Maturity Levels</em>, and the relationship between each other.</p>
<div style="overflow-x: auto; padding: 2px;">
<table>
<caption>CMMI Concepts. Marked cells represent the actual possible levels. [ ------ Time direction ------» ]</caption>
<tbody>
<tr>
<td></td>
<td></td>
<th colspan="6">Capability Levels&nbsp;</p>
<p>Are the objectives of the <em>given</em> Process Area:</th>
</tr>
<tr>
<th colspan="2">Process Area</th>
<th>0- Incomplete</th>
<th>1- Performed</th>
<th>2- Managed</th>
<th>3- Defined</th>
<th>4- Quantitatively Managed</th>
<th>5- Optimized</th>
</tr>
</tbody>
<tbody>
<tr>
<td rowspan="5">Process Management</td>
<td>Organizational Process Definition + IPPD</td>
<td></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Organizational Process Focus</td>
<td></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Organizational Training</td>
<td></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Organizational Process Performance</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Organizational Innovation and Deployment</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
</tr>
</tbody>
<tbody>
<tr>
<td rowspan="6">Project Management</td>
<td>Project Planning</td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Project Monitoring and Control</td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Supplier Agreement Management</td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Integrated Project Management +IPPD</td>
<td></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Risk Management</td>
<td></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Quantitative Project Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
</tbody>
<tbody>
<tr>
<td rowspan="6">Engineering</td>
<td>Requirements Management</td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Technical Solution</td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Product Integration</td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Verification</td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Validation</td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Requirements Development</td>
<td></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
</tbody>
<tbody>
<tr>
<td rowspan="5">Support</td>
<td><strong>Configuration Management</strong></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Process and Product Quality Assurance</td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Measurement and Analysis</td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Decision Analysis and Resolution</td>
<td></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
<tr>
<td>Causal Analysis and Resolution</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
</tr>
</tbody>
<tbody>
<tr>
<td></td>
<td></td>
<td></td>
<th colspan="5">Maturity Levels&nbsp;</p>
<p>Are the objectives of the <em>whole</em> Process Areas:</th>
</tr>
</tbody>
<tbody>
<tr>
<td></td>
<td></td>
<td></td>
<th>1- Initial</th>
<th>2- Managed</th>
<th>3- Defined</th>
<th>4- Quantitatively Managed</th>
<th>5- Optimized</th>
</tr>
</tbody>
<tbody>
<tr>
<td></td>
<td></td>
<td></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
<td class="activeLevel"></td>
</tr>
</tbody>
</table>
</div>
<h1>A Comparison between PAD file and Debian control file</h1>
<p>Those two standard files represent the best practice in commercial software industry and open source community, regarding software publishing.</p>
<div id="attachment_424" class="wp-caption alignnone" style="width: 310px"><a rel="attachment wp-att-424" href="http://www.linuxfuture.org/2011/10/richstyle-software-process/pad/"><img class="size-medium wp-image-424" title="PAD file structure" src="http://www.linuxfuture.org/wp-content/uploads/2011/10/PAD-300x202.png" alt="PAD file structure" width="300" height="202" /></a><p class="wp-caption-text">PAD file structure</p></div>
<div id="attachment_425" class="wp-caption alignnone" style="width: 172px"><a rel="attachment wp-att-425" href="http://www.linuxfuture.org/2011/10/richstyle-software-process/debian-control/"><img class="size-full wp-image-425" title="Debian-Control" src="http://www.linuxfuture.org/wp-content/uploads/2011/10/Debian-Control.png" alt=" Debian Control file structure" width="162" height="290" /></a><p class="wp-caption-text"> Debian Control file structure</p></div>
<p>Although The PAD file is richer than<br />
the Debian Control file, the Debian Control file is used for<br />
functional purposes, rather than providing meta-data about the<br />
software package. It&#8217;s used by the dependency-check function to ensure<br />
the compatibility of the package with the target platform.</p>
<p>&nbsp;</p>
<table class="comparisonTable">
<caption>PAD file vs. Debian control file.</caption>
<tbody>
<tr>
<th colspan="2">PAD File</th>
<th>Debian Control File</th>
<th>Suggested Modifications</th>
</tr>
<tr>
<td rowspan="6">Company Info</td>
<td>Company_Name</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Address_1</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Address_2</td>
<td></td>
<td></td>
</tr>
<tr>
<td>City_Town</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Country</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Company_WebSite_URL</td>
<td></td>
<td></td>
</tr>
<tr>
<td rowspan="6">Contact Info</td>
<td>Author_First_Name</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Author_Last_Name</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Author_Email</td>
<td>Original-Maintainer</td>
<td></td>
</tr>
<tr>
<td>Contact_First_Name</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Contact_Last_Name</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Contact_Email</td>
<td>Maintainer</td>
<td></td>
</tr>
<tr>
<td rowspan="7">Support Info</td>
<td>Sales_Email</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Support_Email</td>
<td></td>
<td></td>
</tr>
<tr>
<td>General_Email</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Sales_Phone</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Support_Phone</td>
<td></td>
<td></td>
</tr>
<tr>
<td>General_Phone</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Fax_Phone</td>
<td></td>
<td></td>
</tr>
<tr>
<td rowspan="16">Program Info</td>
<td>Program_Name</td>
<td>Package</td>
<td></td>
</tr>
<tr>
<td>Program_Version</td>
<td>Version</td>
<td></td>
</tr>
<tr>
<td>Program_Release_Month</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Program_Release_Day</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Program_Release_Year</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Program_Type</td>
<td>Section</td>
<td></td>
</tr>
<tr>
<td>Program_Release_Status</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Program_Install_Support</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Program_OS_Support</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Program_Language</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Program_Change_Info</td>
<td></td>
<td>Mods, Fixes, and FAQs</td>
</tr>
<tr>
<td>Program_Specific_Category</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Program_Category_Class</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Program_System_Requirements</td>
<td>Depends</td>
<td>Software</td>
</tr>
<tr>
<td></td>
<td>Architecture</td>
<td></td>
</tr>
<tr>
<td></td>
<td>Installed-Size</td>
<td>Free_Space, RAM</td>
</tr>
<tr>
<td rowspan="3">File Info</td>
<td>File_Size_Bytes</td>
<td></td>
<td></td>
</tr>
<tr>
<td>File_Size_K</td>
<td></td>
<td></td>
</tr>
<tr>
<td>File_Size_MB</td>
<td></td>
<td></td>
</tr>
<tr>
<td rowspan="7">Expire Info</td>
<td>Has_Expire_Info</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Expire_Count</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Expire_Based_On</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Expire_Other_Info</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Expire_Month</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Expire_Day</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Expire_Year</td>
<td></td>
<td></td>
</tr>
<tr>
<td rowspan="6">Program Description</td>
<td>Keywords</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Char_Desc_45</td>
<td>Description</td>
<td></td>
</tr>
<tr>
<td>Char_Desc_80</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Char_Desc_250</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Char_Desc_450</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Char_Desc_2000</td>
<td></td>
<td></td>
</tr>
<tr>
<td rowspan="2">Permissions</td>
<td>Distribution_Permissions</td>
<td></td>
<td></td>
</tr>
<tr>
<td>EULA</td>
<td></td>
<td></td>
</tr>
<tr>
<td rowspan="5">Application_URLs</td>
<td>Application_Info_URL</td>
<td>Homepage</td>
<td></td>
</tr>
<tr>
<td>Application_Order_URL</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Application_Screenshot_URL</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Application_Icon_URL</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Application_XML_File_URL</td>
<td></td>
<td></td>
</tr>
<tr>
<td rowspan="4">Download_URLs</td>
<td>Primary_Download_URL</td>
<td>Section</td>
<td></td>
</tr>
<tr>
<td>Secondary_Download_URL</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Additional_Download_URL_1</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Additional_Download_URL_2</td>
<td></td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td>Priority</td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td>Recommends</td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td>Suggests</td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td>Conflicts</td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td>Replaces</td>
<td></td>
</tr>
<tr>
<td></td>
<td></td>
<td>Provides</td>
<td></td>
</tr>
</tbody>
</table>
<h1>Use-Case Diagram</h1>
<h2>SDLC Diagram</h2>
<p>This model illustrates the main activities that is performed by the variant project stakeholders.</p>
<p>The dependency arrows between use-cases show the entire software development life cycle (SDLC).</p>
<p>Notice that the sequence direction of the life cycle is the opposite of dependency arrows direction.</p>
<p>Actors represent stakeholders.</p>
<div id="attachment_426" class="wp-caption alignnone" style="width: 272px"><a rel="attachment wp-att-426" href="http://www.linuxfuture.org/2011/10/richstyle-software-process/sdlc-use-cases/"><img class="size-medium wp-image-426" title="SDLC-Use-Cases" src="http://www.linuxfuture.org/wp-content/uploads/2011/10/SDLC-Use-Cases-262x300.png" alt="Use-Case Diagram of SDLC" width="262" height="300" /></a><p class="wp-caption-text">Figure 1 – Use-Case Diagram of SDLC</p></div>
<h1>Actor Specification</h1>
<h2>Analyst</h2>
<p>Analyst is responsible for refining requests and making designs.</p>
<h2>Customer</h2>
<p>A subset of stakeholders  (individual, project, or organization), responsible for accepting the product  or for authorizing payment. The customer is usually external to the project, but not necessarily external to the organization (SEI, 2006).</p>
<p>Customer here is supposed to be the end-user himself or herself.</p>
<h2>Developer</h2>
<p>Developer is responsible for developing code according to the tasks that are generated by the Project Manager.</p>
<p>Also he or she has to review a code developed by another developer along with a third developer.</p>
<h2>Project Manager</h2>
<p>The person responsible for planning, directing, controlling, structuring, and motivating the project. The project manager is responsible for satisfying the customer (SEI, 2006).</p>
<p>Project Manager is responsible for refining designs, and generating tasks, and assigning them to developers, and release a new build of the software product.</p>
<h2>Support</h2>
<p>The staff that is responsible for communication with costumer.</p>
<h2>Tester</h2>
<p>Tester is responsible for unit and acceptance tests.</p>
<h1>Use-Case Specification</h1>
<h2>Buy a Release</h2>
<p>This activity is usually performed by the customer, but particularly, it’s allowed to any stakeholder to perform this activity.</p>
<h2>Design</h2>
<p>This activity is the mission of the analyst.</p>
<h2>Develop</h2>
<p>This activity is the mission of the developer.</p>
<h2>Download a Release</h2>
<p>This activity is usually performed by the customer, but particularly, it’s allowed to any stakeholder to perform this activity.</p>
<h2>Filter Customer Requests</h2>
<p>This activity is the mission of the support staff. This means that support staff can’t filter requests came from any project member (internal stakeholder).</p>
<h2>Generate Tasks</h2>
<p>This activity is one of the project manager’s missions.</p>
<h2>Peer Review</h2>
<p>This activity is the mission of the developer. Two developers should review a code of a third developer.</p>
<h2>Refine Designs</h2>
<p>This activity is one of the project manager missions.</p>
<h2>Refine Requests</h2>
<p>This activity is the mission of the analyst.</p>
<h2>Release</h2>
<p>This activity is one of the project manager missions.</p>
<h2>Request a Change</h2>
<p>This activity is usually performed by the customer, but particularly, it’s allowed to any stakeholder to perform this activity.</p>
<h2>Test</h2>
<p>This activity is the mission of the tester.</p>
<p>Accepting test should be done before unit test.</p>
<h1>Class Diagram</h1>
<h2>Database Diagram</h2>
<p>This diagram represents the data structure required for the whole software development process.</p>
<p>It’s based on an improved version of PAD file, supplied and associated with ‘back-end’ classes used by the organization.</p>
<div id="attachment_427" class="wp-caption alignnone" style="width: 310px"><a rel="attachment wp-att-427" href="http://www.linuxfuture.org/2011/10/richstyle-software-process/database-classes/"><img class="size-medium wp-image-427" title="Database-Classes" src="http://www.linuxfuture.org/wp-content/uploads/2011/10/Database-Classes-300x300.png" alt="Class Diagram of Database" width="300" height="300" /></a><p class="wp-caption-text">Figure 2 – Class Diagram of Database</p></div>
<h2>User Interface Diagram</h2>
<p>It illustrates the structure of the web interface that web developer should be committed to, in order to guarantee the compatibility with RichStyle© library.</p>
<div id="attachment_428" class="wp-caption alignnone" style="width: 310px"><a rel="attachment wp-att-428" href="http://www.linuxfuture.org/2011/10/richstyle-software-process/user-interface-classes/"><img class="size-medium wp-image-428" title="User-Interface-Classes" src="http://www.linuxfuture.org/wp-content/uploads/2011/10/User-Interface-Classes-300x268.png" alt="Class Diagram of User Interface" width="300" height="268" /></a><p class="wp-caption-text">Figure 3 – Class Diagram of User Interface</p></div>
<h1>Component Diagram</h1>
<h2>User Interface Diagram</h2>
<p>This model illustrates the set of software libraries that are used in RichStyle© package.</p>
<p>Tango Icons package offers a standard structure for icon naming, i.e. it offers a standard interface to communicate with other software components.</p>
<div id="attachment_429" class="wp-caption alignnone" style="width: 310px"><a rel="attachment wp-att-429" href="http://www.linuxfuture.org/2011/10/richstyle-software-process/user-interface-components/"><img class="size-medium wp-image-429" title="User-Interface-Components" src="http://www.linuxfuture.org/wp-content/uploads/2011/10/User-Interface-Components-300x187.png" alt="Component Diagram of User Interface" width="300" height="187" /></a><p class="wp-caption-text">Figure 4 – Component Diagram of User Interface</p></div>
<h1>Component Specification</h1>
<h2>RichStyle.js.php</h2>
<p>A PHP-powered JavaScript file, stores the events’ functions of the entire RichStyle framework. It also checks the browser compatibility, and returns a list of the compatible browsers if false.</p>
<h2>Richstyle PHP Templates</h2>
<p>It typically includes: header.php, footer.php,/data/data.php, /data/footer.php, /data/advert.php.</p>
<h2>RichStyle CSSs</h2>
<p>It’s a set of CSS files designed for web pages and HTML  documents that might include lists, tables, images, codes, preformatted texts, notes, and quotes, in content area.</p>
<p>Actually, web page usually differs from document in two main aspects:</p>
<ul>
<li>It contains user interface elements, like banner, footer, and menus.</li>
<li>Content area is usually dealt as either poor plain text, or messy rich text, making it misses balance between richness and consistency.</li>
</ul>
<p>CSS specifications allow web developer to build more than one kind of layout template for a web page, depending on the used media, i.e. one for the screen, and another one for printing media (paper).</p>
<p>As an implantation solution, RichStyle© package offers:</p>
<ul>
<li>Content area maintain the balance between richness and consistency.</li>
<li>No classes as much as possible, HTML tags should be enough.</li>
<li>No attributes as much as possible, unless they were representing content, not format instruction, ie. the source of an image, or the destination of a link.</li>
</ul>
<h2>RichStyle HTML Template</h2>
<p>A template file called <q>Web-Document.web</q> added to the Nautilus file manager, which is an empty HTML5 file linked to the CSS files.</p>
<h2>Tango Icons</h2>
<p>A cross-platform icon theme follows the FreeDesktop.org guidelines, such as the Standard Icon Naming Specification, and the Standard Icon Theming Specification.</p>
<h2>jQuery.js</h2>
<p>A JavaScript library designed to simplify the client-side scripting of HTML.</p>
<p>It simplifies the way developer handles events, Ajax interactions, and perform animations.</p>
<h2>rsBobb’s File List System</h2>
<p>It’s a PHP library used to generate an HTML list of files and subdirectories located in a specific directory.</p>
<h2>rsTinyMCE</h2>
<p>It’s a restricted version of TinyMCE, a web-based WYSIWYG HTML editor. It’s customized here to prevent user to insert messy format instructions, and deviate the common look and feel of the web page. i.e. user can’t change fonts or colors in text area.</p>
<p>Technically, It converts HTML text-area field to an editor instance.</p>
<h2>rsjQuery Date Picker</h2>
<p>It’s a JavaScript library used to generate a client-side calendar. It’s based on jQuery.</p>
<h1>Deployment Diagram</h1>
<h2>SDLC Diagram</h2>
<p>It’s a simple client-server architecture. This means that all the project stockholders will deal with the same user interface, but with variant permissions.</p>
<div id="attachment_430" class="wp-caption alignnone" style="width: 310px"><a rel="attachment wp-att-430" href="http://www.linuxfuture.org/2011/10/richstyle-software-process/sdlc-deployment/"><img class="size-medium wp-image-430" title="SDLC-Deployment" src="http://www.linuxfuture.org/wp-content/uploads/2011/10/SDLC-Deployment-300x254.png" alt="Deployment Diagram of SDLC" width="300" height="254" /></a><p class="wp-caption-text">Figure 5 – Deployment Diagram of SDLC</p></div>
<h1>Node Specification</h1>
<h2>Client PC</h2>
<p>RichStyle library requires one of the following web browsers:</p>
<ul>
<li>Chrome 1.0.154.65</li>
<li>Chromium 1.0.154.65</li>
<li>Epiphany 2.30.2</li>
<li>Firefox 3.6.12</li>
<li>Galeon 2.0.6</li>
<li>Konqueror 4.4</li>
<li>Midori 0.2.2</li>
<li>Opera 10.10</li>
<li>Safari 4.0.3</li>
</ul>
<p>Regardless the used platform.</p>
<h2>Database Server</h2>
<p>Since the components are based on PHP, it’s recommended to use LAMP platform (Linux/Apache/MySQL/PHP), although PHP, MySQL, and Apache can be used under Windows platform.</p>
<h2>Web Server</h2>
<p>Since the components are based on PHP, it’s recommended to use LAMP platform (Linux/Apache/MySQL/PHP), although PHP, MySQL, and Apache can be used under Windows platform.</p>
<h1>Glossary</h1>
<dl>
<dt id="Appraisal">Appraisal</dt>
<dd> An examination of one or more processes by a trained team of professionals using an appraisal reference model as the basis for determining, at a minimum, strengths and weaknesses. </dd>
<dt id="Capability_Level">Capability Level</dt>
<dd> Achievement of <a href="#Process_Improvement">process improvement</a> within an individual <a href="#Process_Area">process area</a>. A capability level is defined by the appropriate <a href="#Specific_Practice">specific</a> and <a href="#Generic_Practice">generic practices</a> for a process area. </dd>
<dt>CMM</dt>
<dd> A methodology for the development and improvement of an organization&#8217;s software development process. The model describes a five-stage evolutionary path of an increasingly organized process (Cadle &amp; Yeates, 2004). </dd>
<dt id="CMMI">CMMI</dt>
<dd> An integrated approach to process capability maturity modeling. It supports discrete and continuous maturity modeling and integrates systems and software engineering process maturity models (Sommarville, 2007). </dd>
<dd> A <a href="#Process_Improvement">process improvement</a> approach that helps <a href="#Organization">organizations</a> improve their performance. CMMI can be used to guide process improvement across a <a href="#Project">project</a>, a division, or an entire organization (Wikipedia.org, 2010).&nbsp;</p>
<p>According to the Software Engineering Institute (SEI, 2008), CMMI helps <q>integrate traditionally separate organizational functions, set process improvement goals and priorities, provide guidance for quality processes, and provide a point of reference for <a href="#Appraisal">appraising</a> current processes.</q></p>
</dd>
<dt id="CMMI_Framework">CMMI Framework</dt>
<dd> The basic structure that organizes <a href="#CMMI_Model_Component">CMMI components</a>, including common elements of the current <a href="#CMMI_Model">CMMI models</a> as well as rules and methods for generating models, <a href="#Appraisal">appraisal</a> methods (including associated artifacts), and training materials. The framework enables new <a href="#Discipline">disciplines</a> to be added to CMMI so that the new disciplines will integrate with the existing ones. </dd>
<dt id="CMMI_Model">CMMI Model</dt>
<dd> One from the entire collection of possible models that can be generated from the <a href="#CMMI_Framework">CMMI Framework</a>. Since the CMMI Framework can generate different models based on the needs of the organization using it, there are multiple CMMI models. </dd>
<dt id="CMMI_Model_Component">CMMI Model Component</dt>
<dd> Any of the main architectural elements that compose a <a href="#CMMI_Model">CMMI model</a>. Some of the main elements of a CMMI model include:&nbsp;</p>
<ul>
<li><a href="#Process_Area">Process Areas</a></li>
<li>and</li>
</ul>
<table class="fixedTable">
<tbody>
<tr>
<th>CMMI Component</th>
<th>Expected</th>
<th>Required</th>
</tr>
<tr>
<th>Specific</th>
<td><a href="#Specific_Practice">Specific Practices</a></td>
<td><a href="#Specific_Goal">Specific Goals</a></td>
</tr>
<tr>
<th>Generic</th>
<td><a href="#Generic_Practice">Generic Practices</a></td>
<td><a href="#Generic_Goal">Generic Goals</a></td>
</tr>
<tr>
<th></th>
<td><a href="#Capability_Level">Capability Levels</a></td>
<td><a href="#Maturity_Level">Maturity Levels</a></td>
</tr>
</tbody>
</table>
</dd>
<dt id="CMMI_Product_Suite">CMMI Product Suite</dt>
<dd> The complete set of products developed around the CMMI concept. These products include:&nbsp;</p>
<ul>
<li>The <a href="#CMMI_Framework">framework</a> itself</li>
<li><a href="#CMMI_Model">Models</a></li>
<li><a href="#Appraisal">Appraisal</a> methods</li>
<li>Appraisal materials</li>
<li>and various types of <a href="#Training">training</a></li>
</ul>
</dd>
<dt id="Configuration_Management">Configuration Management</dt>
<dd> A <a href="#Discipline">discipline</a> applying technical and administrative direction and surveillance to:&nbsp;</p>
<ol>
<li>identify and document the functional and physical characteristics of a <a href="#Configuration_Item">configuration item</a>,</li>
<li>control changes to those characteristics,</li>
<li>record and report change processing and implementation status, and</li>
<li>verify compliance with specified requirements.</li>
</ol>
<p>See also:<br />
<q>configuration audit</q>,<br />
<q>configuration control</q>,<br />
<q>configuration identification</q>, and<br />
<q>configuration status accounting</q>.</p>
</dd>
<dd> The process of managing the changes to an evolving software product. It involves (Sommarville, 2007):&nbsp;</p>
<ol>
<li>configuration planning,</li>
<li>version management,</li>
<li>system building, and</li>
<li>change management.</li>
</ol>
</dd>
<dt id="Configuration_Item">Configuration Item</dt>
<dd> An aggregation of <a href="#Work_Product">work products</a> that is designated for <a href="#Configuration_Management">configuration management</a> and treated as a single entity in the configuration management process. </dd>
<dd> A machine-readable unit, such as a document or a source code file, that is subject to change and where the change has to be controlled by a <a href="#Configuration_Management">configuration management</a> system (Sommarville, 2007). </dd>
<dt id="Customer">Customer</dt>
<dd> A subset of <a href="#Stakeholder">stakeholders</a> (individual, project, or organization), responsible for accepting the <a href="#Product">product</a> or for authorizing payment. The customer is usually external to the <a href="#Project">project</a>, but not necessarily external to the <a href="#Organization"> organization</a>. </dd>
<dt id="Customer_Requirement">Customer Requirement</dt>
<dd> The result of eliciting, consolidating, and resolving conflicts among the needs, expectations, constraints, and interfaces of the <a href="#Product">product</a>&#8216;s relevant <a href="#Stakeholder">stakeholders</a> in a way that is acceptable to the <a href="#Customer">customer</a>. </dd>
<dt>CSS</dt>
<dd> A <a title="Style sheet language" href="http://en.wikipedia.org/wiki/Style_sheet_language">style sheet language</a> used to describe the <a title="Presentation semantics" href="http://en.wikipedia.org/wiki/Presentation_semantics"> presentation semantics</a> (that is, the look and formatting) of a document written in a <a title="Markup language" href="http://en.wikipedia.org/wiki/Markup_language">markup language</a>. Its most common application is to style web pages written in <a title="HTML" href="http://en.wikipedia.org/wiki/HTML">HTML</a> and <a title="XHTML" href="http://en.wikipedia.org/wiki/XHTML">XHTML</a>, but the language can also be applied to any kind of <a title="XML" href="http://en.wikipedia.org/wiki/XML">XML</a> document, including <a title="Scalable Vector Graphics" href="http://en.wikipedia.org/wiki/Scalable_Vector_Graphics">SVG</a> and <a title="XUL" href="http://en.wikipedia.org/wiki/XUL">XUL</a> (Wikipedia.org, 2010). </dd>
<dt id="Data">Data</dt>
<dd> Recorded information, regardless of the form or method of recording, including technical data, computer software documents, financial information, management information, representation of facts, numbers, or datum of any nature that can be communicated, stored, and processed. </dd>
<dt>Debian</dt>
<dd> Voluntary organization that produces distributions of Free Software operating systems, including Linux. Because it is a nonprofit organization run by passionate Free Software advocates, it is considered the most ethically sound of all Linux outfits. Many distributions, including Ubuntu, use Debian as the basis for their software because of its claimed reliability and relative simplicity (Thomas, 2007). </dd>
<dt>Dependency</dt>
<dd> A way of referring to system files that a program requires in order to run. If the dependencies are not present during program installation, a program might refuse to install (Thomas, 2007). </dd>
<dt id="Development">Development</dt>
<dd> Not only development activities but also maintenance activities may be included.<br />
<a href="#Project">Projects</a> that benefit from the best practices of CMMI can focus on development, maintenance, or both. </dd>
<dt id="Document">Document</dt>
<dd> A collection of data, regardless of the medium on which it is recorded, that generally has permanence and can be read by humans or machines. So, documents include both paper and electronic documents. </dd>
<dt id="Discipline">Discipline</dt>
<dd> The bodies of knowledge available to you when selecting a <a href="#CMMI_Model">CMMI model</a> (e.g., systems engineering). The CMMI Product Team envisions that other bodies of knowledge will be integrated into the <a href="#CMMI_Framework">CMMI Framework</a> in the future. </dd>
<dt id="Enterprise">Enterprise</dt>
<dd> The full composition of companies. Companies may consist of many <a href="#Organization">organizations</a> in many locations with different <a href="#Customer">customers</a>. </dd>
<dt id="Expected_CMMI_Components">Expected CMMI Components</dt>
<dd> <a href="#CMMI_Model_Component">CMMI components</a> that explain what may be done to satisfy a <a href="#Required_CMMI_Components">required CMMI component</a>. Model users can implement the expected components explicitly or implement equivalent alternative practices to these components.<br />
These are expected model components:&nbsp;</p>
<ul>
<li><a href="#Specific_Practice">Specific  Practices</a></li>
<li><a href="#Generic_Practice">Generic Practices</a></li>
</ul>
</dd>
<dt id="Generic_Goal">Generic Goal</dt>
<dd> A <a href="#Required_CMMI_Components">required CMMI component</a> that describes the characteristics that must be present to <a href="#Institutionalization">institutionalize</a> the processes that implement a <a href="#Process_Area">process area</a>. </dd>
<dt id="Generic_Practice">Generic Practice</dt>
<dd> An <a href="#Expected_CMMI_Components">expected model component</a> that is considered important in achieving the associated <a href="#Generic_Goal">generic goal</a>. The generic practices associated with a generic goal describe the activities that are expected to result in achievement of the generic goal and contribute to the <a href="#Institutionalization">Institutionalization</a> of the processes associated with a <a href="#Process_Area">process area</a>. </dd>
<dt id="Goal">Goal</dt>
<dd> A <a href="#Required_CMMI_Components">required CMMI component</a> that can be either:&nbsp;</p>
<ul>
<li>a <a href="#Generic_Goal">generic goal</a></li>
<li>or a <a href="#Specific_Goal">specific goal</a>.</li>
</ul>
<p>When you see the word goal in a <a href="#CMMI_Model">CMMI model</a>, it always refers to a <a href="#CMMI_Model_Component">model component</a> (e.g., generic goal and specific goal).</p>
<p>See also: <a href="#Objective">objective</a>.</p>
</dd>
<dt id="HTML">HTML</dt>
<dd> A publishing language; set by W3 Consortium; used by the World Wide Web (W3C, 2003). </dd>
<dt id="Institutionalization">Institutionalization</dt>
<dd> The ingrained way of doing business that an organization follows routinely as part of its corporate culture. </dd>
<dt id="Maturity_Level">Maturity Level</dt>
<dd> Degree of <a href="#Process_Improvement">process improvement</a> across a predefined set of <a href="#Process_Area">process areas</a> in which all <a href="#Goal">goals</a> in the set are attained. </dd>
<dt id="Objective">Objective</dt>
<dd> When used as a noun, the term objective replaces the word <a href="#Goal">goal</a> as used in its common everyday sense since the word goal is reserved for use when referring to the <a href="#CMMI_Model_Component">CMMI model components</a> called <a href="#Specific_Goal">specific goals</a> and <a href="#Generic_Goal">generic goals</a>. </dd>
<dt id="Organization">Organization</dt>
<dd> An administrative structure in which people collectively manage one or more <a href="#Project">projects</a> as a whole, and whose projects share a senior manager and operate under the same <a href="#Organizational_Policy">policies</a>. However, the word organization as used throughout <a href="#CMMI_Model">CMMI models</a> can also apply to one person who performs a function in a small organization that might be performed by a group of people in a large organization.&nbsp;</p>
<p>See also: <a href="#Enterprise">enterprise</a> and <q>organizational unit</q>.</p>
</dd>
<dt id="Organizational_Policy">Organizational Policy</dt>
<dd> A guiding principle typically established by senior management that is adopted by an <a href="#Organization">organization</a> to influence and determine decisions. </dd>
<dt>PAD</dt>
<dd> PAD is an XML-based description file for Portable Applications, aims to help authors provide product descriptions and specifications to online sources in a standard way, using a standard data format that will allow web masters and program librarians to automate program listings (pad.asp-software.org, 2010). </dd>
<dt id="Peer_Review">Peer Review</dt>
<dd> The review of <a href="#Work_Product">work products</a> performed by peers during <a href="#Development">development</a> of the <a href="#Work_Product"> work products</a> to identify defects for removal. The term peer review is used in the <a href="#CMMI_Product_Suite">CMMI Product Suite</a> instead of the term work product inspection. </dd>
<dt id="Process">Process</dt>
<dd> Activities that can be recognized as implementations of practices in a <a href="#CMMI_Model">CMMI model</a>. These activities can be mapped to one or more practices in CMMI <a href="#Process_Area">process areas</a> to allow a model to be useful for <a href="#Process_Improvement">process improvement</a> and process <a href="#Appraisal">appraisal</a>. </dd>
<dt id="Process_Area">Process Area</dt>
<dd> A cluster of related practices in an area that, when implemented collectively, satisfy a set of <a href="#Goal">goals</a> considered important for making improvement in that area. </dd>
<dt id="Process_Improvement">Process Improvement</dt>
<dd> A program of activities designed to improve the performance and maturity of the organization’s processes and the results of such a program. </dd>
<dd> The process of making change to a process with the aim of making that process more predictable or to improve the quality of its output.&nbsp;</p>
<p>For example, if your aim is to reduce the number of defects in the delivered software, you might improve the process by adding new validation activities (Sommarville, 2007).</p>
</dd>
<dt id="Product">Product</dt>
<dd> A <a href="#Work_Product">work product</a> that is intended for delivery to a <a href="#Customer">customer</a> or end user. The form of a product can vary in different contexts. </dd>
<dt id="Product_Component">Product Component</dt>
<dd> A <a href="#Work_Product">work product</a> that is a lower level component of the <a href="#Product">product</a>. Product components are integrated to produce the product. There may be multiple levels of product components. </dd>
<dt id="Project">Project</dt>
<dd> A managed set of interrelated resources which delivers one or more <a href="#Product">products</a> to a <a href="#Customer">customer</a> or end user. A project has a definite beginning (i.e., project startup) and typically operates according to a plan. Such a plan is frequently documented and specifies what is to be delivered or implemented, the resources and funds to be used, the work to be done, and a schedule for doing the work. A project can be composed of projects. </dd>
<dt id="Project_Manager">Project Manager</dt>
<dd> The person responsible for planning, directing, controlling, structuring, and motivating the project. The project manager is responsible for satisfying the <a href="#Customer">customer</a>. </dd>
<dd> The person given day-to-day control of a project under the delegated authority of the <a href="#Sponsor">sponsor</a> (Cadle &amp; Yeates, 2004). </dd>
<dt>Release</dt>
<div id="attachment_431" class="wp-caption alignright" style="width: 157px"><a rel="attachment wp-att-431" href="http://www.linuxfuture.org/2011/10/richstyle-software-process/release/"><img class="size-full wp-image-431" title="Release" src="http://www.linuxfuture.org/wp-content/uploads/2011/10/Release.png" alt="Release is a type of Version" width="147" height="181" /></a><p class="wp-caption-text">Release is a type of Version</p></div>
<dd> A version of a software system that is made available to system <a href="#Customer">customers</a> (Sommarville, 2007). </dd>
<dt id="Relevant_Stakeholder">Relevant Stakeholder</dt>
<dd> A <a href="#Stakeholder">stakeholder</a> that is identified for involvement in specified activities and is included in a plan. </dd>
<dt id="Required_CMMI_Components">Required CMMI Components</dt>
<dd> <a href="#CMMI_Model_Component">CMMI components</a> that are essential to achieving <a href="#Process_Improvement">process improvement</a> in a given <a href="#Process_Area">process area</a>. These components are used in <a href="#Appraisal">appraisals</a> to determine process capability. These are required model components:<br />
&nbsp;</p>
<ul>
<li><a href="#Specific_Goal">Specific Goals</a></li>
<li><a href="#Generic_Goal">Generic Goals</a></li>
</ul>
</dd>
<dt id="Service">Service</dt>
<dd> A service is a <a href="#Product">product</a> that is intangible and non-storable. </dd>
<dt id="Software_Engineering">Software Engineering</dt>
<dd>
<ol>
<li>The application of a systematic, disciplined, quantifiable approach to the <a href="#Development">development</a>, operation, and maintenance of software.</li>
<li>The study of approaches as in (1).</li>
</ol>
</dd>
<dt id="Software_Life_Cycle">Software Life Cycle</dt>
<dd> Often used as another name for the <a href="#Software_Process">software process</a>. Originally coined to refer to the waterfall model of the software process (Sommarville, 2007). </dd>
<dt id="Software_Process">Software Process</dt>
<dd> The related set of activities and processes that are involved in developing and evolving a software system (Sommarville, 2007). </dd>
<dt id="Specific_Goal">Specific Goal</dt>
<dd> A <a href="#Required_CMMI_Components">required CMMI component</a> that describes the unique characteristics that must be present to satisfy the <a href="#Process_Area">process area</a>. </dd>
<dt id="Specific_Practice">Specific Practice</dt>
<dd> An <a href="#Expected_CMMI_Components">expected model component</a> that is considered important in achieving the associated <a href="#Specific_Goal">specific goal</a>. The specific practices describe the activities expected to result in achievement of the specific goals of a <a href="#Process_Area">process area</a>. </dd>
<dt id="Sponsor">Sponsor</dt>
<dd> An integrated team sponsor is a manager (individual or team) who is responsible for establishing and providing resources to an integrated team, monitoring its activities and progress, and taking corrective action when needed. A sponsor may manage one or many teams. Team sponsors can be project managers. </dd>
<dd> The person who &#8216;owns&#8217; a project from a business perspective and who is usually responsible to the organization for the achievement of the project&#8217;s business case (Cadle &amp; Yeates, 2004). </dd>
<dt id="Stakeholder">Stakeholder</dt>
<dd> An<br />
individual or group that is affected by the activities and/or the outcome of a <a href="#Project">project</a> or an <a href="#Organization">organization</a> (Cadle &amp; Yeates, 2004). Stakeholders may include:&nbsp;</p>
<ul>
<li><a href="#Project">Project</a> members
<ul>
<li>e.g. <a href="#Project_Manager">Project Manager</a></li>
</ul>
</li>
<li>Suppliers</li>
<li><a href="#Customer">Customers</a></li>
<li>End users</li>
<li><a href="#Relevant_Stakeholder">Relevant Stakeholders</a>
<ul>
<li>e.g. <a href="#Sponsor">Sponsor</a></li>
</ul>
</li>
</ul>
</dd>
<dt id="Standard">Standard</dt>
<dd> When you see the word standard used as a noun in a <a href="#CMMI_Model">CMMI model</a>, it refers to the formal mandatory requirements developed and used to prescribe consistent approaches to <a href="#Development">development</a> (e.g., ISO/IEC standards, IEEE standards, and organizational standards). Instead of using standard in its common everyday sense, we use another term that means the same thing (e.g., typical, traditional, usual, or customary). </dd>
<dt id="Standard_Process">Standard Process</dt>
<dd> An operational definition of the basic process that guides the establishment of a common process in an <a href="#Organization">organization</a>. </dd>
<dt id="Training">Training</dt>
<dd> Formal and informal learning options, which may include in-class training, informal mentoring, Web-based training, guided self-study, and formalized on-the-job training programs. The learning options selected for each situation are based on an assessment of the need for training and the performance gap to be addressed. </dd>
<dt id="UML">UML</dt>
<dd> The leader in modeling languages used for specifying and documenting the artifacts of software development process and has become the de facto standard (Deek &amp; McHugh Eljabiri, 2005). </dd>
<dt id="Work_Product">Work Product</dt>
<div id="attachment_432" class="wp-caption alignright" style="width: 173px"><a rel="attachment wp-att-432" href="http://www.linuxfuture.org/2011/10/richstyle-software-process/work_product/"><img class="size-full wp-image-432" title="Work_Product" src="http://www.linuxfuture.org/wp-content/uploads/2011/10/Work_Product.png" alt="Product is a type of Work Product, and consist of Product Components" width="163" height="249" /></a><p class="wp-caption-text">Product is a type of Work Product, and consist of Product Components</p></div>
<dd> a useful result of a process. This can include:<br />
&nbsp;</p>
<ul>
<li>Files</li>
<li><a href="#Document">Documents</a></li>
<li><a href="#Product">Products</a></li>
<li><a href="#Product_Component">Product Components</a></li>
<li><a href="#Service">Services</a></li>
<li>Process descriptions</li>
<li>Specifications</li>
<li>Invoices</li>
</ul>
<p>A key distinction between a work product and a <a href="#Product_Component"> product component</a> is that a work product is not necessarily part of the <a href="#Product">product</a>.</p>
</dd>
<dt>XHTML</dt>
<dd> An improved version of <a href="#HTML">HTML</a>; committed to <a href="#XML">XML</a> standard; set by W3 Consortium. </dd>
<dt id="XML">XML</dt>
<dd> Standard (and its variants) used to improve compatibility between the disparate systems of business partners by defining the meaning of data in business documents (Truban, 2006). </dd>
</dl>
<h1>Acronyms and Abbreviations</h1>
<dl>
<dt>ASP</dt>
<dd>Association of Software Professionals</dd>
<dt>CSS</dt>
<dd>Cascading Style Sheets</dd>
<dt>CMM</dt>
<dd>Capability Maturity Model</dd>
<dt>CMMI</dt>
<dd>Capability Maturity Model Integration</dd>
<dt>DEB</dt>
<dd>Debian Package File</dd>
<dt>HTML</dt>
<dd>Hypertext Markup Language</dd>
<dt>ISO</dt>
<dd>International Standards Organization</dd>
<dt>LAMP</dt>
<dd>Linux, Apache, MySQL, and PHP</dd>
<dt>PAD</dt>
<dd>Portable Application Description</dd>
<dt>SEI</dt>
<dd>Software Engineering Institute</dd>
<dt>TinyMCE</dt>
<dd>Tiny Moxiecode Content Editor</dd>
<dt>UML</dt>
<dd>Unified Modeling Language</dd>
<dt>WYSIWYG</dt>
<dd>What You See Is What You Get</dd>
<dt>XHTML </dt>
<dd>Extensible Hypertext Markup Language</dd>
<dt>XML</dt>
<dd>Extensible Markup Language</dd>
</dl>
<h1>References</h1>
<ul>
<li> CMMI Product Team,	<em>CMMI for Development v1.2</em>, 	Carnegie Mellon Software Engineering Institute (SEI), 2006</li>
<li> Sommarville I,		<em>Software Engineering 8e</em>, 		Addison Wesley, 2007</li>
<li> Turban E,			<em>Electronic Commerce</em>, 			Prentice Hall, 2006</li>
<li> Cadle &amp; Yeates,		<em>Project Management for Information Systems 4e</em>, 	Prentice Hall, 2004</li>
<li> Deek &amp; McHugh Eljabiri,	<em>Strategic Software Engineering</em>,		Auerbach Publications, 2005</li>
<li> Thomas K,			<em>Beginning Ubuntu Linux 2e</em>,		Apress, 2007</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.linuxfuture.org/2011/10/richstyle-software-process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Linux vs. Windows, An Abstract View</title>
		<link>http://www.linuxfuture.org/2011/09/linux-vs-windows-an-abstract-view/</link>
		<comments>http://www.linuxfuture.org/2011/09/linux-vs-windows-an-abstract-view/#comments</comments>
		<pubDate>Fri, 02 Sep 2011 13:15:26 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://www.linuxfuture.org/?p=391</guid>
		<description><![CDATA[It&#8217;s been a while since I post a paper titled &#8220;Linux vs. Windows, Software Engineering Perspective&#8220;. Nowadays, when I call it back, I always say that the must important idea out of it was what I can call it an age-old conflict between user&#8217;s requirements and developer&#8217;s requirements. I believe that the weight of this [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s been a while since I post a paper titled &#8220;<a title="Linux vs. Windows, Software Engineering Perspective" href="http://www.linuxfuture.org/2009/07/linux-vs-windows-software-engineering-perspective/">Linux vs. Windows, Software Engineering Perspective</a>&#8220;.  Nowadays, when I call it back, I always say that the must important idea out of it was what I can call it an age-old conflict between user&#8217;s requirements and developer&#8217;s requirements.</p>
<p>I believe that the weight of this conflict in Windows world, comparing to it in Linux world, is the critical factor that lays out the bright Linux future.</p>
<p>Imagine that user&#8217;s requirements are represented by just a hot-air-balloon, and developer&#8217;s requirements are represented by the basket&#8217;s content. Take a look!</p>
<div id="attachment_393" class="wp-caption alignnone" style="width: 265px"><a rel="attachment wp-att-393" href="http://www.linuxfuture.org/2011/09/linux-vs-windows-an-abstract-view/linux-vs-windows/"><img class="size-medium wp-image-393" title="Linux-vs-Windows" src="http://www.linuxfuture.org/wp-content/uploads/2011/09/Linux-vs-Windows-255x300.png" alt="Linux vs. Windows" width="255" height="300" /></a><p class="wp-caption-text">Linux vs. Windows</p></div>
<p>Believe me, penguin, sometimes, can fly better than a flag! <img src='http://www.linuxfuture.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.linuxfuture.org/2011/09/linux-vs-windows-an-abstract-view/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GWrite as a RichStyle Front-End</title>
		<link>http://www.linuxfuture.org/2011/08/gwrite-as-a-richstyle-front-end/</link>
		<comments>http://www.linuxfuture.org/2011/08/gwrite-as-a-richstyle-front-end/#comments</comments>
		<pubDate>Tue, 23 Aug 2011 08:02:49 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[Desktop Applications]]></category>
		<category><![CDATA[RichStyle]]></category>

		<guid isPermaLink="false">http://www.linuxfuture.org/?p=371</guid>
		<description><![CDATA[GWrite, from my point of view, represents the best choice to implement my vision for the perfect word processor; an HTML5/CSS3-powered word processor, as a front-end for RichStyle library. I&#8217;ve developed a custom version of TinyMCE, called rsTinyMCE, as a prototype to illustrate this vision as much as possible. Things that I couldn&#8217;t represent in [...]]]></description>
			<content:encoded><![CDATA[<p>GWrite, from my point of view, represents the best choice to implement my vision for the<em> perfect word processor</em>; an HTML5/CSS3-powered word processor, as a front-end for RichStyle library.</p>
<p>I&#8217;ve developed a custom version of TinyMCE, called <a title="rsTinyMCE Demo" href="http://www.richstyle.org/rsTinyMCE.html" target="_blank">rsTinyMCE</a>, as a prototype to illustrate this vision as much as possible.</p>
<p>Things that I couldn&#8217;t represent in this prototype, had drawn in the following fake screenshot.</p>
<div id="attachment_372" class="wp-caption alignnone" style="width: 310px"><a rel="attachment wp-att-372" href="http://www.linuxfuture.org/2011/08/gwrite-as-a-richstyle-front-end/rstinymce/"><img class="size-medium wp-image-372" title="rsTinyMCE" src="http://www.linuxfuture.org/wp-content/uploads/2011/08/rsTinyMCE-300x188.png" alt="rsTinyMCE: A GWrite prototype" width="300" height="188" /></a><p class="wp-caption-text">rsTinyMCE: A GWrite prototype</p></div>
<p>The differences, as you see, are:</p>
<ul>
<li>&#8220;Active Languages&#8221; combo box: To add lang=&#8221;" attribute to any tag or string. RichStyle library will take care of the appropriate font and directionality of the selected language.</li>
<li>Views: Screen, Print, Source, Split.</li>
</ul>
<p>&#8220;Find and Replace&#8221; fields should appear as a tool bar, not as a pop-up window, just like Firefox.</p>
<p>There&#8217;s a discussion on Launchpad about GWrite as an alternative word processor for elementaryOS:<br />
<a title="https://blueprints.launchpad.net/elementaryos/+spec/abiword-alternative" href="https://blueprints.launchpad.net/elementaryos/+spec/abiword-alternative">https://blueprints.launchpad.net/elementaryos/+spec/abiword-alternative</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.linuxfuture.org/2011/08/gwrite-as-a-richstyle-front-end/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>RichStyle and GNOME</title>
		<link>http://www.linuxfuture.org/2011/08/richstyle-and-gnome/</link>
		<comments>http://www.linuxfuture.org/2011/08/richstyle-and-gnome/#comments</comments>
		<pubDate>Thu, 18 Aug 2011 10:42:32 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[Desktop Applications]]></category>
		<category><![CDATA[RichStyle]]></category>
		<category><![CDATA[Web Applications]]></category>

		<guid isPermaLink="false">http://www.linuxfuture.org/?p=364</guid>
		<description><![CDATA[It&#8217;s been more than ten years since I attended the first IT-related course in my life, which was an MS Windows and Office course. Since that time, I&#8217;ve been asking myself, could HTML/CSS standards offer an alternative to office-applications&#8217; capabilities? No doubt that HTML standards and tools at that time weren&#8217;t mature enough, they were [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s been more than ten years since I attended the first IT-related course in my life, which was an MS Windows and Office course. Since that time, I&#8217;ve been asking myself, could HTML/CSS standards offer an alternative to office-applications&#8217; capabilities?</p>
<p>No doubt that HTML standards and tools at that time weren&#8217;t mature enough, they were very poor comparing to the exist office tools and applications that were, in turn, growing without disciplines or clear standards.</p>
<p>However, HTML5 and CSS3 nowadays offer very powerful standards, and implemented by very powerful user agents; standards and agents that merge office capabilities with multimedia capabilities arriving to an ultimate rich content experience.</p>
<p>Using CSS3, you are supposed to be able to display the same document in different &#8220;views&#8221; for different media, with no need to reproduce it for each media. A view for web pages, another for printing media (papers), a third one for projector, and so on.</p>
<p>My loyal to CSS led me to develop what I can call it a &#8220;Standard Implementation of the Standard Specifications&#8221;; a CSS library that represents, in my opinion at least, the best practice in its field.</p>
<p>I don&#8217;t claim that it&#8217;s a ready-to-use library. Instead, I try to keep it grow along with specifications, without tricks or twisted solutions, but with recommendations; recommendations that help specifications grow in turn. It aims to put HTML5/CSS3 standards in action, and send back feedback and recommendations. See: <a title="http://richstyle.org/todo.php" href="http://richstyle.org/todo.php">http://richstyle.org/todo.php</a>.</p>
<p>On the other hand, I have a theory says that; for simplicity&#8217;s sake; user can outsource the document&#8217;s format-instructions to the entire-system&#8217;s theme, so that all documents around can comply the system&#8217;s theme, and have the same spirit of the whole system. However, there could be an option in the user-agent&#8217;s interface that gives user a chance to display the document the way the original author has wrote it. Technically, it&#8217;s a chance to activate the CSS instructions included in that document. This means that CSS instructions included in a document should be disabled by default. It seems to me that the CSS-powered GNOME 3 advances this theory.</p>
<p>Imagine that everything in your desktop complies with this central CSS file:</p>
<ul>
<li>Web pages</li>
<li>Yelp pages</li>
<li> Documents</li>
<li>Emails</li>
<li>DocBooks</li>
<li>Spreadsheets</li>
<li>UML diagrams</li>
<li>GTK widgets</li>
<li>SVG icons</li>
</ul>
<p>Everything is powered by one theme.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.linuxfuture.org/2011/08/richstyle-and-gnome/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pure CSS Icons</title>
		<link>http://www.linuxfuture.org/2011/08/pure-css-icons/</link>
		<comments>http://www.linuxfuture.org/2011/08/pure-css-icons/#comments</comments>
		<pubDate>Wed, 17 Aug 2011 12:41:41 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[RichStyle]]></category>
		<category><![CDATA[Web Applications]]></category>

		<guid isPermaLink="false">http://www.linuxfuture.org/?p=345</guid>
		<description><![CDATA[Thanks to Nicolas Gallagher for his great work, Pure CSS GUI Icons, you can draw icons on your web pages using only CSS rules stored in a single CSS file, with no external images at all! This means two main advantages: Significant reduction in HTTP requests. Your web page will be faster. High-flexibility for modification. [...]]]></description>
			<content:encoded><![CDATA[<p>Thanks to Nicolas Gallagher for his great work, <a href="http://nicolasgallagher.com/pure-css-gui-icons/" target="_blank">Pure CSS GUI Icons</a>, you can draw icons on your web pages using only CSS rules stored in a single CSS file, with no external images at all!</p>
<div id="attachment_346" class="wp-caption alignnone" style="width: 310px"><a rel="attachment wp-att-346" href="http://www.linuxfuture.org/2011/08/pure-css-icons/pure-css-gui-icons/"><img class="size-medium wp-image-346" title="pure-css-gui-icons" src="http://www.linuxfuture.org/wp-content/uploads/2011/08/pure-css-gui-icons-300x200.png" alt="Pure CSS GUI icons" width="300" height="200" /></a><p class="wp-caption-text">Pure CSS GUI icons</p></div>
<p>This means two main advantages:</p>
<ol>
<li>Significant reduction in HTTP requests. Your web page will be faster.</li>
<li>High-flexibility for modification. The icon colors &#8211; and the other attributes &#8211; can be simply modified using a one single CSS file.</li>
</ol>
<p>I just have several notes:</p>
<ul>
<li>I think this set of icons misses a very important one: A print icon.</li>
<li>Bug: Letters used in those icons are not zoom-able along with icons themselves.</li>
<li>I wish if the class names used for these icons comply with the &#8220;Icon Naming Specifications&#8221; according to freedosktop.org.</li>
<li>I believe that such a unique solution should be extended and cover the whole operating-system icons. Such icons could be used for the GNOME panel. Not to mention that GNOME3 adopts CSS3 for the desktop themes.</li>
</ul>
<div id="attachment_238" class="wp-caption alignnone" style="width: 265px"><a rel="attachment wp-att-238" href="http://www.linuxfuture.org/2011/07/an-elementary-review-of-the-elementaryos/light-on-dark-2/"><img class="size-full wp-image-238" title="light-on-dark" src="http://www.linuxfuture.org/wp-content/uploads/2011/07/light-on-dark.png" alt="Light-on-dark colors" width="255" height="125" /></a><p class="wp-caption-text">Light-on-dark colors</p></div>
<p>Finally, this work really deserves to be published as a Debian/RPM package.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.linuxfuture.org/2011/08/pure-css-icons/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>تراخيص البرمجيات الحرة بالعربية</title>
		<link>http://www.linuxfuture.org/2011/07/%d8%aa%d8%b1%d8%a7%d8%ae%d9%8a%d8%b5-%d8%a7%d9%84%d8%a8%d8%b1%d9%85%d8%ac%d9%8a%d8%a7%d8%aa-%d8%a7%d9%84%d8%ad%d8%b1%d8%a9-%d8%a8%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9/</link>
		<comments>http://www.linuxfuture.org/2011/07/%d8%aa%d8%b1%d8%a7%d8%ae%d9%8a%d8%b5-%d8%a7%d9%84%d8%a8%d8%b1%d9%85%d8%ac%d9%8a%d8%a7%d8%aa-%d8%a7%d9%84%d8%ad%d8%b1%d8%a9-%d8%a8%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9/#comments</comments>
		<pubDate>Sun, 31 Jul 2011 11:25:46 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[Arabesque]]></category>
		<category><![CDATA[Localization]]></category>
		<category><![CDATA[RichStyle]]></category>
		<category><![CDATA[Affero]]></category>
		<category><![CDATA[Arabic]]></category>
		<category><![CDATA[BSD]]></category>
		<category><![CDATA[Debian Social Contract]]></category>
		<category><![CDATA[GNU]]></category>
		<category><![CDATA[GPL]]></category>
		<category><![CDATA[License]]></category>
		<category><![CDATA[MIT]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[ترجمة]]></category>
		<category><![CDATA[تعريب]]></category>
		<category><![CDATA[رخصة]]></category>

		<guid isPermaLink="false">http://www.linuxfuture.org/?p=313</guid>
		<description><![CDATA[أضع بين يدي القارئ العربي الكريم طائفة من تراخيص البرمجيات الحرة الأكثر أهمية وانتشاراً، مترجمة إلى العربية. تشمل هذه التراخيص كلاً من: رخصة GPL2 من غنو رخصة AGPL1 من أفيرو رخصة BSD رخصة MIT بيان ورخصة W3C® عقد دبيان الاجتماعي]]></description>
			<content:encoded><![CDATA[<div style="direction: rtl; text-align: right;" lang="ar">
<p>أضع بين يدي القارئ العربي الكريم طائفة من <a title="تراخيص البرمجيات الحرة بالعربية" href="http://os-licenses.richstyle.org/">تراخيص البرمجيات الحرة</a> الأكثر أهمية وانتشاراً، مترجمة إلى العربية.</p>
<p>تشمل هذه التراخيص كلاً من:</p>
<ul>
<li><a href="http://os-licenses.richstyle.org/GNU-GPL2-ar.php">رخصة GPL2  من غنو</a></li>
<li><a href="http://os-licenses.richstyle.org/Affero-GPL1-ar.php">رخصة AGPL1 من أفيرو</a></li>
<li><a href="http://os-licenses.richstyle.org/BSD-ar.php">رخصة BSD</a></li>
<li><a href="http://os-licenses.richstyle.org/MIT-ar.php">رخصة MIT</a></li>
<li><a href="http://os-licenses.richstyle.org/W3C-ar.php">بيان ورخصة W3C®</a></li>
<li><a href="http://os-licenses.richstyle.org/Debian-Social-Contract-ar.php">عقد دبيان الاجتماعي</a></li>
</ul>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.linuxfuture.org/2011/07/%d8%aa%d8%b1%d8%a7%d8%ae%d9%8a%d8%b5-%d8%a7%d9%84%d8%a8%d8%b1%d9%85%d8%ac%d9%8a%d8%a7%d8%aa-%d8%a7%d9%84%d8%ad%d8%b1%d8%a9-%d8%a8%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Gnumeric and HTML</title>
		<link>http://www.linuxfuture.org/2011/07/gnumeric-and-html/</link>
		<comments>http://www.linuxfuture.org/2011/07/gnumeric-and-html/#comments</comments>
		<pubDate>Mon, 25 Jul 2011 09:58:34 +0000</pubDate>
		<dc:creator>Anas R.</dc:creator>
				<category><![CDATA[Desktop Applications]]></category>
		<category><![CDATA[RichStyle]]></category>
		<category><![CDATA[Cheat Sheet]]></category>
		<category><![CDATA[CheatSheet]]></category>
		<category><![CDATA[CSS3]]></category>
		<category><![CDATA[Gnumeric2HTML]]></category>
		<category><![CDATA[Gnumeric2PDF]]></category>
		<category><![CDATA[Guide]]></category>
		<category><![CDATA[HTML5]]></category>
		<category><![CDATA[Tutorial]]></category>

		<guid isPermaLink="false">http://www.linuxfuture.org/?p=269</guid>
		<description><![CDATA[When I was working on the last version of RichStyle project, a sub-project emerged. It was the HTML5/CSS3 Quick References. The main challenge at that time was choosing the right spreadsheet application that helps me generate the best PDF file out of it. At the same time, my loyal to CSS has led me to [...]]]></description>
			<content:encoded><![CDATA[<p>When I was working on the last version of RichStyle project, a sub-project emerged. It was the <a title="HTML5 Quick Reference" href="http://web-standards.richstyle.org/" target="_blank">HTML5/CSS3 Quick References</a><a title="CSS3 Quick Reference" href="http://richstyle.org/download/CSS3_Quick_Reference_1.0.pdf"></a>. The main challenge at that time was choosing the right spreadsheet application that helps me generate the best PDF file out of it. At the same time, my loyal to CSS has led me to another challenge; I had to use Prince XML along with RichStyle library to generate the desired PDF file.</p>
<p>Back to the spreadsheet application issue, I decided to use Gnumeric rather than OpenOffice Calc. It&#8217;s my absolute commitment to GNOME.</p>
<p>So, the whole process had to pass through three conversion processes, and four file formats!</p>
<div id="attachment_270" class="wp-caption alignnone" style="width: 310px"><a rel="attachment wp-att-270" href="http://www.linuxfuture.org/2011/07/gnumeric-and-html/ss2pdf/"><img class="size-medium wp-image-270" title="ss2pdf" src="http://www.linuxfuture.org/wp-content/uploads/2011/07/ss2pdf-300x39.png" alt="Gnumeric to PDF" width="300" height="39" /></a><p class="wp-caption-text">Gnumeric to PDF</p></div>
<p>In order to simplify this process, Gnumeric should testify more commitment to HTML standards as much as possible.</p>
<ul>
<li>TH cells: There should be a kind of cells called &#8220;title cell&#8221;, represented by TH tag.</li>
<li>Improved links: Internal links should use ID attribute as the target&#8217;s address, exactly the way XHTML 1.1 does.</li>
<li>Support  CLASS attribute for cells, rows, and columns.</li>
<li>Cell padding: Using CSS, user should be able to adjust a cell&#8217;s padding from the &#8220;Format cells&#8221; dialog.</li>
<li>TBody for grouping.</li>
</ul>
<p>Once user wants to export to HTML, Gnumeric should consider the following:</p>
<ul>
<li>Metadata: Metadata of the Gnumeric file should be resented by and exported to HTML metadata.</li>
<li>Export printing area only.</li>
<li>Except hidden sheets.</li>
</ul>
<p>With the following options:</p>
<ul>
<li>Represent each sheet as: caption/h1/h2/h3/h4.</li>
<li>Formulas: Dynamic/Static.</li>
<li>Print a formula report: i.e. A5 = A1 * 2.</li>
</ul>
<p>Finally, regardless HTML, I wish I could see the following:</p>
<ul>
<li>Rotate: A command under &#8220;Tool&#8221; menu to convert rows to columns and vice versa.</li>
<li>Using &#8220;unit&#8221; instead of &#8220;currency&#8221;: i.e. I can use meter, pound, or any other unit; not just currency.</li>
<li>An ability to distinguish formula cells (kind of conditional format).</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.linuxfuture.org/2011/07/gnumeric-and-html/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

