Scribd
Upload
4 views6 pages

Assignment SDA

The document outlines the Intelligent Traffic Management System (ITMS) designed to optimize traffic flow using sensor data and AI models, with features like helmet and seatbelt detection, shortest path calculation, and anomaly detection. It details the development process through the Waterfall and V-Model methodologies, highlighting functional and non-functional requirements, system design, implementation, testing, deployment, and maintenance. The V-Model is recommended as the best approach due to its emphasis on early validation and reliability for safety-critical applications.

Uploaded by

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

Assignment SDA

The document outlines the Intelligent Traffic Management System (ITMS) designed to optimize traffic flow using sensor data and AI models, with features like helmet and seatbelt detection, shortest path calculation, and anomaly detection. It details the development process through the Waterfall and V-Model methodologies, highlighting functional and non-functional requirements, system design, implementation, testing, deployment, and maintenance. The V-Model is recommended as the best approach due to its emphasis on early validation and reliability for safety-critical applications.

Uploaded by

Iqra Tariq
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Assignment

Name: Iqra Tariq


Roll no: 048/BSSE/sp-2023
Department: Software engineering
Subject: SDA
Submitted to: Sir Umer
Semester: Fifth
Intelligent Traffic Management System

Functional Requirements:
 Intelligent traffic management system aims to optimize traffic flow using sensor data, traffic
light, automation and predictive algorithm.
 ITMS must detect helmets and seatbelts of passengers using AI models.
 Intelligent Traffic Management system should provide shortest path calculation feature by
using cameras and threshold concept.
 ITMS must detect anomaly via cameras and sensors that are used in it.

Non-Functional Requirements:
 ITM system must provide shortest path and process data in real time.
 System must detect anomaly and provide updates to users via mobile app within 5 seconds.
 System must be accurate enough to provide traffic measurements.

Problem Statement:
There is no system that provide shortest path for emergency vehicles that must be
prioritised because of safety of people. Due to anomaly or any accidental issue on road
traffic jams and there’s no specific or efficient system that update other drivers for the real
time condition or about traffic on road.

Waterfall Model:

1. Requirements Analysis

 Objective: Define the full scope and functionalities of the ITMS.


 Activities:
o Meet with stakeholders (e.g., city traffic authorities, law enforcement).
o Identify key requirements:
 Real-time traffic monitoring
 Dynamic signal control
 Emergency vehicle prioritization
 Data logging and reporting
 Integration with traffic cameras and IoT devices
o Document functional and non-functional requirements.
 Deliverables: Software Requirement Specification (SRS) document.

2. System Design

 Objective: Create a blueprint for the system.


 Activities:
o High-level system architecture:
 Sensors (IoT, CCTV, traffic light controllers)
 Central traffic management server
 User interfaces (for traffic admins, mobile apps, etc.)
o Database design for vehicle logs, traffic patterns, etc.
o Define communication protocols between components.
 Deliverables: System architecture diagrams, Data flow diagrams (DFD), Entity
Relationship Diagrams (ERD).

3. Implementation

 Objective: Develop each module as per the design documents.


 Activities:
o Front-end development: dashboards, control panels.
o Backend development: traffic signal algorithms, real-time processing.
o Integration with hardware APIs (sensors, traffic lights).
o Programming languages used (e.g., Python for AI logic, JavaScript for UI).
 Deliverables: Working software modules.

4. Testing

 Objective: Ensure all modules work together and meet requirements.


 Activities:
o Unit testing of each component (camera input, signal controller).
o Integration testing: Sensor data → decision engine → traffic light control.
o System testing in a simulated or real environment.
o Performance testing under heavy traffic loads.
 Deliverables: Test cases, test results, bug reports.

5. Deployment

 Objective: Launch the system in the actual environment.


 Activities:
o Install the system in a selected area (pilot zone).
o Configure servers, sensors, and user access.
o Train operators and maintenance staff.
 Deliverables: Deployed system, deployment report, user manual.

6. Maintenance

 Objective: Ensure the system continues to perform efficiently.


 Activities:
o Monitor for software bugs and hardware issues.
o Regular updates (e.g., new AI models, database updates).
o Add new features (e.g., predictive congestion alerts).
 Deliverables: Maintenance logs, patches, updated documentation.
Pros:

1. Simple and Structured: Easy to manage due to its linear and sequential nature—
good for clearly defined ITMS requirements.
2. Early Documentation: Well-documented stages help in planning hardware-software
integration with city infrastructure.

Cons:

1. Inflexible to Changes: Difficult to go back and modify requirements once


development has started—problematic if ITMS needs evolve.
2. Late Testing: System is tested only after implementation, which may lead to late
discovery of critical integration issues.

V and V model:
Verification (Development Phases):
1. Requirements Analysis
Collect functional and non-functional requirements. Examples: traffic flow optimization,
real-time monitoring, integration with sensors and cameras.
2. System Design

Create system architecture. Define how components (sensors, signal controllers, central
server) interact.
3. High-Level Design (HLD)
Design individual modules: signal control logic, sensor data processor, traffic prediction AI.
Define APIs, module communication.
4. Low-Level Design (LLD)

Specify internal logic for each module. Example: AI-based decision engine, database schema
for vehicle logs.
5. Coding / Implementation

Develop the actual software components using programming languages and tools.

Validation (Testing Phases):


1. Unit Testing

Test individual modules in isolation (e.g., AI algorithm, sensor parser


2. Integration Testing

Ensure modules work together (e.g., sensor data flows to decision engine to signal controller)
3. System Testing

Validate the entire system in a controlled or live traffic environment. Test real-time
responsiveness, load handling.
4. Acceptance Testing

Conducted with client/stakeholders. Test overall functionality (emergency vehicle handling,


congestion detection).

Pros:

1. Early Test Planning: Each development stage has a corresponding test phase,
improving reliability of the ITMS.
2. Better Risk Management: Continuous validation helps catch issues early, ideal for
safety-critical systems like traffic control.

Cons:

1. No Flexibility: it's rigid unexpected changes (e.g., new sensor tech) are hard to
accommodate mid-process.
2. High Initial Effort: Requires significant planning and documentation early on, which
can delay actual development work.

Best Suitable Model on ITMS


The V-Model is best suited for ITMS due to its strong focus on early validation and reliability
in safety-critical systems.

You might also like