“  SANKALAN ” Gathering things together … Rishabh Enterprises Sanwer Road,Indore ( M.P. ) for by : Kiran Prasad Kushagra G...
Universe of Database <ul><li>Rishabh Enterprises: </li></ul><ul><li>Having benchmark record in industrial maintenance of: ...
Rishabh Enterprises <ul><li>Three main Divisions: </li></ul><ul><ul><li>Shah Electricals </li></ul></ul><ul><ul><ul><ul><l...
Rishabh Enterprises <ul><li>Goals: </li></ul><ul><ul><li>Timely and successful job completion. </li></ul></ul><ul><ul><li>...
Rishabh Enterprises <ul><li>Current System: </li></ul><ul><li>No any computerized System </li></ul><ul><li>All the jobs ar...
Rishabh Enterprises <ul><li>Current System: </li></ul><ul><ul><li>Further Processing </li></ul></ul><ul><ul><li>A Motor Re...
Rishabh Enterprises <ul><li>Current System: </li></ul><ul><li>Respective employee tells about the work done </li></ul><ul>...
Rishabh Enterprises <ul><li>Limitations of Current System: </li></ul><ul><li>No proper maintenance of information in any p...
Rishabh Enterprises <ul><li>Limitations of Current System: </li></ul><ul><li>No records of previous industrial visits  </l...
Rishabh Enterprises <ul><li>Proposed System: </li></ul><ul><li>Record of all the Customers </li></ul><ul><li>Payments of B...
Rishabh Enterprises <ul><li>Proposed System: </li></ul><ul><li>Records of all kinds of Motors </li></ul><ul><li>Searching ...
Aim of “SANKALAN” “ To design and develop a fully automated system for the Rishabh Enterprises and thereby learning the co...
Objectives of “SANKALAN” <ul><li>To learn the concepts of Database Management System. </li></ul><ul><li>To perform a thoro...
Objectives of “SANKALAN” <ul><li>To follow SDLC to develop the system. </li></ul><ul><li>To develop an appropriate Enterpr...
Goals of “SANKALAN” <ul><li>To make a responsive, easy to operate, fast and efficient retrieval of information as per the ...
Goals of “SANKALAN” <ul><li>To make a database that is consistent, reliable and secure. </li></ul><ul><li>To provide corre...
Current Scenario Main dealing of the Rishabh Enterprises is with  CUSTOMER . A  CUSTOMER  comes to the Organization at the...
Current Scenario A  MOTOR REQUEST  is sent to Shah Electricals,  BLADE REQUEST  to Sharp Edge and an  INDUSTRIAL VISIT REQ...
Entity Identification <ul><ul><li>Customer </li></ul></ul><ul><ul><li>Division </li></ul></ul><ul><ul><li>Employee </li></...
Enterprise Data Model Receives Supplied by  Requires  Requires  Forwarded to Forwarded to Prepared by Pays through Worked ...
Transaction Requirements <ul><li>System must provide password to the user for their identification. </li></ul><ul><li>User...
Input/Output Requirements <ul><li>Input Requirements: </li></ul><ul><li>Details of the employees working in the organizati...
Input/Output Requirements <ul><li>Output Requirements: </li></ul><ul><li>Details of the job done on a particular motor cam...
System Development Methodology System development Life Cycle (SDLC): Project Identification and selection. Project Initiat...
Time Scheduling Gantt chart - Demonstration - Testing & Implementation * Physical Design & Coding * Logical Design * Conce...
Project Identification & Selection <ul><li>Centre for Advance Technology (CAT) </li></ul><ul><li>Rajshahi Palace </li></ul...
Initiation & Planning <ul><li>“ Sankalan” </li></ul><ul><li>Gathering Things Together… </li></ul><ul><li>An opportunity to...
Analysis Phase <ul><li>Scheduled a series of meetings with Client </li></ul><ul><ul><li>3 meetings with Dheeraj Bhai Shah ...
Analysis Phase <ul><li>Questions asked: </li></ul><ul><ul><li>Complete organizational Structure </li></ul></ul><ul><ul><li...
Design Phase <ul><li>Three steps in Design Phase </li></ul><ul><ul><li>Conceptual Design </li></ul></ul><ul><ul><li>Enhanc...
Design Phase <ul><li>Conceptual Design </li></ul><ul><li>Entity Identification </li></ul><ul><li>Listing attributes for al...
Design Phase  Conceptual Design <ul><li>List of all the Entities Identified from Analyzed Scenario: </li></ul><ul><ul><li>...
Design Phase  Conceptual Design <ul><li>Relationship Identification between Entities: </li></ul><ul><li>MOTOR poses DEMAND...
Design Phase  Conceptual Design Relationship Identification between Entities: MOTOR poses   DEMAND   <ul><li>A MOTOR may p...
Design Phase  Conceptual Design Identification of Weak & Associative Entities: Two Weak Entities identified DEMAND SUPPLIE...
Design Phase  Conceptual Design Super type/Subtype Classification: Two Super type/Subtype Relations Identified 1.)  REQUES...
Design Phase  Conceptual Design Super type/Subtype Classification: Two Super type/Subtype Relations Identified 2.)  EMPLOY...
Final EER Schema S_BILL MOTOR BILL DIVISION REQUEST CUST_TRANS SUPPLIER_PAYMENT STOCK SUPPLIER_STOCK DEMAND MTR_JOB_CARD B...
Design Phase <ul><li>Logical Design: </li></ul><ul><li>Conversion from Entity to Relation </li></ul><ul><li>Entity Relatio...
Design Phase  Logical Design Conversion from Entity to Relation: CUSTOMER Cust_Id  Cust_Name  Industry_Name  Cust_Add  Cus...
Design Phase  Logical Design Primary key-Foreign key association between Relations: CUSTOMER Cust_Id   Cust_Name   Industr...
Design Phase  Logical Design Normalization: First Normal Form: No multivalued Attribute detected in any of the Relations S...
Design Phase <ul><li>Physical Design: </li></ul><ul><li>Designing Fields: </li></ul><ul><ul><ul><ul><li>Type of data (stor...
Design Phase  Physical Design Relation:   CUSTOMER Primary Key:  Cust_Id Not Null Number Balance Due to Customer Bal_Due N...
Design Phase  Physical Design Choosing Database (Back-End Tool): SQL Server 2000: Internet Integration Scalability and Ava...
Design Phase  Physical Design <ul><li>Choosing Front-End Tool: </li></ul><ul><li>Visual Basic Dot Net (VB.Net): </li></ul>...
Implementation, Coding & Testing  CUSTOMER Table: CREATE TABLE [dbo].[Customer] ( [Cust_ID] [varchar] (10)  NOT NULL , [Cu...
Conclusion  Problem Areas: Searching of UoD System Analysis Selection of DBMS Representation of various Business Functions...
Conclusion  <ul><li>Lesson Learned: </li></ul><ul><li>Experience to convenience the unknown client (Searching Phase) </li>...
The Working Log Project Leader: Kushagra Goyal System Analysis: Sushil Kumar Singh Kushagra Goyal Database Design: Kiran P...
Thank You!!!
Upcoming SlideShare
Loading in …5
×

Industrial Automation

1,690 views

Published on

Published in: Education, Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,690
On SlideShare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
35
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Sankalan
  • Industrial Automation

    1. 1. “ SANKALAN ” Gathering things together … Rishabh Enterprises Sanwer Road,Indore ( M.P. ) for by : Kiran Prasad Kushagra Goyal Sushil Kumar Singh MCA III rd semester
    2. 2. Universe of Database <ul><li>Rishabh Enterprises: </li></ul><ul><li>Having benchmark record in industrial maintenance of: </li></ul><ul><ul><ul><ul><ul><li>Heavy industrial motors and </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Metal sheet cutting blades. </li></ul></ul></ul></ul></ul><ul><li>It is situated at </li></ul><ul><li>Agarbatti Complex, </li></ul><ul><li>Sanwer Road, </li></ul><ul><li>Indore. </li></ul>
    3. 3. Rishabh Enterprises <ul><li>Three main Divisions: </li></ul><ul><ul><li>Shah Electricals </li></ul></ul><ul><ul><ul><ul><li>Deals with Repairing and Rewinding of old worn-out Motors </li></ul></ul></ul></ul><ul><ul><li>Sharp Edge </li></ul></ul><ul><ul><ul><ul><li>Deals with Grinding and Sharpening of metal sheet cutting blades </li></ul></ul></ul></ul><ul><ul><li>Industrial Visit </li></ul></ul><ul><ul><ul><ul><li>Deals with visits to various Industries on the basis of the Request made </li></ul></ul></ul></ul>
    4. 4. Rishabh Enterprises <ul><li>Goals: </li></ul><ul><ul><li>Timely and successful job completion. </li></ul></ul><ul><ul><li>The job completed must be done of good – quality. </li></ul></ul><ul><ul><li>Proper administration of business firms. </li></ul></ul><ul><ul><li>And total cooperation among all divisions of the organization. </li></ul></ul><ul><ul><li>Complete customer satisfaction. </li></ul></ul><ul><li>Critical Success Factors: </li></ul><ul><ul><li>Maintain healthier customer relationship. </li></ul></ul><ul><ul><li>Good financial management </li></ul></ul>
    5. 5. Rishabh Enterprises <ul><li>Current System: </li></ul><ul><li>No any computerized System </li></ul><ul><li>All the jobs are done manually on papers </li></ul><ul><li>A Customer comes and submits his Request. </li></ul><ul><li>Request </li></ul><ul><li>To Purchase or Repair a Motor </li></ul><ul><li>For the repair of electrical panel or a starter </li></ul><ul><li>To grind or manufacture an industrial Blade, </li></ul><ul><li>For an industrial visit. </li></ul><ul><li>A job card sheet is filled manually and kept into the </li></ul>
    6. 6. Rishabh Enterprises <ul><li>Current System: </li></ul><ul><ul><li>Further Processing </li></ul></ul><ul><ul><li>A Motor Request to Shah Electricals </li></ul></ul><ul><ul><li>Blade Request to Sharp Edge </li></ul></ul><ul><ul><li>Industrial Visit Request to the Industrial Visit Division. </li></ul></ul><ul><li>spare parts are supplied by purchase division. </li></ul><ul><li>Purchase division </li></ul><ul><ul><li>old or new motors </li></ul></ul><ul><ul><li>Blade manufacturing materials </li></ul></ul><ul><li>No record is maintained for the purchases </li></ul>
    7. 7. Rishabh Enterprises <ul><li>Current System: </li></ul><ul><li>Respective employee tells about the work done </li></ul><ul><li>the details about the spare parts used </li></ul><ul><li>Final Estimate/ Challan/ Bill is issued at the time of delivery. </li></ul><ul><li>Bill is generated manually by the respective employee </li></ul><ul><li>particular is delivered to the respective Customer </li></ul><ul><li>Manual maintenance of record of Bills issued </li></ul>
    8. 8. Rishabh Enterprises <ul><li>Limitations of Current System: </li></ul><ul><li>No proper maintenance of information in any parts of the organization. </li></ul><ul><li>Manual searching of the previous records stored of each motor. </li></ul><ul><li>Problem in recovering the debts on customers as no record is maintained of each customer. </li></ul><ul><li>Hard to maintain all records for long duration. </li></ul><ul><li>No data of the motors they have in their storehouse, </li></ul><ul><li>Exact dimensions of blades are to be kept while remanufacturing the blades, which are not there. </li></ul>
    9. 9. Rishabh Enterprises <ul><li>Limitations of Current System: </li></ul><ul><li>No records of previous industrial visits </li></ul><ul><li>No record is maintained for the Suppliers who supply the spare parts to the organization. </li></ul><ul><li>No distinct maintenance of cash book, challan book and bill book for the Customer Transaction. </li></ul><ul><li>None of the worker timings are recorded. </li></ul><ul><li>Realizing the actual financial loss or profit in every fiscal year is very much difficult. </li></ul>
    10. 10. Rishabh Enterprises <ul><li>Proposed System: </li></ul><ul><li>Record of all the Customers </li></ul><ul><li>Payments of Bills by Customers </li></ul><ul><li>Generation of </li></ul><ul><ul><ul><li>Estimate </li></ul></ul></ul><ul><ul><ul><li>Challan </li></ul></ul></ul><ul><ul><ul><li>Bill </li></ul></ul></ul><ul><li>Record of Login and Logout time of each Employee on daily basis </li></ul>
    11. 11. Rishabh Enterprises <ul><li>Proposed System: </li></ul><ul><li>Records of all kinds of Motors </li></ul><ul><li>Searching of any specific configuration of Motor </li></ul><ul><li>Dimensions of all the Blades ordered by particular Customers </li></ul><ul><li>Records of all the Industrial Visits made </li></ul><ul><li>Records of the whole Stock available and to be purchased </li></ul><ul><li>Record of all the Suppliers, payments to be made to them </li></ul>
    12. 12. Aim of “SANKALAN” “ To design and develop a fully automated system for the Rishabh Enterprises and thereby learning the concepts of Database Management System.”
    13. 13. Objectives of “SANKALAN” <ul><li>To learn the concepts of Database Management System. </li></ul><ul><li>To perform a thorough analysis of working of the whole organization. </li></ul><ul><li>To study the problem with the current scenario through fact finding techniques. </li></ul><ul><li>To suggest all possible solutions through IT and select the most appropriate solution as project. </li></ul>
    14. 14. Objectives of “SANKALAN” <ul><li>To follow SDLC to develop the system. </li></ul><ul><li>To develop an appropriate Enterprise Data Model (EDM) for the system and identify its entities. </li></ul><ul><li>To develop conceptual, logical and physical model for the system. </li></ul><ul><li>To develop Graphical User Interface (GUI) as per convenience of the user. </li></ul><ul><li>To implement the physical model, being tested as per the standards. </li></ul><ul><li>To document our efforts and analysis in a proper comprehensible manner. </li></ul>
    15. 15. Goals of “SANKALAN” <ul><li>To make a responsive, easy to operate, fast and efficient retrieval of information as per the user requirements. </li></ul><ul><li>To provide all material like reports, reminders etc. that might serve as a helping hand to the users. </li></ul><ul><li>To provide adequate information about the customer transaction etc. </li></ul><ul><li>To provide ease in the maintenance of records of various configurations of motors arriving to the organization. </li></ul>
    16. 16. Goals of “SANKALAN” <ul><li>To make a database that is consistent, reliable and secure. </li></ul><ul><li>To provide correct, complete, ongoing information. </li></ul><ul><li>To develop a well-organized information storage system. </li></ul><ul><li>To make good documentation so as to facilitate possible future enhancements. </li></ul>
    17. 17. Current Scenario Main dealing of the Rishabh Enterprises is with CUSTOMER . A CUSTOMER comes to the Organization at the Reception DIVISION and submits his REQUEST . A REQUEST may be to Purchase or Repair a MOTOR ; it may be for the repair of electrical panel or a starter. A REQUEST may be to grind or manufacture an industrial BLADE , or it may be for an INDUSTRIAL VISIT . A JOB CARD sheet is prepared manually for the REQUEST . Requested particular is sent to the respective DIVISION for the further processing.
    18. 18. Current Scenario A MOTOR REQUEST is sent to Shah Electricals, BLADE REQUEST to Sharp Edge and an INDUSTRIAL VISIT REQUEST is sent to the Industrial Visit Division. While processing the REQUEST if a MOTOR needs some Spare Parts then these are supplied by purchase DIVISION . Purchase DIVISION is also responsible for purchasing of old or new MOTOR and BLADE manufacturing materials. On the basis of the job done final Estimate/ Challan/ BILL is issued at the time of delivery.
    19. 19. Entity Identification <ul><ul><li>Customer </li></ul></ul><ul><ul><li>Division </li></ul></ul><ul><ul><li>Employee </li></ul></ul><ul><ul><li>Bill </li></ul></ul><ul><ul><li>Request </li></ul></ul><ul><ul><li>Motor </li></ul></ul><ul><ul><li>Blade </li></ul></ul><ul><ul><li>Industrial Visit </li></ul></ul><ul><ul><li>Stock </li></ul></ul><ul><ul><li>Supplier </li></ul></ul>
    20. 20. Enterprise Data Model Receives Supplied by Requires Requires Forwarded to Forwarded to Prepared by Pays through Worked by Comes to CUSTOMER DIVISION EMPLOYEE BILL REQUEST MOTOR BLADE STOCK SUPPLIER
    21. 21. Transaction Requirements <ul><li>System must provide password to the user for their identification. </li></ul><ul><li>User must be able to input and search details about Customers, their Request. </li></ul><ul><li>User must be able to input and retrieve details about Motor, Blade and any kind of Industrial Visit. </li></ul><ul><li>User must be able to view availability of any spare part and to enter new purchases. </li></ul><ul><li>System must provide timely Reminders to the user about due amount to the Customers & Suppliers and about expiry date of particulars etc. </li></ul>
    22. 22. Input/Output Requirements <ul><li>Input Requirements: </li></ul><ul><li>Details of the employees working in the organization </li></ul><ul><li>Details of the customers making request to the organization </li></ul><ul><li>Details of the motor, coming for repairing </li></ul><ul><li>Dimensions of the blades, coming for grinding need to be recorded </li></ul><ul><li>Details of the job need to be done during a visit to an industry. </li></ul><ul><li>Records of the old purchased motors need to be maintained. </li></ul>
    23. 23. Input/Output Requirements <ul><li>Output Requirements: </li></ul><ul><li>Details of the job done on a particular motor came for the repair. </li></ul><ul><li>Details of the job done on a particular blade came for the grinding purposes. </li></ul><ul><li>Details of the job done by the employee on an industrial visit. </li></ul><ul><li>Record of all the industries visited by the organization. </li></ul><ul><li>Determine schedule for industrial visits. </li></ul><ul><li>Generation of challan. </li></ul><ul><li>Generation of bills. </li></ul>
    24. 24. System Development Methodology System development Life Cycle (SDLC): Project Identification and selection. Project Initiation & planning . Analysis Logical Design Physical Design Implementation Maintenance Conceptual Data Modeling Logical Database Design Physical Database design Database Implementation Database Maintenance Enterprise Modeling
    25. 25. Time Scheduling Gantt chart - Demonstration - Testing & Implementation * Physical Design & Coding * Logical Design * Conceptual Design * * Analysis * Initiation & Planning * Project Identification & Selection 15-20 Nov 1-15 Nov 1-30 Oct 1-30 Sep 20-30 Aug 21July- 20Aug 14-21 July 6-14 July Stage of Development
    26. 26. Project Identification & Selection <ul><li>Centre for Advance Technology (CAT) </li></ul><ul><li>Rajshahi Palace </li></ul><ul><li>Amaltas Hotel </li></ul><ul><li>Life Care (C& F) </li></ul><ul><li>Rajpal Honda </li></ul><ul><li>Mehta Motors </li></ul><ul><li>Harsh Honda </li></ul><ul><li>Sony World </li></ul><ul><li>Veermani Enterprises </li></ul>
    27. 27. Initiation & Planning <ul><li>“ Sankalan” </li></ul><ul><li>Gathering Things Together… </li></ul><ul><li>An opportunity to gather data scattered all over the </li></ul><ul><li>“ Rishabh Enterprises”. </li></ul><ul><li>No any computerized system at all. </li></ul><ul><li>All the work being done on papers only. </li></ul><ul><li>A great opportunity to analyze a Huge Database and to Design a Database Management System . </li></ul>
    28. 28. Analysis Phase <ul><li>Scheduled a series of meetings with Client </li></ul><ul><ul><li>3 meetings with Dheeraj Bhai Shah (The Owner). </li></ul></ul><ul><ul><li>6 meetings with Rishabh Shah & various Employees of the Rishabh Enterprises. </li></ul></ul><ul><ul><li>Lots of phone calls to authorized persons. </li></ul></ul>
    29. 29. Analysis Phase <ul><li>Questions asked: </li></ul><ul><ul><li>Complete organizational Structure </li></ul></ul><ul><ul><li>Goals </li></ul></ul><ul><ul><li>Existing systems </li></ul></ul><ul><ul><li>Problem Areas </li></ul></ul><ul><ul><li>What he wants ? </li></ul></ul><ul><ul><li>Detailed working Each & Every Section </li></ul></ul><ul><ul><li>Business Rules </li></ul></ul><ul><ul><li>policies </li></ul></ul>
    30. 30. Design Phase <ul><li>Three steps in Design Phase </li></ul><ul><ul><li>Conceptual Design </li></ul></ul><ul><ul><li>Enhanced ER Diagram </li></ul></ul><ul><ul><li>Logical Design </li></ul></ul><ul><ul><li>Relational Data Model </li></ul></ul><ul><ul><li>Physical Design </li></ul></ul><ul><ul><li>Data types & Storage Specification </li></ul></ul>
    31. 31. Design Phase <ul><li>Conceptual Design </li></ul><ul><li>Entity Identification </li></ul><ul><li>Listing attributes for all the Entities </li></ul><ul><li>Relationship Identification </li></ul><ul><li>Identification of Weak and Associative Entities </li></ul><ul><li>Removal of many to many Relationships </li></ul><ul><li>Super type/Subtype classification </li></ul><ul><li>Final EER Schema </li></ul>
    32. 32. Design Phase Conceptual Design <ul><li>List of all the Entities Identified from Analyzed Scenario: </li></ul><ul><ul><li>CUSTOMER CUST_TRANS </li></ul></ul><ul><ul><li>BILL DIVISION </li></ul></ul><ul><ul><li>REQUEST INDUSTRY_REQ </li></ul></ul><ul><ul><li>MTR_JOB_CARD BLD_JOB_CARD </li></ul></ul><ul><ul><li>MOTOR BLADE </li></ul></ul><ul><ul><li>DEMAND STOCK </li></ul></ul><ul><ul><li>SUPPLIER_STOCK SUPPLIER </li></ul></ul><ul><ul><li>SUPPLIER_PAYMENT SUPPLIER_BILL </li></ul></ul><ul><ul><li>WORK_DETAIL EMPLOYEE </li></ul></ul><ul><ul><li>WAGED_EMP SALARIED_EMP </li></ul></ul><ul><ul><li>PHONE_DIR TAX_RATE </li></ul></ul><ul><ul><li>USER_ACCOUNT </li></ul></ul>
    33. 33. Design Phase Conceptual Design <ul><li>Relationship Identification between Entities: </li></ul><ul><li>MOTOR poses DEMAND . </li></ul><ul><li>“ While processing MOTOR, it may pose some DEMAND for some parts to be purchased. DEMAND records different Part_Id for each Request_Id, also it keeps track of Quantity Used and Unit Price of the part being used.” </li></ul><ul><li>A MOTOR may pose DEMAND for zero, one or many part. </li></ul><ul><li>A DEMAND for part can be posed by one and only one MOTOR. </li></ul>MOTOR DEMAND poses
    34. 34. Design Phase Conceptual Design Relationship Identification between Entities: MOTOR poses DEMAND <ul><li>A MOTOR may pose DEMAND for one or many part. </li></ul><ul><li>A DEMAND for part can be posed by one and only one MOTOR. </li></ul>MOTOR DEMAND poses D1. D2. D3. D4. D5. M1. M2. M3.
    35. 35. Design Phase Conceptual Design Identification of Weak & Associative Entities: Two Weak Entities identified DEMAND SUPPLIER_STOCK Cured by assigning identifier attribute from owner Entities. One Associative Entity (initially ) WORK_DETAIL
    36. 36. Design Phase Conceptual Design Super type/Subtype Classification: Two Super type/Subtype Relations Identified 1.) REQUEST is divided into three subtypes MTR_JOB_CARD BLD_JOB_CARD INDUSTRY_REQUEST “ M” “I” “B” REQUEST d MTR_JOB_CARD INDUSTRY_REQ BLD_JOB_CARD
    37. 37. Design Phase Conceptual Design Super type/Subtype Classification: Two Super type/Subtype Relations Identified 2.) EMPLOYEE is divided into two Subtypes: WAGED_EMP SALARIED_EMP “ W” “S” EMPLOYEE WAGED_EMP SALARIED_EMP d
    38. 38. Final EER Schema S_BILL MOTOR BILL DIVISION REQUEST CUST_TRANS SUPPLIER_PAYMENT STOCK SUPPLIER_STOCK DEMAND MTR_JOB_CARD BLD_JOB_CARD INDUSTRY_REQ WORK_DETAIL BLADE WAGED_EMP CUSTOMER EMPLOYEE SUPPLIER SALARIED_EMP c payed_by relates_to comes_to generates requires receives maintains sent_to sent_to poses poses maintained_by supplied_by receives c fulfilled_by performed_by
    39. 39. Design Phase <ul><li>Logical Design: </li></ul><ul><li>Conversion from Entity to Relation </li></ul><ul><li>Entity Relation </li></ul><ul><li>Attributes Columns </li></ul><ul><li>Entity Instances Rows </li></ul><ul><li>Relationship Association Foreign Key-Primary Key Normalization </li></ul><ul><li>1 st Normal Form </li></ul><ul><li>2 nd Normal Form </li></ul><ul><li>3 rd Normal Form </li></ul>
    40. 40. Design Phase Logical Design Conversion from Entity to Relation: CUSTOMER Cust_Id Cust_Name Industry_Name Cust_Add Cust_City Cust_State Bal_Due CUSTOMER Cust_Id Cust_Name Industry_Name Cust_Add Cust_State Cust_City Bal_Due
    41. 41. Design Phase Logical Design Primary key-Foreign key association between Relations: CUSTOMER Cust_Id Cust_Name Industry_Name Cust_Add Cust_City Cust_State Bal_Due CUST_TRANS Trans_Id Trans_Amt Cust_Id Bill_Id Trans_Date BILL Bill_Id Bill_Date Estemate_Status Delevery_Date Challan_Date Request_Id Parts_Charges Labour_charges Tax Total_Amt INDUSTRY_REQ Request_Id Cust_Id Visitors_Name Request_Desc Desc_Of_Job_Done REQUEST Request_Id Cust_Id Particulars Entry_Date Exp_Serv_Date
    42. 42. Design Phase Logical Design Normalization: First Normal Form: No multivalued Attribute detected in any of the Relations Second Normal Form: No partial Functional Dependency detected Third Normal Form: No Transitive Dependency at all CUSTOMER Cust_Id Cust_Name Industry_Name Cust_Add Cust_City Cust_State Bal_Due
    43. 43. Design Phase <ul><li>Physical Design: </li></ul><ul><li>Designing Fields: </li></ul><ul><ul><ul><ul><li>Type of data (storage type) used to represent values of concerned field. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Data integrity controls built into the database. </li></ul></ul></ul></ul><ul><li>Choosing Data Types: </li></ul><ul><ul><ul><ul><ul><li>Minimize storage space </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Represent all possible values </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Improve data integrity </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Support all data manipulations </li></ul></ul></ul></ul></ul>
    44. 44. Design Phase Physical Design Relation: CUSTOMER Primary Key: Cust_Id Not Null Number Balance Due to Customer Bal_Due Null String Customer State Cust_State Not Null String Customer City Cust_City Not Null String Customer Address Cust_Add Null String Name of the concerned Industry Industry_Name Not Null String Customer Name Cust_Name Not Null String Customer Id Cust_Id VALUES DOMAIN DESCRIPTION ATTRIBUTE
    45. 45. Design Phase Physical Design Choosing Database (Back-End Tool): SQL Server 2000: Internet Integration Scalability and Availability Enterprise-Level Database Features Ease of installation, deployment, and use Data warehousing
    46. 46. Design Phase Physical Design <ul><li>Choosing Front-End Tool: </li></ul><ul><li>Visual Basic Dot Net (VB.Net): </li></ul><ul><ul><ul><ul><li>Simple </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Object-Oriented </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Multithreaded </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Robust </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Distributed </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Dynamic: </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Event-Driven </li></ul></ul></ul></ul>
    47. 47. Implementation, Coding & Testing CUSTOMER Table: CREATE TABLE [dbo].[Customer] ( [Cust_ID] [varchar] (10) NOT NULL , [Cust_Name] [varchar] (40) NULL , [Industry_Name] [varchar] (40) NULL , [Cust_Address] [varchar] (80) NOT NULL , [Cust_City] [varchar] (15) NOT NULL , [Cust_Pin] [varchar] (6) NULL , [Cust_State] [varchar] (15) NOT NULL , [Bal_Due] [decimal](18, 0) NOT NULL ) ; INSERT INTO Supplier(Supplier_Id, Supplier_Name, Supplier_Add, Supplier_City, Supplier_State) VALUES (@Supplier_Id, @Supplier_Name, @Supplier_Add, @Supplier_City, @Supplier_State);
    48. 48. Conclusion Problem Areas: Searching of UoD System Analysis Selection of DBMS Representation of various Business Functions into Codes Designing of Test Cases Scarcity of Human Resources
    49. 49. Conclusion <ul><li>Lesson Learned: </li></ul><ul><li>Experience to convenience the unknown client (Searching Phase) </li></ul><ul><li>Live project experience </li></ul><ul><li>Team working </li></ul><ul><li>Time management </li></ul><ul><li>Improve technical knowledge </li></ul><ul><li>How to follow Database approach. </li></ul><ul><li>Backup and recovery management. </li></ul><ul><li>Write what you do, do what you write. </li></ul><ul><li>Approach of problem solving. </li></ul>
    50. 50. The Working Log Project Leader: Kushagra Goyal System Analysis: Sushil Kumar Singh Kushagra Goyal Database Design: Kiran Prasad Sushil Kumar Singh Programmer: Kiran Prasad Kushagra Goyal Testing & Documentation: The Complete Team
    51. 51. Thank You!!!

    ×