Mattu University

College Of Business And Economics

Department Of Management Information System
Group Assignment for Decision Support System

Name Id Number

1 WENDM KASSA 4331

2 ESHETU NIGUSE 6888

3 SEYFADIN UMER 4070

4 GEMECHIFTU FIKADU 4029

5 OBANG OGULIA 1903

 Table content

Introduction ………………………………………………………………………………………………………………………………….2

1 Defining the DSS Architecture 3

1.1 components of DSS architecture.......................................................................................................5

2 DSS on the central corporate system.................................................................................................7
2.1 Advantages of DSS in the central corporate system........................................................................8
2.2 Disadvantages of DSS in the central corporate system:...................................................................8
3 DSS and client/ server computing.......................................................................................................9
3.1 Client/Server Functions...............................................................................................................11
3.2 Client/Server Topologies..................................................................................................................12
3.3 CLIENTS/SERVER—ADVANTAGES AND DISADVANTAGES...............................................13
Conculusion...........................................................................................................................................14

Reference...............................................................................................................................................15

1
 INTRODUCTION

Decision Support Systems (DSS) are designed to help users make informed decisions by
analyzing and modeling data. The architecture of a DSS typically involves a centralized corporate
system where data is stored and processed. This centralized system allows for efficient data
management and analysis, as well as providing a single source of truth for decision-making.

In the context of client/server computing, DSS can be accessed and utilized by users from their
own devices, such as desktop computers or mobile devices. This is made possible by the
client/server architecture, where the DSS software and data are hosted on a centralized server,
and users can access and interact with the system through client applications on their devices.
This architecture allows for remote access to the DSS, as well as scalability and easier
maintenance of the system.

Overall, the combination of DSS and client/server computing provides organizations with a
powerful tool for decision-making, allowing users to access and analyze data from a centralized
system, while still benefiting from the flexibility and accessibility of client/server computing.

Information technology (IT) architectures and computing infrastructures are evolving rapidly in
corporations. In some companies, the IT infrastructure is being built in an uncoordinated,
opportunistic manner. This approach is understandable given the rapid pace of technological
change, but companies need much more than a “Web server here and a router there” approach
to IT architecture and networking.

2
 1 Defining the DSS Architecture
A DSS architecture includes the IS/IT architecture components relevant to the DSS. A DSS may
be a subsystem of a larger information system and a specific DSS may have multiple types of
decision support subsystems. Having a well-defined and well-communicated DSS architecture
provides an organization with significant benefits. An architecture document helps developers
work together, improves planning, increases the development team’s ability to communicate
system concepts to management, increases the team’s ability to communicate needs to
potential vendors, and increases the ability of other groups to implement systems that must
work with the DSS. Technical benefits of a DSS architecture document include the ability to plan
systems in an effective and coordinated fashion and to evaluate technology options within the
context of how they will work rather than from a more abstract perspective. A DSS vision and an
architecture document help communicate the future, and provide a consistent goal for making
individual design decisions. Achieving all these benefits requires that both information system
professionals and prospective DSS users cooperate closely in developing the architecture.

a DSS architecture should define and specify the following components:

1. Database or databases, including any existing databases, internal or external to the

organization and any databases that are created specifically for DSS use. The architecture
schematic should identify who is responsible for different types of databases, including their
accuracy, currency, and security.

2. Model or models, including information about their sources of data, processing, the
organizational unit responsibility for maintaining them, and limits on access to them.

3. Software tools for users to access the database and the models, and software tools which
system administrators can use to manage the database and the models.

4. Hardware and operating system platforms on which the databases and models reside, on
which the programs run, and through which users access the DSS. Any constraints, such as a

3
policy to standardize on products of a particular vendor or products that use a particular
operating system, should be stated.

5. Networking and communication capabilities needed to connect the hardware platforms.

These capabilities must support needs to connect to one or more servers and databases, needs
of work group members to communicate within the group, and enterprise needs to link work
groups to each other or to shared data. In many DSS situations the corporate network is used. In
this case the network must be examined to make sure it meets present and future Decision
Support traffic needs.

1.1 components of DSS architecture

There are four fundamental components of DSS architecture:

 User Interface

 Database

 Model (context or situation representation)

 Knowledge
 User Interface

we learnt what it takes to design and build an effective user interface design. Since it’s a
full-fledged subject of study, we looked at the prerequisites of a good user interface
design, concerns pertaining to dialogue development, flexibility, mode of feeding
information, interface design rules and factors influencing the success of a user interface
design.

 The Database

Next, comes the database. It serves as the storehouse of information. It contains:

i. Personal/internal information – details collected from within the organization, from

employees, customers. It may include ideas, your own thoughts, experiences and
insights.

4
 ii. External information – information collected from outside sources, like independent
researches, internet, government organizations, etc.

A DSS accesses information directly from the database, depending upon your needs and
type of decision you are making. A decision support system architecture scheme focuses on

i. Type of database required for a particular decision making system model

ii. Who’s responsible for different types of databases

iii. How to maintain accuracy and security of database

 Model
