Meting minutes 26-10

Date: 26/10/2010
Place: Chun’s office
Participants: Arthur, Chun, and Khalid.
Time: 2:15 – 2:55

- Research for now should be wide and narrow it later.
- discussed worked done by Khalid.
- Arthur will be away for the next 2 weeks.
- Chun and Khalid agreed on moving the meeting to Monday 2 p.m. for the next 2 weeks.
- Khalid should continue the work and keep with the plan.
- Risk and BPM was discussed as a potential narrowing filed.
- Papers found so far are good.

Work to be done before next meeting:
- Khalid should contact the Author of one of the papers to get the paper.
- Khalid should contact Guy regarding the INN courses.
- Khalid should contact Peter regarding the IFN001 course.

From the BPM Book ..

" Unfortunately, the Techniques that guarantee transactional behaviour in databases systems cant be used for Business Process transactions, since they are based on preventing access to data objects by locking, and locking data objects during process instance is no valid option..." (Weske, Mathias. 2007 Business Process management. chapter 1. page 14)

1st month plan

Plan for 1^st month (20/10 – 20/11):           

Week	Date	Basic readings	BPM	Papers	Extra
1	20-27/10	Introduction To logic cha. 1-4 + exercises	Chapter 1	Search for papers	Learn DBLP
2	28/10–4/11	Naive Set Theory + exercises	Chapter 2	Read and summarize 3 papers	Learn Latex
3	5-12/11	Workflow management cha. 1-4	Chapter 3	Read and summarize 3 papers	Pitri net T. Murata
4	13-19/11	Yawl chapter 1-3	Chapter 4	Read and summarize 3 papers	Learn Harzing + web of science

Research Methodology: Design Science

Design Science consist of 7 guidelines:

1- Addresses design as an artifact: must produce a viable artifact in the form of a construct, a model, a method, or an instantiation.
2- Describes problem relevance: where the objective of the research is to develop technology-based solutions to important and relevant business problems.
3- Describes the importance of using strict evaluation methods for the design: The utility, quality, and efficacy of a design artifact must be rigorously demonstrated via well-executed evaluation methods.
4- Addresses the importance of the work being considered as a contribution to the academic world: IS research effort should be considered a contribution to the field.
5-  Focuses on research strictness: research relies upon the application of strict methods in both the construction and evaluation of the design artifact.
6- Design as a search process: the search for an effective artifact requires utilizing available means to reach desired ends while satisfying laws in the problem environment.
7-  addresses the importance that the work be published: in both the academic community and in the practitioner’s community.

-----------------------------------------
Source:
DESIGN SCIENCE IN INFORMATION SYSTEMS RESEARCH.
Alan R. Hevner, Sudha Ram, Salvatore T. March, Jinsoo Park.
2004.

These PhD comics are truly funny

That is actually a really good one:

so true ..

Confidentiality & BPM

Confidentiality is one of the three core security goals. Security has always defined confidentiality, integrity, and availability to be the core principles of information security, these three, also know as the “CIA triad”, are the hard security requirements (Allen, 2001).

Confidentiality was defined by the International Organization for Standardization (ISO) in ISO-17799 as "ensuring that information is accessible only to those authorized to have access". So basically confidentiality is to make sure that unauthorized personal will not get access to the information, and that can be easily reflect on BPM and need for it in BPM can be seen.

Vijay Atluri (2002) defines confidentiality in BPM terms when he says: “This refers to unauthorized disclosure of information including the workflow specification, and the workflow instances during its execution”.  Alhaqbani et al. (2010) in terms of distinguishing between privacy and confidentiality they say that data confidentiality aim to give the owner of the data control over its accessibility.                                       

An example to show the importance on confidentiality in BPM lets take an example of an “Payment” process in an on line parches. For the example let us assume that Adam wants to buy something from company’s “A” website. One important part of the parches process is the payment process, where the website offers the use of credit card, during this process Adam has the right to ask for his credit card information to e hidden and that non of the employees working in this company can see it; while this process can not be completed without Adam providing such information. So this is a case here information needed to be entered to the process while also the owner of the information requires a confidentiality restriction on this information. This is a case shows how important it is to have confidentiality control in BPM.

Currently there are not any specific solution that was proposed to as a solution to the confidentiality problem in BPM, but the work done by Alhaqbani et al. (2010), which was a solution for the privacy, is an outstanding solution and also can be used to solve the confidentiality requirement, there solution can be easily modified to be used also as a confidentiality solution.

-------------------------------

All Rights reserved @ Khalid Alissa 2010.