A systematic process for obtaining the behavior of context-sensitive systems

Journal of Software Engineering Research and Development

Table 2 List of contexts of meeting scheduler example and the context sources needed to monitor them

	Description	Variation	Context
		Point type	Source
C1	The number of participants is small		Mechanism to
	and The number of rooms available	OR	information
	is small and The date range is small		storage.
C2	The number of participants is high and		Mechanism to
	The number of rooms available is high	OR	information
	and The date range is high		storage.
C3	The number of participants is small		Mechanism to
	or The meeting is urgent	OR	information
	or Participants do not usually answer		storage.
	meeting requests by email
C4	Number of participants is high or		Mechanism to
	The meeting is not urgent or	OR	information
	Participants usually answer		storage.
	meeting requests by email
C5	The participants agenda is up to date	OR	Mechanism to
			information storage.
C6	Goal Schedule defined failed or The	AND	Mechanism to
	number of conflicts is higher than [MCA]		information storage.
C7	Response Time is higher than 2s	AND	Mechanism to
	more than five times in the week		information storage.
C8	The Number of conflicts is	OR	Mechanism to
	higher than [MCA]	OR	information storage.
C9	The Step back strategy have failed	OR	Mechanism to
			information storage.
C10	The Add new server	OR	Mechanism to
	strategy have failed		information storage.
C11	Response Time is higher than 2s	OR	Mechanism to
	more than five times in the week		information storage.