Business Requirements Report: OSDS Architecture and Cloud Edge

This business requirements report addresses the needs of DSI (Department of Spatial Information), which provides spatial data through its Online Spatial Delivery System (OSDS). The report evaluates potential deployment models, focusing on cloud-based OSDS, and assesses the advantages and disadvantages of IaaS and PaaS. It explores the use of Cloud Edge for OSDS, detailing its benefits and drawbacks. The report also compares monolithic and microservice architectures, evaluating their respective strengths and weaknesses, and provides recommendations for the best architectural approach for DSI. The report concludes with a summary of findings and references.

Running head: BUSINESS REQUIRMENTS REPORTS
Business Requirements Report
Name of the Student
Name of the University
Author’s Note

1BUSINESS REQUIREMENTS REPORT
Table of Contents
Introduction......................................................................................................................................2
Possible delivery and deployment models.......................................................................................2
IaaS and PaaS Evaluation............................................................................................................3
Possible Architecture for OSDS..................................................................................................4
Use of Cloud Edge for OSDS..........................................................................................................5
Differences between monolithic & MicroService Architectures.....................................................7
Evaluation of Software Architectures..............................................................................................9
Recommended Approach...............................................................................................................11
Conclusion.....................................................................................................................................12
References......................................................................................................................................14

2BUSINESS REQUIREMENTS REPORT
Introduction
DSI (Department of Spatial Information), which applies to the state government business,
offers spatial information exclusively to government agencies and limited detail to the public. It
uses the Online Spatial Delivery System (OSDS) to provide this sort of information. To handle
all that material, DSI uses the web services as well as other internal applications. As the interest
in this program grew, DSI had decided to introduce a modern knowledge management
framework, retaining the infrastructure and providing it to the public and government alike. After
figuring out several ideas DSI Executive team came up with two recommendations either to
expand the storage and hosting capability of DSI data centers or to move OSDS to cloud
provider. The executive of DSI chose to adopt the OSDS to the cloud provider for meeting their
budget restriction. Therefore, this report aims to discuss the advantages and disadvantages of
IaaS and PaaS and evaluate the usages of Cloud edge for OSDS. This report also compares the
monolithic and MicroService architectures and evaluates the software architecture.
Possible delivery and deployment models
The possible deployment model for DSI is cloud-based OSDS, which will be very
beneficial for them. An OSDS is the computer storage system, which connects the data through
containers called artifacts defined by a user or program (Noel & Lama, 2017). The objects are
positioned in the flat address space where all of them reside at the same stage and it cannot be
put within each other. It has the unique object identifier, which enables the end user or the
server for retrieving it without knowing the physical location of the data stored within.

3BUSINESS REQUIREMENTS REPORT
IaaS and PaaS Evaluation
For this study, the chosen service of OSDS is PaaS. PaaS (Platform as a Service) will
help in enabling DSI to reserve computing room on the computer, which offers capacity for
running applications, apps, which operating systems in the cloud as well (Yangui et al., 2016). It
will help the developers to check new applications if and when required on leased virtual
computers. There are benefits as well as a few drawbacks as in PaaS.
Advantages
 Automated Upgrades: The upgrades of the applications are performed automatically and
all the new releases, improvements are available (Kolb & Wirtz, 2014). An upgrade will
not run the risk of losing out. That will save loads of time and money. Security updates
address any glitches and other technical concerns.
 Low Investments: DSI will be able to use the app without needing to spend in technology
elsewhere in an in-house environment.
 Reduced Costs: Because the billing process is pay-as-you-use, significant savings are
rendered for the organization without needing to buy the required tools such as
databases and server to operate the application (Amaral et al., 2015).
 Collaboration: Since this is an internet-based network, it helps workers to access and
operate on the apps from anywhere, upgrade them without being physically present in the
company premises.
 Focus: Instead of getting drawn to system repairs, the IT unit will rely mainly on key
applications.
Disadvantages

4BUSINESS REQUIREMENTS REPORT
 Lock-in risks: This is one option that the organization needs to carefully test before
