I need a complete Software Requirements Specification for a Bike Rental Management System that my college can accept without revisions. The document must span 60–70 well-formatted pages and follow the typical academic project-report layout: cover page, abstract, table of contents, numbered chapters, references—everything a supervisor expects. Core scope The system itself should be described with these key features in mind: user registration and secure login, real-time bike availability with booking, and integrated payment processing that issues receipts. All requirements, functional and non-functional, must revolve around those three pillars. Visual modelling Please embed the following diagrams, each created with a professional tool and properly captioned: • Context-level and level-1 Data Flow Diagrams (DFD) • A complete Use Case Diagram covering every actor and scenario • A detailed Class Diagram that matches the object model in the narrative Screenshots I want screenshots that illustrate the user interface examples—mock-ups or working screens are fine—as long as they match the described flows and blend naturally into the report. Formatting rules • Times New Roman, 12 pt, 1.5-line spacing throughout • Consistent heading hierarchy (H1, H2, etc.) • Automatic table of contents and list of figures/tables • Page numbers and captioned figures on every diagram or screenshot Deliverables (attach as separate files) 1. The SRS in editable Word (.docx) and export as PDF 2. Source files for all diagrams (e.g., .drawio, .vsdx, or .uml) 3. Any raw images used for screenshots Acceptance criteria The submission must hit the 60–70-page window, compile without formatting errors, and be ready to print or upload as is. If my instructor flags a formatting or completeness issue, I’ll request one quick turnaround fix. Timeline I need the finished package in my inbox within the next 24 hours, so please take the job only if you can comfortably meet that deadline.