WHERE ARE THE CORPORATE PROGRAMS TODAY?
Document Type:
Collection:
Document Number (FOIA) /ESDN (CREST):
CIA-RDP90G00993R000300140009-0
Release Decision:
RIPPUB
Original Classification:
K
Document Page Count:
4
Document Creation Date:
December 23, 2016
Document Release Date:
May 1, 2012
Sequence Number:
9
Case Number:
Content Type:
MISC
File:
Attachment | Size |
---|---|
![]() | 82.09 KB |
Body:
Declassified in Part - Sanitized Copy Approved for Release 2012/05/01 : CIA-RDP90GO0993R000300140009-0
STAT
STAT
/, 2r)~,t
Declassified in Part - Sanitized Copy Approved for Release 2012/05/01 : CIA-RDP90GO0993R000300140009-0
Declassified in Part - Sanitized Copy Approved for Release 2012/05/01 : CIA-RDP90G00993R000300140009-0
WHERE ARE THE CORPORATE PROGRAMS TODAY?
1. Who is moving toward or who has implemented a "corporate"
environment using IDMS/R?
2. How do you define "corporate" systems?
3. How are applications development and support activities
divided across organizational boundaries? Is it working?
What are the problems with your organizational structure?
What are the strengths of your organizational structure?
4. What functions does your central data processing organization
perform? What functions does your "customer" organization
perform?
5. Do customer organizations develop any of your "corporate"
systems? How well has this worked? Do you still have a
centralized "corporate" architect and standards function?
How are the standards enforced?
6. Who has the maintenance responsibility for "corporate" systems?
7. To what extent are you developing "corporate" systems vs. using
commercial applications packages?
8. If you're using commercial packages how much customizing have
you had to do?
9. Are you using IDMS/R for other than "corporate" systems?
Declassified in Part - Sanitized Copy Approved for Release 2012/05/01 : CIA-RDP90G00993R000300140009-0
Declassified in Part - Sanitized Copy Approved for Release 2012/05/01 : CIA-RDP90GO0993R000300140009-0
Support costs for IDMS/R
Our early expectations:
"commercial software products will increase our productivity"
"..... will install and be operational quickly"
.... will require less support resources"
"..... Off-The-Shelf software will help reduce our backlog"
Our experiences:
We had unique requirements resulting in significant intergration
requirements. (security,operating systems architecture)
We had significant learning curve problems in all development and
support groups.
We had some overly optimistic schedules.
Declassified in Part - Sanitized Copy Approved for Release 2012/05/01 : CIA-RDP90GO0993R000300140009-0
Declassified in Part - Sanitized Copy Approved for Release 2012/05/01 : CIA-RDP90GO0993R000300140009-0
Round Table Discussion Points:
How does the organizational structure of your agency impact
your IDMS/R support costs?
what are the roles and scope of responsibilities of
your DBA, systems programmers, developers, end
user developers, and operations personnel ?
How much of your support costs are due to unique site
requirements or restrictions? (ie; security or hardware constraints)
Can productivity improvements be made in the area of systems
intergration?
What software maintenance strategies are you using and what
needs to be done to improve productivity in this area?
What are your configuration management (change control) procedures
and what can be done to improve productivity in this area?
Do you have different support costs associated with different
data base management systems? Can the same support strategies be
used across various systems?
Declassified in Part - Sanitized Copy Approved for Release 2012/05/01 : CIA-RDP90GO0993R000300140009-0