|| Jai Sri Gurudev ||

Sri Adichunchanagiri Shikshana Trust®

SJB INSTITUTE OF TECHNOLOGY
An Autonomous Institute under VTU
Approved AICTE-New Delhi, Recognized by UGC with 2(f) & 12(B)
No.67, BGS Health & Education City, Dr. Vishnuvardhan Road, Kengeri ,
Bengaluru, Karnataka 560060

Department of Computer Science and Engineering

FORMATIVE ASSESSMENT – 1

A report submitted in partial fulfilment of the requirements for the course

Full Stack Development

“FULL STACK DEVELOPMENT – FOUNDATION MODULE”

DOMAIN: “CLOUD RESOURCE MANAGEMENT SYSTEM”

Subject Code: 23CSP623

Submitted by

Sumedh R
Mundewadi
1JB23CS163

Faculty In-Charge Head of the Department

Vijayalakshmi B Dr. Krishna A.N
Academic Year: 2025-26
 ACKNOWLEDGEMENT

I would like to express my profound grateful to His Divine Soul Jagadguru Padmabhu-
shan Sri Sri Sri [Link] Mahaswamiji and His Holiness Jagadguru
Sri Sri Sri Dr. Nirmalanandanatha Mahaswamiji for providing us an opportunity to
complete my academics in this esteemed institution.

I would also like to express my profound thanks to Revered Sri Sri Dr. Prakashnath
Swamiji, Managing Director, BGS & SJB Group of Institutions, for his continuous sup-
port in providing amenities to carry out this project work in this admired institution.

I express my gratitude to Dr. Puttaraju, Academic Director, BGS & SJB Group of
Institutions, and Dr. K. V. Mahendra Prashanth, Principal, SJB Institute of Technol-
ogy, for providing me with an excellent facilities and academic ambience, which have
helped me with the satisfactory completion of project.

I extend my sincere thanks to Dr. Krishna A N, HOD, Computer Science and Engineer-
ing, for providing me an invaluable support throughout the period of the course.

I extend my heartfelt gratitude to Dr. Babu N V, Dean Academics, for his unwavering
support and inspiring academic environment all of which played a pivotal role in the
successful completion.

I express my deepest gratitude and sincere thanks to faculty in-charge for the course
Shilpashree S, Assistant Professor, Department of Computer Science and Engineer-
ing, for her valuable guidance, suggestions and cheerful encouragement throughout the
duration.

Finally, I take this opportunity to extend my earnest gratitude to my parents, Teaching

& Non- teaching staffs of the department, all my friends, who have directly or indirectly
supported me during the period of course.

Regards,
Sumedh R
1JB23CS163

i
 ABSTRACT
The Cloud Resource Management System is a conceptual academic project aimed at demonstrating
the application of fundamental software engineering and full-stack development concepts. The project
focuses on understanding how a real-world cloud infrastructure platform can be designed by modeling
resources, administrative interactions, and data flow, rather than implementing a complete functional
application. In modern enterprise environments, cloud management systems are essential for
monitoring the deployment and utilization of virtualized infrastructure. This project models such a
system using object-oriented programming principles, semantic web technologies, and database design
concepts. The emphasis is placed on clarity of design, proper structuring of components, and
adherence to standard development practices. The project is divided into four technical milestones. The
first milestone applies object-oriented programming concepts using Python to model different cloud
entities—such as virtual machines and storage buckets—demonstrating inheritance, method
overriding, and polymorphism. The second milestone focuses on frontend structure using semantic
HTML and HTTP concepts, where static web pages are designed to represent resource provisioning
and monitoring processes, along with a justified use of the POST method for form submission. The
third milestone involves designing an Entity-Relationship (ER) model that identifies key entities,
their attributes, and relationships, with an emphasis on minimizing data redundancy. The fourth
milestone demonstrates the use of the Command Line Interface (CLI) and virtual environments to
manage project setup and dependencies, highlighting the importance of environment isolation and
reproducibility in collaborative development. Overall, this project provides a structured overview of
how different layers of a software system can be planned and organized. By integrating object-oriented
design, web fundamentals, data modeling, and development environment management, the Cloud
Resource Management System serves as a comprehensive academic exercise aligned with real-world
software development workflows.

ii
 TABLE OF CONTENTS

