Abstract: Visualization of the result of user interface code is provided in the context of code review. Changes to user interface code can be visualized to enable code reviewers to easily understand the effect of such changes. Furthermore, the visualization, or view, provides a surface for users to provide precise feedback to a developer.

Abstract: Described is a method for managing test artifacts. According to an embodiment of the method, a test plan for a product is selected by a user. The test plan has multiple test artifacts that include the test plan and at least one of a test case, an execution record defining a configuration of the product, and a product requirement. One of the test artifacts is selected for a snapshot and the snapshot is acquired. The snapshot acquisition includes storing a current state of the selected test artifact, storing a current state of relationships of the selected test artifact to the other test artifacts, and storing a current state of the other test artifacts that have a relationship with the selected test artifact.

Abstract: A computer-implemented method of controlling version branching within a software configuration management system (SCMS) can include, responsive to a user initiating a check-out operation of a file within the SCMS, identifying the file and a workspace of the user and searching nodes of the repositories of the SCMS for a successor version of the file. When a successor version of the file is located within a node that is within a predetermined distance of the workspace of the user, a notification that the successor version of the file is within the predetermined distance of the workspace of the user can be output. When a successor version of the file is not located within a node within a predetermined distance of the workspace of the user, the file can be checked-out to the workspace of the user.

Abstract: Modeling a governance process of creating a new version of a service in a governed SOA and generating, in dependence upon the modeled governance process, automation modules that include modules of computer program instructions that, when executed by a computer processor, support performance of one or more steps of the modeled governance process and where the modeled governance process includes reviewing requested updates to a deployed service; determining, in dependence upon the requested updates and a specification of a present version of the deployed service, whether a new version of the deployed service is required; if a new version of the deployed service is required, determining whether the present version of the deployed service will be subsumed by the new version; and if the present version of the deployed service will be subsumed by the new version, retiring the present version of the deployed service.

Abstract: A method, apparatus and computer program are disclosed for modifying an application comprising a plurality of modules. A user is presented with a list of modules. The user is able to specify input regarding any permitted version modifications for the modules listed. It is then determined whether the requested modifications are possible with one or more failure messages being output when any of the requested modifications are not possible. At least one of the failure messages is used to enable modification of the initial input provided by the user. In one embodiment, information is provided to the user based on one or more failure messages in order to enable the user to modify their choices. In another embodiment, the initial input is automatically modified. A permitted version modification may be, for example, a version upgrade, a version downgrade, and an indication that there is no preference.

Abstract: Version labeling of an artifact in a version control system. An embodiment can include accepting at least one change set into a configuration for the artifact. Based on the change set, a new version of the artifact can be selected by the configuration. Via a processor, an identifier can be generated for the newly selected version of the artifact. The identifier can include at least a branch name for a branch in which the newly selected version of the artifact is contained and a sequence number for the newly selected version of the artifact. The newly selected version of the artifact can be labeled with the generated identifier.

Abstract: Versions of a model in UML or another modeling language can be published on web feeds, such as RSS or Atom web feeds. A model feed includes a sequence of incremental differences to a base version of a model; the base version can be an empty model or a snapshot of another model feed, for example. Stream charts show the relationship between model feeds. A selected sequence of incremental differences can be applied, in forward or reverse, to animate changes in a model. A developer working on a different computer than another developer can create new model versions which use some elements from a published feed and other elements introduced by the local developer. New model versions and semantic information about the sequence taken to reach them can be shared through web feeds.

Abstract: A method, apparatus and computer program are disclosed for modifying an application comprising a plurality of modules. A user is presented with a list of modules. The user is able to specify input regarding any permitted version modifications for the modules listed. It is then determined whether the requested modifications are possible with one or more failure messages being output when any of the requested modifications are not possible. At least one of the failure messages is used to enable modification of the initial input provided by the user. In one embodiment, information is provided to the user based on one or more failure messages in order to enable the user to modify their choices. In another embodiment, the initial input is automatically modified. A permitted version modification may be, for example, a version upgrade, a version downgrade, and an indication that there is no preference.

Abstract: A system, method, and computer readable medium for script logic graphical mapping comprises displaying a panel associated with at least one script, presenting a branching logic associated with the panel and creating a graphical map of the panel and the branching logic where the graphical map allows zooming in to show panel logic associated with the panel, and the graphical map allows zooming out to show the branching logic associated with the panel.

