Mba Project Report
Table of Contents
1. INTRODUCTION 3 1.1 Purpose of this Document 3 1.2 Scope of the Development Project 3
2. PROJECT PLAN 5 2. 1 Project Organization 5 2.2 Management Structure 5 2.3 Work Breakdown Structure 7
3. GENERAL DESCRIPTION 8 3.1 User Characteristics 8 3.2 Product Perspective 8 3.3 Software & Hardware Infrastructure 9 3.3 System Use Cases 10 3.4 Overview of Functional Requirements 11 3.5 General Constraints, Assumptions, Dependencies, Guidelines 12 3.6 User View of Product Use 12
4. SPECIFIC REQUIREMENTS 13 4.1 External Interface Requirements 13 4.2 Detailed Description of Functional Requirements 13 4.3 Performance Requirements 21 4.4 Quality Attributes 21
5. SYSTEM ARCHITECTURE 22 5.1 Overview of Modules and Components 22 5.2 Modular Architecture of the System 30
6. DATA-FLOW DIAGRAMS 35 6.1 DFD-Level 0 35 6.2 DFD-Level 1 36 6.3 DFD-Level 2 38
7. DATA REQUIREMENTS 41 7.1 Entity Relationship Diagram 41 7.2 Class Diagram of the system 42 7.3 State-Transition diagram 43
8. DATABASE DESIGN AND DATA DICTIONARY 44 8.1 List of Database Tables 44 8.2 Database Tables 45 8.3 Definitions, Acronyms, and Abbreviations 54
9. SYSTEM TEST CASES 55
1O. INTEGRATION TEST CASES 80 10.1. Functional Tests: 81 10.2 Load Tests: 85 10.3. Stress Tests: 86
11. SCREEN DESIGN 87 11.1 Web Page Layout 87 11.2 Web Page Organization 88 11.3 Individual Web Pages 89
12. ERROR AND MESSAGE SUMMARY 99 12.1 Error Collection 99 12.2 Message Collection 101
13. CODING STANDARDS 103
14. USER MANUAL 105
15. REFERENCES 110
1. INTRODUCTION
The General store needs a web-based system to keep track of all orders placed by customers and payment received. It needs to permit customers to establish a list of regularly purchased items in a reusable shopping cart. For each order, system needs to store the total amount that was
1. INTRODUCTION 3 1.1 Purpose of this Document 3 1.2 Scope of the Development Project 3
2. PROJECT PLAN 5 2. 1 Project Organization 5 2.2 Management Structure 5 2.3 Work Breakdown Structure 7
3. GENERAL DESCRIPTION 8 3.1 User Characteristics 8 3.2 Product Perspective 8 3.3 Software & Hardware Infrastructure 9 3.3 System Use Cases 10 3.4 Overview of Functional Requirements 11 3.5 General Constraints, Assumptions, Dependencies, Guidelines 12 3.6 User View of Product Use 12
4. SPECIFIC REQUIREMENTS 13 4.1 External Interface Requirements 13 4.2 Detailed Description of Functional Requirements 13 4.3 Performance Requirements 21 4.4 Quality Attributes 21
5. SYSTEM ARCHITECTURE 22 5.1 Overview of Modules and Components 22 5.2 Modular Architecture of the System 30
6. DATA-FLOW DIAGRAMS 35 6.1 DFD-Level 0 35 6.2 DFD-Level 1 36 6.3 DFD-Level 2 38
7. DATA REQUIREMENTS 41 7.1 Entity Relationship Diagram 41 7.2 Class Diagram of the system 42 7.3 State-Transition diagram 43
8. DATABASE DESIGN AND DATA DICTIONARY 44 8.1 List of Database Tables 44 8.2 Database Tables 45 8.3 Definitions, Acronyms, and Abbreviations 54
9. SYSTEM TEST CASES 55
1O. INTEGRATION TEST CASES 80 10.1. Functional Tests: 81 10.2 Load Tests: 85 10.3. Stress Tests: 86
11. SCREEN DESIGN 87 11.1 Web Page Layout 87 11.2 Web Page Organization 88 11.3 Individual Web Pages 89
12. ERROR AND MESSAGE SUMMARY 99 12.1 Error Collection 99 12.2 Message Collection 101
13. CODING STANDARDS 103
14. USER MANUAL 105
15. REFERENCES 110
1. INTRODUCTION
The General store needs a web-based system to keep track of all orders placed by customers and payment received. It needs to permit customers to establish a list of regularly purchased items in a reusable shopping cart. For each order, system needs to store the total amount that was