Abstract: The present disclosure involves systems, software, and computer implemented methods for providing self-documentation of development systems. One process includes operations for identifying at least one software component for deployment on a client device. An installation package is received from a source server, the installation package including the at least one software component and at least one artifact associated with the software component. Source documentation is generated for the at least one software component based on the at least one artifact.

Abstract: A system, method, and computer-readable medium, is described that finds similarities among programming applications based on semantic anchors found within the source code of such applications. The semantic anchors may be API calls, such as Java's package and class calls of the JDK. Latent Semantic Indexing may be used to process the application and semantic anchor data and automatically develop a similarity matrix that contains numbers representing the similarity of one program to another.

Abstract: In accordance with certain embodiments of the present disclosure, specifying integration points of a system-of-systems includes identifying an integration point that associates interfaces of system components. The integration point is characterized according to the identification to generate a set of attributes describing the interfaces. The integration point is specified according to the set of attributes.

Abstract: A method for managing a software development process, the method includes: receiving information representative of instances of simple software development process events; detecting, by a complex event processing (CEP) engine and in response to the received information, at least one complex situation; and invoking at least one software management process reaction responsive to a detection of the at least one complex situation.

Abstract: The present disclosure discloses a method, system, and computer program product for extracting business rules of a Service-Oriented Architecture (SOA) system. Each of the method, system, and computer program product providing functions comprising: obtaining values of a plurality of business objects; obtaining structure units of the SOA system; establishing association relationships between the structure units and the values of the business objects; and generating business rules based on the association relationships. Using one or more embodiments of the present disclosure can break through the limitations of the conventional method of extracting business rules of a SOA system based on code, and can extract business rules of a complex SOA system.

