Professional Documents
Culture Documents
Live Conference 1
Sep. 1, 2021 @ 10:30 AM - 1:30 PM
* Database Management
Dream Melee ecin
= Database:
= A collection of related data.
=" Data:
= Known facts that can be recorded and have an implicit meaning.
= Mini-world:
= Some part of the real world about which data is stored in a
database. For example, student grades and transcripts at a
university.
= Database Management System (DBMS):
=" A software package/ system to facilitate the creation and
maintenance of a computerized database.
= Database System:
= The DBMS software together with the data itself. Sometimes, the
applications are also included.
Dream Melee ecin
Users/Programmers
Database 1
System !
Application Programs/Queries
Software to Access
Stored Data
Stored Database
Definition Stored Database
(Meta-Data)
Figure 1.1
A simplified database
system environment.
Dream Melee ecin
Typical DBMS > Functionality
ganized combination of
ople, hardware, software,
Personal/Individual Functions:
socializing
study
shopping
banking
entertainment
Information System
Information Systems prior to IT Era
Information:
A collection of facts organized in such a
way that they have additional value
beyond the value of the facts themselves.
1a decision
Information System
System
Business Information
Systems
Information System
decision making
Information System
Systems Development
Information System
Systems Development:
Computer Literacy:
'’ Control
Feedback
Information System
Main Concept of Information Systems
Information System
Data:
Raw unorganized facts
Information:
Data organized in a meaningful
way for the user (in consideration of
the environment)
Information System
Information System
Information System
Activities
Data entry
e
Editing
Machine readable
e
Source documents
— Formal record of a transaction
User interface
— How users interact with information system
— Optical scanning; menu; prompts; fill in
blanks
Information System
Information System
Information System
Systems Applications in the Organization
| Decisions | | Management Levels | Information Systems
Unstructured Genior
E SS
Strategic Management
- DSS
Knowledge and
GIS, CAD/CAM,
Tactical Data Worker
Middle
Management
Lower
Management
Technical
(Operational)
Functions Buy Make
Structured
Information System
Major Types of Information Systems
5-Year Sales Trend
Forecasting
S-Year Operating Plan
Profit Planning
Personnel Planning
| —; Executive
\ pport Systems (ESS)
Sales Management
Sales Region Analysis
Inventory Control
Production Scheduling
Transaction
Processing
Systems
(TPs)
FUNCTIONAL
AREAS
Inter-Disciplinary Perspectives in Information Systems
; a Technical
N
Applied
socisleny
Information
ee Pc RSSn
. Operations
Economics
Management
7
Process centric
Marketing a
Management
1.2 Civil Engineering
~ Information System
Civil Engineering Information System
My Payroll
Gross Basic Allowance House Rent Allowance ESI Employee PF Employee Professional Tax
%58064.52 %29032.26 5806.45 % 1600.00 % 3600.00 200.00
@ MyTax 3 ] ee yeneie
Documentation
Conceptual
4
ate
Information _
Modeling _| |
ee
Construction
4D/5D
BIM vs EIS
BIM vs EIS
Documentation
Estimating Run Time
Civil Engineering Information System
Why EIS?
_) EIS not only provides intensified productivity through
improved operational process, but also heightens project
environment.
_! EIS improve productivity which in-turn will increase project
production and services.
Thanks!
Live Conference 2
Sep. 6, 2021 @ 10:30 AM - 1:30 PM
Module 2
P
7 Information Engineering
we Me eWAlcenlicaatic=
Oe Q
Oe TEA
enact
cron. ok om
79h ig
_) Information Engineering (IE)
A methodology for developing an integrated information system
based on the sharing of common data, with emphasis on decision
support needs as well as transaction-processing (TP) requirements.
An integrated and evolutionary set of tasks and techniques that
enhance business communication throughout an enterprise enabling
itto develop people, procedures and systems to achieve its vision.
Its aim is to enable an enterprise to improve the management of its
resources, including capital, people, and information systems, to
support the achievement of its business vision.
Y Information Engineering has sometimes been described as an
organization-wide set of automated disciplines ror getting the
right information to the right people at the right time
° Asaconcept, information engineeringis intended to unify and
combine the different requirements that must be engineered in any
complex system or application.
J Characteristic of IE
© |E applies structured techniques on an enterprise-wide basis, or to a
larger sector of an enterprise, rather than on a project-wide basis.
° IE progresses in a top-down fashion through the following stages:
Enterprise strategic systems planning
Enterprise information planning
Business Area analysis
System Design
Construction
Cutover
_) Characteristic of IE (cont'd)
Stage1:
[© Information Strategy Planning.
Stage 2:
[ Business Area Analysis.
Stage 3:
[= System Design.
Stage 4:
[© Construction.
_) Four Stages of IE (cont’d)
>» Business-driven
_) IE Variants (cont'd)
DP-driven (data processing)
Information Strategy Planning (ISP)
Outline Business Area Analysis (OBAA)
Detailed Business Area Analysis (DBAA)
Business System Design
Technical Design
Construction
Transition
_) IE Variants (cont'd)
Business-driven
Strategy Analysis
Strategic Modelling
Tactical and Operational Modelling
Activity Modelling
Process Modelling
Code Generation
_) Phases of IE (Business-driven IE Variant)
Data Modelling.
Process Modelling.
Systems Design
/mplementation.
Information Engineering (IE)
Strategic
Direction STRATEGIC BUSINESS PLANNING
Phases of IE
Independent
Technology
information Ca DATA MODELLING
(Business-driven) Requiremen
Information
Usage
&
ae miohlied
2 eo 5
NAVIGATION and
WAYFINOING
SEARCH
— Sos
. . ee =
_) Information Architecture on oa IL.
Hof " Ta
ocinteiiniiine — asalyaiiet tie
VY |s the design and organization of content, pages and data into a structure
that aids users understanding of a system.
¥ Amore organized system enables users to more easily find the information
they require and complete the intended tasks.
_) Information Architecture (cont'd)
J) Information
Se aa | Using the Library § Research Support § Course Support Perkins & Bostock
Hours (1 Wk)
Center for -
Peep Citation Tools Instructional Dake Uenaraity
Tech (CIT)
eBooks ‘Computer
ab Copyright Login to Sakai Lilly Library Directions
one penta
Publish&
Film & Video Techepiay1g Archive Your | | Music Library | Data & Reports
Work
Special Create Manage Your Divinity School Contact
Collections Multimedia Data Library
ee
See
Data & Digital FOOTER NAVIGATION
Maps
Address Tse &
Duke ( & Phone ) ContactUs | | Privacy | | Reproduction
iat Library Service {logo} Social
‘Center Media.
_) Information Architecture (cont'd)
~ | {i
i-Do i——|| {
Wh Lil 6
| °
Uhl tie
a i i
ml , iG 5 3 oe
106° \|\O
i —|16 16 s— |e lI-
lle 9 lle, |o ©
i i-
i
il!
Site Map and
Ecommerce
7 Baa
i-
i-G
Brand
aa - &G 6
User Flows
Hoe
j— 7
‘2,
i nT e =]
Information architecture has somewhat different meanings in different
branches of Information systems or Information technology:
P
Iw) Information Strategy
> Planning :
_) Information Strategy (IS) Planning
Is an organizational management activity that is used to set priorities,
focus energy and resources, strengthen operations, ensure that
employees and other stakeholders are working toward common
goals, establish agreement around intended outcomes/results, and
assess and adjust the organization's direction in response to a
changing environment.
_) Information Strategy (IS) Planning
1. Top-down planning
2. Bottom-up planning
_) Approaches to IS Planning
1. Top-down planning
_) Approaches to IS Planning (cont'd)
2. Bottom-up planning
Business Units
_) Principles of IS Planning
Segmentation Analysis:
© The purpose of this process is to match the company’s current or
prospective products and services with the market's potential.
© The alignment of the company’s products with the market potential
helps focus the strategic planning activities of the company in areas of
highest volume potential and highest financial return.
_) Principles of IS Planning (cont'd)
STRENGTHS | wEAKNESSES
— oy
What are = What obstacles
your goals? — do you face?
OPPORTUNITIES
kb the balance
_) Principles of IS Planning (cont'd)
Evaluation:
© The evaluation process needs to be ongoing and continuous.
© The evaluation process provides a clinical check-up on the progress of
the business compared to both the near-term Business Plan and the
long-term Strategic Plan.
_) Benefits of IS Planning
Lack of leadership:
© If the leaders of the institution, school, program, or department do not
support the plan, it will fail.
_) Challenges to IS Planning (cont'd)
Lack of consensus:
© It is often said that the process of strategic planning is what matters,
not the product.
Too ambitious:
© The problem of too many goals is exacerbated by implementation
planning.
¥
_) Challenges to IS Planning (cont'd)
Failure to integrate the plan into the culture, operations, and budget:
© Failures often occur because the strategic plan is divorced from the
daily life of an organization.
© Leaders must model the plan, and that includes talking about it—often.
_) Challenges to IS Planning (cont'd)
Topics
1. Introduction
2. Civil Engineering Information System
1.1 | Introduction
Information Systems
Personal/Individual Functions:
• socializing
• study
• shopping
• banking
• entertainment
Information Systems prior to IT Era
As major new technologies for recording and processing information were invented over
the millennia, new capabilities appeared, and people became empowered. The invention
of the printing press by Johannes Gutenberg in the mid-15th century and the invention
of a mechanical calculator by Blaise Pascal in the 17th century are but two
examples. These inventions led to a profound revolution in the ability
to record, process, disseminate, and reach for information and knowledge. This led, in
turn, to even deeper changes in individual lives, business organizations, and human
governance.
The first large-scale mechanical information system was Herman Hollerith’s census
tabulator. Invented in time to process the 1890 U.S. census, Hollerith’s machine
represented a major step in automation, as well as an inspiration to develop
computerized information systems.
Main Concept of Information Systems
Inter-Disciplinary Perspective
1.2 | Civil Engineering Information
Systems
Civil Engineering Information Systems
In Building and Construction projects, tasks typically tend to become more routine at
the clerical and supervisory levels, but more challenging and demanding at the senior
levels. However, computers also permit solutions to problems they cannot be attacked
manually, with a consequent increase in job satisfaction at the relevant level.
The utilization of on-site Engineering Information Systems (EIS) is becoming more and
more common:
• Complete Project Information database that will include all the client's contact
numbers, personal information, and histories. All of the negotiations and documents
will also be integrated within the EIS.
• Detailed Project Outline, which includes information such as costing agreements;
drawings of related plans including underground sewerage, electricity, storm runoffs,
easements, caveats, and other factors which can influence the satisfactory
completion of the project.
• Payroll, including all the payroll documentation, including payslips and payroll queries,
job application forms are also integrated within the EIS.
• All the Correspondence including all the information which is unable to be stored as
hard copies are stored in digital formats. This information includes drawings and
photographs of scanned images or databases of significant information.
• Digital Information, including all the information which is unable to be stored as hard
copies are stored as digital formats. This information includes drawings, and
photographs of scanned images or databases of significant information.
• Miscellaneous Information, which is not part of the other outcomes is incorporated
here.
2.0 Intended Learning Outcomes
and Topics
Intended Learning Outcomes
At the end of this module, the students will be able to:
Topics
2.1 | Information Engineering and Architecture
2.2 | Information Strategy Planning
2.1 | Information Engineering and
Architecture
Information Engineering and Architecture
o The underlying theme for both of these perspectives is that confidentiality must be
insured and misuse must be both prohibited and prevented.
o Moreover, it should be clear that information engineering must span the entire
business process, and not be limited to the design and development of an
application.
This is most easily quantified via the following list of design level questions.
• Stage 1:
Information Strategy Planning. Concerned with top management goals and critical
success factors. Concerned with how technology can be used to create new
opportunities or competitive advantages. A high level overview is created of the
enterprise, its functions, data, and information needs.
• Stage 2:
Business Area Analysis. Concerned with what processes are needed to run a selected
business area, how these processes interrelate, and what data is needed.
• Stage 3:
System Design. Concerned with how selected processes in the business area are
implemented in procedures and how these procedures work. Direct end user
involvement is needed in the design of procedures.
• Stage 4:
• Business-driven
o Strategy Analysis : This is a rapid delivery method for senior managers
and business unit managers for refinement of existing strategic business
plans, or development of new strategic business plans if none exist yet.
o Strategic Modeling: This uses a facilitated modeling session with senior
business managers who review the strategic business plans to develop a
strategic model.
o Tactical and Operational Modeling : This uses the same approach as for
strategic modeling, but focuses on tactical business units.
o Activity Modeling : Activity models, based on IDEF0 and activity-based
costing, are used to document priority business activities for rapid
delivery.
o Process Modeling : Business Process Modeling Notation (BPMN) is
used, supported by modeling tools, to define process model diagrams in
BPMN of priority activities for rapid delivery into production.
o Code Generation : BPMN process model diagrams are used to generate
XML-based code in Business Process Execution Language (BPEL) for
execution.
The Phases of Information Engineering (Business-driven IE variant)
Strategic Business Planning: The business directions that senior managers set for the
future are defined in strategic business plans, with their greater definition in tactical
business plans and implementation in operational business plans
Data Modelling: Data models should ideally be based on directions set by
management for the future. As discussed, these are defined in business plans.
Process Modelling: A business event is an essential link between a business plan and
a business process. It initiates strategies and tactics. In the plan, an event is defined as
a narrative statement.
Systems Design and Implementation: The Business Model, comprising data models
and process models that are developed from business plans, indicate the business
needs to be addressed by relevant information systems and databases. They define the
systems requirements from a business perspective, which is one part of systems
design.
• Entity analysis : identifies all the things that the enterprise may want to hold data
about.
• Function analysis and process dependency : takes a function (a major business
activity) of the enterprise and breaks it down into elementary business processes.
• Process logic analysis : describes the sequences of actions carried out by a
business process and shows which data are used by each action.
• Entity type lifecycle analysis : describes the significant business changes to entities
and confirm that processes have been modelled to effect these changes
• Matrix cross-checking : creates cross- references between data objects and
processes to verify that they are necessary and complete.
• Normalization : provides a formal means of confirming the correctness of the entity
model.
• Cluster analysis : helps define the scope of design areas for proposed business
systems.
• Data flow and data analysis : makes a comparison possible between the business
area models and the systems currently supporting this area, these current systems
are analyzed using data flow and data analysis techniques.
▪ Is the design and organization of content, pages and data into a structure that
aids users understanding of a system.
▪ A more organized system enables users to more easily find the information
they require and complete the intended tasks.
▪ To create an effective information architecture you need to understand the
relationship between the content and the interoperability of the system you
are designing.
▪ A flow or hierarchy is often established with IA that allows users to
understand where they are, and where they can go next.
▪ Information Architecture is a discipline of it’s own and can be performed by
specialists or any other members of a design team.
▪ An Information architect's output can be expressed visually through: site
maps, wireframes, navigation, taxonomic designs, metadata and more.
Information architecture has somewhat different meanings in different branches of
Information systems or Information technology:
Approaches to IS Planning
• Top-down Planning
•
o Focuses on organizational goals first, then on the needs of business
units.
o Top-down, or goal-driven, planning considers the organization as a
whole.
• Bottom-up Planning
•
o Focuses on the needs of business units first, then on organizational
goals.
o In bottom-up planning, the process starts with consideration of
individual concerns.
The Principle of IS Planning
There is no one formula or process for strategic planning.
There are, however, principles and required steps that optimize the value of strategic
planning.
The steps in the process of strategic planning are presented below:
Benefits of IS Planning
IS planning serves a variety of purposes in organizations, including to:
• Clearly define the purpose of the organization and to establish realistic goals and
objectives consistent with that mission in a defined time frame within the
organization’s capacity for implementation.
• Communicate those goals and objectives to the organization’s constituents.
• Develop a sense of ownership of the plan.
• Ensure the most effective use is made of the organization’s resources by focusing
the resources on the key priorities.
• Provide a base from which progress can be measured and establish a mechanism
for informed change when needed.
• Listen to everyone’s opinions in order to build consensus about where the
organization is going.
• Provide clearer focus for the organization, thereby producing more efficiency and
effectiveness.
• Bridge staff/employees and the board of directors (in the case of corporations).
• Build strong teams in the board and in the staff/employees (in the case of
corporations).
• Provide the glue that keeps the board members together (in the case of
corporations).
• Produce great satisfaction and meaning among planners, especially around a
common vision.
• Increase productivity from increased efficiency and effectiveness.
• Solve major problems in the organization.
Challenges to IS Planning
There are many reasons IS plans fail, but the following challenges are among the most
common:
• Lack of leadership:
o If the leaders of the institution, school, program, or department do not
support the plan, it will fail.
o This point seems obvious, but far too often leaders talk about the
importance of the strategic plan as the planning process gets underway,
only to show little interest down the line.
• Lack of consensus:
o It is often said that the process of strategic planning is what matters, not
the product.
o Of course, the process itself is vital; yet if an institution is serious about
implementing the plan, then an excellent product is imperative.
o Strategic planning is about consensus building. Done correctly, the
process promotes communication, participation, and collaboration.
• Too ambitious:
o The problem of too many goals is exacerbated by implementation
planning.
o More often than not, strategies and goals are deconstructed into literally
hundreds of specific objectives.
• Failure to integrate the plan into the culture, operations, and budget:
o Failures often occur because the strategic plan is divorced from the daily
life of an organization.
o Leaders must model the plan, and that includes talking about it—often.
• Lack of momentum in the short term:
o Even with a shorter time frame, an annual (or sometimes biennial,
depending on the environment), systematic assessment of the plan is
necessary for course corrections.
o The planning process itself should create momentum but if the process
takes too long, then those involved begin to lose their enthusiasm. Thus
the timeline is important; staying with an aggressive timeline sends the
message that the planning is a serious endeavor.