A C++ data model supporting reachability analysis and dead code detection
ESEC '97/FSE-5 Proceedings of the 6th European SOFTWARE ENGINEERING conference held jointly with the 5th ACM SIGSOFT international symposium on Foundations of software engineering
A C++ Data Model Supporting Reachability Analysis and Dead Code Detection
IEEE Transactions on Software Engineering
Disaggregating and Calibrating the CASE Tool Variable in COCOMO II
IEEE Transactions on Software Engineering
Structural unity of product, process and organization form in the GIPSY process support framework
SEE '97 Proceedings of the 8th International Conference on Software Engineering Environments (SEE '97)
Integrating Through User Interface: A Flexible Integration Framework for Third-Party Software
COMPSAC '96 Proceedings of the 20th Conference on Computer Software and Applications
A framework for modeling and implementing visual notations with applications to software engineering
ACM Transactions on Software Engineering and Methodology (TOSEM)
Project management process framework for developing and IT systems
ICCOMP'08 Proceedings of the 12th WSEAS international conference on Computers
Hi-index | 0.00 |
Software engineering tools are critical to the progress of software development, virtually defining the limits of what developers can accomplish. Each generation of tools is preceded by promises of shorter life cycles, greater productivity, greater portability and simplified maintenance. Unfortunately, these promises are often not realized, primarily because tool creators cannot overcome the difficulties associated with integrating tools into a cohesive environment one that is adaptable to both development and maintenance organizations. The paper discusses a list of considerations for managers when evaluating how well a tool fits the organisation's context. It considers integrated project support environments