Task Manipulation - Revision history

Catglobe at 09:31, 8 July 2009

2009-07-08T09:31:38Z

← Older revision		Revision as of 09:31, 8 July 2009
Line 1:		Line 1:
	This artical is made due to standardizing requirements when manipulating with task. Task is a resource which is very distinguish with others because it has many people get ~~involed~~ and spends on several phases in its cycle life.		This artical is made due to standardizing requirements when manipulating with task. Task is a resource which is very distinguish with others because it has many people get involVed and spends on several phases in its cycle life.

	= <span style="color: #ff9900">PEOPLE INVOLVED</span> =		= <span style="color: #ff9900">PEOPLE INVOLVED</span> =
Line 13:		Line 13:
	The life cycle of a task is quite complicated but in short description, since a task is created, it will be accepted to carry out by the responsible and end at approval or calcellation. And the workflow below is describing in more details		The life cycle of a task is quite complicated but in short description, since a task is created, it will be accepted to carry out by the responsible and end at approval or calcellation. And the workflow below is describing in more details

	[[Image:TASK MANIPULATING.jpg]]		[[Image:TASK MANIPULATING.jpg]]

	= <span style="color: #ff9900">STATUSES</span> =		= <span style="color: #ff9900">STATUSES</span> =

Catglobe at 09:31, 8 July 2009

2009-07-08T09:31:23Z

← Older revision		Revision as of 09:31, 8 July 2009
Line 1:		Line 1:
	This artical is made due to standardizing requirements when manipulating with task. Task is a resource which is very distinguish with others because it has many people get involed and spends on several phases in its cycle life.		This artical is made due to standardizing requirements when manipulating with task. Task is a resource which is very distinguish with others because it has many people get involed and spends on several phases in its cycle life.

	= <span style="color: #ff9900">PEOPLE ~~INVOLED~~</span> =		= <span style="color: #ff9900">PEOPLE INVOLVED</span> =

	The people are		The people are
Line 13:		Line 13:
	The life cycle of a task is quite complicated but in short description, since a task is created, it will be accepted to carry out by the responsible and end at approval or calcellation. And the workflow below is describing in more details		The life cycle of a task is quite complicated but in short description, since a task is created, it will be accepted to carry out by the responsible and end at approval or calcellation. And the workflow below is describing in more details

	[[Image:TASK MANIPULATING.jpg]]		[[Image:TASK MANIPULATING.jpg]]

	= <span style="color: #ff9900">STATUSES</span> =		= <span style="color: #ff9900">STATUSES</span> =

Catglobe at 09:30, 8 July 2009

2009-07-08T09:30:39Z

← Older revision		Revision as of 09:30, 8 July 2009
Line 28:		Line 28:
	Besides, we can see that there are two loops in the workflow above. Those loops happen when it happens the confliction or disagreement between responsible and supervisor. Specificly, supervisor can reject responsible rejection to get the task status back to NEED ACCEPTANCE, or when the issue does neither working properly nor causing another issue after fixing, he/she will disapprove which get the task back to IN PROGRESS.		Besides, we can see that there are two loops in the workflow above. Those loops happen when it happens the confliction or disagreement between responsible and supervisor. Specificly, supervisor can reject responsible rejection to get the task status back to NEED ACCEPTANCE, or when the issue does neither working properly nor causing another issue after fixing, he/she will disapprove which get the task back to IN PROGRESS.

	= <span style="color: #ff9900">EXECUTIVE ACTIONS AND ~~VALIDATIONS~~</span> =		= <span style="color: #ff9900">EXECUTIVE ACTIONS AND CONSTRAINTS</span> =

	The task status is changed when a manipulating action is executed. According to the workflow above, we can seethere are 7 actions whose names are clear to understand what they are. However, a question comes out. Who can do that? Is there any constraint on executing?		The task status is changed when a manipulating action is executed. According to the workflow above, we can seethere are 7 actions whose names are clear to understand what they are. However, a question comes out. Who can do that? Is there any constraint on executing?
