<Company Name>

<Project name>
Development-Organization Assessment

Version 2.1
<Project name> Version: 2.1
Development Infrastructure Date: 05/25/04

Revision History
Date Version Description Author
03/18/04 1.0 Initial Creation Sam Jones
03/19/04 1.1 Updates Sam Jones
04/12/04 1.2 Updates with project directory Richard Hart
04/14/04 1.3 Updates Sam Jones
04/18/04 1.4 Updates Mike Teff
4/22/04 1.5 Updates with Environment and Mary Higgins
CCM network locations
4/26/04 1.6 Updates based on the meeting with Mary Higgins
IBM on 04/22/2004
5/11/04 2.0 Updates based on Iteration 2 Mary Higgins
Assessment meeting
5/25/04 2.1 Add proxy information for proxy Mary Higgins
server setting; Updates project
directory structure

Confidential <Company Name> 2010 Page 2 of 8

<Project name> Version: 2.1
Development Infrastructure Date: 05/25/04

Table of Contents
1. Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms, and Abbreviations 4
1.4 References 4
1.5 Overview 4

2. Environment 4
2.1 Hardware 4
2.2 Software 4
2.3 Network location 5
2.4 Password 5

3. Project Management 5
3.1 Hardware 5
3.2 Software 5
3.3 Network location 5
3.4 Password 5

4. Configuration and Change Management 5

4.1 Hardware 5
ACD2284CC01: This server is hosting the following application programs and services: 5
ACD2287RATL01: This server is hosting the following application programs and services: 6
4.2 Software 6
4.3 Network location 6
4.4 Password 7

5. Project Directory Structure 7

Confidential <Company Name> 2010 Page 3 of 8

<Project name> Version: 2.1
Development Infrastructure Date: 05/25/04

Development-Organization Assessment
1. Introduction
1.1 Purpose
The development infrastructure artifact includes the hardware and software, such as computers and operating
systems, on which the tools run. The development infrastructure also includes the hardware and software used to
interconnect computers and users. This is used to assist new team members in joining in the project and to provide
guidance to the team when they need to modify the environment.
1.2 Scope
This artifact describes the RAP1 development infrastructure to support the three RUP disciplines being adopted;
Environment, Project Management and Configuration and Change Management. When all disciplines are
completed, a compiled version will be created to reflect the entire development infrastructure for the <Project
Name> team.
1.3 Definitions, Acronyms, and Abbreviations
See Glossary.doc.
1.4 References
Rational Unified Process, 2003, IBM/Rational software
Workstation Setup artifact
1.5 Overview
This artifact is structured around the RUP disciplines that are being adopted. Each section will contain the
description of the elements to support the use of tools for those disciplines, as well as any other details such as
references to passwords and network access information.

2. Environment
2.1 Hardware
This discipline is focused on the process environment. The process tool is the RUP. It is a set of HTML pages that
are viewed via a web browser. The RUP can be hosted locally on each desktop or on a shared file server that does
require a web server. The details on the minimum required hardware include:

Windows
• Any Pentium-based PC-compatible computer system with SVGA-compatible display
• Any pointing device with at least two buttons
• Microsoft Windows NT 4.0 (SP6a) or Windows 2000 (SP2 or 3)
• 64 MB RAM minimum, 256 MB recommended
• 255 MB disk space

The RUP is being installed to provide the new process engineers and project team members with a source for
information and guidance. The RUP server will be acd2287ratl01, running the Windows 2000 Server operating
system SP 4. The logical partitions are as follows:
• Operating system (7 GB min)
• Rational License Server application (1 GB min)
• Other (Remaining disk space)

2.2 Software
If installed locally, the software resides in a folder installed under Program Files/Rational/RationalUnifiedProcess
if installed using the default settings on a desktop. This location is determined at the time of the installation and
can be defined differently when using a shared file server. We will be creating a configuration for <Project Name>

Confidential <Company Name> 2010 Page 4 of 8

<Project name> Version: 2.1
Development Infrastructure Date: 05/25/04

that is based on the core RUP repository with the J2EE and IBM WebSphere Application Server plug-ins. See the
Workstation Setup artifact for details on installing the correct plug-ins for the RUP and for setting up the proxy
server settings. The details on the minimum required software include:

Windows
Either of the following supporting software is required:
Microsoft Internet Explorer 5.01 with SP2 or later
Netscape Navigator versions 4.72 to 4.77 and 7.0

2.3 Network location

Currently it hosted on the Web Server 1-rs026665. The URL is: http://1-rs026665/rup/. The final location will be
on a shared file server acd2287ratl01.
2.4 Password
The RUP does not require use of a password for access.

3. Project Management
3.1 Hardware
This discipline is focused on the project management activities. The tools for this include Microsoft Excel, Word
and Microsoft Project. These tools are located on each user’s desktop. See Workstation Setup for details on
installing and configuration of these tools.
3.2 Software
The details on the minimum required software include:

Version 2000 or higher for all three tools.

MS Project recommended ideal version is 2002.
3.3 Network location
The files will be located in the Project Directory Structure. This location would be the location of the files we use
for the Project Mgmt discipline, like the MS Project Plans. These artifacts will be under version control using
ClearCase. Access to certain folders may be limited to specific roles. The MS Project files are located at
\\usr\ratl\msproj. See the latest file for current schedule information.
3.4 Password
The Microsoft Office tools do not require use of a password for access. MS Project can require access passwords
to be used if necessary.

