Implementation and Customization

Adapt and customize
CA Endevor
to best fit your needs
ce18
Once you have installed
CA Endevor
, you are ready to implement and customize the product to best fit your needs. This section introduces the key aspects of implementation and customization, including the following:
  • Methods of implementation, for Source, Output, and Configuration Management
  • Types of implementation, including Rapid Implementation and Installing the Sample Application
  • Tables such as C1DEFLTS and ENDICNFG
  • Additional features such as Quick Edit and Integration for the Natural Environment
Read below for considerations you should take in account when you implement
CA Endevor
Implementation Considerations
Organizations can expect higher productivity, less production downtime, and better overall software quality shortly after implementing 
CA Endevor
. However, any change to organizational procedures requires careful project planning, education, awareness, management support, and internal selling. To help assist and prepare you for a successful implementation, consider the following organizational and technical areas.
 
 
3
 
3
 
 
Considerations for Organizational Change
To assess how 
CA Endevor
 will be received in your organization, consider the following points:
  • How large is your organization? Would you consider your organization small (50 developers or less), medium (50-200 developers), or large (more than 200 developers)?
  • How concise are the standards for software management now? Are they documented? Are they enforced? If the standards are not clear, what will it take for your organization to agree upon what the standards will be?
  • Will 
    CA Endevor
     be used extensively across groups within the organization? For example, will development, QA, and production turnover all use it?
  • Have all groups that will use 
    CA Endevor
     been involved in the evaluation and buying decision? If any of those groups were not involved in the original assessment, you may need to explain to them the benefits of 
    CA Endevor
    .
  • Are the organization's reasons for purchasing 
    CA Endevor
     clearly understood by all groups impacted by the purchase? Different levels of objectives include control, standardization, and the ability to audit.
Considerations for Developing a Strategy
When all considerations are addressed, you need to develop a strategy for proceeding. Make decisions about the following issues:
  • How much of the implementation effort do you want to spend on organizational activities, such as education and internal selling? How much effort on technical activities, such as writing processors?
  • For an average size organization (approximately 100 developers), the ratio of time spent should be about 50/50. For larger organizations, the percentage of time spent on organizational issues must be higher.
  • How extensively should you document current procedures, and how much time is needed to define new procedures?
  • How do you get different groups to agree on a standardized set of procedures?
  • How much internal selling is needed to obtain management support for 
    CA Endevor
     in the organization?
  • What is the scope of the implementation? For example, should you implement source management first, and output and configuration management at a later time? Or, do you want a phased approach such as JCL for the entire organization, then copybooks, then COBOL, and so on?
Recommendations for Selecting an Implementation Team
We strongly recommend that at least one full-time person is devoted to coordinating the 
CA Endevor
 implementation effort. You can add more resources as needed. When selecting an implementation team, consider the following recommendations:
  • Technical Knowledge
    You should select team members with the following technical and knowledge sets:
    • IBM z/OS JCL
    • SMP/E
    • Application development software (such as compilers, linkage editors, and so on)
    • Utilities, report writers, and so on
    • Operation and use of ISPF/PDF facilities
    • Your security system (usually RACF, CA Top Secret, or CA ACF2)
    • Audit requirements
    • Testing and production standards and turnover procedures
    • Applications to be implemented
    • Current procedures (standard and emergency changes, approval procedures, and so forth)
  • Organizational Involvement
    Ownership of 
    CA Endevor
     varies by organization. However, representatives from the following areas will probably be required for the implementation:
    • Technical Services
      System software specialists are needed to install and verify the installation. Operations analysts are needed to address JCL, production scheduling, and other general production turnover questions.
    • Production Control
      Representatives are needed to assist in automating the movement of new or changed software into production. This ensures that new procedures satisfy the business needs of the organization.
    • Applications
      At least one analyst from each application must be available during that application's implementation, to assist in application classification, compile procedures, training, and so on.
    • Security Administration
      An authorized person must define the appropriate security rules.
    • Auditing
      A person from the auditing department must ensure that audit requirements are defined and that the new procedures satisfy these requirements.
    • Training and documentation
      These groups need to be involved in developing training and internal documentation to support the system.
  • Public Relations Knowledge
    Some very large organizations have a dedicated person handling "public relations" work related to 
    CA Endevor
    . Based on how you want to handle this aspect of the implementation (that is, the need to gain acceptance from many parts of the organization), consider involving people with the following skills on the implementation team:
    • Experience with the environment
      Having an experienced person who understands the environment and is easy to communicate with is highly beneficial. This person should be able to relate to the production control and operations perspectives and the development and QA perspectives.
    • Organizational skills
      Often, a representative from the implementation team is asked to mediate discussions between different groups trying to derive standards for software management.
How to Introduce 
CA Endevor
 to Your Development Team
When your organization made the decision to acquire 
CA Endevor
, CA representatives most likely spent time with the people performing the evaluation, explaining how 
CA Endevor
 could suit the needs of the organization. Whatever the scope of your implementation, the implementation team will probably have to do some internal selling as well. Management, production turnover staff, developers from different groups, auditors, the QA staff, and other groups will need to learn about and accept 
CA Endevor
 before offering their support for the implementation.
