Difference between revisions of "Inter-Organizational Workflow"
Line 39: | Line 39: | ||
==Universal Abstraction and Context Awareness== | ==Universal Abstraction and Context Awareness== | ||
Context awareness refers, in information and communication technologies, to a capability to take into account the situation of entities, which may be users or devices, but are not limited to those. | [[Wikipedia:Context awareness]] refers, in information and communication technologies, to a capability to take into account the situation of entities, which may be users or devices, but are not limited to those. Various categorizations of context have been proposed in the past. Dey and Abowd (1999)<ref name="ReferenceA">[ftp://ftp.cc.gatech.edu/pub/gvu/tr/1999/99-22.pdf Towards a Better Understanding of Context and Context-Awareness]</ref> distinguish between the context types ''location'', ''identity'', ''activity'' and ''time''. Kaltz et al. (2005)<ref name="kaltz2005">{{cite journal | ||
Various categorizations of context have been proposed in the past. Dey and Abowd (1999)<ref name="ReferenceA">[ftp://ftp.cc.gatech.edu/pub/gvu/tr/1999/99-22.pdf Towards a Better Understanding of Context and Context-Awareness]</ref> distinguish between the context types ''location'', ''identity'', ''activity'' and ''time''. Kaltz et al. (2005)<ref name="kaltz2005">{{cite journal | |||
|author1=Kaltz, J.W. |author2=Ziegler, J. |author3=Lohmann, S. | year = 2005 | |author1=Kaltz, J.W. |author2=Ziegler, J. |author3=Lohmann, S. | year = 2005 | ||
| title = Context-aware Web Engineering: Modeling and Applications | | title = Context-aware Web Engineering: Modeling and Applications |
Revision as of 12:27, 7 July 2021
We can plan the meta workflows here and the link to the sub workflows internally
Project Management
Useful project management namespaces.[1]
Time Management
We can abstract and list the purpose for async and sync communication. For sync meeting, I found it efficient to demonstrate something which one already have, like a wiki function, technical issue. The listener can output all of their thoughts and start discussion base on the rich context
Communication Management
From Synchronous to Asynchronous Communication
By specifying different communication scenarios, collaborators can have better expectation of one another's reply time.
- Face-to-face meeting: participants communicate in realtime by either audio or video.
- 1st level: participants are focusing on the message; the turn taking period is 5 to 60 seconds.
- 2nd level: participants work on other things and talk at the same time; the turn taking period is 1-10 minutes.
- 3rd level: the turn taking period is 10mins to 1hr
- 4th level: the turn taking period is several hours to days.
Structuring Talks
Communication data is an important data source. To best utilize communication, each piece of information could be further transformed into content, actions, or any types of data and managed in PKC. This process could be iteratively improved by some rules of a team. The core of the rules is the abstraction of data. For each piece of information, if its type is well-defined, users can categorize it and trigger following actions [either manually or automatically/place at the back]. If the type isn't defined or only weakly defined, users should choose whether to define its type, optimize them, or do nothing. (Universal data abstraction, evolving abstraction). So there are two levels of communication:
- Basic level: the communication goes on by the words' pragmatics. [2]
- Meta level: the communication triggers actions to improve the system.
For example:
- For an undefined pattern, define a new page.
- For a set of messages, create a summary and locate in Channel namespace.
- For some actions, create an action item and locate in Project namespace.
To do:formalizing the abstraction rule
Improvement of data abstraction
- Data abstraction in given Design Space
- Defining new structure and expanding the Design Space
Universal Abstraction and Context Awareness
Wikipedia:Context awareness refers, in information and communication technologies, to a capability to take into account the situation of entities, which may be users or devices, but are not limited to those. Various categorizations of context have been proposed in the past. Dey and Abowd (1999)[3] distinguish between the context types location, identity, activity and time. Kaltz et al. (2005)[4] identified the categories user&role, process&task, location, time and device to cover a broad variety of mobile and web scenarios. They emphasize yet for these classical modalities that any optimal categorization depends very much on the application domain and use case. Beyond more advanced modalities may apply when not only single entities are addressed, but also clusters of entities that work in a coherence of context, as e.g. teams at work or also single bearers with a multiplicity of appliances.
Namespace Management
The namespace of a project is constantly built up by the abstraction process.
Exchanging working status
- ↑ https://project-management-knowledge.com/definitions/l/log/
- ↑ Wikipedia:Pragmatics
- ↑ Towards a Better Understanding of Context and Context-Awareness
- ↑ Kaltz, J.W.; Ziegler, J.; Lohmann, S. (2005). "Context-aware Web Engineering: Modeling and Applications" (PDF). Revue d'Intelligence Artificielle. 19 (3): 439–458. doi:10.3166/ria.19.439-458.