Patent Application
20140181835
This disclosure relates to dependency analysis of computer data.
Various analyses may be performed on computer statements that may allow users to determine characteristics of the program that would prevent pitfalls in situations such as security parallelization and refactoring. Data-flow analysis may generally relate to gathering information about the set of possible data values calculated at various points in a computer program. A basic form of data-flow analysis is data dependence analysis, which only establishes data dependencies between program locations without considering data values.
According to a first aspect of the disclosure, a computer-implemented method includes computing, by one or more computing devices, one or more dynamic hints based on a finite set of executions of a computer program. The method also includes performing, by the one or more computing devices, a hybrid dependence analysis of one or more statements of the computer program.
One or more of the following features may be included. Performing the hybrid dependence analysis may be a combination of performing a dynamic analysis and performing a sound static analysis. The one or more dynamic hints may be used to perform the sound static analysis. Performing the sound static analysis may include performing a specialized static abstraction based on the one or more dynamic hints. The one or more dynamic hints may be produced by the dynamic analysis. The dynamic analysis may be performed on one or more dynamic executions of the computer program, using one or more inputs to the computer program. Computing the one or more dynamic hints may further include performing one or more dependency queries that determine whether at least one statement of the one or more statements of the computer program may be dependent on at least another statement of the one or more statements of the computer program. Each of the one or more dependency queries may produce a result that may be a positive result or may be a negative result. The positive result may indicate dependence between the one or more statements involved in the hybrid dependence analysis. The negative result may indicate independence between the one or more statements involved in the hybrid dependence analysis. Performing the specialized static abstraction based on the one or more dynamic hints may include using memory locations involved during the one or more dependency queries of a subset of the one or more statements of the computer program that may produce the negative result.
According to another aspect of the disclosure, a computer program product resides on a computer readable storage medium and has a plurality of instructions stored on it. When executed by a processor, the instructions cause the processor to perform operations including computing one or more dynamic hints based on a finite set of executions of a computer program. Instructions may be included for performing a hybrid dependence analysis of one or more statements of the computer program.
One or more of the following features may be included. Performing the hybrid dependence analysis may be a combination of performing a dynamic analysis and performing a sound static analysis. The one or more dynamic hints may be used to perform the sound static analysis. Performing the sound static analysis may include performing a specialized static abstraction based on the one or more dynamic hints. The one or more dynamic hints may be produced by the dynamic analysis. The dynamic analysis may be performed on one or more dynamic executions of the computer program, using one or more inputs to the computer program. Computing the one or more dynamic hints may further include performing one or more dependency queries that determine whether at least one statement of the one or more statements of the computer program may be dependent on at least another statement of the one or more statements of the computer program. Each of the one or more dependency queries may produce a result that may be a positive result or may be a negative result. The positive result may indicate dependence between the one or more statements involved in the hybrid dependence analysis. The negative result may indicate independence between the one or more statements involved in the hybrid dependence analysis. Performing the specialized static abstraction based on the one or more dynamic hints may include using memory locations involved during the one or more dependency queries of a subset of the one or more statements of the computer program that may produce the negative result.
According to another aspect of the disclosure, a computing system includes at least one processor and at least one memory architecture coupled with the at least one processor. The computing system also includes a first software module executable by the at least one processor and the at least one memory architecture. The first software module is configured to perform a hybrid dependence analysis of one or more statements of a computer program. The computing system also includes a second software module executable by the at least one processor and the at least one memory architecture. The second software module is configured to compute one or more dynamic hints based on a finite set of executions of the computer program.
One or more of the following features may be included. Performing the hybrid dependence analysis may be a combination of performing a dynamic analysis and performing a sound static analysis. The one or more dynamic hints may be used to perform the sound static analysis. Performing the sound static analysis may include performing a specialized static abstraction based on the one or more dynamic hints. The one or more dynamic hints may be produced by the dynamic analysis. The dynamic analysis may be performed on one or more dynamic executions of the computer program, using one or more inputs to the computer program. Computing the one or more dynamic hints may further include performing one or more dependency queries that determine whether at least one statement of the one or more statements of the computer program may be dependent on at least another statement of the one or more statements of the computer program. Each of the one or more dependency queries may produce a result that may be a positive result or may be a negative result. The positive result may indicate dependence between the one or more statements involved in the hybrid dependence analysis. The negative result may indicate independence between the one or more statements involved in the hybrid dependence analysis. Performing the specialized static abstraction based on the one or more dynamic hints may include using memory locations involved during the one or more dependency queries of a subset of the one or more statements of the computer program that may produce the negative result.
The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will become apparent from the description, the drawings, and the claims.
a is a diagrammatic view of an aspect of an implementation of a directed acyclic diagram;
b is a diagrammatic view of an aspect of an implementation of a directed acyclic diagram;
Like reference symbols in the various drawings indicate like elements.
According to some example implementations consistent with the present disclosure, users of a software program may want to determine whether statements in a software program are dependent on one another. For example, it may be beneficial for a user to know if one statement in the software program may modify another software program statement. Data-flow analysis is generally the problem of gathering information about the set of possible data values calculated at various points in a computer program. One basic form of dependence analysis, which only establishes data dependencies between program locations without considering data values, is called data dependence analysis. A data dependency may generally include a situation in which a program statement or instruction refers to the data of a preceding statement. In compiler theory, a technique used to discover data dependencies among statements is called dependence analysis. Information about data dependencies may be useful for many situations such as security, parallelization and refractoring. It is understood that although security, parallelization and refractoring are listed as examples of possible uses of dependency analysis, this is only for illustrative purposes only and other situations may be benefited from the dependence analysis.
Security, as mentioned above, may generally relate to integrity and confidentiality violations, for example, where data either flows from an untrusted location to a trusted location (integrity) or vice versa (confidentiality) in web applications for example. Cross-site scripting (XSS) and SQL injection (SQLi) are two examples of integrity violations. Information leakage (where, e.g., an SQL exception is reported to the user in a detailed manner) is an example of a confidentiality violation. The vulnerability may be due to flow of data between two program locations that differ in terms of their security classification. Testing whether there is data dependence between these locations may thus provide a direct answer to the security query.
For parallelization, the data-dependence relation between operations may be a safe approximation of the binary commutativity property: If there is no dependence path connecting between operations O1 and O2, then these operations commute, and moreover, they can be run in parallel. In mathematics, a binary operation is commutative if changing the order of the operands does not change the result. This may result from the disjoint concurrency property that holds in the absence of data dependencies, and may be stronger than commutativity. In disjoint concurrency, programs may be constructed so that they do not ever attempt to access the same memory locations. The parallel thread programming construct C1//C2 is used to denote the creation of two threads, C1 and C2, which are then executed in parallel. For example, a loop can be parallelized if there are no loop-carried dependencies between its iterations, which amount to testing for data dependencies between program locations from distinct iterations.
Refactoring may be a disciplined technique for restructuring an existing body of code, for example by altering the internal structure of the body of code without changing its external behavior. Advantages of refactoring may include improved code readability and reduced complexity to improve the maintainability of the source code. Many refactoring techniques may rely on code motion, the ability to move a program statement to a new location. Code motion may be predicated on the assumption that the moved statement commutes with the operations it changed order with.
Referring to
For example, HDA process 10 may be implemented as a purely server-side process via HDA 10s. Alternatively, HDA process 10 may be implemented as a purely client-side process via one or more of client-side application 10c1, client-side application 10c2, client-side application 10c3, and client-side application 10c4. Alternatively still, HDA process 10 may be implemented as a server-side/client-side process via HDA process 10s in combination with one or more of client-side application 10c1, client-side application 10c2, client-side application 10c3, and client-side application 10c4. In such an example, at least a portion of the functionality of HDA process 10 may be performed by HDA 10s and at least a portion of the functionality of HDA process 10 may be performed by one or more of client-side application 10c1, 10c2, 10c3, and 10c3.
Accordingly, HDA process 10 as used in this disclosure may include any combination of HDA process 10s, client-side application 10c1, client-side application 10c2, client-side application 10c3, and client-side application 10c4.
Referring to
HDA process 10s may be a server application and may reside on and may be executed by computing device 12, which may be connected to network 14 (e.g., the Internet or a local area network). Examples of computing device 12 may include, but are not limited to: a personal computer, a server computer, a series of server computers, a mini computer, a mainframe computer, or a dedicated network device.
The instruction sets and subroutines of HDA process 10s, which may be stored on storage device 16 coupled to computing device 12, may be executed by one or more processors (not shown) and one or more memory architectures (not shown) included within computing device 12. Examples of storage device 16 may include but are not limited to: a hard disk drive; a tape drive; an optical drive; a RAID device; an NAS device, a Storage Area Network, a random access memory (RAM); a read-only memory (ROM); and all forms of flash memory storage devices.
Network 14 may be connected to one or more secondary networks (e.g., network 18), examples of which may include but are not limited to: a local area network; a wide area network; or an intranet, for example.
Examples of client-side applications 10c1, 10c2, 10c3, 10c4 may include but are not limited to an automated software testing application, a web browser, or a specialized application (e.g., an application running on a mobile platform). The instruction sets and subroutines of client-side application 10c1, 10c2, 10c3, 10c4, which may be stored on storage devices 20, 22, 24, 26 (respectively) coupled to client electronic devices 28, 30, 32, 34 (respectively), may be executed by one or more processors (not shown) and one or more memory architectures (not shown) incorporated into client electronic devices 28, 30, 32, 34 (respectively). Examples of storage devices 20, 22, 24, 26 may include but are not limited to: hard disk drives; tape drives; optical drives; RAID devices; random access memories (RAM); read-only memories (ROM), and all forms of flash memory storage devices.
Examples of client electronic devices 28, 30, 32, 34 may include, but are not limited to, personal computer 28, laptop computer 30, mobile computing device 32, notebook computer 34, a notebook computer (not shown), a server computer (not shown), a gaming console (not shown), a data-enabled television console (not shown), and a dedicated network device (not shown). Client electronic devices 28, 30, 32, 34 may each execute an operating system.
Users 36, 38, 40, 42 may access HDA process 10 directly through network 14 or through secondary network 18. Further, HDA process 10 may be accessed through secondary network 18 via link line 44.
The various client electronic devices (e.g., client electronic devices 28, 30, 32, 34) may be directly or indirectly coupled to network 14 (or network 18). For example, personal computer 28 is shown directly coupled to network 14. Further, laptop computer 30 is shown wirelessly coupled to network 14 via wireless communication channels 44 established between laptop computer 30 and wireless access point (WAP) 48. Similarly, mobile computing device 32 is shown wirelessly coupled to network 14 via wireless communication channel 46 established between mobile computing device 32 and cellular network/bridge 50, which is shown directly coupled to network 14. WAP 48 may be, for example, an IEEE 802.11a, 802.11b, 802.11g, 802.11n, Wi-Fi, and/or Bluetooth device that is capable of establishing wireless communication channel 44 between laptop computer 30 and WAP 48. Additionally, personal computer 34 is shown directly coupled to network 18 via a hardwired network connection.
In some embodiments, HDA process 10 may communicate with, interact with, and/or include a component or module of an automated software testing application (e.g., test framework application 54). In an embodiment, test framework application 54 may facilitate automated software testing. For example, test framework application may allow authoring and execution of software tests, e.g., that may be run via test framework application 54, a client application (e.g., one or more of client applications 10c1-10c4, which may include web browsers and/or other suitable applications). One or more of users 36, 38, 40, 42 may access test framework application 54 via one or more respective client electronic devices (e.g., client electronic devices 28, 30, 32, 34) to author and/or execute a software test, e.g., of a user interface, etc.
As generally discussed above, HDA process 10 may generally perform a dependency analysis of various statements in a software program that determines whether these statements are dependent on one another. For example, one statement might eventually modify a prior statement or one statement might result in a different output depending on another statement in the software program. The dependence analysis captures the flow of data that needs to be looked at and makes a decision whether it meets defined dependency criteria.
In some implementations, HDA process 10 may be performed by a combination of sound static analysis and dynamic analysis. The dynamic analysis may provide hints (e.g., dynamic hints) that may be used as inputs into the sound static analysis. For example, running a software program using a number of inputs and performing a query to determine if two statements are dependent of each other. The result of the query for each input may be observed and recorded in a graph from which a subset of query results may be used as inputs into the sound static analysis. The sound static analysis may use an abstraction technique on the subset of query results to form the hybrid analysis.
Soundness of a static analysis may include a static analysis that may result in certain outcome while running the software program using a number of inputs. A static analysis may be considered sound, when two statements are found to be dependent on each other, then the static analysis will likely to report a dependency. In other words, if no dependency was found between two statements, then no execution of the software program using the inputs would show a dependency between these two statements. Unsoundness of a static analysis may include a circumstance in which the static analysis may give a solution however that solution may not reflect a possible dependency between two statements across all possible executions of the software program.
As discussed above, HDA process 10 may compute 100 one or more dynamic hints based on a finite set of executions of a computer program. HDA process 10 may also perform 102 a hybrid dependence analysis of one or more statements of the computer program.
HDA process 10 may compute 100 the one or more dynamic hints based on a finite set of executions of a computer program. For example, and referring also to
As generally discussed above, the dynamic hints (e.g. dynamic hints 302) may be produced by dynamic analysis 300. The dynamic analysis may be performed on one or more dynamic executions of the computer program, using one or more inputs to the computer program. For example, dynamic analysis 300 may be performed by executing computer software program 304 using inputs 306 (i.e. as inputs ij: 1≦j≦n). The outcome of computer software program may result in dynamic hints. As stated above, the dynamic hints may be the result of performing dependencies queries on the computer statements (e.g., 308). The outcome of the queries may be used in order to generate the dynamic hints. The generation of the dynamic hints will be explained in more detail below.
In an embodiment, the dynamic hints may be computed by performing 104 one or more dependency queries to determine whether at least one statement of the one or more statements (e.g., statement 308) of the computer program is dependent on at least another statement of the one or more statements of the computer program. For example, computer software program 304 maybe executed on finite set of inputs (e.g., inputs 306). Further, a set of queries, having as parameters computer statements (e.g., statements 308), may be performed in order get a result. The queries may be in form of one or more dependency queries between at least two computer statements 308 (e.g., s1 to sk, where k is a finite number). For example, the dependency query may have computer statement s1 and s2 as parameters. Statements s1 and s2 may be represented to the dependency query in the form (s1, s2). It is understood that although computer statements may be represented as (s1, s2), this is only for illustrative purposes only and other representation may be used. For each input ij, 1≦j≦n, a dependence graph may be computed over trace P(i). It understood that other representation of a dependence result may be used and the above dependence graph is only for illustrative purposes. In some embodiments, the solution of a dependence analysis may be represented as a graph structure, G=(V, E), where:
In some embodiments, there are three types of dependencies, Read-After-Write (RAW), Write-After-Read (WAR) and Write-After-Write (WAW). For the purposes of this disclosure all types of dependencies may be treated uniformly. Referring to
Each of the one or more dependency queries may produce a result that may be either a positive result or a negative result. The positive result may indicate dependence between the one or more statements involved in the hybrid dependence analysis. The negative result may indicate independence between the one or more statements involved in HDA process 10. Referring to
As explained above, there may be two possibilities; either the query returns a positive or a negative answer to the query of whether computer statements (e.g., s1 and s2) are dependent. For example, s1 and s2 may be found to be dependent if there is an index 1≦j≦n, such that trace P(ij) shows s1 to be dependent on s2. In that case, the analysis may respond with a positive answer to the query. Consequently, it may not be necessary to continue the dependency analysis of s1 and s2 because the result may have been established that for an input ij, s1 and s2 are found to be dependent of each other. It is understood that although the dependency queries are between s1 and s2, this is only for illustrative purposes and other computer statements (i.e. statement 308: s1 to sk, k being a finite number) may be used as parameters to the dependency query.
As explained above, HDA process 10 may also perform 102 a hybrid dependence analysis of one or more statements of the computer program. As will be described in more detail, HDA process 10 may include a combination of a sound static analysis and a dynamic analysis (e.g., dynamic analysis 300). The dynamic analysis may provide one or more dynamic hints that may become inputs to the sound static analysis. For example, running a computer software program (e.g., computer software program 304) using a number of inputs and performing a query to determine if at least two computer statements 308 (e.g., s1 to sk, where k is a finite number) are dependent on each other. As will be described later, the sound static analysis may use an abstraction technique on the subset of query results to form the hybrid analysis. It is understood that the above are only examples and the HDA process 10 may be performed by other means.
The hybrid dependence analysis may perform 106 a combination of a dynamic analysis (e.g., dynamic analysis' 300) and a sound static analysis. Sound static analysis may be a static dependency analysis of a computer software program (e.g., computer software program 304) that may be performed without actually executing the computer software program. Static dependence analysis may be complicated; especially when considering modern object-oriented (OO) software, which may typically span millions of lines of sophisticated library code, consist of multiple abstraction layers, and make wide use of OO concepts such as encapsulation and polymorphism. Some, and/or all, these challenges may be addressed to a reasonable degree given that the analysis may be sufficiently precise in its modeling of the concrete memory. In some circumstances, defining the set of abstract memory locations to be tracked and maintained by the analysis may present challenges, such that it may still scale to real-world programs.
As explained above, dynamic analysis 300 may be performed on one or more executions of the computer program (e.g., 304), using one or more inputs (e.g., inputs 306) to the computer program. For example, dynamic analysis 300 may be performed by executing computer software program (e.g., computer software program 304) using inputs 306 (i.e. as inputs ij: 1≦j≦n). HDA process 10 may be based on the one or more dynamic hints (e.g., dynamic hints 302). These dynamic hints may be computed based on a finite set of runs of the subject program (e.g., computer software program 304), and may be then used to specialize the ensuing sound static analysis such that its precision may be boosted without impairing its scalability.
In an embodiment, dynamic hints may be used to perform the sound static analysis. As explained above, dependency queries may produce a result that may be either a positive result or a negative result. The negative result may indicate independence between the one or more statements involved in HDA process 10. For example, there may be two possibilities; either the query returns a positive or a negative answer to the query of whether computer statements 308 (e.g., s1 and s2) are dependent. If for example, the result of the dependence query is a negative result, this may not provide confidence that the two statements (i.e., s1 and s2) are actually independent. There may be other inputs outside the finite inputs used (i.e. inputs ij: 1≦j≦n) that may result in dependence between s1 and s2. The queries that resulted in a negative result may provide useful hints (e.g., dynamic hints 302) that may be used in the sound static analysis.
HDA process 10 may perform 108 a specialized static abstraction based on the one or more dynamic hints (e.g., dynamic hints 302). For example, dynamic hints 302 may be exploited for building an effective static abstraction. Abstraction may be a process by which concepts are derived from the usage and classification of literal (“real” or “concrete”) concepts, first principles, or other methods. Further, abstraction may be a process by which data and programs are defined with a representation similar in form to its meaning (semantics), while hiding away the implementation details. When the result of the dependency query is a negative result, which, as explained above, does not mean that for other than inputs ij, 1≦j≦n the result would still be negative (i.e., independent). There may be other inputs outside 1≦j≦n that may yield a dependency between s1 and s2 for example. In that case, a specialized static abstraction may be necessary in order to create confidence in the result of the dependency queries. As will be explained in more detail below, the abstraction may be based on concrete memory locations.
In case s1 and s2 are found to be independent for inputs ij, 1≦j≦n, for each P(ij) the analysis may have a precise notion of the memory locations involved in the subgraph of P(ij) whose source may be statement src (i.e., 406) and whose target may be tgt (i.e. 408). Src and tgt may be statements of a computer software program (e.g., computer software program 304). Src and tgt may be part of a dependency query of whether src is dependent on tgt. This information may then be used to form a specialized abstraction of the concrete memory locations that may be effective when reasoning about query (tgt, src). It is understood that the above is only for illustrative purposes only and other means of abstraction may be used.
In another embodiment, HDA process 10 may use 110 memory locations involved during the one or more dependency queries of a subset of the one or more statements of the computer program that produces the negative result when HDA process 10 performs 108 the specialized static abstraction based on dynamic hints. As explained above, the concrete memory locations that may be effective when reasoning about query (tgt, src) may be used to form a specialized abstraction. Although other representation may be implemented, below is an example implementation of the specialized static abstraction and is only for illustrative purposes.
Consider a set {P(ij): 1≦j≦n} of traces of inputs (e.g., ij: 1≦j≦n) and let G[P(ij)] be the dynamic dependence graph corresponding to trace P(ij). This graph may exhibit dependencies between statements (i.e., statement 308) in the computer software program (e.g., computer software program 304) based only on the information in trace P(ij). Considering input query (tgt,src), denote the subgraph of G[P(ij)], whose source is src, by G[P(ij),src]. G[P(ij),src]=(V′,E′) is a directed acyclic graph (DAG) where:
V′={vεV:v→src}; and
E′={e=(v1,v2)εE:v1,v2εV′},
Tgt may be absent from G[P(ij),src] for all 1≦j≦n, since otherwise a positive answer may have been returned based on the dependence query performed above.
For illustrative purposes only, assume that edges in G[P(ij),src] are annotated with sets of dynamic memory locations, those involved in each dependency. Further, for illustrative purposes, denote by M[P(ij),src] the set of memory locations participating in G[P(ij),src] (i.e., appearing on edges in G[P(ij),src]). Then retaining the analysis' precision with regard to the locations in Uj=1nM[P(ij), src] may be desired, while treating the remaining memory locations in Uj=1nG[P(i1)] in a coarse manner. This is in light of the likely invariant that statement src may not influence statement tgt, which may be born out of n runs of computer software program 304 on representative inputs (i.e. ij: 1≦j≦n).
Assuming that the inputs chosen for the n runs of the computer software program (e.g., computer software program 304) are indeed representative, memory locations whose value is not influenced by src in any of the n runs may not be relevant for the proof. The remaining memory locations may be, on the other hand, important for the proof: If the analysis treats them coarsely, then it may wrongly reject the proposition that src is independent of tgt. However, memory locations involved in the traces may be incomparable as a result of being dynamic. Abstraction may be needed to normalize between memory locations across different traces. A standard way of performing the normalization may be via the classic allocation-site-based abstraction of concrete objects, where the site where a concrete object is allocated is the object's abstract name. This partitioning of the unbounded set of runtime objects may be finite, and may be refined by taking into account a k-approximation of the call string leading to the allocation site. Although, k-approximation is utilized, other types of approximation algorithms may be used. Approximation algorithms may be, but not limited to, k-approximation, ρ-approximation algorithm and r(n)-approximation.
Assuming this base abstraction, a specialized abstraction may be created that discriminates between relevant and irrelevant memory locations (according to {P(ij): 1≦j≦n}) as explained above. There are two classes of memory locations, heap locations and environment locations. Under specialization, each of the categories may be explained as:
Specialization may help when using glob (i.e., global) in place of multiple abstract memory locations. Glob may reflect future knowledge of which memory locations would matter when reasoning about the proposition that src is independent of tgt, which may be made possible thanks to the dynamic hints. Dynamic information may indicate which abstract locations to map to glob, and hence may play a role in letting the analysis use an affordable abstraction, and may still compute a more precise solution. The dynamic analysis thus may play a predictive role. However, predication may have errors especially given the fact that the prediction may be based on finite runs of the program. Glob may enable the analysis to err on the safe side, since the information loss it embodies can only cause the analysis to reject a valid independence proposition, but not vice versa.
Referring also to
Computing system 12 may include microprocessor 502 configured to e.g., process data and execute instructions/code for screen capture process 10. Microprocessor 502 may be coupled to storage device 16. As discussed above, examples of storage device 16 may include but are not limited to: a hard disk drive; a tape drive; an optical drive; a RAID device; an NAS device, a Storage Area Network, a random access memory (RAM); a read-only memory (ROM); and all forms of flash memory storage devices. IO controller 504 may be configured to couple microprocessor 502 with various devices, such as keyboard 506, mouse 508, USB ports (not shown), and printer ports (not shown). Display adaptor 510 may be configured to couple display 512 (e.g., a CRT or LCD monitor) with microprocessor 502, while network adapter 514 (e.g., an Ethernet adapter) may be configured to couple microprocessor 502 to network 14 (e.g., the Internet or a local area network).
As will be appreciated by one skilled in the art, the present disclosure may be embodied as a method (e.g., executing in whole or in part on computing device 12), a system (e.g., computing device 12), or a computer program product (e.g., encoded within storage device 16). Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, the present disclosure may take the form of a computer program product on a computer-usable storage medium (e.g., storage device 16) having computer-usable program code embodied in the medium.
Any suitable computer usable or computer readable medium (e.g., storage device 16) may be utilized. The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium may include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a transmission media such as those supporting the Internet or an intranet, or a magnetic storage device. The computer-usable or computer-readable medium may also be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-usable medium may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave. The computer usable program code may be transmitted using any appropriate medium, including but not limited to the Internet, wireline, optical fiber cable, RF, etc.
Computer program code for carrying out operations of the present disclosure may be written in an object oriented programming language such as Java, C#.NET, PHP, C++ or the like. However, the computer program code for carrying out operations of the present disclosure may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through a local area network/a wide area network/the Internet (e.g., network 14).
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor (e.g., processor 502) of a general purpose computer/special purpose computer/other programmable data processing apparatus (e.g., computing device 12), such that the instructions, which execute via the processor (e.g., processor 502) of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory (e.g., storage device 16) that may direct a computer (e.g., computing device 12) or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer (e.g., computing device 12) or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.
A number of embodiments and implementations have been described. Nevertheless, it will be understood that various modifications may be made. Accordingly, other embodiments and implementations are within the scope of the following claims.
