This chapter discusses database design and the systems development life cycle (SDLC). It explains that the SDLC traces the development of an information system through planning, analysis, design, implementation, and maintenance phases. Within the information system, the database life cycle (DBLC) describes the development of the database through initial study, design, implementation, testing, operation, and maintenance phases. The chapter also covers topics of conceptual database design, logical design, and physical design.
The document discusses database design within the context of information systems and their life cycles. It describes the systems development life cycle (SDLC) and database life cycle (DBLC) as frameworks for developing and maintaining databases and applications. The database design process involves conceptual, logical, and physical design stages to model data and map the design to a target database management system. Centralized and decentralized approaches as well as top-down and bottom-up strategies are discussed for database design.
This document outlines the key principles and learning objectives covered in Chapter 13 of Principles of Information Systems, Ninth Edition. It discusses systems design, implementation, maintenance, and review. Specifically, it covers: 1) the purpose of systems design and differences between logical and physical design, 2) considerations for implementation including acquiring software/hardware and user preparation, and 3) the importance of maintenance and review to extend a system's useful life.
This document provides an overview of database systems, data centers, and business intelligence. It defines key concepts such as entities, attributes, keys, and discusses the relational database model and logical and physical database design. It also describes database management systems, popular DBMSs, data warehouses, data mining, and how databases support business intelligence. The document emphasizes that well-organized data and effective data management are crucial for organizational decision making.
The document discusses the database development life cycle (DBLC), which follows a similar process to the systems development life cycle (SDLC). The DBLC involves gathering requirements, database analysis, design, implementation, testing and evaluation, and maintenance. It describes each stage in detail, including conceptual, logical, and physical data modeling during the design stage. The goal is to systematically plan and develop a database to meet requirements while ensuring completeness, integrity, flexibility, and usability.
Business intelligence and data warehousesDhani Ahmad
This chapter discusses business intelligence and data warehouses. It covers how operational data differs from decision support data, the components of a data warehouse including facts, dimensions and star schemas, and how online analytical processing (OLAP) and SQL extensions support analysis of multidimensional decision support data. The chapter also discusses data mining, requirements for decision support databases, and considerations for implementing a successful data warehouse project.
This document discusses database administration and security. It describes the roles and responsibilities of database administrators including managing resources, enforcing policies and procedures, ensuring security, and performing technical tasks using tools in Oracle like creating tablespaces and users. Database security involves securing the system through policies, audits, and access controls to maintain data confidentiality, integrity and availability. The document outlines the technical and managerial skills required of DBAs.
This document provides an overview of systems analysis and design. It discusses the role of the systems analyst and describes the typical software development process. This includes methodologies, techniques, and tools used for analysis and design. It also summarizes key components of an information system like data, data flows, and processing logic. Finally, it outlines the traditional systems development life cycle with its phases of project identification, analysis, design, implementation, and maintenance.
This chapter introduces systems analysis and design and discusses the impact of information technology on business. It defines the components of an information system as hardware, software, data, processes, and people. The chapter also explains different types of information systems and the role of systems analysts in developing systems using various methods like structured analysis, object-oriented analysis, and agile development.
The document discusses database design within the context of information systems and their life cycles. It describes the systems development life cycle (SDLC) and database life cycle (DBLC) as frameworks for developing and maintaining databases and applications. The database design process involves conceptual, logical, and physical design stages to model data and map the design to a target database management system. Centralized and decentralized approaches as well as top-down and bottom-up strategies are discussed for database design.
This document outlines the key principles and learning objectives covered in Chapter 13 of Principles of Information Systems, Ninth Edition. It discusses systems design, implementation, maintenance, and review. Specifically, it covers: 1) the purpose of systems design and differences between logical and physical design, 2) considerations for implementation including acquiring software/hardware and user preparation, and 3) the importance of maintenance and review to extend a system's useful life.
This document provides an overview of database systems, data centers, and business intelligence. It defines key concepts such as entities, attributes, keys, and discusses the relational database model and logical and physical database design. It also describes database management systems, popular DBMSs, data warehouses, data mining, and how databases support business intelligence. The document emphasizes that well-organized data and effective data management are crucial for organizational decision making.
The document discusses the database development life cycle (DBLC), which follows a similar process to the systems development life cycle (SDLC). The DBLC involves gathering requirements, database analysis, design, implementation, testing and evaluation, and maintenance. It describes each stage in detail, including conceptual, logical, and physical data modeling during the design stage. The goal is to systematically plan and develop a database to meet requirements while ensuring completeness, integrity, flexibility, and usability.
Business intelligence and data warehousesDhani Ahmad
This chapter discusses business intelligence and data warehouses. It covers how operational data differs from decision support data, the components of a data warehouse including facts, dimensions and star schemas, and how online analytical processing (OLAP) and SQL extensions support analysis of multidimensional decision support data. The chapter also discusses data mining, requirements for decision support databases, and considerations for implementing a successful data warehouse project.
This document discusses database administration and security. It describes the roles and responsibilities of database administrators including managing resources, enforcing policies and procedures, ensuring security, and performing technical tasks using tools in Oracle like creating tablespaces and users. Database security involves securing the system through policies, audits, and access controls to maintain data confidentiality, integrity and availability. The document outlines the technical and managerial skills required of DBAs.
This document provides an overview of systems analysis and design. It discusses the role of the systems analyst and describes the typical software development process. This includes methodologies, techniques, and tools used for analysis and design. It also summarizes key components of an information system like data, data flows, and processing logic. Finally, it outlines the traditional systems development life cycle with its phases of project identification, analysis, design, implementation, and maintenance.
This chapter introduces systems analysis and design and discusses the impact of information technology on business. It defines the components of an information system as hardware, software, data, processes, and people. The chapter also explains different types of information systems and the role of systems analysts in developing systems using various methods like structured analysis, object-oriented analysis, and agile development.
The document describes the systems development life cycle (SDLC) as a framework for developing information systems using well-defined sequential phases: planning, analysis, design, implementation, and maintenance. It explains the key tasks for each phase and also discusses newer approaches like prototyping, outsourcing options, and agile methodologies.
Chapter 1 Introduction to Systems Analysis and Design .pptxAxmedMaxamuudYoonis
This chapter introduces systems analysis and design and the role of information technology in business. It defines the components of an information system as hardware, software, data, processes, and people. It also explains the role of systems analysts in developing information systems using various methods like structured analysis, object-oriented analysis, and agile development. The chapter emphasizes that information technology and effective information systems are crucial for business success.
This document provides an overview of database systems, data centers, and business intelligence. It defines key concepts such as databases, database management systems, data modeling, and data warehouses. It also describes popular database types, how data is stored and retrieved from databases, and how business intelligence tools can analyze database information.
The document discusses the key phases of systems development: design, implementation, maintenance, and review. It describes the logical and physical design process, including object-oriented design. Implementation activities like acquiring hardware and software, user training, and testing are also outlined. The importance of ongoing maintenance to fix issues and adapt to changes is highlighted. Systems are regularly reviewed to ensure they continue to meet needs.
The document discusses the database system development lifecycle. It notes that 80-90% of database projects do not meet performance goals and are often late and over budget. Reasons for failure include a lack of complete requirements specification, inappropriate development methodology, and poor system decomposition. The solution is to follow a structured approach like the Information Systems Lifecycle, Software Development Lifecycle, or Database System Development Lifecycle. Key stages of the Database System Development Lifecycle include planning, definition, requirements collection, design, prototyping, implementation, data conversion, testing, and operational maintenance.
This document provides information about system engineering. It defines system engineering as an approach to design, implement, and evaluate complex systems. It lists several jobs that system engineers can have, such as system engineer, safety engineer, and space craft system engineer. It describes some of the duties of system engineers, which include ensuring everything works properly, creating new ideas, and coordinating with others. The document discusses elements of computer-based systems, including software, hardware, people, databases, documentation, and procedures. It also covers topics like system modeling, business process engineering, system architectures, product engineering, and requirements engineering.
The document provides an overview of the Structured Systems Analysis and Design Method (SSADM). It describes SSADM as a comprehensive, structured approach to systems development that is considered the true successor to traditional system development lifecycles. The key techniques of SSADM are described as logical data modeling, data flow modeling, and entity event modeling. The stages of the SSADM methodology are then outlined, including feasibility study, investigation of the current environment, business system options, requirements specification, technical system options, logical design, and physical design.
This document provides an overview of systems analysis, including the differences between systems analysis and design, common phases and tasks of systems analysis like requirements discovery, and different approaches to systems analysis like structured analysis and accelerated systems analysis using prototypes. It describes tasks involved in scope definition, problem analysis, requirements analysis, logical design, and decision analysis phases.
The document discusses the database development process, including conceptual data modeling using entity-relationship diagrams, logical and physical database design, and implementation using SQL. It also covers information systems architecture and planning, involving developing an enterprise data model and process decomposition. The prototyping and system development life cycle approaches to database development are presented, as well as the roles of various people involved. Finally, it describes the three-schema database architecture separating conceptual, external and internal schemas, and the three-tiered database location architecture separating presentation, process and data tiers.
This document discusses the key principles and learning objectives for Chapter 12 of the textbook "Principles of Information Systems, Tenth Edition". It covers the importance of teamwork in systems development and identifies the roles of key participants. It also discusses different systems development life cycles like traditional, prototyping, and rapid application development. Finally, it outlines factors that influence the success or failure of systems development projects, including project planning, managing change, and quality standards.
This chapter introduces systems analysis and design. It discusses how information technology impacts business strategy and defines the components of an information system. It also explains different types of information systems and development methods like structured analysis, object-oriented analysis, and agile methods. The role of systems analysts and developing high-quality information systems is also covered.
01. Developing Business _ IT Solutions 2011.pptiqbal051663
The document discusses the systems development process, including systems analysis and design, prototyping, user interface design, implementation, project management, and post-implementation activities. It provides learning objectives for each step and examples to illustrate key points. The overall goal is to apply a systems approach to information systems development and management of the development process.
The document discusses the goals of the Tool Vendor Challenge which include capturing stakeholder needs, requirements management, deriving system requirements, decision analysis, gap analysis, consistency checking, and change management. It also discusses capturing atomic requirements using rich text, tables, workflows and documentation. Additional topics covered include risk management, reusing existing elements, impact analysis, and semantic searching of reusable components.
System analysis and design
Introduction
Information system components
Business today
Modeling business operation
Business information systems
What information do user need
Systems development tools
Systems development methods
Chapter exercises
The document discusses various topics related to software architecture and design including software design phases, goals and limitations of software architecture, data modeling types, database design life cycle, data warehouse modeling, analyzing alternative architectural designs both qualitatively and quantitatively, and measuring architectural complexity based on different dependency types.
The document discusses databases and data warehouses. It begins by explaining the differences between traditional file organization and database management approaches. It then describes how relational and object-oriented databases are used to construct, populate, and manipulate databases. Finally, it discusses how data is transferred from transactional databases to data warehouses for analysis and decision making.
This chapter introduces systems analysis and design and information systems. It discusses how information technology impacts business strategy and defines the components of an information system. It also explains different types of information systems and development methods like structured analysis, object-oriented analysis, and agile development. The role of systems analysts and how they help develop high-quality information systems is also covered.
Introduction To System Analysis & DesignSyedQamar9
An information system is a collection of components that collect, process, store, and output information needed to complete business tasks. Examples include course registration, online ordering, and banking systems. System analysis involves understanding business goals, defining information requirements, and solving problems using IT without programming. The role of a system analyst is to have business knowledge, solve business problems, and translate requirements into IT projects. The traditional system development life cycle includes planning, analysis, design, implementation, and support phases. Design decides how the system will operate in terms of hardware, software, network infrastructure, user interface, forms, reports, programs, databases and files.
This document discusses systems analysis and design. It begins with an overview of information systems analysis and design, the systems development life cycle (SDLC), and agile methodologies like eXtreme Programming and Scrum. It then covers the SDLC phases of planning, analysis, design, implementation, and maintenance. Finally, it discusses how agile methodologies focus on adaptive processes, people over roles, and self-adaptive processes.
How to Build a Module in Odoo 17 Using the Scaffold MethodCeline George
Odoo provides an option for creating a module by using a single line command. By using this command the user can make a whole structure of a module. It is very easy for a beginner to make a module. There is no need to make each file manually. This slide will show how to create a module using the scaffold method.
The document describes the systems development life cycle (SDLC) as a framework for developing information systems using well-defined sequential phases: planning, analysis, design, implementation, and maintenance. It explains the key tasks for each phase and also discusses newer approaches like prototyping, outsourcing options, and agile methodologies.
Chapter 1 Introduction to Systems Analysis and Design .pptxAxmedMaxamuudYoonis
This chapter introduces systems analysis and design and the role of information technology in business. It defines the components of an information system as hardware, software, data, processes, and people. It also explains the role of systems analysts in developing information systems using various methods like structured analysis, object-oriented analysis, and agile development. The chapter emphasizes that information technology and effective information systems are crucial for business success.
This document provides an overview of database systems, data centers, and business intelligence. It defines key concepts such as databases, database management systems, data modeling, and data warehouses. It also describes popular database types, how data is stored and retrieved from databases, and how business intelligence tools can analyze database information.
The document discusses the key phases of systems development: design, implementation, maintenance, and review. It describes the logical and physical design process, including object-oriented design. Implementation activities like acquiring hardware and software, user training, and testing are also outlined. The importance of ongoing maintenance to fix issues and adapt to changes is highlighted. Systems are regularly reviewed to ensure they continue to meet needs.
The document discusses the database system development lifecycle. It notes that 80-90% of database projects do not meet performance goals and are often late and over budget. Reasons for failure include a lack of complete requirements specification, inappropriate development methodology, and poor system decomposition. The solution is to follow a structured approach like the Information Systems Lifecycle, Software Development Lifecycle, or Database System Development Lifecycle. Key stages of the Database System Development Lifecycle include planning, definition, requirements collection, design, prototyping, implementation, data conversion, testing, and operational maintenance.
This document provides information about system engineering. It defines system engineering as an approach to design, implement, and evaluate complex systems. It lists several jobs that system engineers can have, such as system engineer, safety engineer, and space craft system engineer. It describes some of the duties of system engineers, which include ensuring everything works properly, creating new ideas, and coordinating with others. The document discusses elements of computer-based systems, including software, hardware, people, databases, documentation, and procedures. It also covers topics like system modeling, business process engineering, system architectures, product engineering, and requirements engineering.
The document provides an overview of the Structured Systems Analysis and Design Method (SSADM). It describes SSADM as a comprehensive, structured approach to systems development that is considered the true successor to traditional system development lifecycles. The key techniques of SSADM are described as logical data modeling, data flow modeling, and entity event modeling. The stages of the SSADM methodology are then outlined, including feasibility study, investigation of the current environment, business system options, requirements specification, technical system options, logical design, and physical design.
This document provides an overview of systems analysis, including the differences between systems analysis and design, common phases and tasks of systems analysis like requirements discovery, and different approaches to systems analysis like structured analysis and accelerated systems analysis using prototypes. It describes tasks involved in scope definition, problem analysis, requirements analysis, logical design, and decision analysis phases.
The document discusses the database development process, including conceptual data modeling using entity-relationship diagrams, logical and physical database design, and implementation using SQL. It also covers information systems architecture and planning, involving developing an enterprise data model and process decomposition. The prototyping and system development life cycle approaches to database development are presented, as well as the roles of various people involved. Finally, it describes the three-schema database architecture separating conceptual, external and internal schemas, and the three-tiered database location architecture separating presentation, process and data tiers.
This document discusses the key principles and learning objectives for Chapter 12 of the textbook "Principles of Information Systems, Tenth Edition". It covers the importance of teamwork in systems development and identifies the roles of key participants. It also discusses different systems development life cycles like traditional, prototyping, and rapid application development. Finally, it outlines factors that influence the success or failure of systems development projects, including project planning, managing change, and quality standards.
This chapter introduces systems analysis and design. It discusses how information technology impacts business strategy and defines the components of an information system. It also explains different types of information systems and development methods like structured analysis, object-oriented analysis, and agile methods. The role of systems analysts and developing high-quality information systems is also covered.
01. Developing Business _ IT Solutions 2011.pptiqbal051663
The document discusses the systems development process, including systems analysis and design, prototyping, user interface design, implementation, project management, and post-implementation activities. It provides learning objectives for each step and examples to illustrate key points. The overall goal is to apply a systems approach to information systems development and management of the development process.
The document discusses the goals of the Tool Vendor Challenge which include capturing stakeholder needs, requirements management, deriving system requirements, decision analysis, gap analysis, consistency checking, and change management. It also discusses capturing atomic requirements using rich text, tables, workflows and documentation. Additional topics covered include risk management, reusing existing elements, impact analysis, and semantic searching of reusable components.
System analysis and design
Introduction
Information system components
Business today
Modeling business operation
Business information systems
What information do user need
Systems development tools
Systems development methods
Chapter exercises
The document discusses various topics related to software architecture and design including software design phases, goals and limitations of software architecture, data modeling types, database design life cycle, data warehouse modeling, analyzing alternative architectural designs both qualitatively and quantitatively, and measuring architectural complexity based on different dependency types.
The document discusses databases and data warehouses. It begins by explaining the differences between traditional file organization and database management approaches. It then describes how relational and object-oriented databases are used to construct, populate, and manipulate databases. Finally, it discusses how data is transferred from transactional databases to data warehouses for analysis and decision making.
This chapter introduces systems analysis and design and information systems. It discusses how information technology impacts business strategy and defines the components of an information system. It also explains different types of information systems and development methods like structured analysis, object-oriented analysis, and agile development. The role of systems analysts and how they help develop high-quality information systems is also covered.
Introduction To System Analysis & DesignSyedQamar9
An information system is a collection of components that collect, process, store, and output information needed to complete business tasks. Examples include course registration, online ordering, and banking systems. System analysis involves understanding business goals, defining information requirements, and solving problems using IT without programming. The role of a system analyst is to have business knowledge, solve business problems, and translate requirements into IT projects. The traditional system development life cycle includes planning, analysis, design, implementation, and support phases. Design decides how the system will operate in terms of hardware, software, network infrastructure, user interface, forms, reports, programs, databases and files.
This document discusses systems analysis and design. It begins with an overview of information systems analysis and design, the systems development life cycle (SDLC), and agile methodologies like eXtreme Programming and Scrum. It then covers the SDLC phases of planning, analysis, design, implementation, and maintenance. Finally, it discusses how agile methodologies focus on adaptive processes, people over roles, and self-adaptive processes.
How to Build a Module in Odoo 17 Using the Scaffold MethodCeline George
Odoo provides an option for creating a module by using a single line command. By using this command the user can make a whole structure of a module. It is very easy for a beginner to make a module. There is no need to make each file manually. This slide will show how to create a module using the scaffold method.
A Strategic Approach: GenAI in EducationPeter Windle
Artificial Intelligence (AI) technologies such as Generative AI, Image Generators and Large Language Models have had a dramatic impact on teaching, learning and assessment over the past 18 months. The most immediate threat AI posed was to Academic Integrity with Higher Education Institutes (HEIs) focusing their efforts on combating the use of GenAI in assessment. Guidelines were developed for staff and students, policies put in place too. Innovative educators have forged paths in the use of Generative AI for teaching, learning and assessments leading to pockets of transformation springing up across HEIs, often with little or no top-down guidance, support or direction.
This Gasta posits a strategic approach to integrating AI into HEIs to prepare staff, students and the curriculum for an evolving world and workplace. We will highlight the advantages of working with these technologies beyond the realm of teaching, learning and assessment by considering prompt engineering skills, industry impact, curriculum changes, and the need for staff upskilling. In contrast, not engaging strategically with Generative AI poses risks, including falling behind peers, missed opportunities and failing to ensure our graduates remain employable. The rapid evolution of AI technologies necessitates a proactive and strategic approach if we are to remain relevant.
This slide is special for master students (MIBS & MIFB) in UUM. Also useful for readers who are interested in the topic of contemporary Islamic banking.
Introduction to AI for Nonprofits with Tapp NetworkTechSoup
Dive into the world of AI! Experts Jon Hill and Tareq Monaur will guide you through AI's role in enhancing nonprofit websites and basic marketing strategies, making it easy to understand and apply.
Assessment and Planning in Educational technology.pptxKavitha Krishnan
In an education system, it is understood that assessment is only for the students, but on the other hand, the Assessment of teachers is also an important aspect of the education system that ensures teachers are providing high-quality instruction to students. The assessment process can be used to provide feedback and support for professional development, to inform decisions about teacher retention or promotion, or to evaluate teacher effectiveness for accountability purposes.
Physiology and chemistry of skin and pigmentation, hairs, scalp, lips and nail, Cleansing cream, Lotions, Face powders, Face packs, Lipsticks, Bath products, soaps and baby product,
Preparation and standardization of the following : Tonic, Bleaches, Dentifrices and Mouth washes & Tooth Pastes, Cosmetics for Nails.
This presentation was provided by Steph Pollock of The American Psychological Association’s Journals Program, and Damita Snow, of The American Society of Civil Engineers (ASCE), for the initial session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session One: 'Setting Expectations: a DEIA Primer,' was held June 6, 2024.
বাংলাদেশের অর্থনৈতিক সমীক্ষা ২০২৪ [Bangladesh Economic Review 2024 Bangla.pdf] কম্পিউটার , ট্যাব ও স্মার্ট ফোন ভার্সন সহ সম্পূর্ণ বাংলা ই-বুক বা pdf বই " সুচিপত্র ...বুকমার্ক মেনু 🔖 ও হাইপার লিংক মেনু 📝👆 যুক্ত ..
আমাদের সবার জন্য খুব খুব গুরুত্বপূর্ণ একটি বই ..বিসিএস, ব্যাংক, ইউনিভার্সিটি ভর্তি ও যে কোন প্রতিযোগিতা মূলক পরীক্ষার জন্য এর খুব ইম্পরট্যান্ট একটি বিষয় ...তাছাড়া বাংলাদেশের সাম্প্রতিক যে কোন ডাটা বা তথ্য এই বইতে পাবেন ...
তাই একজন নাগরিক হিসাবে এই তথ্য গুলো আপনার জানা প্রয়োজন ...।
বিসিএস ও ব্যাংক এর লিখিত পরীক্ষা ...+এছাড়া মাধ্যমিক ও উচ্চমাধ্যমিকের স্টুডেন্টদের জন্য অনেক কাজে আসবে ...
Executive Directors Chat Leveraging AI for Diversity, Equity, and InclusionTechSoup
Let’s explore the intersection of technology and equity in the final session of our DEI series. Discover how AI tools, like ChatGPT, can be used to support and enhance your nonprofit's DEI initiatives. Participants will gain insights into practical AI applications and get tips for leveraging technology to advance their DEI goals.
This presentation includes basic of PCOS their pathology and treatment and also Ayurveda correlation of PCOS and Ayurvedic line of treatment mentioned in classics.
A workshop hosted by the South African Journal of Science aimed at postgraduate students and early career researchers with little or no experience in writing and publishing journal articles.
2. Database Systems, 8th Edition 2
Objectives
• In this chapter, you will learn:
– That successful database design must reflect
the information system of which the database is
a part
– That successful information systems are
developed within a framework known as the
Systems Development Life Cycle (SDLC)
3. Database Systems, 8th Edition 3
Objectives (continued)
• In this chapter, you will learn: (continued)
– That within the information system, the most
successful databases are subject to frequent
evaluation and revision within a framework
known as the Database Life Cycle (DBLC)
– How to conduct evaluation and revision within
the SDLC and DBLC frameworks
– About database design strategies: top-down vs.
bottom-up design and centralized vs.
decentralized design
4. Database Systems, 8th Edition 4
The Information System
• Provides for data collection, storage, and
retrieval
• Composed of:
– People, hardware, software
– Database(s), application programs, procedures
• Systems analysis
– Process that establishes need for and extent of
information system
• Systems development
– Process of creating information system
5. Database Systems, 8th Edition 5
The Information System (continued)
• Applications
– Transform data into information that forms basis
for decision making
– Usually produce the following:
• Formal report
• Tabulations
• Graphic displays
– Composed of following two parts:
• Data
• Code by which data are transformed into
information
7. Database Systems, 8th Edition 7
The Information System (continued)
• Performance depends on three factors:
– Database design and implementation
– Application design and implementation
– Administrative procedures
• Database development
– Process of database design and implementation
– Implementation phase includes:
• Creating database storage structure
• Loading data into the database
• Providing for data management
8. Database Systems, 8th Edition 8
The Systems Development Life Cycle
(SDLC)
• Traces history (life cycle) of information system
• Database design and application development
mapped out and evaluated
• Divided into following five phases:
– Planning
– Analysis
– Detailed systems design
– Implementation
– Maintenance
• Iterative rather than sequential process
10. Database Systems, 8th Edition 10
Planning
• General overview of company and objectives
• Assessment of flow-and-extent requirements
– Should the existing system be continued?
– Should the existing system be modified?
– Should the existing system be replaced?
• Study and evaluate alternate solutions
– Technical aspects of hardware and software
requirements
– System cost
– Operational cost
11. Database Systems, 8th Edition 11
Analysis
• Problems defined during planning phase
examined in greater detail during analysis
• Thorough audit of user requirements
• Existing hardware and software systems are
studied
• Goal:
– Better understanding of:
• System’s functional areas
• Actual and potential problems
• Opportunities
12. Database Systems, 8th Edition 12
Detailed Systems Design
• Designer completes design of system’s
processes
• Includes all necessary technical specifications
• Steps laid out for conversion from old to new
system
• Training principles and methodologies are also
planned
– Submitted for management approval
13. Database Systems, 8th Edition 13
Implementation
• Hardware, DBMS software, and application
programs are installed
– Database design implemented
• Cycle of coding, testing, and debugging
continues until database ready for delivery
• Database created and system customized
– Creation of tables and views
– User authorizations
14. Database Systems, 8th Edition 14
Maintenance
• Three types of maintenance activity:
– Corrective maintenance
– Adaptive maintenance
– Perfective maintenance
• Computer-aided systems engineering
(CASE)
– Produce better systems within reasonable
amount of time and at reasonable cost
– CASE-produced applications are structured,
documented, standardized
15. Database Systems, 8th Edition 15
The Database Life Cycle (DBLC)
• Six phases:
– Database initial study
– Database design
– Implementation and loading
– Testing and evaluation
– Operation
– Maintenance and evolution
17. Database Systems, 8th Edition 17
The Database Initial Study
• Overall purpose:
– Analyze company situation
– Define problems and constraints
– Define objectives
– Define scope and boundaries
• Interactive and iterative processes required to
complete first phase of DBLC successfully
19. Database Systems, 8th Edition 19
The Database Initial Study (continued)
• Analyze the company situation
– General conditions in which company operates,
its organizational structure, and its mission
– Discover what company’s operational
components are, how they function, and how
they interact
• Define problems and constraints
– Formal and informal information sources
– Finding precise answers is important
– Accurate problem definition does not always
yield a solution
20. Database Systems, 8th Edition 20
• Database system objectives must correspond
to those envisioned by end users
– What is proposed system’s initial objective?
– Will system interface with other systems in the
company?
– Will system share data with other systems or
users?
• Scope: extent of design according to
operational requirements
• Boundaries: limits external to system
The Database Initial Study (continued)
21. Database Systems, 8th Edition 21
Database Design
• Necessary to concentrate on data
• Characteristics required to build database
model
• Two views of data within system:
– Business view
• Data as information source
– Designer’s view
• Data structure, access, and activities required to
transform data into information
24. Database Systems, 8th Edition 24
I. Conceptual Design
• Data modeling creates an abstract database
structure
– Represents real-world objects
• Embodies clear understanding of business and
its functional areas
• Ensure that all data needed are in model, and
that all data in model are needed
• Requires four steps
25. Database Systems, 8th Edition 25
I. Conceptual Design (continued)
• Data analysis and requirements
– Discover data element characteristics
• Obtains characteristics from different sources
– Take into account business rules
• Derived from description of operations
• Entity relationship modeling and normalization
– Designer enforces standards in design
documentation
• Use of diagrams and symbols, documentation
writing style, layout, other conventions
27. Database Systems, 8th Edition 27
I. Conceptual Design (continued)
• Data model verification
– Verified against proposed system processes
– Revision of original design
• Careful reevaluation of entities
• Detailed examination of attributes describing
entities
– Define design’s major components as modules:
• Module: information system component that
handles specific function
30. Database Systems, 8th Edition 30
I. Conceptual Design (continued)
• Data model verification (continued)
– Verification process
• Select central (most important) entity
– Defined in terms of its participation in most of
model’s relationships
• Identify module or subsystem to which central
entity belongs and define boundaries and scope
• Place central entity within module’s framework
31. Database Systems, 8th Edition 31
I. Conceptual Design (continued)
• Distributed database design
– Portions of database may reside in different
physical locations
– Processes accessing the database vary from
one location to another
– Designer must also develop data distribution
and allocation strategies
32. Database Systems, 8th Edition 32
II. DBMS Software Selection
• Critical to information system’s smooth
operation
• Common factors affecting purchasing
decisions:
– Cost
– DBMS features and tools
– Underlying model
– Portability
– DBMS hardware requirements
33. Database Systems, 8th Edition 33
III. Logical Design
• Translate conceptual design into internal model
• Logical design is software-dependent
• Requires all objects be mapped to specific
constructs used by selected database software
– Definition of attribute domains, design of
required tables, access restriction formats
– Tables must correspond to entities in conceptual
design
• Translates software-independent conceptual
model into software-dependent model
35. Database Systems, 8th Edition 35
IV. Physical Design
• Process of selecting data storage and data
access characteristics of database
• Storage characteristics are function of:
– Device types supported by hardware
– Type of data access methods supported by
system
– DBMS
• More complex when data are distributed
36. Database Systems, 8th Edition 36
Implementation and Loading
• New database implementation requires special
storage-related constructs for end-user tables
• Performance
– Difficult to evaluate
• Not all DBMSs have tools embedded
• No standard measurement
• Security:
– Physical and password security
– Access rights and audit trails
– Data encryption and diskless workstations
37. Database Systems, 8th Edition 37
Implementation and Loading
(continued)
• Backup and Recovery
– Full backup
– Differential backup
– Transaction log backup
• Integrity
– Enforced via proper use of primary, foreign key
rules
• Company standards
– Standards may be partially defined
38. Database Systems, 8th Edition 38
Testing and Evaluation
• Occurs in parallel with applications
programming
• Database tools used to prototype applications
• If implementation fails to meet some of
system’s evaluation criteria:
– Fine-tune specific system and DBMS
configuration parameters
– Modify physical or logical design
– Upgrade software and/or hardware platform
39. Database Systems, 8th Edition 39
Operation
• Once database has passed evaluation stage, it
is considered operational
• Beginning of operational phase starts process
of system evolution
• Problems not foreseen during testing surface
• Solutions may include:
– Load-balancing software to distribute
transactions among multiple computers
– Increasing available cache
40. Database Systems, 8th Edition 40
Maintenance and Evolution
• Required periodic maintenance:
– Preventive maintenance (backup)
– Corrective maintenance (recovery)
– Adaptive maintenance
– Assignment of access permissions and their
maintenance for new and old users
– Generation of database access statistics
– Periodic security audits
– Periodic system-usage summaries
42. Database Systems, 8th Edition 42
Database Design Strategies
• Top-down design
– Identifies data sets
– Defines data elements for each of those sets
• Definition of different entity types
• Definition of each entity’s attributes
• Bottom-up design
– Identifies data elements (items)
– Groups them together in data sets
44. Database Systems, 8th Edition 44
Centralized vs. Decentralized Design
• Centralized design
– When data component is composed of small
number of objects and procedures
– Typical of small systems
• Decentralized design
– Data component has large number of entities
– Complex relations on which complex operations
performed
– Problem spread across several operational sites
47. Database Systems, 8th Edition 47
Centralized vs. Decentralized Design
(continued)
• All modules integrated into one model
• Aggregation problems to be addressed:
• Synonyms and homonyms
• Entity and entity subtypes
• Conflicting object definitions
49. Database Systems, 8th Edition 49
Summary
• Information system facilitates transformation of
data into information
– Manages both data and information
• SDLC traces history (life cycle) of an
application within the information system
• DBLC describes history of database within the
information system
50. Database Systems, 8th Edition 50
Summary (continued)
• Database design and implementation process
moves through series of well-defined stages
• Conceptual design subject to several variations:
– Top-down vs. bottom-up
– Centralized vs. decentralized