Scribd
Upload
2 views5 pages

Software Engineering Questions

Drive utilizes the Agile development model with a Peer-to-Peer negotiation framework and follows a Client-Server architecture supported by Microservices and Event-Driven architecture. It adheres to ISO standards for security and software quality, including ISO/IEC 27001 and ISO/IEC 25010. The document also outlines the database structure through an ERD and system design via a UML Class Diagram, detailing key entities, relationships, and classes involved in the system.

Uploaded by

meerali5284
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views5 pages

Software Engineering Questions

Drive utilizes the Agile development model with a Peer-to-Peer negotiation framework and follows a Client-Server architecture supported by Microservices and Event-Driven architecture. It adheres to ISO standards for security and software quality, including ISO/IEC 27001 and ISO/IEC 25010. The document also outlines the database structure through an ERD and system design via a UML Class Diagram, detailing key entities, relationships, and classes involved in the system.

Uploaded by

meerali5284
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

WHICH MODEL is used in in drive?

Yes, in Drive uses the Agile model for development, but its core system is based
on a Peer-to-Peer negotiation model
Which Pattern is USED?
In Drive mainly uses the Peer-to-Peer (P2P) pattern, supported by MVC
Model: handles data (rides, users)
View: user interface (app screens)
Controller: processes user actions.

SOFTWARE ARCHITECTURE?
In Drive uses Client–Server architecture as its core, supported by Micro services
and Event-Driven architecture for scalability and real-time communication.
Question: which ISO standard is used?
In Drive typically follows:
1. ISO/IEC 27001 for security
2. ISO/IEC 27017 and 27018 for cloud and privacy
3. ISO/IEC 25010 for software quality.

How to control or monitor your software system?


Answer: Jira
How to Create an Epic in Jira?
Answer: Jira ¬ Create Task ¬ Epic.
Lack of Control: JIRA
Q/A: Readability, Maintainability, and Efficiency.
TRIAD: Confidently, Integrity, Availability.
SDLC: Design, Analysis, Implementation, Development, Testing/Integration,
Maintenance.
ERD Explanation (Left Side)
🎯 Purpose:

Shows database structure (tables + relationships)

🔹 Main Entities:

 User → base entity (can be driver or passenger)


 Driver & Passenger → derived from User
 Vehicle → belongs to Driver
 Ride → central entity (stores trip info)
 Payment → linked with Ride
 Rating → feedback after ride
 Notification → alerts to users

🔗 Relationships:

 One User → Driver / Passenger


 One Driver → Vehicle
 One Passenger → many Rides
 One Driver → many Rides
 One Ride → one Payment
 One Ride → Rating
 One User → many Notifications

👉 Key Point:
ERD focuses on data & database tables

🏗️ UML Class Diagram Explanation (Right


Side)
🎯 Purpose:

Shows system design (classes + behavior)

🔹 Main Classes:

👤 User

 Attributes: name, email, phone


 Functions: login(), register()

🚶 Passenger

 requestRide()
 makePayment()

🚗 Driver

 acceptRide()
 rejectRide()

🚙 Vehicle

 Stores car info

📍 Ride

 Contains trip details


 Function: createRide()

💳 Payment

 Handles payment
 processPayment()

⭐ Rating

 Stores feedback
 submitRating()

🔗 Relationships:

 Passenger requests Ride


 Driver accepts/rejects Ride
 Ride uses Vehicle
 Ride linked to Payment & Rating

👉 Key Point:
UML shows logic + behavior of system

You might also like