Where CASE fits into Software Engineering.

• Complete Reqirements Specifications- Most specification methodologies enfore end-user involvement since it is impossible to complete the specification without developing a model of the end-user's process or business function. Some tools help to organize data and develop specifications.
  
  
• Accurate Design Specifications- There is nothing more frightening for a novice software engineer than facing the task of maintaining a large software system with incomplete, inaccurate, or nonexistent design documentation.
  
  
• Current Design Specifications- Inaccurate design specifications not kept up-to-date relative to modifications made to the source code base can be an even bigger problem than incomplete design specifications. Some CASE Tools can help maintain synchronization with the code implementation.
  
  
• Reduced Development Time- Software developers must feel they are being productive in the requirements analysis and design specifications phases as they feel when writing code during implementation phase. CASE Tools can help organize time and help move the processes along.
  
  
• Highly Extensible / Maintainable Code- Any successful project will never be finished. The problem comes when trying to keep the design specifications inline with maintenece and enhancement after the implementaion phase has ended. Again CASE can help maintain synchronization.
  
  Next