Getting Started in Systems Analysis and Design Appendix F DAVID
M. KROENKE and DAVID J. AUER DATABASE CONCEPTS, 6 th Edition
Slide 2
All rights reserved. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted, in any
form or by any means, electronic, mechanical, photocopying,
recording, or otherwise, without the prior written permission of
the publisher. Printed in the United States of America. Copyright
2013 Pearson Education, Inc. Publishing as Prentice Hall KROENKE
and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson
Education, Inc. Publishing as Prentice Hall F-2
Slide 3
Appendix Objectives To understand information systems To
understand business processes To understand and be able to apply
the systems development life cycle (SDLC) model To understand
business process modeling using Business Processing Modeling
Notation (BPMN) To be able to gather data and information during
Requirements Analysis KROENKE and AUER - DATABASE CONCEPTS (6th
Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-3
Slide 4
Appendix Objectives (continued) To understand use cases To
understand business rules To be able to create a user requirements
document (URD) To be able to create a statement of work (SOW) To
understand how the topics in this document link to chapters in
Database Concepts KROENKE and AUER - DATABASE CONCEPTS (6th
Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-4
Slide 5
Data and Information DataRecorded facts and numbers Information
Knowledge derived from data Data presented in a meaningful context
Data processed by summing, ordering, averaging, grouping, comparing
or other similar operations KROENKE and AUER - DATABASE CONCEPTS
(6th Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-5
Slide 6
Information Systems SystemA set of components that interact to
achieve some purpose or goal Information systemA system that has
the goal of producing information KROENKE and AUER - DATABASE
CONCEPTS (6th Edition) Copyright 2013 Pearson Education, Inc.
Publishing as Prentice Hall F-6
Slide 7
Five Component Information Systems Framework KROENKE and AUER -
DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson Education,
Inc. Publishing as Prentice Hall F-7 Figure F-1: The Five Component
Information System Framework
Slide 8
Competitive Strategy Competitive StrategyA company's organized
response to the industry structure of the industry in which it
operates, and thus, how to compete within that structure KROENKE
and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson
Education, Inc. Publishing as Prentice Hall F-8
Slide 9
Porters Five Forces Model The industry structure is determined
by relative strength or weakness within the industry of: The
bargaining power of customers The availability ("threat") of
substitutable products The bargaining power of suppliers The ease
("threat") of new competitors entering the industry The rivalry
between competitors KROENKE and AUER - DATABASE CONCEPTS (6th
Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-9
Slide 10
Porters Primary or Operational Activities Inbound logistics:
receiving, storing and distributing product inputs Manufacturing
operations: transforming inputs into the final product Outbound
logistics: collecting, storing, and distributing the product to
buyers Sales and marketing: convincing customers to buy the product
and selling it to them Customer service: assisting the customers in
their use of the product KROENKE and AUER - DATABASE CONCEPTS (6th
Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-10
Slide 11
Porters Support Activities Procurement: managing supplier
relationships and buying the product inputs Technology management:
product research and development and new procedures, methods and
techniques Human resources management: managing employee resources
Firm infrastructure management: general management of the firm,
finance, accounting, legal services, and government affairs KROENKE
and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson
Education, Inc. Publishing as Prentice Hall F-11
Slide 12
Business Process Business processA set of activities that
transforms inputs into outputs KROENKE and AUER - DATABASE CONCEPTS
(6th Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-12 Figure F-2: A Generalized Business Process
Slide 13
The Manufacturing Process KROENKE and AUER - DATABASE CONCEPTS
(6th Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-13 Figure F-3: The Manufacturing Process
Slide 14
The Manufacturing Process as it Overlays Porters Operational
Activities KROENKE and AUER - DATABASE CONCEPTS (6th Edition)
Copyright 2013 Pearson Education, Inc. Publishing as Prentice Hall
F-14 Figure F-4: The Manufacturing Process as It Overlays Porter's
Operational Activities
Slide 15
The Manufacturing Process with Supporting Information System
KROENKE and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013
Pearson Education, Inc. Publishing as Prentice Hall F-15 Figure
F-5: The Manufacturing Process with Supporting Information
System
Slide 16
Business Process Modeling Business process modelingThe study
and documentation of business processes Business process modeling
notation (BPMN) A commonly used system for drawing business process
models Microsoft Visio Insights blogMicrosoft Visio Insights blog
Microsoft Visio 2010 Premium has BPMN templateMicrosoft Visio 2010
Premium has BPMN template Object Management Groups Business Process
Management InitiativeObject Management Groups Business Process
Management Initiative KROENKE and AUER - DATABASE CONCEPTS (6th
Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-16
Slide 17
Systems Analysis and Design Systems analysis and designThe
process of creating and maintaining information systems Systems
development life cycle (SDLC)The classic methodology used to in
systems analysis and design to develop information systems. System
definition Requirements analysis Component design Implementation
System maintenance DeliverablesEach step should produce one or more
deliverables, which are the step results. KROENKE and AUER -
DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson Education,
Inc. Publishing as Prentice Hall F-17
Slide 18
The SDLC in Use KROENKE and AUER - DATABASE CONCEPTS (6th
Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-18 Figure F-6: The SDLC in Use
Slide 19
System Definition Step The system definition step is a process
that starts with the need for an information system to support a
business process as its input, and produces a project plan as its
output. During this process, we need to: Define the information
system project goals and scope. Assess the feasibility of the
project (cost, schedule, technical, organizational). Form the
project team. Plan the project (specify tasks, assign personnel,
determine task dependencies, set schedules). KROENKE and AUER -
DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson Education,
Inc. Publishing as Prentice Hall F-19
Slide 20
Requirements Analysis Step The requirements analysis step is a
process that starts with the project plan as its input, and
produces a set of approved user requirements as its output. During
this step we need to: Conduct user interviews. Evaluate existing
systems. Determine needed new forms/reports/queries. Identify
needed new application features and functions. Consider security.
Create the data model. Consider the five components of an
information system - hardware, software, data, procedures, and
people KROENKE and AUER - DATABASE CONCEPTS (6th Edition) Copyright
2013 Pearson Education, Inc. Publishing as Prentice Hall F-20
Slide 21
Requirements Analysis Step Deliverables The requirements
analysis deliverables may include: Data model User requirements
document (URD) Statement of Work (SOW) KROENKE and AUER - DATABASE
CONCEPTS (6th Edition) Copyright 2013 Pearson Education, Inc.
Publishing as Prentice Hall F-21
Slide 22
Component Design Step The component design step is a process
that starts with the approved user requirements as its input, and
produces a final system design as its output. During this step we
need to: Determine hardware specifications Determine program
(software) specifications Create the database design Design
business procedures Create job descriptions for business personnel
KROENKE and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013
Pearson Education, Inc. Publishing as Prentice Hall F-22
Slide 23
Component Design Step Deliverables The component design
deliverables may include: Database design Documented system design
KROENKE and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013
Pearson Education, Inc. Publishing as Prentice Hall F-23
Slide 24
Implementation Step The implementation step is a process that
starts with the final system design as its input, and produces a
final system as its output. During this step we need to: Build
system component Conduct component tests Integrate the components
Conduct integrated component tests Convert to the new system The
implementations deliverable is: The installed information system,
including a Database KROENKE and AUER - DATABASE CONCEPTS (6th
Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-24
Slide 25
The SDLC Design and Implementation Steps for the Five
Information System Components KROENKE and AUER - DATABASE CONCEPTS
(6th Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-25 Figure F-8: The SDLC Design and Implementation
Steps for the Five Information System Components
Slide 26
System Maintenance Step The system maintenance step is a
process that starts with the implemented system as its input, and
produces an update system or a request for system modification
using the SDLC as its output. During this step we need to: Update
the system with patches, service packs, and new software releases
Record and prioritize requests for system changes or enhancements.
KROENKE and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013
Pearson Education, Inc. Publishing as Prentice Hall F-26
Slide 27
Project Scope Project scopeThe work that must be done to
provide a product, service, or result to the customer with the
specified functions and features KROENKE and AUER - DATABASE
CONCEPTS (6th Edition) Copyright 2013 Pearson Education, Inc.
Publishing as Prentice Hall F-27
Slide 28
Use Cases Use casesDescriptions of the ways users will employ
the features and functions of the new information system A use case
consists of a description of the roles users will play when
utilizing the new system, together with descriptions of activity
scenarios. Inputs provided to the system and outputs generated by
the system are defined. Use cases provide sources of requirements
and also can be used to validate the data model, database design,
and implementation. KROENKE and AUER - DATABASE CONCEPTS (6th
Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-28
Slide 29
Use Cases in Microsoft Visio 2010 KROENKE and AUER - DATABASE
CONCEPTS (6th Edition) Copyright 2013 Pearson Education, Inc.
Publishing as Prentice Hall F-29 Figure F-9: The Microsoft Visio
2010 UML Use Case Diagram
Slide 30
Business Rules Business rules are constraints on database
activities. Generally, such rules arise from business policy and
practice. KROENKE and AUER - DATABASE CONCEPTS (6th Edition)
Copyright 2013 Pearson Education, Inc. Publishing as Prentice Hall
F-30
Slide 31
User Requirements Document (URD) A deliverable for requirements
analysis is an approved set of user requirements as a user
requirements document (URD). Typically a URD may contain: A table
of contents A revision history An introduction A general
description of the project (including project assumptions and
dependencies) A data model Functional requirements Non-functional
requirements (speed and time, capacity and reliability) Project
delivery requirements KROENKE and AUER - DATABASE CONCEPTS (6th
Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-31
Slide 32
Statement of Work (SOW) Typically a SOW may contain
descriptions of: A history of the problem or need that generated
the project An identification of the client for the work An
identification of who will do the work The scope of the work to be
done The objectives of the work to be done Any constraints on the
work to be done The location of the work (where the work will be
done) KROENKE and AUER - DATABASE CONCEPTS (6th Edition) Copyright
2013 Pearson Education, Inc. Publishing as Prentice Hall F-32
Slide 33
Statement of Work (SOW) (Contd) A set of tasks with an
associated timeline: An outline of the tasks that will make up the
work to be done The time period for the work (start date, finish
date, details about how many hours may be worked, etc.) A
deliverables schedule Criteria for determining whether the project
has been successfully completed A payment schedule Signature blocks
to record acceptance of the SOW by all parties KROENKE and AUER -
DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson Education,
Inc. Publishing as Prentice Hall F-33
Slide 34
Highline University: Sample College Report KROENKE and AUER -
DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson Education,
Inc. Publishing as Prentice Hall F-34 Figure F-11: The Highline
University Sample College Report
Slide 35
Highline University: Data Model for Sample College Report
KROENKE and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013
Pearson Education, Inc. Publishing as Prentice Hall F-35 Figure
F-12: Data Model for the Sample College Report
Slide 36
Highline University: Sample Department Report KROENKE and AUER
- DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson Education,
Inc. Publishing as Prentice Hall F-36 Figure F-13: The Highline
University Sample Department Report
Slide 37
Highline University: Data Model Using 1:N Relationship KROENKE
and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson
Education, Inc. Publishing as Prentice Hall F-37 Figure F-14: Data
Model Using N:M Relationships
Slide 38
Highline University: Data Model Using N:M Relationship KROENKE
and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson
Education, Inc. Publishing as Prentice Hall F-38 Figure F-15: Data
Model Using 1:N Relationships
Slide 39
Highline University: Data Model Using an Association Pattern
KROENKE and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013
Pearson Education, Inc. Publishing as Prentice Hall F-39 Figure
F-16: Data Model Using an Association Pattern
Slide 40
Highline University: Data Model Using an Association Pattern
and a 1:N Relationship KROENKE and AUER - DATABASE CONCEPTS (6th
Edition) Copyright 2013 Pearson Education, Inc. Publishing as
Prentice Hall F-40 Figure F-17: Data Model Using an Associations
Pattern and a 1:1 Relationship
Slide 41
Highline University: Sample Department Student Report KROENKE
and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson
Education, Inc. Publishing as Prentice Hall F-41 Figure F-18: The
Highline University Sample Department Student Report
Slide 42
Highline University: Data Model with STUDENT Entity KROENKE and
AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson
Education, Inc. Publishing as Prentice Hall F-42 Figure F-19: Data
Model with STUDENT Entity
Slide 43
Highline University: Sample Department Student Report KROENKE
and AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson
Education, Inc. Publishing as Prentice Hall F-43 Figure F-20: The
Highline University Sample Student Acceptance Letter
Slide 44
Highline University: Data Model with STUDENT Entity KROENKE and
AUER - DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson
Education, Inc. Publishing as Prentice Hall F-44 Figure F-21: Data
Model Using an Advises Relationship
Slide 45
Highline University: The Final Data Model KROENKE and AUER -
DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson Education,
Inc. Publishing as Prentice Hall F-45 Figure F-22: Final Data
Model
Slide 46
Highline University: The Database Design KROENKE and AUER -
DATABASE CONCEPTS (6th Edition) Copyright 2013 Pearson Education,
Inc. Publishing as Prentice Hall F-46 Figure F-23: Highline
University Database Design
Slide 47
Getting Started in Systems Analysis and Design End of
Presentation on Appendix F DAVID M. KROENKE and DAVID J. AUER
DATABASE CONCEPTS, 6 th Edition