System Requirements Document for real-estate-developer

1. Introduction

This document specifies the system requirements for real-estate-developer, the new website for Group Integrated (alternate name: Integrated Space Limited), a residential real estate developer operating in Mumbai, India, with a 37-year record of delivering residential projects in Ghatkopar West.

The product intent is to rebuild the developer's public web presence as a PHP-implemented website whose content and structure follow the existing site at https://groupintegrated.com/, which is the authoritative reference for content and structure. The site presents Group Integrated's residential developments — arya (1 & 2 BHK Flats), ahana (3 & 3.5 BHK Flats), and pranay (1 RK) — together with the company's mission, its measured track record, and its two stated project USPs, and it gives prospective homebuyers a direct path to enquire about a specific property. It also gives Group Integrated's own staff a protected workspace to maintain the property and project content that visitors see.

The audience is twofold:

• Prospective homebuyers / property seekers in Mumbai, particularly the Ghatkopar West area, evaluating 1 BHK, 2 BHK, 3 BHK, 3.5 BHK and 1 RK residential units, who are financially careful and emotionally invested in a once-in-a-lifetime purchase and who need verifiable facts — Maha-Rera registration numbers, possession status, unit types, location — before they make contact.
• Group Integrated's site administrator / content editor, the person inside the developer organisation who keeps the public property and project content current and accurate.

2. System Overview

The system is a server-rendered PHP website with a public, anonymously browsable front end and a small protected administrative area. Public visitors can read the developer's story, review the project portfolio, open an individual project's details, and submit an enquiry about a selected property. The site administrator signs in to a protected area to review, add and update the property and project content that the public site displays.

Current delivery covers:

• A public Landing page carrying the project hero, the "We Are Integrated Spaces" mission statement, the four company statistics, the two project USPs, and the enquiry call to action.
• A public Properties page listing Group Integrated's developments.
• A public Property Details page for an individual project.
• A public Inquiry page for submitting an enquiry about a selected property or project.
• A Login page for returning verification of the site administrator.
• A protected Content overview and a protected Content Editor workspace for maintaining property and project content.

Actors are the two accepted human personas — the Prospective Homebuyer / Property Seeker and the Group Integrated Site Administrator / Content Editor — plus the PHP application itself, which owns persistence of property/project content and of submitted enquiries, and the outbound telephone contact channel published as 98198 99600.

Narrow exclusions: this document does not add online payment, booking, unit inventory allocation, customer account self-service, document vaults, or any capability not present in the authoritative requirement thread or the reference content. The published telephone number is a contact channel, not a system capability.

2a. Product Interpretation and Delivery Boundary

The public site is anonymous-first: a prospective homebuyer can read the mission, the statistics, the USPs, the project portfolio and an individual project's details, and can submit an enquiry, without creating an account. No identity is required to browse or to enquire.

Identity exists only where continuity is genuinely required: the site administrator must privately own and resume durable property and project content across sessions, so the administrative area is protected and the administrator verifies returning access through Login. Because the administrator is provisioned by the developer organisation rather than self-registering, first-use access is established by invitation or provisioning, not by an open sign-up flow. The Login page is itself anonymously reachable — it is the anonymous entry boundary through which protected state is reached — while Content and Content Editor remain unavailable until identity is established.

The protected area is restricted to the site administrator role. No differentiated permission tiers, role hierarchies, or per-user visibility rules are established by the source, and none are introduced here.

Everything in this document is current delivery. No future-horizon requirements were accepted in the authoritative thread.

2b. Source Content Inventory

The following facts are preserved from the authoritative content source https://groupintegrated.com/ and must appear in the new site's content.

Brand

• Brand name: Group Integrated
• Alternate name: Integrated Space Limited

Projects

Call to action

• "Jodi Option Available Enquire Now! 98198 99600"

Company statistics

• Years of Excellence: 37
• Happy Families: 2 Thousand+
• Delivered: 1 Million Sq. Ft.
• In Progress: 2 Million Sq. Ft.

Project USPs

• ZERO – WASTAGE PLANNING: Special focus on construction design that ensures optimal use of all available spaces in our projects.
• LOW MAINTENANCE PROJECTS: Our project are ensured with lower maintenance cost by the way of logical and necessary amenities.

Mission statement

"With every project, we aspire to create spaces that are functionally and aesthetically sound. We take pride, that, our projects are holistically planned for light and ventilation, maximum utilization of every square foot and structures that are in harmony with the landscape. Every Integrated project is built to be a worthy 'life space' for its residents, for years to come."

