Abstract: A system and method for creating transparent and easily maintainable information systems is implemented through a configuration oriented programming paradigm. The information system is implemented by identifying specific needs in a top-down Analysis phase and directly mapping them to a Configuration of the information system in a similar top-down approach.

Abstract: A mobile information application is generated for use with a mobile information tool on a mobile computing device platform. A reader framework for integrating with one or more platform-independent documents is generated from a platform-independent document generator, and the platform-independent documents are imported into an integrated development environment project. A mobile information application is generated with an application generator from the integrated development environment project, and deployed on one or more mobile computing devices associated with the mobile computing device platform.

Abstract: Provided are a tool for supporting open computing language (OpenCL) application software development for an embedded system and a supporting method thereof. The tool in conjunction with a target system includes a project management unit configured to separate and store OpenCL application software constituted of a host program and a kernel program into a host source code corresponding to the host program and a kernel source code corresponding to the kernel program, and manage a tool-chain corresponding to an OpenCL platform of the target system, and a builder configured to determine a compile type of the kernel source code and determine whether the kernel source code is built in response to the compile type. Accordingly, it is possible to rapidly provide a tool for supporting OpenCL application software development that can develop OpenCL application software for an embedded system.

Abstract: Quality of modularization of source code is tested using different perspectives such as a structural modularity perspective, an architectural modularity perspective, a size perspective, and a similarity of purpose perspective. A history of changes in modularization may be kept such that the degree to which given source code is well-modularized can be determined over time. The changes made to the code by individual programmers may be kept, such that the degree to which their coding enhanced or harmed modularization may be tracked.

Abstract: Dynamic memory management configuration enables certain behavior of an application to be controlled without touching or affecting any executable portion of the application.

Abstract: Engineering team activities are facilitated through social networked collaboration driven by engineering project events. An engineering team member profile on a private network contains an identification of the team member including an offline name, direct links to profiles of other team members, automatically generated news items of team member engineering activities, and a summarized view of engineering project data. A news generator automatically collects engineering events and includes corresponding event descriptions in the profile, for wiki article updates, software bug reports, software modifications, project schedule changes, and other engineering events. Some news items automatically include a suggested engineering activity as a follow up for the team member to perform. For example, the team member may click a news item link to view an updated product specification, create a product test, view detailed test results, or create a virtual machine session.

Abstract: A method and system for an open application programming interface (API) dashboard system for monitoring and managing one or more developer programmed applications configured to use one or more services provided by a service owner are provided. The system includes an application area associated with a corresponding programmed application, each application area including a call metrics group configured to display summarized metrics, a services used group configured to display a listing of each service called by the programmed application and metrics associated with each service, and a key management group configured to prompt a developer of the programmed application to request or revoke a key, wherein the key includes a developer identification, a programmed application identification, and signed certificates relating to services used by the programmed application.

Abstract: A method of managing agile software development includes displaying a group of assets associated with an agile software development process. The group has a particular type and the assets include a first set of attributes selected for display. In response to detecting a request by a first user, a group of available attributes is displayed including the first set. De-selection of an attribute from the first set is detected. For other users accessing respective groups of assets of the particular type, the first set of attributes is displayed for assets in the respective groups, wherein the first set does not include the deselected attribute.

Abstract: Configuration requirements that specify the provision of services using a system-level description are automatically generated from user requirements. The user requirements are decomposed into one or more levels of decomposed functionalities using an ontology as input. The ontology stores known decompositions of functionalities and relations between the known decompositions. The lowest level of the decomposed functionalities is mapped into a set of components provided by vendors, and additional components on which the set of components depend are identified. Based on the set of components and the additional components, a required number of instances of service workload is calculated to generate the configuration requirements of the system that satisfy the user requirements.

