Abstract: A computer-implemented method of handling exceptions in a business process is disclosed. In one embodiment, a business process exception is identified, classified as being at least one of a plurality of exception types, wherein the classification is based at least in part on a plurality of classification rules, and allocated to at least one user based at least in part on a plurality of allocation rules. The exception can then be investigated and resolved.

Abstract: Tools and methods are described herein that allows for measuring and using the relationship between artifacts of a software design, such as requirements, test plans, and so on. The relationship can be quantified by determining a relationship quotient for quantifying a similarity between components of software design artifacts and presenting the quantified relationships to a user, such as a software designer, so that he or she can account for the relationship between such components during design changes and so on. The relationship quotient is made more representative of substantive similarity by selecting the key terms that are to be submitted to a similarity analysis such that words that are too common in the English language, such as conjunctions, articles, etc., are not used. Ubiquity of certain key terms in an enterprise is accounted for by adding a term significance weight to the similarity analysis.

Abstract: A powerful set of features can assist software developers in searching source code. Source code can be queried to find occurrences of source code elements mapped to domain concepts appearing in an ontology. Queries can specify a search for occurrences of particular operations performed on domain concepts within the source code. Query expansion can be used to locate related domain concepts as indicated in the ontology. Query keyword weighting can be used to emphasize one domain concept over another. Tools can be provided to create the ontology and associate the ontology with the elements appearing in the source code. Results can include user interface features assisting in navigation to a location within the source code associated with the query results.

Abstract: Described herein are methods and systems for capturing functional and non-functional requirements of a software system. Both functional and non-functional requirements are captured in a framework that is easy for end users to use for participating directly at various levels of a requirements capture process. Functional aspects are desirably captured in terms of workflow notations to form a task flow model of the system, which in turn provides a desirable framework for eliciting and appropriately capturing the non-functional requirements. The task flow model updated with functional and non-functional requirements can be comprehensive and accurate enough to be used to generate test cases, to simulate usability and to generate conventional text based use cases. The requirements captured can be verified for quality of domain context to encourage re-use of domain terms.