they sign up with any other company. If the organization gets stuck in a certain language,
application, or interface, which could impact the organization with some unwanted
framework they do not need.
 Restricted Scalability: PaaS can be marginally inflexible when the organization will need
on demand supplies (Androcec, Vrcek & Küngas, 2015). In the PaaS setting the reduction
or extension dependent on business needs is minimal.
 Data Backup: While PaaS offers replication, one of the own should be done because the
system will often have the same vulnerabilities towards any accident.
Possible Architecture for OSDS
Fig: Possible architecture for OSDS infrastructure (Source: Karakoyunlu, Runde &
Chandy, 2014)

5BUSINESS REQUIREMENTS REPORT
Following Image can be the possible architecture and deployment of the OSD system of
DSI. There are two key components to the program, the OSD initiator and the OSD aim. The
image displays the design elements and their partnerships. Using the iSCSI, the initiator and the
target interact among themselves. The iSCSI protocol requires the SCSI commands to be
transmitted over a network, normally TCP/IP (Gode et al., 2014). The sub-sections that follow
discuss the architecture problems and choices that DSI can make during the development of an
initiator and aim for OSD.
The initiator library of OSDS exports the code to connect with the OSD aim used by
the client applications. The OSD aim is responsible for handling iSCSI sessions, receiving
requests from the initiators, accessing or generating objects, and possibly establishing and
retrieving attributes, and eventually returning an appropriate response.
Use of Cloud Edge for OSDS
Cloud Edge is the new generation mobile broadband solution that is based on the Service-
Oriented Architecture, Network Functions Virtualization and cloud architecture developed. The
Cloud Edge framework optimizes and improves the supporting application functionality to offer
cloud-based advantages like automated installation and elastic scaling, to satisfy availability,
efficiency and other specifications for carrier-grade applications (Wang et al., 2017). Inevitable
development of cloud-based applications is edge computing. If the field of technology continues
to evolve, the IoT scope will also develop, with most electronics and computer-driven devices
eventually communicating. Moreover, the vast volume of empty computer power that remains
unused will be exploited for usage, generating thousands of times bigger storage system than the

6BUSINESS REQUIREMENTS REPORT
one actually in operation. Therefore, the organization DSI can chose the Cloud Edge
infrastructure for OSDS.
Advantages of Cloud Edge
 Speed: By bringing the data collection devices and software closer to the real source of
the data, decreasing the physical distance, the data of the organization will migrate and
the time taken to transfer, edge computing significantly decreases the inactivity or latency
times, thereby improving the overall service’s sensitivity, pace and efficiency (Chang et
al., 2014).
 Reliable and uninterrupted connection: Edge computing offers the local microdata
centers for the data collection and retrieval. As a result, the organization may rely on
stable networking for their IoT (Internet of Things) applications, even though it involves
cloud resources (Georgakopoulos et al., 2016). Additionally, edge computing helps IoT
devices to use less capacity and to run normally with restricted access, minimizing issues
regarding knowledge and data leakage in industries.
 Low cost: The organisation will be able to minimize their costs by growing the necessary
capacity, replacing data centers with decentralized system systems, and growing data
storage demands, contributing to lower prices for IoT products and applications.
Disadvantages of Cloud Edge
There are multiple disadvantages or drawbacks, where there are benefits and edge
computing is no difference. The following drawbacks for edge computing should be known to
the organization:

7BUSINESS REQUIREMENTS REPORT
 Edge computing collects and analyzes only the subset of data by discarding the raw and
unfinished knowledge (Satria, Park & Jo, 2017). Organizations will determine which
extent of the lack of knowledge is appropriate.
 Edge computing will raise vectors for attacks. The possibilities for malicious hackers or
attacks to penetrate the networks and access confidential data have improved with the
introduction of IoT, network-connected machines, and built-in computers (Kozik et al.,
2017).
 Edge computing for more local hardware is needed. IoT devices, for example, need an