4. Configuration and Change Management

Change Management will not be adopted in the RAP1 project; it will only be documented. The entire
infrastructure for Change Management will be determined at a later date.
4.1 Hardware
The production instance of the Rational Products Server system is running on servers hosted in the corporate
computer room.
There are two servers:
• ACD2284CC01
• ACD2287RATL01
Both servers are running the Windows 2000 Server operating system.
ACD2284CC01: This server is hosting the following application programs and services:
• ClearCase LT Server

Confidential <Company Name> 2010 Page 5 of 8

<Project name> Version: 2.1
Development Infrastructure Date: 05/25/04

The logical partitions are as follows:

• Operating system (6 GB min)

• ClearCase LT Server applications (6 GB min)
• ClearCase Repository (Remaining disk space)

ACD2287RATL01: This server is hosting the following application programs and services:
• Rational Floating License Server
• Rational Software Release Area.

The logical partitions are as follows:

C: Operating system (6 GB min)

E: Rational License Server application (1 GB min)
F: Other (Remaining disk space)

4.2 Software

The Rational Products Server system consists of the following products and services:
• Rational ClearCase LT. This is a version control application for source code, documents, etc. ClearCase LT is a
client-server application. The server component manages a database and a hierarchy of file system folders on the
server.
• Rational Floating License Server. This application controls access to Rational desktop applications.
IBM/Rational uses Globetrotter FlexLM. FlexLM is a commonly used licensing tool. NOTE: The license itself is
a number composed from server hardware serial numbers such as disk drive ID, NIC ID, etc. If a hardware
component of this server is changed after installation, we will need to acquire a new license key. If hardware
changes occur without foreknowledge, all ClearCase processes become invalid until we contact the vendor and get
a temporary license.
• Rational Software Release Area. The IT and PC support staff will use this area of the file system as the source for
installing versions of Rational applications on the developer’s desktops. We will implement this as a hidden share
that is publicly readable but only writable by the RationalAdmins group described below under Security.

The current release of IBM/Rational tools is NOT certified compliant with Windows Server 2003. Therefore, we
require that the operating systems on these servers be Windows 2000 Server SP 4.

4.3 Network location

• The ClearCaseLT VOBs are located at \\ACD2284CC01\ClearCaseStorage\VOBs.

VOB tags will have the following format:

\Admin For the highest level administrative VOB
\<SYSTEM NAME> For a single VOB or the system level
administrative VOB
\<SYSTEM NAME>_<Subsystem> For the main subsystem VOB
\<SYSTEM NAME>_<Subsystem>_<n> For each partitioned subsystem VOB

The project will have the following VOBs:

VOB Name Contents
\Admin Global metadata for all ClearCase implementations
Confidential <Company Name> 2010 Page 6 of 8
<Project name> Version: 2.1
Development Infrastructure Date: 05/25/04

\Documents Project documentation

\Java Source All Java source code
\Web Content All web content including JSP’s, HTML files, style sheets, images, etc.
\Help Source The source files for generating the web help text.
\Configuration The configuration files including property files, external jar files, etc
\Deployment Deployment artifacts including the EAR file, configuration specs for release
versions, deployment and release notes, etc.

4.4 Password
The service account login ID for the Rational Server System is “svc_ccadm”. This account should be an active
directory account and an administrator on the server. It will be a member of the 000-RationalClearCaseAdmins
group. It will also be the ClearCase administrator account.

We created the following security groups in Active Directory:

4.4.1.1 000-RationalClearCaseUsers Group
One important requirement of ClearCase LT involves accounts and groups. ClearCase LT uses your Windows
account to determine access. It is best if everyone requiring access to ClearCase LT is a member of a common
Windows group, either a domain global group or an Active Directory universal group. We generally recommend
creating a ClearCase users group, and making all ClearCase LT users members of this group. It's also a good idea
to create an ClearCase LT administration account and make this account a member of the ClearCase LT users
group. If the ClearCase LT client and server machines are not members of the same domain that the user accounts
and groups belong to, then the machines must be a member of a domain that trusts the user/group domain.
The members of this group will be the ClearCase user community and the service account for ClearCase
administration.
This group will be email-enabled so that the members can be contacted as needed.
A member of the 000-RationalClearCaseAdmins group will authorize adding or removing members from the 000-
RationalClearCaseUsers group.

4.4.1.2 000-RationalClearCaseAdmins Group

This Active Directory group will contain the logins for the persons listed below as Application Owners. The
members of this group will also be local administrators on both servers.
This group will be email-enabled so that the members can be contacted as needed.
These person’s network logins are the members of the 000-RationalClearCaseAdmins security group:
• Debby Jones – Primary Manager Contact
• Mike Teff – Primary Team Lead Contact
• Mike Rogers – Primary ClearCase LT Contact
• Bobby Desser – Secondary ClearCase LT Contact

5. Project Directory Structure

The contents of each folder will be documented in Readme file. The Readme file will be included in each folder. The
Readme will contain information on what should be stored in the folder.

Confidential <Company Name> 2010 Page 7 of 8

<Project name> Version: 2.1
Development Infrastructure Date: 05/25/04

Confidential <Company Name> 2010 Page 8 of 8