Posts Topics Forums Images
Search videos from message boards Videos Search messages from microblogs Microblogs Search messages from imdb.com Imdb Search messages from yuku.com Yuku Search messages from lefora.com (free forums) Lefora
My account: Login | Sign Up
Loading... 

Thread: database doccumentation

Started 1 month, 1 week ago by Derek Asirvadem
Quote: Originally Posted by AnanthaP 1 I don't understand why you are not freezing the specs 2 Does it not make the programmers have a rough time? 3 Programmers then would have to define only temporary tables etc. 1 I did not mean it like that. Yes, of course, for any single deliverable, a ...
Site: dBforums - Database Support Community  dBforums - Database Support Community - site profile
Forum: Database Concepts & Design  Database Concepts & Design - forum profile
Total authors: 5 authors
Total thread posts: 9 posts
Thread activity: no new posts during last week
Domain info for: dbforums.com

Other posts in this thread:

AnanthaP replied 1 month, 1 week ago
Derek, The context is clear. Now some clarifications. (1) What do people normally do on MS systems? (2) In my case also, progressive developments are normal and additionally since I work in a large tier II automobile company, I have to face the end user and thus have to give effective systems from day zero. The trick is of course to minimise scope-creep (in a release cycle) by doing a...

Derek Asirvadem replied 1 month, 1 week ago
naumanarshadkiyan Sorry, I missed your post. Quote: thanks for kind reply sir My pleasure. Quote: actually my question was that which reports are used to document a database. e.g capacity planing; data resource planning etc Those are operational reports, not really db documentation. At the ...

blindman replied 1 month, 1 week ago
Quote: Originally Posted by Derek Asirvadem AnanthaP I do occasionally get dragged across to the MS side to inject some quality into that area which is usually devoid of it. I have implemented a few small systems on MS as well. But I am in no way a specialist in that end of town, in fact I do not see the point in being a ...

Derek Asirvadem replied 1 month ago
Anathap Quote: Originally Posted by AnanthaP (1) What do people normally do on MS systems? (2) effective systems from day zero ... The trick is of course to minimise scope-creep ... Actually, I answered both your questions in fair detail. But the post has been deleted by an unknown person for unknown reasons...

HogHunter replied 1 month ago
Quote: Originally Posted by blindman Really? Cuz, I dropped out of Sybase seven years ago after attending a conference in Florida where it became abundantly clear to me that it is a dead and stagnant platform. I suppose if you never want to learn anything new and more powerful, or are incapable of adapting to change, then legacy ...

AnanthaP replied 1 month ago
Anyway, to get back to the original query. As systems get more complex and encompass more and more features, they tend to interact more and more with other systems. In this context, I would add an overall "context" diagram that tells the interaction between the system on hand and other external systems. Here I would detail the nature of the links, whether internal or external, volumes etc. ...

Derek Asirvadem replied 1 month ago
AnanthaP Yes. When you have system interaction you need a context or interaction diagram. For external systems (payment gateways; SWIFT/FIX; etc) we normally have the gateway fully defined once, that includes the interaction/protocol requirements, once. Then each consumer system needs just a chapter on the context/interaction it has with the external system/gateway.

Derek Asirvadem Registered User replied 1 month ago
AnanthaP Yes. When you have system interaction you need a context or interaction diagram. For external systems (payment gateways; SWIFT/FIX; etc) we normally have the gateway fully defined once, that includes the interaction/protocol requirements, once. Then each consumer system needs just a chapter on the context/interaction it has with the external system/gateway.

 

Top contributing authors

Name
Posts
Derek Asirvadem
4
user's latest post:
database doccumentation
Published (2009-11-12 01:54:00)
AnanthaP Yes. When you have system interaction you need a context or interaction diagram. For external systems (payment gateways; SWIFT/FIX; etc) we normally have the gateway fully defined once, that includes the interaction/protocol requirements, once. Then each consumer system needs just a chapter on the context/interaction it has with the external system/gateway.
AnanthaP
2
user's latest post:
database doccumentation
Published (2009-11-11 23:19:00)
Anyway, to get back to the original query. As systems get more complex and encompass more and more features, they tend to interact more and more with other systems. In this context, I would add an overall "context" diagram that tells the interaction between the system on hand and other external systems. Here I would detail the nature of the links, whether internal or external, volumes etc. Tis would carried overinto specific...
blindman
1
user's latest post:
database doccumentation
Published (2009-11-10 12:44:00)
Quote: Originally Posted by Derek Asirvadem AnanthaP I do occasionally get dragged across to the MS side to inject some quality into that area which is usually devoid of it. I have implemented a few small systems on MS as well. But I am in no way a specialist in that end of town, in fact I do not see the point in being a specialist in mere low-end "software" that changes completely every few years, demanding a...
HogHunter
1
user's latest post:
database doccumentation
Published (2009-11-11 15:34:00)
Quote: Originally Posted by blindman Really? Cuz, I dropped out of Sybase seven years ago after attending a conference in Florida where it became abundantly clear to me that it is a dead and stagnant platform. I suppose if you never want to learn anything new and more powerful, or are incapable of adapting to change, then legacy systems such as sybase are the best career choice for you. Do tell? Blindman, This thread is quite revealing,...
Derek Asirvadem Registered User
1
user's latest post:
database doccumentation
Published (2009-11-12 01:54:00)
AnanthaP Yes. When you have system interaction you need a context or interaction diagram. For external systems (payment gateways; SWIFT/FIX; etc) we normally have the gateway fully defined once, that includes the interaction/protocol requirements, once. Then each consumer system needs just a chapter on the context/interaction it has with the external system/gateway.

Related threads on "dBforums - Database Support Community":

Related threads on other sites:

Thread profile page for "database doccumentation" on http://www.dbforums.com. This report page is a snippet summary view from a single thread "database doccumentation", located on the Message Board at http://www.dbforums.com. This thread profile page shows the thread statistics for: Total Authors, Total Thread Posts, and Thread Activity