The Searching Analysis PatternABSTRACTIntroduction: Stability BackgroundExtracting Patterns Using Software Stability ConceptsProblemContextForcesSolution and Pattern StructureCRC-CardsConsequences2-Easy to Extend. As searching pattern provide the nucleus of any searching, it is expected that any application that will use this pattern will need to add on the top of it to build the required system. One of the main features of the searching patternCase Study 1: Searching the newspaper for a jobApplicabilityExample 1CaseExample 2ConclusionReferencesAnyMedia PatternProblemContextSolution and ParticipantsProblemContextSolution and ParticipantsTHE SEARCHING ANALYSIS PATTERNS THE SEARCHING ANALYSIS PATTERN Mohamed E. Fayad1, Haitham Hamza2, and Valerie Stanton3 1, 3Computer Engineering Dept., College of Engineering, San José State University One Washington Square, San José, CA 95192-0180 Ph: +1 408 924-7364, Fax: +1 408 924-4153 [email protected], [email protected] 2Computer Science and Engineering Dept., University of Nebraska-Lincoln Lincoln, NE 68588, USA Ph: +1 402 4729492 [email protected] ABSTRACT This paper introduces the Searching analysis pattern. The pattern presents an abstract model that analyzes the core concept of the searching independent of a specific application. This pattern has been developed based on the concepts of Stable Analysis Patterns we introduced in [1, and 7]. Stable analysis patterns are built based on the concepts of software stability introduced in [4, 5, and 6]. The paper provides detailed documentation of the proposed searching pattern. Introduction: Stability Background A SSM can be partitioned into three different levels: Enduring Business Themes (EBTs), Business Objects (BOs), and Industrial Objects (IOs). EBTs represent intangible objects that remain stable internally and externally. BOs are objects that are internally adaptable but externally stable, and IOs are the external interface of the system [4 & 5]. In addition to the conceptual differences between EBTs and BOs, a BO can be distinguished from an EBT by tangibility. While EBTs are completely intangible concepts, BOs are partially tangible. These artifacts develop a hierarchal order for the system objects, from totally stable at the EBTs level to unstable at the IOs level, through adaptable though stable at the BOs level. The stable objects of the system are those that do not change over time. Some common-core systems may look different, but in fact, the only differences lay on the surface (i.e. IOs). If they have a common internal structure, why should we deal with them differently? It suffices to develop one system for all of these similar applications to be extracted from. At this point, the importance of SSMs becomes apparent. The more the systems share, the less will need to be changed. Changes will be made to the IOs, the EBTs and BOs need not be touched. Therefore, the EBTs and BOs can be reused among those applications. Figure 1 shows the Stable Models Architecture. The EBTs represent the nucleus of the model, while the IOs represent the surface of the system. The BOs lay in between. Intuitively, the further objects are placed from the interface the more stable and reusable they will be. As a result, common-core applications share the inner layers (i.e. EBTs and BOs), and differ at the outer layer.THE SEARCHING ANALYSIS PATTERNS Figure 1. SSM layers layout Stable Base System Core Knowledge- EBTs Layer Concrete Objects- BOs Layer EXTRACTING PATTERNS USING SOFTWARE STABILITY CONCEPTS Applications that share the same domain have some similarities in their models. For instance, renting applications have core aspects that are common and independent of the nature of the rented item. Therefore, capturing these core aspects in a single model can be beneficial for developing different renting applications without starting from scratch. As mapping to software stability concepts, the model that captures the common aspects of some applications is a model that combines both the EBTs and the BOs of these applications. The resultant sub-model, which combines the EBTs and BOs of the applications, forms a stable pattern for these applications. To obtain stable domain-neutral patterns from the stability model of one problem, we need to obtain a second level of abstraction for each EBT and BO in the problem stability model. This second level of abstraction is obtained by modeling each EBT and BO using stability concepts. The result is that we will have built a stable model for each EBT and BO in the problem. Each new stable model will stand as a pattern by itself. This pattern is focused on a specific problem and can be reused to model this problem in any context, therefore, it is considered to be a domain-neutral pattern. Stable domain-neutral patterns resulting from modeling each EBT and BO can be further classified into stable analysis pattern [6,7, and 8] and stable design pattern, respectively. For instance, a concept such as Satisfaction, which is an EBT, is a general concept that can be found in wide range of applications that span different domains; whether developing a wireless telecommunication system or an interface for a bank’s ATM, Satisfaction is an essential goal. The stable model that represents the EBT Satisfaction is a stable analysis pattern. Similar reasoning can be applied to BOs: the BO Account can be modeled and reused in the developing of different applications, so the stable model representing the Account BO is a stable design pattern. Participants (EBTs and BOs) are classes. If the any class (EBT or BO) is an atomic concept (doesn’t decompose any more for more concepts) and it is an EBT then it may beTHE SEARCHING ANALYSIS PATTERNS what we called a stable analysis pattern and if it is a BO then it may be what we called a stable design pattern. If the class (EBT and BO) is not atomic concept and can be composed of more EBTs and BOs then it is what we called stable architecture pattern. Participants can be classified as following: Tag Name Applied to Value Type Description <EBT> Class <BO> Class <IO> Class <Pattern-EBT> Pattern Represents Stable Analysis Pattern <Pattern-BO> Pattern Represents Stable Design Pattern Pattern-EBT and Pattern-BO can be model using SSM in the second level. See the extended version of the paper. PATTERN NAME: Searching PROBLEM How can we build a model that can capture the core