Abstract
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. >
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
