Kellie Fitton wrote:
> Hello everyOne,
>
> When designing and developing new large commercial business
> applications, what is the preferred charting scheme as part of the
> program and system do***entation?. I know in the IT world its
> always horses for courses and depending on where you are working,
> however, maintenance, modification and enhancements are always
> a major part of any large business application in the long run.
>
> There are some methods that seem to be favored and work very well
> for describing different sections of a program or a system, which
> I can list three of them here -- perhaps there is a better
> approach that you would like to pointOut, which makes
> maintainability a much easier task:
>
> 1). Data Flow Diagram: to show the flow of data thru the complete
> system and its subSystem modules.
>
> 2). Decision Table: to show listing of the actions required for
> numerous if..else..and case evaluate conditions.
>
> 3). Data Structure Diagram: to show system data and relation****p
> between the data entities within the file system or dataBase.
>
> Regards, Kellie.
>
Hi Kellie,
just as a note for next time, you will get a better response posting
such a general RDB (Relational Database) question to the COMP.DATABASES
newsgroup.
COMP.DATABASES.RDB is specific to the Oracle Rdb database (not the same
as the Oracle Classic Database).
Oracle Rdb Homepage
http://www.oracle.com/technology/products/rdb/index.html
Wikipedia - Oracle Rdb
http://en.wikipedia.org/wiki/Oracle_Rdb
So as not to leave you empty handed, I have collected a few pertinent
links regarding your question.
Data model
http://en.wikipedia.org/wiki/Data_model
Data modeling
http://en.wikipedia.org/wiki/Data_modelling
Conceptual data model
http://en.wikipedia.org/wiki/Conceptual_data_model
Logical data model
http://en.wikipedia.org/wiki/Logical_data_model
Physical data model
http://en.wikipedia.org/wiki/Physical_data_model
There are many methods with associated diagram and modeling techniques.
The next link gives a taste of the various diagrams one may encounter in
any one specific software development shop.
Diagram
http://en.wikipedia.org/wiki/Diagram
Data Structure Diagram
http://en.wikipedia.org/wiki/Data_Structure_Diagram
Entity-relation****p model
http://en.wikipedia.org/wiki/Entity-relation****p_model
Data profiling
http://en.wikipedia.org/wiki/Data_profiling
Database normalization
http://en.wikipedia.org/wiki/Database_normalization
Agile software development is a conceptual framework for undertaking
software engineering projects. There are a number of agile software
development methodologies, such as those espoused by the Agile Alliance,
a non-profit organization.
Agile software development
http://en.wikipedia.org/wiki/Agile_software_development
Data Modeling 101
http://www.agiledata.org/essays/dataModeling101.html
A Vision for the Agile Data Method
http://www.agiledata.org/essays/vision.html
Agile Data Modeling: From Domain Modeling to Physical Modeling
http://www.agiledata.org/essays/agileDataModeling.html
UML is increasingly being adopted, but is not specific to data modeling
for databases, and is intended as a modeling and specification technique
and not a method or life cycle Software Engineering tool.
Unified Modeling Language
http://en.wikipedia.org/wiki/Unified_Modeling_Language
Information Architecture Institute
http://iainstitute.org/
Cheers!
Keith Cayemberg
|