Abstract: Methods, systems, and apparatus, including computer program products are provided for indexing tags in source code. Implementations provide an enhanced retrieval of source code, in which a score for each of a plurality of files is derived based on a quantity of references to each file in source code of the remaining plurality of files. A query is received identifying a source code tag. Matching files of the plurality of files that satisfy the query are identified, a ranking of the matching files is generated based on the derived scores, and the ranking is provided.

Abstract: A solution for identifying a software developer based on debugging information includes an identification module configured to identify a developer of a line of source code, a determination module configured to determine a developer contact tag for the developer, an encoding module configured to encode the developer contact tag, a tagging module configured to automatically tag the line of source code with the developer contact tag associated with the developer. The solution also includes a debug module configured to provide debug information, a decoding module configured to decrypt the developer contact tag, and a presentation module configured to present the debug stack trace in human readable form.

Abstract: A version file retrieving unit of a game device retrieves via a network a version file including version information identifying an OS recommended for the execution of game software running. An OS version comparing unit compares first version information on the OS running with second version information identifying the OS recommended for the execution of the game software running. When the second version indicates a version newer than that of the first version information, the OS retrieving unit downloads the latest OS and stores it in the hard disk drive.

Abstract: A method may include receiving a request to install a second version of a software product over a first version of the software product, installing the second version of the software product in a dormant state while the first version of the software product is running, and swapping the first and second versions of the software product by activating the second version of the software product and deactivating the first version of the software product. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: A likelihood indicating the distribution of the frequency of use of each specification of the existing device is calculated for each version of a software component used in the control software of the existing device, and a prior probability indicating the distribution of the frequency of use of each version is calculated for each software component used in the control software of the existing device. A posterior probability indicating the reusability of each version of the existing software component is calculated for each specification of a device to be developed, on the basis of the likelihood and the prior probability.

Abstract: Concepts and technologies are described herein for incremental compositional dynamic test generation. The concepts and technologies described herein are used to increase the code coverage and security vulnerability identification abilities of testing applications and devices, without significantly increasing, and in some cases decreasing, computational and time costs associated with the testing. Test summaries that describe how code is tested by a test engine are generated and stored during testing of code. These test summaries can be evaluated when additional iterations or versions of the code are tested. If functions corresponding to the test summaries are unchanged from, or logically equivalent to, a version of the function previously tested, the test summary may be used when testing the new version of the code.

Abstract: Method and apparatus for in-place updating an old version of a file stored on a storage device to form a new version, wherein the old version includes blocks. The form of the old version is determined for indicating at which end of the old version free space is located, as well as determining whether an update package is a corresponding update package for the form. If the update package is a corresponding update package, blocks in the old version are updated according to the update package, giving rise to a new version having an alternative form, where free space in the new version is at an opposite end to the old version.

Abstract: A method, a system and a computer program product for hierarchical program source management retrieve a main program from a memory and initiate a layer representing a portion of the main program for editing on the display. Program code is edited within the layer in response to detected user programming inputs. A layer abstract syntax tree corresponding to the edited program code is generated. The layer abstract syntax tree is compared with a main program abstract syntax tree and a layer file is generated including the differences between the layer abstract syntax tree and the main program abstract syntax tree.

Abstract: A computer method and apparatus for managing revisions to engineered products includes a repository, a local data store (working copy) and a revision manager. Each engineered product is formed of one or more assets. The repository holds the plurality of assets and tracks changes of the assets. For a given asset, the revision manager provides, together in a certain screen view, display of (a) indications of changes made to a working copy of the given asset relative to the given asset as held in the repository, and (b) indications of changes made to the given asset in the repository relative to the working copy of the given asset. The certain screen view in one embodiment employs a tabular format with sortable columns, color coded symbols, textual summaries of changes made to assets and textual description of changes made to assets in the repository.

Abstract: Collaborative program development systems are provided which implement methods for providing automated programming assistance to code developers in a collaborative program development environment. In particular, systems and methods for automated programming assistance are supported by leveraging a database or library of shared code snippets that are classified according to code patterns and rating scores that are derived from feedback and input from various code developers within a collaborative program development environment.

Abstract: Implementations of the present disclosure provide computer-implemented methods including retrieving a predefined configuration model from a plurality of predefined configuration models electronically stored in a configuration repository, the predefined configuration model providing predefined configuration data for a particular software application, comparing the predefined configuration data to existing configuration data of one or more target systems to generate a first delta, a first system landscape including the one or more target systems, determining one or more configuration actions based on the first delta, and executing the one or more configuration actions to update a configuration state of the one or more target systems from an initial configuration state.