embedded device to transmit video data across the internet and a more complex
processing method for more specialized software implementations, such as motion
tracking or facial recognition.
Differences between monolithic & MicroService Architectures
Monolithic Architecture Applications have generally been designed on a monolithic design, a paradigm in which
all components within a framework are integrated into a single, self-contained structure.
All functionality occurs inside the single codebase, indicating that the whole program is
implemented concurrently, and that scaling is accomplished by inserting additional nodes
(Namiot & Sneps-Sneppe, 2014).
 Makes prototypes larger and larger and is impossible to handle because, if the
specification becomes too massive, it requires a long time to launch.
 Continuous implementation is challenging, because a minor modification in the code to a
part involves redeployment of the whole program.

8BUSINESS REQUIREMENTS REPORT
 Application scaling involves complete framework scaling that is launching several
instances of the wide monolithic program to meet the need, but only a limited portion of
the framework is resource-intensive (Fan & Ma, 2017). Monolithic is ideal because the program itself is very small, and has few logic and
modules in it. In the monolithic application, modules may deal with each other and communicate
to each other easily by utilizing internal language processes or calling the different
process as it is part of the single framework.
MicroService Architecture
 The concept is to break the framework into a collection of smaller, integrated programs
rather than the single monolithic program. Increasing MicroService is the small program
that has its own hexagonal architecture is included with the business logic with multiple
different adapters (Villamizar et al., 2016).
 The scale should stay considerably smaller, as each portion is dissected into smaller
facilities.
 Continued delivery here is feasible, because each infrastructure may be delivered
individually.
 Microservice-based design is ideally adapted if the program is very large, complicated,
and is doing a number of things.
 Single component scaling is important here, since every specific component is de-
coupled to various systems, and can be distributed horizontally and independently (Singh
& Peddoju, 2017).

9BUSINESS REQUIREMENTS REPORT
 In reality, microservice-based architecture isn’t recent. While the theory behind UNIX
architecture remains just the same. While the usage of microservice-based design has
certain benefits, it is not a solution to the application creation and delivery problems.
 In the case of microservice-based design, developers would have to cope with reasoning
for service-to-service intercommunication, and even manage vulnerabilities between
them.
Evaluation of Software Architectures
Fig: Difference
between Monolithic and MicroService architecture (Source: Villamizar et al., 2015)
Benefits of Monolithic Architecture
 Simple in developing any program
 It is very simple for testing any program. For instance, anyone can enable end-to-end
verification, by merely launching the program and checking the UI with the Selenium.
 Monolithic is very simple in deploying (Villamizar et al., 2015). Only copy the bundled
code into a folder.

10BUSINESS REQUIREMENTS REPORT
 It is easy in scaling horizontally, with several copies operating behind the load balancer.
Disadvantages of Monolithic Architecture
 The basic solution has complexity and limitation in size.
 Technology is too large and complicated to easily and accurately comprehend and create
improvements (Kazanavičius & Mažeika, 2019).
 The application size will slow down startup time.
 Upon every upgrade the organization will need to redeploy the whole program.
 This is challenging to continuous launch.
Advantages of MicroService Architecture
 This addresses the complexity issue by breaking down framework into a series of
accessible resources that are much simpler to create, and much easier to learn and sustain.
 It allows for the autonomous production of each project by a team that is based on that
business (Villamizar et al., 2015).
 It removes obstacles to the introduction of emerging technology because developers are
able to select which innovations make sense for their business and are not constrained by
the choices made at the project startup.
Disadvantages of MicroService Architecture
 Microservices design adds value to the project simply by rendering a distributed device a
microservices program (Singh & Peddoju, 2017). The organization will need to pick and
enforce an inter-process coordination system focused on messaging, and write code for
managing partial failure and taking other distributed computing errors into account.

