Fairfield Institute of Management and Technology

Subject Name: Software Engineering

Subject Code: BCA(108)

Submitted to: Submitted by:

MR. Ms. Aruna Joshi Name: GARV
(ASST. PROF IT DEPARTMENT) Enrollment no: 00190102024
Course: BCA
Semester/Section: 2nd SEM
 TABLE OF CONTENTS

S.NO TOPIC SIGN.

1.
Select and Write down the problem statement for a real time system of
relevance

2.
Analyze requirement for a system and develop Software Requirement
Specification (SRS) for suggested system.

3.
To create the function oriented diagram: Data Flow Diagram (DFD).

4.
To perform the users view analysis for the suggested system: Use case
diagram.

5.
To draw the structural view diagram for the system: Class diagram

6.
To draw the behavioral view diagram : Statechart diagram or Activity
diagram.

7.
To perform the behavioral view diagram for the suggested system :
Sequence diagram.

8.
Draw the component diagram.

9.
Draw the Deployment diagram.

10.
Perform Measurement of complexity with Halstead Metrics for chosen
system. Suggested Application .(i) Inventory Management.
Q-1 Select and Write down the problem statement for a real time system of
relevance.

🧾 Problem Statement: Real-Time

Fault Detection System (RTFDS)

🔍 Title:

Design and Development of a Real-Time Fault Detection System for Industrial

Machine
s

📌 Background:

In modern industries, the continuous and reliable functioning of

machinery is critical. Downtime due to unexpected faults can lead to
significant production losses, equipment damage, and even safety
hazards. Traditional fault detection methods are often reactive,
inefficient, or too delayed to prevent impact.

🎯 Problem:

There is a lack of a system that can continuously monitor industrial machines

in real time, detect anomalies in sensor data immediately, and generate
actionable alerts for operators and maintenance teams before a critical failure
occurs.

✅ Objective:
To design and implement a Real-Time Fault Detection System (RTFDS) that:

1. Continuously collects data from various machine sensors (temperature, pressure,

vibration, etc.).

2. Analyzes the data in real time using predefined thresholds and rules.

3. Detects abnormalities (faults) as soon as they occur.

4. Sends alerts to concerned personnel (operator/maintenance) with relevant fault

details.
 5. Allows acknowledgment and logging of alerts for future analysis and maintenance
scheduling.

🔧 Scope of the System:

 Sensor data acquisition (real or simulated).

 Real-time fault detection logic.

 Alert generation and notification.

 User roles: Operator, Maintenance Staff, and Admin.

 Dashboard to display machine health and alert status.

 Fault log and reporting features.

📈 Expected Outcome:

The system will help industries minimize unplanned downtimes, improve

equipment longevity, enhance safety, and support predictive maintenance by
detecting potential faults early.
Q-2 Analyze requirement for a system and develop Software Requirement
Specification (SRS) for suggested system.

📝 Software Requirement Specification (SRS)

1.Introduction

1.1 Purpose

The purpose of this document is to define the Software Requirements

Specification (SRS) for a Real-Time Fault Detection System (RTFDS)
designed to monitor machinery in a manufacturing environment. This system
will detect faults in real-time and notify maintenance teams to prevent
breakdowns and reduce downtime.

1.2 Scope

The RTFDS will:

• Collect data in real-time from sensors installed on machinery.

• Detect faults by analyzing sensor data.

• Notify maintenance teams instantly when an issue is detected.

• Provide a dashboard for real-time status monitoring.

• Support predictive maintenance based on historical data.

• Be scalable for use in medium and large manufacturing plants.

1.3 Definitions, Acronyms, and Abbreviations

• RTFDS: Real-Time Fault Detection System

• UI: User Interface

• DBMS: Database Management System

• IoT: Internet of Things

1.4 References

• IEEE 830-1998 SRS Standard

• Sensor datasheets (temperature, vibration, pressure, etc.)

 • Manufacturing maintenance policies

2.Overall Description

2.1 Product Perspective

The RTFDS will integrate with existing production systems and machinery. It will
have modules for data collection, fault detection, alerting, and visualization.

2.2 Product Functions

• Real-time data collection from sensors.

• Real-time fault detection using threshold and pattern analysis.

• Fault notification system (SMS, email, dashboard alert).

• Dashboard for monitoring and reports.

• Historical data storage and analysis.

2.3 User Characteristics

• Operators: Monitor dashboard and respond to alerts.

• Maintenance Team: Receive fault alerts and perform actions.

• Admin/IT Staff: Manage system configuration and sensor setup.

2.4 Constraints

• Real-time processing must occur within 1 second of data input.

• System must handle at least 1000 sensor inputs concurrently.

• Should support integration with third-party maintenance tools.

2.5 Assumptions and Dependencies

• All machinery is equipped with compatible sensors.

• Stable network connectivity within the manufacturing plant.

3.Specific Requirements

3.1 Functional Requirements

FR1: The system shall collect sensor data every 500ms.

FR2: The system shall detect faults based on predefined thresholds.
FR3: The system shall notify users of faults through the dashboard and email.
FR4: The system shall display real-time machine status on the dashboard.
FR5: The system shall store all sensor data in a database.
FR6: The system shall allow users to define custom thresholds per
machine. FR7: The system shall generate reports of faults and
maintenance actions.

3.2 Non-Functional Requirements

NFR1: The system shall provide fault detection results within 1 second.
NFR2: The system shall have 99.9% uptime.
NFR3: The dashboard shall be accessible via secure login.
NFR4: The system shall support role-based access control.
NFR5: The system shall support at least 1000 concurrent sensor data streams.

3.3 Interface Requirements

• Hardware Interface: Supports IoT-enabled sensors (temperature, vibration,

etc.)

• Software Interface: REST API for integration with ERP or CMMS tools.

• User Interface: Web-based dashboard, responsive for mobile and desktop.

Q-3 To create the function oriented diagram: Data Flow Diagram (DFD).

✅ 🔹Level 0 DFD (Context Diagram)

This shows the system as a single process and its interactions with external
entities.
🔹Level 1 DFD (Decomposition)

Breaks the system into multiple functional components:

Q-4 To perform the users view analysis for the suggested system: Use case
diagram.

Output
Q-5 To draw the structural view diagram for the system: Class diagram
Q-6 To draw the behavioral view diagram : Statechart diagram or Activity
diagram.
Q-7 To perform the behavioral view diagram for the suggested system :
Sequence diagram.

Output:-
Q-8 Draw the component diagram.

Output:-
Q-9 Draw the Deployment diagram.

Output:-
Q-10 Perform Measurement of complexity with Halstead Metrics for chosen
system.

Suggested Application.

(i) Inventory Management.

Output

Halstead Metrics Calculation

• Program Vocabulary (η) = η + η = 5 + 4 = 9

• Program Length (N) = N + N = 6 + 7 = 13

• Volume (V) = N × log (η) = 13 × log (9) ≈ 13 × 3.17 ≈ 41.2

• Difficulty (D) = (η / 2) × (N / η ) = (5 / 2) × (7 / 4) = 2.5 × 1.75 = 4.375

• Effort (E) = V × D = 41.2 × 4.375 ≈ 180.25

• Time (T) = E / 18 ≈ 10.0 seconds

• Estimated Bugs (B) = V / 3000 ≈ 0.0137 bugs