Structure reference — homepage sections, in order

1. Image slider featuring projects (arya, ahana, pranay)
2. "We Are Integrated Spaces" (mission statement)
3. Years of Excellence / Happy Families / Delivered / In Progress (company stats)
4. Project USP (Zero-Wastage Planning, Low Maintenance Projects)
5. Call to Action: Jodi Option Enquire Now

Domain context

• Audience: prospective homebuyers in Mumbai, particularly the Ghatkopar West area.
• Market focus: residential real estate development in Mumbai.
• Terminology: "flats" refers to BHK units (1, 2, 3, 3.5 BHK); "Ghatkopar West" is a specific Mumbai locality; "Maha-Rera" is a regulatory approval identifier.
• Brand positioning: established localised developer with decades of experience delivering life-oriented, efficient residential projects.
• Unique selling points: zero-wastage planning for optimal space usage; low-maintenance design; holistic planning for light, ventilation, and harmony with the landscape.

2c. Page Content and Component Coverage

Landing

• Information / state: Anonymous public entry. Presents the current flagship project hero (project name, unit type, location, possession status, Maha-Rera serial), the "We Are Integrated Spaces" mission statement, the four company statistics, the two project USPs, and the enquiry call to action with the published number 98198 99600.
• Primary actions: Switch the hero between projects (arya / ahana / pranay); open a project's details; open the enquiry path; place the published enquiry call.
• Supporting actions: Navigate to Properties; navigate to Login.
• Domain entities: Project (name, unit type, location, possession status, Maha-Rera number), Company Statistic (label, value), Project USP (ordinal, title, explanation), Mission Statement, Enquiry Call to Action.
• Component responsibilities:
  • Project hero — full-bleed graded facade image, oversized condensed project name, ruled spec line beneath it, possession gauge, amber enquiry block.
  • Project dial index — vertical ruled tabs for arya / ahana / pranay with the active tab amber-underlined; switching wipes the hero horizontally.
  • Mission panel — mission statement set as a measured text column beside an amber-ruled stat column.
  • Stat strip — four 1px-bordered cells (37 / 2 Thousand+ / 1 Million Sq. Ft. / 2 Million Sq. Ft.), each with an SVG needle gauge that sweeps once on scroll into view.
  • USP rows — numbered ruled rows "01 ZERO-WASTAGE PLANNING" and "02 LOW MAINTENANCE PROJECTS" with explanation text aligned right against a hairline.
  • Enquiry call-to-action block — amber fill, dark text, published number.
• States:
  • Loading: hero image and gauge render progressively; gauges show their final values immediately under reduced motion.
  • Empty: if a project has no recorded Maha-Rera number (pranay), the serial slot renders as an explicit "not recorded" state rather than a blank or fabricated value.
  • Success: hero, mission, stats, USPs and call to action all render with source content.
  • Error: if a hero image fails to load, the panel retains its dark ground, project name, spec line and call to action so the page remains usable.
  • Recovery: the project dial index remains operable so the visitor can switch to another project.

Login

• Information / state: Anonymous entry boundary for returning verification of the site administrator. States that access is provisioned by Group Integrated rather than self-registered.
• Primary actions: Submit credentials to establish an administrator session.
• Supporting actions: Return to the public site.
• Domain entities: Administrator identity, session.
• Component responsibilities:
  • Credential form — identifier and secret fields with inline validation messaging.
  • Provisioning notice — states that administrator access is established by invitation or provisioning from Group Integrated.
• States:
  • Loading: submit control shows an in-progress state; the form is not double-submitted.
  • Empty: pristine form with no error styling.
  • Success: session established and the administrator is taken to the protected Content overview.
  • Error: invalid credentials produce a single non-enumerating message that does not reveal whether the identifier exists.
  • Recovery: the form is cleared of the secret value and remains submittable; the visitor can return to the public site.

Properties

• Information / state: Anonymous public listing of Group Integrated's developments, presented as a ruled, table-like grid of project cards.
• Primary actions: Open an individual project's details.
• Supporting actions: Navigate to Landing; navigate to the enquiry path.
• Domain entities: Project (name, unit type, location, possession status, Maha-Rera number).
• Component responsibilities:
  • Project card — 1px border on a lighter surface, no shadow; carries project name, unit type, location, possession status chip and Maha-Rera serial slot.
  • Status chip — small rectangle with a 1px border and a single leading dot; teal for "OC Received, Ready Possession", amber for "Nearing Possession".
  • Ruled grid — hairline-divided layout consistent with the instrument grid.
