Cyberthink Ecommerce Shopping Cart

Transcription

1 Cyberthink Ecommerce Shopping Cart Created by: Paurva Buch, Prachee Patel, Rachit Purohit 1

2 Table of contents Project Summary Systems Planning Identify problems and define proposed solutions (System Request) Feasibility Analysis Cost-benefit analysis, etc. Project Plan Size Estimation Work Breakdown Structure\ Work Plan (Gantt Chart/Pert Diagram) Risk Assessment Systems Analysis Requirements Gathering Documentation (interview, questionnaire, documents, etc.) Use cases and use-case diagrams Data Flow diagram Context-level diagram 0-level diagram, etc. Next-level diagrams Data dictionary Data flow with data structure Data storage with data structure Data input and data structure Data output and data structure Data element description Process description Systems Design Database design (E-R diagram) Program design Document and design input screens Document and design output reports/screen Systems Implementation System architecture Database development (tables and queries) User interface (screen capture of forms and reports) Created by: Paurva Buch, Prachee Patel, Rachit Purohit 2

3 Project Summary Reusable ecommerce module contains all the modules those are used by most of every ecommerce site. So according to customer requirements organization use those modules and prepare system and deliver it more efficiently. It is developed with the purpose of saving time and manpower, instead of developing ecommerce website every time from the scratch. Specific modules of specific system are difficult to use in any other system, but the modules that are created by this system are purely general which can be used in any application. To create new site pages for the system dynamically and display these pages on the front side as they are created. There is no need to create content pages as static now. The contents of the page are dynamically added from the database. The system is designed with the purpose in mind to give full fledge facility to the users for online shopping. is an essential part of any business site; system provides manager which helps admin to send to customers. Our designed E-shopping cart system can support following features: System can fit in any shopping cart related requirements with no or just little modifications. Modules like user management, product catalogue, news letter can be used in any projects with no or little modifications Our designed E-shopping cart system can not support following features: It is not fully fledge customized system in terms of module selection. i.e. Any non technical guy can not separate out modules as system does not have admin driven customization option like which are the modules to be deployed in the final solution. etc... Some designing related changes are required when the system is used as plug and play to any other e commerce project. For example when we fit our shopping cart to other E-commerce system then we need to do some designing related changes to our system. Created by: Paurva Buch, Prachee Patel, Rachit Purohit 3

4 1 System Planning 1.1 System Request Project Sponsor: Ravinder S. Thind, President and CEO Corporate headquarters: Bridge water, NJ Project Team: Paurva Buch, Prachee Patel, Rachit Purohit Business profile: Provider of IT Solutions and Staffing Outsourcing and BPO Services It also has 2 other headquarters at England and India. Business need: Present: We make modules as we get project in hand. Problem: We have to make same type of modules each time as we get a new project (e.g. Registration and Login, Search etc.) Solution: We will make such reusable ecommerce modules that contains common functionality and so that it can be reused with no or little change. It is a plug and play system which is having standard modules that can be used in any of ecommerce website. Business Value System is developed as an internet application and is portable. Consistent data is available through out the system. Report can viewed by date, month, year, sales and inventory. Saving of time. Reduction of manpower. Using already built modules( i.e. reusable modules) will save a lot of money. Created by: Paurva Buch, Prachee Patel, Rachit Purohit 4

5 System Request Reusable ecommerce contains all the modules that are used by most of the ecommerce sites. Build a shopping cart application for ecommerce. Instead of developing modules of the system from the scratch, our modules can be used with minimal changes. Modules created in this application are purely general and are flexible with different systems System is designed with the purpose in mind to give full fledge facility to the users for online shopping. Transactions are safe and secure. Confirms order processing by . Issues/constraints: Project should be completed by Jan The system should be user friendly, as this would prevent the need to hire tech savvy workers, thereby keeping labor costs down Created by: Paurva Buch, Prachee Patel, Rachit Purohit 5

