only for online mobile phone shopping

1. PROJECT
By
Amarnath Patwa
Arjun Tiwari
Amrit Raj
Amit Kumar

2.  SCOPE
 Objectives
 Processing Environment
 System Implementation
 UML Diagrams
 Future Enhancements
 Conclusion
 Thank you

3. SCOPE
 The project could be implemented in an average sized organization.
 An average company will not be very keen on spending loads of money on ledgers.
Whereas these project will greatly reduce the costs which is using common and cheap
office items like database and desktop application.
 And also there is no requirement to store books or accounts.
 The data is directly stored in the database in the hard disk of the PC.

4. OBJECTIVE OF PROJECT
 The main objective of the project is to help the ongoing user help to attain an easy
way to navigate the customer’s details and solve the Customers problems.
 It is basically a very instant processing System by which customer can get the mobile
in the right condition.
 It’s basically build in the platform of .NET windows application which makes the
application quite flexible and easy to be operated.
 The manager of the Mobile store also finds it sufficient enough to view the details of
the sales, servicing and well organized way to employ the staff that are included in the
mobile store itself.

5. PROCESSING ENVIRONMENT
Processing environment includes hardware and software requirements.
Software Requirement
 Operating system: - Windows7,8
 Front-end Tool: - Visual studio 2012
 Back-end Tool: - Sql server 2008
Hardware Requirement
 Operating system: Windows 7 and above.
 Minimum 5 GB HDD space
 3.00 Megahertz Intel Pentium IV Processor
 1 GB RAM

6. SYSTEM IMPLEMENTATION
 Computer will be used to maintain the records of the Mobile, Customer, sales and
purchase, in the computer database.
 A Computerized report in a particular format can be generated.
 Availability of Mobile can be checked.
 Finding employee, customer, Mobile details is easier.
 The details of the sales and purchasing of Mobiles will be recorded in the system.

7.  UML DIAGRAMS
 Use case Diagram
 ER- Diagram
 Activity Diagram
 Sequence Diagram
 DFD
 Class Diagram

8. USE CASE DIAGRAM

9. ER DIAGRAM

10. ACTIVITY DIAGRAM
Activity Diagram for system

11. ACTIVITY DIAGRAM CONTD….
Activity Diagram for Mobile Phone
Activity Diagram for Customer

12. ACTIVITY DIAGRAM CONTD….
Activity Diagram for sales report

13. SEQUENCE DIAGRAM

14. DFD - LEVEL 1(TOP LEVEL DFD)

15. SECOND LEVEL DFD
Second level DFD Item master Second level DFD Sale

16. Second level DFD Purchase
Second level DFD Employee Detail

17. Second level DFD Report

18. CLASS DIAGRAM

19. MENU TREE

20. FUTURE ENHANCEMENTS
 The system could be modified suitably to work on a large network. This involves,
among other, resolving used conflicts, protecting database integrity and ensuring
consistency of data if it is distributed across multiple locations.
 Maintain attendance details of employee
 Maintain Mobile details.

21. CONCLUSION
 An attempt is made in all its earnest towards the successful completion of the project.
This system was verified with valid as well as with invalid data.
 This system is user friendly since it has been developed in visual studio 8 a
successful GUI environment. Since the connection can be extended to any database.
The control will be more powerful.
 Connecting it to any type of database extends the development control. Any
suggestions for future development of the system are welcome
 Upgrading the system if may can be done without affecting the proper functioning of
system.

22. Thank you……