Acknowledgement ..................................................................................................... i
Abstract ..................................................................................................................... ii
Table of Contents ..................................................................................................... iii
List of figures ............................................................................................................ v
List of Tables ............................................................................................................ vi

Chapter 1
Milestone 1: Object-oriented design in Python
1.1 Identification of Classes .............................................................................. 7
1.2 Object-Oriented Concepts Used .................................................................. 7
1.3 Source Code .............................................................................................. 8
1.4 Sample Output ........................................................................................... 10
1.5 Justification for the use of Inheritance ........................................................ 10

Chapter 2
Milestone 2: Semantic HTML and HTTP Concepts
2.1 Use of Semantic Html Elements................................................................. 11
2.2 HTML Form Design .................................................................................. 11
2.3 Use of HTTP POST Method ..................................................................... 12
2.4 Justification for using POST in this Application ........................................ 12
2.5 Comparison of GET And POST Methods.................................................. 12
2.6 Source code ...............................................................................................13
2.7 Screenshots ................................................................................................ 17

Chapter 3
Milestone 3: Entity Relationship Modeling
3.1 Identification of Entities........................................................................... 19
3.2 Summary of Primary and Foreign Keys ................................................... 19
3.3 Entity Relationship Diagram .................................................................... 20
3.4 Redundancy Minimization ....................................................................... 21

iii
Chapter 4
Milestone 4: Command Line Interface and Virtual Environments
4.1 Use of Command Line Interface (CLI). .................................................... 22
4.2 Purpose of Virtual Environments............................................................. 22
4.3 Flow Role of Dependency Specification ................................................... 22
4.4 Importance of CLI Proficiency in Collaborative Development ................. 23
4.5 Screenshots .............................................................................................. 23

Conclusion ............................................................................................................. 26

iv
 LIST OF FIGURES

SL NO DESCRIPTION PAGE NO

Fig 1.1 Output of python OOP code 10

Fig 2.1 Cloud Resource submission page 1 17

Fig 2.2 Cloud Resource submission page 2 17

Fig 2.3 Resource Deploy page 18

Fig 3.1 ER Diagram of Cloud Resource Management System 20

Fig 4.1 Creating the project and verification of Python installation 23

Fig 4.2 Creating and Activating the Virtual Environment 24

Fig 4.3 Installing the requests library using pip 24

Fig 4.4 [Link] file contents 25

v
 LIST OF TABLES

SL NO DESCRIPTION PAGE NO

Table 2.1 Comparison of GET and POST methods 12

Table 3.1 Summary of Primary and Foreign keys 19

vi
FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 1

CHAPTER 1

MILESTONE 1:

OBJECT-ORIENTED DESIGN IN PYTHON

1.1 IDENTIFICATION OF CLASSES

Existing systems are often complex or lack usability; the proposed web-based solution
offers a simple, interactive, and automated approach. The following classes are identi-
fied to model the system:

 CloudResource (Base Class): Represents a generic system cloud resource and

contains common attributes such as resource ID, name, and resource type.
 Provision (Derived Class): Represents users who deploy cloud resources. This
class extends the User class and includes additional attributes related to research
specialization.
 Reviewer (Derived Class): Represents users who review submitted proposals. This
class also extends the User class and includes attributes related to expertise.

The use of inheritance establishes an is-a relationship, where a Researcher and a Re-
viewer are both types of Users.

1.2 OBJECT-ORIENTED CONCEPTS USED

1.2.1 Inheritance
Inheritance is used to share common attributes and methods through a base User
class. The Researcher and Reviewer classes extend this base class by adding role-
specific data, improving code reusability and maintainability.
1.2.2 Method Overriding
Method overriding allows derived classes to provide role specific behavior by rede-
fining the same method. Although the method name remains unchanged, its imple-
mentation differs for researchers and reviewers.
1.2.3 Polymorphism

Polymorphism is demonstrated by handling different user objects through a com-

mon interface. The same method call invokes different implementations at runtime
based on the object type, enabling flexible management of multiple user roles.

Dept. of CSE, SJBIT 2025-2026 Page 7

 FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 1

1.3 SOURCE CODE

The Python program demonstrates inheritance, method overriding, and polymorphism

using a simple base class and derived classes, with a focus on clarity and readability.
# Cloud Resource Management System
# Milestone 1 – Object Oriented Programming in Python

class CloudResource:

"""Base class Representing a CloudResource asset."""

