IBM Redbooks - Websphere Studio Asset Analyzer
Authors: N
Published year: 2004
Pages: 13-15/84

<< Previous page
Table of contents
Next page >>

< Day Day Up >

1.4 Summary

That concludes our introduction to the WebSphere Studio Asset Analyzer. This should give you a good sense of what WSAA is and how you might want to use the product at your site.

As a WSAA system or product administrator, you now have a better understanding of the information that your site’s application development managers and programmers can obtain by querying the database.

As an application development project manager or group leader, we hope we got your thought processes whirling as you dream of ways in which you can more quickly scope out your projects and view your application’s interdependencies.

As an application programmer, you can probably see how using WSAA can let you access detailed information faster and easier than by reading through saved compiler listings or by scanning production source code libraries.

< Day Day Up >

Chapter 2: Roles and Responsibilities

Overview

In this chapter, we discuss the various roles and responsibilities of the people who support and use WebSphere Studio Asset Analyzer. We also provide a brief look at the activities they perform.

This chapter describes the roles of the following individuals and organizations:

WSAA system or product administrator
Additional IT support personnel
Application development project manager or leader
Application programmer

Our goal is to let you, the WSAA system or product administrator, know how these individuals can assist you and how you, in turn , can help your site’s application development community. We suggest that you share the contents of this chapter with them so that they understand what it is they must do.

< Day Day Up >

2.1 How we view your roles and responsibilities

One of the unique aspects of WebSphere Studio Asset Analyzer (WSAA) is that you, as the WSAA system or product administrator, have your hands full!

We took some time to think about all of the people you need to work with to get WSAA established at your site. At first glance, it might be overwhelming.

Table 2-1 briefly outlines a way in which you can view your work.

Table 2-1: Roles and responsibilities of WSAA participants
Role	Planning and installation	Post installation
WSAA system or product administrator	Yes	Yes
MVS systems programmer	Yes
DB2 database administrator	Yes	Yes
Change Management manager	Yes	Yes
Quality Assurance manager	Yes	Possibly
CICS systems programmer	Yes
IMS systems programmer	Yes
Storage administrator	Yes	Possibly
Security administrator	Yes	Possibly
WebSphere Application Server coordinator	Yes
Application project managers		Yes
Application programmers		Yes

As you can see, there are quite a few people who must help you plan for and install WebSphere Studio Asset Analyzer. Depending on your site’s size and organizational structure, there may be more people or groups involved or fewer.

Just the same, it requires a significant amount of work to load the WSAA database with your site’s production source code and online resources. Only a few groups are involved afterwards to actually take advantage of the results of your work. However, your site’s application development groups will be in a significantly better position to help your organization enhance the contents of its application portfolio.

We describe each of these roles, and the corresponding responsibilities, in the following sections.

Note

The Program Directory for IBM WebSphere Studio Asset Analyzer for Multiplatforms V2R2, GI10-8483 (hereafter referred to as the WSAA PID) describes, in detail, the activities your site must take to install and correctly configure WSAA.

Refer to Appendix D, “WSAA installation notes” on page 195 for additional highlights associated with this document.

< Day Day Up >