This component of DSS architecture takes care of:
i. DSS model and
ii. DSS model management system
While a model is a representation of context, a situation or an event, a DSS model
management system stores and maintains DSS models.
A model makes an important component of DSS architecture because it allows you to
carry out a particular type of data analysis that you need for a particular kind of decision-
making. For example, you need to understand what happens if you change a particular
variable. A spreadsheet-based model will help you conduct what-if analysis.
A model management system just stores and manages DSS models. But it doesn’t help you
decide the best model for a decision type. Decision makers can use their expertise to
decide the model for resolving a particular model.
 Knowledge

This element of DSS architecture provides information about the relationship among data,
which is too complex. It manages the knowledge and provides decision makers with alternative
solutions of a problem. It also sends signals to decision makers when there is any mismatch
between forecasted and actual results.

A well defined DSS architecture scheme address:

 A problem definition that a DSS is expected to resolve

5
  The objectives of a DSS
 Components of a DSS and connection between them
 Development and maintenance schedule
 Skills, tools, funds and other support required for DSS development
 Anticipated enhancements
 Project participants and their roles

Image for decision support system Arichitecture

2 DSS on the central corporate system

DSS (Decision Support System) on the central corporate system refers to the use of technology
and software to provide executives and managers with the information and tools they need to
make informed decisions. This can include data analysis, forecasting, and modeling to support
strategic planning and decision-making at the corporate level. DSS on the central corporate
system can help organizations improve efficiency, reduce risk, and drive better business
outcomes by providing access to real-time data and insights. It can also integrate with other
systems and processes to streamline decision-making across the organization.

6
The role of DSS in the central corporate system is to provide executives and managers with the
necessary information and tools to make informed decisions. This includes data analysis,
forecasting, and modeling to support strategic planning and decision-making at the corporate
level. DSS helps organizations improve efficiency, reduce risk, and drive better business
outcomes by providing access to real-time data and insights. Additionally, it can integrate with
other systems and processes to streamline decision-making across the organization. Overall, the
role of DSS in the central corporate system is to support and enhance decision-making
processes for the organization as a whole.

2.1 Advantages of DSS in the central corporate system

1.Improved decision-making: DSS provides executives and managers with the

necessary information and tools to make informed decisions, leading to better
strategic planning and business outcomes.
2. Real-time data access: DSS allows for access to real-time data and insights,
enabling quick and informed decision-making.

3. Integration with other systems: DSS can integrate with other systems and
processes, streamlining decision-making across the organization and improving
efficiency.

4. Risk reduction: DSS helps in reducing risk by providing accurate and reliable
data for decision-making, leading to more informed and calculated decisions.

5. Enhanced strategic planning: DSS supports strategic planning by providing data

analysis, forecasting, and modeling to support long-term planning and decision-
making.

7
 2.2 Disadvantages of DSS in the central corporate system:

1. Cost: Implementing and maintaining a DSS can be expensive, including the cost of
software, hardware, training, and ongoing support.

2. Complexity: DSS can be complex to implement and use, requiring specialized knowledge
and skills to operate effectively.

3. Data security concerns: With the integration of various systems and access to real-time
data, there may be concerns about data security and privacy.

4. Overreliance on technology: There is a risk of overreliance on DSS, leading to a decrease

in critical thinking and decision-making skills among executives and managers.

5. Resistance to change: Some employees may resist the implementation of DSS, leading
to challenges in adoption and usage within the organization

An example of a DSS in a central corporate system could be a business intelligence

platform that integrates data from various sources within the organization, such as sales,
marketing, finance, and operations. The DSS architecture would include the hardware
infrastructure to support the data storage and processing, the software for data analysis
and reporting, the databases to store the integrated data, and the user interface for
accessing and interacting with the DSS. Additionally, it may include modules for predictive
analytics, data visualization, and ad-hoc querying to support different types of decision-
making processes within the organization. The architecture would be designed to ensure
that the DSS can handle large volumes of data, provide real-time insights, and support a
variety of decision-making needs across different departments and levels of the
organization.

3 DSS and client/ server computing