11BUSINESS REQUIREMENTS REPORT
In certain cases the safest alternative is a monolithic program. For instance, if any
application is small, implementing the distributed architecture such as MicroService, before it
is required will result in an unnecessarily complicated application and increased overhead
(Villamizar et al., 2016). Companies contemplating creating a mobile device from scratch or
designing proof of concept will even take benefit of accepting the monolith. Although it may
sound counterintuitive, tiny monoliths are an uncomplicated and cost-effective alternative. These
are easy in understanding and quick to model, check and disable.
Recommended Approach
 Based on the study, usage of cloud infrastructure as data storage medium can be advised.
OSDS infrastructure provides an innovative approach. Data on data reveals the value of
computer collection; system repair and backup computer on existing maturity level
and on data protection priority stage (Pardeshi, 2014). OSDS deployment makes
comprehensive data management feasible with easy capital infrastructure. This is
consistent with the cloud infrastructure that handles the resource in a clear way and
through maintenance effort.
 Implementation in cloud services allows network management expenses to be minimized.
Meanwhile, the sensitive data is vulnerable, and a cloud data management analysis is
required. Recommendation is rendered from low significance results. It is presumed that
the data is of low level of entry.
 The organization must specifically define the files, processing activities or resources that
might be storing in cloud platform when preparing to utilize Cloud computing.

12BUSINESS REQUIREMENTS REPORT
 The move to cloud needs a robust technologically and legally safe strategy. By
comparison to traditional outsourcing offerings, in which the service providers have
the perfect solution to a customer-defined request, many cloud service deals are
normal for all customers and do not follow that requirements.
 This is necessary for businesses to carry out a thorough risk analysis in order to be able to
identify acceptable compliance precautions to be requested from the service provider or
to be placed in effect inside the business (Kwon & Tilevich, 2014). The cloud approach is
important as a form of risk analysis such that personal data are regarded as properties to
be covered and that the data subjects impacts on privacy, which are taken into account.
Therefore, DSI must conduct a full analysis of the platform or the service before
migrating.
 The organization DSI must ensure they can meet their commitments in the platform of
cloud. In order to do so, they will select service providers who guarantee the setting up of
adequate protection and confidentiality mechanisms and who are open to their consumers
on the methods used to deliver their services as well as transfer of data overseas, use of
subcontractors, security policies and controls.
Conclusion
In conclusion, this can be said that when IoT is more common, so should edge computing
do the same. The ability to examine data closer to the source would decrease latency, lower
internet load, improve privacy and protect as well as reduce the data processing costs. The
adoption of cloud based OSDS will begin to play a vital role in aggregating essential details and
performing research on this vast collection of knowledge to extract perspectives that can be

13BUSINESS REQUIREMENTS REPORT
transmitted out to the edge users. The integration of edge and cloud infrastructure will help you
handle and interpret the data efficiently, and increasing the IoT efforts dramatically. The purpose
of this study was to discuss the migration of the OSDS to the cloud to resolve protection
vulnerabilities and solutions. This can be found from this study that a great deal of work has been
undertaken to ensure the protection of the single cloud as well as cloud storage although less
attention has been given to multi-domain protection. The organization DSI must go with the
migration to the cloud-based OSDS because the new platform will have the potential to reduce
security threats impacting cloud computing users.

14BUSINESS REQUIREMENTS REPORT
References
Amaral, L. A., Tiburski, R. T., de Matos, E., & Hessel, F. (2015, April). Cooperative middleware
platform as a service for internet of things applications. In Proceedings of the 30th
Annual ACM Symposium on Applied Computing (pp. 488-493).
Androcec, D., Vrcek, N., & Küngas, P. (2015, June). Service-level interoperability issues of
platform as a service. In 2015 IEEE World Congress on Services (pp. 349-356). IEEE.
Chang, H., Hari, A., Mukherjee, S., & Lakshman, T. V. (2014, April). Bringing the cloud to the
edge. In 2014 IEEE Conference on Computer Communications Workshops (INFOCOM
WKSHPS) (pp. 346-351). IEEE.
Fan, C. Y., & Ma, S. P. (2017, June). Migrating monolithic mobile application to microservice
architecture: An experiment report. In 2017 IEEE International Conference on AI &
Mobile Services (AIMS) (pp. 109-112). IEEE.
Georgakopoulos, D., Jayaraman, P. P., Fazia, M., Villari, M., & Ranjan, R. (2016). Internet of
Things and edge cloud computing roadmap for manufacturing. IEEE Cloud
Computing, 3(4), 66-73.
Gode, N., Kashalkar, R., Kale, D., & Bhingarkar, S. (2014). Feature-based Comparison of iSCSI
Target Implementations. International Journal of Computer Applications, 85(16), 13-16.

