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

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.”

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. 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.

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

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. 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

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. 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. 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. 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

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. 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. 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

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. 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

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. 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

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. Thank You!!!