Data Design and System

Architecture
Topic 7
 NETWORK MODELS DATA DESIGN CONCEPT

CLIENT/SERVER & E-COMMERCE

OUTLINE WEB-BASED DESIGN
ARCHITECTURE

ARCHITECTURE CHECKLIST DATA DESIGN TERMS

Data Design
 Data Structure

• A data structure is a framework for

organizing, storing, and managing data.
• Data structures consist of files or tables
that interact in various ways.
• Each file or table contains data about
people, places, things, or events.
• Over time, the modern relational
database became a standard model for
systems developers.
 Database Management
Systems

• A database management system (DBMS) is a collection of tools,

features, and interfaces that enables users to add, update, manage,
access, and analyze data.
• In addition to interfaces for users, DBAs, and related systems, a
DBMS also has a data manipulation language, a schema and
subschemas, and a physical data repository.
• The complete definition of a database, including descriptions of all
fields, tables, and relationships, is called a schema.
• A subschema is a view of the database used by one or more systems
or users. A subschema defines only those portions of the database
that a particular system or user needs or is allowed to access.
• To resolve potential database connectivity and access problems,
companies use ODBC-compliant software that enables
communication among various systems and DBMSs.
• Open database connectivity (ODBC) is an industry-standard
protocol that makes it possible for software from different
vendors to interact and exchange data.
 Web Design
• Web-based systems are popular
because they offer ease of access,
cost-effectiveness, and worldwide
connectivity—all of which are vital to
companies that must compete in a
global economy.
• To access data in a web-based system,
the database must be connected to
the Internet or intranet.
• The database and the Internet speak
two different languages, however.
• To bridge the gap, it is necessary to
use middleware, which is a software
that
• Integrates different applications and
allows them to exchange data.
Middleware can interpret client
requests in HTML form and translate
the requests into commands that the
database can execute.
 Data Design Term

Entity Table/File

Field Record

Key Fields
System Architecture
 Architecture Checklist
• System architecture translates the logical design of an information system into a physical
structure that includes hardware, software, network support, processing methods, and
security.
• The end product of the systems design phase is the system design specification.
• A systems analyst must consider several issues that will affect the architecture choice.
This is done with an overall architecture checklist:
• Corporate organization and culture
• Enterprise resource planning (ERP)
• Initial and total cost of ownership (TCO)
• Scalability
• Web integration
• Legacy system interface requirements
• Processing options
• Security issues
• Corporate portals
 Architecture Checklist
1. Corporate Organization and Culture
• To be successful, an information system must perform well in a company’s organization and
culture.
• How might corporate organization and culture issues affect the consultant’s recommendation?.
The best approach probably would be to study day-to-day business functions, talk to users at all
levels, and focus on operational feasibility issues, just as was done earlier in the development
process.

2. Enterprise Resource Planning (ERP)

• Many companies use enterprise resource planning (ERP) software to establish a company-wide
strategy for using IT that includes a specific architecture, standards for data, processing, network,
and user interface design
• Many companies are extending internal ERP systems to their suppliers and customers, using a
concept called supply chain management (SCM)

3. Initial Cost and TCO

• TCO includes tangible purchases, fees, and contracts called hard costs. However, additional soft
costs of management, support, training, and downtime are just as important but more difficult to
measure.
 Architecture Checklist
4. Scalability
• Scalability, sometimes also called extensibility, refers to a system’s ability to expand, change, or
downsize to meet the changing needs of a business enterprise.
• A scalable system is necessary to support a dynamic, growing business.

5. Web Integration
• An information system includes applications, which are programs that handle the input, manage
the processing logic, and provide the required output
• A web-centric architecture follows Internet design protocols and enables a company to integrate
the new application into its e-commerce strategy

6. Legacy Systems
• A new system might have to interface with one or more legacy systems, which are older systems
that use outdated technology but still are functional.
• Interfacing a new system with a legacy system involves analysis of data formats and compatibility
• Finally, to select the best architecture, the analyst must know if the new application eventually will
replace the legacy system or will coexist with it.
 Architecture Checklist
7. Processing Options
• In planning the architecture, designers also must consider how the system will process data:
online or in batches.
• If the system must operate online, 24 hours a day and seven days a week (24/7), provision must
be made for backup and speedy recovery in the event of system failure
8. Security Issues
• From the simple password protection to complex intrusion detection systems, security threats and
defenses are a major concern to a systems analyst.
• As the physical design is translated into specific hardware and software, the analyst must consider
security issues and determine how the company will address them
• Web-based systems introduce additional security concerns, as critical data must be protected in
the Internet environment
9. Corporate Portals
• A portal is an entrance to a multifunction website. After entering a portal, a user can navigate to a
destination using various tools and features provided by the portal designer.
• A corporate portal can provide access for customers, employees, suppliers, and the public. A
well-designed portal can integrate with various other systems and provide a consistent look and
feel across multiple organizational divisions.
 Client/Server Architecutre

• Whether it’s a departmental network or a

multinational corporation, a systems analyst
works with a distributed computing strategy
called client/server architecture.
• In a typical client/server system, the client
handles the entire user interface, including
data entry, data query, and screen
presentation logic. The server stores the data
and provides data access and database
management functions. Application logic is
divided in some manner between the server
and the clients. Cloud computing is seen by some observers as an entirely new
concept. Others see it as the ultimate form of client/server
architecture, where Internet-based computing becomes the
server part of client/server and handles processing tasks, while
the Internet itself becomes the platform that replaces
traditional networks.
 Client/Server Architecture
Client/Server Tiers
• In a two-tier design, the user interface resides on the
client, all data resides on the server, and the
application logic can run either on the server or on the
client or be divided between the client and the server.
• In a three-tier design, the user interface runs on the
client and the data is stored on the server, just as with
a two-tier design. A three-tier design also has a
middle layer between the client and server that
processes the client requests and translates them into
data access commands that can be understood and
carried out by the server.
• The middle layer can be considered an
application server, because it provides the
application logic, or business logic, required by
the system.
• Three-tier designs also are called n-tier designs,
to indicate that some designs use more than one
intermediate layer.
 E-Commerce Architecture

When planning an e-commerce architecture, analysts can examine in-house development, packaged
solutions, and service providers.
1. In-House Solutions
• An in-house solution usually requires a greater initial investment but provides more flexibility for
a company that must adapt quickly in a dynamic e-commerce environment.
• By working in-house, a company has more freedom to integrate with customers and suppliers and
is less dependent on vendor-specific solutions.
2. Packaged Solutions
• If a small company is reluctant to take on the challenge and complexity of developing an Internet
commerce site in-house, an alternative can be a packaged solution.
• For large-scale systems that must integrate with existing applications, packaged solutions might
be less attractive.
3. Service Provides
• Another alternative is to use an application service provider (ASP). An ASP provides applications,
or access to applications, by charging a usage or subscription fee.
Networks Models
Networks Models
Networks Models