Assignment Week 6

BUSINESS PROCESS DEVELOPMENT

Class Code: W24 BU1193-SCM G1

Prof: TONY BEJJANI

Team Members:
Anges Martin 202207143
Pardeep 202302938
Mohit Kumar 202303296
Gurpreet Singh 202302582

Due Date: Feb 16, 2024

Q1. Describe the differences between the three generations of enterprise systems – mainframe
architecture, client-server architecture, and service-oriented architecture.

Mainframe Architecture: The mainframe architecture is a computing platform in which all processing
and data storage occurs on a centralized, high-performance computer known as a mainframe. This
architecture was popular in the early days of computers, commencing in the 1950s, and is still used
today in a variety of sectors, particularly in large enterprises where reliability, security, and adaptability
are crucial.

 The mainframe design centralizes computer processes including data processing, application
execution, and user interactions, resulting in effective resource usage and administration.
 Mainframes are ideal for mission-critical applications such as banking and airline reservation
systems due to their high availability and stability, resulting in little downtime.
 Mainframes are optimized for batch processing, which includes systematically processing huge
amounts of data at regular intervals. This is typically utilized for processes such as payroll, billing,
and financial transactions.
 Mainframes are highly scalable systems that can handle large workloads and expand needs
without sacrificing performance by increasing processing power, memory, and storage.
 Mainframe applications are huge, integrated systems that can handle several jobs and serve
multiple users concurrently.

Client-Server Architecture: Client-server architecture is a computing approach in which tasks are

distributed across two types of specialized computers: clients and servers. This design first appeared in
the 1980s and became popular in the 1990s, with the advent of personal computers and local area
networks (LANs).

 Client-server architecture distributes computing tasks across client devices (often desktop or
laptop computers) and server equipment (dedicated or virtual servers). This decentralization
allows for more efficient resource use and scalability.
 Client-side software allows users to request services and resources from servers, communicate
with users, show data, and do local processing.
 The server-side software handles client-requested resources, processes data, and provides
access to shared resources. It might be customized hardware or virtual machines operating on
high-performance PCs or cloud infrastructure.
  Standard networking protocols provide data and instruction exchange between clients and
servers across networks, including LANs and the Internet.
 The client-server architecture enables more scalable and adaptable solutions than mainframes.
Resources can be added and withdrawn more simply.

Service-Oriented Architecture (SOA): Service-Oriented Architecture (SOA) is a software architecture

technique that divides systems into loosely linked, accessible services. These services are separate units
of functionality that may be accessed and utilized independently inside and between systems. SOA
encourages the creation of modular, reusable components that may be constructed and coordinated to
facilitate complicated business operations.

 SOA arranges applications as interoperable, modular services. Each service represents a separate
unit of functionality that can be accessed and used independently across various systems,
increasing flexibility, maintainability, and reusability.
 SOA promotes interoperability by allowing smooth communication and interaction across
services, independent of technology, platform, or programming language, leading to integration
and cooperation across organizational boundaries.
 SOA offers dynamic service discovery and composition, allowing consumers to access services
through registries or directories and integrate them into business applications or workflows.

In summary, mainframe design prioritizes centralized processing and high availability, client-server
architecture decentralizes computing processes and encourages scalability, and service-oriented
architecture stresses modular, interoperable services for more flexibility and integration. Each generation
illustrates an evolution in corporate computing, fueled by technological developments and shifting
business requirements.

Q2. Explain the functions of the different systems in an application suite. How are they related?

Mainframe Architecture

In mainframe architecture, the computing power is on the mainframe and can serve multiple users or
clients at one time.

Functions:
Processing Is Centralized: The mainframe system takes care of everything, including data processing,
storage, and application execution.

Scalability: Mainframes can handle very fresh data very quickly, making them suitable for business-class
applications.

Reliable Operation: Mainframes offer a high level of availability fault tolerance through redundancy and
failure of component mechanisms.

Security: In mainframes, tight security is provided to keep sensitive data and resources safe from
unauthorized access.

Batch Processing: Mainframes do a splendid job of handling batch processing, meaning big blocks of
similar work are carried out together for good Results.

Client-Server Architecture

Client-server architecture represents a form of distributed system in which tasks are partitioned.

Functions:

Client Interface: In the case of client devices, it provides a user interface with which the software activity
can be controlled by the user and results displayed in the form to them.

Server Processing: The core business logic, data storage, and various processes are all hosted on servers.
They service requests from clients or deal with the data, producing results.

Scalability: Client-server architecture allows for scalable solutions by distributing processing tasks across
multiple servers and accommodating varying numbers of clients.

Flexibility: By using client-server models, applications gain in that each side has its own distinct set of
features and unique technical effects. With multiple kinds of devices possible on the internet, this provides
a simple window all around operation for program deployment from either side.

Interoperability: Client-server systems can support interoperability between different software

components, enabling seamless integration of diverse functionalities.

Service-Oriented Architecture (SOA)

SOA is an architectural approach where software components are designed as loosely coupled services
that communicate over a network using standardized protocols.

Functions:

Service Abstraction: SOA abstracts application functionalities into reusable services with well-defined
interfaces, promoting modular and interoperable software design.

Service Discovery: In an SOA environment, services can be discovered and accessed dynamically, making
it possible to flexibly compose and reconfigure component combinations while the software is running.

Scalability: Businesses can use flexible systems and Software as and when necessary, with this service-
oriented approach.

Service Identification: Finding discrete functions and turning them into services is an essential step
towards achieving business issues.

