~cdparra/gelee/trunk

<br><br>In the majority of cases however, the lifecycle is informally defined, and is executed, monitored, and managed <i>by hand</i>, if at all. This

is because generic process management tools are too complex and too rigid for this purpose, and are tightly coupled with the artifact they manage.

In Gelee we aim at providing an abstractions framework and a supporting environment that overcome these

limitations and enable <b>universal resource lifecycle management</b>. We use the terms <i>universal</i> and <i>resource</i> as we want the system to manage

whatever can be identified by an URI, regardless of its nature, managing application, owner, or location. We realize that such universality

can often be at odds with ease of use, and indeed this is one of the challenges we face and address. The main characteristics of the proposed

approach are the following:

<li> The system is targeted at advanced web users (e.g., users comfortable with writing on wikis), not only programmers. The lifecycle model is very simple, essentially based on state machines. There are no complex features such as path conditions, transactions or exceptions.

<li> There is no need for modeling the resource being managed and its properties. The resource can be a "black box" from the lifecycle perspective. This is key both to universality and to keep the model simple from the perspective of the lifecycle designer who does not

need to worry about the specifics of each resource.

<li> We support automation of operations on the resources (e.g., changing access rights, submitting for reviews, etc.), achieved by actions that can be associated to phases (states) and executed upon entering a phase. Actions are where both the complexity and the resource

type-specific behavior reside (e.g., sending a Google doc for review also requires setting access rights, and the way this is done is Google docs-specific). They are written by programmers, who populate a library of useful actions.

<li> The model is targeted at unstructured lifecycles, where there is a high potential variability and the need to place the human in the driver's seat. For example, the lifecycle owner can determine when the resource transitions to the next phase or which is the next phase among the possible ones.

<li> The lifecycle management tool is hosted and available as a service, together with the lifecycle design interface and the monitoring interface, i.e., the interface a project manager would use to visualize status and history of the resources under her responsibility.

</ul>

</div>

100

</div>

101

102

<br>

103

104

<span id="ext-gen20" >Project members</span>

105

106

</div>

107

108

109

110

111

112

113

<h2>Research Staff</h2>

114

<ul>

115

<li>Fabio Casati</li>

116

<li>Maurizio Marchese</li>

117

<li>Florian Daniel</li>

118

<li>Marcos Baez</li>

119

<li>Cristhian Parra</li>

120

</ul>

121

</td>

122

<td>

123

<h2>Students</h2>

124

<ul>

125

<li>Kasia di Meo</li>

126

<li>Silvia Zobele</li>

127

<li>Carlo Menapace</li>

128

<li>Andrea Cristelli</li>

129

<li>Iliaria Eccher</li>

130

</ul>

131

</td>

132

</tr>

133

</table>

134

</div>

135

</div>

136

</div>

137

138

139

</div>

140

<div>

141

142

143

<span id="ext-gen20" class="x-panel-header-text">Login</span>

144

145

</div>

146

147

148

149

150

<p>Use your existing accounts to connect with us!</p>

151

152

153

154

google.friendconnect.renderSignInButton({ 'id': 'fc-login', 'text' : 'Sign in to Gelee', 'style': 'standard' });

155

</script><br>

156

<!--

157

<p>Login with your OpenID </p>

158

159

-->

160

161

</div>

162

163

164

</div>

165

<br>

166

167

<br>

168

169

Brought to you by:

170

</div>

171

172

173

174

</div>

175

176

177

</div>

178

179

<br>

180

<br>

181

182

183

184

185

186

<tr>

187

188

<span id="ext-gen20" class="x-panel-header-text"><a href="developers.html">Developers</a></span>

189

</td>

190

191

<span id="ext-gen20" class="x-panel-header-text"><a href="ecosystem.html">Ecosystem</a></span>

192

</td>

193

194

<span id="ext-gen20" class="x-panel-header-text"><a href="publications.html">Publications</a> </span>

195

</td>

196

197

<span id="ext-gen20" class="x-panel-header-text"><a href="about.html">About</a></span>

198

</td>

199

</tr>

200

</table>

201

</div>

202

</div>

203

204

<!--

205

206

207

208

209

210

<tr>

211

212

213

<li><a href="https://dev.liquidpub.org/svn/holms/">Checkout the source code!</a></li>

214

<li><a href="https://dev.liquidpub.org/trac/holms/">Report a bug or ask for a feature in our track system</a></li>

215

<li><a href="https://dev.liquidpub.org/svn/holms/trunk/client/">Integrate Gelee with you system. Checkout the client Code </a></li>

216

</ul>

217

</td>

218

219

220

<li><a href="https://dev.liquidpub.org/svn/holms/trunk/widgets/">Embed Gelee widgets in your Netvibes or iGoogle dashboards</a></li>

221

</ul>

222

</td>

223

224

225

<li><a href="http://www.sap.com/china/company/sapresearch/en/wiss09/files/wiss09_r4.pdf">Publications</a></li>

226

<li><a href="#">Tutorial (coming soon)</a></li>

227

</ul>

228

</td>

229

230

231

<li><a href="#">The project</a></li>

232

<li><a href="#">Collaborator</a></li>

233

<li><a href="#">Contact us</a></li>

234

</ul>

235

</td>

236

</tr>

237

</table>

238

</div>

239

</div>

240

</div>

241

-->

242

</div>

243

244

</div>

245

</body>

246

</html>

b'\\ No newline at end of file'

Older »