Abstract: Content owners (e.g., Website publishers) are provided with a simple mechanism to automatically summarize and display information (news, images, maps, etc.) related to inferred interests of a user or users visiting their Website. The targeting can driven by a variety of mechanisms including, for example, an automated contextual understanding of the content of the Web page, profile-based information derived from personal data supplied by, or inferred from actions by, the user visiting the Website, location-targeted information (e.g., inferred by the Website visitor's current geography), etc. “Related Content Units” may be used to help content owners render useful, related, content by allowing for a variety of targeting methods to gather related pieces of Internet content and present them integrated into an HTML iFrame or a JavaScript/XML feed which can be easily integrated by the Website publisher onto the Web pages of their Website.

Abstract: A stripped-down version of a library is generated from server source code extracted from a server project. The transitive closure of program entities extracted from the server source code and referenced by the extracted program entities can be computed. A placeholder entity can be inferred for an entity defined by the transitive closure computation if a definition of the entity cannot be found in the server source code. The stripped-down library generated from the extracted server source code is received by a reflection-based component that uses reflection to generate documentation and disclosure information helpful in the development of the client source code. A placeholder entity can be marked or decorated to signal to the reflection-based component that client source code is not to be generated for the decorated entities.

Abstract: A method that includes: running a set of functional tests over a computer code; determining, for each code element of the computer code, which functional test covered it, to yield a tests-elements coverage map; associating portions of the computer code with corresponding design portions or requirements derived from a design document or a requirements document respectively, associated with the computer code, to yield a design/requirements-code tracing map; deriving, from the tests-code coverage map and the design/requirements-code tracing map, a design/requirements-tests coverage map, exhibiting coverage of the computer code by the functional tests, in terms of the design or the requirements, wherein at least one of the running, the determining, the associating, and the deriving is executed by at least one processor.

Abstract: A method that may include: building a dependencies graph representing dependencies between code elements of a computer code; associating portions of the computer code with corresponding design specifications or requirements derived from a design specifications document or a requirements document respectively which is associated with the computer code, to yield a design specifications or requirements-code tracing map; and analyzing the design specifications or requirements-code tracing map based on the dependencies graph to yield an ordered list of design specifications or requirements respectively, wherein the order is selected such that functional tests written for the computer code and addressing design specifications or requirements of a higher order, will yield a higher level of functional test coverage of the computer code in terms of design specifications or requirements.

Abstract: Systems and methods for processing software application metadata associated with a software application are provided. A representative method includes the step of collecting software application metadata associated with a software application. The software application metadata includes a first set of information related at least one of the following: screens, paths, and layers associated with the software application. The method further includes the step of storing the software application metadata in a data repository.

Abstract: An apparatus for locating isolation points in an application under multi-tenant environment includes a scanning module configured to scan the application, by using scanning rules, to obtain potential isolation points and relationships between the potential isolation points; a specifying module configured to specify at least one isolation point among the potential isolation points; and an isolation point screening module configured to screen an isolation point from the potential isolation points by using relationships between the specified at least one isolation point and the remaining potential isolation points.

Abstract: A computer implemented method for locating isolation points in an application under multi-tenant environment includes scanning, using a computer device an application by using scanning rules, to obtain potential isolation points and relationships between the potential isolation points; specifying at least one isolation point among the potential isolation points; and screening an isolation point from the potential isolation points by using relationships between the specified at least one isolation point and the remaining potential isolation points.

Abstract: Approaches that allow the context of an SMI task to be saved between SMIs. Upon entering an SMI handler for a task, a new task context stack is created. Thereafter, the SMI handler uses the task context, leaving the original stack unchanged. When the time limit for a single SMI is almost reached, the CPU is directed back to the original stack, and the task context stack persists in memory and retains the context of the task in hand. The soft SMI exits with an indication to signify that a new SMI should be invoked to continue processing. The entity that caused the first soft SMI then invokes another, passing in an indication to signify that this is a continuation of the prior task. On entering the SMI handler, the handler notes the request for continuation, switches to the saved task context stack and continues processing where it left off.

Abstract: A system and computer program product for providing a maintenance environment for computer program code Portions of the computer program code are selectively stored and one or more lists of the stored portions are created. Links are created between the lists and the stored portions of the computer program code for navigational purposes. A maintenance environment for the computer program code is provided.

Abstract: A system and method for field analysis, in an organization is described herein. According to the present invention, the system parses the software code to prepare an abstract syntax tree, extract attributes and relational report, load the report in a common repository, perform impact analysis on the said common repository based on user provided seed, and prepare the list of impacted variables. Further, if required the impacted fields are expanded based on the target size information provided.

Abstract: An analytical software design system arranged to receive informal system design specifications and to convert them into verified design specifications for use in creating source code and carrying out implementation testing of the source code is described. The system comprises a verified black box specification generator arranged to process the received informal system design specifications to create formal specifications; to generate from the formal specifications mathematical models representing the system behavior; to analyze the mathematical models to determine if they have the required behavior; to adjust the formal specifications until the required behavior is achieved; and to derive the required verified design specifications from the mathematical models.

Abstract: A method, system and computer-readable medium for creating software in a standardized manner are presented. The method includes the steps of: receiving, at a software factory, a description of software needs from a customer; creating, in the software factory, a project proposal that meets performance criteria found in the description of software needs; inducting the project proposal into the software factory, where inducting the project proposal initially evaluates the project proposal's compatibility with a capacity of the software factory; parsing the project proposal into major functional areas; retrieving work packets that are appropriate for the project proposal, where the work packets are pre-stored, reusable, self-contained, discrete units of software code; assembling the work packets into a deliverable software; testing the deliverable software; and delivering the deliverable software to the customer.

Abstract: A component name manager operates within an integrated development environment to assist developers in creating dynamic websites and Internet applications. The component name manager identifies an input field displayed on a graphical user interface of an object-oriented software development environment. The input field uses a fully-qualified name of a software component for accessing to access instructions and data associated with the software component and located at an application server. In response to receiving an input associated with the input field, the component name manager displays a list of qualified names of software components available for use in the object-oriented software development environment. Each of the qualified names identifies a path for accessing a corresponding software component. The component name manager can resolve fully qualified names by accessing one or more of an application file, an administrator interface, project level mappings, and global level preference mappings.

Abstract: The automated generation of code decoration for a body of code under review. Upon accessing the body of code, the system evaluates portions of the code for context. For at least some of those portions of code, the system identifies a decoration corresponding to that context, and adds the identified decoration to the body of code in a manner that the decoration is visually associated with the corresponding portion of the code.

Abstract: Mechanisms for evaluating software sustainability are provided. The illustrative embodiments provide code scanning tools for identifying authors of portions of a software product and various attributes about the development, maintenance, and improvement of portions of the software product over time. This information may be correlated with organizational information to identify portions of the software product that may be lacking in sustainability by the persons currently associated with the software organization. Moreover, this information may be used to obtain information regarding the relative quality of the composition or conception of portions of the software product, portions of the software product that have required a relatively larger amount of resources to develop over time, a relative indication of which portions of the software product are “harder” or “easier” to sustain and who is associated with those portions of the software product, and the like.

Abstract: Creating metadata for dynamic code in a descriptive metadata language. The method includes obtaining one or more first data structures defining constructs in a body of dynamic language source code. From the one or more first data structures, identifier information is extracted for one or more of the defined constructs. Knowledge about the constructs is augmented. Metadata about the body of the dynamic language source code is provided, with the source code, in a specific metadata format, to a user.

Abstract: Analyzing dynamic source code. A method includes accessing a specific metadata format data structure. The data structure was created by obtaining one or more first data structures defining constructs in a body of dynamic language source code. From the one or more first data structures, identifier information is extracted for one or more of the defined constructs. Knowledge about the constructs is augmented. The metadata format data structure is parsed to compute metrics about the metadata format data structure. The metrics about the metadata format data structure are provided to a user.

Abstract: A method, system, and computer-readable medium for maintaining a health of a software factory that creates custom software in a standardized manner is presented. In a preferred embodiment, the method includes the steps of: defining work packets to perform sub-functions of a custom software; tracking a transmission of the work packets to an assembly line in a software factory; monitoring any retrieval of software artifacts that are used to create the work packets; monitoring any on-going changes of work activities that are contained in the work packets; determining if execution of the work packets conforms to governance guidelines for the software factory; monitoring the software factory to ensure that the work packets comply with an architecture of the software factory; tracking quality metrics for an execution of the work packets in an assembly line in the software factory; and transmitting all tracked and monitored information described above to a dashboard.

Abstract: In general, in one aspect, the invention relates to a method for identifying program properties in source code. The method includes: identifying a set of program objects corresponding to a potential program property within the source code; identifying a function associated with the set of program objects in the source code; identifying an input and an output of the function in the source code; creating a value flow graph by: creating a function input node representing the input; creating a function output node representing the output; identifying value flow functions, where each value flow function defines a conditional dependency between a pair of graph nodes, and creating, based on the value flow functions, directed graph edges modeling a potential flow of data through the value flow graph; and identifying a feasible path in the value flow graph depicting an occurrence of the potential program property in the source code.

Abstract: Methods and systems are provided for securing electronic control unit code. In one implementation, a method is provided. According to the method, an order for the program code may be transmitted to a developer. The order may include specifications and an authentication key. The method may further include receiving the program code and the authentication certification from the developer and verifying the authentication certificate to determine whether the developer was an authorized source of the program code. The method may generate metadata identifying the authorized source of the program code and embed the metadata in the program code.

Abstract: A design matrix structure visualization technique and tool for the study and analysis of systems, such as software systems, where the bounds of the matrix are defined by a selected focusing metric and entities forming the system are displayed in the matrix as blocks of size relative to their proportion of the selected focusing metric. Relationships between entities are illustrated by summing all relationships between individual elements forming each displayed entity. Where possible, an identifier defining the characteristic of a displayed block is also shown. Preferably, the technique and tool includes a “zoom” feature to allow a user to drill down and uncover details associated with smaller blocks as shown in the original view.

Abstract: A schema is provided that supports documenting API elements that is flexible and captures current technologies as well as evolves without interfering or breaking the definitions of the existing elements. The schema utilizes a flexible and extensible element that can be used to define various elements of the APIs and can be extended to define new technology when it is introduced.

Abstract: A system and method for creating customized documentation is disclosed. The method comprises storing one or more documents such that each of the one or more documents corresponds to one of a plurality of versions of a software product. The version of the software product which is installed in an installation environment is detected. The configuration of the installation environment is also detected. At least one document from the one or more documents that corresponds to the version of the software product installed in the installation environment is selected. A subset of the selected document that includes the version of the software product installed in the installation environment and the configuration of the installation environment is then determined. A customized document is composed, based on one or more subsets of the selected document.

Abstract: A method and system provides one or more product type descriptions, and constructs a map between the sub-conditions of the product type descriptions and constructs in a Web Ontological Language (OWL). The method converts the product type description rules into new OWL classes by creating a new OWL class for each corresponding rule; adding the new OWL class to the OWL ontology; for each condition of the corresponding rule, extracting sub-conditions; for each the sub-condition extracted; creating new constructs for the new OWL class using the map; and adding new class restrictions to the new OWL class, wherein each of the new class restrictions relates to a corresponding condition of the corresponding rule.

Abstract: A computer implemented apparatus for automatically generating and filtering creative proposals is disclosed. Particularly, the computer implemented apparatus automatically generates all possible featured component code sets which corresponding to all possible featured components, and compares them to the prior art code sets which corresponding to the prior objects. Thereby, the novel code sets which corresponding to the novel creative proposals are rapidly filtered out. The computer implemented apparatus comprises a standard component database, a permutation and combination module, a featured component code set database, a prior art code set database, a matching module, a sifting module and an output module.

Abstract: Certain exemplary embodiments can provide a system, which can comprise a block processor. The block processor can be adapted to automatically render a list of automatically described modifications to a first version of a block of a software program adapted to control a programmable logic controller (PLC). The first version can differ from an original version of the block.

Abstract: A build process management system can acquire data pertaining to a software build process that is currently being executed by an automated software build system. The software build process can include executable process steps, metadata, and/or environmental parameter values. An executable process step can utilize a build artifact, representing an electronic document that supports the software build process. The acquired data can then be synthesized into an immutable baseline build process and associated baseline artifact library. The baseline artifact library can store copies of the build artifacts. The immutable baseline build process can include baseline objects that represent data values and dependencies indicated in the software build process. In response to a user-specified command, an operation can be performed upon the baseline build process and associated baseline artifact library.

Abstract: A build process management system can acquire data pertaining to a software build process that is currently being executed by an automated software build system. The software build process can include executable process steps, metadata, and/or environmental parameter values. An executable process step can utilize a build artifact, representing an electronic document that supports the software build process. The acquired data can then be synthesized into an immutable baseline build process and associated baseline artifact library. The baseline artifact library can store copies of the build artifacts. The immutable baseline build process can include baseline objects that represent data values and dependencies indicated in the software build process. In response to a user-specified command, an operation can be performed upon the baseline build process and associated baseline artifact library.

Abstract: A method for proofing a prototype dynamic webpage version referencing first configuration data is disclosed. The prototype dynamic webpage can be derived from a live version referencing second configuration data and accessible via a live link. The method includes storing first configuration data in a configuration database also containing second configuration data, providing a prototype link to the prototype dynamic webpage version dissimilar from the live link; and returning, upon a prototype link request, the prototype dynamic webpage version, involving rendering the prototype dynamic webpage version based on the first configuration data without altering the live dynamic webpage version. Also disclosed is a dynamic webpage versioning system working off a configuration database and distinct versions of configuration data.

Abstract: A service definition document (SDD) framework is provided for defining blended services that utilize multiple service endpoints. The SDD framework can comprise a first category that defines a service endpoint representing a blended service, a second category that defines a plurality of service endpoints utilized by the blended service, and a third category that defines execution of the blended service. Blended services can be provided by creating a model of a blended service and saving a representation of the model of the blended service in a service definition document (SDD) framework. A blended service defined in a SDD framework can be executed by receiving the SDD and executing the blended service as defined by the SDD using a service execution environment (SEE).

Abstract: A method for building and verifying and validating a software system that is used for regulated industry software related activities, such as FDA trials, field trials, biomedical data gathering, and similar efforts includes building the application into a virtual appliance using, for example, Vmware. The application and the supporting software are encapsulated in a single virtual file to create a virtual appliance that is independent of hardware and dependent only on virtual appliance support.

Abstract: A method, operable on a processing device, for assessment of skills of a user may include receiving, by the processing device, an error message reporting an error associated with the user. The method may also include determining, by the processing device, a categorization of the error. Determining the categorization of the error may include assigning one of a plurality of predetermined skill ratings to the user. Each predetermined skill rating may be associated with a predefined condition. The method may additionally include generating, by the processing device, a report for assessment of the skills of the user. The report may include an identification of the user, the error, identification of a system if a system associated error, identification of a product if a product associated error, the categorization of the error and the predetermined skill rating assigned to the user.

Abstract: A method and system for detecting plagiarism of software source code. In one embodiment, a first set of arrays and a second set of arrays are created for a first program source code file and a second program source code file respectively. Each pair of arrays in the first and second sets has entries corresponding to program elements of a distinct program element type such as functional program code, program comments, or program code identifiers. Next, each pair of arrays from the first and second sets is compared to find similar entries, and an intermediate match score is calculated for each pair of arrays based on the similar entries. Further, the resulting intermediate match scores are combined to produce a combined match score, which is then used to provide an indication of copying with respect to the first program source code file and the second program source code file.

Abstract: A method and architecture is described that discovers software application metadata and generates data access applications based on the discovered software application metadata. The discovered metadata along with handcrafted metadata goes through a discovery process and is converted into common, generic abstract metadata objects. The abstract metadata objects then go through an instantiation process to be translated into concrete metadata objects that represent the unique configuration, context and terminology of the source software application. The concrete metadata objects can be generated into numerous forms for the purposes of data access and information sharing. The system also has upgrade protection.

Abstract: A method of analyzing a legacy source code application is described. The method comprises traversing a generated set of entries of a module hash array, a summary count catalog, and an occurrence location catalog to determine duplicate lines of code of the legacy source code application. The method also comprises determining a duplicate sequence of one or more lines of code with respect to at least one other sequence of one or more lines of code of the legacy source code application based on traversal of the generated set of entries of the module hash array, the summary count catalog, and the occurrence location catalog. The method also comprises storing a match result identifying the determined duplicate sequence and the at least one other sequence.

Abstract: The present invention discloses an automatic method and system for generating and filtering out the innovation proposals. Particularly, it is about a system, which generates all the possible element code sets, compares them to the code sets of existing objects or documents, and then filters out the novel element code sets. The system comprises a standard element depository, a permutation and combination module, a testing object processing module, a matching module, a sifting module, and an output module.

Abstract: An abstract component model can be used to drive an editor by providing an underlying stateful model for component implementation without the need to re-implement details, such as event listening, lifecycle and update management, etc. An implementation needs to provide objects that make up the model, some logic to listen to environmental changes and recognize when an update is needed, and a builder which can generate a lightweight version of the model based on the current “state of the world.” In addition, abstract component model is operable to support an editor such as page flow.

Abstract: Harvesting assets for packaged application practices, in one aspect, may include obtaining one or more work products associated with deployment of packaged software applications, extracting content and style, enhancing content and style with models of work products, and storing assets in asset repository.

Abstract: There are disclosed systems and methods for aiding programmers in identifying a location in a program while coding. In an embodiment, the method comprises defining a plurality of sections of code within the program, associating at least one section of code with a background color, and displaying the at least one section of code against the associated background color. Sections of code corresponding to the same module may be associated with the same background color. A user-selectable control may be provided for viewing only those sections of code corresponding to a user-selected module, and upon selection of the module by the user, only those sections of code corresponding to the module may be displayed against the associated background color. A text description may also be associated with each section of code, and the text description may be displayed when a cursor is placed in the section of code.

Abstract: Methods and apparatus, including computer systems and program products, that implement a description language and a parser for a description language. A method includes receiving input including a specification of base items, a specification of contexts, and a specification of a selected context from the contexts. The method further includes generating an output set of items by evaluating the selected context. In that method, each item in the output set of items includes core attributes of a corresponding base item and can include attributes from a context. Generating an output set of items can include generating a specific bill of materials.

Abstract: Interface identifier parameterization techniques are described. In one or more implementations, a textual description is obtained of a parametric type represented in a binary standard of a programming model and an interface identifier is generated based at least in part on the obtained textual description of the parametric type.

Abstract: Various technologies and techniques are disclosed for retargeting applications to different types. A development environment is provided for writing software. Input is received from a user to write application logic for a project. The user selects an option to save the project as a particular type of project. The application logic is wrapped with metadata appropriate for the particular type of project and at least one resulting file is created. The system determines if the resulting file needs compiled, and if so, compiles the resulting file into a compiled application. A second selection can be received from the user to save the project as a second type. In such a case, the application logic is wrapped with metadata appropriate for the second type of project and at least one resulting file is created.

Abstract: Methods and systems for providing a monitoring center with sensors that are inserted at one or more locations within an operating framework software engine. The sensors monitor the interpretive framework engine's process of loading commands, combining variables with coded commands, and executing commands with event processing, variable values, and user interactions. The sensors watch and gather information that has been deemed relevant by the monitoring center's configuration and pass that information to the center so that storage functions can route the information to the appropriate data storage locations. Alternatively, each sensor can be self-contained providing monitoring, gathering, processing, data transmission, and storage within the sensor.

Abstract: Methods and systems described herein implement a recommendation system for providing recommendations for generating a requirements specification for agile software development. In one implementation, the system includes a processor and a memory coupled to the processor. The memory comprises a mapping module and an agile recommendation module. The mapping module is configured to map knowledge elements of at least one ontology instance selected from among a plurality of ontology instances with another ontology instance selected from among the plurality of the ontology instances. The agile recommendation module is configured to generate a knowledge corpus based on the mapped knowledge elements of the ontology instances and at least one environmental parameter, receive modifications in the knowledge corpus, and provide recommendations to generate a requirements specification based at least, in part, on the received modifications.

Abstract: A content management system (CMS) for computer software provides automatic notification and correlation of changes in a design document with corresponding code, and provides automatic notification and correlation of changes in the code with one or more corresponding design documents. Traceability rules are defined that correlate which portions of the code correspond to which portions of the design document. A traceability update policy governs whether interested parties are notified of a change to either the design document or the corresponding code, and whether the change to one causes an automatic update to the other. The result is a content management system that helps keep the code and corresponding design documents consistent with each other so the system has accurate and consistent information at all times.