def __init__(self, resource_id, region, owner_email):
self.resource_id = resource_id
[Link] = region
self.owner_email = owner_email
[Link] = "STOPPED"

def deploy(self):
"""Method to be Overriden by the Child classes(Derived classes)"""
pass

def get_cost_estimation(self):
"""Polymorphic method to calculate cost"""
return 0.0

class LambdaFunction(CloudResource):
"""Derived class for serverless function"""
def __init__(self, resource_id, region, owner_email, runtime, memory_db):
super().__init__(resource_id, region, owner_email)
[Link] = runtime
self.memory_db = memory_db

def deploy(self):
[Link] = "RUNNING"
print(f"Deploying Lambda: '{self.resource_id}' ({[Link]}) to
{[Link]}....")

def get_cost_estimation(self):
"""Mock Calculation: $0.00000067 per GB-second"""
return 5.50

Dept. of CSE, SJBIT 2025-2026 Page 8

 FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 1

class DynamoDBTable(CloudResource):

"""Derived class for No SQL Databases lie=ke DynamoDB"""

def __init__(self, resource_id, region, owner_email, partition_key):

super().__init__(resource_id, region, owner_email)
self.partition_key = partition_key
def deploy(self):
[Link] = "RUNNING"
print(f"Provisioning DynamoDB Table '{self.resource_id}' in {[Link]}...")
def get_cost_estimation(self):
# Mock Calculation: Storage + Read/Write units
return 25.00

# Main Execution
if __name__ == "__main__":
print(f"---Cloud resource Monitor System---")
# Instantiating Multiple derived types
fn_processor = LambdaFunction("data-proc-v1", "us-east-1", "student@[Link]",
"python3.14", 128)
db_users = DynamoDBTable("user-table-prod", "ap-south-1", "student@[Link]",
"UserID")
# Storing in a single collection
resources = [fn_processor, db_users]
# Demonstrating Polymorphism
total_cloud_cost = 0.0
for res in resources:
[Link]() # Method Overriding in action
cost = res.get_cost_estimation()
total_cloud_cost += cost
print(f"Resource: {res.resource_id} | Status: {[Link]} | Est. Cost: ${cost:.2f}\n")

print(f"Total Projected Monthly Cloud Bill: ${total_cloud_cost:.2f}")

Dept. of CSE, SJBIT 2025-2026 Page 9

 FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 1

1.4 SAMPLE OUTPUT

Fig 1.1: Output of python OOP code

The program processes Researcher and Reviewer objects together, where the same
method call produces different outputs, demonstrating polymorphism and method over-
riding.

1.5 JUSTIFICATION FOR THE USE OF INHERITANCE

In the Cloud Resource Management System, inheritance is used to model different infrastructure
components with shared characteristics. A base CloudResource class stores common attributes
such as resource ID, region, and status. The ComputeInstance and StorageBucket classes inherit
from this base class and implement type-specific behaviors, such as instance provisioning and
capacity monitoring. This approach improves code reusability, reduces redundancy, and provides a
clear hierarchical structure, making the system easier to extend with additional resource types in the
future.

Dept. of CSE, SJBIT 2025-2026 P a g e 10

FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4

CHAPTER 2

MILESTONE 2:

SEMANTIC HTML AND HTTP CONCEPTS

2.1 USE OF SEMANTIC HTML ELEMENTS

Semantic HTML elements describe the purpose of content rather than its appearance. In
this project, semantic tags are used to clearly separate different parts of the web page,
making the structure easier to understand and maintain.

The <header> element is used to display the title and description of the Cloud Resource
Management System, providing context to the user. Navigation links are placed inside
the <nav> element, allowing users to move between the proposal submission page and
the proposal listing page.

The <main> element contains the primary content of the page, ensuring that the core
information is clearly identified. Related content is grouped using <section> elements,
while individual grant proposals are represented using <article> elements. The <footer>
element is used to display copyright information and ownership details.

Using semantic HTML improves accessibility for screen readers, enhances search en-
gine understanding, and follows best practices in modern web development.

2.2 HTML FORM DESIGN

The proposal submission page includes an HTML form designed to collect essential
details required for a research grant proposal. The form contains input fields for resource
title, principal resource details, resource name, resource region, estimated resource
amount,usage duration, and a brief abstract.
Each form element is labeled clearly to ensure usability and avoid confusion during data
entry. Required fields are marked to guide users and ensure that important information
is not omitted. Different input types such as text fields, selection lists, numeric inputs,
and text areas are used to represent various data formats.
Although the form is static and does not store data, its structure accurately represents
how proposal submission would occur in a real-world resource management system.

Dept. of CSE, SJBIT 2025-2026 P a g e | 11

FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4

2.3 USE OF HTTP POST METHOD

The HTTP POST method is used for submitting the proposal form. POST is designed to
send data to the server in the request body, making it suitable for operations that create
new records or modify existing data. In the Cloud Resource Management System,
proposal submission involves sending detailed and sensitive information such as
project descriptions and funding requirements. Using POST ensures that this data is not
exposed in the URL and allows larger amounts of data to be transmitted securely.

2.4 JUSTIFICATION FOR USING POST IN THIS APPLICATION

The POST method is chosen for this application because submitting a Cloud Resource
results in the creation of a new system record. Additionally, proposal data includes
sensitive information that should not be visible in the URL Using POST aligns with
HTTP standards and reflects real-world implementation practices used in academic and
research platforms.

2.5 COMPARISON OF GET AND POST METHODS

Aspect GET Method POST Method

Used to submit
Used to retrieve data
Purpose data to the
from the server
server
Data is appended to Data is sent in
Data Visibility
the URL the request body
More suitable
Less secure for sensi-
Security for
tive information
confidential
data
Limited by URL Supports larger
Data Size
length data sizes
Form submis-
Searching and filter-
Typical Usage sion and data
ing
creation
Table 2.1: Comparison of GET and POST methods

Table 2.1 Presents a comparison of the GET and POST HTTP methods, highlighting
their differences in functionality, data handling, and use cases.

Dept. of CSE, SJBIT 2025-2026 P a g e | 12

FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4

2.6 SOURCE CODE

2.6.1 [Link]
3 <!doctype html>
4 <html lang="en">
5 <head>
6 <meta charset="UTF-8" />
7 <title>Cloud Monitor Dashboard</title>
8 <link rel="stylesheet" href="[Link]" />
9 </head>
10 <body>
11 <header>
12 <h1>Serverless Cloud Monitor</h1>
13 <nav>
14 <ul>
15 <li><a href="[Link]">Dashboard</a></li>
16 <li><a href="[Link]">Provision Resource</a></li>
17 </ul>
18 </nav>
19 </header>
20
21 <main>
22 <section>
23 <h2>Active Resources</h2>
24 <article>
25 <h3>Function: data-proc-v1</h3>
26 <p>Region: us-east-1 | Status: <strong>Running</strong></p>
27 <p>Runtime: Python 3.14</p>
28 </article>
29 <article>
30 <h3>DB: user-table-prod</h3>
31 <p>Region: ap-south-1 | Status: <strong>Active</strong></p>
32 <p>Type: NoSQL Store</p>
33 </article>
34 </section>
35 </main>
36
37 <footer>
38 <p>&copy; 2026 Cloud Monitor System. Student ID: 1JB23CS163</p>
39 </footer>
40 </body>
41 </html>

Dept. of CSE, SJBIT 2025-2026 P a g e | 13

 FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4

2.6.2 [Link]

3 <!doctype html>
4 <html lang="en">
5 <head>
6 <meta charset="UTF-8" />
7 <title>Provision New Resource</title>
8 <link rel="stylesheet" href="[Link]" />
9 </head>
10 <body>
11 <header>
12 <h1>Provisioning Portal</h1>
13 <nav>
14 <ul>
15 <li><a href="[Link]">Dashboard</a></li>
16 <li><a href="[Link]">Provision Resource</a></li>
17 </ul>
18 </nav>
19 </header>
20
21 <main>
22 <section>
23 <h2>Deploy New Asset</h2>
24 <form action="/api/deploy" method="POST">
25 <label for="res_name">Resource Name:</label><br />
26 <input
27 type="text"
28 id="res_name"
29 name="resource_name"
30 required
31 /><br /><br />
32
33 <label for="res_type">Service Type:</label><br />
34 <select id="res_type" name="service_type">
35 <option value="lambda">AWS Lambda</option>
36 <option value="dynamodb">Amazon DynamoDB</option>
37 <option value="s3">S3 Bucket</option></select
38 ><br /><br />
39
40 <label for="region">Target Region:</label><br />
41 <select id="region" name="region">
42 <option value="us-east-1">US East (N. Virginia)</option>
43 <option value="ap-south-1">Asia Pacific (Mumbai)</option></select
44 ><br /><br />
45
46 <button type="submit">Deploy Resource</button>
47 </form>
48 </section>
49 </main>

Dept. of CSE, SJBIT 2025-2026 P a g e | 14

 FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4
49.6 SCREENSHOTS

49.7

Fig 2.1: Cloud Resource submission page 1

Fig 2.1 Illustrates the first view of the research proposal submission page used to collect
initial proposal details in the Cloud Resource Management System.

Fig 2.2: Cloud Resource submission page 2

Fig 2.2 Illustrates the research proposal submission page used for entering and submit-
ting proposal details in the Cloud Resource Management System.

Dept. of CSE, SJBIT 2025-2026 P a g e | 15

FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4

Fig 2.3: Resource Provision page

Fig 2.3 Illustrates the review proposal page used to display submitted research proposals
for evaluation in the Cloud Resource Management System.

Dept. of CSE, SJBIT 2025-2026 P a g e | 16

FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4

CHAPTER 3

MILESTONE 3:

ENTITY RELATIONSHIP MODELING

3.1 IDENTIFICATION OF ENTITIES

Based on the system requirements, the following entities are identified:
 Researcher: Represents users who submit research grant proposals.
 GrantProposal: Represents research proposals submitted for funding considera-
tion.
 Reviewer: Represents users responsible for reviewing and evaluating submitted
proposals.
These entities represent the core components of the system and are sufficient to model
the main data requirements without unnecessary complexity.

3.2 SUMMARY OF PRIMARY AND FOREIGN KEYS

Entity Name Primary Key Foreign Key(s)

Researcher researcher_id —

Reviewer reviewer_id —

GrantProposal proposal_id researcher_id,reviewer_id

Table 3.1: Summary of Primary and Foreign keys

Table 3.1 Provides a summary of the primary and foreign keys used in the Entity Rela-
tionship design of the Research Grant Proposal Management System.

Each entity in the Research Grant Proposal Management System is uniquely identified
using a primary key. The researcher_id uniquely identifies each researcher, while the
reviewer_id uniquely identifies each reviewer. The proposal_id uniquely identifies each
grant proposal. Foreign keys are used in the GrantProposal entity to establish relation-
ships with the Researcher and Reviewer entities. These keys ensure referential integrity
by linking proposals to the users who submit and review them.

Dept. of CSE, SJBIT 2025-2026 P a g e | 17

FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4

3.3 ENTITY RELATIONSHIP DIAGRAM

The ER diagram visually represents the identified entities, their attributes, and the rela-
tionships between them. Rectangular boxes represent entities, attributes are listed within
the entities, and relationships are shown using connecting lines with appropriate cardi-
nalities.

Fig 3.1: ER Diagram of Cloud Resource Management System

Fig 3.1 Illustrates the Entity Relationship diagram representing the data structure of the
Cloud Resource Management System.

Dept. of CSE, SJBIT 2025-2026 P a g e | 18

FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4

The diagram clearly highlights primary keys and foreign keys, providing a clear and
structured view of the system’s data organization

3.4 REDUNDANCY MINIMIZATION

The ER design reduces data redundancy by storing administrative details and regional
information only once in their respective entities. These are referenced in the CloudResource
entity using foreign keys, which prevents the repetition of data when multiple resources are
deployed by the same admin or in the same region. This approach improves data consistency,
simplifies updates, and ensures a scalable database structure aligned with normalization
principles.

Dept. of CSE, SJBIT 2025-2026 P a g e | 19

FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4

CHAPTER 4

MILESTONE 4:

COMMAND LINE INTERFACE AND VIRTUAL

ENVIRONMENTS

4.1 USE OF COMMAND LINE INTERFACE (CLI)

The Command Line Interface is used to perform all project setup tasks. Using the CLI al-
lows developers to execute commands directly, automate repetitive tasks, and maintain better
control over the development process.
In this milestone, the CLI is used to:
 Create and navigate project directories
 Verify Python installation
 Create and activate a virtual environment
 Install external libraries
 List project files and folders
These operations demonstrate familiarity with basic yet essential command-line operations.

4.2 PURPOSE OF VIRTUAL ENVIRONMENTS

A virtual environment is used to create an isolated workspace for the project. It contains
its own Python interpreter and installed libraries, separate from the system-wide Python
installation.
The primary purpose of using a virtual environment is to avoid dependency conflicts
between different projects. Each project can maintain its own set of libraries and ver-
sions, ensuring predictable behavior. This is especially important when working on mul-
tiple projects or collaborating with other developers.

4.3 ROLE OF DEPENDENCY SPECIFICATION

Dependency specification is achieved by generating a [Link] file using the pip
freeze command. This file lists all installed libraries along with their versions.
The [Link] file allows other developers to recreate the same development en-
vironment easily. By installing dependencies from this file, consistency is maintained

Dept. of CSE, SJBIT 2025-2026 P a g e | 20

FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4

across different systems, reducing environment-related issues during development and

testing.

4.4 IMPORTANCE OF CLI PROFICIENCY IN COLLABORATIVE

DEVELOPMENT
Command Line Interface (CLI) proficiency is essential in collaborative software devel-
opment as it provides a consistent way to perform tasks across different systems and
environments. Developers use the CLI to manage directories, set up virtual environ-
ments, install dependencies, and run scripts efficiently. It is also widely used in version
control, build processes, and deployment workflows.
In team environments, CLI usage ensures consistent project setup, reduces configuration
errors, and enables quick environment reproduction. Overall, CLI proficiency improves
efficiency, supports automation, and enhances collaboration, making it a vital skill in
professional software development.

4.5 SCREENSHOTS

Fig 4.1: Creating the project and verification of Python installation

Fig 4.1 Illustrates the creation of the project directory and the verification of the Python
installation required for the Cloud Resource Management System.

Dept. of CSE, SJBIT 2025-2026 P a g e | 21

FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4

Fig 4.2: Creating and Activating the Virtual Environment

Fig 4.2 Illustrates the creation and activation of the virtual environment used for isolat-
ing project dependencies in the Cloud Resource Management System.

Fig 4.3: Installing the requests library using pip

Fig 4.3 Illustrates the installation of the requests library using pip within the virtual en-
vironment for the Cloud Resource Management System.

Dept. of CSE, SJBIT 2025-2026 P a g e | 22

FULL STACK DEVELOPMENT – FOUNDATION MODULE MILESTONE 4

Fig 4.4: [Link] file contents

Fig 4.4 Illustrates the contents of the [Link] file listing the project dependen-
cies for the Cloud Resource Management System.

Dept. of CSE, SJBIT 2025-2026 P a g e | 23

FULL STACK DEVELOPMENT – FOUNDATION MODULE CONCLUSION

CONCLUSION

The Cloud Resource Management System project was carried out as part of the Full
Stack Development course with the objective of understanding and applying
fundamental software engineering and web development concepts. The project focused
on conceptual clarity, structured design, and adherence to standard development
practices rather than building a fully functional system. Through the milestone-based
approach, the project demonstrated how a real-world infrastructure domain can be
analyzed and modeled effectively. The first milestone applied object-oriented
programming concepts using Python to represent cloud resources and their operational
states. By using inheritance, method overriding, and polymorphism, the system design
became modular, reusable, and aligned with real-world infrastructure relationships. The
second milestone focused on frontend structure using semantic HTML and HTTP
concepts. Static web pages were designed to represent resource provisioning and status
monitoring, and the use of the POST method was justified based on data sensitivity
and system behavior. This milestone highlighted how user interaction with cloud
services is conceptually modeled at the web interface level. The third milestone
involved designing an Entity Relationship (ER) model to structure system data
efficiently. Key entities such as Cloud Resources, Administrators, and Regions were
identified, with an emphasis on minimizing redundancy and maintaining data
consistency. This design forms a strong foundation for future cloud database
implementation. The final milestone demonstrated the use of the Command Line
Interface and virtual environments to manage project setup and dependencies. By
following standard CLI-based workflows, the project reinforced the importance of
environment isolation, dependency management, and reproducibility in collaborative
development. Overall, this project provided a comprehensive understanding of how
different layers of a software system are planned and structured. The Cloud Resource
Management System serves as a valuable academic exercise that strengthens
foundational skills required for advanced full stack development and real-world
software engineering practices.

Dept. of CSE, SJBIT 2025-2026 P a g e | 24