Patent Application
20160170717
A software application is designed to include a number of features. These features may include core functionality, user interface controls, application programming interfaces, internal and external messaging support, etc. Typically, one or more software developers develops program code which implements the desired features, and the code is compiled to generate the software application.
Software applications are updated regularly, and each new release offers a different mix of features than prior versions. Several different versions of a software application may be offered for various usage scenarios (e.g., home, business, etc.), with each version also providing a unique mix of features. Software developers modify the program code of a software application to implement the features required by each version or release. Systems to facilitate this modification are desired.
The following description is provided to enable any person in the art to make and use the described embodiments. Various modifications, however, will remain readily apparent to those in the art.
Any of the depicted elements of architecture 100 may be implemented by one or more hardware devices coupled via any number of public and/or private networks. Two or more of such devices may be located remote from one another all devices may communicate with one another via any known manner of network(s) and/or via a dedicated connection.
Development client systems 120-124 may comprise a desktop computer, a laptop computer, a netbook computer, a tablet computer, a smartphone, and/or any other computing system that is or becomes known. Each of systems 120-124 provides a development environment for developing program code. For example, each of systems 120-124 may include a memory storing program code of an Integrated Development Environment and a processor to execute the code. The code of the Integrated Development Environment may be located remote from systems 120-124 and provided as a service, in which case systems 120-124 execute program code of a client application such as a Web browser.
Development system 110 stores program code of software applications. Development system 110 may also provide compilation functions and/or an Integrated Development Environment as described above according to some embodiments. Accordingly, development client systems 120-124 may utilize functionality provided by development system 110 to develop software applications.
Code bases 112, 114 and 116 represent the core code of respective software applications. Code bases 114 and 116 are associated with development branches. Specifically, code base 114 is associated with a development branch comprising program code 114A and 114A1, and code base 116 is associated with two development branches, one including program code 116A and 116A, and the other including program code 116B. According to some embodiments, one or more developers may create and modify program code stored in development system 110.
Feature planning system 130 may facilitate the planning and management of software application development. Feature planning system 130 may allow developers to create lists of application features, prioritize feature development, distribute the development of features to workgroups, assign features to various software releases, etc. Feature planning system 130 may comprise a computer server which executes program code of a feature planning software application. According to some embodiments, feature planning system 130 is an element of development system 110.
Initially, at S210, program code of a software application is identified. Next, an application feature associated with the program code is identified at S220. According to some embodiments, the application feature is identified first, and associated program code of a software application is then identified. Examples reflecting both scenarios will be described below.
User interface 300 includes feature area 310 and feature information area 320. Feature area 310 includes feature list 312 and control 314, and feature information area 320 displays information relating to a currently-selected feature of feature list 312 (e.g., Radio Buttons). The information displayed in areas 310 and 320 may be provided by feature planning system 130, but embodiments are not limited thereto.
A developer enters program code, in any suitable programming language, into code development area 330. Execution of such program code provides debug output which is displayed in debug output area 340. An integrated development environment according to some embodiments may provide additional controls and features not described herein.
With respect to process 200, a developer may select a feature from feature list 312 and then select Start Coding control 314. Next, as illustrated in
It will be assumed that the developer selects the Associate with Feature option of context menu 334. As a result, window 338 of
Embodiments are not limited to the examples of
Returning to process 200, data associating the program code with an identifier of the application feature is stored at S230. The identifier of the feature may comprise a descriptive and/or technical name of the feature, an alphanumeric ID, or any other suitable identifier. The associated program code may comprise a text file including the program code (which, as described above, may include added and/or deleted program code). The data may be a database table record including fields identifying the feature and the program code. Such a record may include other fields, such as those identifying one or more developers of the program code, a date the feature was added, a software version associated with the feature, etc.
According to some embodiments, the stored data comprises parseable text inserted within the program code itself For example, a developer may place text markers around portions of program code and an identifier of an associated feature within one or more of the markers.
Usage data for features of the software application are collected at S810. The usage data describes the quantity and quality of usage of particular features of the software application. Usage data may be collected for any number and type of application features. For example, the usage data may indicate how often a particular analysis function is used, how often a particular user interface is accessed, how often a user abandons a particular workflow, etc.
The usage data may be collected by the software application as the application executes on a client system and/or an application server. Collection of usage data of many users may be facilitated in a case that the application is served by an application server. In this regard,
System 900 includes a plurality of clients 910. Each of clients 910 comprises a hardware device including a processor for executing a client application such as, but not limited to, a Web browser. Network 920 may comprise any number of electronic networks for transmitting data. In some embodiments, network 920 is the World Wide Web. According to the illustrated embodiment, application server 930 executes the software application, receives data from and transmits data to clients 910, and collects the usage data at S810.
Next, at S820, it is determined whether to remove a feature from the software application based on the usage data. The determination may occur at predetermined intervals, after collection of a particular amount of usage data, upon instruction of an administrator of application server 930, and/or continuously.
It may be determined at S820 to remove a feature for any reason. According to some embodiments, it may be determined to remove a feature if it is rarely used, if it is often used incorrectly, if it impacts performance significantly, if it results in an unacceptable frequency of crashes, etc. In some embodiments, the determination at S820 may be user-specific. That is, it may be determined at S820 to remove a feature from the software application for a particular user or subset of users (e.g., employees of a particular company).
Flow cycles between S810 and S820 to continue to collect usage data until the determination at S820 is affirmative. At this point, flow proceeds to S830 to identify stored data which associates an identifier of the feature with program code. As described above, such data may be stored in development system 940. Accordingly, application server 930 may operate in conjunction with development server 940 at S830 to identify stored data of development system 940 which associates an identifier of the feature with program code. The data may comprise the source code of the software application (e.g., in a case that the feature identifier is embedded in the source code), a database table record, or any other suitable data structure. The program code associated with the identifier may include program code which was added to implement the feature, was deleted to implement the feature, and/or was edited to implement the feature.
Next, at S840, source code of the software application is modified based on the program code. Modification may be performed by development system 940 according to some embodiments. Modification of the source code may include automatic deletion from the source code of program code which was added to implement the feature, automatic addition from the source code of program code which was deleted to implement the feature, and/or automatic reversal of edits made to program code of the source code to implement the feature.
The modified source code is compiled at S850 to generate a modified software application. The modified software application may then be deployed to one or more clients using any suitable deployment paradigm. According to some embodiments, the modified software application is deployed by development system 940 to application server 930, and served to one or more clients 910 therefrom.
Flow returns from S850 to S810 to continue collection of usage data. In this regard, it may be subsequently determined at S820 to remove a second feature from the modified software application, in which case flow proceeds as described above to identify stored data associating an identifier of the second feature with second program code, to modify the source code of the modified software application based on the second program code, and to compile the modified source code of the modified software application to generate a second modified software application.
Apparatus 1000 includes processor 1010 operatively coupled to communication device 1020, data storage device 1030, one or more input devices 1040, one or more output devices 1050 and memory 1060. Communication device 1020 may facilitate communication with external computing systems, such as via a computer network. Input device(s) 1040 may comprise, for example, a keyboard, a keypad, a mouse or other pointing device, a microphone, knob or a switch, an infra-red (IR) port, a docking station, and/or a touch screen. Input device(s) 1040 may be used, for example, to enter information into apparatus 1000. Output device(s) 1050 may comprise, for example, a display (e.g., a display screen) a speaker, and/or a printer.
Data storage device 1030 may comprise any appropriate persistent non-transitory storage media, including combinations of magnetic storage devices (e.g., magnetic tape, hard disk drives and flash memory), optical storage devices, Read Only Memory (ROM) devices, etc., while memory 1060 may comprise Random Access Memory (RAM).
Integrated development environment 1032 of data storage device 1030 may comprise program code executable by processor 1010 to provide any of the functions described herein, including but not limited to processes 200 and 800. Embodiments are not limited to execution of these functions by a single apparatus. Data storage device 1030 may also store data and other program code for providing additional functionality and/or which are necessary for operation thereof, such as device drivers, operating system files, etc.
Code bases and branches 1034 may include source code of one or more software applications. The source code may also include data associating features of the software applications with program code. Moreover, feature associations 1036 may also or alternatively include data associating features of the software applications with program code.
All systems and processes discussed herein may be embodied in program code stored on one or more computer-readable non-transitory media. Such non-transitory media may include, for example, a fixed disk,a floppy disk, a CD-ROM, a DVD-ROM, a Flash drive, magnetic tape, and solid state RAM or ROM storage units. Embodiments are therefore not limited to any specific combination of hardware and software.
Embodiments described herein are solely for the purpose of illustration. Those in the art will recognize other embodiments may be practiced with modifications and alterations to that described above.