• States:
  • Loading: card grid renders with placeholder rules in the instrument style.
  • Empty: if no projects are published, an explicit ruled empty state explains that no projects are currently listed.
  • Success: all published projects render with their status chips and serial slots.
  • Error: if the listing cannot be retrieved, a ruled error state offers a retry.
  • Recovery: retry re-requests the listing; navigation to Landing remains available.

Property Details

• Information / state: Anonymous focused readout for one project: project name, unit type, location, possession status, Maha-Rera serial, and the project's supporting content.
• Primary actions: Begin an enquiry about this project.
• Supporting actions: Return to Properties; switch to another project.
• Domain entities: Project (name, unit type, location, possession status, Maha-Rera number), Enquiry.
• Component responsibilities:
  • Spec readout — two-column instrument layout with aligned label/value rows and hairline dividers.
  • Sticky enquiry rail — persistent enquiry entry point carrying the project context.
  • Status chip and serial slot — as on Properties, with the Maha-Rera number treated as an instrument serial.
• States:
  • Loading: spec rows render in the ruled style while project data resolves.
  • Empty: a project without a recorded Maha-Rera number shows an explicit "not recorded" serial slot rather than a blank.
  • Success: full spec readout with the enquiry rail active.
  • Error: an unknown or unavailable project produces a ruled not-found state with a route back to Properties.
  • Recovery: the visitor can return to Properties and select another project.

Inquiry

• Information / state: Anonymous focused destination for submitting an enquiry about a selected property or project. Carries the selected project's context into the form.
• Primary actions: Submit the enquiry.
• Supporting actions: Change the selected project; place the published enquiry call to 98198 99600.
• Domain entities: Enquiry (selected project, enquirer contact details, message), Project.
• Component responsibilities:
  • Project context block — shows which project the enquiry concerns, with the project's status chip and Maha-Rera serial.
  • Enquiry form — contact fields and message field with inline validation.
  • Published contact block — the number 98198 99600 presented as a direct call action.
• States:
  • Loading: submit control shows an in-progress state; the form is not double-submitted.
  • Empty: pristine form with the project context pre-filled when the visitor arrived from a project.
  • Success: a confirmation state acknowledges receipt of the enquiry and states what happens next.
  • Error: field-level validation errors are shown inline; a submission failure preserves the entered values and offers a retry.
  • Recovery: the visitor can correct fields and resubmit, or use the published number instead.

Content

• Information / state: Protected overview for the site administrator, listing the property and project content currently maintained for the public site, in the same hairline ruled table language as the public site.
• Primary actions: Open a content item in the Content Editor; start adding a new item.
• Supporting actions: Sign out; return to the public site.
• Domain entities: Project (name, unit type, location, possession status, Maha-Rera number), content item status.
• Component responsibilities:
  • Ruled content table — one row per content item with name, unit type, location, possession status and Maha-Rera serial columns.
  • Row actions — open for editing.
  • Add action — starts a new content item.
• States:
  • Loading: table renders with ruled placeholder rows.
  • Empty: an explicit ruled empty state explains that no content items exist yet and offers the add action.
  • Success: all maintained content items are listed with their current values.
  • Error: if the content list cannot be retrieved, a ruled error state offers a retry.
  • Recovery: retry re-requests the list; the administrator can sign out and return later.

Content Editor

• Information / state: Protected focused workspace for adding and updating the property and project content shown on the public site, using the same hairline table language with inline edit rows.
• Primary actions: Create a new content item; update an existing content item; save changes.
• Supporting actions: Cancel an edit; return to the Content overview.
• Domain entities: Project (name, unit type, location, possession status, Maha-Rera number), content item.
• Component responsibilities:
  • Inline edit rows — editable fields for project name, unit type, location, possession status and Maha-Rera number, aligned to the ruled table columns.
  • Save and cancel controls — commit or discard the current edit.
  • Validation messaging — inline messages for missing or malformed values.
• States:
  • Loading: the editor renders its ruled structure while the item resolves.
  • Empty: a new-item editor opens with empty fields and the required-field rules visible.
  • Success: a saved item is confirmed and the updated values appear on the public site.
  • Error: validation failures are shown inline against the offending field; a save failure preserves the entered values and offers a retry.
  • Recovery: the administrator can correct the field and save again, or cancel and return to the Content overview.