Abstract: Techniques for open application lifecycle management frameworks are described, including using a framework hosted on one or more computers and having one or more services to integrate the one or more services with one or more applications using one or more providers, each of the one or more providers is adapted to at least one of the one or more applications, registering one or more repositories associated with the one or more applications using a location service module, receiving an input creating a project context associated with a project, data associated with the input being stored in a data structure associated with the project, the data structure being stored in a repository associated with the framework, generating a link, after registering the one or more repositories, between one or more element containers associated with the project, the link and the one or more element containers being stored in the repository, and configuring the framework to detect another input indicating interaction with an ar

Abstract: A computer system is provided, comprising: a transceiver; and a processor configured to facilitate: collecting and storing information related to a software project having one or more software artifacts, the information including: a project identifier, artifact identifiers for the artifacts used by the project, information about the temporal version for the artifacts, and contact information for a project user; collecting, from a repository, artifact metadata associated with the software artifacts, the artifact metadata including: information identifying the artifact, information about security risks associated with the artifact, information about a license associated with the artifact, or information indicative of a level of use or user rating of the artifact; periodically monitoring the metadata to determine whether there has been any actionable change in the artifact metadata; and notifying the project user using the contact information if it is determined that there has been an actionable change in the ar

Abstract: This invention relates to a method and apparatus for developing software. In one embodiment, a method for facilitating the distributed development of software components includes providing a skill rating for software developers, communicating specifications for a software component to a subset of the developers, receiving submissions from the developers, scoring the submissions, and selecting one submission to be included in a software repository. In another embodiment, a method for compensating a software developer includes soliciting software developers for the submission of computer software components, receiving software components in response to the solicitation from the developers, evaluating the received software components, selecting one or more of the submissions for potential distribution to the public, and allotting the proceeds from the distribution to the developers.

Abstract: A method, system, and/or computer-readable medium analyzes problems in a software factory. Factory metrics that describe resources and operations within the software factory are collected and analyzed to detect problems that might have occurred during an execution of a work packet within the software factory. If the detected problems exceed one or more threshold criteria, then a detailed analysis of the detected problems is performed by matching each detected problem to one or more specific root causes through an analysis of the factory process building blocks.

Abstract: A target amount of effort to spend on requirements of a software development project may be determined. A visualization can be displayed comparing the target amount of effort to an actual amount of effort spent on the requirements. In an example, the effort may be represented as time.

Abstract: A system and a method associated with a system landscape having a plurality of independent systems are provided to determine a refactoring object associated with modification of at least one code-based object and transport the refactoring object to a set of independent systems in the system landscape where each independent system is coupled to a communications network. Furthermore modifications of code-based objects are arranged to be performed at each of the set of independent systems in the system landscape.

Abstract: A method includes creating an initial test plan including initial estimates of effort and defect distributions, creating an alternative test plan including alternative estimates of effort and defect distributions, and displaying at least one metric of the initial test plan and the alternative test plan side by side for comparison by a user.

Abstract: A method and system is provided for estimating size and effort of software assurance project for distributing the estimated effort across the software assurance project phases. Particularly, the invention provides a method and system for estimating the software assurance project size based on the predefined weight ratios assigned to the test cases after classifying them into simple, medium and complex categories. Further, the invention provides a method and system for utilizing the estimated software assurance project size and organizational baseline productivity information for estimating the software assurance efforts. Further, the invention provides a method and system for distributing the estimated effort across the software assurance project phases.

Abstract: An embodiment of the invention produces software documentation that includes first and second sections. Skills a technical writer needs are determined, wherein preparation of the first and second sections require different skill sets. A database is searched to select technical writers qualified to prepare each of the multiple document sections, wherein the database contains the identities and qualifications of persons qualified to be technical writers. Preparation of the first and second sections are then assigned to first and second writers having first and second skill sets, respectively. Each prepared section is validated for incorporation into the software documentation.