Interoperability: By standardizing data formats and communication protocols, SOA can promote
interoperability between systems of different make or type.

Relation between Architectures

These models are not mutually exclusive at all. You can use each one at the same time within a system.
Mainframe architecture may provide the back-end processing and the data storage facilities that client-
server or SOA components use. A client-server architecture may act as the front-end 'man-machine'
interface for service users in situations where a mainframe or SOA system provides services. Advertising
Here SOA principles can be applied to both mainframe and client-server systems for service-oriented
design. This is how to achieve interoperability across the suite.

Q3. What are the roles of organizational data, master data, and transaction data in an ES?

In an Enterprise System (ES), let's examine the functions of transaction, master, and organizational data.
1. Organizational Data:

Definition: The structural components of an organization are represented by organizational data.

Information on departments, divisions, manufacturing sites, storage facilities, and other organizational
units are all included.

Function:
Identification: The organizational hierarchy is identified by organizational data. It facilitates consumers'
understanding of the connections between various elements.
Context: By specifying the parameters that business processes function inside, it offers context for other
sorts of data.
Stability: Over time, organizational data rarely changes.
Examples include plant locations, business units, divisions, and warehouses.

2. Master Information
Definition: Stable core entities are referred to as master data. These organizations are necessary for
precise and reliable corporate operations.

Function:

Base: The cornerstone of an organization's data architecture is master data. It contains important data
such as personnel profiles, vendor records, product specifications, and consumer information.

Contextualization: Transactions are given structure and context by master data. It guarantees uniformity
amongst different systems. Integration is the process of connecting several applications and business
processes. Products, materials, vendors, workers, and customers are some examples.

3. Information on Transactions:

Definition: Transaction data records certain actions or jobs carried out by the organization. It depicts
how the business is really run.

Function: Transaction data is used to record various occurrences, including purchases, sales, invoices,
shipments, payments, and inventory movements.

Dynamic: Transaction data is subject to frequent changes as business processes progress, in contrast to
master data.

Execution: It represents how business operations are carried out. Sales orders, bills, production logs, and
inventory movements are a few examples.
To sum up, transaction data records business operations in real-time, master data offers context and
consistency, and organizational data establishes the structure. Together, these three data kinds allow an
ES to operate effectively and efficiently.
Q4. Provide two examples of organizational data, master data, and transaction data within the context
of your university or another organization you are familiar with.

Employee Records: Employee records, which comprise data like names, IDs, contact information, job
titles, departments, and salary information, are a subset of organizational data. Monitoring employee
performance, overseeing compliance with employment laws, and managing human resources all depend
on this data. Employee data is frequently kept in a central HR database that is only accessible by
authorized staff members in the company.

2. Asset Inventory - Asset inventory, which comprises details on the organization's tangible assets
including machinery, cars, and buildings, is another type of organizational data. Typically, this
information consists of asset IDs, descriptions, acquisition dates, maintenance records, depreciation
schedules, and current locations. Organizations may better track their resources, maximize asset use,
and make investment plans by managing asset inventory data.

3. Master Information

1. Course Catalog: In the context of a university, master data comprises the course catalog, which offers
detailed information on every course that the institution offers. Course codes, titles, descriptions, credit
hours, prerequisites, teachers, and scheduling information are all included in this data. The course
catalog helps students with their course selection and academic planning by acting as a primary source
of academic information.

2. Student Records: Student records, which include comprehensive information about each individual
student enrolled in the university, are another type of master data in an academic setting. Names, IDs,
contact details, academic program information, grades, transcripts, and enrollment status are all
included in this data. Academic advice, grading, degree audits, and upholding regulatory compliance in
education all depend on student records.

Library Checkouts - Another example of transaction data in a university is library checkouts, which
record the borrowing of library materials by students, faculty, and staff. This data includes transaction
timestamps, borrower IDs, item IDs, due dates, and return statuses. Managing library checkout data
helps libraries track circulation, monitor inventory, and provide access to resources for academic
research and learning.
 References

Chiradeep, B. (2023, January 2023) What Is a Mainframe.

https://www.spiceworks.com/tech/tech-101/articles/what-is-mainframe/

John, T. (2024) What is Client-Server Architecture. https://www.simplilearn.com/what-is-client-server-

architecturearticle#:~:text=Client%2Dserver%20architecture%2C%20alternatively%20called,linked%20by
%20a%20computer%20network.

Nick, B. and Tom, N. (2023) Service-oriented architecture (SOA).

https://www.techtarget.com/searchapparchitecture/definition/service-oriented-architecture-SOA

What is SOA? - SOA architecture explained - AWS. (n.d.).

https://aws.amazon.com/what-is/service-oriented-architecture/

Who uses mainframes and why do they do it? IBM. (n.d.).

https://www.ibm.com/docs/en/zos-basic-skills?topic=vmt-who-uses-mainframes-why-do- they-do-it

What is the client-server model? A comprehensive overview. MonoVM.com. (2023, August 17).
https://monovm.com/blog/what-is-client-server-model/

DataMC. (n.d.). Master, Transactional, and Reference Data. https://datamc.com/understanding-master-

transactional-reference-data/

Reference and Master Data Management - EWSolutions. (2017, May 16).

https://www.ewsolutions.com/reference-master-data-management/

Marini Systems. (n.d.). Difference between Master Data and Transactional Data https://marini.systems/en/help-
center/docs/what-is-the-difference-between-master-and-transaction-data/