Database Design

:: Client List

:: Latest News
JAKS bagged a prestigious order from Govt. Of Uttar Pradesh for setting up labs in Government Departments>> JAKS & UEPPCB join hands for website upgradation>> JAKS got a prestigious order from AIRTEL, UP West & Uttaranchal for setup of entire Boardroom's wireless LAN>> JAKS continues its success story by getting an order from PEPSICO, Bazpur & Jainpur>> JAKS continue to strive excellence in getting contract from Frooti>> JAKS giving value Proposition for Six Sigma >> JAKS RFID Warehouse Solution>> JAKS bagging a Prestigious order from Indian Defence>> JAKS continue to strive excellence in getting contract for Media Industry>> JAK Software along with MindTree Consulting begged a Largest E-Governance Project for Govt. of Rajasthan

Database Design

The Technical team at JAKS has experience in Database Application Development, setting up and using different databases; used for small projects, to huge and efficient Oracle database servers with complex structure. We have a team with strong database management background and PL SQL programming experience. JAKS can provide with resources onsite or offsite, with a varied experience in Oracle Solutions, as Database Consultants.
The data model is one part of the conceptual design process. The other is the function model. The data model focuses on what data should be stored in the database while the function model deals with how the data is processed. To put this in the context of the relational database, the data model is used to design the relational tables. The functional model is used to design the queries that will access and perform operations on those tables.
Data modeling is preceeded by planning and analysis. The effort devoted to this stage is proportional to the scope of the database. The planning and analysis of a database intended to serve the needs of an enterprise will require more effort than one intended to serve a small workgroup.
The information needed to build a data model is gathered during the requirments analysis. Although not formally considered part of the data modeling stage by some methodologies, in reality the requirements analysis and the ER diagramming part of the data model are done at the same time.
Data modeling must be preceded by planning and analysis. Planning defines the goals of the database, explains why the goals are important, and sets out the path by which the goals will be reached. Analysis involves determining the requirements of the database. This is typically done by examining existing documentation and interviewing users.
An effective data model completely and accurately represents the data requirements of the end users. It is simple enough to be understood by the end user yet detailed enough to be used by a database designer to build the database. The model eliminates redundant data, it is independent of any hardware and software constraints, and can be adapted to changing requirements with a minimum of effort.
Data modeling is a bottom up process. A basic model, representing entities and relationships, is developed first. Then detail is added to the model by including information about attributes and business rules.