Abstract: Embodiments may provide a makefile interposer, which enables a makefile to be used for building software for different platforms without modifying the makefile. In some embodiments, the interposer intercepts the commands run by makefile and automatically interposes the correct library files, dependencies, paths, and other information used by make to build the program for a particular platform. Additionally, calls that the invoked tools themselves make are intercepted and the interposer may redirect them to the platform-specific tools or file system locations including redirecting file descriptors. In some instances, when a tool is called that is not in the platform, the interposer may also fall back on the other system tools.

Abstract: Disclosed is a system and method that resolves a mismatch between software versions executing on redundant controllers. A mismatch between a first software version executing on a first redundant controller and a second software version executing on a second redundant controller is identified. By comparing software version identifiers associated with the first software version, the second software version, and a stored system software identifier, a preferred software version is selected. The preferred software version is copied from a controller running the preferred software version to the other controllers.

Abstract: An aspect of the present invention determines interface differences between different versions of an operating system. In one embodiment, the corresponding images of a first (older) version and a second (newer) version is inspected to identify whether access mechanism of a publicly accessible resource associated with a first interface provided by the first version is changed in the second version. Example of change in access mechanism includes a difference in the signature of function type resources, non-existence or change in the name or location of a file type resource and change in the physical file pointed to by a symbolic link type resource in the second version (as compared to that in the first version). A list of publicly accessible resources that are identified as having changed in the second version is then formed.

Abstract: Software change management (SCM) systems can be extended to uniformly handle artifacts which lack constraints typically imposed on managed items. In the solution, a data type associated with a SCM system can enable management of unmanaged artifacts. Unmanaged artifacts can include, but is not limited to, artifacts which lack can traditional change management constraints, managed artifacts not directly associated with the SCM, artifacts with different constraints than the SCM imposed constraints, and the like. In one embodiment, an unmanaged artifact can have different lifecycles, policies, and the like which can make it unsuitable for traditional management approaches by the SCM. The SCM can utilize the data type to manage unmanaged artifacts without requiring significant change in functionality of the SCM by permitting change management processes to be applied to the unmanaged artifacts.

Abstract: A computer-implemented method of managing work items associated with agile software development includes displaying a first group of incomplete work items associated with a current iteration of an agile software development project. In response to a first user input, a first incomplete work item of the first group is transferred from the current iteration to a subsequent iteration of the agile software development project. A determination is made that no incomplete work items remain associated with the current iteration. The current iteration is closed and the subsequent iteration is activated.

Abstract: The present disclosure discloses embodiments of an apparatus and method for loading codes of cluster-based Java application system. The loading techniques provided by the present disclosure do not need to publish the latest codes to each server in the cluster or restart the Java application in each server of the cluster. The loading techniques only need to update the codes in the codes storage server, such as a SVN server. Each server in the cluster will automatically load the latest codes, thereby improving the usability of the Java cluster system.

Abstract: Work item rules for a work item tracking system are provided. Work item rules may be accessible, usable and subject to interpretation by multiple software entities. Further, work item rules may be configured to be subject to creation and change by users, for example, by exposure to users through a user interface. A work item rule may specify an identifier by which the abstraction can be identified and/or a name, and may specify, or be indicative of, a condition and an action to be taken if the condition is satisfied. In response to a first user action affecting a first work item rule, one or more work item rules corresponding to the first user and/or the first work item may be determined. The one or more work item rules then may be interpreted, and the user action responded to based on the interpretation.

Abstract: A computer-implemented system may include a data store to store business data, an application platform, and a business application. The application platform may include a repository to store metadata defining a plurality of business objects, each of the business objects comprising a respective model of data and associated logic, each business object associated with respective business object entities, and a framework in communication with the repository to provide access to the business data. The business application is to access the data via the framework and based on the metadata, wherein the metadata associates a first plurality of the business object entities with a RELEASED release status code, and wherein the metadata associates a second plurality of the business object entities with a DEPRECATED release status code.

Abstract: A modification method and system. The method includes retrieving by a computer processor of a computing system a list of features and plug-ins associated with an application. The features include features version metadata and the plug-ins include plug-ins version metadata. The computer processor compares features source code associated with the features with previous versions of associated source code. The computer processor generates modified features version metadata associated with the features version metadata. The modified features version metadata includes updated version labels differing from previous version labels of the previous versions of associated source code. The features are assembled into an application.

