Thesis Topic Details
Topic ID: |
3190 | |
Title: |
Transparent database for end-user data | |
Supervisor: |
Ingo Weber | |
Research Area: |
Business Process Management, Services, Web Applications | |
| Associated Staff | ||
|---|---|---|
Assessor: |
Helen Hye-Young Paik | |
| Topic Details | ||
Status: |
Active | |
Type: |
R & D | |
Programs: |
CS CE SE | |
Group Suitable: |
Yes | |
Industrial: |
No | |
Pre-requisites: |
-- | |
Description: |
In business processes, often the data entered by a user is the same. For example, when asking for business travel reimbursement, a traveller's name, address, and bank account information does not change very often. If such a process is implemented in standard business software, then this is usually taken care of: the application stores the data for each user. Business process management systems (BPMS) are often more flexible than legacy enterprise applications, so that it becomes easier for companies to make changes to the process. However, BPMSs rarely keep track of the user's data: the user has to enter this information each time she wants to execute the process. The topic proposed here aims to build a transparent database of user information, which will work roughly as follows. A process modeller can specify upfront which of the fields will contain rather static data, i.e. data that is unlikely to change often. When a user first uses such a process, all fields will be blank. But when she returns to use the process again, the fields will already be pre-filled. This can be integrated with our end-user process modelling tool [1]. Development should be done in Java or PHP. After the above-described basic extension has been designed and implemented, advanced challenges can be addressed, such as: tagging fields and using user information across different processes; automatically suggesting tags; learning frequently used values for fields that are not static, e.g. "travel destination" in Australia is often Melbourne, Brisbane, Canberra, etc. Students are welcome to contact the supervisor(s) to tailor the details of individual thesis projects within the given context. Completion of COMP9322 (Service-Oriented Architectures) is not a prerequisite but will be useful. [1] FormSys, see demonstrations and papers here: http://www.cse.unsw.edu.au/~FormSys/FormSys/ |
|
Comments: |
-- | |
| Past Student Reports | ||
| No Reports Available. Contact the supervisor for more information.
Check out all available reports in the CSE Thesis Report Library. NOTE: only current CSE students can login to view and select reports to download. |
||