Browse Prior Art Database

Code Appreciation Disclosure Number: IPCOM000250453D
Publication Date: 2017-Jul-19
Document File: 3 page(s) / 49K

Publishing Venue

The Prior Art Database

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 39% of the total text.

Title – Code Appreciation *Enter a brief abstract for this article Abstract: While working in companies the main cause of retention of employees is respect in the form appreciation that one gets from his colleagues, management and leadership. The problem is genuine as many a times the people expected to appreciate are not aware of when to appreciate or what is the contribution made to be appreciated. Here an intelligent mechanism is needed to be able to identify when and how a person should be appreciated. Here the system should appreciate the respective person and inform his colleagues, managers for the same too. As a user writes code, he would be monitored to understand if he is using a construct for the first time, or solving a complex business problem or solving a complex technical problem. Based on these he would be appreciated by the system. And a notification for his good work would be sent to his manager / lead. *Enter the body of your Invention Disclosure Publication below. You may include drawings and highlighting as appropriate. Brief about the solution: Using any code development tool a profile of a person is created. For example, this would be an extension to the workspace created in RTC for an individual over the local and server space. The profile would have the basics created as of a new developer or an experienced developer. For a new developer the implementation mechanism would be that if he uses any code construct first time, he would be appreciated. For example if a new developer writes a piece of code, wherein he has used a nested for net loop. And the test case related to it passed then the developer would be appreciated for it. Here the limitation of appreciation would be to usage of basic constructs only. Once a developer has used all the basic constructs then he would be treated like a senior developer. But it would be different in the mechanism of implementation of an experienced developer. Here there would not be an appreciation based on the code constructs being used first time, rather it would be in the problem statement being solved. In a software development life cycle, the requirements are the key and primary inputs that determine the type of project life cycle - easy, slightly challenging and highly complex and very challenging. While most requirements analysis so far had been subjective, making it objective enables in a better judgment on the key areas in the project. Earlier tools and methods stressed on using one or several semantic constructs with strict and restrictive rules and boundaries that limited the scope of using the specified requirements. With the advent of NLP, requirements can be written as it is being stated in common English without much constraints. Applying NLP, and obtaining the deterministic and logical statements, these statements can be further analyzed into the groups of attributes - nouns and verbs and applying simpler mathematical rules, the complexity can be established. This enabl...