6 1.2 FEASIBILITY ANALYSIS Economic Feasibility The software resource requirement of the proposed system is.net Framework 2.0 and Sql Server 2005 that are already owned by the organization and do not require additional investment. The hardware requirement of the system is at least a PC for an administrator to handle the site from admin panel. And front users need just a PC with internet connection which they can have from their work place or from home Technical Feasibility The system will be hosted on the server of the company. And company has till now developed many sites and hosted them on their server. So, it will not cause any problem. The database server used will support tera data so the storage of data in the system is not a problem. System will be portable in nature so will be accessible from all the PC environments. The 3 trainees allotted to handle the project are sufficient to complete the project within the specified time Operational Feasibility The system will be implemented on the internet and accessible to all the PCs in the internet network so its operational requirements will be fulfilled. The login process would validate and limit the access of the user according to his role type in the system so the operations would be appropriately structured. Created by: Paurva Buch, Prachee Patel, Rachit Purohit 6

7 1.3 Project Planning Project Size Estimation The shopping cart system uses the function point approach in its size determination. This is a three step process which takes into account system size estimation, required effort and required time estimation. 1) System Size estimation: The size is estimated by function point approach. First the complexity of the system is calculated by unadjusted function points of system components. Complexity Description Total number low Complexity Index low Medium Complexity index medium high Complexity index high Total Inputs Outputs Queries Program Interfaces Total unadjusted feature points 156 Created by: Paurva Buch, Prachee Patel, Rachit Purohit 7

8 Complexity scale(0-3) Data communications 2 Heavy use configurations 0 Transaction Rate 3 End user efficiency 0 Complex processing 2 Installation Ease 0 Multiple sites 2 Performance 0 Distributed Functions 3 Online data entry 1 Online Update 2 Reusability 0 Operational ease 0 Extensibility 1 Total processing complexity 16 The processing complexity calculation allows us to calculate the total unadjusted function points. Adjusted project complexity(apc) =0.65 (0.01 X 16) =0.81 Total adjusted function points APC X TUFPP=0.81X 156 = The total unadjusted function points that will be needed to determine the number of lines of code that will be needed to develop system of Microsoft Visual basic TAFP Lines of code per function Total point lines of code will be needed to develop the system. Created by: Paurva Buch, Prachee Patel, Rachit Purohit 8

9 1.3.4 Risk Assessment Risk Identification: 1. Personnel Shortfalls 2. Unrealistic Schedule 3. Developing wrong software functions 4. Developing wrong user interface Risk Analysis: 1. Personnel Shortfalls: They may cause the developmental delays and would cause a change in the working strategy due to developmental dependencies of the functional modules. 2. Unrealistic Schedule: It may cause the developers to give unrealistic commitments to the users and so lose their faith when the deliverables are not produced as per schedule. 3. Developing wrong Software functions: It can be caused due to wrong requirement analysis or wrong programming method used to automate the requirements. It may cause the system to fail and not be implemented at all. 4. Developing wrong User Interface: It may be caused due to lack of user acceptance and user involvement during development Risk Control Strategies: 1. Personnel Shortfalls: Ensuring the presence of at least one of the project member through the project duration and completing the targeted work for the day according to priority handled it. Planning is done in advance for the targeted work to be carried out in absence of one of the project member. Created by: Paurva Buch, Prachee Patel, Rachit Purohit 9

10 2. Unrealistic Schedule: Plan is done to develop the system at least one month before the training period completion in order to handle the schedule delay. 3. Developing wrong Software functions/developing wrong User Interface: A constant user involvement at all stages of project deliverables was done in order to check for the correct system flow as well as for user acceptance testing. Created by: Paurva Buch, Prachee Patel, Rachit Purohit 10