Abstract: Configuration requirements for an Availability Management Framework (AMF) configuration are generated from high level user requirements that specify a subset of properties of an AMF configuration. The user requirements are first mapped into entity prototypes defined in an extended Entity Types File (ETF) model. A computer system identifies additional entity prototypes and dependency thereof that support functionalities of the mapped entity prototypes under a set of grouping conditions. The computer system calculates the required number of component service instances (CSIs) and service instances (SIs) that satisfy the user requirements. The calculation is based on the subset of the properties specified by the user requirements and measurements associated with the entity prototypes in the extended ETF model. The computer system then forms configuration requirements including the required number of CSIs and SIs for generating the AMF configuration that satisfies the user requirements.

Abstract: As provided, a method for capital expenditure/expense flip targeting and balancing in software pipeline management that includes providing, for each of multiple projects in a software project pipeline, a set of inputs that includes 1) resource demand, 2) budget constraint, 3) start date, and 4) a capital expenditure/expense flip date. The method also includes aggregating the inputs. The method further comprises calculating an overall capital expenditure/expense ratio, and comparing the ratio to a threshold as of a predetermined date.

Abstract: Retrieving a question regarding requirements of an application from a data object node of an architecture design solution repository with architecture design solutions comprising a plurality of data object trees each with a plurality of data object nodes. Displaying a question regarding the requirements of the application to an application user through an interface and receiving an indication of an answer chosen by the application user. Indicating within the data object node which answer was chosen by the application user and determining which data object node to retrieve a next question from based on answer indicated by the user. Determining which architecture design solution within the architecture design solution repository matches the requirements of the application indicated by the application user and generating an architecture design work product based on matching the data object nodes to architecture design solutions within the architecture design solution repository.

Abstract: Resource tracker techniques are described in which resource trackers may be generated, assigned to resources, and used to track resources throughout a development environment. The resource trackers may be configured in a designated format that is suitable to distinguish different resources one from one another. In one approach, resource trackers are derived as a combination of a user-supplied project identifier and defined resource identifiers. Resource trackers may be embedded into code defining corresponding resources and exposed to identify resources in connection with various development operations. In an embodiment, the resources trackers may be employed to provide visual indications of resources that appear within a user-interface for a project that is output for testing. A developer may identify resources based on resource trackers exposed via the user-interface and navigate back to underlying code in various ways to address any issues identified through the testing.

Abstract: Computer method and apparatus manage requests to make changes to a given software system (e.g., application program or program portion). The invention method and apparatus form a change request object representing a user's request to make a change to the given software system. The invention method and apparatus form one or more hierarchies of objects and sub-objects to represent work to be performed and work performed in making the requested change. One embodiment creates a root issue object for each change request object and allows a user to partition an issue object into issue sub-objects. The embodiment (a) allows a user to create a task object to define the work needed to address an issue and allows a user to partition a task object into task sub-objects, and (b) allows a user to create an activity object to track work performed and allows a user to partition an activity object into activity sub-objects. Issue objects and issue sub-objects are relatable to task objects and task sub-objects.

Abstract: Examples of a continuous deployment system are provided that manage and track releases of software code, where some or all of the steps between check-in and deployment to production can be automated. Such systems can reduce the amount of developer effort needed to deploy a package, as developers may not have to be responsible for scheduling package builds, clicking deployment buttons, or manually running tests. The system can take care of all or some of that work.

Abstract: A method and system for generating an application programming interface (API) request message for an API service application is provided. The API service application is stored within a service owner (SO) computer device and includes a memory device for storing data and a service provider (SP) computer system that includes a processor and an open API platform. The SP computer system in communication with the memory device and the SO computer device. The SP computer system is programmed to receive from a developer a plurality of selections of parameters defining an API service request, generate an API request message for a specific API service using the received parameter selections, the API request message including the received parameter selections in a predetermined format required by the specific API service, generate a response to the generated API request message, and display the generated API request message and response on a single webpage.

Abstract: A framework (referred to herein as Application Integration Architecture, or AIA) that formalizes and orchestrates activities in an SOA development lifecycle. In one set of embodiments, AIA can capture development-related information in a shared data store and cause the information to flow in an automated or semi-automated manner from one lifecycle phase to the next as the lifecycle progresses. This information flow can, in turn, facilitate automations at each lifecycle phase for the responsible stakeholders (e.g., solution architects, developers, installation developers, etc.), thereby enforcing SOA best practices, enhancing development productivity, and ensuring the quality of the final SOA deliverables.

