Patent Abstract:
A module validation system and methods are disclosed for use with graphical user interfaces provided by a workstation that, among other things, remotely monitor and/or control game and/or gaming devices and/or systems. Validation of modules used in shells that provide graphical user interfaces enables the module validation system to provide users with varying levels of access to a gaming system.

Full Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
     This application claims benefit under 35 U.S.C. 119(e) of U.S. Patent Application Ser. No. 61/115,690 filed Nov. 18, 2008 and entitled “Module Validation,” which is incorporated herein by reference in its entirety. 
    
    
     COPYRIGHT NOTICE 
     A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. 
     BACKGROUND 
     1. Technical Field 
     The present disclosure relates to validation of software modules in a software system, and in particular to module validation for ensuring the integrity of a software module in systems where modules may be provided by different groups. 
     2. Description of the Related Art 
     Software systems have been developed which use software modules to perform functions. As systems have become more complicated, different groups, sometimes within an organization and sometimes across different organizations, develop software modules for performing functions which are important to and within the competence of the group. Systems have been developed which integrate software modules from across different groups into a unified whole executable application. Such systems enable new features and functionality, maximize code reuse, improve user interface design, maximize efficiency and exploit talents and strengths of the different groups, enable collaboration among the groups, improve interoperability, and enable visual and non-visual software parts to be built, assembled, and deployed by independent teams on independent schedules. 
     However, in such systems, it is possible that during the integration process, one or more modules may not be in correct condition to be integrated into the whole executable application. For example, a module may have been modified, altered or tampered with. It is desirable to ensure that all modules to be integrated into the executable application are valid before integrating them into the executable application. 
     SUMMARY 
     In accordance with principles of the disclosure, software modules are validated at runtime. The validation process verifies that the software module has not been modified since it was installed in the executable application. Such a process may also enforce licensing restrictions. 
     A computer implemented method of providing security to a workstation having a processor and a processor-readable storage medium with a plurality of modules stored therein, the plurality of modules consisting of a first number (N, where 1&lt;N) of modules, may be summarized as including executing a user-interface application with the processor of the workstation, the user-interface application being stored in the storage medium and having an application shell for at least a second number (M, 1&lt;M≦N) of modules, the second number of modules consisting of modules of the plurality of modules, and the application shell providing a desktop window on a display device; and for each one of the second number of modules, retrieving a respective module of the second number of modules from the storage medium and a corresponding respective authentic module validation indicator from a database of the user-interface application, the database stored in the storage medium, calculating a respective comparison module validation indicator based at least on the retrieved respective module, comparing the comparison module validation indicator with the authentic module validation indicator, and loading the respective retrieved module in the application shell only if the comparison module validation and the authentic module validation indicator are the same. 
     The method may further include determining whether a first user is authorized for a respective module of the plurality of modules; and preventing the respective module from being loaded in the application shell if the first user is not authorized for the respective module. Determining whether the first user is authorized for a respective module of the plurality of modules may include receiving authentication information indicative of whether the first user is or is not authorized for the respective module from a remote server; and determining whether the first user is or is not authorized based at least on the received authentication information. 
     The method may further include retrieving a respective user profile from a plurality of user profiles stored in the storage medium of the workstation, the plurality of user profiles including a respective user profile of the first user and at least a respective profile of at least a second user; and determining whether the first user is authorized for a respective module of the plurality of modules based at least on the respective profile of the first user. 
     The method may further include, prior to retrieving a corresponding respective authentic module validation indicator, decrypting a first password stored in the storage medium, and opening a first connection to the database from which the respective authentic module validation indicator is retrieved based at least on the first password. 
     The method may further include associating a first password with the first user; encrypting the first password; and storing the encrypted first password in the storage medium, wherein the encrypted first password stored in the storage medium is one of a plurality of encrypted passwords, the plurality of encrypted passwords including a second encrypted password being associated with the at least second user. 
     The method may further include determining whether the second user is authorized for a respective module of the plurality of modules based at least on the respective profile of the second user. 
     The method may further include, prior to retrieving a corresponding respective authentic module validation indicator, decrypting a second password stored in the storage medium, and opening a second connection to the database from which the respective authentic module validation indicator is retrieved based at least on the second password. 
     A networked gaming system may be summarized as including a network; a plurality of gaming machines coupled to the network; and a workstation communicatively coupled to the plurality of gaming machines via the network, the workstation comprising at least one processor and at least one processor-readable storage medium that stores a user-interface application having an application shell, a plurality of modules for the application shell, the plurality of modules consisting of a first number (N, where 1&lt;N) of modules, and instructions that cause the at least one processor to provide a respective graphical user interface, by: initializing the application shell for at least a second number (M, 1&lt;M≦N) of modules in response to input from a respective user of the plurality of users, the second number of modules consisting of modules of the plurality of modules; and for each respective module of the second number of modules, determining whether a respective user of the plurality of users is authorized for the respective module of the second number of modules, determining whether the respective module of the second number of modules is valid, and loading the respective module in the application shell only if both the respective module is valid and the respective user is authorized for the respective module. 
     The networked gaming system wherein the at least one processor-readable storage medium stores instructions that cause the at least one processor to provide a respective graphical user interface, wherein determining whether the respective module of the second number of modules is valid includes retrieving the respective module of the second number of modules from the storage medium and a corresponding respective authentic module validation indicator from a database of the user-interface application, the database stored in the storage medium; calculating a respective comparison module validation indicator based at least on the retrieved respective module; and comparing the comparison module validation indicator with the authentic module validation indicator, wherein the respective module is valid only if the comparison module validation indicator and the authentic module validation indicator are the same. 
     The networked gaming system wherein the at least one processor-readable storage medium stores instructions that cause the at least one processor to provide a respective graphical user interface, wherein determining whether a respective user of the plurality of users is authorized for the respective module of the second number of modules includes receiving authentication information indicative of whether the respective user is or is not authorized for the respective module from a remote server, and determining whether the first user is or is not authorized based at least on the received authentication information. 
     The networked gaming system wherein the at least one processor-readable storage medium stores instructions that cause the at least one processor to provide a respective graphical user interface, further by retrieving a respective user profile from a plurality of user profiles stored in the storage medium of the workstation; and determining whether the respective user is authorized for a respective module of the plurality of modules based at least on the respective profile of the respective user. 
     The networked gaming system wherein the at least one processor-readable storage medium stores instructions that cause the at least one processor to provide a respective graphical user interface, further by: decrypting a password stored in the storage medium and associated with the respective user; and opening a connection to the database from which the respective authentic module validation indicator is retrieved based at least on the password. 
     The networked gaming system wherein the at least one processor-readable storage medium stores instructions that cause the at least one processor to provide a respective graphical user interface, further by: associating the password with the respective user; encrypting the password; and storing the encrypted password in the storage medium, wherein the encrypted password stored in the storage medium is one of a plurality of encrypted passwords, each one of the encrypted passwords being associated with another respective user. 
     A module validation system that validates modules used by a shell application providing a graphical user interface may include a processor-readable storage medium having a database and a plurality of modules stored therein and at least one client database having a respective authentic module validation indicator associated with a respective module included therewith; and a database module enumerator that retrieves a list of modules available for use by a respective user, and for each module in the list of modules, compares a respective comparison module validation indicator with a respective authentic module validation indicator, and loads the respective module in a shell only if the respective comparison module validation indicator and the respective authentic module validation indicator are the same. The database module enumerator may generate the respective comparison module validation indicator based at least on a respective corresponding module stored in the storage medium. The database module enumerator may generate the respective comparison module validation indicator based at least on a secure hash function. 
     The module validation system may further include a database installer that installs the at least one client database in the storage medium. 
     The module validation system may further include a module installer that installs the modules in the storage medium. 
     Other features and numerous advantages of the various embodiments will become apparent from the following detailed description when viewed in conjunction with the corresponding drawings. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a class diagram of a logging class structure, according to one illustrated embodiment. 
       FIGS.  2  and  2 - 1  are a class diagram of a security class structure, according to one illustrated embodiment. 
         FIG. 3  is a transaction diagram of a security process, according to one illustrated embodiment. 
         FIG. 4  is a schematic diagram of a system having an installer application and a Desktop application, according to one illustrated embodiment. 
         FIG. 5  is a transaction diagram of a database creation process, according to one illustrated embodiment. 
         FIG. 6  is a transaction diagram of a Data Retrieval process from a database, according to one illustrated embodiment. 
         FIG. 7  is a transaction diagram of a validation process, according to one illustrated embodiment. 
         FIG. 8  is a transaction diagram of a process for storing and retrieving user profiles, according to one illustrated embodiment. 
         FIG. 9  is a transaction diagram of a Multilanguage provisioning process, according to one illustrated embodiment. 
         FIG. 10  is a class diagram of a Status Bar functionality, according to one illustrated embodiment. 
         FIG. 11  is a transaction diagram of a Status Bar functionality order, according to one illustrated embodiment. 
         FIG. 12  is a schematic diagram of a database schema, according to one illustrated embodiment. 
         FIG. 13  is a screen print showing a top level window or screen of a graphical user interface, according to one illustrated embodiment. 
         FIG. 14  is a screen print showing a window or screen of a graphical user interface for a user to specify user settings, according to one illustrated embodiment. 
         FIG. 15  is a screen print showing a window or screen of a graphical user interface for providing information about an executable application, according to one illustrated embodiment. 
         FIG. 16  is a schematic diagram of a module validation system, according to one illustrated embodiment. 
         FIG. 17  is a block diagram of a computing system, according to one illustrated embodiment. 
     
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     A software system in which embodiments may be implemented is described below. 
     The software system is loaded into a storage medium of a computer system such as a commercially available Bally control panel or workstation or Bally Desktop computer station, personal computer etc. The software system includes a Desktop application such as a commercially available Bally Desktop application that employs Client Framework architecture. The Desktop application and Client Framework enables the consolidation of the myriad of software products into a single User Interface (UI). It provides usability to users while creating a custom user experience depending upon the users&#39; security role and the installed products. 
     The Desktop&#39;s loosely coupled and modular architecture make it easier to extend and maintain and enables new capabilities to be deployed to customers incrementally, while minimizing downtime. This modularity enables independent development and QA cycles between independent development teams. 
     The Desktop executable application increases productivity, quality, and the consistency of development, while reducing the overall development time by providing a central UI infrastructure, and enabling independent teams to focus on domain-specific business logic. It increases the reusability between independent teams by providing proven solutions to common client UI development challenges. 
     As used herein: Modular Design means the application is composed of loosely coupled parts which allows for the modular construction of the application. A UI framework is a prefabricated software infrastructure which enables this loose coupling. An Application Shell is a container that hosts user facing functionality provided by one or more Modules. Business logic is logically separated into Modules or Plug-ins based on the business logic that is implemented. Modules can be developed independently by independent teams. 
     The Desktop application is a UI development platform/framework that provides a consistent look and feel to Client UI screens while maximizing code reuse. The following are some of the architectural goals considered during the design of the Desktop Architecture: (a) Create reusable source-code components that provide proven solutions to common development challenges; (b) Provide a modular architecture that enables independent development cycles between development pods; (c) Deploy multiple functional UI&#39;s with a consistent look and feel; (d) Dynamically load UI elements based on user/role assignments; (e) Create a central infrastructure for security, Data Access, Logging, Web Service Interfaces, etc.; (f) Employ an infrastructure for common architecture patterns like the Model View Controller, Model View Presenter, Publish/Subscribe, or Command Pattern; (g) Enable Windows Presentation Foundation (WPF) development; (h) Provide a transition plan from Win32 forms based development to WPF; and (i) Separate the design and developer roles. 
     A composite pattern is developed and chosen to enable the manipulation of UI elements in a homogeneous fashion. A Smart Client—Composite UI Application Block (CAB) was developed as the composite pattern implementation starting point for the Desktop application as it provides a proven infrastructure for the composite pattern. 
     A Smart Client Software Factory (SCSF) is developed and chosen to help provide guidance for the Desktop application&#39;s implementation of the composite pattern. The SCSF provides a collection of reusable components, templates, wizards, architectural documentation and patterns, and implementation references. In general the SCSF provides the Desktop application with a high quality starting point for implementing the composite pattern. 
     Logging in the Desktop application is provided as a service. There are different levels of messages that can be logged depending on the severity of the messages. Following is the list of the severity level in descending severity order: 
     1. Error 
     2. Warn 
     3. Info 
     4. Verbose 
       FIG. 1  shows a Logging process class structure  100 , according to one illustrated embodiment. A Logger is capable of logging to an Event Recording System (ERS) database, a local File and/or an Event Viewer. The Logger may be configured to behave differently by changing the Application Config file. 
     The Desktop framework also provides security functions, such as authentication, authorization and module validation. 
     FIGS.  2  and  2 - 1  show a security class structure  200 , according to one illustrated embodiment. 
       FIG. 3  shows a transaction diagram of a security process  300  in a Desktop application, according to one illustrated embodiment. As a shell application  302  is run or initiated, the shell application  302  runs a Composite UI Application Block (CAB) application  304 . The CAB application  304  calls an authenticate method implemented by the ClientAuthenticationService  306 . The ClientAuthenticationService  306  provides a UserLogonService  308 , which displays a Login dialog to the user. The user enters his credentials, such as user name and password. The credentials are now sent to a SecurityProvider Service  310 , which in turn sends it to an AuthWeb Security Service  312  for authentication. 
     In some embodiments, the AuthWeb Security Service  312  may be implemented by a remote computing system or server. 
     If the authentication fails then the user is informed and the Login dialog reappears. If the user credentials are authenticated then an EnumerateModules method of DatabaseModuleEnumerator  314  is called, which fetches the respective names of the modules to be loaded from a local Desktop Database  316 . The user operations corresponding to each module that needs to be loaded are added, and the operations that are permitted for the current user are authorized. The ClientAuthenticationService  306  may call the SecurityProvider Service  310 , which may in turn call the AuthWeb Security Service  312  for authorization of the current user for each one or selected ones of the modules. Based on the permitted operations, a decision is made whether a respective module will be loaded or not for some or all of the fetched modules. Below are two conditions under which a module is not loaded: 
     1. If a user has no operation permission on a given module. 
     2. If a validation check fails. This is described in more detail below. 
     Discussed below is an exemplary method for preventing unauthorized users from accessing the database  316 . 
       FIG. 4  is a schematic diagram of a system  400  having an installer  402  and components of a Desktop application, according to one illustrated embodiment. The Desktop application includes a client application  404 , at least one client configuration file  406  and at least one client database  408 . The client application  404 , the client configuration file  406  and the client database  408  are stored in a storage medium of a user&#39;s workstation. The installer  402  is an application that installs the Desktop application on the user&#39;s workstation (not shown). The installer  402  is a separate program from the Bally Desktop Client. The Installer  402  is responsible for creating the application database  408  and its assets. 
     The client database  408  may be a local database which may be used by the Desktop application and/or Desktop application components, e.g., client application  404  to store and retrieve data. 
       FIG. 5  is a transaction diagram of a database creation process  500 , according to one illustrated embodiment. An installer  502  installs a client application  504 . The client application  504  may be one or more portions of the Desktop application and/or the Desktop application. The client application  504  may be an update to one or more portions of the Desktop application and/or an update to the Desktop application. 
     The installer  502  gets a user to provide a password. The password may be different from a password to logon to the user&#39;s workstation. The installer  502  creates a client database  506  for the client application  504 . The installer  502  may create the client database  506  based at least on the password. 
     The installer  502  may create a client configuration file  508 , and may encrypt the password and write the encrypted password to the client configuration file  508  file. This encrypted password is used by a Desktop Client application to connect to database  506 . The installer  502  creates tables in the database  506  and adds the appropriate data to them. The installer  502  may store a key used to encrypt the password in the client database  506 . 
       FIG. 6  is a transaction diagram of a data retrieval process  600 , according to one illustrated embodiment. A client application  602  such as a Desktop Client, reads an encrypted password from a configuration (config) file  604 , and based on a key stored with the client application such as a Desktop Client, the client application  602  decrypts the password. The key may be stored in a client database  606 . The client application  602  may use this password to open a connection with the client database  606  and start reading data. Among other things, the retrieved data may include module validation indicators, which are indicative of a module being valid. Module validation indicators may be stored in client database  606  in encrypted form. 
       FIG. 7  is a transaction diagram of a validation process  700 , according to one illustrated embodiment. A validator application  702  such as DatabaseModuleEnumerator validates the module by retrieving an authentic module validation indicator for the module from a client application database  704  such as a Desktop Client. The authentic module validation indicator may be stored in the client application database  704  as part of an installation or updating process. The authentic module validation indicator may be, among other things, a hash value. The validator application  702  may calculate a comparison module validation indicator (using Secure Hash Algorithm 1 (SHA1)) of the assembly file (corresponding to the module) in a storage medium  706  of the user&#39;s workstation. The validator application  702  may compare the comparison module validation indicator with the authentic module validation indicator retrieved from the database  704 . If these values match, then the module is considered validated. If the values don&#39;t match, then the module is considered not validated. If not validated, the module is not loaded into the client application, such as a Desktop Client. 
       FIG. 8  is a transaction diagram of a storing and retrieving process  800 . Profile settings in the Desktop application are stored in a local database  802  by a shell application  804 . The shell application  804  calls a SettingService  806  for storing the settings. Two types of settings may be saved: User Settings and Application Settings. User Settings are settings that may be saved for a user of a module. Every user setting has a user and a module associated with it. Application Settings are settings which apply to a module, and therefore, such settings have a module associated with them, but not a user. A ‘getter’ and a ‘setter’ function are provided for both types of settings. The behavior of the ‘setter’ function is such that, if a user tries to set a setting which does not exist, the setting is created. 
       FIG. 9  is a transaction diagram of a Multilanguage provisioning process  900 , according to one illustrated embodiment. A user sets “Regional Settings” via a Client System  904  to a desired Locale. The Client System  904  may provide a control panel for the user to set the “Regional Settings.” An exemplary control panel is a commercially available Bally control panel provided by a Bally Desktop application. When a shell  906  is initialized, the shell retrieves an initial locale indicator from the operating system (OS). The shell  906  calls a SettingsService  908  and sets a CurrentCulture and a CurrentUICulture of a Current Thread. The localization (CurrentUICulture) is also set to the Locale of the client system  904 . As a user logs in, the Desktop application searches the database for any localization override for the user. If an override is found, a language specified in the override data is set as the localization for this user. If an override is not found, the Desktop application continues to operate with the current settings. The Shell  906  reads a resource File  910  corresponding to the CurrentUICulture and gets all the appropriate resources and populates the UI. As the shell  906  starts loading modules  912 , a respective module detects the shell&#39;s locale data and the respective module sets its Locale accordingly. 
     A Status Bar is added to the RootWorkItem&#39;s UIExtensionSite. A status panel is added to this status bar which is shared by all the modules and the Shell. This status panel is also added to the RootWorkItem&#39;s Item collection (to facilitate the retrieval of the object in different modules). Each view generated by the Desktop SCSF Guidance package provides a way to add a message to the status bar. Every view also has a state variable to hold the last displayed message by the view, which facilitates the framework to show status messages relevant to the view in context. 
       FIG. 10  is a class diagram of a Status Bar functionality  1000  and  FIG. 11  is a transaction diagram of Status Bar functionality order  1100 . In  FIGS. 10 and 11 , a framework is modified such that every time a view is shown in a workspace such as in a control panel or a window provided by a user interface. Referring to  FIG. 11 , a shell  1102  calls a View  1104 . The View  1104  calls a StatusPanel  1106 , which may employ a method OnViewActivate( ). 
     In one embodiment, all views generated by a Desktop SCSF package implement an IViewActivate interface. A Desktop SCSF Guidance package also implements this function in a Generated View class where the Desktop SCSF Guidance package loads the Last Displayed Message by the View to the Status Bar. 
       FIG. 12  is a schematic diagram of a database schema  1200 , according to one illustrated embodiment. The database schema  1200  may be employed by the client database  408  (see  FIG. 4 ). The database schema  1200  includes three tables. A first table, Module table  1202 , which includes columns containing data representing each module. Illustrated columns include ModuleID; Name; ApplicationServerName; AssemblyFile; HashCode and a Permitted flag. A second table, UserSettings table  1204 , includes columns containing data representing user settings. Illustrated columns include SettingID, Key, Value, UserLogin, and ModuleID. A third table, AppSettings table  1206 , includes columns containing data representing application settings. Illustrated columns include SettingID, Key, Value, and ModuleID. One skilled in the art understands that other tables may be defined and used by the system, and that other columns may be defined for the tables illustrated in  FIG. 12 . The UserSettings table  1206  includes settings that may be saved for a user of a module. The AppSettings table  1206  includes settings which apply to a module and which do not apply to a user. 
       FIGS. 13 through 15  are respective screen prints of graphical user interface (GUI) windows generated and used by a system for interacting with a user. 
     Referring to  FIG. 13 , a top level window or screen  300  of a graphical user interface (GUI) is shown. The window  1300  is generated by a module. In  FIG. 13 , a Test Module  2  generates a View 1  view  1302  or a subwindow of window  1300 . A tabbed interface  1304  enables a user to select a first tab entitled “Test Module 2  Tab  1 ,” which provides the illustrated view, or a second tab entitled “Test Module 2  Tab  2 ,” which provides a different view (not shown). A task bar may also provide another interface that enables a user to select various views. 
       FIG. 14  is a screen print showing window or screen  1400  of a graphical user interface for a user to specify user settings, according to one illustrated embodiment. Referring to  FIG. 14 , a user may use screen  1400  to specify user settings such as language and for allowing a user to ask for help, log off, or exit the executable application. 
       FIG. 15  is a screen print showing window or screen  1500  of a graphical user interface for providing information about an executable application, according to one illustrated embodiment. Referring to  FIG. 15 , the screen  1500  may be an ‘about’ page. The screen  1500  may include a text box  1502  that lists the processes associated with this running instance of the application, for example: shell, TestModule 1  and TestModule 2 . 
       FIG. 16  is a schematic diagram of a module validation system  1600 . Referring to  FIG. 16 , the module validation system  1600  includes a database installer  1602 , a module installer  1604 , and a client database  1606 . The database installer  1602  installs or creates the client database  1606  and/or configuration files  406  (see  FIG. 4 ) in a storage medium. The module installer  1604  installs or stores modules  1608  in the storage medium, and the installed  1608  modules may be selectively available to users. 
     When modules  1608  are installed (see  FIG. 6 ), an authentic module validation indicator such as a hash code is generated by the module installer  1604  based on the assembly file of the module  1608 . This authentic module validation indicator or hash is stored in the client database  1606 . When the Desktop is invoked, a shell  1610  accesses a database module enumerator  1612  to retrieve a list of modules  1608  available for use by the user. When modules  1608  are loaded (see  FIG. 7 ), the authentic module validation indicator or hash previously stored in the client database  1606  is retrieved from the  1606  database by the database module enumerator  1612 ; and a comparison module validation indicator or generated hash is generated of the module currently being considered. The authentic module validation indicator or hash retrieved from the client database  1606  is compared to the comparison module validation indicator or generated hash of the version of the module requested for installation. If the authentic module validation indicator or hash matches the comparison module validation indicator or generated hash, then the module is deemed valid and the module is installed and made available to the user. If the authentic module validation indicator or hash does not matches the comparison module validation indicator or generated hash, then the module is deemed invalid and the module is not installed. 
     Referring to  FIG. 17 , a block diagram of a computing system  1700  is shown, according to one illustrated embodiment. The computing system  1700  may include, among other things, a memory  1702 , a processor  1704 , and input/output (I/O) devices  1706 , which are connected by a bus  1708 . 
     The memory  1702  may include, among other things, any one or combination of volatile memory elements such as a read-only memory (ROM) and a random access memory (RAM). The random access memory (RAM) may include dynamic random-access memory (DRAM), static random-access memory (SRAM), synchronous dynamic random-access memory (SDRAM), flash RAM, etc. 
     The memory  1702  may store one or more logic modules or logic routines, each of which may comprise an ordered listing of executable instructions for implementing logical functions. In particular, the memory  1702  stores an operating system  1710  and, among other things, software such as module validation logic  1712  and modules  1714  such as a Desktop Module, for example Bally Desktop, with a user interface (UI) and Enterprise Environment module. The execution of the operating system  1710  by the processor  1704  essentially controls the execution of other logic, such as the desktop application software and provides scheduling, input-output control, file and data management, memory management, and communication control and related services. 
     The memory  1702  may also store databases  1716  of various ones of the modules  1714 , authentic module validation indicators  1718 , configuration files,  1720 , user profiles  1722 , and a respective password  1724  for one or more users of the computing system  1700 . A user&#39;s password  1724  and/or user profile may be used in determining which ones of the modules  1714  the user is authorized to access or use. A user&#39;s password may also be employed in opening a connection to a respective module or modules  1714 . 
     The processor  1704  may be a device for executing software, particularly that stored in the memory  1702 . The processor may be a custom made or commercially available processor, a central processing unit (CPU), a semiconductor based microprocessor (in the form of a microchip or chip set), or generally any device for executing software instructions. 
     In some embodiments, the processor  1704  may execute one or more of the modules  1714  to provide a user of the computing system  1700  with a user interface such as a graphical user interface. One or more of the modules  1714  may be loaded into a shell that provides the user interface. In some embodiments, the processor  1704  may execute the validation logic  1712  at a time before loading a respective module  1714  into a shell such as, but not limited to, during bootup of the computing system  1700 , during a login procedure, and/or during an initialization period of an application or module. 
     The I/O devices  1706  include, among other things, a computer mouse, keyboard, input pad, display devices, touch screens, and speakers. 
     While the example embodiments have been described with relation to a gaming environment, it will be appreciated that the above concepts can also be applied to any system in which modules and/or plugins are installed at run-time in an executable application. 
     The foregoing description, for purposes of explanation, uses specific nomenclature and formula to provide a thorough understanding of the embodiments of the invention. It should be apparent to those of skill in the art that the specific details are not required in order to practice the invention. The embodiments have been chosen and described to best explain the principles of the invention and its practical application, thereby enabling others of skill in the art to utilize the invention, and various embodiments with various modifications as are suited to the particular use contemplated. Thus, the foregoing disclosure is not intended to be exhaustive or to limit the invention to the precise forms disclosed, and those of skill in the art recognize that many modifications and variations are possible in view of the above teachings.

Technology Classification (CPC): 6