15BUSINESS REQUIREMENTS REPORT
Karakoyunlu, C., Runde, M. T., & Chandy, J. A. (2014, September). Using an object-based
active storage framework to improve parallel storage systems. In 2014 43rd International
Conference on Parallel Processing Workshops (pp. 70-78). IEEE.
Kazanavičius, J., & Mažeika, D. (2019, April). Migrating legacy software to microservices
architecture. In 2019 Open Conference of Electrical, Electronic and Information Sciences
(eStream) (pp. 1-5). IEEE.
Kolb, S., & Wirtz, G. (2014, April). Towards application portability in platform as a service.
In 2014 IEEE 8th International Symposium on Service Oriented System Engineering (pp.
218-229). IEEE.
Kozik, R., Choraś, M., Ficco, M., & Palmieri, F. (2018). A scalable distributed machine learning
approach for attack detection in edge computing environments. Journal of Parallel and
Distributed Computing, 119, 18-26.
Kwon, Y. W., & Tilevich, E. (2014). Cloud refactoring: automated transitioning to cloud-based
services. Automated Software Engineering, 21(3), 345-372.
Namiot, D., & Sneps-Sneppe, M. (2014). On micro-services architecture. International Journal
of Open Information Technologies, 2(9), 24-27.
Noel, R. R., & Lama, P. (2017, June). Taming performance hotspots in cloud storage with
dynamic load redistribution. In 2017 IEEE 10th International Conference on Cloud
Computing (CLOUD) (pp. 42-49). IEEE.

16BUSINESS REQUIREMENTS REPORT
Pardeshi, V. H. (2014). Cloud computing for higher education institutes: architecture, strategy
and recommendations for effective adaptation. Procedia Economics and Finance, 11,
589-599.
Satria, D., Park, D., & Jo, M. (2017). Recovery for overloaded mobile edge computing. Future
Generation Computer Systems, 70, 138-147.
Singh, V., & Peddoju, S. K. (2017, May). Container-based microservice architecture for cloud
applications. In 2017 International Conference on Computing, Communication and
Automation (ICCCA) (pp. 847-852). IEEE.
Villamizar, M., Garcés, O., Castro, H., Verano, M., Salamanca, L., Casallas, R., & Gil, S. (2015,
September). Evaluating the monolithic and the microservice architecture pattern to
deploy web applications in the cloud. In 2015 10th Computing Colombian Conference
(10CCC) (pp. 583-590). IEEE.
Villamizar, M., Garces, O., Ochoa, L., Castro, H., Salamanca, L., Verano, M., ... & Lang, M.
(2016, May). Infrastructure cost comparison of running web applications in the cloud
using AWS lambda and monolithic and microservice architectures. In 2016 16th
IEEE/ACM International Symposium on Cluster, Cloud and Grid Computing
(CCGrid) (pp. 179-182). IEEE.
Wang, X., Yang, L. T., Xie, X., Jin, J., & Deen, M. J. (2017). A cloud-edge computing
framework for cyber-physical-social services. IEEE Communications Magazine, 55(11),
80-85.

17BUSINESS REQUIREMENTS REPORT
Yangui, S., Ravindran, P., Bibani, O., Glitho, R. H., Hadj-Alouane, N. B., Morrow, M. J., &
Polakos, P. A. (2016, June). A platform as-a-service for hybrid cloud/fog environments.
In 2016 IEEE International Symposium on Local and Metropolitan Area Networks
(LANMAN) (pp. 1-7). IEEE.