Scribd
Upload
487 views16 pages

Defence Management System

The document outlines the design of a Defense Management System (DMS) to manage military resources including proposing tables to store user, role, employee, department, asset and assignment data, presenting an entity relationship diagram and normalized database schema up to second normal form. It also discusses conducting a feasibility study and requirements analysis to design the system and concludes that an integrated DMS is crucial for modern military organizations to effectively manage defense resources and operations.

Uploaded by

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

Defence Management System

The document outlines the design of a Defense Management System (DMS) to manage military resources including proposing tables to store user, role, employee, department, asset and assignment data, presenting an entity relationship diagram and normalized database schema up to second normal form. It also discusses conducting a feasibility study and requirements analysis to design the system and concludes that an integrated DMS is crucial for modern military organizations to effectively manage defense resources and operations.

Uploaded by

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

Defence

Management
System
NAME Ekankika Pradhan

REGD. NO.
2101020464
SEMESTER 4th

BRANCH CSE
CONTENT
 Introduction
 A feasibility study and Requirement Analysis
 Table Description with all constraints
 Design ER Diagram
 Relational Database Schema
 Normalized table (Up to 2NF)
 Conclusion
 References
Acknowledgement
 
 
We would like to articulate our deep gratitude to our project guide MONALISHA MISHRA

Asst. Professor, Department of Computer Science and Engineering, who has consistently
served as a source of inspiration and steadfast support. Additionally, we would like to express
our gratitude and debt of gratitude to the entire faculty and staff of the Department of
Computer Science and Engineering, without whose excellent effort and timely assistance, our
project work would have been extremely challenging.

Without our citation of and inspiration from the works of others, whose specifics are listed in
the references section, an assembly of this kind could never have been attempted. We
acknowledge that we owe them all something .
 
Introduction
 
The Defense Management System (DMS) is a comprehensive and highly integrated database
management system used by the military to manage its resources and maintain readiness for
national security. DMS is a complex network of databases, applications, and processes that
enable the military to efficiently and effectively manage its personnel, equipment, and
operations.
The role of DMS in national security cannot be overstated. It is a critical component of
military readiness, enabling the military to plan, execute, and support operations in an
increasingly complex and rapidly changing global environment. DMS helps the military
make data-driven decisions that improve situational awareness, optimise resource allocation,
and enhance operational effectiveness.
A feasibility study and requirement analysis
Feasibility Study:

Introduction: The development and implementation of a Defense Management System (DMS) requires a
comprehensive feasibility study to assess the technical, economic, and operational feasibility of the project.

Technical Feasibility: The technical feasibility study should evaluate the availability and suitability of the
database technologies and architectures, scalability of the system, required hardware and software resources,
and the reliability and availability of the system. The system should be designed to ensure high availability,
fault tolerance, and security.

Economic Feasibility: The economic feasibility study should assess the cost of hardware and software
resources, development and maintenance costs, potential return on investment, total cost of ownership, and
cost savings achieved through the use of DMS.

Operational Feasibility: The operational feasibility study should evaluate the user requirements, potential
impact on existing processes and workflows, potential benefits of DMS, usability and user interface, and
system integration with other military systems and databases.
Requirement Analysis:

Introduction: A comprehensive requirement analysis is essential for designing and implementing DMS. It should
identify user requirements, data and information needs, technical and operational requirements, and any constraints or
limitations on the system.

User Requirements: The requirement analysis should consider potential users, their roles and responsibilities, and their
information needs.

Data and Information Needs: The analysis should identify the data and information needs of the military and ensure that
the system is designed to provide real-time data access, handle large volumes of data, and process complex queries.

Technical and Operational Requirements: The analysis should consider the integration of DMS with existing military
systems and databases, security and privacy requirements, performance and availability requirements, and potential risks
or challenges associated with the system.

Constraints and Limitations: The analysis should identify any legal or regulatory requirements, budgetary constraints,
or technical limitations that may impact the design and implementation of DMS.
Table Description with all constraints:
There are several tables required for a defence management system. The table descriptions and their constraints are as follows:

a) Table: Users
Description: This table stores information about the users who have access to the system.

Constraints:
UserID: Primary key
Username: unique and not null
Password: not null

b) Table: Roles
Description: This table stores information about the roles of users in the system.

Constraints:
RoleID: Primary key
RoleName: Unique and not null
c) Table: User Roles
Description: This table stores the mapping between users and roles.

Constraints:
UserRolesID: Primary key
UserID: Foreign key referencing the Users table
RoleID: Foreign key referencing the Roles table

e) Table: Employees
Description: This table stores information about the employees of the defence organisation.

Constraints:
EmployeeID: Primary key
FirstName: Not null
LastName: Not null
Email: unique and not null
PhoneNumber: Not null
f) Table: Department Employees
Description: This table stores the mapping between departments and employees.

Constraints:

DepartmentEmployeeID: Primary key


DepartmentID: Foreign key referencing the Departments table
EmployeeID: Foreign key referencing the Employees table
g) Table: Assets
Description: This table stores information about the assets of the defence organisation.

Constraints:
AssetID: Primary key
AssetName: Not null
AssetType: not null
AssetLocation: Not null

h) Table: Asset Assignments


Description: This table stores the mapping between assets and employees who are
assigned to them.

Constraints:
AssetAssignmentID: Primary key
AssetID: Foreign key referencing the Assets table
EmployeeID: Foreign key referencing the Employees table
Design ER Diagram
Relational Database Schema
Users(UserID: primary key, Username, Password)

Roles(RoleID: primary key, RoleName)

UserRoles(UserRolesID: primary key, UserID: foreign key referencing Users, RoleID: foreign key
referencing Roles)

Departments(DepartmentID: primary key, DepartmentName)

Employees(EmployeeID: primary key, FirstName, LastName, Email, PhoneNumber)

DepartmentEmployees(DepartmentEmployeeID: primary key, DepartmentID: foreign key referencing


Departments, EmployeeID: foreign key referencing Employees)

Assets(AssetID: primary key, AssetName, AssetType, AssetLocation)

AssetAssignments(AssetAssignmentID: primary key, AssetID: foreign key referencing Assets,


EmployeeID: foreign key referencing Employees)
Normalized table (Up to
2NF)
Here are the normalized up to 2NF in table form:
Users table:
Roles table:

UserID Username Password

Primary key Non-key attribute Non-key attribute

RoleID RoleName

Primary key Non-key attribute


Conclusion
It can be concluded that the implementation of a comprehensive and integrated defence management
system is crucial for the success of any modern military organization. Such a system enables effective
and efficient coordination and management of defence resources, including personnel, equipment,
and information.
 
The use of advanced technologies such as artificial intelligence, big data analytics, and cybersecurity
measures is also essential to enhance the capabilities of the defence management system and ensure
the security of military operations and information.

You might also like