Line 42:		Line 42:
	Secondly, is there any constraint? Yes, the task must be qualified some criteria when an action is executed such as the task must be completed before approval action is executed.<br> And here we go for input and output when an action is executed.		Secondly, is there any constraint? Yes, the task must be qualified some criteria when an action is executed such as the task must be completed before approval action is executed.<br> And here we go for input and output when an action is executed.

	[[Image:~~Task_actions~~.jpg]]		[[Image:Task actions.jpg]]

Catglobe at 09:26, 8 July 2009

2009-07-08T09:26:21Z

← Older revision		Revision as of 09:26, 8 July 2009
Line 40:		Line 40:
	#Observer (Read only)		#Observer (Read only)

	Secondly, is there any constraint? Yes, the task must be qualified some criteria when an action is executed such as the task must be completed before approval action is executed.<br> And here we go for input and output when an action is executed.		Secondly, is there any constraint? Yes, the task must be qualified some criteria when an action is executed such as the task must be completed before approval action is executed.<br> And here we go for input and output when an action is executed.

			[[Image:Task_actions.jpg]]

	~~#<span style="color~~: ~~#800000">ACCEPT</span> <br>~~
	~~#<span style="color: #800000">REJECT</span>~~
	~~#<span style="color: #800000">REJECT REJECTION</span>~~
	~~#<span style="color: #800000">DONE (SET COMPLETE)</span>~~
	~~#<span style="color: #800000">APPROVE/DISAPPROVE</span>~~
	~~#<span style="color: #800000">CANCEL</span>~~

Catglobe at 09:04, 8 July 2009

2009-07-08T09:04:11Z

← Older revision		Revision as of 09:04, 8 July 2009
Line 28:		Line 28:
	Besides, we can see that there are two loops in the workflow above. Those loops happen when it happens the confliction or disagreement between responsible and supervisor. Specificly, supervisor can reject responsible rejection to get the task status back to NEED ACCEPTANCE, or when the issue does neither working properly nor causing another issue after fixing, he/she will disapprove which get the task back to IN PROGRESS.		Besides, we can see that there are two loops in the workflow above. Those loops happen when it happens the confliction or disagreement between responsible and supervisor. Specificly, supervisor can reject responsible rejection to get the task status back to NEED ACCEPTANCE, or when the issue does neither working properly nor causing another issue after fixing, he/she will disapprove which get the task back to IN PROGRESS.

	= <span style="color: #ff9900">EXECUTIVE ACTIONS AND VALIDATIONS</span> =		= <span style="color: #ff9900">EXECUTIVE ACTIONS AND VALIDATIONS</span> =

	The task status is changed when a manipulating action is executed. According to the workflow above, we can seethere are 7 actions whose names are clear to understand what they are. However, a question comes out. Who can do that? Is there any constraint on executing?		The task status is changed when a manipulating action is executed. According to the workflow above, we can seethere are 7 actions whose names are clear to understand what they are. However, a question comes out. Who can do that? Is there any constraint on executing?

	First at all, who can do that? The people can do that could be the responsibles or supervisors or observers which are considered basing on resource access. So instead of saying observer with a specific permission, I will use a minimium specific permission. And here is the range of who		First at all, who can do that? The people can do that could be the responsibles or supervisors or observers which are considered basing on resource access. So instead of saying observer with a specific permission, I will use a minimium specific permission. And here is the range of who

	#Responsible		#Responsible
	#Supervisor		#Supervisor
	#Administrator (Full control)		#Administrator (Full control)
	#Manager (Write only)		#Manager (Write only)
	#Observer (Read only)		#Observer (Read only)

			Secondly, is there any constraint? Yes, the task must be qualified some criteria when an action is executed such as the task must be completed before approval action is executed.<br> And here we go for input and output when an action is executed.



	#<span style="color: #800000">ACCEPT</span>		#<span style="color: #800000">ACCEPT</span> <br>
	#<span style="color: #800000">REJECT</span>		#<span style="color: #800000">REJECT</span>
	#<span style="color: #800000">REJECT REJECTION</span>		#<span style="color: #800000">REJECT REJECTION</span>
	#<span style="color: #800000">DONE (SET COMPLETE)</span>		#<span style="color: #800000">DONE (SET COMPLETE)</span>
	#<span style="color: #800000">APPROVE/DISAPPROVE</span>		#<span style="color: #800000">APPROVE/DISAPPROVE</span>
	#<span style="color: #800000">CANCEL</span>		#<span style="color: #800000">CANCEL</span>

