 |
 |
BCS OOPS Specialist Group OOPS-149: A Process for Designing Component Systems John Daniels, Syntropy, Ltd. 6:30 pm Wednesday 7th February 2001 Venue: IEE, Savoy Place, London, WC2R 0BL Map at: http://www.iee.org.uk/find-sp.htm Admission Free - No pre-registration required This presentation will describe a simple process for moving from business requirements to specifications of software components, based on the recent book "UML Components" (John Cheesman & John Daniels, Addison-Wesley, 2000). The presentation will outline the steps involved in the process and show how the outputs can be represented in technology-independent UML. John Daniels is a consultant at Syntropy, Ltd., providing help with system architectures and development processes to a number of large corporations. He was an object technology pioneer, and has applied object and component technology in a range of industrial and commercial applications since 1985. Together with Steve Cook he developed the Syntropy method, which led directly to the definition of the UML's Object Constraint Language and which has been highly influential in other recent work. John is a past Chair of the BCS OOPS OT conference, and has presented at many other international conferences. OOPS Meetings Programme Committee: Brian Saxby, Kingston University [[log in to unmask]]; Hedley Apperly, Princeton Softech [[log in to unmask]] Immo Huneke, Logica [[log in to unmask]] OOPS Meetings Schedule - http://www.bcs.org.uk/siggroup/oops.htm Normal monthly meetings are open to all - Admission Free. No pre-registration required. Because of this policy we must reserve the right to restrict entry if the venue reaches capacity. To receive e-mail notification of OOPS events (members & non-members), send e-mail with message body: subscribe bcs-oops-announce "My Real Name" <[log in to unmask]> to: [log in to unmask] (See above WWW pages for regional programmes) Wednesday 7th March 2001 OOPS-150: Technology and Integration Annwen Owen, University of Wales, Bangor (Java & XML, 'Data' Integration, UML)