Since first published in 1998, the Enterprise JavaBeans technology has become a popular choice for the development of middleware systems. Even though its popularity, the technology is considered quite complex and rather difficult to master. The main contribution to its complexity is the part of the EJB that deals with persistence. The most common and most popular way of implementing EJB persistence is called Container Managed Persistence (CMP). Today, developers consider the utilization of CASE tools for the EJB development process obvious. Despite this, available CASE tools have very limited support for the complete CMP development process. In this thesis we have isolated steps within the CMP development process that could benefit from CASE tool support. We have then identified possible solutions and remedies to address these steps. These solutions where then implemented in a full fledged CASE tool, called CMP Developer.