2011-04-25 comments on Readability and Consistency for v5 Consultationit-workforce.com
One of most important area for the ease of use and access is the overall quality and readability of the SFIA framework. When using the framework in total (rather than looking at skills / skill levels in isolation) there is an overall sense of inconsistency in how the descriptors are put together. I propose that 4 areas could be looked at :
1. The range in the length, quality and readability of the skill and skill level descriptions
2. Readability
3. Could SFIA descriptors be presented as bullet points rather than sentences
4. Wide range in the number of skill indicators contained in the skill level descriptions
Wengines, Workflows, and 2 years of advanced data processing in Apache OODTChris Mattmann
With the advent of OODT-215 and OODT-491, there has been a tremendous amount of work to port our next generation Workflow Management system (cutely dubbed "WEngine" for "workflow engine") from an isolated branch into the mainline trunk.
The WEngine system brings amazing advantages including explicit support for branch and bounds in workflow models; prioritized thread pooling and queueing on a per task, and per workflow level; global workflow level conditions (pre and post); condition and workflow timeouts, and an entirely new and more descriptive state model complete with failure codes, and with checkpointing.
WEngine is currently processing the NPOESS Preparatory Project (NPP) PEATE testbed and its thousands of jobs per day, and is being slowly introduced into processing of an entire snow and ice climatology for the Western US and Alaska for the U.S. National Climate Assessment (NCA), working with the world's best snow hydrologists and snow scientists.
With all of those new features, what's an Apache OODT user and fan to do? How can you use WEngine in your system? How does it work today? How will it work tomorrow? We'll answer those questions and more in this fly-by-the-seat-of-your-pants exciting super talk!
2011-04-25 comments on Readability and Consistency for v5 Consultationit-workforce.com
One of most important area for the ease of use and access is the overall quality and readability of the SFIA framework. When using the framework in total (rather than looking at skills / skill levels in isolation) there is an overall sense of inconsistency in how the descriptors are put together. I propose that 4 areas could be looked at :
1. The range in the length, quality and readability of the skill and skill level descriptions
2. Readability
3. Could SFIA descriptors be presented as bullet points rather than sentences
4. Wide range in the number of skill indicators contained in the skill level descriptions
Wengines, Workflows, and 2 years of advanced data processing in Apache OODTChris Mattmann
With the advent of OODT-215 and OODT-491, there has been a tremendous amount of work to port our next generation Workflow Management system (cutely dubbed "WEngine" for "workflow engine") from an isolated branch into the mainline trunk.
The WEngine system brings amazing advantages including explicit support for branch and bounds in workflow models; prioritized thread pooling and queueing on a per task, and per workflow level; global workflow level conditions (pre and post); condition and workflow timeouts, and an entirely new and more descriptive state model complete with failure codes, and with checkpointing.
WEngine is currently processing the NPOESS Preparatory Project (NPP) PEATE testbed and its thousands of jobs per day, and is being slowly introduced into processing of an entire snow and ice climatology for the Western US and Alaska for the U.S. National Climate Assessment (NCA), working with the world's best snow hydrologists and snow scientists.
With all of those new features, what's an Apache OODT user and fan to do? How can you use WEngine in your system? How does it work today? How will it work tomorrow? We'll answer those questions and more in this fly-by-the-seat-of-your-pants exciting super talk!