Abstract: A recording medium readable by an information processing apparatus, has recorded thereon a monitoring program for monitoring an operation status of a monitoring target program that runs on an information processing apparatus having a processor and a memory. The monitoring program causes the information processing apparatus to obtain, at a time of installation of a program, information indicating a status where the program is executed in the information processing apparatus and becomes a monitoring target program. The program monitors, on the basis of the information obtained, whether the monitoring target program exists in a memory in which the monitoring target program has been loaded.

Abstract: A method and system for throttling a volume of request messages to a service application stored within a service provider (SP) computer system through an open application programming interface (API) platform is provided. The SP computer system is in communication with a memory device. The method includes storing a throttling profile for a developer application within the memory device wherein the throttling profile includes at least a throttling amount threshold and a throttling time period, receiving at the API platform a request message initiated by the developer application wherein the request message is included within a volume of request messages initiated by the developer application, identifying the request message as being associated with the developer application, retrieving the throttling profile for the developer application, and validating the volume of request messages as complying with the throttling profile.

Abstract: Techniques for integrating software applications include identifying an enterprise application executable in a first computing environment, where the enterprise application is compatible with a first version of a network application executable in a second computing environment so that a first set of functionality of the first version of the network application is exposed through the enterprise application. The features include identifying a second version of the network application executable in the second computing environment. The second version of the network application includes a second set of functionality at least partially distinct from the first set of functionality. The features include delivering an integration component from the second computing system to the first computing system.

Abstract: A computer-implemented method for managing a social process of developing an application includes: making an integrated development environment accessible to a user; exposing a work product of the user in the integrated development environment to a selected group of users; receiving, in the integrated development environment, a first input regarding the work product from at least one of the selected group of users; and presenting the first input to the user in the integrated development environment.

Abstract: According to one general aspect, a method of managing a web browser extension by an apparatus may include executing, by a processor included by the apparatus, a web browser. The method may include installing on the apparatus, via the web browser, a web browser extension. In one embodiment, the web browser extension may include at least one web page configured to alter the functionality of the web browser, and a substantially unique identifier (UID) based upon a public encryption key. The method may further include launching, via the web browser, the web browser extension based upon the substantially unique identifier.

Abstract: A method for automatically provisioning a platform implementation package to a client device may include receiving from an application executing on the client device, a request for functionality. The request may be received via a client library distributed with the application, and may be for functionality provided by the platform implementation package. The platform implementation package may provide functionality that is not provided by the client library. It may be further automatically determined, by the client device, that the functionality requires an update to the platform implementation package. In response, a request for the update to the platform implementation package may be communicated to a computing system. The update to the platform implementation package may be received from the computing system and installed on the client device. The requested functionality may be provided to the application by the updated platform implementation package.

Abstract: Disclosed are systems, methods, and devices for providing cloud-based indexing services to cloud-based and client-based software development environments. For example, integrated development environment (IDE) services may be provided at a client device via a cloud-based indexing service, and an indexing request related to source code at least partially loaded at the client device transmitted to the cloud-based indexing service with respect to a type of indexing request selected from a code completion request, a usages request, an annotations listing request, and a refactoring request. The cloud-based indexing service may then access one or more indexes maintained at the cloud-based indexing service, and provide responsive index information to the client device, the index information included in the responsive index information being less than all index information from the one or more indexes corresponding to the source code at least partially loaded at the client device.

Abstract: A computer system interacts with a software development environment to enable a software developer to submit one or more software projects to a submission portal for analysis. A processor obtains needed files associated with a software project and then may proceed to compile the artifacts based on compile parameters in order to generate additional artifacts typically containing at least one binary file but that may be dependent on a type of the software project. The configuration data may be created independently of a build environment of the software project. The computer system may then archive artifacts of the software project that may be compressed and uploaded to an analysis tool. The submissions portal can then determine whether the submitted code is complete. The submitted code can be further analyzed by a static analysis engine, where the results are presented to the developer.

