DEPARTMENT OF COMPUTER SCIENCE

GOVT POSTGRADUATE ISLAMIA COLLEGE, FAISALABAD

FYP GENERAL REPORTE FORMAT

CHAPTER 1 (3 to 8 pages)
INTRODUCTION
1.1 Project Scope
1.2 Objectives
1.3 Problem Statement
1.4 Significance of the Study:
1.5 Document Overview:
1.6 Limitation of Project:
CHAPTER 2 (13 to 16 pages)
METHODOLOGY
2.1 System Methodology
2.2 Data Flow Diagrams
2.2.1 Context Level Diagram
2.3 Level ‘0’ Diagram
2.4 Unified Modeling Language (UML)
2.4.1 Use Case Diagram
Detailed Use Case Diagram
2.5 Class Diagram
2.6 System Sequence Diagram
2.7 ER Diagram
2.8 Database Design
2.8.1 Use Case Diagram
2.9 Hardware/Software Interface
2.9.1 Hardware Interface
2.9.2 Software Interface
2.10 Tools and Languages
2.10.1 Language
2.10.1.1 HTML
2.10.1.2 CSS
2.10.1.3 Bootstrap
2.10.1.4 PHP & MySQL
2.10.2 Tools
2.10.2.1 XAMPP
2.10.2.2 Adobe Dreamweaver CC
CHAPTER 3 (15 to 22 pages)
TESTING
3.1 Test Cases
3.1.1 Black Box Testing
3.1.2 White Box Testing
3.2 Admin Dashboard Test Cases
3.2.1 Admin login test case
3.2.2 Admin dashboard test case
3.2.3 Accept/Delete requests test case
3.2.4 Update profile test case
3.2.5 Frontend settings test case
3.2.6 Time Management test case
3.2.7 Discount Management test case
3.2.8 Report Management test case
3.3 Customer Dashboard test case
3.3.1 Customer login test case
3.3.2 Add to Cart test case
3.3.3 Payment test case
3.3.4 Feedback test case

CHAPTER 4 (5 to 8 pages)
RESULTS AND DISCUSSIONS
4.1 List of stake holders
4.2 Client and Customer Contact
4.3 Mandated Constraints
4.3.1 Solution design constraints
4.3.2 Implementation environment of the current system
4.3.3 Partner or collaborative application
4.3.4 Anticipated workplace environment
4.3.5 How long do the developers have for the project?
4.4 Relevant Facts and Assumptions
4.4.1 Look and Feel Requirements
4.4.2 The interface
4.4.3 The style of the product
4.5 Usability and Humanity Requirements
4.5.1 Ease of Use
4.5.2 Personalization and Internationalization Requirements
4.5.3 Ease of Learning
4.5.4 Understandability and Politeness requirements.
4.5.5 Accessibility Requirements
4.6 Performance Requirements
4.6.1 Longevity Requirements
4.7 Operational Requirements
4.7.1 Expected physical Environment
4.7.2 Expected Technological Environment
4.7.3 User Interfaces
4.8 Maintainability and Support Requirement
4.8.1 Maintenance Requirements
4.8.2 Adaptability Requirements
4.9 Security Requirement
4.9.1 Access Requirements
4.10 Legal Requirements
4.11 Open Issues
4.12 Off-the-Shell solutions
4.12.1 Is there a ready-made product that could be bought?
4.12.2 Can ready-made components could be used for this application?
4.12.3 is there something that we could copy?
4.13 New problems
4.13.1 What new problems could the new product cause in the current environment?
4.13.2Will the new development affects any of the installed system?
4.13.3Will any of our existing users be adversely affected by the new development?
4.13.4 Will the new Product create other Problems?
4.13.5 User Documentation and Training
4.14 Ideas for Solutions
SUMMARY (1 page)
REFERENCES (At the end)

List of Figures
INCREMENTAL MODEL
CONTEXT LEVEL DIAGRAM
LEVEL ‘0’ DIAGRAM
DETAILED USE CASE DIAGRAM
CLASS DIAGRAM
SYSTEM SEQUENCE DIAGRAM
ER DIAGRAM
DATABASE DESIGN
USE CASE DIAGRAM
BLACK BOX TESTING
WHITE BOX TESTING
ADMIN LOGIN TEST CASE
ADMIN DASHBOARD TEST CASE
ACCEPT/DELETE REQUESTS TEST CASE
UPDATE PROFILE TEST CASE
FRONTEND SETTINGS TEST CASE
REPORT MANAGEMENT TEST CASE
CUSTOMER LOGIN TEST CASE
ADD TO CART TEST CASE
PAYMENT TEST CASE

List of Tables
ADMIN LOGIN TEST CASE
ADMIN DASHBOARD TEST CASE
ACCEPT/DELETE REQUESTS TEST CASE
UPDATE PROFILE TEST CASE
FRONTEND SETTINGS TEST CASE
TIME MANAGEMENT TEST CASE
DISCOUNT MANAGEMENT TEST CASE
REPORT MANAGEMENT TEST CASE
CUSTOMER LOGIN TEST CASE
ADD TO CART TEST CASE
PAYMENT TEST CASE
FEEDBACK TEST CASE
USER OF THE APPLICATIO
ACCESS REQUIREMENT