Hello everyOne,
When designing and developing new large commercial business
applications, what is the preferred charting scheme as part of the
program and system documentation?. 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.
|
