US2015317601A1PendingUtilityA1

User feedback method and system for business suite customization

Assignee: IBMPriority: Jul 31, 2009Filed: Jul 14, 2015Published: Nov 5, 2015
Est. expiryJul 31, 2029(~3 yrs left)· nominal 20-yr term from priority
G06Q 10/101G06F 8/20G06Q 10/10G06F 8/70
58
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A computer-implemented user feedback method, system and program product for customizing business suite software is executable on a computer system. The method includes: acquiring a business logic software function associated with a feedback mechanism in a business suite software user interface for the business suite software; acquiring an existing customization requirement related to the business logic software function and the relationship between the existing customization requirement related to the business logic software function and another existing customization requirement related to the business logic software function; and presenting the acquired existing customization requirement and the relationship between the existing customization requirement related to the business logic software function and the other existing customization requirement related to the business logic software function. The system includes: a business logic software function collector; a customization requirement manager; and a customization requirement presenter.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A computer-implemented user feedback method for customizing business suite software that is executable on a computer system, said method comprising:
 acquiring a business logic software function associated with a feedback mechanism in a business suite software user interface for said business suite software, wherein said step of acquiring a business logic software function associated with a feedback mechanism in a business suite software user interface is performed in response to said feedback mechanism in said business suite software user interface being activated;   acquiring an existing customization requirement related to said business logic software function and the relationship between said existing customization requirement related to said business logic software function and another existing customization requirement related to said business logic software function; and   presenting said acquired existing customization requirement and said relationship between said existing customization requirement related to said business logic software function and said other existing customization requirement related to said business logic software function.   
     
     
         2 . The method according to  claim 1 , further comprising:
 acquiring a user profile of a business suite software user of said business suite software; and   acquiring an existing customization requirement related to the content of said user profile, and the relationship between said existing customization requirement related to said content of said user profile and another existing customization requirement related to said content of said user profile or another existing customization requirement related to the content of another user profile of another business suite software user of said business suite software.   
     
     
         3 . The method according to  claim 1 , further comprising:
 receiving a new customization requirement input by a business suite software user of said business suite software; and   acquiring, by semantic analysis, the relationship between said existing customization requirement related to said business logic software function and said new customization requirement input by said user.   
     
     
         4 . The method according to  claim 3 , further comprising:
 increasing the weight of said existing customization requirement consistent with said new customization requirement.   
     
     
         5 . The method according to  claim 4 , wherein said step of increasing the weight of said existing customization requirement consistent with said new customization requirement comprises:
 presenting said existing customization requirement consistent with said new customization requirement to said user to be verified by said user;   receiving said user's verification result; and   increasing the weight of said existing customization requirement consistent with said new customization requirement verified by said user.   
     
     
         6 . The method according to  claim 3 , further comprising:
 storing said new customization requirement and said relationship between said new customization requirement and said existing customization requirement, wherein said storing step is performed if said existing customization requirement is not consistent with said new customization requirement.   
     
     
         7 . The method according to  claim 6 , wherein said step of storing said new customization requirement and said relationship between said new customization requirement and said existing customization requirement comprises:
 presenting to said user said acquired relationship between said existing customization requirement and said new customization requirement input by said user,   receiving said user's verification result on said relationship; and   storing said new customization requirement and said relationship between said new customization requirement and said existing customization requirement verified by said user.   
     
     
         8 . The method according to  claim 1 , further comprising:
 receiving a new customization requirement input by a user of said business suite software;   is receiving the relationship between said new customization requirement input by said user and said existing customization requirement;   verifying said relationship between said new customization requirement input by said user and said existing customization requirement; and   storing said verified relationship between said new customization requirement and said existing customization requirement.   
     
     
         9 . An article of manufacture tangibly embodying computer readable instructions which when implemented, causes a computer to carry out the steps of a computer-implemented user feedback method for customizing business suite software that is executable on a computer system according to  claim 1 . 
     
     
         10 . A computer-implemented user feedback system for customizing business suite software that is executable on a computer system, said system comprising:
 a business logic software function collector for acquiring a business logic software function associated with a feedback mechanism in a business suite software user interface for said business suite software, wherein acquiring a business logic software function associated with a feedback mechanism in a business suite software user interface for said business suite software is performed in response to said feedback mechanism in said business suite software user interface being activated;   a customization requirement manager for acquiring an existing customization requirement related with said business logic software function and the relationship between said existing customization requirement related to said business logic software function and another existing customization requirement related to said business logic software function; and   a customization requirement presenter for presenting said acquired existing customization requirement and said relationship between said existing customization requirement related to said business logic software function and said other existing customization requirement related to said business logic software function.   
     
     
         11 . The system according to  claim 10 , further comprising:
 a user profile manager for acquiring a user profile of a business suite software user, and   wherein said customization requirement manager further acquires an existing customization requirement related to the content of said user profile and the relationship between said existing customization requirement related to said content of said user profile and another existing customization requirement related to said content of said user profile or another existing customization requirement related to the content of another user profile of another business suite software user of said business suite software.   
     
     
         12 . The system according to  claim 10 , wherein said customization requirement manager further (i) receives a new customization requirement input by a business suite software user of said business suite software and (ii) acquires, by semantic analysis, the relationship between said existing customization requirement related to said business logic software function and said new customization requirement input by said user. 
     
     
         13 . The system according to  claim 12 , wherein said customization requirement manager further increases the weight of said existing customization requirement consistent with said new customization requirement. 
     
     
         14 . The system according to  claim 13 , wherein, if said existing customization requirement is consistent with said new customization requirement, said customization requirement manager further (i) presents said existing customization requirement consistent with said new customization requirement to said user to be verified by said user, (ii) receives said user's verification result, and (iii) increases the weight of said existing customization requirement consistent with said new customization requirement verified by said user. 
     
     
         15 . The system according to  claim 12 , wherein said customization requirement manager further stores said new customization requirement and said relationship is between said new customization requirement and said existing customization requirement if said existing customization requirement is not consistent with said new customization requirement. 
     
     
         16 . The system according to  claim 15 , wherein if said existing customization requirement is not consistent with said new customization requirement,
 said customization requirement presenter further presents to said user said acquired relationship between said existing customization requirement and said new customization requirement input by said user; and   said customization requirement manager further (i) receives said user's verification result on said acquired relationship between said existing customization requirement and said new customization requirement input by said user and (ii) stores said new customization requirement and said relationship between said existing customization requirement and said new customization requirement verified by said user.   
     
     
         17 . The system according to  claim 10 , wherein said customization requirement manager further (i) receives a new customization requirement input by a business suite software user of said business suite software, (ii) receives the relationship between said new customization requirement input by said user and said existing customization requirement, (iii) verifies said relationship between said new customization requirement input by said user and said existing customization requirement, (iv) and stores said verified relationship between said new customization requirement and said existing customization requirement verified by system. 
     
     
         18 . The method according to  claim 1 , further comprising:
 detecting incorrect input and determining incorrect relationships between customization requirements, and alerting users of the incorrect input and the incorrect relationships, wherein the incorrect input and incorrect relationships are prevented from being stored in the non-transitory computer readable storage medium   
     
     
         19 . The system according to  claim 10 , wherein the customization requirement manager is further configured to detect incorrect input and determine incorrect relationships between customization requirements, and to alert users of the incorrect input and the incorrect relationships, wherein the incorrect input and incorrect relationships are prevented from being stored in the non-transitory computer readable storage medium

Join the waitlist — get patent alerts

Track US2015317601A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.