Abstract: A computer implemented method, system, and/or computer program product assigns work to a software factory for implementing a project. A project model of a project is generated. Project model subcomponents are mapped to work packets that are available to a software factory, thus leading to the generation of a work plan for performing the project via an execution of the available work packets.

Abstract: A method for improving execution efficiency of a software package customization is disclosed. The method includes identifying one or more components from a configuration table to implement at least one of a use case flow or a non functional requirement (NFR) or an interface document or combinations thereof derived using an use case of the software project, sequencing the identified one or more components to prioritize execution of the use case of the software project and attributing complexity of the identified one or more components to determine the effort estimation for execution of the use case. Attributing complexity includes using an unit effort table for determining the effort estimation requirement for execution of each component of the use case. The method further includes identifying a usage type, attributing the reuse level and resolving the dependencies among the identified components.

Abstract: A method and program product to monitor the activities of a named person for developing a computer program. The method comprises the steps of logging operations performed by a software build tool or software test tool, a record in the log for each of the operations comprising an identity of a person that requested the operation and a time stamp of the operation; identifying the activities of the named person; determining that the named person is currently accessing the software build tool or software test tool; querying the log records with a time stamp within a predetermined period to determine that the named person has used the software build tool or software test tool to develop the computer program within the predetermined period; and reporting to the user that the named person used the tool to develop the computer program within the predetermined period.

Abstract: An artifact update notification system that includes a server computer and client computer is discussed and described. The server computer stores artifact preferences, determined according to objective and subjective criteria, of artifact characteristics. The client computer executes a software development environment that makes use of a software artifact. The server computer and client computer interact to perform an update cycle. The update cycle includes the server computer communicating to the client computer whether there is an actionable change to the software artifact with respect to the artifact preferences. If there has been an actionable change to the software artifact, the client computer performs an update action in the software development environment in response to the actionable change.

Abstract: Embodiments of the present invention provide a method, system and computer program product for melding mediation and adaptation modules of a service component architecture (SCA) system. A method for melding mediation and adaptation modules of an SCA system can include selecting each of a mediation module and an adaptation module in an integrated development tool executing in memory by a processor of a computer and loading respectively different descriptor files for each of the mediation module and the adaptation module. The method further can include combining descriptors from the different descriptor files into a single descriptor file for a melded module. Finally, the method can include modifying names and wiring descriptors in the single descriptor file for the melded module to account for a combination of the mediation component and the adaptation component in the melded component.

Abstract: A system may include acquisition of metadata defining a first object model, the first object model comprising an instance of a metaobject, acquisition of enhancement object metadata defining one or more enhancements to the first object model and associating each of the one or more enhancements with one of one or more stable anchors of the first object model, and creation, based on the metadata defining the object model and the metadata defining the one or more enhancements, of metadata defining an extended object model, the extended object model comprising an instance of the metaobject.

Abstract: A method to shape one or more features of Web 2.0 in the form of Web 2.0 solutions, using Web 2.0 realization framework, to the plurality of enterprises is disclosed. The method includes identifying the respective enterprises computing infrastructure and a business application needs of the respective enterprises. The respective enterprises current support system is also measured to find the feasibility of implementing the features of the Web 2.0. The method further comprises offering one or more Web 2.0 features to the respective enterprises based on the business activity. The method includes providing the Web Realization Cycle (WRC) for controlled implementation of Web 2.0 features to the respective enterprises.

