1. 1. Software Engineering I PROJECT PROJECT TITLE MEDICAL STORE MANAGEMENT SYSTEM SUBMITTED TO MAM SARFARAZ SUBMITTEDBY MUHAMMAD HANIF (13-Arid-1289) BILAL IQBAL (13-Arid-1254) KASHIFSULTAN (13-Arid- 1296
2. 2. Introduction Project Name: - Medical Store Management This project is used mainly for medical stores to maintain the details of medical store such as stock and account. This medical shop management software is so designed as to ease the work load of medical shop professionals. The main feature includes inventory and stock control, accounting, client management
3. 3. Scope & Objectives As this is generic software it can be used by a wide variety of outlets (Retailers and Wholesalers) to automate the process of manually maintaining the records related to the subject of maintaining the stock and cash flows. This project is basically updating the manual chemist inventory System To Automated inventory system, So that organization can manage their record in efficient and organized form.
4. 4. This software helps you to track all the products of medical shop moreover its a medical shop accounting software. Flexible and adaptive software suited to medical shops or stores or pharmacies of any size. Project Characteristics: Customer management Transition management Sales management Reporting
5. 5. The main goal of the application is to maintain the records of purchase, Sales and stock details with cash transaction maintenance. Medical Store Management software is very needy for Medical Store . This software help them maintain day to day transactions in computer.
6. 6. Drawbacks Problem To maintian record of daily trananctions They have Work load so they Also haveproblem in dealing with their customer At the End of the they t also have problem in calculating their profit ,sales,Purchases etc,
7. 7. They also have problem to find a specific product Problem I also occur while creating invoices&reports.
8. 8. Project deliveries&budget The Total Cost of the project is 45,000. The project Is Deliver within the time of 3 months as per contract negotiations.
9. 9. Model Implementation Water Fall Model Is Used To develop this project
10. 10. Reason For choosing WaterFall Model This is Small Project and Requirements Are Well understood. This model is simple and easy to understand and use. Waterfall model is simple to implement and also the amount of resources required for it are minimal. It is easy to manage due to the rigidity of the model each phase has specific deliverables and a review process.
11. 11. In this model, output is generated after each stage (as seen before), therefore it has high visibility. The client and project manager gets a feel that there is considerable progress. Here it is important to note that in any project psychological factors also play an important role. In this model phases are processed and completed one at a time. Phases do not overlap. This Project Is Conversion From Manual To Automatic
12. 12. Software Requirement Specification (SRS) Purpose This document outlines the software requirements for the Chemist management system for the D-Watson Chemist. It describes the functional and non-functional requirements, modeling requirements, diagrams and user profiles of the proposed system. The Chemist Management System enables D-watson staff to maintain computerized Record Of Customer Who visits, their Employees & product.Its also perform quick search for their products,Manages Counter sales And Keep record of salesman. This SRS provides detailed information on the internal and external view of the system as well as interfaces required by Chemist management System.
13. 13. Document Convention The following are the list of conventions and synonyms used in the Document &project Administrator : A log in Id representing the user with user administration privileges To Software. Cilient: Intend user of Software Sql (Structured Query language ).used To perform CRUD operations on Database.
14. 14. Oracle A server used To store data in organized form Java Coding language. DFD: Show the Data Flow Between Entities. User interface: Something through which user communicate with system.
15. 15. Project Features There Will be two user Accessing System System Manager : Who will act As Administrator Other Staff: Who Will accessing the System User The Features for manager are Add ,delete update any product Manage store i-e(put price,make salaries,Calculate Revenue )
16. 16. The features for the Other Staff Are Cashier can only search the product and make the bill Can see the list of product Other staff can mark their attendance And check their Status. User can only see the product price and available products
17. 17. User Classes and Characteristics User Of project include customers and staff Customer can be Member or visitor who are accessing this system. Staff Which act as administrator and controlling overall system User Should IT literate And know to use computer Cashier Should Know Data entry & Typing Manager should have knowledge of Internet & Browsing
18. 18. Operating environment This project will be operating in windows environment.Also compatible with internet explorer. The only requirement For using this project is having machine. Design and implemention constraints This project is developed using java.on the back hand for database we are using Sql server. The product is Accomplished With the login facility for user. User Documentation This project will include a user manual. The user manual include Complete overview of the producst,Configuration of the Tool used (Sql Sever or other), technical details, backup procedures and Contact Information which will include email address and Ph# .
19. 19. Hardware Requirements Processor : Intel Pentium 4 RAM : 512 MB RAM Monitor : 1 5Colour Monitor Processor Speed : 1.7 GHZ Hard disk : 1.44 MB FDD CD Drive : 52- X CD ROM Keyboard : Mercury 110 Keys Mouse : Logitech Mouse
20. 20. System Features Description & priorirty Proposed Database is intended to store, retrieve, update, andmanipulate information related to Chemist which include Order Processing & taking Staff information Customer Bill Detail Product Details Calculation of Revenue,Staff Salaries Searching of product Remainder About Products expiry,Shaortage Generate Reports
21. 21. Functional Requirements The software must allow input of products data from Administrator& secured access at , and from the data streaming real-time monitoring equipment The project must request username and password for access to data, only after authentication will allow access to the system. The project must require high levels of error correction and input validation. The project must allow browsing by the Director&Staff of Cms To Acces And update information products & Customers ,vendors. The project must identify the Products & Customer by a unique numeric identifier derived from a function performed on the Customers birth date or product Id;
22. 22. The software to be developed must operate without interruption twenty-four hours a day. The software to be developed shall display the correct time of day in compliance with Standards (ISO etc). The software must retrieve, update, and store data from multiple input . The software must allow full and complete record search queries by Users The product must allow Customer to view their own Concern record allowing changes only to address, phone number, and insurer after initial input. .
23. 23. Non Functional Requirements The software interface must follow design conventions which allow for familiar location of menus,etc. Input errors will be returned in red with appropriate message box. More than three attempts at login and failure will produce a red flag to system administrator. Response Time Should be minimum. No of daily system downs Should not more than 10. System should Automatically Update After Every Transcation
24. 24. Performance Requirements The Physician software should be able to support at least three simultaneous users. 95% of the transactions shall be processed in less than one second. Data should be secured and backed up every quarter hour. Power supply should have a back up and a disaster recovery plan. System should be operable 24 hours a day and accessible in real-time. Encryption will Enable Security
25. 25. Safety Requirements The Database may get crashed or damaged due to some viruses or operating system requirements.Therefore Its is mandatory to have backup for your data.Ups/inverter facility should be there in case of power failure. Security Requirements System will use secure Database Staff can just see the products & mark their attendance .They Cannot edit or,modify anything except their personal information. Proper user Authentication Will be provided. There should be separate account for Admin &user. So that no one else can access the database except Admin.
26. 26. User requirements The User Of system are Staff ,Managers and customer of the store. The members share assumed to have basic knowledge of computer & internet browsing While administrator of system should have more knowledge so he/she can resolve small problems and perform informations. The user manual ,installation guide and other related material should be sufficient to educate the user how to use and maintain the system.
27. 27. Erd
28. 28. Data Flow Diagram (Dfd)O Level/Context Level
29. 29. Data Flow Diagram (Dfd)1 Level
30. 30. WORK BREAK DOWN STRUCTURE
31. 31. Activity Table Activity Description Duration Pre E.S L.S E.F L.F Slack A Requirement Gathering 3 Weeks None 0 9 3 12 4 B Hadware Selection 2 weeks None 0 9 2 11 4 C Designing 4 weeks A 3 7 7 11 0 D Coding` 4 weeks C,A 7 7 7 11 0 E Debugging/testing 4 weeks D,B 11 11 11 15 4 F Writing User Manuals 8 weeks E 22 15 19 23 4 G User training 1 week F, 12 23 16 24 4
32. 32. PDM
33. 33. Purchase
34. 34. Sale
35. 35. Payment
36. 36. Profit and loss analysis
37. 37. Any Questions ?