# US 2014/0157226 A1 · Multi-context remote development > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0157226 A1 - Document ID: US20140157226A1 - Status: Published application - Kind: A1 - Application number: 13/692,486 - Filed: 2012-12-03 - Published: 2014-06-05 - Earliest claimed: 2012-12-03 - Assignees: International Business Machines Corporation - Applicants: International Business Machines Corporation - Inventors: David W. Dykstal; Mike S. Fulton; Dave K. McKnight; Kushal S. Munir; Rick L. Sawyer; Eric V. Simpson - Web page: https://patentgrep.com/patent/US20140157226A1 ## CPC - G06F 8/70: Software maintenance or management - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method implemented by a processor and a system develop a software project targeting one or more remote systems. The method includes generating a project on a local system, which includes receiving user input through a user interface. The project includes one or more source files. The method also includes generating one or more remote contexts corresponding to the one or more remote systems. ## Claims ### Claim 1 A method implemented by a processor to develop a software project targeting one or more remote systems, the method comprising: generating, using the processor, a project on a local system, the generating the project including receiving user input through a user interface and the project including one or more source files; and generating one or more remote contexts corresponding to the one or more remote systems. ### Claim 2 (depends on 1) The method according to claim 1, wherein the generating the one or more remote contexts includes a user creating or modifying the one or more remote contexts through the user interface. ### Claim 3 (depends on 1) The method according to claim 1, further comprising synchronizing one or more of the one or more remote contexts with the project, the synchronizing including determining a synchronization state which indicates pending changes and conflicts between the project and the respective remote context. ### Claim 4 (depends on 3) The method according to claim 3, further comprising storing the synchronization state in association with each of the one or more of the one or more remote contexts and displaying the synchronization state for each of the one or more of the one or more remote contexts one at a time. ### Claim 5 (depends on 3) The method according to claim 3, further comprising storing the synchronization state in association with each of the one or more of the one or more remote contexts and displaying the synchronization state for the one or more of the one or more remote contexts together. ### Claim 6 (depends on 3) The method according to claim 3, wherein the synchronizing includes resolving issues indicted by the synchronization state for the project and the respective remote context. ### Claim 7 (depends on 6) The method according to claim 6, wherein the resolving the issues includes pushing changes in the project to the remote context, pulling changes in the remote context to the project, and addressing conflicts between the project and the remote context using the user interface. ### Claim 8 (depends on 1) The method according to claim 1, further comprising building the project to run on one or more of the one or more remote systems using build information in the corresponding remote context of the one or more of the one or more remote systems. ### Claim 9 (depends on 8) The method according to claim 8, further comprising storing the build information in association with each of the one or more of the one or more remote contexts and displaying the build information for each of the one or more of the one or more remote contexts one at a time. ### Claim 10 (depends on 8) The method according to claim 8, further comprising storing the build information in association with each of the one or more of the one or more remote contexts and displaying the build information for the one or more of the one or more remote contexts together. ### Claim 11 A software development environment to develop a software project targeting one or more remote systems, the system comprising: a development application implemented by a processor, the development application facilitating the generation of a project; a remote context subsystem implemented by the processor, the remote context subsystem facilitating the generation of one or more remote contexts corresponding with the one or more remote systems; and a memory device configured to store the project and the one or more remote contexts. ### Claim 12 (depends on 11) The system according to claim 11, wherein the memory device stores source code included in the project. ### Claim 13 (depends on 11) The system according to claim 11, wherein the memory device stores synchronization state information corresponding with each file of each of the one or more remote contexts. ### Claim 14 (depends on 13) The system according to claim 13, further comprising a synchronization module implemented by the processor, wherein the synchronization module synchronizes the project with each of the one or more remote systems using the respective synchronization state information. ### Claim 15 (depends on 11) The system according to claim 11, further comprising a communication module communicating with the one or more remote systems, wherein the communication module receives build information for a build of the project on one or more of the one or more remote systems. ### Claim 16 (depends on 15) The system according to claim 15, wherein the build information is stored in association with the corresponding remote context.