SAD101 - Study Guide - Module 2
SAD101 - Study Guide - Module 2
0 10-July-2020
Study Guide in (SAD 101 – SYSTEM ANALYSIS AND DESIGN) Module No._2_
MODULE OVERVIEW
System analysis and design methods are used to develop information systems for
organizations. Before learning the process of building systems you need a clear understanding of
the product you are trying to build. This module takes an architectural look at information systems
and applications. We will build a framework for information systems architecture that will
subsequently be used to organize and relate all of the parts in this module.
Organizations are served not by a single information system but, instead, by a federation of
information systems that support various business functions. The idea is illustrated in the figure
below. Notice that most businesses have both front-office information systems that support
business functions that reach out to customers (or constituents) and back-office information
systems that support internal back-office business information systems that feed data to
management information systems and decision support systems that support management needs of
the business. Contemporary information systems are interfacing with customers and suppliers using
electronic commerce technology, customer relations management (CRM), and Supply Chain
Management (SCM) applications over the Internet. Finally, most companies have some sort of
intranet (internal to the business) to support communications between employees and the
information systems
Front–Office Information System – an information system that supports business functions that
extend out to the organization’s customers.
Study Guide in (SAD 101 – SYSTEM ANALYSIS AND DESIGN) Module No._2_
Back–Office Information System – an information system that supports the internal business
operations of an organization, as well as reaches out to suppliers.
In this module, there are several classes of information system applications. Each class
serves the needs of different types of users. These classes overlap such that it isn’t always easy to
differentiate one from another. The various applications should ideally interoperate to complement
and supplement one another. The figure below illustrates the typical roles of information systems.
Notice that an organization can and will have multiple transaction processing systems, office
automation systems, and the like. The “drum” shapes represent stored data. Notice that an
organization has multiple sets of stored data, and only some of them work together. The following
number annotations are on the diagram.
1 The first transaction processing system responds to an input transaction’s data (e.g., an order). It
produces transaction information to verify the correct processing of the input transaction.
2 The second transaction processing system merely produces an output transaction (e.g., an
invoice). Such a system may respond to something as simple as the passage of time (e.g., it is the
end of the month; therefore, it generates all invoices).
3 The first management information system simply produces reports or information (e.g., sales
analysis reports) using data stored in transactional databases (maintained by the aforementioned
transaction processing systems).
4 The second management information system uses business models (e.g., MRP) to produce
operational management Information (e.g., a production schedule).
5 Notice that an MIS may use data from more than one transactional database.
6 Notice that snapshots of data from the transactional databases populate a data warehouse. The
snapshots may be taken at various time intervals, and different subsets of data may be included in
various snapshots. The data in the warehouse will be organized to ensure easy access and inquiry
by the manager’s data (e.g., an order); it produces transaction information to verify the correct
processing of the input transaction.
7 Decision support and executive information systems applications will typically provide read-only
access to the data warehouses to produce decision support and executive management
information.
8 An expert system requires a special database that stores the expertise in the form of rules and
heuristics.
9 An expert system either accepts problems as inputs (e.g., Should we grant credit to a specific
customer?), or senses problems in the environment (e.g., Is the lathe producing parts within
acceptable specifications?) and then responds to a problem with an appropriate solution based on
the system's expertise.
10 Personal office automation systems tend to revolve around the data and business processing
needs of an individual. Such systems are typically developed by the users themselves (and run on
personal computers).
Study Guide in (SAD 101 – SYSTEM ANALYSIS AND DESIGN) Module No._2_
11 Workgroup office automation systems are frequently message-based (e.g., email-based) and are
smaller-scale solutions to departmental needs. As shown in the figure, they can access or import
data from larger, transaction processing systems.
The role of the system designers and builders is more technical. As such, their focus tends to
be placed more on the technologies that may be used by the Information system in order to achieve
the business goal. The system designers' and builders' perspectives of an Information system tend
to focus more on:
The database technologies that support business accumulation and use of business
knowledge.
The software technologies that automate and support business processes and
services.
The interface technologies that support business communications and collaboration.
Study Guide in (SAD 101 – SYSTEM ANALYSIS AND DESIGN) Module No._2_
The information system building blocks do not exist in isolation. They must be carefully
synchronized to avoid inconsistencies and incompatibilities within the system. For example, a
database designer (a system designer) and a programmer (a system builder) have their own
architectural views of the system; however, these views must be compatible and consistent if the
system is going to work properly, Synchronization occurs both horizontally.
In this module, we'll briefly examine each focus and perspective the building blocks of
information systems.
System owners’ view - interested not in raw data but in information that adds new business
knowledge and helps managers make decisions. Business knowledge and information help
managers make intelligent decisions that support the organization’s mission, goals,
objectives, and competitive edge. Business knowledge may initially take the form of a simple
list of business entities and business rules.
System owners are concerned with the big picture. They are generally not interested
in details (such as what fields describe a customer or an order). The primary role of system
owners in a systems development project should be to define the scope and vision for the
project. For KNOWLEDGE, scope can be defined in simple terms such as the
aforementioned business entities and rules. System owners define project vision and
expectations in terms of their Insight Into problems, opportunities, and constraints as they
relate to the business entities and rules.
System Users’ View- Information system users are knowledgeable about the data that
describe the business. As Information workers, they capture, store, process, edit, and use
that data every day. They frequently see the data only in terms of how data is currently
stored or how they think data should be stored. To them, the data are recorded on forms,
stored in file cabinets, recorded in books and binders, organized into spreadsheets, or
stored in computer files and databases. The challenge in systems development is to
correctly identify and verify users’ business data requirements. Data requirements are an
extension of the business entities and rules that were initially identified by the system
owners. System users may identify additional entities and rules because of their greater
familiarity with the data. More importantly, system users must specify the exact data
attributes to be stored and the precise business rules for maintaining that data.
Data requirement – a representation of users’ data in terms of entities, attributes,
relationships, and rules independent of data technology.
A system owner may identify the need to store data about a business entity called a
customer. System users might tell us that we need to differentiate between prospective
Study Guide in (SAD 101 – SYSTEM ANALYSIS AND DESIGN) Module No._2_
customers, active, active customers, and (Inactive customers because they know that
slightly different types of data describe each type of customer. System users can also tell us
precisely what data must be stored about each type of customer.
System Builders' View of Knowledge- The final view of knowledge is relevant to the
system builders. In the KNOWLEDGE column of figure below, system builders are closest to
the actual database management system technology. They must represent data in very
precise and unforgiving languages. The most commonly encountered database language is
SQL (Structured Query Language). Alternatively, many database management systems,
such as Access and Visual FoxPro include proprietary languages or facilities for constructing
a new database.
Business functions - a group of related processes that support the business. Functions
can be decomposed into other sub-functions and eventually into processes that do specific
tasks.
System Owners' View of Processes - system owners are generally interested in the big
picture. They tend to focus not so much on workflow and procedures as on high-level
business functions. Organizations are often organized around these business functions with
a vice president overseeing each function, unlike business events (such as CUSTOMER
submits ORDER) that have a definite beginning and end, a business function has no starting
time or stopping time.
System owners also frequently identify services and levels of service that they seek
to provide to customers, suppliers, and employees. A popular example is customer, supplier,
or employee self-service, Human resource systems, for example, increasingly provide
employees with the ability to enter their own transactions such as change of address,
medical claims, and training requests. System owners also identify need for information
Study Guide in (SAD 101 – SYSTEM ANALYSIS AND DESIGN) Module No._2_
System Users' View of Process- Users are concerned with the business processes, or
work, that must be performed in order to the appropriate responses to business events.
System users specify the business process in terms of process requirements for a new
system. Process requirements are often documented in terms of activities, data flows, or
work flow.
Study Guide in (SAD 101 – SYSTEM ANALYSIS AND DESIGN) Module No._2_
Study Guide in (SAD 101 – SYSTEM ANALYSIS AND DESIGN) Module No._2_
In this module, we unveiled a framework for information systems architecture that was
initially inspired by the work of John Zachman. The Zachman "Framework for Information Systems
Architecture achieved international recognition and use. The Zachman framework is a matrix rows
corresponds to what Zachman calls perspectives of different people involved in systems
development and use different people involved in systems development and use.
LEARNING ACTIVITIES
1. The framework for Information System architecture used in this module is derived from the
pioneering framework developed by John Zachman. What is one of the advantages of
designing systems based on this or similar frameworks?
2. Assume you are designing a retail point-of-sale (POS) system for your company. What are
the typical system interfaces of a point of sale system that need to be taken into account lo
designing the POS system
Study Guide in (SAD 101 – SYSTEM ANALYSIS AND DESIGN) Module No._2_
Encode your final answers in MS Word and submit them on or before the given deadline. Your
answer for each question should be a maximum of 10 sentences only. Check grammar and spelling
errors before submitting. Place your name, year level and section at the beginning of the page.
SUMMARY
Study Guide in (SAD 101 – SYSTEM ANALYSIS AND DESIGN) Module No._2_
project.
System users view communications in terms of the information system's inputs and outputs.
System designers are concerned with the technical design both user and system to system
communication interfaces.
System builders are concerned with the interface technology they use to implement user and
system-to-system communication interfaces.
Today's information systems are built on networks. Network technology allows properly de-
signed information systems to separate the KNOWLEDGE, PROCESS, and COMMUNICATION
building blocks and force them to communicate across the network.
REFERENCE
1. Bentley, Lonnie D., Whitten, Jeffrey L., 2007. System Analysis & Design Methods 7th
edition, McGraw-Hill Education.