Joomla! site syndication http://www.kmglobe.com 2010-09-07T07:48:49+01:00 http://www.kmglobe.com http://www.kmglobe.com/images/M_images/joomla_rss.png text/html 2004-06-12T11:54:06+01:00 http://www.kmglobe.com http://www.kmglobe.com/index.php?option=com_content&task=view&id=1&Itemid=9 The Knowledge Maps are a topology of patterns that are driven by the Software Stability Concepts approach (Fayad, 2002a, 2002b; Fayad Altman, 2001). They consist of knowledge core sets or stable patterns that host the pertinent features and functionality of a particular domain. Furthermore, they can be utilized to build other foundations sets or topologies of patterns of additional domains. Building Knowledge Maps for a determined discipline involves numerous skills, knowledge and steps beyond the identification of tangible artifacts bound to a specific context of applicability. It requires systematic capture and full understanding of the domain where our solution would be deployed and expanded. This includes describing the problem not from its tangible side, but focusing more on its conceptual side, describing underlying affairs with respect to the problem, and using the elements required to fulfill them. The Knowledge Maps’ ultimate representation is driven by the significant mantra “divide and conquer,” which is applied throughout the Knowledge Maps’ structure. For instance, the Knowledge Maps are product of partitioning a domain into different levels of granularity so that we can manage each level with ease. In addition to this, the Knowledge Maps are stratified into five main concerns: analysis concerns (called goals), design concerns (called capabilities), knowledge concerns (goals and capabilities together), development concerns (called development scenarios), and deployment concerns (called deployment scenarios). The relationship between these concerns is represented using the Software Stability Concepts approach’s three layers: EBTs, BOs, and IOs.