3. Functional Requirements

FR-1 — PHP implementation of the Group Integrated website (explicit) As the Group Integrated organisation, I should have the website implemented in PHP, so that the developer's public presence runs on the requested technology.

• Trigger/input: the site is deployed and served.
• Observable result: all pages of the site are served by the PHP application.
• Access state: public pages anonymous; administrative pages protected.
• Failure/recovery: if the application cannot serve a page, the visitor receives an error state with a route back to a working page.
• Continuation: the visitor continues browsing, or the administrator continues managing content.

FR-2 — Site represents the developer and its property offerings (explicit) As a Prospective Homebuyer / Property Seeker, I should see that Group Integrated is a real estate developer and what residential properties it offers, so that I understand who I am dealing with and what is available.

• Trigger/input: the visitor opens the Landing page.
• Observable result: the page presents Group Integrated's identity as a residential developer, its mission, its track record and its project portfolio.
• Access state: anonymous.
• Failure/recovery: if a content element fails to load, the remaining panels still render so the developer's identity and offerings remain legible.
• Continuation: the visitor moves to Properties or to an enquiry.

FR-3 — Content and structure follow the existing site (explicit) As the Group Integrated organisation, I should have the new site's content and structure follow https://groupintegrated.com/, so that the rebuilt site preserves the established presentation of the developer's projects, statistics, USPs and mission.

• Trigger/input: content is authored and published.
• Observable result: the Landing page carries, in order, the project slider, the "We Are Integrated Spaces" mission statement, the four company statistics, the two project USPs, and the enquiry call to action.
• Access state: anonymous.
• Failure/recovery: if a section's content is unavailable, the section renders an explicit empty state rather than disappearing silently.
• Continuation: the visitor continues through the page and into the portfolio.

FR-4 — Project portfolio browsing (required_inference) As a Prospective Homebuyer / Property Seeker, I should browse Group Integrated's property listings and developments, so that I can compare what is available before deciding whether to enquire.

• Trigger/input: the visitor opens the Properties page.
• Observable result: each published project appears as a ruled card carrying its name, unit type, location, possession status and Maha-Rera serial slot.
• Access state: anonymous.
• Failure/recovery: if the listing cannot be retrieved, a ruled error state offers a retry.
• Continuation: the visitor opens an individual project's details.

FR-5 — Individual project details (required_inference) As a Prospective Homebuyer / Property Seeker, I should view an individual property's or project's details, so that I can evaluate that specific development before making contact.

• Trigger/input: the visitor selects a project from Properties or from the Landing hero.
• Observable result: the Property Details page shows the project's name, unit type, location, possession status and Maha-Rera serial in aligned label/value rows, with a persistent enquiry rail.
• Access state: anonymous.
• Failure/recovery: an unknown or unavailable project produces a ruled not-found state with a route back to Properties.
• Continuation: the visitor begins an enquiry about this project, or returns to Properties.

FR-6 — Enquiry submission about a selected property (required_inference) As a Prospective Homebuyer / Property Seeker, I should submit an inquiry about a selected property or project, so that Group Integrated can respond to my interest in that specific development.

• Trigger/input: the visitor opens the Inquiry page, with the selected project carried into the form, and submits their contact details and message.
• Observable result: the enquiry is recorded against the selected project and the visitor sees a confirmation state stating what happens next.
• Access state: anonymous.
• Failure/recovery: field-level validation errors are shown inline; a submission failure preserves the entered values and offers a retry.
• Continuation: the visitor can correct and resubmit, or use the published number 98198 99600.

FR-7 — Published enquiry call to action (explicit) As a Prospective Homebuyer / Property Seeker, I should see the "Jodi Option Available Enquire Now! 98198 99600" call to action, so that I can reach the developer directly about the Jodi option.

• Trigger/input: the visitor views the Landing page call-to-action block or the Inquiry page contact block.
• Observable result: the call to action and the number 98198 99600 are presented as a first-class element, not buried in fine print.
• Access state: anonymous.
• Failure/recovery: if the call action cannot be initiated on the device, the number remains readable and selectable.
• Continuation: the visitor places the call or continues to the enquiry form.

FR-8 — Company statistics presented as measured record (explicit) As a Prospective Homebuyer / Property Seeker, I should see Group Integrated's track record — 37 years of excellence, 2 Thousand+ happy families, 1 Million Sq. Ft. delivered, 2 Million Sq. Ft. in progress — so that I can judge the developer's delivery credibility.

