<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:georss="http://www.georss.org/georss" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0"><id>tag:blogger.com,1999:blog-34916570</id><updated>2009-11-11T09:55:51.820-05:00</updated><title type="text">Ayman's Reflections on Project and Systems Engineering, Architecture, Management and Leadership</title><subtitle type="html">Reflections, thoughts, ideas, definitions, concepts, and observations</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://sys-eng.blogspot.com/" /><link rel="hub" href="http://pubsubhubbub.appspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default?start-index=26&amp;max-results=25" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>92</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership" type="application/atom+xml" /><feedburner:emailServiceId>Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry><id>tag:blogger.com,1999:blog-34916570.post-460473559857638427</id><published>2009-11-11T09:42:00.006-05:00</published><updated>2009-11-11T09:55:51.977-05:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="business architecture" /><category scheme="http://www.blogger.com/atom/ns#" term="capabilities" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise architecture" /><title type="text">Strategy and its Role in Becoming Capable</title><content type="html">Strategy is focused on the matching of an enterprise's opportunities and threats (external factors) to the enterprise's capabilities.&lt;br /&gt;&lt;br /&gt;In some cases an organization might not have a capability in place that allows it to benefit from an opportunity. In such cases the capability will need to be realized otherwise the opportunity will be missed. The realization of such absent capability is part of the enterprise strategy, and will require enablers from across the enterprise such as technology, locations, roles, processes, intellectual property and more.&lt;br /&gt;&lt;br /&gt;__________________________________________&lt;br /&gt;Robert Grant, "Contemporary strategy analysis: concepts, techniques, applications", Blackwell Publishing, 2002.&lt;br /&gt;&lt;br /&gt;Harvey Thompson, "The Customer-Centered Enterprise: How IBM and Other World-Class Companies Achieve Extraordinary Results", Mc Graw-Hill, 2000.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-460473559857638427?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/nnT7pCHIigQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/460473559857638427/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=460473559857638427" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/460473559857638427" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/460473559857638427" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/nnT7pCHIigQ/strategy-and-its-role-in-becoming.html" title="Strategy and its Role in Becoming Capable" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/11/strategy-and-its-role-in-becoming.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-403494032726268166</id><published>2009-11-10T16:03:00.002-05:00</published><updated>2009-11-10T17:20:42.182-05:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="business architecture" /><category scheme="http://www.blogger.com/atom/ns#" term="capabilities" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise architecture" /><title type="text">Getting Capable</title><content type="html">Institutions vary widely in their capabilities to achieve their mission. You could find two organizations in the exact same line of business, with very similar strategies and business drivers, yet very different results due to the differences in their capabilities. Lets take an example of two airlines. Both airlines share the same mission, transporting humans across the globe safely and in an enjoyable manner. Airline A always takes off on time, lands on time and does not lose luggage. Airline B always takes off late and loses luggage.&lt;br /&gt;&lt;br /&gt;Their business requirement is the same, yet their outcomes are very different, which is due to differences in their capabilities.&lt;br /&gt;&lt;br /&gt;A capability is a realized requirement, it could also be said that a capability is a business requirement added to some value acquisition process. The value acquisition process should span the entire enterprise to ensure that is picked from all strengths of the enterprise and also did not bring along any unnecessary baggage.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-403494032726268166?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/42jZ-iT2_kc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/403494032726268166/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=403494032726268166" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/403494032726268166" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/403494032726268166" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/42jZ-iT2_kc/getting-capable.html" title="Getting Capable" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/11/getting-capable.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-910899545238041817</id><published>2009-10-28T16:37:00.004-04:00</published><updated>2009-10-28T16:51:30.361-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="business architecture" /><title type="text">Organizational Capabilities in Less than 100 Words</title><content type="html">How quick can your organization respond to its constituents needs. How effective can it adapt to changing dynamics in the environment surrounding it? How efficient can it deliver its mission? The answer to these questions depends on what we call organizational capabilities.&lt;br /&gt;&lt;br /&gt;Similar to an individual's ability, organizations have abilities to do certain things, these abilities combined with resources, assets, processes and skills form an organizational capability. A few examples of strategic capabilities are (1) The ability to innovate and be creative, (2) the ability to develop and deploy products in a compressed cycle, and (3) the ability to educate and train young people.&lt;br /&gt;&lt;br /&gt;Are your capabilities well defined? Do you know how to improve them, and how to measure where these capabilities are enabling your stakeholders to realize the value proposition you are offering?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-910899545238041817?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/fx12CljKHFE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/910899545238041817/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=910899545238041817" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/910899545238041817" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/910899545238041817" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/fx12CljKHFE/organizational-capabilities-in-less.html" title="Organizational Capabilities in Less than 100 Words" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/10/organizational-capabilities-in-less.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-2445494868426997805</id><published>2009-10-26T15:32:00.002-04:00</published><updated>2009-10-26T15:41:55.237-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="business architecture" /><title type="text">Know Thy Business Events</title><content type="html">A business event is a valuable building block in an enterprise's business architecture. Business events provide insights to triggers and decision points in the business domain. Business events could be classified into three types: External events such as a customer service request, internal events such as closing a project or an employee time sheet submission, and finally temporal events which occur based on the elapse of a given time-frame such as end of month.&lt;br /&gt;&lt;br /&gt;There are many important questions to ask oneself about events when building a business architecture or when defining events. Examples are:&lt;br /&gt;&lt;br /&gt;1. How are these events identified?&lt;br /&gt;2. Are they unique?&lt;br /&gt;3. Can they be repeatable?&lt;br /&gt;4. How can we structure events in the context of a business architecture?&lt;br /&gt;5. How can events be modular?&lt;br /&gt;6. What processes are related to events?&lt;br /&gt;7. What business capabilities are impacted by events?&lt;br /&gt;8. What impact does the event have on the business services, operations and other areas?&lt;br /&gt;9. Who reacts (which roles) to an event and in what way?&lt;br /&gt;10. How often does an event occur and what is its significance?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-2445494868426997805?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/H1HAOGRqlL8" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/2445494868426997805/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=2445494868426997805" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/2445494868426997805" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/2445494868426997805" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/H1HAOGRqlL8/know-thy-business-events.html" title="Know Thy Business Events" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/10/know-thy-business-events.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-8160230985019945834</id><published>2009-09-08T15:21:00.004-04:00</published><updated>2009-09-09T15:34:37.399-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="business architecture" /><category scheme="http://www.blogger.com/atom/ns#" term="architecture" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise architecture" /><title type="text">Step By Step Business Architecture</title><content type="html">Developing a business architecture for an enterprise can be a daunting task. However following a systematic approach makes it a bit easier, or at the very least organized.&lt;br /&gt;&lt;br /&gt;1. Develop a description of the existing business architecture if it exists. The description should include as much of the AS-IS architecture as needed for the development of the TO-BE architecture.&lt;br /&gt;&lt;br /&gt;2. Identify any reference models, tools, patterns and techniques that should be used to develop the TO-BE architecture based on the context, complexity and scope of your business requirements.&lt;br /&gt;&lt;br /&gt;3. Select viewpoints of the business architecture to be utilized to illustrate the architecture, according to the business requirements. Common business architecture view points are operational, systems, technology, governance, financial and functional viewpoints.&lt;br /&gt;&lt;br /&gt;4. Develop an architecture model for your TO-BE business requirements. Ensure that you perform each of these,&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Create the model for the specific view point. For example create the activity model for an operational view point of the business architecture. Common models are activity models, use-case models, class models, node connectivity diagrams and information exchange matrices.&lt;/li&gt;&lt;li&gt;Verify that all stakeholder requirements and concerns are included.&lt;/li&gt;&lt;li&gt;Ensure you have models for business goals and objectives, business functions, business services, business processes,  roles, business data,&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Ensure your architecture has captured the interlocking of organization and functions, and interlocking of processes and systems.&lt;/li&gt;&lt;li&gt;For each business function identify when, where, where, how often and by whom will the function be performed. Identify the inputs to the function and the expected outputs.&lt;/li&gt;&lt;li&gt;Identify dependencies and assumptions for each business function.&lt;/li&gt;&lt;li&gt;Conduct trade-off analysis if any conflict exist among the different views.&lt;/li&gt;&lt;li&gt;Validate and verify the developed model against requirements for completeness and scope&lt;/li&gt;&lt;/ul&gt;5. Select the business architecture building blocks (a.ka. business component model - CBM). Reuse blocks as applicable, and develop new ones to add to the CBM library.&lt;br /&gt;&lt;br /&gt;6. Hold a formal architectural review of the developed model and building blocks with the stakeholders.&lt;br /&gt;&lt;br /&gt;7. Review the non-functional requirements and service level agreements. Common non-functional requirements are scalability, performance, availability, costs, reliability and capacity.&lt;br /&gt;&lt;br /&gt;8. Complete the documentation for the business architecture by ensuring that you,&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Have a completed requiements traceability report.&lt;/li&gt;&lt;li&gt;Identified requirements that are driving the architecture.&lt;/li&gt;&lt;li&gt;Mapped the architecture to reference architectures and models in the organization.&lt;/li&gt;&lt;li&gt;Identified new vs. reused building blocks.&lt;/li&gt;&lt;li&gt;Documented rationale for architectural decisions.&lt;/li&gt;&lt;li&gt;Completed the business architecture report including the business footprint, detailed description of business functions, and their information needs.&lt;/li&gt;&lt;li&gt;Outlined the governance footprint as related to the business needs and scope of the TO-BE&lt;/li&gt;&lt;li&gt;Included a table of standards, rules, guidelines, assumptions, dependencies, and measures used.&lt;/li&gt;&lt;/ul&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-8160230985019945834?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/3xoDvwmFDtY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/8160230985019945834/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=8160230985019945834" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/8160230985019945834" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/8160230985019945834" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/3xoDvwmFDtY/step-by-step-business-architecture.html" title="Step By Step Business Architecture" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/09/step-by-step-business-architecture.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-5039996168626477030</id><published>2009-09-08T12:45:00.003-04:00</published><updated>2009-09-14T12:11:07.346-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="architecture" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise architecture" /><title type="text">Business and Enterprise Architectures: Differences and Commonalities</title><content type="html">Business architecture is a unifying structure that enables the execution of business strategies through initiatives to achieve business results. The business architecture could also be viewed as the relationships and connectivity among the various value streams and the inputs that feed these value steams, the processing centers that enable the value streams and the value realized.&lt;br /&gt;&lt;br /&gt;Business architecture is only one component of enterprise architecture. In an enterprise there are business objectives, technology and infrastructure assets, organizational units, security concerns information handling and processing and various other components, each of which can be defined as a separate architecture and part of a defined framework.&lt;br /&gt;&lt;br /&gt;The business architecture encompasses the business flows, activity models, use cases, user models, class models, node connectivity diagrams and business information exchange matrices. Business architectures usually reflect a baseline known as the AS-IS architecture and defines a future aspiration known as the TO-BE architecture.&lt;br /&gt;&lt;br /&gt;Enterprise architectures explain all aspects of an enterprise; its data, business processes, infrastructure, technology and business&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-5039996168626477030?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/sTtGxa99rn0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/5039996168626477030/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=5039996168626477030" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/5039996168626477030" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/5039996168626477030" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/sTtGxa99rn0/business-and-enterprise-architectures.html" title="Business and Enterprise Architectures: Differences and Commonalities" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/09/business-and-enterprise-architectures.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-7958809939964825469</id><published>2009-08-12T15:29:00.007-04:00</published><updated>2009-08-13T10:50:39.904-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="systems engineering" /><category scheme="http://www.blogger.com/atom/ns#" term="Patterns" /><category scheme="http://www.blogger.com/atom/ns#" term="Processes" /><title type="text">Patterns: What Are They? Part 1</title><content type="html">Literally patterns are defined as a combination of qualities, items, objects, behaviors, or other which form a consistent or characteristic arrangement. We observe dozens of daily patterns every day. Examples are teen behavior, the movement of the earth around the sun, the blooming of flowers and hundreds more.&lt;br /&gt;&lt;br /&gt;&lt;blockquote style="color: rgb(102, 102, 204); font-style: italic;"&gt;&lt;span style="font-size:100%;"&gt;"A combination of qualities, items, objects, behaviors, or other which form a consistent or characteristic arrangement"&lt;/span&gt;&lt;/blockquote&gt;&lt;br /&gt;&lt;br /&gt;Patterns are not new to man-kind, the Creator has informed us about patterns in the Quran and other earlier revelations. Recently system developers started to analyze the concept of patterns, pioneered by Christopher Alexander in his book, " A Timeless Way of Building", he defines a pattern as a three-part rule, expressing a relation between a certain context, a problem and a solution.&lt;br /&gt;&lt;br /&gt;Patterns are a first step in understanding root causes of the problem within a specific context. It also allows the development of architectural and solution building blocks.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-size:180%;"&gt;&lt;/span&gt;&lt;blockquote style="color: rgb(102, 102, 204); font-style: italic;"&gt;&lt;span style="font-size:100%;"&gt;"In systems realization, patterns express a relationship between a problem and its solution within a given context"&lt;/span&gt;&lt;/blockquote&gt;For a software designer some pattern examples are: Message Translators, Process Managers, and Proxies to mention a few. A process manager pattern for example will comprise of a sensor to detect an incoming message which initializes the process manager. The process manager in turn executes a set of rules stored in the process manager memory implementing the processing rules, and detects the subsequent steps through a status feedback detector/analyzer.&lt;br /&gt;&lt;br /&gt;Considering a different domain, take the example of a group that does youth trips, examples of patterns could be: Headcount Process, Critical Supplies, Meal Managers, Activity Itinerary Manager and many more. An Activity Itinerary Manager pattern will comprise of an input process to capture developmental and coaching themes/needs of the youth trip, a search process to match the theme to a group of activities that meet the objectives of the theme from a repository of activities, the selected lists of activities could then pass by the activity processor which breaks down the activity into steps, each assigned to resources, a lead, a cost structure, risk factor and plan of action. Feedback from the actual deployed activity is then finally fed back into the activity manager for updates to the activity definitions and other relevant areas, within quality expectations.&lt;br /&gt;&lt;br /&gt;_____________To Read More _______________&lt;br /&gt;&lt;br /&gt;(1) Hohpe and Woolfe, "Enterprise Integration Patterns: Designing, Building and Deploying Messaging Solutions", Addison Wesley signature Series, 2004.&lt;br /&gt;&lt;br /&gt;(2) Haskins and Raveh, "Introduction to Patterns Through Writing Systems Engineering Patterns", 16th Annual International Symposium, 2006.&lt;br /&gt;&lt;br /&gt;(3) Gross and Yu, "From Non-Functional Requirements to Design Through Patterns".&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-7958809939964825469?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/k9Bi6CWyKio" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/7958809939964825469/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=7958809939964825469" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/7958809939964825469" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/7958809939964825469" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/k9Bi6CWyKio/patterns-what-are-they-part-1.html" title="Patterns: What Are They? Part 1" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/08/patterns-what-are-they-part-1.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-783357749689629026</id><published>2009-08-04T12:41:00.009-04:00</published><updated>2009-08-23T08:00:22.408-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="teams" /><category scheme="http://www.blogger.com/atom/ns#" term="leadership" /><title type="text">The Spark ...</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_P1Z4K44RuMU/SoQo-hpspCI/AAAAAAAAANI/0WTizBZ659s/s1600-h/star+formation.jpg"&gt;&lt;img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 400px; height: 300px;" src="http://1.bp.blogspot.com/_P1Z4K44RuMU/SoQo-hpspCI/AAAAAAAAANI/0WTizBZ659s/s400/star+formation.jpg" alt="" id="BLOGGER_PHOTO_ID_5369461710382736418" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Teamwork is touted as the driver behind progress. This is not necessarily true. There is no doubt that teamwork is a fact of life. As humans we have to interact with one another to satisfy our human needs and desires such as socializing, belonging to a group identity, sustaining needs of life among many others.&lt;br /&gt;&lt;br /&gt;Effective teams need leaders to align them and give them direction and motivation. The spark that makes groups and societies move is the outcome of individuals. These sparks ignite the team and thrust its members forward, but the team members do not necessarily produce any starting sparks. As Igor Sikorsky once said,&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;&lt;span style="font-style: italic; color: rgb(102, 102, 204);"&gt;"The work of the individual still remains the spark that moves mankind ahead, even more than teamwork"&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;/blockquote&gt;If you find yourself on a team, organization or society, with higher levels of motivation, vision and commitment than others, don't despair, that means you are a leader. As a leader you can not work alone, sparks don't develop into fire without a catalyst, and your team is your catalyst. Nurture, coach, and develop the team, and it will be a strong catalyst.&lt;br /&gt;&lt;br /&gt;It was once  said that a small group are the ones carrying the ambitions of the nation, and a group of those are the ones who sacrifice their time and wealth to accomplish these ambitions, and a group of that smaller group are the ones who sacrifice their lives for the sake of succeeding in the accomplishment of these ambitions. A small group, from a small group, from a small group.&lt;br /&gt;&lt;span style="color: rgb(102, 102, 204); font-style: italic;"&gt;&lt;br /&gt;&lt;blockquote&gt;&lt;/blockquote&gt;&lt;/span&gt;&lt;blockquote&gt;&lt;span style="color: rgb(102, 102, 204); font-style: italic;"&gt;"A small group, from a small group, from a small group"&lt;/span&gt;&lt;/blockquote&gt;&lt;br /&gt;______________________&lt;br /&gt;&lt;br /&gt;Picture: Courtesy of NASA: The formation of a star, A molecular cloud is a region containing cool interstellar gas and dust left over from the formation of the galaxy and mostly contains molecular hydrogen. The Spitzer data, in red, green and blue shows the molecular cloud (in the bottom part of the image) plus young stars in and around Cepheus B, and the Chandra data in violet shows the young stars in the field. &lt;a href="http://www.nasa.gov/mission_pages/spitzer/news/spitzer-20090812.html"&gt;http://www.nasa.gov/mission_pages/chandra/multimedia/photo09-062.html&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-783357749689629026?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/inmNzsX5_zo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/783357749689629026/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=783357749689629026" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/783357749689629026" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/783357749689629026" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/inmNzsX5_zo/spark.html" title="The Spark ..." /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/_P1Z4K44RuMU/SoQo-hpspCI/AAAAAAAAANI/0WTizBZ659s/s72-c/star+formation.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/08/spark.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-1519061679433695425</id><published>2009-07-16T10:40:00.005-04:00</published><updated>2009-07-16T11:08:20.357-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="leadership" /><title type="text">10 Attributes of a Learning Oganization</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_P1Z4K44RuMU/Sl9AD-u1nCI/AAAAAAAAAM0/7wBPEoOqyjI/s1600-h/abc-blocks-petri-lummema-01.jpg"&gt;&lt;img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 293px; height: 283px;" src="http://2.bp.blogspot.com/_P1Z4K44RuMU/Sl9AD-u1nCI/AAAAAAAAAM0/7wBPEoOqyjI/s400/abc-blocks-petri-lummema-01.jpg" alt="" id="BLOGGER_PHOTO_ID_5359072518717414434" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Communications is a key component of effective leadership. Leaders don't sit in their offices behind their desk, they are out in the field dealing with customers, suppliers, employees and other constituencies of their organization. This interaction between the leader and these other groups and individuals yields tremendous amounts of experience and knowledge. An organization which shares knowledge and learns from its members is a learning organization.&lt;br /&gt;&lt;br /&gt;Learning organizations are characterized by the following:&lt;br /&gt;&lt;br /&gt;1. Possess solid systems for communications among its members.&lt;br /&gt;2. Knowledge and intellect is respected and appreciated.&lt;br /&gt;3. Team work and collaboration is the norm.&lt;br /&gt;4. Members consult one another on a continuous basis.&lt;br /&gt;5. Members update others on a continuous basis.&lt;br /&gt;6. Teams learn from past experiences, and mistakes are rarely repeated.&lt;br /&gt;7. Information, knowledge storage and retrieval is efficient and effective.&lt;br /&gt;8. Team members are accessible and known for their expertise, contributing to centers of competence.&lt;br /&gt;9. Realizes continuous growth and innovation.&lt;br /&gt;10. Encourages diversity and systems-based thinking.&lt;br /&gt;&lt;br /&gt;Is your organization a learning one? How can you assess its learning capabilities?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-1519061679433695425?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/olh3IOxxHjc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/1519061679433695425/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=1519061679433695425" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1519061679433695425" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1519061679433695425" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/olh3IOxxHjc/10-attributes-of-learning-oganization.html" title="10 Attributes of a Learning Oganization" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_P1Z4K44RuMU/Sl9AD-u1nCI/AAAAAAAAAM0/7wBPEoOqyjI/s72-c/abc-blocks-petri-lummema-01.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/07/10-attributes-of-learning-oganization.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-122887464852643663</id><published>2009-07-14T00:47:00.006-04:00</published><updated>2009-07-23T21:08:40.570-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="islam" /><category scheme="http://www.blogger.com/atom/ns#" term="Change" /><title type="text">Instilling Change: A Key Component of Leadership</title><content type="html">Leading change is by no means a trivial job. Only the experienced leaders with astute vision can lead their teams to change. The Prophet Mohammad (peace be upon him) is a role model for not only change, but transformation.&lt;br /&gt;&lt;br /&gt;Our Creator informs us that no group of people will change unless they take initiative to embrace change themselves. Indeed the only things that is constant is change itself, or as Muslims know it as the sunnah of Allah (ways of Allah).&lt;br /&gt;&lt;br /&gt;Scholars of management [1] define a few steps which are key for successfully leading change. I summarize these points [2] and provide references from the Quran and teachings of the Prophet (PBUH).&lt;br /&gt;&lt;br /&gt;1. Intention:&lt;br /&gt;Quran: Indeed Allah does not change the condition of a group unless they change themselves.&lt;br /&gt;Hadith: Indeed deeds are based on their intentions&lt;br /&gt;&lt;br /&gt;2. Urgency:&lt;br /&gt;Quran: So flee to Allah quickly indeed I am to you from him a clear warning&lt;br /&gt;Quran: And hasten to a forgiveness from your Lord and a paradise the width of the skies and earth&lt;br /&gt;&lt;br /&gt;3. Clear Vision:&lt;br /&gt;Quran: And Indeed Allah is my Lord and your Lord, so worship him, this is the straight path (Mary 36)&lt;br /&gt;&lt;br /&gt;4. Stick to a Good Team:&lt;br /&gt;Quran: And seek patience in your soul with the ones who remember their Lord in the early morning, and the evening late at night, seeking his pleasure and acceptance (Cave 28)&lt;br /&gt;Quran: Wow to me, I wish I have not taken him/her a close companion (friend) (Al-Furqan 28)&lt;br /&gt;&lt;br /&gt;5. Self Critique Self:&lt;br /&gt;Quran: Oh you who believe fear Allah, and shall a soul see what it has prepared for its tomorrow (hereafter), and fear Allah, indeed Allah is with what you have performed all knowing&lt;br /&gt;Hadith: Seek forgiveness, for indeed I seek forgiveness 70 times in a day&lt;br /&gt;&lt;br /&gt;6. Take Action and Perfect it:&lt;br /&gt;Hadith: Indeed Allah loves if one of you do an action, that you perfect it&lt;br /&gt;&lt;br /&gt;7. Be Consistent:&lt;br /&gt;Hadith: The best of deeds are the continuous, even if they are little&lt;br /&gt;&lt;br /&gt;8. Take Small Steps:&lt;br /&gt;Hadith: This way of life (Islam) is deep so get in it slowly and gently&lt;br /&gt;&lt;br /&gt;9. Don't Give Up:&lt;br /&gt;Quran: Tell my servants who have transgressed upon themselves to not despair from the mercy of Allah, indeed Allah forgives all the sins.&lt;br /&gt;&lt;br /&gt;10. Offer Value and Increase Benefit:&lt;br /&gt;Good deeds wipe out bad deeds&lt;br /&gt;&lt;br /&gt;11. Ensure You are Working on a Sound Foundation:&lt;br /&gt;Fix your beliefs and values&lt;br /&gt;Quran: And Satin said when the matter was over (life on earth, and the day of judgment), indeed Allah promised you the promise of truth, and I promised you and broke my promise, and I had no power over you, except that I invited you and you accepted, so do not blame me, and blam yourselves. (Ibrahim 22)&lt;br /&gt;&lt;br /&gt;12. Set and Realize Realistic Goals&lt;br /&gt;Quran: Indeed Allah does not burden a soul with more than what it can handle&lt;br /&gt;&lt;br /&gt;13. Stay Away from Distractions&lt;br /&gt;Quran: Do not even come near fornication&lt;br /&gt;Quran: So flee to Allah&lt;br /&gt;&lt;br /&gt;14. Remember Your Mission in Life:&lt;br /&gt;Quran: I have only created jinn and mankind to worship me&lt;br /&gt;Quran: Is it not that with the rememberance of Allah that hearts have tranquility and content&lt;br /&gt;&lt;br /&gt;15. Remember Life-cycles End:&lt;br /&gt;Hadith: Remember the destroyer of all pleasures (death)&lt;br /&gt;&lt;br /&gt;16. Never Execute Trivial Work:&lt;br /&gt;Hadith: A human's accountability on the day of judgement will not be over until he is asked about four things, from among them is his time and how he utilized it&lt;br /&gt;&lt;br /&gt;17. Forecast Risks:&lt;br /&gt;Quran: Indeed the plotting of Satin is weak&lt;br /&gt;Be vigilant and forecast problems and risks&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;[1] Dan Cohen and John Kotter, "The Heart of Change Field Guide", Harvard Business Press, 2005.&lt;br /&gt;[2] Ayman Nassar, "Implementing Change", Friday Khutbah, Hanover, PA, July 10th, 2009&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-122887464852643663?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/GM2DBLYIXro" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/122887464852643663/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=122887464852643663" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/122887464852643663" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/122887464852643663" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/GM2DBLYIXro/instilling-change-key-component-of.html" title="Instilling Change: A Key Component of Leadership" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/07/instilling-change-key-component-of.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-1157908713889180916</id><published>2009-06-22T08:32:00.003-04:00</published><updated>2009-06-22T08:57:07.516-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="systems engineering" /><category scheme="http://www.blogger.com/atom/ns#" term="Airlines" /><category scheme="http://www.blogger.com/atom/ns#" term="Quality" /><title type="text">The Demise of Quality - My Wife's Friend, British Airways and Air France</title><content type="html">I was vacuuming the living room last evening, when my wife told me that her friend arrived safely in Egypt after a long flight from Washington with a connection in London. She then added that her 10 year old son is walking around in his swimsuit at home and her friend is wearing some old maternity clothes she had from a decade ago. I asked my wife "Did they lost their luggage?", she replied that no a single bag of the eight pieces her friend and her three kids had arrived.&lt;br /&gt;&lt;br /&gt;It has been two days since my wife's friend family had arrived on&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_P1Z4K44RuMU/Sj9_JT65N0I/AAAAAAAAAMs/BzTc9CNrQ4g/s1600-h/Slide1.JPG"&gt;&lt;img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 320px; height: 240px;" src="http://4.bp.blogspot.com/_P1Z4K44RuMU/Sj9_JT65N0I/AAAAAAAAAMs/BzTc9CNrQ4g/s320/Slide1.JPG" alt="" id="BLOGGER_PHOTO_ID_5350134680282281794" border="0" /&gt;&lt;/a&gt; board British Airways with no luggage. I mentioned to my wife that her friend should request a compensation of some sort, may $100 per passenger, so they can use this modest pocket money to go buy some clothes until their bags appear. My wife's response was "we are thankful that they arrived safely". Well, yes of course compared to Air France's latest flight that plunged in the Atlantic, the losses and inconvenience is minimal, and one should always be thankful, regardless of what one goes through". The point however is that the passenger's (customer) expectation is be transported safely along with his luggage from point A to point B. If customer's start changing their expectations, quality will automatically by definition change.&lt;br /&gt;&lt;br /&gt;An attorney would seize the opportunity and ask the passenger to file a suit against the airline asking for some ridiculous amount of money as a compensation for damages. Maybe $1 million dollars per lost bag, or the highest that the court will allow. We have various mindsets of customers when it comes to settling disputes with a service provider. At one extreme a client will say no problem, just get me my bags if you can, when you can. On another extreme another customer will say meet me at court, and then there are infinite of perspectives in between.&lt;br /&gt;&lt;br /&gt;What would you do? What would a good system's engineer do? Share your thoughts in the comments below.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-1157908713889180916?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/tALCPANYSJU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/1157908713889180916/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=1157908713889180916" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1157908713889180916" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1157908713889180916" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/tALCPANYSJU/demise-of-quality-my-wifes-friend.html" title="The Demise of Quality - My Wife's Friend, British Airways and Air France" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_P1Z4K44RuMU/Sj9_JT65N0I/AAAAAAAAAMs/BzTc9CNrQ4g/s72-c/Slide1.JPG" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/06/demise-of-quality-my-wifes-friend.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-4695164971982394283</id><published>2009-06-03T21:00:00.005-04:00</published><updated>2009-07-14T00:45:42.485-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="statistics" /><category scheme="http://www.blogger.com/atom/ns#" term="decision-making" /><title type="text">Probability Distributions for Business Events - Binomial</title><content type="html">System engineers and technical managers need to make decisions based on the probability of certain events occurring. For example during a risk assessment practice, the systems engineering might be calculating the risk value of an event, and based on the value of the risk level the organization will take certain steps to respond to the risk.&lt;br /&gt;&lt;br /&gt;To accurately calculate the risk value which is calculated as the (impact level * probability of occurrence), the probability distribution selected needs to be accurate.&lt;br /&gt;&lt;br /&gt;In some events outcomes could be binary, for example: good or bad, correct or incorrect, successful or failed, conforming or non-conforming. A suitable probability distribution would be a binomial probability distribution, using a binomial calculator the system engineer can calculate the probability of occurrence of one of the two possible events knowing the sample size (n), the rate of good versus bad, or correct versus incorrect (p) and the number of items (x) fitting a particular outcome. For example if we select a sample of six items from a batch which has a defect rate of 3%, we can find the probability that the sample has one defective item using the binomial formula&lt;br /&gt;&lt;br /&gt;P(x) = [n! / x! (n-x)! ] p^x (1-p)^(n-x)&lt;br /&gt;&lt;br /&gt;In the above example, n=6, p=0.03, x=1&lt;br /&gt;&lt;br /&gt;Using the formula above or the &lt;a href="http://www.stat.tamu.edu/%7Ewest/applets/binomialdemo.html"&gt;binomial calculator&lt;/a&gt; available at Texas A&amp;amp;M, we get that P(1) = 0.1546&lt;br /&gt;&lt;br /&gt;Stay tuned for other probability distributions that are also common in business environments.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-4695164971982394283?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/T_JI9CMs8Q4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/4695164971982394283/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=4695164971982394283" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/4695164971982394283" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/4695164971982394283" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/T_JI9CMs8Q4/probability-distributions-for-business.html" title="Probability Distributions for Business Events - Binomial" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/06/probability-distributions-for-business.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-6457451593029879608</id><published>2009-06-01T19:53:00.005-04:00</published><updated>2009-06-12T11:33:45.373-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="statistics" /><category scheme="http://www.blogger.com/atom/ns#" term="systems engineering" /><category scheme="http://www.blogger.com/atom/ns#" term="Project Mgmt" /><title type="text">Two Approaches to Use Statistics on Your Project</title><content type="html">Most people don't like statistics, and most decision-makers make wild guesses when they need to take a decision. Statistics might not be the most straight-forward science during the college years, but it has tremendous value in providing insights and guidance for making rational decisions.&lt;br /&gt;&lt;br /&gt;Using statistics one can show various properties of a set of data such as the mean, mode, median, dispersion and distribution. These parameters can be represented graphically using histograms, charts and other visual illustrations.&lt;br /&gt;&lt;br /&gt;Another approach using statistics is to develop inferences, test hypothesis and develop forecasts through the use of sample data from a bigger population. Relationships between variables can be developed and illustrated using a scatter diagram or a regression equation.&lt;br /&gt;&lt;br /&gt;&lt;script src="http://digg.com/tools/diggthis.js" type="text/javascript"&gt;&lt;/script&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-6457451593029879608?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/RV98-Bl1ZeY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/6457451593029879608/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=6457451593029879608" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/6457451593029879608" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/6457451593029879608" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/RV98-Bl1ZeY/two-approaches-to-use-statistics-on.html" title="Two Approaches to Use Statistics on Your Project" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/06/two-approaches-to-use-statistics-on.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-1161237372957360172</id><published>2009-05-31T11:44:00.006-04:00</published><updated>2009-06-13T08:39:05.899-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="DFSS" /><category scheme="http://www.blogger.com/atom/ns#" term="systems engineering" /><category scheme="http://www.blogger.com/atom/ns#" term="six sigma" /><category scheme="http://www.blogger.com/atom/ns#" term="Processes" /><title type="text">Six Sigma's DMAIC vs. Design for Six Sigma's IDOV / DMADV</title><content type="html">Six sigma's success is mainly contributed to its DMAIC model. The DMAIC model focuses on defining an issue with an existing process or product, measuring the deviation from the expected behavior, analyzing the data for insights to root causes, improve the current process or product through minimization of deviations or improvements and finally controlling the system to sustain the gains achieved.&lt;br /&gt;&lt;br /&gt;IDOV and DMADV which are two design-based models slightly differ from DMAIC as follows.&lt;br /&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 153); font-weight: bold;"&gt;Objective and Approach&lt;/span&gt;: DMAIC views the current process or product as correct and economical, but needs to minimize some gap leading to inefficiencies. IDOV / DMADV view the current process or product as in need of redesign or design change to achieve customer satisfaction.&lt;br /&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 153); font-weight: bold;"&gt;Process Capability&lt;/span&gt;: DMAIC views current process as capable of satisfying customer needs, whereas IDOV / DMADV views current processes as a candidate for improved yield regardless of volume and complexity.&lt;br /&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 153); font-weight: bold;"&gt;Design&lt;/span&gt;: DMAIC views the current design as satisfactory for the client's needs, whereas IDOV / DMADV views the need to consider various drivers for design, such as cost, manufacturing, producibility, maintainability, robustness, usability, efficiency, security, agility, compliance and testability.&lt;br /&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 153); font-weight: bold;"&gt;Flexibility&lt;/span&gt;: DMAIC assumes that the current design and processes are flexible to meet customer demands and needs, whereas IDOV / DMADV highly considers potential customer demands and forecasts newly developed needs&lt;br /&gt;&lt;br /&gt;&lt;span style="color: rgb(0, 0, 153); font-weight: bold;"&gt;Validation&lt;/span&gt;: IDOV and DMADV both consider validation and verification of the outcomes of a design or process in meeting objectives.&lt;br /&gt;&lt;br /&gt;To read more:&lt;br /&gt;[1] Chrisitian Madu, "The House of Quality in a Minute", Chi Publishers, 2006.&lt;br /&gt;[2] Rod Munro, "The Certified Six Sigma Green Belt Handbook", Quality Press, 2008.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-1161237372957360172?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/3qIR2Np2MJI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/1161237372957360172/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=1161237372957360172" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1161237372957360172" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1161237372957360172" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/3qIR2Np2MJI/six-sigmas-dmaic-vs-design-for-six.html" title="Six Sigma's DMAIC vs. Design for Six Sigma's IDOV / DMADV" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/05/six-sigmas-dmaic-vs-design-for-six.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-242533947408760315</id><published>2009-05-20T10:53:00.008-04:00</published><updated>2009-05-20T11:44:36.541-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Agile" /><category scheme="http://www.blogger.com/atom/ns#" term="Processes" /><title type="text">3 Practices to Becoming an Agile and Lean Enterprise</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_P1Z4K44RuMU/ShQlNXd8I8I/AAAAAAAAALE/kX-8oeMBqyk/s1600-h/business-1-1210009578RK4m.jpg"&gt;&lt;img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 320px; height: 214px;" src="http://4.bp.blogspot.com/_P1Z4K44RuMU/ShQlNXd8I8I/AAAAAAAAALE/kX-8oeMBqyk/s320/business-1-1210009578RK4m.jpg" alt="" id="BLOGGER_PHOTO_ID_5337932369908999106" border="0" /&gt;&lt;/a&gt;About a month ago I was approached by a client asking to give advice regarding some organizational changes and major layoffs they were embarking upon. The client sent me an email with about six or seven different options to pursue to cut on their operating expenses.&lt;br /&gt;&lt;br /&gt;I noticed that all the options were focused on eliminating employees. My question to myself, if eliminating employees seems the favorable and only approach that comes to mind, why were these employees present in the first place? There must have been a need for them in the organization, otherwise why were they hired in the first place? What operations will suffer when these folks are let go?&lt;br /&gt;&lt;br /&gt;Many businesses fail to realize that a lot could be done way in advance to avoid shedding off employees. Letting go of your most valuable resources, your staff, should be the last thing to do, before closing shop. I list ten actions that can be done months before the crunch becomes severe to be forced to shut down.&lt;br /&gt;&lt;br /&gt;&lt;span style="color: rgb(51, 51, 255);"&gt;1. Reduce non-valuable activities, a.k.a trivial work. &lt;/span&gt;&lt;br /&gt;Non-valuable activities are those which your customers are not willing to pay for, they do not change the form or function of the product or service they are interested in. An example is rework, due to defects in a process used to produce the end product or service. Other examples are wait-time during the process. For example if you order a book online, you are willing to pay for the book to be shipped from the publisher to your location, you are interested in how much time it takes the book to wait at each regional hub for its next pickup. If there is a cost to the shipper to pay for the time spent at each shipping hub it will increase the cost of your book shipment and will not provide you any value. The only value you realize is the book being shipped to you as fast as possible. Instead of focusing on accelerating valuable processes, one should first eliminate non-valuable processes, as the effort of work will probably be less and the outcomes more effective.&lt;br /&gt;&lt;br /&gt;Muslims also know non-valuable activities as "Lagow", an Arabic term mentioned in the Quran in several places, as deeds that have no benefit, or are a mere waste of time. These are deeds that keeps one's focus away from his purpose in life, which is the success in the hereafter.&lt;br /&gt;&lt;br /&gt;Before improving valuable processes, it is important to get rid of as many non-valuable processes as possible. In the case of my client, they were focussing on products that yielded low profit margins, were difficult to market, promote and sell, and required large staffing and overhead.&lt;br /&gt;&lt;br /&gt;&lt;span style="color: rgb(51, 51, 255);"&gt;2. Reduce waste&lt;/span&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_P1Z4K44RuMU/ShQk4VvYJII/AAAAAAAAAK8/3CI9xYRBdw0/s1600-h/overprod+CD-1-1208707554nqU5.jpg"&gt;&lt;img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 316px; height: 212px;" src="http://4.bp.blogspot.com/_P1Z4K44RuMU/ShQk4VvYJII/AAAAAAAAAK8/3CI9xYRBdw0/s320/overprod+CD-1-1208707554nqU5.jpg" alt="" id="BLOGGER_PHOTO_ID_5337932008668013698" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Waste is all around us in our activities. It is imperative that before we develop new processes to improve deficiencies we actually reduce waste as much as possible. Waste could be due to over production, excessive steps due to complexities of processes, queuing and idle time, defect correction and rework, poor organizational and planning processes, lack of controls and creativity stagnation.&lt;br /&gt;&lt;br /&gt;Through some auditing and analysis it was found that my client had opportunities to reduce expenses of photocopying, utilities, rent and other non-valuable activities prior to let go of employees who were driving valuable activities for the end user.&lt;br /&gt;&lt;br /&gt;&lt;span style="color: rgb(51, 51, 255);"&gt;3. Use facilitation to reduce cycle time and enhance efficiencies&lt;/span&gt;&lt;br /&gt;A facilitator who is neutral to the different entities in your enterprise, and who has no authority or decision-making control, can bring tremendous value to your organization. The facilitator can apply collaboration concepts, systemic approaches and architectural thinking to decompose problems, address impacts in all areas of interest, and ensure a collaborative environment exists where the various team members can share ideas, brainstorm and foster creativity.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-242533947408760315?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/BEEBjKq35mA" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/242533947408760315/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=242533947408760315" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/242533947408760315" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/242533947408760315" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/BEEBjKq35mA/3-practices-to-becoming-agile-and-lean.html" title="3 Practices to Becoming an Agile and Lean Enterprise" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_P1Z4K44RuMU/ShQlNXd8I8I/AAAAAAAAALE/kX-8oeMBqyk/s72-c/business-1-1210009578RK4m.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/05/3-practices-to-becoming-agile-and-lean.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-5902797474133442529</id><published>2009-05-18T23:17:00.006-04:00</published><updated>2009-08-13T11:01:21.049-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Failed Projects" /><category scheme="http://www.blogger.com/atom/ns#" term="Processes" /><title type="text">Controling Many Small Changes: Taming the Culprit for Most Accidents or Failures</title><content type="html">As changes creep upon our processes, methods and systems; we accumulate little bits of inefficiencies which eventually become large and cripple the system.&lt;br /&gt;&lt;br /&gt;Six Sigma helps ensure continuous improvement, through the use o&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_P1Z4K44RuMU/SiAC_zY-6MI/AAAAAAAAAMI/ka3ysrxvROA/s1600-h/nile+delta.jpg"&gt;&lt;img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 320px; height: 129px;" src="http://4.bp.blogspot.com/_P1Z4K44RuMU/SiAC_zY-6MI/AAAAAAAAAMI/ka3ysrxvROA/s320/nile+delta.jpg" alt="" id="BLOGGER_PHOTO_ID_5341272453211416770" border="0" /&gt;&lt;/a&gt;f data collection to analyze and understand how a process works or changes. The focus in this case is to reduce variations to processes or design ultimately leading to less defects. Common approaches to identify these variations or deltas is through the voice of the customer (VOC), quality function deployment (QFD), failure mode effect analysis (FMEA) among many others.&lt;br /&gt;&lt;br /&gt;Lean improvement approaches can also help address change creep consequences. The focus in this case is more on waste minimization and elimination. Common approaches are value stream analysis, the five S, Kaizen events, just in time, work standardization and error proofing.&lt;br /&gt;&lt;br /&gt;__________________________&lt;br /&gt;&lt;br /&gt;Picture: The Nile Delta in Northern Egypt. Image depicts delta erosion.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-5902797474133442529?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/QWmx46cjQ80" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/5902797474133442529/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=5902797474133442529" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/5902797474133442529" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/5902797474133442529" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/QWmx46cjQ80/many-small-changes-culprit-for-most.html" title="Controling Many Small Changes: Taming the Culprit for Most Accidents or Failures" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_P1Z4K44RuMU/SiAC_zY-6MI/AAAAAAAAAMI/ka3ysrxvROA/s72-c/nile+delta.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/05/many-small-changes-culprit-for-most.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-5720549096231304496</id><published>2009-05-18T18:31:00.008-04:00</published><updated>2009-05-18T20:35:50.327-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Feedback" /><category scheme="http://www.blogger.com/atom/ns#" term="Processes" /><title type="text">Feedback: A Core Component of a Successful Process</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_P1Z4K44RuMU/ShHnTjxlw8I/AAAAAAAAAKc/bi7YW5tYBUM/s1600-h/watercycle.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 312px; height: 234px;" src="http://3.bp.blogspot.com/_P1Z4K44RuMU/ShHnTjxlw8I/AAAAAAAAAKc/bi7YW5tYBUM/s320/watercycle.jpg" alt="" id="BLOGGER_PHOTO_ID_5337301356617515970" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Processes comprise of a functions which operate on inputs to produce outputs. Data associated with the inputs and outputs can be used to further enhance the process quality. The data related to the process outputs could include important elements that when fed back to the input within a solid analytical framework could offer valuable insights and impacts on the process improvement.&lt;br /&gt;&lt;br /&gt;Several key steps in designing the appropriate data collection, analysis and feedback system are summarized below:&lt;br /&gt;&lt;br /&gt;1. &lt;span style="color: rgb(0, 0, 153);"&gt;Decide where to collect the data&lt;/span&gt;&lt;br /&gt;Data can be collected at the input, various processing points, decision-points, at the output or any combination of all of these locations.&lt;br /&gt;&lt;br /&gt;2. &lt;span style="color: rgb(0, 0, 153);"&gt;Decide what measurement systems to use&lt;/span&gt;&lt;br /&gt;Various techniques exist to collect and measure data. Decisions need to be made on best statistical approaches, summarization techniques, collection methods and the levels of accuracy and precision needed.&lt;br /&gt;&lt;br /&gt;3. &lt;span style="color: rgb(0, 0, 153);"&gt;Decide how to analyze the data&lt;/span&gt;&lt;br /&gt;Approaches of data analysis need to be determined. It is important to determine cause and effects, root causes, correlation, regression dependencies and other relationships among the various variables and factors.&lt;br /&gt;&lt;br /&gt;4. &lt;span style="color: rgb(0, 0, 153);"&gt;Decide on how to use the information resulting from the data analysis&lt;/span&gt;&lt;br /&gt;Decisions related to the application of the information learned is important. For example will information be applied in real-time, or after process reengineering is brainstormed.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-5720549096231304496?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/tEyA7DbPGwk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/5720549096231304496/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=5720549096231304496" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/5720549096231304496" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/5720549096231304496" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/tEyA7DbPGwk/feedback-as-core-component-of.html" title="Feedback: A Core Component of a Successful Process" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/_P1Z4K44RuMU/ShHnTjxlw8I/AAAAAAAAAKc/bi7YW5tYBUM/s72-c/watercycle.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/05/feedback-as-core-component-of.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-1207842718324714295</id><published>2009-05-18T09:22:00.004-04:00</published><updated>2009-05-18T09:56:04.285-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="New Product Development" /><category scheme="http://www.blogger.com/atom/ns#" term="Project Mgmt" /><category scheme="http://www.blogger.com/atom/ns#" term="Cool Systems" /><title type="text">The Cruiseterminal - The World's Floating Dock</title><content type="html">Even by Dubai's standards the Cruiseterminal is an extravagant project. Rigged to a foundation in the Persian Gulf it can host three of the largest cruise ships. Its an integrated system comprising of its own photovoltaic electricity generation subsystem, an entertainment and retail subsystem, a 180 room lodging subsystem, docks for tens of smaller boats.&lt;br /&gt;&lt;br /&gt;A system such as the cruiseterminal brings new challenges not only to system design and development, but also system operations, support and maintainability.&lt;br /&gt;&lt;br /&gt;To check pictures of the Dubai floating Cruiseterminal among other structures, check De51gn at &lt;a href="http://de51gn.com/design/the-floating-world-of-koen-olthuis/"&gt;http://de51gn.com/design/the-floating-world-of-koen-olthuis/&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-1207842718324714295?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/pwDB703LRdY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/1207842718324714295/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=1207842718324714295" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1207842718324714295" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1207842718324714295" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/pwDB703LRdY/cruiseterminal-worlds-floating-dock.html" title="The Cruiseterminal - The World's Floating Dock" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/05/cruiseterminal-worlds-floating-dock.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-1397075447245944329</id><published>2009-04-29T10:02:00.012-04:00</published><updated>2009-05-31T11:00:37.861-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="islam" /><category scheme="http://www.blogger.com/atom/ns#" term="systems engineering" /><category scheme="http://www.blogger.com/atom/ns#" term="Constraints" /><category scheme="http://www.blogger.com/atom/ns#" term="islamic financing" /><title type="text">Using the Theory of Constraints &amp; Six Sigma to Fix Critical Components of the Economy</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_P1Z4K44RuMU/SfhjcP6jyOI/AAAAAAAAAJ8/JRUis3kl0eE/s1600-h/TOC.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 320px; height: 240px;" src="http://2.bp.blogspot.com/_P1Z4K44RuMU/SfhjcP6jyOI/AAAAAAAAAJ8/JRUis3kl0eE/s320/TOC.jpg" alt="" id="BLOGGER_PHOTO_ID_5330119495952615650" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Constraints are all around us. The theory of constraints is a lean problem-solving concept based on a simple concept, that a process can not move faster than the slowest part of the process.&lt;br /&gt;&lt;br /&gt;Our economy as a complex enclosed system has constraints and it will respond to stimulus as quick as the slowest link in the economy. The chart on the left illustrates some major components of the economy. They all need to be improved for the stimulus to realize benefits, otherwise it will be a temporary patch.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The root of the problem lies in three areas:&lt;br /&gt;&lt;br /&gt;1. The concept of printing money and the process followed to release cash into the market. The &lt;a href="http://www.federalreserve.gov/"&gt;Federal Reserve Bank&lt;/a&gt; - which is not a government entity - is provided the authority to distribute the nation's currency and supervise banks which are members in the system. When the US releases currency into the market it requests the Federal Reserve Bank to print dollar bills in return for an interest payment on the amount. No real assets are provided as collateral to backup the value of the printed currency. The value of the currency is only backed up by the reputation and promise of the US government to accept the currency as a form of payment.  As users of the currency lose faith in the governments ability to keep the promise the value can drop significantly. One reason for the poor confidence in the currency, is the automatic depreciation of the currency the day it was printed. For every US dollar printed a small percentage is due to the Federal Reserve Bank as interest on that printed dollar, in a sense every dollar released into the market is really worth 0.98 of a dollar, if we assume an interest rate of 2%. Add onto this, the fact that the US government is running into a non-stop deficit in social security, and other areas leading to increase in bond issuing to countries such as China and India, further diminishing the value of the US currency.&lt;br /&gt;&lt;br /&gt;2. Interest rate or usury is another problem in the overall system. The fact that currency value depreciates today based on some future value determined by an interest rate automatically leads to inflation, and future depreciation of natural resources. Charging interest is like pumping steroids into a body builder, eventually at some point the body will collapse.&lt;br /&gt;&lt;br /&gt;3. Selling what we don't own. The idea that goods and services can be sold without actually owning them creates a virtual commodity system, not backed up by real commodities or assets.&lt;br /&gt;&lt;br /&gt;Unless these areas are fixed no stimulus package can work on the long term. Some simple steps to address this issue are:&lt;br /&gt;&lt;br /&gt;a. Identify the constraints of the financial and monetary systems&lt;br /&gt;b. Exploit the constraint or re-engineer&lt;br /&gt;c. Subordinate other steps in the overall process to the improved constraint&lt;br /&gt;d. Revise the constraint if it has not been eliminated by steps b and c&lt;br /&gt;e. Repeat the steps above for other constraints&lt;br /&gt;&lt;br /&gt;Applying this into practice can be as follows:&lt;br /&gt;&lt;br /&gt;a. Identify the constraints of the financial and monetary systems&lt;br /&gt;- Currency not backed by a true tangible asset (some natural resource like gold or silver)&lt;br /&gt;- Currency being depreciated the day it is printed, solely due to interest&lt;br /&gt;- Distribution and sale of products that do not exist (example lending money to a business when the bank does not have the exact cash reserved, selling a commodity that one does not own and has not yet paid for)&lt;br /&gt;- Using interest rates to discount projects, assets and commodities to a future value, leading to valueless future assets, commodities, natural resources&lt;br /&gt;&lt;br /&gt;b. Exploit the constraint or re-engineer&lt;br /&gt;- Re-engineer the monetary system that issues a currency based on a true asset and not just a promise&lt;br /&gt;- Re-engineer the concept of future valuation&lt;br /&gt;- Re-engineer the concept of wealth circulation&lt;br /&gt;&lt;br /&gt;c. Subordinate other steps in the overall process to the improved constraint&lt;br /&gt;- Use a sustainable natural resource to backup the value of an issued currency&lt;br /&gt;- Use  joint partnerships, gifting (0% loans) and entrepreneurship, moving away from interest bearing loans of money that is not owned by lenders.&lt;br /&gt;- Base future valuation on true-value (value proposition) provided to global society rather than a discounted interest rate.&lt;br /&gt;&lt;br /&gt;d. Revise the constraint if it has not been eliminated by steps b and c&lt;br /&gt;e. Repeat the steps above for other constraints&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-1397075447245944329?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/KQXQ0jUubUY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/1397075447245944329/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=1397075447245944329" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1397075447245944329" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1397075447245944329" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/KQXQ0jUubUY/using-theory-of-constraints-six-sigma.html" title="Using the Theory of Constraints &amp; Six Sigma to Fix Critical Components of the Economy" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_P1Z4K44RuMU/SfhjcP6jyOI/AAAAAAAAAJ8/JRUis3kl0eE/s72-c/TOC.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/04/using-theory-of-constraints-six-sigma.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-4187629725624640572</id><published>2009-04-27T14:59:00.010-04:00</published><updated>2009-04-27T15:10:08.980-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="system engineer" /><category scheme="http://www.blogger.com/atom/ns#" term="New Product Development" /><category scheme="http://www.blogger.com/atom/ns#" term="Failed Projects" /><title type="text">One Way to Ruin a Great Product Idea - When Design and Implementation Miss</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_P1Z4K44RuMU/SfYDBraLSGI/AAAAAAAAAJ0/786W4tiCzo8/s1600-h/driveway2.jpg"&gt;&lt;img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 320px; height: 267px;" src="http://2.bp.blogspot.com/_P1Z4K44RuMU/SfYDBraLSGI/AAAAAAAAAJ0/786W4tiCzo8/s320/driveway2.jpg" alt="" id="BLOGGER_PHOTO_ID_5329450536406829154" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_P1Z4K44RuMU/SfYCjvErmqI/AAAAAAAAAJs/GXzeVjdvwFs/s1600-h/escalator.jpg"&gt;&lt;img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 231px; height: 308px;" src="http://2.bp.blogspot.com/_P1Z4K44RuMU/SfYCjvErmqI/AAAAAAAAAJs/GXzeVjdvwFs/s320/escalator.jpg" alt="" id="BLOGGER_PHOTO_ID_5329450021994338978" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_P1Z4K44RuMU/SfYCJSzTizI/AAAAAAAAAJM/-5HhUTyf0OE/s1600-h/atm.jpg"&gt;&lt;img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 242px; height: 320px;" src="http://1.bp.blogspot.com/_P1Z4K44RuMU/SfYCJSzTizI/AAAAAAAAAJM/-5HhUTyf0OE/s320/atm.jpg" alt="" id="BLOGGER_PHOTO_ID_5329449567728667442" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;A friend of mine sent me some interesting pictures for projects that might have seemed successful on paper, when in implementation they failed. This is where a systems engineer comes in handy, in cases like these.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_P1Z4K44RuMU/SfYCN3SpcCI/AAAAAAAAAJU/xZkDcuNcGmM/s1600-h/lamp.jpg"&gt;&lt;img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 175px; height: 320px;" src="http://1.bp.blogspot.com/_P1Z4K44RuMU/SfYCN3SpcCI/AAAAAAAAAJU/xZkDcuNcGmM/s320/lamp.jpg" alt="" id="BLOGGER_PHOTO_ID_5329449646243278882" border="0" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-4187629725624640572?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/3rUxMJUNC_M" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/4187629725624640572/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=4187629725624640572" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/4187629725624640572" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/4187629725624640572" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/3rUxMJUNC_M/one-way-to-ruin-great-product-idea-when.html" title="One Way to Ruin a Great Product Idea - When Design and Implementation Miss" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_P1Z4K44RuMU/SfYDBraLSGI/AAAAAAAAAJ0/786W4tiCzo8/s72-c/driveway2.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/04/one-way-to-ruin-great-product-idea-when.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-8121009262011795549</id><published>2009-04-18T14:45:00.005-04:00</published><updated>2009-05-12T09:02:09.551-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="islam" /><category scheme="http://www.blogger.com/atom/ns#" term="Economic Systems" /><category scheme="http://www.blogger.com/atom/ns#" term="islamic financing" /><title type="text">A Financing System for Prosperity, Growth and Social Justice</title><content type="html">My dear friend Mohamed El Habashy sent me a link to an &lt;a href="http://www.pbs.org/wnet/religionandethics/episodes/april-10-2009/islamic-financing/2629/"&gt;interview&lt;/a&gt; that he was part of on &lt;a href="http://www.pbs.org/"&gt;PBS&lt;/a&gt;. He was one of several experts interviewed on hot topic of Islamic financing. It seems that the World suddenly woke up to realize that a system that was revealed to mankind some 1430 years ago is now all the sudden a good choice.&lt;br /&gt;&lt;br /&gt;&lt;p&gt;The Islamic financing system is based on one of three main models:&lt;/p&gt;- Mosharaka (joint ownership through stocks, capital partnerships)&lt;br /&gt;- Qard Hasan (good lending, a loan with no interest (0%) regardless of amount and maturity date)&lt;br /&gt;- Mudaraba (entrepreneurship or partnership with effort and experience)&lt;br /&gt;&lt;br /&gt;Several key concepts in Islamic financing are&lt;br /&gt;&lt;p&gt;1. Joint sharing in risk and reward (property/asset price increase and decrease) - is part of the definition of ownership in Islam, and it provides responsibility and fairness to all parties. &lt;/p&gt; &lt;p&gt;2. The concept of selling money (lending with interest) is prohibited. In Islam lending money as a form of investment is prohibited and not in compliance with the Islamic Shariyah.&lt;br /&gt;&lt;/p&gt; &lt;p&gt;3. Sales are only acceptable on items owned. This means someone can not sell an item (product, service, shares, commodity, etc..) unless he has paid for it in full and has full control on it. In Islam a person selling stocks that he never paid for is prohibited and not in compliance with the Shariyah.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt; &lt;p&gt;As of today there are no 100% Islamic compliant financing vehicles in the US, the efforts mentioned above in the PBS article are good and trying to strive to get close to the fair and just Islamic financing. However due to regulations and other factors there are some gaps, such as the joint risk sharing in a partnership model. Islamic financing has been around for 1430 years from the days of Prophet Mohamed and it is implemented in many parts of the World (UK Links: &lt;a href="http://www.islamic-banking.com/"&gt;1&lt;/a&gt;, &lt;a href="http://news.bbc.co.uk/2/hi/business/6483343.stm"&gt;2&lt;/a&gt;, &lt;a href="http://news.bbc.co.uk/2/hi/uk_news/7677181.stm"&gt;3&lt;/a&gt;, &lt;a href="http://news.bbc.co.uk/2/hi/business/8025410.stm"&gt;4&lt;/a&gt;, &lt;a href="http://news.bbc.co.uk/2/hi/business/6168800.stm"&gt;5&lt;/a&gt;)  we in the US are just behind. There is a &lt;a href="http://www.universityislamicfinancial.com/"&gt;US institution&lt;/a&gt; that has started offering some Islamic vehicles.&lt;br /&gt;&lt;/p&gt; &lt;p&gt;There is no question that Islamic financing is fair, just and solid, providing fair social rewards to all parties involved, unlike other means of financing. Islamic financing can be used by non-Muslims as well whether they decide to fund or use the system.&lt;br /&gt;&lt;/p&gt; &lt;p&gt;Usury/interest was prohibited not only in the Quran, but Jesus and Moses were ordered to tell the people to not engage in usury. (proverbs 28:8, Ezekiel 18:8, Exodus 22:25)&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-8121009262011795549?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/Y0L0htMjSP0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/8121009262011795549/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=8121009262011795549" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/8121009262011795549" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/8121009262011795549" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/Y0L0htMjSP0/financing-system-for-prosperity-growth.html" title="A Financing System for Prosperity, Growth and Social Justice" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/04/financing-system-for-prosperity-growth.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-1154203919267991809</id><published>2009-04-17T15:47:00.004-04:00</published><updated>2009-04-17T16:20:23.037-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="System Boundary" /><category scheme="http://www.blogger.com/atom/ns#" term="system attribute" /><category scheme="http://www.blogger.com/atom/ns#" term="Cool Systems" /><title type="text">Finally America Might See a High Speed Rail System</title><content type="html">It's not about time that America gets a high speed rail. It is way past due. Japan had one for decades, and Europe has been there, did that ages ago.&lt;br /&gt;&lt;br /&gt;These days there are discussions about two impressive high rail initiatives worth mentioning. In the West Obama is pushing for $13 billion ($30 billion total cost) high speed rail system (links &lt;a href="http://www.latimes.com/news/nationworld/nation/la-na-highspeed-rail17-2009apr17,0,7332059.story"&gt;1&lt;/a&gt;, 2, 3) in California and the heart of America's Mid-West, Chicago, my favorite city. In the East King Abdullah is launching a high speed &lt;a href="http://www.saudirailexpansion.com/SaudiRailExpansion/default.aspx"&gt;rail route&lt;/a&gt; between Makkah and Madinah.&lt;br /&gt;&lt;br /&gt;Wikipedia has compiled a &lt;a href="http://en.wikipedia.org/wiki/Planned_high-speed_rail_by_country"&gt;list of high speed rail projects&lt;/a&gt; across the globe. The Saudi project is impressive as it has the least cost / mile worldwide. The American is impressive because it is the first in the Western Hemisphere and second fastest worldwide reaching a little over 150 miles / hr.&lt;br /&gt;&lt;br /&gt;Now here is the big project. China's high speed rail, the longest worldwide reaching over 800 miles and exceeding the American train speed. A really neat chart showing the world's top high speed projects can be found at &lt;a href="http://www.infrastructurist.com/2009/04/06/chart-comparing-new-hs-projects-around-the-world/"&gt;infrastructurist.com&lt;/a&gt; by Yonah Freemark.&lt;br /&gt;&lt;br /&gt;So the questions that pop up are: Why did it take America too long to initiate such a project? Will it be a success or another &lt;a href="http://www.amtrak.com/servlet/ContentServer?pagename=Amtrak/am2Route/Vertical_Route_Page&amp;amp;cid=1080772074490"&gt;Acela&lt;/a&gt; (links &lt;a href="http://www.amtrak.com/servlet/ContentServer?pagename=Amtrak/am2Route/Vertical_Route_Page&amp;amp;cid=1080772074490"&gt;1&lt;/a&gt;, &lt;a href="http://www.railway-technology.com/projects/amtrak/"&gt;2&lt;/a&gt;).  Successful system development is contigent on many factors some of the critical ones are policies, supporting infrastructure, overall cost, stakeholder value proposition.&lt;br /&gt;&lt;br /&gt;So why do I consider Acela a failure ( &lt;a href="http://www.fff.org/freedom/fd0511g.asp"&gt;1&lt;/a&gt;, 2)? Well, for one it was a very expensive system, secondly, it did not take away much volume from other modes of transportation. If it takes me an hr to drive from my home to get to an Acela station in Washington DC so that I can get to New York City in a couple of hrs, I might be better off driving up to New York in 2.5 hrs and pay less in gas and have the convienence of my own transportation in all the other pockets of cities and suburbs that lack public transportation. Just one of many aspects of the overall system that needs to be considered.&lt;br /&gt;&lt;br /&gt;The boundary of a high speed rail system does NOT stop at the tracks, it goes beyond the tracks and stations to the supporting infrastructure that will allow people to get to the high speed stations, use the facilities and services within the service levels and value proposition a stakeholder will expect.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-1154203919267991809?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/BkAD_vTKnao" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/1154203919267991809/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=1154203919267991809" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1154203919267991809" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1154203919267991809" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/BkAD_vTKnao/finally-america-might-see-high-speed.html" title="Finally America Might See a High Speed Rail System" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/04/finally-america-might-see-high-speed.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-1572631448771682677</id><published>2009-04-16T17:26:00.009-04:00</published><updated>2009-05-13T17:39:13.143-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Project Mgmt" /><category scheme="http://www.blogger.com/atom/ns#" term="PMP" /><title type="text">New PMP Practice Book Released Today</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_P1Z4K44RuMU/Sej4SDkz2TI/AAAAAAAAAI8/SREUMIRnUQ0/s1600-h/Book_Cover-Web-239x350.jpg"&gt;&lt;img style="margin: 0pt 0pt 10px 10px; float: right; cursor: pointer; width: 239px; height: 350px;" src="http://2.bp.blogspot.com/_P1Z4K44RuMU/Sej4SDkz2TI/AAAAAAAAAI8/SREUMIRnUQ0/s400/Book_Cover-Web-239x350.jpg" alt="" id="BLOGGER_PHOTO_ID_5325779548446644530" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I just received a proof copy of my new PMP practice book today. The book is a great tool for those who prefer the self-study route. It comprises of 15 chapters covering the concepts of project management, a project's life cycle phases, process groups and project domain areas (scope, schedule, cost, risk, communications, risk, procurement, quality, human resources and integration). It also includes a chapter on professional responsibility, and a chapter with extra 130+ questions. The whole book offers over 420 practice questions very similar to the exam. The book is not a study guide (it does not have content to study, just problems to practice), it does have a chapter on how to prepare for the exam and various tips ranging from "how to get to the test center" to "how to respond to questions"&lt;br /&gt;&lt;br /&gt;It can be purchased online from &lt;a href="https://www.createspace.com/3380201"&gt;https://www.createspace.com/3380201&lt;/a&gt; or from &lt;a href="http://www.amazon.com/"&gt;Amazon.com&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-1572631448771682677?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/fhrJ89NlQtg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/1572631448771682677/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=1572631448771682677" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1572631448771682677" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1572631448771682677" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/fhrJ89NlQtg/new-pmp-practice-book-released-today.html" title="New PMP Practice Book Released Today" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_P1Z4K44RuMU/Sej4SDkz2TI/AAAAAAAAAI8/SREUMIRnUQ0/s72-c/Book_Cover-Web-239x350.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/04/new-pmp-practice-book-released-today.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-235353849879971740</id><published>2009-04-15T11:41:00.003-04:00</published><updated>2009-04-15T11:48:10.751-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Tools" /><category scheme="http://www.blogger.com/atom/ns#" term="Project Mgmt" /><title type="text">Tools Alone Produce Fools</title><content type="html">Managing a project or defining a complex system requires the knowledge and skills of appropriate methodologies and processes to realize the objectives. An individual who only knows how to use a project management tool (see selected list of tools in the sidebar), but lacks the understanding of the iterative and progressive nature of projects and how to manage the different processes within each phase will not be able to lead a successful project.&lt;br /&gt;&lt;br /&gt;There is a big difference between developing a schedule that works and a schedule that looks good in a tool. Expert project managers need nothing more than a pencil and sheet of paper to lead a project. Tools help automate calculations and enable updates and corrections easily, allow tracking of changes and ensure a controlled environment that is agile and flexible. Tools do not defie methodologies, approaches, strategies, or plans. Tools do not execute, monitor or control and tools do not communicate, coach, inspire, motivate and collaborate. Only project managers do.&lt;br /&gt;&lt;br /&gt;Are your pencils sharpened?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-235353849879971740?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/0WZrzEccops" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/235353849879971740/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=235353849879971740" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/235353849879971740" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/235353849879971740" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/0WZrzEccops/tools-alone-produce-fools.html" title="Tools Alone Produce Fools" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/04/tools-alone-produce-fools.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-34916570.post-1663821878355394821</id><published>2009-04-03T08:26:00.004-04:00</published><updated>2009-04-03T08:43:42.183-04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="management" /><title type="text">High Availability Systems Failure</title><content type="html">&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_P1Z4K44RuMU/SdYEeZhH9oI/AAAAAAAAAIk/tmgCo5i0fjE/s1600-h/complex+network.jpg"&gt;&lt;img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 124px; height: 93px;" src="http://1.bp.blogspot.com/_P1Z4K44RuMU/SdYEeZhH9oI/AAAAAAAAAIk/tmgCo5i0fjE/s200/complex+network.jpg" alt="" id="BLOGGER_PHOTO_ID_5320444930077226626" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Does your business require availability capabilities? In today's complex business landscape and the demand for high accountability and transparency, high availability becomes a basic requirement in operations, information access and decision-making.&lt;br /&gt;&lt;br /&gt;Interestingly most high availability environments that fail are unable to deliver the expected results no because of technology immaturity, but mostly due to poor management and oversight. A publicly known example is the &lt;a href="http://www.dallasnews.com/sharedcontent/dws/dn/latestnews/stories/102908dntextechnology.158eb68f0.html"&gt;State of Texas data loss&lt;/a&gt; as a result of invalid checks and balances and inappropriate technical management. In this particular case according to the article in the &lt;a href="http://www.dallasnews.com/sharedcontent/dws/news/texassouthwest/stories/DN-computers_15tex.ART.State.Edition1.4a351d8.html"&gt;Dallas Morning News&lt;/a&gt; &lt;span class="vitstorybody"&gt;&lt;span class="vitstorybody"&gt;IBM has been fined $5.4 million. Of that, $2.7 million was for failing to resolve problems quickly and $1.2 million was for server outages. Data backup breaches, missed mail deadlines and taking more than 15 minutes to respond to serious incidents accounted for the rest, according to department records released this week.&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Next time you implement a high availability solution, do not get fooled by the latest server technology, data backup system or disaster recovery tools. A high availability technology with a staff member who can not use it makes it useless.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/34916570-1663821878355394821?l=sys-eng.blogspot.com'/&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~4/foHyAhH8IkE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://sys-eng.blogspot.com/feeds/1663821878355394821/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=34916570&amp;postID=1663821878355394821" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1663821878355394821" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/34916570/posts/default/1663821878355394821" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Reflections-ProjectAndSystemsEngineeringArchitectureManagementAndLeadership/~3/foHyAhH8IkE/high-availability-systems-failure.html" title="High Availability Systems Failure" /><author><name>Ayman Nassar</name><uri>http://www.blogger.com/profile/09380153517319452000</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="10424429043793430595" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/_P1Z4K44RuMU/SdYEeZhH9oI/AAAAAAAAAIk/tmgCo5i0fjE/s72-c/complex+network.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://sys-eng.blogspot.com/2009/04/high-availability-systems-failure.html</feedburner:origLink></entry></feed>