Catglobe at 08:34, 8 July 2009

2009-07-08T08:34:13Z

← Older revision		Revision as of 08:34, 8 July 2009
Line 1:		Line 1:
	This artical is made due to standardizing requirements when manipulating with task. Task is a resource which is very distinguish with others because it has many people get involed and spends on several phases in its cycle life.		This artical is made due to standardizing requirements when manipulating with task. Task is a resource which is very distinguish with others because it has many people get involed and spends on several phases in its cycle life.

	= <span style="color: #ff9900">PEOPLE INVOLED</span> =		= <span style="color: #ff9900">PEOPLE INVOLED</span> =

	The people are		The people are
Line 15:		Line 15:
	[[Image:TASK MANIPULATING.jpg]]		[[Image:TASK MANIPULATING.jpg]]

	= <span style="color: #ff9900">STATUSES</span> =		= <span style="color: #ff9900">STATUSES</span> =

	In its life cycle, a task might spend on several statuses:		In its life cycle, a task might spend on several statuses:
Line 22:		Line 22:
	#IN PROGRESS : after being accepted, it goes to this status.		#IN PROGRESS : after being accepted, it goes to this status.
	#REJECTED : or it might go to this status when the responsible thinks it is not true.		#REJECTED : or it might go to this status when the responsible thinks it is not true.
	#COMPLETED : after making the issue working, the responsible sets it complete.		#COMPLETED : after making the issue working, the responsible sets it complete.
	#APPROVED : the task's supervisor retests the issue and see it workign properly and approve it for good.		#APPROVED : the task's supervisor retests the issue and see it workign properly and approve it for good.
	#CANCELLED : the supervisor can cancel the task whenever he/she see it no need to be fixed any more.		#CANCELLED : the supervisor can cancel the task whenever he/she see it no need to be fixed any more.

	Besides, we can see that there are two loops in the workflow above. Those loops happen when it happens the confliction or disagreement between responsible and supervisor. Specificly, supervisor can reject responsible rejection to get the task status back to NEED ACCEPTANCE, or when the issue does neither working properly nor causing another issue after fixing, he/she will disapprove which get the task back to IN PROGRESS.		Besides, we can see that there are two loops in the workflow above. Those loops happen when it happens the confliction or disagreement between responsible and supervisor. Specificly, supervisor can reject responsible rejection to get the task status back to NEED ACCEPTANCE, or when the issue does neither working properly nor causing another issue after fixing, he/she will disapprove which get the task back to IN PROGRESS.

			= <span style="color: #ff9900">EXECUTIVE ACTIONS AND VALIDATIONS</span> =

			The task status is changed when a manipulating action is executed. According to the workflow above, we can seethere are 7 actions whose names are clear to understand what they are. However, a question comes out. Who can do that? Is there any constraint on executing?

			First at all, who can do that? The people can do that could be the responsibles or supervisors or observers which are considered basing on resource access. So instead of saying observer with a specific permission, I will use a minimium specific permission. And here is the range of who

			#Responsible
			#Supervisor
			#Administrator (Full control)
			#Manager (Write only)
			#Observer (Read only)



			#<span style="color: #800000">ACCEPT</span>
			#<span style="color: #800000">REJECT</span>
			#<span style="color: #800000">REJECT REJECTION</span>
			#<span style="color: #800000">DONE (SET COMPLETE)</span>
			#<span style="color: #800000">APPROVE/DISAPPROVE</span>
			#<span style="color: #800000">CANCEL</span>

