Geeks With Blogs

News Ashraful Alam Joy

Create Your Badge

Ashraful Alam is a Software Architect, who has 8 years of professional experience in Software Development industry. This Bangladeshi national is involved with project management and development of several US based software projects from his country. Already he has managed and developed several software projects, which are being used by several users of different countries, such as USA, Canada, Australia, and Bangladesh. While developing and managing a team, he contains and maintains a set of well defined engineering practices developed by him and other online developer communities.

Due to his willingness to give effort to improve and share better software development practices, Ashraf has been awarded as “Most Valuable Professional” (MVP) in ASP.NET category by Microsoft since year 2007 multiple times, which is a rare honor and prestigious reorganization among the developers around the world.

Check his portfolio to know more about him and his works.

.NETTER Characters... Every part of your life is best, if you can know yourself and thus create your life like an artist!


I have been working in SQL Server 2000 for previous several years. Of course it's  a nice tool, where I can compile the top level requirements to physical implementation layer in much professional way. Well, as a developer, I have been faced a common problem in multiple projects, where I got confused while seeing the database diagram of an existing system, after a long time while I designed the database. Using database diagram, I can easily see the data fields, analyze the relations etc. But the problem is, since the attributes and relations are designed and shown in a technical manner, sometimes it becomes a bit tricky to match the top level requirements with the physical data model.

For that reason, I needed a support in the server tools set for another level of documentation, which lies between the top level requirements documents and physical data model.

[Top level requirement doc] -> [Readable documentation of physical db objects] -> [Physical data model]

In this level each physical entities, attributes and relations will be explained in much human readable way,  in short a support for description for database objects, which can easily be integrated, reused in technical way (i.e. support for navigation while clicking/pointing the object in the documentation, specific data logic (for instance how particular query will be achieved using attributes) etc.

Well, right now, I am using MS Word, to describe entities, relations in very simple, but meaningful text and trying to discover a better and smarter structure of database documentation in the mentioned layer.

Posted on Wednesday, October 18, 2006 9:13 PM Database , Software Development | Back to top

Comments on this post: Concentration on Smarter Database Documentation

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Ashraf Alam | Powered by: | Join free