Learning from IPSE's mistakes

The authors argue that current work on integrated project support environments (IPSEs) is based on an inappropriate view of integration, and that IPSE developers should create semantically rich infrastructures or produce well-integrated tool sets rather than open repositories or infrastructures. The...

Full description

Saved in:
Bibliographic Details
Published in:IEEE software 1992-03, Vol.9 (2), p.23-28
Main Authors: Brown, A.W., McDermid, J.A.
Format: Article
Language:English
Subjects:
Automation
Computer aided software engineering
Data engineering
Engineering
Infrastructure
Interfaces
Large-scale systems
Productivity
Program processors
Programming
R&D
Research & development
Research and development
Software development
Software engineering
Software quality
Terminology
Citations: Items that this one cites
Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:The authors argue that current work on integrated project support environments (IPSEs) is based on an inappropriate view of integration, and that IPSE developers should create semantically rich infrastructures or produce well-integrated tool sets rather than open repositories or infrastructures. The requirements of IPSEs are outlined. The meaning of integration is examined, and tool integration in IPSEs, the only form of integration most IPSEs have, is discussed. CASE tools are perceived to be more effective and are much more widely used than IPSEs.< >
ISSN:0740-7459
1937-4194
DOI:10.1109/52.120598