Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
5Activity
0 of .
Results for:
No results containing your search query
P. 1
A Database System High Level Design Template

A Database System High Level Design Template

Ratings: (0)|Views: 4,672|Likes:
Published by Brendan Furey
The concept of top-down design is very important in IT systems design. Every IT system is unique, but also shares many common features with other systems, and one of the keys to good design is to identify the common features. In this way established methods, and perhaps applications and code, can be applied to the majority of the system, leaving just a small part that is genuinely unique. It is similar to the concept in mathematics of solving a complex problem by first reducing it to a problem with a known solution plus an unsolved but smaller additional problem. Achieving the equivalent in IT systems design requires the taking of a similarly abstract view of the system design at the higher levels, and high level design documents can play a key role here. This document provides a template for the high level design of a database system.

Incidentally, it seems likely that lack of a sufficiently rigorous top-down approach may be a major cause of the failure of some big IT projects, where it is especially necessary. I have noticed while working on large pan-European projects a lack of awareness of its importance even within the very large software services providers. There tends to be requirements specifications and very detailed design documents but a gap in the middle (non-technical people, such as managers and business analysts, usually think the more detailed the design the better, but that’s not the case).
The concept of top-down design is very important in IT systems design. Every IT system is unique, but also shares many common features with other systems, and one of the keys to good design is to identify the common features. In this way established methods, and perhaps applications and code, can be applied to the majority of the system, leaving just a small part that is genuinely unique. It is similar to the concept in mathematics of solving a complex problem by first reducing it to a problem with a known solution plus an unsolved but smaller additional problem. Achieving the equivalent in IT systems design requires the taking of a similarly abstract view of the system design at the higher levels, and high level design documents can play a key role here. This document provides a template for the high level design of a database system.

Incidentally, it seems likely that lack of a sufficiently rigorous top-down approach may be a major cause of the failure of some big IT projects, where it is especially necessary. I have noticed while working on large pan-European projects a lack of awareness of its importance even within the very large software services providers. There tends to be requirements specifications and very detailed design documents but a gap in the middle (non-technical people, such as managers and business analysts, usually think the more detailed the design the better, but that’s not the case).

More info:

Categories:Types, Research
Published by: Brendan Furey on Nov 28, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less

07/23/2013

pdf

text

original

 
OracleD
ATABASE
S
YSTEM
H
IGH
L
EVEL
D
ESIGN
T
EMPLATE
Author:Brendan FureyCreation Date:28 November 2010Version:1.0Last Updated:
46877296.doc
.Page 1 of 24
 
Table of Contents
Other XX Tables .........................................................................................................10Database Packages and Functions ..................................................................................11Backend .....................................................................................................................11Web Service Packages ..............................................................................................12Functions ....................................................................................................................12Database Triggers ............................................................................................................13Trigger List.................................................................................................................13Database Links .................................................................................................................14Link List......................................................................................................................14Views/Synonyms ..............................................................................................................15Views .........................................................................................................................15Database Link Views/Synonyms ................................................................................15Interfaces ..........................................................................................................................16Interfaces List.............................................................................................................16Interfaces Diagrams ...................................................................................................16
Batch Programs ................................................................................................................19Interface Jobs .............................................................................................................19Non-Interface Jobs .....................................................................................................19Scripts ...............................................................................................................................20SQL Scripts ................................................................................................................20Unix Scripts ................................................................................................................20User Interactions ..............................................................................................................21Company.com ............................................................................................................21Call Centre .................................................................................................................21Business Objects .......................................................................................................21Database Jobs ..................................................................................................................22Job List.......................................................................................................................22Batch Jobs Schedule ........................................................................................................23
46877296.doc
Page 2 of 24

Activity (5)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Mohan Raj liked this
ghisuddin liked this
Ernestina Er liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->