11 1.4 Work Breakdown Structure Task Number Task Name Duration (days) Dependency 1 Planning Phase System Request Feasibility Analysis Economic Feasibility Technical Feasibility Organizational Feasibility Project Plan Project Size Work Breakdown structure Work Plan Staffing Plan Standards Risk Assessment 2 2 Analysis Phase Requirements Gathering Interviews Questionnaires Joint Application Design Data Flow Data Dictionary 3 3 Design Phase Database Design E-R Diagram Document and Design User Interface Document & Design Input Screens Document & Design Output Screens Program Design Program Test Design Implementation Phase System Architecture Database Development Program Code User Interface Program Testing 10 Created by: Paurva Buch, Prachee Patel, Rachit Purohit 11

12 1.5 Gantt Chart ID Task Name Duration Jun 2008 Jul 2008 Aug /6 15/6 22/6 29/6 6/7 13/7 20/7 27/7 3/8 10/8 1 System Planning Phase 18d 2 System Request 5d 3 Feasibility Analysis 5d 4 Economic Feasibility 2d 5 Technical Feasibility 2d 6 Organizational Feasibility 2d 7 Project Plan 8d 8 Project Size 3d 9 Work Breakdown Structure 2d 10 Work Plan 1d 11 Staffing Plan 2d 12 Standards 1d 13 Risk Assesment 2d 14 System Analysis Phase 6d 15 Requirement Gathering 5d 16 Interviews 1d 17 Questionnaires 1d 18 Joint Application Design 1d 19 Data Flow 3d 20 Data Dictionary 3d 21 System Design Phase 6d 22 Database Design 3d Created by: Paurva Buch, Prachee Patel, Rachit Purohit 12

13 2 System Analysis 2.1 Study of Current System The current system is basically designed for specific domain. So it contains only specific modules related to it system as of which it is use for the specific purpose only. 2.2 Problems and Weaknesses of Current System In today s world the current system is specifically designed for the specific domain. So while using one or more modules of current system ( like jewellery, computers etc) and integrating it with new system becomes difficult, however it is possible but it is time consuming, expensive and not accurate up to the mark. 2.3 Requirements of New System User Requirements For the users who are busy, physically not fit and who want to shop at any time anywhere, shopping is nearly impossible, while our system is developed in such a way by keeping such persons in a mind. Shopping is done online where users have to go to the site and start shopping; there is a service of dispatching commodities directly to their home. No need for staying in queue. Billing is done instantly. Our system provides a great flexibility to the users and save their quality time in day to day life System Requirements In this, system is developed with the motive of developing an efficient system consuming less time. It is a plug and play system which can be added to any ecommerce websites, if module which is not required or required by the user can also be removed or added to the system. It is being developed with the motive of user s facilities and ease. Created by: Paurva Buch, Prachee Patel, Rachit Purohit 13

14 2.4 Context Diagram Created by: Paurva Buch, Prachee Patel, Rachit Purohit 14

15 2.5 Level 0 diagram Level 1 DFD Created by: Paurva Buch, Prachee Patel, Rachit Purohit 15

16 2.6 Level 1 Process-2 (Customer Login) Created by: Paurva Buch, Prachee Patel, Rachit Purohit 16

17 2.6.1 Level 1 Process-5 (Shopping Cart) Created by: Paurva Buch, Prachee Patel, Rachit Purohit 17

18 2.7 Level 2 Process-5.1 (Process Shopping Cart) Created by: Paurva Buch, Prachee Patel, Rachit Purohit 18

19 2.8 DATA DICTIONARY Table Name: Customer Sr. No Field Name DataType Size Required Key 1 Cust_ID Varchar 10 Yes Primary Key 2 Cust_FirstName Char 30 Yes 3 Cust_LastName Char 30 Yes 4 Cust_Address Varchar 100 Yes 5 Cust_Phone Number 10 Yes 6 Cust_City Char 15 Yes 7 Cust_State Char 10 Yes 8 Cust_Country Char 10 Yes 9 Cust_Zipcode Number 10 Yes 10 Session_Id Varchar 50 Yes Primary Key Table Name: Category Info Sr. No Field Name DataType Size Required Key 1 Cat_Id Varchar 10 Yes Primary Key 2 Cat_Title Char 20 Yes 3 Cat_Desc Char 50 Yes 4 Cat_PageName Char 20 Yes 5 Prod_Id Varchar 10 Yes 6 Cust_ID Varchar 10 Yes Foreign Key Created by: Paurva Buch, Prachee Patel, Rachit Purohit 19

