OOPSLA Midyear Finance Workshop
Call For Participation
General Description
On July 19th through July 21st, OOPSLA is sponsoring a unique unique event that will consist of three day workshops devoted to Applied Object Technology. These workshops will bring together practitioners to share experiences and issues in the implementation of real world object systems. Our workshop specifically addresses the application of Information Technology in general and Object Technology in particular to business problems in Finance.
Accepted Papers
Areas of Interest
Business Specifications
- As a common ground for business users, business analysts and developers
- How to avoid write-only business specifications
- Business Patterns
- Tool Support for Developing Business Specifications
- Demonstrating correspondence of business specifications to business requirements
- How to determine business requirements?
- How to validate that business specifications fulfill the requirements?
- What formalisms are appropriate for particular portions of business and software specifications?
- How to create specifications that are apprehensible by business people.
- How to create business specifications that are not corrupted by system concepts, e.g., messages, database tables, collaborations, etc.
- How to promote precision and explicitness as opposed to slides and stories
- Feature Control (featuritis prevention)
Software Specifications
- Interfaces for Interworking
- Composing Solutions from New and Legacy Systems
- Specifying existing systems (both systems to interface with and components to build from)
- Specifying the behavior and semantics of software components and middleware at interfaces including:
- Transaction Processing
- Message Oriented Middleware
- CORBA
- DCOM
- DCE
- Technology and Middleware selection issues
- Object Modeling and Design
- Approaches, Techniques, Tools, Methods, Methodologies, Methodists…
- Tool Support for Developing Software Specifications
- Software Patterns
- How to avoid write-only software specifications
- Demonstrating traceability of software specifications to business specifications and back
Experience Reports
- Creating Business Specifications for Large Scale Systems that are understandable by and helpful to business users
- Building Industrial Strength Systems Using CORBA
- Building Industrial Strength Systems Using Java
- Building Industrial Strength Systems Using DCOM
- Assuming that Nietzsche was correct then tell us how you got so strong
- UML Experience
- What should rationally be expected from UML
- Which parts of UML are most useful
- Examples of using the Object Constraint Language (OCL) to specify semantics
- Which parts of UML are most useful for specifying dynamic behavior in an understandable manner
- Strengths and weaknesses of continuous and transformational methods (elaboration versus translation)
Project Management
- Managerial Issues
- Development lifecycle models (spiral, waterfall, etc., variations of these)
- Estimation/Resourcing
- Tracking/Measurement
- Project Risk Management Techniques
- Risk Assessment
- Prototyping
- Experimental Programming
- Iterative Development
- Development Team Organization
- Development Process (Technical Issues)
- Effective use of Patterns
- Traceability between business (including process model) and software (e.g., object model) specifications
- Organizational Dynamics of software development teams
- Methodologies for defining and documenting distributed components
- Testing. Tools, techniques and management issues
- Change management
Structure of the workshop
There are two primary forums provided by this workshop. This bifurcated structure does not imply separate and discrete activities. As at the primary OOPSLA conference, participants are encouraged to share their time. We will start with a joint plenary, breakup into several workgroups and then rejoin at midway through the last day.
The first forum is the traditional paper presentation format. This will provide an opportunity to air your ideas before a knowledgeable and experienced audience. All presentations will be published in the proceedings of the workshop.
The second forum will focus on hands-on problem solving.
- Example: propose a business domain (sub) area or an application area (like secondary mortgage market, IPOs, ...) and organize a project around it. Specifically, create a business specification together with your user, start developing a system specification, and planning a system based on your (and othersí) experience. This is a [3-day] team exercise with the team including a [Big Boss], project manager, business analyst, customer, system analyst, architect, developer(s), etc. Some people may play more than one role, but the roles are very distinct. Ideas and experience presented in the first forum are more than welcome to be reused. Description of the process and the result of this exercise would be a great achievement.
- Other proposals for focused work are encouraged
Submission Details
Papers should not exceed 6000 words. Papers will be reviewed by members of the program committee according to: technical quality, originality, clarity, appropriateness to the workshop focus, and adequacy of references to related work.
Electronic submissions in Postscript, PDF, MIF, or RTF will be accepted. Postscript submissions must conform to the Adobe Postscript Level 2 Specification or higher. Page size for all electronic submissions must be 8.5x11 (US Letter). Electronic submissions should be sent to dkulshrestha@checkfree.com. The submission deadline is April 27, 1998. Early submissions are encouraged.
Program Committee
Dheeraj Kulshrestha <dkulshrestha@checkfree.com> Lead
Kevin P. Tyson <kpt@enteng.com>
Mitch Goldstein <mgoldstein@greenwich.com>
Haim Kilov <haim_kilov@ml.com>
John Daniels <jdaniels@cix.compulink.co.uk>
Luis Andrade <landrade@oblog.pt>
Pervinder Johar <pjohar@statestreet.com>