• Trigger/input: the visitor scrolls the Landing page to the statistics strip.
• Observable result: the four statistics render in their own bordered cells with needle gauges that sweep once into view.
• Access state: anonymous.
• Failure/recovery: under reduced motion the counters render their final values immediately.
• Continuation: the visitor continues to the USP rows and the call to action.

FR-9 — Project USPs presented as engineering arguments (explicit) As a Prospective Homebuyer / Property Seeker, I should read the two project USPs — Zero-Wastage Planning and Low Maintenance Projects — with their explanations, so that I understand the design and cost arguments behind the developments.

• Trigger/input: the visitor scrolls the Landing page to the USP rows.
• Observable result: "01 ZERO-WASTAGE PLANNING" and "02 LOW MAINTENANCE PROJECTS" render as numbered ruled rows with their explanation text.
• Access state: anonymous.
• Failure/recovery: if an explanation is unavailable, the numbered row still renders with its title.
• Continuation: the visitor continues to the call to action or into the portfolio.

FR-10 — Mission statement presentation (explicit) As a Prospective Homebuyer / Property Seeker, I should read the "We Are Integrated Spaces" mission statement, so that I understand how Group Integrated plans its projects for light, ventilation, square-foot utilisation and harmony with the landscape.

• Trigger/input: the visitor reads the mission panel on the Landing page.
• Observable result: the mission statement is presented as a measured text column beside an amber-ruled stat column.
• Access state: anonymous.
• Failure/recovery: if the mission content is unavailable, the panel renders an explicit empty state.
• Continuation: the visitor continues to the statistics strip.

FR-11 — Administrator access is provisioned, not self-registered (required_inference) As a Group Integrated Site Administrator / Content Editor, I should be invited or provisioned before first-use administration, so that only authorised staff can manage the developer's public content.

• Trigger/input: Group Integrated provisions an administrator identity.
• Observable result: the provisioned administrator can establish a session through Login; no open self-registration path exists.
• Access state: the Login page is anonymously reachable; protected state remains unavailable until identity is established.
• Failure/recovery: an unprovisioned visitor cannot obtain administrative access and is returned to the public site.
• Continuation: the provisioned administrator signs in and reaches the Content overview.

FR-12 — Returning administrator verification through Login (required_inference) As a Group Integrated Site Administrator / Content Editor, I should verify my returning access through Login, so that I can resume managing durable property and project content.

• Trigger/input: the administrator submits their credentials on the Login page.
• Observable result: a session is established and the administrator reaches the protected Content overview.
• Access state: Login is anonymous; Content and Content Editor require the established session.
• Failure/recovery: invalid credentials produce a single non-enumerating message; the secret field is cleared and the form remains submittable.
• Continuation: the administrator proceeds to review or edit content, or returns to the public site.

FR-13 — Protected content overview (required_inference) As a Group Integrated Site Administrator / Content Editor, I should review the property and project content maintained for the public site, so that I can see what visitors are currently being shown.

• Trigger/input: the administrator opens the Content page with an established session.
• Observable result: a ruled table lists each content item with its name, unit type, location, possession status and Maha-Rera serial.
• Access state: protected; unavailable without an established administrator session.
• Failure/recovery: if the list cannot be retrieved, a ruled error state offers a retry.
• Continuation: the administrator opens an item in the Content Editor or starts a new one.

FR-14 — Adding and updating property and project content (required_inference) As a Group Integrated Site Administrator / Content Editor, I should add and update the property and project content shown on the public site, so that the public site stays current and accurate.

• Trigger/input: the administrator edits fields in the Content Editor and saves.
• Observable result: the saved values appear on the public Properties, Property Details and Landing surfaces.
• Access state: protected; unavailable without an established administrator session.
• Failure/recovery: validation failures are shown inline against the offending field; a save failure preserves the entered values and offers a retry.
• Continuation: the administrator continues editing, returns to the Content overview, or signs out.

FR-15 — Maha-Rera numbers and possession status are first-class content (explicit) As a Prospective Homebuyer / Property Seeker, I should see each project's Maha-Rera registration number and possession status paired to the project name, so that I can verify the regulatory standing and readiness of a development.

• Trigger/input: the visitor views a project on the Landing hero, Properties, or Property Details.
• Observable result: the Maha-Rera serial (P51800004521 for arya, P51800002899 for ahana) and the possession status ("Nearing Possession" for arya and ahana; "