Abstract: A system that includes: a configuration management system configured to receive resource updates submitted by developers of a product line; an update monitor configured, in manual monitoring, to mark each submitted resource update with respective variability data specified as relevant to the update submission, by the developer; and a tracer configured, in automatic monitoring, to trace portions of the updated resource into respective features or products of the product line, to determine variability data relevant to the update submission, wherein when an update request is initiated by the developer, the configuration management system is configured to associate the submitted resource updates with the update request based on common variability data, to provide resource updates on demand, based on variability data, wherein in automatic update, the configuration management system is configured to notify developers on resource updates, based on variability data common to the updated resource and the notified deve

Abstract: Embodiments of the present invention address deficiencies of the art in respect to defect classification for software development and provide a method, system and computer program product for automated defect classification in a software development tool. In an embodiment of the invention, a defect classification method can be provided. The method can include computing differences between versions of a line of source code, lexically analyzing the computed differences to produce a lexical construct, mapping the lexical construct to a classification, and assigning the defect classification to the line of source code.

Abstract: The present invention discloses a system for generating a software TLM model, comprising a processing unit; a compiler coupled to the processing unit to generate target binary codes of a target software; a decompiler coupled to the processing unit to decompile the target binary codes into high level codes, for example C or C++ codes, to generate a functional model of the target software, wherein the functional model includes a plurality of basic blocks; an execution time calculating module coupled to the processing unit to calculate overall execution time of the plurality of the basic blocks of the functional model; a sync point identifying module coupled to the processing unit to identify sync points of the software transaction-level modeling model; and a time annotating module coupled to the processing unit to annotate the overall execution time of the basic blocks and the sync points into the functional model to obtain the software transaction-level modeling model.

Abstract: A computer method and system dynamically provide consistency of JAVA application files. A processor executed routine is configured (e.g., instrumented as an agent) to intercept each class that is loaded into a subject JAVA application or JVM. The system computes a cyclic redundancy check (CRC) of the respective JAR file surrounding the loaded class. The system compares the computed CRC value to a CRC value of at least one other copy of the respective JAR file. Based on the comparison, the system determines consistency (e.g., same version) of the multiple copies of the respective JAR file used by the subject Java application. If the multiple copies of the respective JAR file are determined to be inconsistent, the system alerts the user and/or enables the application to abort.

Abstract: An information processor includes a first part storing one or more programs included in one or more packages; a second part correlating and retaining the package and version information of the programs on a program basis; a third part comparing, if one of the installed programs is to be installed, the version information of the installed one of the programs and the one of the programs to be installed; a fourth part determining whether the one of the programs to be installed is subordinate to a package other than a package including the one of the programs to be installed, if the version information of the one of the programs to be installed is determined to be lower; and a fifth part installing the one of the programs to be installed if the one of the programs to be installed is determined to be not subordinate to the other package.

Abstract: A computer system identifies a plurality of source code files to be compared, parses each source code file to identify a code statement structure present in the file, and compares the plurality of source code files using corresponding code statement structures.

Abstract: An interface is provided between a running computer application and a system monitor. The system monitor handles notification messages generated by the computer application. The interface includes an import module to scan a source file, extract notification messages from the source file and store the notification messages in a scan file. The interface includes a manager module to display each notification message in the scan file in a table in a graphical user interface to allow modifications to the data in the table. The data is exported to an export stage. The export module performs any translation required to create a file of the notification messages in a format that is acceptable to the system monitor.

Abstract: Embodiments of the present invention provide a system profiler that can be used on any processor architecture. In particular, instead of copying an entire stack every time, the stack is divided into blocks of a fixed size. For each block, a hash value is computed. As stack blocks are sent out of the kernel, the hash value and a copy of the block contents is kept in a user space cache. In the kernel, the hash codes of sent stack blocks are tracked in a table. During system profiling, the kernel module sampling the call stack determines if that stack block was previously sent by checking for the hash value in the kernel table. If the hash matches an entry in the kernel table, then only the hash value is sent. If the hash value is not in the table, the entire block and the hash value is sent.

Abstract: A system for controlling version branching can perform operations including, responsive to a user initiating a check-out operation of a file within a software configuration management system (SCMS), identifying the file and a workspace of the user and searching nodes of the repositories of the SCMS for a successor version of the file. When a successor version of the file is located within a node that is within a predetermined distance of the workspace of the user, a notification that the successor version of the file is within the predetermined distance of the workspace of the user can be output. When a successor version of the file is not located within a node within a predetermined distance of the workspace of the user, the file can be checked-out to the workspace of the user.

