This application is a U.S. National Stage Application of and claims priority to international Patent Application No. PCT/US2013/067517, filed on Oct. 30, 2013, and entitled “TECHNOLOGY RECOMMENDATION FOR SOFTWARE ENVIRONMENT,” the entire content of which is hereby incorporated in its entirety.
Over the past few years, an increasing number of technologies and frameworks for web and mobile development has been explored and researched, such as a software application for a mobile device or a personal desktop computer, or any kind of a computing device. This booming development leads to a variety of choices for a developer or a business to develop a new software application.
For a detailed description of various examples, reference will now be made to the accompanying drawings in which:
The use of software applications for web sites, mobile devices and desktop computers has gained attention in recent years. To stay abreast with the trend, a large number of technologies to develop such software applications have increased. More specifically, to develop a software application, there are a variety of choices on technologies to use, such as the type of device on which the application is to execute, an operating system, whether real time tracking of online data is desired, etc. However, in order to develop a software application to help guide the decisions on the various technology components on which the application may be based, a developer may resort to consulting colleagues, investigating online forums, and searching online libraries. Because of the large number of technological resources, it may be time-consuming for the developer to develop the software applications, and thus economically wasteful for a business. The disclosed implementations provide an efficient design for developers to develop software applications by receiving a developer's requirements to develop the software applications, or so called software environment, and to automatically recommend a software technology choice to use to develop the software application.
The client device 102 may be implemented as a computer (e.g., laptop, desktop, etc.) and may be used to develop an application to be run on the target device 104. The client device 102 interacts with the server 106 to receive technology recommendations on which to base the application to be developed. In the example shown in
In some embodiments, the technology recommendations may include a software framework, a software development language, a software protocol, and a software platform, which provide a guide to the user to develop the application. As such, the user may follow the guide and develop the application according to the user's requirements at an economic cost, thus making the development more efficient for the developer and the corresponding business.
Referring to
The knowledge base 108 may include any suitable type of online library, forums, or database, which may continuously update the latest technologies associated with software application development, and/or may be manually updated by the users or developers.
The server 106 is configured to analyze the input from the user against the knowledge base 108, and generate a report to be transmitted to the client device 102. The report provided by the server 106 includes a technology recommendation for the user to use for developing the software application.
As shown in
Further, the processor 302 is configured to execute a plurality of software modules (e.g., parameter input module 306, parameter transmission module 308, technology recommendation reception module 310) stored in the non-transitory, computer-readable storage device 304, to implement the functions described herein as attributed to the client device 102. More particularly, the processor 302 is configured to execute the parameter input module 306 to receive a parameter from the user, which indicates a feature of a software environment for the software application to be developed by the user. The processor 302 also executes the parameter transmission module 308 to transmit the received parameters to the server 106. Still more particularly, the technology recommendation reception module 310 is executed by the processor 302 to receive the technology recommendation provided by the server 106 and to provide (e.g., display) the recommendation to the user of the client device 102. In some implementations, the modules 306-310 may be implemented as standalone software modules. The modules 306-310 may be combined together as a one piece of software in other implementations. Further still, the software modules 306-310 may be implemented as a web browser.
For the server 106 to generate a technology recommendation for the user, the server 106 acquires various pieces of information about the intended application and does so by traversing through the query tree 400. The type of information inquired from the user at each level of the tree depends on the user's response to the preceding level of the tree. For example, at the top-most level of the query tree 400, the leaf nodes 402, 404 and 406 may be associated with a question soliciting the type of device on which the user would like to execute the software application to be developed, and the questions may be provided in the form of a multiple choice questionnaire. For example, the leaf node 402 may correspond to the device type as to be used on a website (e.g., web server). The leaf node 404 may correspond to the device type being a mobile device (e.g., smart phone), while the leaf node 406 may correspond to the device type being a desktop computer. Based on the user's answer to the question regarding device type at the top-most level of the query tree 400, the server 106 analyzes the answer and guides the user to the next level. For example, if the user would like to develop an application for a mobile device as the target device 104, the user so specifies to the server 106. Based on the chosen answer, the server 106 branches to the next level which may include three leaf nodes 408, 410 and 412 corresponding to three choices for a second question pertaining to the type of operating system to be run on the intended mobile device.
Subsequently, using the given example in
Once the user specifies the intended operating system via leaf nodes 408-412, the server then guides the question-and-answer interaction with the user to the next level comprising leaf nodes 414 and 416. These particular leaf nodes are used to determine from the user what kind of server role the user would like to choose for the software application. More specifically, the leaf node 414 may correspond to a thin server, and the leaf node may correspond to a full stack server.
The query tree guides the process of learning about the characteristics that the user has in mind to develop the software application for the target device 104. The various characteristics may include device type, operating system, etc. The query tree guides the process in a systematic approach, with at least some questions depending on previous answers. If the server determines that enough information regarding developing the application has been collected, the server stops generating question, or simply leaf node. Based on analyzing all the answers to each of the leaf nodes in the query tree, the server provides the technology recommendation via searching the knowledge base.
Any of a variety techniques may be used to implement the logic of the query tree. For example,
Still referring to
At 604, by executing the knowledge basis analysis module 210, the server 106 analyzes the input transmitted from the client device 102 by searching against the knowledge base 108 to generate a technology recommendation.
The method 600 continues at 606 with executing the technology recommendation module 212 to provide the technology recommendation to the client device 102. In some embodiments, the technology recommendation may include a software framework, a software development language, a software protocol, and a software platform.
If the server 106 determines that enough information has been collected, the method 700 continues in block 712 with providing the technology recommendation. And the technology recommendation is transmitted to the client device 102. On the other hand, if the server 108 determines that not enough information has been collected, the flow chart loops back to block 706 to generate more subsequent questions.
The above discussion is meant to be illustrative of the principles and various embodiments of the present invention. Numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2013/067517 | 10/30/2013 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2015/065372 | 5/7/2015 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
5269014 | Ogino | Dec 1993 | A |
6763342 | Mattern et al. | Jul 2004 | B1 |
6976067 | Gusler | Dec 2005 | B2 |
7401031 | Hughes | Jul 2008 | B2 |
7418447 | Caldwell et al. | Aug 2008 | B2 |
7546577 | Do | Jun 2009 | B2 |
8250532 | Guyette | Aug 2012 | B2 |
8332394 | Fan | Dec 2012 | B2 |
8468110 | Podgorny | Jun 2013 | B1 |
8494978 | Pinckney | Jul 2013 | B2 |
8615755 | Gargash | Dec 2013 | B2 |
8788356 | Georgis | Jul 2014 | B2 |
8938708 | DeLuca | Jan 2015 | B2 |
9021416 | Grechanik | Apr 2015 | B2 |
9070087 | Hatami-Hanza | Jun 2015 | B2 |
9129038 | Begel | Sep 2015 | B2 |
9572647 | Couse | Feb 2017 | B2 |
9594594 | Schmit | Mar 2017 | B2 |
20060129972 | Tyburski | Jun 2006 | A1 |
20070094219 | Kipersztok | Apr 2007 | A1 |
20080103936 | Churlik | May 2008 | A1 |
20080133500 | Edwards et al. | Jun 2008 | A1 |
20080227063 | Kenedy | Sep 2008 | A1 |
20080255696 | Chaar | Oct 2008 | A1 |
20080313124 | Arseneault | Dec 2008 | A1 |
20090113400 | Pelleg | Apr 2009 | A1 |
20090119637 | Ganapathy | May 2009 | A1 |
20090287678 | Brown | Nov 2009 | A1 |
20090292687 | Fan | Nov 2009 | A1 |
20100211924 | Begel | Aug 2010 | A1 |
20110083127 | Georgis | Apr 2011 | A1 |
20120072968 | Wysopal | Mar 2012 | A1 |
20120078873 | Ferrucci | Mar 2012 | A1 |
20120079449 | Sanderson et al. | Mar 2012 | A1 |
20120159441 | Ghaisas | Jun 2012 | A1 |
20120209663 | Gaskins, Jr. et al. | Aug 2012 | A1 |
20120290560 | Das | Nov 2012 | A1 |
20120331440 | Meermeera | Dec 2012 | A1 |
20130060785 | Sweeney | Mar 2013 | A1 |
20130159404 | Pfaff | Jun 2013 | A1 |
20140052680 | Nitz | Feb 2014 | A1 |
20140143750 | Gangadharan | May 2014 | A1 |
20140337372 | Lee | Nov 2014 | A1 |
Number | Date | Country |
---|---|---|
1834908 | Sep 2006 | CN |
20130101222 | Sep 2013 | KR |
Entry |
---|
Francis Palma, Recommendation System for Design Patterns in Software Development an DPR Overview, pp. 1-5, 2012 (Year: 2012). |
Luca Ponzanelli, Leveraging Crowd Knowledge for Software Comprehension and Development, pp. 57-65, 2013 (Year: 2013). |
Will Haines, Recommendations for End-User Development, pp. 42-48, 2010 (Year: 2010). |
Peter Clark, Enabling Domain Experts to Convey Questions to a Machine: A Modified, Template-Based Approach, 2003, pp. 1-7. https://pdfs.semanticscholar.org/05a7/8c9daf602e950112842a3eebe78be1e7f1c7.pdf (Year: 2003). |
Johan Aberg, Collection and Exploitation of Expert Knowledge in Web Assistant Systems, 2001, pp. 1-10. http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=927089 (Year: 2001). |
Fia, Software Development and Change Management Recommendations, 2012, pp. 1-8 https://secure.fia.org/downloads/software_change_management.pdf (Year: 2012) |
Doolittle, J. et al., “Building a Mobile Application Development Framework,” Intel, Aug. 2012, 8 pages, available at http://www.intel.in/content/dam/www/public/us/en/documents/best-practices/mobile-app-development-framework.pdf. |
International Search Report & Written Opinion received in PCT Application No. PCT/US2013/067517, dated Jul. 29, 2014, 15 pages. |
Verbert, K. et al., “Context-aware Recommender Systems for Learning: A Survey and Future Challenges,” IEEE Transactions on Learning Technologies 5.4, Jan. 2007, 20 pages. |
Number | Date | Country | |
---|---|---|---|
20160266874 A1 | Sep 2016 | US |