Catglobe at 08:18, 8 July 2009

2009-07-08T08:18:29Z

← Older revision		Revision as of 08:18, 8 July 2009
Line 1:		Line 1:
	This artical is made due to standardizing requirements when manipulating with task. Task is a resource which is very distinguish with others because it has many people get involed and spends on several phases in its cycle life.		This artical is made due to standardizing requirements when manipulating with task. Task is a resource which is very distinguish with others because it has many people get involed and spends on several phases in its cycle life.

			= <span style="color: #ff9900">PEOPLE INVOLED</span> =

	The people are		The people are
Line 11:		Line 13:
	The life cycle of a task is quite complicated but in short description, since a task is created, it will be accepted to carry out by the responsible and end at approval or calcellation. And the workflow below is describing in more details		The life cycle of a task is quite complicated but in short description, since a task is created, it will be accepted to carry out by the responsible and end at approval or calcellation. And the workflow below is describing in more details

	[[Image:~~TASK_MANIPULATING~~.jpg]]		[[Image:TASK MANIPULATING.jpg]]

			= <span style="color: #ff9900">STATUSES</span> =

			In its life cycle, a task might spend on several statuses:

	~~In its life cycle~~, a task might ~~spend on several statuses~~:		#NEED ACCEPTANCE : when created, a task needs to be assigned to someone.
			#IN PROGRESS : after being accepted, it goes to this status.
			#REJECTED : or it might go to this status when the responsible thinks it is not true.
			#COMPLETED : after making the issue working, the responsible sets it complete.
			#APPROVED : the task's supervisor retests the issue and see it workign properly and approve it for good.
			#CANCELLED : the supervisor can cancel the task whenever he/she see it no need to be fixed any more.

	#NEED ACCEPTANCE : when ~~created~~, a task ~~needs~~ to ~~be assigned to someone.~~		Besides, we can see that there are two loops in the workflow above. Those loops happen when it happens the confliction or disagreement between responsible and supervisor. Specificly, supervisor can reject responsible rejection to get the task status back to NEED ACCEPTANCE, or when the issue does neither working properly nor causing another issue after fixing, he/she will disapprove which get the task back to IN PROGRESS.
	#IN PROGRESS ~~: after being accepted, it goes to this status~~.
	~~#REJECTED : or it might go to this status when the responsible thinks it is not true~~

Catglobe at 08:06, 8 July 2009

2009-07-08T08:06:03Z

← Older revision		Revision as of 08:06, 8 July 2009
Line 9:		Line 9:
	<br>		<br>

	The life cycle of a task is quite complicated but in short description, since a task is created, it will be accepted to carry out by the responsible and end at approval or calcellation. And the workflow below is describing in more details		The life cycle of a task is quite complicated but in short description, since a task is created, it will be accepted to carry out by the responsible and end at approval or calcellation. And the workflow below is describing in more details

			[[Image:TASK_MANIPULATING.jpg]]

			In its life cycle, a task might spend on several statuses:

			#NEED ACCEPTANCE : when created, a task needs to be assigned to someone.
			#IN PROGRESS : after being accepted, it goes to this status.
			#REJECTED : or it might go to this status when the responsible thinks it is not true

Catglobe: New page: This artical is made due to standardizing requirements when manipulating with task. Task is a resource which is very distinguish with others because it has many people get involed and spen...

2009-07-08T07:58:57Z

New page: This artical is made due to standardizing requirements when manipulating with task. Task is a resource which is very distinguish with others because it has many people get involed and spen...

New page

This artical is made due to standardizing requirements when manipulating with task. Task is a resource which is very distinguish with others because it has many people get involed and spends on several phases in its cycle life.

The people are

#Responsible : the person will take care the task.
#Supervisor : the person monitors the process of task execution.
#Observer : the person who concern the task executing process.

<br>

The life cycle of a task is quite complicated but in short description, since a task is created, it will be accepted to carry out by the responsible and end at approval or calcellation. And the workflow below is describing in more details