Guided By: Ms. Sweta Jethva Project Manager

1. Guided By: Ms. Sweta Jethva Project Manager Mr. Subhas Talati Prepared By: Pratik Patel Exam No: 6625 Parul Institute of Engineering & Technology, Vadodara

2. Company Profile • S.K INFOSOFT is Software Services Company with a team of well qualified creative designers and developers of experience in design and development. • Services Offered: • Open Source Development • Web Development & Web Design • B2B Application Development • E-Commerce Development & Multimedia • I-phone Application • Industrial Training

3. Project Profile

4. What Is CRM • A CRM is a collection of people, processes, software, and internet capabilities that helps an enterprise to manage customer relationship effectively and systematically. • The goal of CRM is to understand and anticipate the needs of current and potential customer to increase customer retention and loyalty while optimizing the way product and services are sold.

5. Drawback Of Existing System • The existing system in the organization is not completely computerized. The system is not working smoothly; therefore the organization has decided to replace it with a completely computerized one. The problems, which the existing system faces are: • Low Functionality • Erroneous Input And Output • Portability • Security • Data Redundancy • Processing Speed • Manual Errors • Complexity In Work:

6. Scope Of Project • In project management, the term scope has two distinct uses: • Project Scope • Product Scope. • To provide user friendly application to maximum user. • Reduces the manual entries of raw data collected. • Satisfies all the levels of the customer by after sales services

7. Project Objective • To replace a manual book keeping system in a company. • To manage customer data effectively. • Provide services to customer and maintain relation. • To perform analysis on customer data. • To provide security as only an authorized user can interact with the system. • To Provide product information to the customer. • Provide a fast mechanism for correcting service deficiencies. • To provide mechanism to deal with customer complaints effectively. • To provide facility of submitting feedback of the customer. • Automatic management of data.

8. Continue…. • Provides efficient solution with quick speed. • Customer is been treated as the main boss of our application and is being dedicated with the best and high quality services. • Admin side work is also been simplified. It is also been as an objective of our application. • Timely updating is achieved in our application to remain up to date about all market issues, customers, technology, tools, software resources etc.

9. Proposed System • Scope of the Project defines the boundary within which our system is working. Scope of this project is to implement an application according to the requirement of particular client. • Delayed and Distored Information. • Lack of proper communication. • Lack of proper data collecting and processing. • Lack of proper interaction. • Lack of better Customer services. • Lack of solution of customer Query. • Absence of factual, reliable and accurate reports.

10. Feasibility Study There are three aspects in the feasibility study:- Technical Feasibility: The feasibility deals with the technical details of the system such as, • Whether the tools for the development of the system are available or not? • Are developers aware of these technologies?

11. Continue…. Economical Feasibility: Economic feasibility addresses to the following issues: • Economical feasibility deals with the fact that will the system be cost effective? • Does the organization have enough budgets to develop the system? Operational Feasibility: • Operational feasibility measures how well the system works does or performs. How helpful it for the end-user who use the system to extract or store information through the system.

12. Requirement Specification Functional Requirement: • The users must be able to run the software according to the privileges, which are given to them. • Software must execute all queries according to the database design. • Admin must be able to Add, Update and Delete information on requirement. • Admin can manage and verify whole System,

13. Continue…. Non- Functional Requirements: • Software must support the existing hardware setup. • It must also support operating system used currently. • Deleting, Updating or adding any data should be applied with 100% accuracy.

15. Admin Module • Login verification and management • Manage project • Manage database • Manage employee,customer,supplier • Send Email and Message • Check Sales & Purchase details • Forget Password • Change password • Logout

16. Employee Module • Registration • Login • Set purchase & Sales details • Set and edit stock details • Place an order to Supplier • Deliver product to Customer • Make payment from customer • Register and Handle Complain of customer • Get Feedback from customer • Logout

17. Process Hierarchy Chart • A variety of process charts has been designed to meet the needs of a particular level or stage of analysis; they can be used at a detailed level.

24. Uml Diagrams • Unified Modeling Language (UML) is a standardized general-purpose modeling language in the field of software engineering. The standard is managed, and was created by, the Object Management Group. Uml Diagrams contains following diagrams: • Activity Diagrams • Sequence Diagram • Use case Diagram • Class Diagram

25. Activity Diagram • Displays a special state diagram where most of the states are action states and most of the transitions are triggered by completion of the actions in the source states. This diagram focuses on flows driven by internal processing.

28. Sequence Diagram • Sequence diagrams describe interactions among classes in terms of an exchange of messages over time. • It displays the time sequence of the objects participating in the interaction.

31. Use Case Diagram • Use case Diagram displays the relationship among actors and use cases.Each use case should provide some observable and valuable result to the actors or other stakeholders of the system

34. Class Diagram • UML class diagrams define static structure diagram that describes the structure of a system by showing the system‘s classes, their attributes and interfaces, operations (or) methods and the relationships between the classes. Relationship In Class Diagram: • Association: • Aggregation: • Composition • Generalization • Dependency

36. Structure Chart Diagram • Structure Chart describes functions and sub-functions of each part of system. It shows relationships between common and unique modules of a computer program. • This Chart is tree-like with root module and branches. Structure Charts are based on the DFD and Data Dictionary.

38. Data Dictionary • A Data dictionary is an automated tool for collecting and organizing the detailed information about system components. Data dictionaries maintain facilities to document data elements, records, programs, systems, files, users, and other system components.

39. CountryMaster State

40. PageMaster

41. DepartmentMaster DesignationMaster

42. GroupMaster

43. ItemMaster

44. Employee

46. Customer

47. Supplier

48. Sales

49. SalesReturn

50. Purchase