The following recommendations may help you to introduce 
CA Endevor
 to your team:
  • Plan on preparing a presentation to introduce 
    CA Endevor
     to the people in your organization who are not familiar with the product. Depending on the complexity of your organization, you may need to create several presentations. Your presentations should include items such as the following:
    • A summary of the problems faced under the current software management procedures, and the justification for the acquisition of 
      CA Endevor
      . Whenever possible, use objective numbers and cost justifications, such as number of system outages per month due to software problems.
    • An overview of 
      CA Endevor
       functionality.
    • An explanation of how 
      CA Endevor
       will help your organization meet its goals.
    • A brief explanation of the proposed 
      CA Endevor
       implementation, including a walkthrough of the software lifecycle. As the presentation proceeds, explain the benefits and relate the solution to the problems identified above.
    • Time frames for the implementation, and what is expected of the group you are addressing.
  • Tailor the Presentation
    Tailor your presentation to your audience. For a presentation to higher-level management, for example, you may want to de-emphasize the lifecycle and technical issues surrounding the implementation and focus on the resources required, the payback expected, and the time frames for implementation. For developers, focus on how 
    CA Endevor
     can increase their productivity by allowing them to view change history for their programs online, or show them how to use the footprint display panels to view source directly from load modules.
    Emphasize goals in all presentations and public relations efforts. Work into each presentation the goals of productivity, availability of the production software environment, and any additional objectives for which 
    CA Endevor
     as acquired.
  • Introduce 
    CA Endevor
     to Your Organization
    After the groundwork is in place for the implementation, it is time to introduce 
    CA Endevor
     to the various groups within the organization that will use the product and benefit from it. When making a presentation to the following groups, consider stressing the points indicated:
    • Management
      Management must accept the proposed implementation and give it the appropriate priority over other tasks. Inevitably, a manager has limited resources, so convince the manager that 
      CA Endevor
       is the best way to increase software quality and personnel productivity.
      Show management that 
      CA Endevor
       improves productivity, improves software quality, and standardizes the software management process. You may want to discuss approvals and reporting, areas in which management may be involved with 
      CA Endevor
      .
    • Development
      It is important to show development personnel how 
      CA Endevor
       can improve the process of solving problems, viewing changes, preventing regression, and improving production availability which results in fewer late night phone calls. Show them that 
      CA Endevor
       can make their jobs easier by reducing software development and maintenance time.
    • Production turnover
      Show how 
      CA Endevor
       will automate the production turnover process, move source and executables together, facilitate backing out and addressing quick fixes, and provide a better audit trail of who made changes. 
      CA Endevor
       also enforces standards for things like JCL (by automating the invocation of JCL-checkers like JOB-SCAN) without the production staff's involvement. By the time a change gets to the production staff, they can be sure it has passed standards.
    • Audit
      The audit group can have a great deal of influence over software management procedures, particularly in regulated industries. In addition to the other benefits of 
      CA Endevor
      , audit groups should be shown the change tracking, SMF recording, and footprinting features.
      Emphasize that 
      CA Endevor
       can provide auditors with preventive controls rather than detective controls; that is, prevent the exception before it occurs rather than improve the process through which exceptions are detected.
After the presentation, keep in touch with the attendees to gain feedback from the presentation, to alert them when their group will be affected by the implementation process, and to address ongoing questions or concerns from them or anyone in their group.
Presentations are not the only way to introduce 
CA Endevor
 to your organization. Additional implementation aids include the following:
  • CA sales materials
    CA representatives are more than happy to provide sales materials that you can distribute to coworkers.
  • Demonstrations
    You may want to use the supplied MVSTEST and MVSPROD environments to show people how 
    CA Endevor
     works. Use a simple demo (RETRIEVE, ADD, MOVE) to show functionality. Tailor your demo to the audience (for example, auditors would probably like to see footprinting, while developers would like to see online change history tracking).
  • Personal contact
    Consider setting up a special phone number that people can call for answers to their questions about 
    CA Endevor
    . Have someone readily available to communicate reliable product and implementation information.
Recommendations for a Pilot Project
One of the best ways to implement 
CA Endevor
 is to start with a pilot application. No matter how you decide to approach the implementation (for source, output, or configuration management), a successful pilot can make the rest of the implementation easier.
The implementation of a pilot system has the following benefits:
  • Validates your software lifecycle design and procedures.
  • Builds momentum and excitement about 
    CA Endevor
     within the organization.
A pilot application ideally has the following characteristics:
  • One system, two to four subsystems, and a good sampling of element types to be managed.
  • Approximately 200 - 400 or more elements, with the maximum amount of 1000. Remember that an element is any component that belongs to the application, whether it is a copybook, program, JCL, or other type.
  • Relatively little change activity.
  • Available personnel. Because this is the first application to be implemented, more time than usual may be required of the people involved with the pilot group.
You may want to rate several applications according to the above criteria to determine the best application to use as the pilot.
How to Build Momentum for Your Implementation
Building momentum in the organization is a good way to keep the implementation process on track. In addition to implementing a successful pilot application, you can also build momentum by doing the following:
  • Talking 
    CA Endevor
    For example, when you hear of a developer overlaying a colleague's code, do not hesitate to mention how the situation could have been avoided with 
    CA Endevor
    .
  • Using the pilot project as a reference
    When people ask how 
    CA Endevor
     works, refer them to the pilot application staff to share their experiences.
  • Charting the progress of each group in the implementation effort
    Use, for example, a Power Point Presentation to visualize the implementation effort of different teams, perhaps in the context of an implementation newsletter.
Many sites that have tried this approach found that it improved the motivation of teams that were on or ahead of schedule and those teams that were behind schedule.