Client/server computing is a model in which a client (such as a user's computer) requests
services or resources from a server (such as a central corporate system). In the context of
8
 DSS, client/server computing allows users to access and interact with the DSS from their
own devices, such as desktop computers, laptops, or mobile devices. The DSS software
and data are hosted on the central server, while the client devices connect to the server to
retrieve and process the data, run analyses, and generate reports.

What is the client?

The client is a process (program) that sends a message to a server process, requesting that
the server perform a task (services).

What is the server?

A server process fulfills the client request by performing the task required. server
programs receive requests from client programs execute database retrieval and updates
and dispatch responses to client requests.

This client/server architecture enables users to access the DSS remotely, from different
locations and devices, while still benefiting from the centralized data storage and
processing capabilities of the central corporate system. It also allows for easier scalability and
maintenance of the DSS, as updates and changes can be made on the central server and
propagated to all connected client devices.

Overall, the combination of DSS and client/server computing provides a flexible and
efficient way for organizations to leverage their central corporate system for decision-
making processes across different departments and locations.

Client/Server computing is new technology that yields solutions to many data

management problems faced by modern organizations. The term Client/Server is used to
describe a computing model for the development of computerized systems. This model is
based on distribution of functions between two types of independent and autonomous
processes: Server and Client. A Client is any process that requests specific services from
the server process. A Server is a process that provides requested services for the Client.
Client and Server processes can reside in same computer or in different computers linked
by a network.

9
When Client and Server processes reside on two or more independent computers on a
network, the Server can provide services for more than one Client. In addition, a client can
request services from several servers on the network without regard to the location or the
physical characteristics of the computer in which the Server process resides. The network
ties the server and client together, providing the medium through which the clients and
the server communicate. The Fig. 1.1 given below shows a basic Client/Server computing
model

From the Fig. 1.1 it is clear that services can be provided by variety of computers in the
network. The key point to Client/Server power is where the request processing takes
place. For example: Client/Server Database. In case of Client/Server database system,
the functionality is split between the server system and multiple clients such that
networking of computers allows some tasks to be executed on the client system.

3.1 Client/Server Functions

The main operations of the client system are listed below:

• Managing the user interface.

• Accepts and checks the syntax of user inputs.

• Processes application logic.

• Generates database request and transmits to server.

• Passes response back to server. The main operations of the server are listed below:

• Accepts and processes database requests from client.

10
• Checks authorization.

• Ensures that integrity constraints are not violated.

• Performs query/update processing and transmits responses to client.

• Maintains system catalogue.

• Provide concurrent database access.

• Provides recovery control.

3.2 Client/Server Topologies

A Client/Server topology refers to the physical layout of the Client/Server network in
which all the clients and servers are connected to each other. This includes all the
workstations (clients) and the servers. The possible Client/Server topological design and
strategies used are as follows:

(i) Single client, single server

(ii) Multiple clients, single server

(iii) Multiple clients, multiple servers

(i) Single client, single server: This topology is shown in the Fig. 1.2 given
below. In this topology, one client is directly connected to one
server.

ii) Multiple clients, single server: This topology is shown in the Fig. 1.3 given
below. In this topology, several clients are directly connected to only one
server.

11
(ii) Multiple clients, multiple servers: This topology is shown in the following
Fig. 1.4 In this topology several clients are connected to several servers.

The main difference between Decision Support Systems (DSS) and

client/server computing is that DSS refers to a specific type of
software or system that helps users make decisions based on data
analysis and modeling, while client/server computing is a broader
architectural model for organizing and accessing software and data.

However, there are also similarities between DSS and client/server

computing. Both involve the use of centralized servers to host
software and data, allowing users to access and interact with the
system from their own devices. This centralized architecture provides
benefits such as remote access, scalability, and easier maintenance of

12
 the system. In the context of DSS, client/server computing allows
users to access and utilize the DSS software and data from their own
devices, while still benefiting from the centralized data storage and
processing capabilities of the serve

3.3 CLIENTS/SERVER—ADVANTAGES AND DISADVANTAGES

 Advantages
There are various advantages associated with Client/Server computing mode

(i) Performance and reduced workload

(ii) Workstation independence
(iii) System interoperability
(iv) Scalability
(v) Data integrity
(vi) Data accessibility (enhanced data sharing)
(vii) System administration (centralized management)
(viii) Integrated services
(ix) Sharing resources among diverse platforms
(x) Masked physical data access
(xi) Location independence of data processing
(xii) Reduced operating cost
(xiii) Communication costs are reduced
 Disadvantages

There are various disadvantages associated with the Client/Server computing mode

(i) Maintenance cost

(ii) Training cost
(iii) Hardware cost
(iv) Software cost
(v) Comp

13
 Conculusion

the architecture of a Decision Support System (DSS) on a centralized corporate system, combined with
client/server computing, provides organizations with an efficient and flexible tool for informed decision-
making. The centralized system allows for effective data management and analysis, while the
client/server architecture enables remote access, scalability, and easier maintenance of the DSS. This
combination empowers users to access and analyze data from a centralized system while still benefiting
from the flexibility and accessibility of client/server computing. Overall, this architecture enhances the
capabilities of DSS and contributes to better decision-making within organizations

A well-defined DSS architecture has many benefits. Developing a DSS should therefore include adequate
attention to the many important architecture issues

14
 Reference

 Google.com
 A Mallach, Efrem G (2000). Decision Support and Data Warehouse System: McGraw-Hill.
 O'Brien and M Marakas (2006) Management information system 7th edition
 Stair, Ralph M., and George W. Reynolds (1997). Principles of Information Systems: A Managerial
Approach: Cambridge.
 Martin, E. Wainwright, Daniel W. DeHayes, Jeffrey A. Hoffer, and William C. Perkins (1991).
Managing Information Technology: What Managers Need to Know : Macmillan, New York
 Deloitte & Touche. “Information Protection and Client Server.” 1993
 SYBASE. “The Road Map to Enterprise Client/Server Computing.” 19

15