Abstract: Techniques are provided for capturing the ID of a work item, and the corresponding effort level information, as a part of the actual check-in process of the artifacts into the underlying change management system. This effort information can then be propagated to an external system for subsequent reporting and analysis. In one embodiment, tasks (or similar items such as issues or bugs) are entered into a common task or issue tracking system. As part of this process each task is assigned a unique identifier. A “call-out” is added to the source control management system which captures the effort level and task ID associated with the proposed change. The data entered is validated to ensure that the task ID is valid and that the effort entered is within a valid range. If the data entered is valid, the change to the underlying artifact is allowed to proceed and the effort and task information is stored for later analysis.

Abstract: A set of tools and other mechanisms automatically enforce software development change policies by providing a way to map physical source control system codelines to projects and by providing a way to maintain current project and codeline state information. The set of tools and other mechanisms also provide ways to define change management rules and policies, as well as, ways to evaluate and allow or deny each proposed change against the defined change policy.

Abstract: A method and system of marking the deprecation status of components, such as services, processes, operations, and data types that may be used in a computing application, and displaying this status to developers within the computing application is provided. Components may be marked as deprecated, or they may include information reflecting a sunset policy, which consists of either a specific date or an upcoming version number of the application or programming language the computing application supports. The sunset policy determines when a component has reached its end of life and is either no longer supported or will be removed from the underlying product. Using this deprecation status information, the computing application may be configured to dynamically notify developers of when components will be deprecated. The computing application may further be configured to provide automated migration support by recommending alternative components and assisting in their configurations.

Abstract: A method is implemented in a computer infrastructure having computer executable code tangibly embodied on a computer readable storage medium having programming instructions. The programming instructions are operable to receive a maturity level for an organization and select at least one defect analysis starter/defect reduction method (DAS/DRM) defect profile based on the maturity level. Additionally, the programming instructions are operable to determine a projection analysis for one or more stages of the life cycle of a software code project of the organization based on the at least one DAS/DRM defect profile.

Abstract: Embodiments of the present invention provide a method, system and computer program product for melding mediation and adaptation modules of a service component architecture (SCA) system. A method for melding mediation and adaptation modules of an SCA system can include selecting each of a mediation module and an adaptation module in an integrated development tool executing in memory by a processor of a computer and loading respectively different descriptor files for each of the mediation module and the adaptation module. The method further can include combining descriptors from the different descriptor files into a single descriptor file for a melded module. Finally, the method can include modifying names and wiring descriptors in the single descriptor file for the melded module to account for a combination of the mediation component and the adaptation component in the melded component.

Abstract: Validating executable data for interactions among a plurality of process artifacts at design time. A data context is created to include the plurality of process artifacts. The data context carries interaction rules among the plurality of process artifacts. The executable data from a data source is associated with the plurality of process artifacts in the created data context. A subset of the interaction rules is selected corresponding to at least one of the plurality of process artifacts. The associated executable data is validated when the associated executable data is in accordance with the selected subset of the interaction rules.

Abstract: A system and associated method for generating a Service Component Architecture (SCA) module with Service Oriented Architecture (SOA) model elements. A service model is created according to a process model that has activities and a process flow. Services of the service model are respectively associated with the activities. Each service is determined to employ only one service operation definition to render a message specification of a respective activity that is associated with each service. The activities, the process flow, and the message specification are utilized to produce the SCA module in executable implementations.

Abstract: A method of task management for shared artifacts can include detecting a change tag associated with a software artifact and determining, via a processor, each software artifact that is dependent upon the software artifact. A task associated with each dependent software artifact can be generated. Each task can specify a need for a modification to the associated software artifact. A responsible party for each dependent software artifact can be determined. Each task can be automatically assigned to the responsible party for the software artifact associated with the task.

Abstract: Elastic computing is an optimization framework that combines standard application code with specialized elastic functions and corresponding optimization tools. The elastic functions provide a knowledge-base of implementation alternatives and parallelization strategies for a given function. When an application calls an elastic function, the elastic computing tools analyze available devices and resources (e.g., cores, GPUs, FPGAs, etc.) and current run-time parameters, and then transparently select from numerous pre-analyzed implementation possibilities to optimize for performance, power, energy, size, or any combination of these goals.