Abstract: A processing device executing an integrated development environment scans for available projects, each project having a directory structure that contains source code. The processing device identifies available projects that match predetermined criteria. The processing device then automatically groups the projects that match the predetermined criteria into a working set, wherein projects arranged into the working set are visually presented to a user together, and wherein one or more operations can be performed on every project in the working set based on a single user command.

Abstract: The invention relates to a process for the automatic matching of a control software component to a control unit network in order to permit communication between control software components of the control unit network, whereby the control unit network-independent communication commands of a control software component in the program code are replaced by control unit network-dependent communication commands.

Abstract: A method and system facilitating the development and distribution of software is provided. The system includes tracking revisions to elements of a database on the computing device by establishing time stamps for each stored element changed at a specified time, enabling a user to select an applicable time period comprising a beginning time point and an end time point, and assembling elements for execution based on time stamps limited to the selected applicable time period.

Abstract: A method for allowing selective delivery of changesets by environment includes selecting at least one value in software code of a software program; specifying at least one environment for the selected at least one value; compiling the software code in each specified at least one environment; delivering the software code to a central repository; determining how the specified at least one environment is defined; and choosing at least one environment to build against, thereby ensuring that only software code for the chosen environment is pulled from the central repository.

Abstract: Embodiments of the invention monitor requests for a source code build of a program. The source code build is generated using the most recent applicable release of the dependencies. The source code build is dynamically merged into at least one subsequent release. Other embodiments may be described and claimed.

Abstract: An effective and user-friendly system is disclosed for creating and running a software application for medical imaging, having at least one framework which has a service layer and a superordinate toolkit layer as an application programming interface, wherein functions of the toolkit layer and of the service layer are grouped in each case in a number of components which are arranged strictly hierarchically in such a way that any component can only ever be accessed from a superordinate component.

Abstract: A method for operating an automation system which executes, as an automation solution, a control program having a plurality of software modules, where the method comprises replacing at least one software module comprising an old software module at the runtime of the control program with a new software module wherein the new software module is loaded into a memory of the automation system, an old data area associated with the old software module is compared with a new data area associated with the new software module, program code instructions for converting data for or from the old data area into data for or from the new data area is generated, and a program code instruction for invoking the old software module is replaced with program code instructions for invoking the generated program code instructions for data conversion and for invoking the new software module.

Abstract: A metadata migration tool helps GUI application developers keep track of institutional knowledge that may be lost between application versions. The maintenance and transference of this knowledge from one application version to another aids developers in conforming future applications to restrictions and requirements imposed on previous versions that may not be immediately apparent. The architecture and processes facilitate the migration of this institutional knowledge, thus greatly reducing the time, cost, and resource expenditures spent re-creating similar components in an updated application and updated scripts to test those application components.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for versioning components of an application. These mechanisms and methods for versioning components of an application can ensure that an updated application maintains backwards compatibility, such that the application developer may maintain a single application while supporting multiple prior versions of the application.

Abstract: One embodiment involves a system comprising a network, a server, and a requesting device. The server and requesting device are connected with the network. The server comprises a processor configured to receive a request from the requesting device and determine information about the requesting device based at least in part on the request. The processor is further configured to determine an abstract representation of an application and at least one mapping from a plurality of mappings based at least in part on the information about the device. The abstract representation comprises a plurality of components. Each mapping comprises an attribute for at least one of the plurality of components. The processor is further configured to generate a version of the application on-the-fly based at least in part on the abstract representation and the at least one mapping and send the version of the application to the requesting device.

Abstract: A method, apparatus, and article are provided for managing migration of annotations between versions of source code. Annotations associated with patterns of source code are identified. A comparison of the modified source code is conducted in conjunction with the identified annotations in a prior version of the source code to determine if the annotations may be migrated to any portions of the modified source code. The comparison includes an exact match and a partial match. With respect to the partial match, a threshold value is employed to define the parameters of a partial match. All annotations that are determine to be an exact match or a partial match are automatically migrated to a location in the modified source code determine to match within the threshold value.

Abstract: An apparatus for identifying a contextual change to a source code file, in a development environment, the apparatus including: a detector component for detecting a modification to the source code file; a requester component for retrieving a previous version of the modified source code file; a parser component for parsing a first source code set associated with the source code file and a second source code set associated with the previous version of the source code file and for building an in-memory representation of the first and second source code sets; and a comparator component for comparing the in-memory representation of the first source code set with the in-memory representation of the second source code set in order to generate contextual information identifying a change made to a source code element associated with the modified source code set.