1. Revision 1.0
TIER II CONSOLIDATION
TECHNICAL AWARENESS (TA) and
TECHNICAL REQUIREMENTS REVIEW (TRR)
STANDARD OPERATING PROCEDURES
Prepared by the Tier II Technical Support Center
Distributed Systems Management Support
2. DRAFT
i
TABLE OF CONTENTS
1 Introduction .................................................................................................................. 1
1.1 Definitions.......................................................................................................................... 1
2 The TA and TRR Process ............................................................................................ 1
2.1 Purpose of the TA and TRR............................................................................................... 1
3 TA Procedures ............................................................................................................. 3
3.1 Data Collection Activity ...................................................................................................... 3
3.2 Conduct of the TA.............................................................................................................. 4
4 TRR Procedures........................................................................................................... 5
5 Identification, Roles, and Responsibilities of TA and TRR Participants........................ 6
5.1 The DSMB TA and TRR Team .......................................................................................... 6
5.1.1 DSMB Project Management Office (PMO) Contact/Moderator....................................... 6
5.1.2 TA Coordinator .............................................................................................................. 6
5.1.3 SUN Section Contact..................................................................................................... 7
5.1.4 Database Section Contact ............................................................................................. 7
5.1.5 Optional Attendees ........................................................................................................ 7
5.1.5.1 Hardware Architecture Contact.................................................................................. 7
5.1.5.2 Infrastructure Migration Test (IMT) Contact ............................................................... 7
5.1.5.3 DSMB Capacity Management Contact....................................................................... 7
5.1.6 Scribe(s)........................................................................................................................ 7
5.2 Tier II Consolidation Project Office (T2CPO)...................................................................... 8
5.3 Project (Application) Team................................................................................................. 8
5.3.1 Project Manager/Lead ................................................................................................... 8
5.3.2 Development Lead and Team........................................................................................ 8
5.3.3 Subject Matter Experts (SMEs)...................................................................................... 8
6 TA Products ................................................................................................................. 8
6.1 Meeting Notes.................................................................................................................... 9
6.2 Follow-up Items (FUIs)....................................................................................................... 9
6.3 Items Requiring Clarification .............................................................................................. 9
6.4 TRR Discussion Points ...................................................................................................... 9
APPENDIX A - TA Meeting Agenda Format...............................................................A - 1
4. DRAFT
1
1 Introduction
As projects (applications) continue to migrate into the Tier II Consolidated Environment, the
understanding of a project’s infrastructure requirements is essential. With a clear understanding
of a project’s infrastructure requirements by both the project and Tier II staff, a successful
migration into the Tier II Consolidated Environment will be achieved.
For the purposes of the Tier II Consolidation effort, DSMB will conduct the Technical Awareness
(TA) and Technical Requirements Review (TRR) meetings. These TA and TRR meetings
collect requirements from the Project and develop an understanding with the Projects.
1.1 Definitions
Data Collection Activity: The assembly of Project relevant information that provides DSMB with
an understanding of the Project’s requirements prior to the TA. The following types of
documentation are collected:
• Requirements Assessment Form (RAF) or Input Requirements Assessment Document
(IRAD)
• System description
• System flowcharts
• Waivers (when available)
• Schedule requirements
• Consolidated location
• Capacity Studies
• Request for Information Services (RIS)
Technical Awareness (TA): The meeting hosted by DSMB with the Project to form collaborative
relationships with the staffs, explain the concept of a consolidated and shared environment, and
discover the infrastructure impacts of the Project's business requirements.
Refer to Appendix A for the TA agenda.
Technical Requirements Review (TRR): The process for examining the TA findings to derive the
technical specifications for the infrastructure resources to be provided for the Project within
established IRS and DSMB standards. DSMB presents a formal TRR Document to the project
for them to assess and agree on the requirements and recommendations specified by DSMB.
2 The TA and TRR Process
In the context of Tier II Consolidation, the TA and TRR Process is the Tier II corollary of the
traditional life-cycle stage of Requirements Definition.
2.1 Purpose of the TA and TRR
The purpose of the Technical Awareness (TA) meeting is to introduce the project staff and
DSMB and explain the concept of a consolidated and shared environment, while defining the
infrastructure requirements of the project in relation to the Tier II Consolidated Environment.
The TA (or Technical Awareness) meeting serves as the initial requirements meeting between
DSMB and the Project (Application) staff. Tier II Consolidation Project Office (T2CPO) often
attends for information.
5. DRAFT
2
The TRR (or Technical Requirements Review) serves as the follow-on to the TA for a more
technically detailed session to agree upon the content of the TRR document.
Refer to Section 5 for the identification, roles, and responsibilities of the TA and TRR
participants.
6. DRAFT
3
3 TA Procedures
The following procedures will guide the conduct of the TA meeting, and must be strictly adhered
to. This is to ensure both an orderly progression throughout the meeting, and to ensure that all
required items are covered during the course of the meeting.
ACTION: PREPARE FOR AND CONDUCT TA MEETINGS
Responsible Party Action Metric Escalation/Referral Pt
PRE-TA ACTIVITIES
TA Coordinator Schedule TA Meeting At least 1 month in
advance
DSMB PMO
T2CPO POC Provide all available
Project materials to TA
Coordinator
At least 2 weeks before
meeting
DSMB Management
TA Coordinator Provide TA Agenda and
supporting materials to
all Team members
At least 48 hours before
meeting
DSMB PMO
Moderator Fill in the Agenda
templates with
introductory information
At least 24 hours before
meeting
DSMB Management
Section Contact Fill in the Agenda
templates with section
information
At least 24 hours before
meeting
DSMB PMO
TA MEETING
Moderator Introduce meeting
participants
5 minutes DSMB Management
Moderator Provide an overview of
the TA process
5 minutes DSMB Management
Moderator Provide an explanation
of references
5 minutes DSMB Management
Moderator Conduct ‘Open
Discussion’ period
30 – 45 minutes or
longer
DSMB Management
Section Contacts Address Project
(Application)
requirements for their
section
As Needed DSMB Management
Moderator Meeting ‘Wrap-up’ 5 – 10 minutes DSMB Management
POST-TA ACTIVITIES
TA Team Follow-up Items (FUIs)
Meeting
30 – 60 minutes DSMB Management
TA Team Prepare FUIs 30 – 60 minutes DSMB PMO
Scribe Prepare Meeting Notes 48 hours DSMB PMO
TA Team members Submit corrections 24 hours DSMB PMO
PMO Post Notes to DSMB
Web site
24 hours DSMB Management
3.1 Data Collection Activity
Generally, a properly completed RAF or IRAD document will be the major source of relevant
Project Information. It will contain the Project’s current hardware/software status and a
description of what the target system is expected to look like. The Document should contain the
names of Project responsible parties and their contact information.
7. DRAFT
4
It is the responsibility of the T2CPO to provide RAF or IRAD documents to the DSMB TA
Coordinator as required. It is also the responsibility of the T2CPO to provide at least one (1)
Point of Contact (POC) for the Project. This POC will also interface with DSMB in the TA
process, and will facilitate interactions between the Project and DSMB in the acquisition of
materials required by DSMB to prepare for a TA.
Additional data may be collected by DSMB from supporting T2CPO staff and/or Project
members by personal contact, web search, email contact, or telephone conversation. The
materials assembled by the Data Collection Activity are evaluated and are input to the TA team.
3.2 Conduct of the TA
The TA is a meeting between DSMB and the Project. The T2CPO POC for the Project should
be present to clarify the T2CPO position, when needed, and to gain an understanding of the
Project's requirements, characteristics, etc.
After the introduction by the T2CPO, the DSMB PMO/Moderator will have control of the TA
meeting. The Moderator has complete authority during this portion of the TA meeting.
A large audience is counter-productive since it tends to distract from the TA by creating
extraneous noise and movement. Side conversations will not be allowed. Individuals engaging
in side conversations will be asked once to curtail that activity. If they continue, they will be
excused from the meeting.
The successful TA requires free interaction between the TA team and the representatives of the
Project. These Project representatives will be conversant with the Project’s business and
technical requirements, and have the technical expertise to translate the Project’s business
requirements into viable hardware/software system(s).
Follow on TA(s) may be scheduled at the discretion of DSMB in the event that outstanding
questions exist about the Project’s requirements after the initial TA is concluded.
Refer to Section 6 for the details of the TA products.
8. DRAFT
5
4 TRR Procedures
The Technical Requirements Review (TRR) is a two-week process where contacts and the
PMO get closure and understanding on all infrastructure requirements.
The following procedures will guide the conduct of the TRR meeting, and must be strictly
adhered to. This is to ensure both an orderly progression throughout the meeting, and to
ensure that all required items are covered during the course of the meeting.
ACTION: PREPARE FOR AND CONDUCT TRR MEETING
Responsible Party Action Metric Escalation/Referral Pt
PMO/Moderator Distribute TRR
Document to DSMB and
Project teams
At least 2 days before
the TRR meeting
DSMB Management
Moderator Introduce meeting
participants
5 minutes DSMB Management
Moderator, Project
Team
Review of TRR
Document
1 – 1.5 hours DSMB Management
Moderator, Project
Team
Wrap-up and Sign-off 15 minutes DSMB Management
PMO/Moderator Provide draft Change
Request (CR) when
Project signs the TRR
End of TRR meeting DSMB Management
Scribe Prepare Meeting Notes 48 hours DSMB PMO
Scribe Submit Notes to PMO 24 hours DSMB PMO
PMO Post Notes to DSMB
Web site
24 hours DSMB Management
The Project (Application) team will address any concerns in the document. The DSMB team will
note these items. If a consensus can be achieved, that will be noted. These items may be re-
evaluated as included in a revised TRR document.
Each section contact will be responsible for taking notes pertaining to their discussion area.
These notes will be copied by the section contact, and provided to the team scribe for inclusion
in the Project (Application) Case File.
If all questions, concerns, and issues have been addressed at the conclusion of the TRR
meeting, The PMO contact and the Project (Application) contacts will sign off indicating that
agreement has been reached.
If there are changes required to the TRR Document, the PMO contact will specify a date when a
follow-on session may be held, and sign-off obtained.
9. DRAFT
6
5 Identification, Roles, and Responsibilities of TA and TRR Participants
The personnel attending a TA and TRR meeting will represent the following groups:
• The Distributed Systems Management Branch (DSMB)
• The Project (Application) and the IS Support Team
5.1 The DSMB TA and TRR Team
The Distributed Systems Management Branch (DSMB) will provide the following personnel to
attend the TA and TRR meeting:
• DSMB Project Management Office (PMO) Contact/Moderator
• TA Coordinator
• A SUN Section Contact
• A Database Section Contact
• Optional Attendees
• Hardware Architecture Contact
• Infrastructure Migration Test (IMT) Contact
• A DSMB Capacity Management Contact
• One or more Scribes
5.1.1 DSMB Project Management Office (PMO) Contact/Moderator
The DSMB Project Management Office (PMO) Contact/Moderator, hereafter referred to as ‘The
Moderator’, will guide the meeting. This includes, but is not limited to, the introductory period.
The Moderator is responsible for controlling the discussion using the TA Agenda as a guideline
for discussion.
The Moderator will additionally serve as the DSMB contact for the Project (Application).
The Moderator will be responsible for controlling staff members who may have a tendency to
dominate the meeting with their own section’s agenda and focus. The contacts need to
remember that this a requirements gathering session, and that ample time will be provided for
the TRR preparation to explore lengthy details, impacts, ramifications, alternatives, business
practices during Follow Up Item (FUI) preparation for the TRR. This restraint is needed so that
all DSMB sections may participate in the meeting within the timeframe allowed.
The Moderator may, at his/her discretion, stop a discussion path to get the meeting back on
focus. Team members who do not follow the direction of the Moderator may, at the request of
the Moderator, be replaced in further meetings.
5.1.2 TA Coordinator
The TA Coordinator is responsible for arranging the TA meeting, and ensuring that all materials
needed (white board, phone access for dial-in participants, etc.) have been procured.
The TA Coordinator will serve as the liaison between the DSMB team and the T2CPO. The TA
Coordinator will endeavor to obtain all relevant Project materials from the T2CPO at least 2
weeks before the scheduled TA.
10. DRAFT
7
The TA Coordinator should provide the team members with the Agenda, and all associated
supporting materials, at least 48 hours before the meeting is held.
The moderator and section contacts will fill in their templates with their respective information to
stimulate a meaningful discussion of their items.
5.1.3 SUN Section Contact
The SUN Section contact will address those items in the TA Agenda corresponding to SUN
Section’s area of responsibility. He/she is to be concerned only with items that will affect the
SUN Section, and will confine all questions to the Project (Application) requirements that would
affect his/her section.
5.1.4 Database Section Contact
The Database Section contact will address those items in the TA Agenda corresponding to
Database Section’s area of responsibility. He/she is to be concerned only with items that will
affect the Database Section, and will confine all questions to the Project (Application)
requirements that would affect his/her section.
5.1.5 Optional Attendees
The following optional attendees will be responsible for items within their area of responsibility.
If they are unable to attend, the Moderator will address those items.
5.1.5.1 Hardware Architecture Contact
The DSMB Hardware Architecture contact will address those items in the TA Agenda
corresponding to DSMB Hardware Architecture’s area of responsibility. He/she is to be
concerned only with items that will affect the DSMB Hardware Architecture group, and will
confine all questions to the Project (Application) requirements that would affect his/her section.
5.1.5.2 Infrastructure Migration Test (IMT) Contact
The DSMB Infrastructure Migration Test (IMT) contact will address those items in the TA
Agenda corresponding to DSMB Infrastructure Migration Test (IMT)’s area of responsibility.
He/she is to be concerned only with items that will affect the DSMB Infrastructure Migration Test
(IMT) group, and will confine all questions to the Project (Application) requirements that would
affect his/her section.
5.1.5.3 DSMB Capacity Management Contact
The DSMB Capacity Management contact will address those items in the TA Agenda
corresponding to DSMB Capacity Management’s area of responsibility. He/she is to be
concerned only with items that will affect the DSMB Capacity Management group, and will
confine all questions to the Project (Application) requirements that would affect his/her section.
5.1.6 Scribe(s)
The scribe will document the main points of the TA meeting. Wherever possible, the scribe will
document the various facets of the ‘Open Discussion” period to the best of his/her ability with
help from the contacts in the follow-on meeting.
11. DRAFT
8
The scribe may, at his/her discretion, request that a meeting be recorded for later transcription.
If recorded, the scribe must announce that the meeting will be recorded, and get agreement
from all parties present.
5.2 Tier II Consolidation Project Office (T2CPO)
The Tier II Consolidation Project Office (T2CPO) will provide one (1) contact to the TA and TRR
sessions per Project (Application). The contact of the T2CPO will provide the perspective of the
Project Office for the TA and TRR meeting, and serve as the Point of Contact (POC) for the
T2CPO. This POC will also interface with DSMB in the TA process, and will facilitate
interactions between the Project and DSMB in the acquisition of materials required by DSMB to
prepare for a TA.
It is the responsibility of the T2CPO to provide all available Project documentation including,
when available, the RAF or IRAD documents to DSMB as required.
5.3 Project (Application) Team
The Project (Application) Team will provide the following personnel to attend the TA and TRR
meeting:
• Project Manager/Lead
• Development Lead and Team
• Subject Matter Experts (SMEs)
5.3.1 Project Manager/Lead
The Project Manager/Lead will provide the management focus for the Project (Application)
team, and serve as primary liaison to the DSMB TA Team and the T2CPO Point of Contact.
5.3.2 Development Lead and Team
The Development Lead and Team will provide the technical expertise regarding the Project
(Application). This individual will posses an in-depth knowledge of the technical requirements of
the Project (Application), and will be available for subsequent meetings, if circumstances
warrant.
5.3.3 Subject Matter Experts (SMEs)
The Subject Matter Experts (SMEs) will provide the business perspective needed for a complete
understanding of the project’s (Application’s) requirements.
6 TA Products
The TA meeting process will produce a specified set of deliverables. These include, but are not
limited to, the following:
• Meeting notes, including notes from all meeting participants.
• A list of “Follow-up items” (FUIs) for management action.
• A list of items requiring further clarification from the Project (Application).
• A list of discussion points for the follow-on Technical Requirements Review (TRR).
• A draft CR for the project signing the TRR document.
12. DRAFT
9
6.1 Meeting Notes
The notes compiled during the meeting by the scribe will eventually be posted to the DSMB
website. The TA Team notes will be placed into the Project (or Case) folder.
The scribe should endeavor to compile the meeting notes, and distribute them to the team for
comment within 48 hours. The team members will then have 24 hours to submit any
corrections. After all corrections have been made, the TA notes will be posted to the DSMB
website
6.2 Follow-up Items (FUIs)
The Follow-up Items (FUIs) are items/issues that must be escalated to DSMB management for
action, and tracked until resolved. Each section contact will be responsible for items within their
respective area.
These items will be addressed daily by DSMB management until closed. If a resolution is not
pending in the near future, the section contact must determine an estimated closing date, and
update the Projects Database accordingly.
6.3 Items Requiring Clarification
Items requiring clarification are those that require a response on the part of the Project
(Application) team. These items may be about any subject that was discussed during the TA
meeting. The section contact who identified the item is responsible for documenting this item,
and monitoring it until it is resolved.
All items requiring clarification should be resolved prior to the TRR session. If this is not
possible, then the section contact must state that this item is still open at the TRR meeting.
6.4 TRR Discussion Points
The TRR discussion points will be drawn from the TA meeting notes, any follow-on TA meeting
notes, the IRAD, and other sources as applicable. TRR discussion points are addressed prior
to the TRR with the Project POC for clarification and/or resolution. Any follow-on discussion
may be presented at the TRR.
13. DRAFT
A - 1
APPENDIX A - TA Meeting Agenda Format
The following pages present the TA Meeting Agenda format. This is the format that should be
followed for all TA meetings unless there is a specific need to deviate from this format. This
format may be revised as needed to reflect changes and improvements in the TA and TRR
process.
1. Introductions
TA Team
Position Name Phone Number
PMO/Moderator: 202-
TA Coordinator:
SUN Section:
Database Section:
DSMB Capacity Mgmt:
Scribe:
Other
T2CPO
Position Name Phone Number
POC:
Application Team
Position Name Phone Number
Project Manager/Lead:
Development Lead:
Subject Matter Expert(s)
2. TA Overview (Moderator)
3. References
Accessible from the DSMB Home Page (http://ssd.web.irs.gov/dsmb/):
• Approved Products List on the DSMB web site
• SIG (Standards Implementation Guide) within the Standards page)
• Infrastructure Migration Testing and Migration Standards (within the Standards
page)
All technical requests are to be directed to the TSC Hotline or Email Address (202-
283-5465, *Tier-II-Tech-Support-Center@irs.gov) and the DSMB Project
Management Office (PMO) contact
4. Project Manager – Presents the Project to DSMB.
• General Discussion prior to questions
5. Business Requirements
14. DRAFT
A - 2
• Planned transition to SUN
• Hardware requirements
• DB requirements
• Future requirements
• Project specifics
• Approved Products List
• Approved by Tier II, but not necessarily funded by Tier II
• COTS
• Waivers
• Purpose
• Time Dependent
• Alternative
• Required
• Reviewed
• Approved or denied
• Duration
• WBS
• This is a required item
• The Project needs to add IMT activities to their WBS
• This will be addressed by the T2CPO WBS Coordinator
• Section 508 Compliance
• Projects must meet with the Section 508 office to determine the applicability
of Section 508 requirements for their project
• Security Issues
• Live taxpayer data
• Other
• Scripts
• Training
• This must be minimized - Scope Creep!
6. Open discussion
6.1 Moderator
6.1.1 Identify Requirements
Implementation Schedule/Production Update Window:
• Was it provided?
Required Production Date:
• Is there any Business Requirement to substantiate this Production date.
• Is the Project Tier B Funded?
• If Yes, please provide supporting documentation
Resources
• DR
15. DRAFT
A - 3
• Oracle Support
• Other
6.1.2 Security certification status and the application security requirements
6.1.3 Physical, audit, and privacy control
• Items to address
6.1.4 SAT/Testing/Transmittals/Self SAT or other
6.1.5 Update of Application documentation required for Production
Does the Project documentation include the COH, CPB, etc.
• If Yes, it must be provided to DSMB
• Location
• Current status
• If No, the project will need to provide it by the date in the schedule
6.1.6 Production Schedule ------ duration, peaks, locations
• Hours of operation
• Expected uptime
• Tolerance for downtime (required for mandatory maintenance/patching
versus costs to the Project for fail-over capabilities)
• Backups
6.1.7 Telecomm Concerns need to be addressed by the Project to the Telecomm
group.
• Volume Statistics
6.1.8 Staffing – availability of development team, requirement for assistance, in what
area(s)
6.1.9 CR Status
• Development: At TRR if we get enough information
• Production: At a later date
• DR:
6.1.10 Freeware/Shareware/COTS products proposed:
• In Development
• In Production
6.1.11 Will application development be performed at MCC?
16. DRAFT
A - 4
6.1.12 If development is not performed at MCC:
• OS and version proposed:
• Database, version and development tools proposed:HW proposed:
• Everything must be compiled and thoroughly tested at MCC.
• The application will be responsible for maintaining consistency of all
versions of software offsite that are implemented on the development
platform at MCC.
• All transmittals to IMT and Production must come from MCC through
Software Distribution Operations (SD OPS) or the DSMB interim
transmittal process.
• What is the Application’s proposed procedure to transmit the application
to the development and test domains at MCC:
6.1.13 ClearCase must be used. The software does exist at MCC.
• The application is responsible for getting the account and training
scheduled through ITCC. They can contact Carol Usher (M:I:PA:I:SC) at
202-283-5952.
6.1.14 Number of Users in the system
• Total:
• Concurrent:
6.1.15 Is there a need for Training environment:
(affects Database and SUN Sections)
6.1.16 Will this be a web application:
(impacts Architecture, Database and SUN Sections)
• What web app server is proposed:
6.1.17 Dataflow Description
• Application file system
• Data Media requirements (tape?)
• Data access/retention (near line, archive?)
• External feeds (typically ftp) or Interfaces
• Databases
6.1.18 Workflow Description
• User Interface
17. DRAFT
A - 5
• External User dependencies/interfaces
• Transaction volumes
• Concurrent user requirements
• Adjunct and Ad Hoc business requirements
6.1.19 Connectivity
• Schedule/frequency
• Size of communications
• Required transfer rates (may be an operations window dependency)
• Quality of Service
6.1.20 Security (The Moderator will ensure these topics are addressed)
• Logging/audit requirements
• Firewall/intranet/internet
• Approved software
• User Access
• Ad Hoc processes
6.1.21 (To be addressed by Moderator or Capacity Representative)
• Latest Capacity Study Date:
• Status:
6.1.22 Legacy/External constraints (such as modem software, etc.)
6.1.23 Special Migration Concerns
6.1.24 Service Level Agreement (SLA) will be coordinated by T2CPO
6.2 Database Section
6.2.1 Database:
6.2.2 Is the application proposing multiple instances on development or production?
6.2.3 If this is an Informix to Oracle Conversion, will the application perform parallel
processing/testing?
18. DRAFT
A - 6
6.2.4 Does the application contain tax payer or other sensitive data
• What is the interface to get the data?
• How is the data used?
• How is the data reported?
• How is the data displayed?
• How is the data printed?
• Is the data transmitted to other interfaces?
• What, if any, storage, cut/copy/paste functions occur on the Tier 3?
6.2.5 Scripts (#s, tools, shell), CRON jobs, system level, process spawning
6.2.6 Database/file sizes
Current System:
New System:
6.2.7 Command line access
(The application must read the SIG for further guidance)
6.2.8 Generic accounts
6.2.9 Interfaces with other systems/offices, downloads, shared files with other apps
or sites
6.2.10 Installation procedures ----- scripts, interaction by SA
(refer the application to the IMT and Migration Standards for further guidance)
6.2.11 Data migration strategy from current system to the new:
6.2.12 Has the Application been baselined for movement to the new environment?
6.2.13 Backup requirements
6.2.14 Development Tools/Test
(project must purchase DB development tools, e.g., Oracle Developer and
Oracle Context Cartridge)
6.2.15 What software is anticipated to be loaded on the client workstation:
6.2.16 Adhoc Query tools used in current system:
6.2.17 Report generation tools used in current system:
19. DRAFT
A - 7
6.2.18 What is the process for report generation?
6.2.19 How is the application planning to do user authentication?
6.2.20 Does the application require user level auditing? (can be affected by connection
pooling)
6.2.21 Will the application require ODBC or JDBC connection to the database?
6.2.22 Will any data reside on the client workstation?
6.3 SUN Section
6.3.1 OS:
6.3.2 Disk storage requirements:
6.3.3 Generic accounts
Are there any NT Workstations or Servers in the current Development or
Production environment?
• If Yes, explain in detail
6.3.4 Parallel processing requirements – requires multiple domains:
(Informix to Oracle Conversions)
6.3.5 Will the application be executing any code as daemons?
6.3.6 Is the application proposing the use of any TCP/IP ports?
6.3.7 Is there any exchange of data with other hosts?
6.3.8 Are there any special file system requirements (including NFShares)?
6.3.9 What are the requirements for server availability/downtime availability?
6.3.10 Are any specific compilers required by the application?
6.3.11 What are the CRON requirements for the application?
6.3.12 Command line access to the server is not permitted.
6.3.13 Equipment
• Installed base equipment (existing):
• Proposed baseline equipment:
• Is there a requirement to maintain the existing system for any time
period:
20. DRAFT
A - 8
6.3.14 Print/Reporting Requirements
• Destinations
• Volumes
6.3.15 Backup requirements
6.3.16 Disaster Recovery
• What does the application business need dictate? (DR and maintenance
requirements)
• Application must provide a copy of the document justifying the need.
• Static/Dynamic restore requirements
• Projected sizes
• Acceptable degradation of capability
• What is the turn around time:
6.3.17 Maintenance
• Code Upgrades
• Data Updates
• Scheduled windows of availability
6.3.18 How many Production sites are proposed?
• The application must provide business justification for having more than
one.
