Chair: Daan Hoogland, Luminis B.V.
Featuring MDAFest and once again XPFest.
DesignFest® is an OOPSLA specific conference feature. It is suitable for school and company environment, but it is integrated in no where else as it is in at OOPSLA. It has documented results sinse 1995 and has a more informal history before that.
DesignFest® is a training method, not in the courseware sense, but in the sportlike sense. It is an exercise in design with your peers. What it really is, I found can be said in a number of ways.
Some quotes of former DesignFest® chairs:
DesignFest® is a free event (for conference registrants) created to give OOPSLA attendees the opportunity to learn more about design by doing it.
The OOPSLA DesignFest® is about design and creativity.
DesignFest® is not about passively sitting and listening to experts talk about design.
DesignFest is about sharpening your design skills by rolling up your sleeves and working on a real problem with others in the field.
In a DesignFest® groups are formed to work on design problems. A group does not get to see its full problem description until the moment the DesignFest® starts. However, the group is free to communicate beforehand to agree on proces if they so desire. Each member of the team assumes a specific role. The group is expected to produce a set of deliverables by the end of the session.
Of course roles and deliverables may vary when special processes are agreed upon. This is certainly true for MDAFest and XPFest but is not limited to such specific settings. We will provide a wiki area for each group where you can discuss and document your proces and deliverables. If you agree we will also give your email adres to your fellow group members.
Like in the past few years, a limited number of teams will be able to use EXtreme Programming practices in the XPFest. New this year is the addition of an MDAFest, where participants will try their skills using Model Driven Architecture. The MDAFest is not a tutorial on MDA; it is an opportunity for practitioners to discuss practices and tools, working on a specific problem.
Teamwork for Physical Therapists of Children
The problem is to design a system that can help a small team of physical therapists that treat children, to communicate between team members, with doctors and with parents.
When treating children, continuity is very important, communication with parents plays a role, and the children themselves are often not able to participate in the planning and keeping track of treatment as an adult would do.
The first and most important requirement of the team of physical therapists is to have a system that would allow them to transfer work of one therapist to another (in case of absence or illness of a therapist) seamlessly to ensure continuity of the therapy. Since this would require already a fair amount of data about treatments for each child to be kept, the team would like to be able to put this data to additional use for communication with doctors and parents, and to keep appointment schedules.
On-Line Image Management
The proposal involves the design of a system that manages digital images as a Web-service, specifically focused for use by larger or international organizations. The system will be used by professional photographers to deliver their photo's and by print shops, both possibly external to the organization that deploys the image system.
Many organizations of any size own images to be used for company brochures, advertising material, and internal or external publications. During the last few years these images are increasingly kept on digital media.
The management of these digital images poses problems that are different from managing a set of text-documents, for example:
Images take much more space than documents, typically 10-40MB.
Additional information about an image needs to be stored external to the image to allow searching.
The copyright of an image may reside outside the company that uses it.
New technology and standards make it feasible to provide management of images as a web-service. This enables organizations to have loose relationships with image providers, and media providers to offer flexible contracts, customized towards the need of a specific organization.
Identity Management Reference Architecture
In this design fest we will come up with a design for identity management for a large enterprise. Many large companies have a number of different systems doing identity management in different ways. Some systems use LDAP, some use RDBMS and some others use Active Directory as identity store.
Different systems are currently in production and they use ERP systems, a number of COTS products and Java/J2EE. LDAP and Active Directory are being kept in Sync using synchronization tools. A user that is added to one system may need to be added to multiple systems with different privileges. Another challenge is to provision two million volunteers. Identity products from different vendors are being considered.
Here is the general workflow of the system to be built: Employees are first provisioned in HR system and user identity flows to Active Directory followed by LDAP. Volunteers are usually provisioned using the provisioning tool which propagates identity with appropriate privileges. User is provided with password synchronization across all the systems. When a user does not need access, they are de-provisioned automatically. Some systems need single sign on capability and this is provided by policy server(s) from vendors.
Provisioning an internet provider's network
This problem has been introduced into the domain of telecom providers and cable-television suppliers as they broadened their range of products and started to delve into each others markets.
The maintenance people of a service provider have to administer and configure devices and daemons running on server machines. This can be quite cumbersome and is a good candidate for automation.
A system for configuring and maintaining a network of devices for routing and processing and receiving ip data must be maintained. A lot of it is automated. But this is not standard of the shelf software. Big and small service providers often build their own.
The systems involved run very different hardware. Some are configurable through snmp interfaces others through html over http interfaces. Again others run commandline interfaces on proprietary operating systems.
Extreme Programming Production of a Tournament Management System
In this project, the DesignFest participants will use the Extreme Programming (XP) methodology to design and build a working tournament management system within one day. The organizers will provide ongoing instruction in the XP practices as appropriate, and will also act as the customer for the software project. The day will proceed as a series of iterations. During each iteration, the customers and designers will "negotiate" the features of the system that are to be developed, coding will take place, and the customer will be given the chance to accept or reject the delivered system. At the end of each iteration, the customer should have a working system that incorporates the features that were previously negotiated.
Manufacturing / Printing Process Simulator
Designers of real-time embedded software are often faced with a serious problem. The physical system that their software will control is being designed concurrently and is therefore not available as a test platform for the software. Add to this the usual dangers of running untested software on systems that have inherent safety and property damage risks, and the arguments in favor of simulation environments become quite strong.
Design Fest teams choosing this assignment will design a general-purpose simulator for a mechanical process. This proposal addresses a specific domain within embedded systems: that where software must control the transport of physical objects through various way points where physical actions are applied to them.
Software is needed to simulate the physical system so that the software being designed to control that system can be empirically tested. The control software is not part of this proposal.
In our experience people do not want to start their designfest during the keynote. Therefore this year we will have a 3/4-day session on Wednesday that starts right after the keynote.
Daan Hoogland (Chair)
Sunday, 8:30, half day, San Diego Room
Daan Hoogland (Chair)
Sunday, 8:30, full day, San Diego Room
Daan Hoogland (Chair)
Sunday, 13:30, half day, San Diego Room
Daan Hoogland (Chair)
Wednesday, 10:30, 6 hours 30 minutes, Sunset
Daan Hoogland (Chair)
Wednesday, 13:30, half day, Dover and Stratford rooms