Introduction to software engerinng_PPT[1].pptx

ise presention of srs

1. BOOKSTORE MANAGEMENT SYSTEM GROUP 3

2. PEOPLE INVOLED GROUP- 3 005 - AFRAH FAWAD 017 - HARRAM HABIB 042 - NOOR UL IRFAN 047 - SYEDA DUA E ZAHRA

3. TABLE OF CONTENT 01. 02. INTRODUCTION PRODUCT SCOPE OF PROJECT AUDIENCE OF PROJECT 03. FUNCTIONAL REQUIREMENTS 04. NON-FUNCTIONAL REQUIREMENTS PRODUCT PERSPECTIVE AND FUNCTIONALITIES BLOCK DIAGRAM ASSUMPTIONS AND DEPENDENCIES BEHAVIOUR REQUIREMENT SEQUENCE DIAGRAM

4. Introduction

5. 1. INTRODUCTION 1.1.1 Modules 1.1.2 Security 1.1.3 Reporting 1.1.4 Scalability 1.1.5 Integration 1.1.6 User Experience 1.1 Scope of project

6. 1.1.1 MODULES 01 02 03 USER REGISTERATION BOOK ISSUEANCE BOOK RETURN

7. 1.2 AUDIENCE OF PROJECT DOCUMENT WRITER 02 03 01 04 DESIGNERS TESTERS DEVELOPERS

8. 1.3 References IEEE Recommended Practice for Software Requirements Specifications https://ieeexplore.ieee.org/document/720574 Designing Software Requirement Specification Document https://spada.uns.ac.id/pluginfile.php/819931/mod_resource/content/1/W04%20Software%20Requirements%20 Specification

9. 1. User-Centric Design 2. OVERALL DESCRIPTION •Easy Registration •Seamless Book Browsing •Effortless Transactions 3. Security and Trust • Secure Transactions •Confidential user Information • Trustworthy System 2. Convenience and Efficiency • RFID Card Usage • Fast Transaction Processing • User Account . 2.1 PRODUCT PERSPECTIVE 4. Innovation and Technology Integration • RFID Card Technology •Real-time Book Databases •Secure Payment Processing 6. Scalability and Adaptability • Adaptable to Growth •Future-Proof Technology •Expandable Book Inventory 5. Financial Transaction Transparency: • Clear Fare Details •Transparent Charges •Integration with Bank Accounts

10. 2.3 BLOCK DIAGRAM USER REGISTRATION ISSUE RFID CARD VALIDATE INPUT (EMAIL, CONTACT NO, BANK DETAILS) PRINT BOOKRACK DETAILS CONFIRM RETURN BOOK SELECTION (CATEGORY) & BOOK FARE DISPLAY ISSUED BOOKS RETURN BOOK BOOK ISSUANCE DATABASE

11. 2.3 BLOCK DIAGRAM ATM Machine Database RFID CARD RFID Reader Data Link Graphical user Interface (GUI)

12. 2.2 PRODUCT FUNCTIONALITY GENERATE PRINTOUTS DISPLAY DATA SELECT AUTHENTICATION UPDATE DATA PF-1 PF-2 PF-3 PF-4 PF-5

13. 2.4 FUNCTIONAL REQUIREMENTS AUTHENTICATE USER GENERATE RFID CARD VALIDATE USER INPUT REGISTER USER DISPLAY BOOK CATEGORIES FR1 FR2 FR3 FR4 FR5 SELECT BOOK FR6

14. 2.4 FUNCTIONAL REQUIREMENTS DISPLAY ISSUED BOOKS AUTHENTICATE USER FOR RETURN PRINT BOOKRACK DETAILS DEDUCT FARE PROCESS BOOK RETURN FR7 FR8 FR9 FR10 FR11 CONFIRM RETURN FR12

15. 2.5 ASSUMPTIONS AND DEPENDENCIES Assumptions: Dependencies: • STABLE AND RELIABLE INTERNET CONNECTION. • USERS WILL INPUT ACCURATE PERSONAL INFORMATION. • WELL-MAINTAINED AND UPDATED BOOK DATABASE. • DEPENDENCY ON EXTERNAL SERVICES FOR EMAIL VALIDATION. • SECURE AND RELIABLE PAYMENT GATEWAY

16. 3.BEHAVIOUR REQUIREMENTS 3.1 USECASE DIAGRAM

17. 1.REGISTER USER 3.BEHAVIOUR REQUIREMENTS

18. 2.LOG IN 3.BEHAVIOUR REQUIREMENTS

19. 3.BEHAVIOUR REQUIREMENTS 3.ISSUANCE OF RFID CARD

20. 3. BEHAVIOUR REQUIREMENTS 4.SELECT BOOK

21. 3. BEHAVIOUR REQUIREMENTS 5.Book Return

22. 3.BEHAVIOUR REQUIREMENTS 3.2 SEQUENCE DIAGRAM REGISTRATION

23. 3.BEHAVIOUR REQUIREMENTS 3.2 SEQUENCE DIAGRAM ISSUE BOOK

24. 3.BEHAVIOUR REQUIREMENTS 3.2 SEQUENCE DIAGRAM RETURN BOOK

25. 4. NON-FUNCTIONAL REQUIREMENTS 4.1 PERFORMANCE REQUIREMENTS 01 02 03 RESPONSE TIME THROUGHPUT SCALABILITY

26. 4. NON-FUNCTIONAL REQUIREMENTS 4.2 SAFETY AND SECURITY REQUIREMENTS ACCESS CONTROL 02 03 01 04 SECURE COMMUNICATION DATA ENCRYPTION INTRUSION DETECTION AND PREVENTION

27. 06 05 07 PHYSICAL SECURITY MEASURES LOGGING AND AUDITING AUTHENTICATION MECHANISMS 4. NON-FUNCTIONAL REQUIREMENTS 4.2 SAFETY AND SECURITY REQUIREMENTS

28. 4. NON-FUNCTIONAL REQUIREMENTS 4.3 SOFTWARE QUALITY ATTRIBUTES AVAILABILITY Uptime Target Backup and Recovery Monitoring and Alerting USABILITY Intuitive Interface User Assistance and Help PORTABILITY CROSS-PLATFORM COMPATIBILITY REUSABILITY MODULAR DESIGN ROBUSTNESS GRACEFUL DEGRADATION ERROR HANDLING CORRECTNESS DATA INTEGRITY 1 1 2 4 1 5 6 1 3

29. THANKYOU FOR PATIENTLY LISTENING!