Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/60—Software deployment
  • G06F8/61—Installation
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/60—Software deployment
  • G06F8/61—Installation
  • G06F8/63—Image based installation; Cloning; Build to order
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/70—Software maintenance or management
  • G06F8/71—Version control; Configuration management
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements

Definitions

• Embedded devices are typically single application devices. In order for the application to work properly on the embedded device, the operating system of the embedded device must support all the features of the application. Many times, when an application is integrated into the operating system image for an embedded device, dependencies exist in the application that are not supported in the operating system image. For example, the application might need to render video and therefore need a system component, such as video player, to do so.
• a system for creating an operating system image for an embedded device includes an operating system base module including an operating system for the embedded device, a software application module, the software application module including one or more software applications that are programmed to execute on the embedded device, and an analysis program module programmed to identify dependencies in the one or more software applications.
• the system also includes a components module including one or more components that are added to the operating system base, and a mapping module programmed to map the dependencies to one or more components from the components module.
• an integrated development system for creating an operating system image for an embedded device includes an operating system base module including an operating system for the embedded device, and a software application module including one or more software applications that are provided in one or more formats.
• the system also includes an analysis program module including one or more analysis programs that are programmed to analyze the software applications to determine operating system dependencies in the software applications, a components module including one or more components that are programmed to be added to the operating system, a user interface module that permits the selection of the formats and the components, and a dependency processing module that executes the analysis programs to analyze the software applications and map the dependencies to the components that are displayed on the user interface.
• a method for creating an operating system image for an embedded device using an integrated development system includes: identifying a software application to be executed on the base the operating system base; selecting a format for the software application from a user interface of the integrated development system; performing a dependency analysis on the software application using one or more analysis programs included in the integrated development system; determining operating system dependencies from the dependency analysis; mapping the dependencies to one or more components to be added to the operating system base; displaying the one or more components on the user interface; adding the selected components to the operating system base and adding the software application to the operating system base.
• Figure 1 shows an example system for creating an operating system image for an embedded device.
• Figure 2 shows an example system for creating an operating system image for an embedded device using an integrated development system.
• Figure 3 shows an example user interface for a system for creating an operating system image for an embedded device using an integrated development system.
• Figure 4 shows a flow chart for an example method for creating an operating system image for an embedded device using an integrated development system.
• the present application is directed to systems and methods for building an operating system image for an embedded device.
• the systems and methods use dependency analysis programs to determine operating system dependencies for one or more software applications running on the embedded device. Operating system components are identified that can be added to the operating system image to resolve these dependencies.
• the analysis programs can be run alone or as part of an integrated development system.
• Figure 1 shows an example system 100 used to build a customized operating system image on an embedded device.
• the example system 100 includes an operating system base module 102, a software application module 104, an analysis program module 106, a components module 108, a mapping module 110, and a build module 112.
• the end result of the build is a customized operating system image 114.
• the example operating system base module 102 includes an operating system base used for embedded systems such as, for example, the WINDOWS® Embedded CE or XP Embedded operating systems provided by Microsoft Corporation of Redmond, Washington. Other operating systems can also be used.
• the operating system base is a shell of the full operating system that contains basic functions such as a kernel, a file system, core components, etc.
• the software application module 104 includes one or more software applications that run on an embedded operating system such as, for example, a point-of-sale (POS) application that runs on a POS device.
• the software application module 104 may require support in the operating system from one or more system components. Such requirements are called dependencies.
• the software application module 104 might require an audio capability which, in turn, would require the addition of a media component to the operating system base module 102.
• some other example dependencies include, without limitation, a web browser used to render documents formatted in the hypertext markup language format, and a firewall used to limit connections to and from the embedded device.
• the analysis program module 106 is programmed to analyze and identify the dependencies associated with the software application module 104.
• One example of such an analysis program is Dumpbin.exe, which is a command-line tool that can be used to identify the dependencies associated with the software application module 104.
• Dumpbin.exe analyzes the structure of binary files and dynamic link libraries.
• an analysis program such as Depends.exe, which is programmed to scan the software application module 104 and determine any dependencies associated with it that would prevent the software application from operating properly.
• Such analysis programs are typically static programs that can be run alone or within the context of an integrated development system, such as the VISUAL STUDIO® development system provided by Microsoft Corporation.
• the dependencies in the software application that are discovered by the analysis program module 106 are mapped to operating system components that are used to resolve the dependencies.
• the components are included in example components module 108.
• the mapping is performed by mapping program module 110.
• Some examples of operating system components include a web browser such as: the INTERNET EXPLORER® internet browser provided by Microsoft Corporation; a media component such as the WINDOWS MEDIA® player; and a firewall component, such as Windows firewall. Other examples of components are possible.
• the mapping program module 110 can be programmed to map the dependencies to the components by the can be accomplished using a variety of techniques.
• the dependencies are mapped using lists, tables, databases or any other data structure.
• a table is used to map the dependencies.
• One example table that can be used is a hash table that includes a data structure that associates keys with values.
• the hash table includes a list of possible dependencies, and maps the dependencies to one or more system components that meet the dependencies. Other configurations are possible.
• the build module 112 is used to build an operating system image using the identified operating system components.
• the end result of this process is an operating system image 114 that satisfies the dependencies in the software application module 104.
• the customized operating system image 114 can be embedded in an embedded device, such as a POS device, to operate the device in a desired environment.
• Figure 2 shows an example integrated development system 200 that is used for building an operating system image for an embedded device.
• One example of such an example integrated development system is the VISUAL STUDIO® development system.
• Other tools can also be used.
• the development system 200 is a stand-alone tool used to identify dependencies, map the dependences to system components, and/or create a customized operating system image, as described further below.
• the integrated development system 200 includes the operating system base module 102, the software application module 104, the analysis program module 106, the components module 108, and the build module 112.
• the example integrated development system 200 also includes a user interface module 210, a dependency processing module 212, a build module 214, and a test and design module 216.
• the example user interface module 210 generally permits the user to control identification of dependencies, mapping the dependences to system components, and creating a customized operating system image.
• the user interface module 210 permits a user to select a format for the software application module 104.
• One of several formats can be selected including a binary file, a source code file, and an install file.
• the example user interface module 212 also provides a display of components that can be added to the operating system base module 102.
• the example dependency processing module 212 runs the one or more analysis programs on a software application, identifies operating system dependencies in the software application, and maps the dependencies into operating system components that resolve these dependencies. In some embodiments, the dependency and processing module 212 automatically adds the identified operating system components to a list of operating system components and builds a new operating system image based on these components. In other embodiments, the identified components are presented to a user via the user interface module 210 and the user selects the components to be added.
• the build module 214 is used to build the operating system image.
• the built operating system image is then tested by the test and design module 216 to determine if any additional dependencies exist in the operating system.
• the test and design module 216 includes analysis programs that analyze the operating system image created by the build module 112. Because the operating system image can include both software and hardware dependencies, the test and design module 216 can be programmed to discover new dependencies that the dependency processing module 212 may have missed.
• the example test and design module 216 identifies any new operating system dependencies and also identifies operating system components that can resolve these dependencies. In some embodiments, the test and design module 216 automatically adds the identified operating system components to a list of operating system components and builds a new operating system image based on these components. In other embodiments, the identified components are presented to a user via the user interface module 210 and the user selects the components to be added.
• FIG. 3 An example user interface 300 generated by the user interface module 210 is shown in Figure 3.
• the example user interface 300 includes a section 302 for selecting the format of the software application, and a section 304 for selecting components.
• the example section 302 includes checkboxes for selecting the file format of a software application. Included is a checkbox 306 for a binary file format, a checkbox 308 for a source file format and a checkbox 310 for an install file format. [0028]
• the example components section 304 includes checkboxes for selecting system components to satisfy dependencies.
• the components section 304 lists such components as: a proprietary user interface 312 such as, for example, the WINDOWS® XP operating system interface provided by Microsoft Corporation; a checkbox 314 for a media player; a checkbox 316 for a web browser; a checkbox 318 for a firewall; and a checkbox 320 for network framework such as, for example, the.Net framework provided by Microsoft Corporation.
• a proprietary user interface 312 such as, for example, the WINDOWS® XP operating system interface provided by Microsoft Corporation
• a checkbox 314 for a media player such as, for example, the WINDOWS® XP operating system interface provided by Microsoft Corporation
• a checkbox 314 for a media player
• a checkbox 316 for a web browser
• a checkbox 318 for a firewall
• a checkbox 320 for network framework such as, for example, the.Net framework provided by Microsoft Corporation.
• Other components are possible.
• one or more checkboxes in the section 304 may be automatically checked by the integrated development system 200 to select the components identified by the dependency processing module 212 to resolve dependencies in the software application.
• the user may select additional components by manually checking one or more of the checkboxes in the section 304.
• the systems 100, 200 and the user interface 300 are implemented on one or more computer systems.
• the systems 100, 200 include a processing unit and computer readable media.
• the computer readable media can include memory such as volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination thereof.
• the systems 100, 200 can include mass storage (removable and/or nonremovable) such as a magnetic or optical disks or tape.
• An operating system and one or more application programs can be stored on the systems 100, 200. Other configurations are possible.
• Figure 4 is a flowchart illustrating an example method 400 for creating an operating system image for an embedded device using an integrated development system.
• the integrated development system is generally used to build operating system images for a specific embedded operating system platform.
• a software application is identified for adding to the operating system platform. This may be done, for example, by opening a project file in the example integrated development system and selecting a software application.
• the file type for the software application is selected such as, for example, a binary file, a source code file or an install file. The selection may be done on the user interface of the integrated development system by selecting a checkbox corresponding to the appropriate file type. Alternate methods of selection are possible such as, for example by using a project file in the integrated development system.
• the user can select other parameters as well.
• the integrated development system is programmed to handle multiple types of operating systems, such as the WINDOWS® Embedded CE or XP Embedded operating systems.
• the user can select which operating system is desired prior to the analysis of the software application.
• one or more analysis programs included in the integrated development system are run against the software application to determine if there are any operating system dependencies in the software application.
• the identified dependencies are mapped to operating system components that are used to resolve the dependencies.
• the identified operating system components are then displayed on the user interface of the integrated development system at operation 410.
• the integrated development system may display the identified components, for example, by checking a checkbox for the component on the user interface.
• the user chooses to accept the identified components, deselect a component or manually select additional components. Once the user is satisfied with the selection, the software application is added to the operating system base at operation 414 and the operating system image is built at operation 416.
• the built image is tested to determine if additional dependencies exist.
• the integrated development system may include additional test and analysis programs that test the build operating system image from the standpoint of the operating system hardware.
• the test and analysis programs may identify additional components that may be added to further adjust the operating system image.
• these additional components may be added to the operating system image. The addition of these components may be done automatically may the integrated development system or may be added manually by the user.
• the operating system image is rebuilt on the integrated development system.

Landscapes

• Engineering & Computer Science (AREA)
• Software Systems (AREA)
• Theoretical Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Computer Security & Cryptography (AREA)
• Stored Programmes (AREA)

Priority Applications (3)

Applications Claiming Priority (2)

Publications (2)

Family

ID=40999634

Family Applications (1)

Country Status (7)

Families Citing this family (10)

Family Cites Families (20)

• 2008
  • 2008-02-26 US US12/037,635 patent/US20090217259A1/en not_active Abandoned
• 2009
  • 2009-01-07 TW TW098100399A patent/TW200937287A/zh unknown
  • 2009-01-21 JP JP2010548756A patent/JP2011513833A/ja active Pending
  • 2009-01-21 WO PCT/US2009/031469 patent/WO2009108416A2/en not_active Ceased
  • 2009-01-21 KR KR1020107018555A patent/KR20100124726A/ko not_active Ceased
  • 2009-01-21 CN CN200980106990.4A patent/CN101960419B/zh not_active Expired - Fee Related
  • 2009-01-21 EP EP09715834A patent/EP2263148A4/en not_active Withdrawn

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events