20 Table Name: Product Info Sr. No Field Name DataType Size Required Key 1 Prod_Id Varchar 10 Yes Primary Key 2 Prod_Name Char 20 Yes 3 Prod_Price Number 5,2 Yes 4 Prod_Desc Char 50 Yes 5 Prod_Color Char 10 Yes 6 Prod_Quantity Number 4 Yes 7 Cat_Id Varchar 10 Yes Foreign key 8 Order_Id Varchar 10 Yes Foreign key Table Name: Sales and Payment Info Sr. No Field Name DataType Size Required Key 1 Order_Id Varchar 10 Yes Primary key 2 Cust_ID Varchar 10 Yes 3 Order_Date Date/Time Yes 4 Order_Total Number 5,2 Yes 5 Order_Payment_Status Char 10 Yes 6 Order_Payment_Method Char 10 Yes 7 Purchase_Id Varchar 10 Yes Foreign Key Created by: Paurva Buch, Prachee Patel, Rachit Purohit 20

21 Table Name: Purchase Info Sr. No Field Name DataType Size Required Key 1 Purchase_Id Varchar 10 Yes Primary key 2 Purchase_Order_Total Number 5,2 Yes 3 Order_Payment_Status Char 10 Yes 4 Order_Payment_Method Char 10 Yes 5 Order_Payment_Confirmation Char 10 Yes 6 Session_Id Varchar 10 Yes Foreign Key Created by: Paurva Buch, Prachee Patel, Rachit Purohit 21

22 3 Systems Design 3.1 E-R diagram Created by: Paurva Buch, Prachee Patel, Rachit Purohit 22

23 3.2 Program Design Created by: Paurva Buch, Prachee Patel, Rachit Purohit 23

24 3.3 Design Input Screen Created by: Paurva Buch, Prachee Patel, Rachit Purohit 24

25 Created by: Paurva Buch, Prachee Patel, Rachit Purohit 25

26 3.4 Design output screen Created by: Paurva Buch, Prachee Patel, Rachit Purohit 26

27 Created by: Paurva Buch, Prachee Patel, Rachit Purohit 27

28 4 System Implementation 4.1 System Architecture Internet CyberThink VSNL Leased Line 8 PORT SWITCH PRINTER MAIL SERVER ITI SERVER WEB SERVER/FIREWALL 16 PORT SWITCH Workstation Workstation Workstation Created by: Paurva Buch, Prachee Patel, Rachit Purohit 28

29 4.2 Database Physical Design Customer Database (Cust_ID, Cust_FirstName, Cust_LastName, Cust_Address, Cust_Phone, Cust_City, Cust_State, Cust_Country, Cust_Zipcode, Session_Id) Category Info Database ( Cat_Id, Cat_Title, Cat_Desc, Cat_PageName, Prod_Id, Cust_ID) Product Info Database ( Prod_Id, Prod_Name, Prod_Price, Prod_Desc, Prod_Color, Prod_Quantity, Cat_Id, Order_Id) Sales and Payment Info Database ( Order_Id, Cust_ID, Order_Date, Order_Total, Order_Payment_Status, Order_Payment_Method, Purchase_Id) Purchase Info Database ( Purchase_Id, Purchase_Order_Total, Order_Payment_Status, Order_Payment_Method, Order_Payment_Confirmation, Session_Id) Created by: Paurva Buch, Prachee Patel, Rachit Purohit 29

30 4.3 User Interface Created by: Paurva Buch, Prachee Patel, Rachit Purohit 30

31 Created by: Paurva Buch, Prachee Patel, Rachit Purohit 31

32 Created by: Paurva Buch, Prachee Patel, Rachit Purohit 32