By Topic

Introducing shareable frameworks into a procedural development environment

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $33
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
R. L. van der Salm ; Consist B.V., Nevelgaarde 20, P.O. Box 500, 3430 AM Nieuwegein, Netherlands

Typically, an IBM midrange-oriented independent software vendor such as the Dutch company Consist B.V. is not a leader in using new technology. Such companies prefer to use stable, proven technology environments to create and sell their products rather than take the risk of using new, unproven technologies. Consist B.V. has been known for over 20 years in the Benelux market for delivering stable applications and investing only in proven technology. Why is it, then, that they now invest large sums of money in new technologies such as framework-based development, Java™, CORBA™, and object-oriented programming? This paper describes the business reasons that influenced Consist B.V. to make this shift in its strategy and the way in which the traditional procedurally oriented development organization is changed into an object-oriented, framework-using software factory. Apart from the technical implications and the steep learning curve associated with using these technologies, some attention is also given to the human resource management aspects of the organization.

Note: The Institute of Electrical and Electronics Engineers, Incorporated is distributing this Article with permission of the International Business Machines Corporation (IBM) who is the exclusive owner. The recipient of this Article may not assign, sublicense, lease, rent or otherwise transfer, reproduce, prepare derivative works, publicly display or perform, or distribute the Article.  

Published in:

IBM Systems Journal  (Volume:37 ,  Issue: 2 )