Final Exam Review Geb Thomas. Information Systems Applications.

Slides:



Advertisements
Similar presentations
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Advertisements

Lecture-7/ T. Nouf Almujally
Alternative Approach to Systems Analysis Structured analysis
Using Data Flow Diagrams
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Using Dataflow Diagrams
Copyright Irwin/McGraw-Hill Data Modeling Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten & L. D. Bentley.
Systems Analysis and Design 9th Edition
Modeling the Data: Conceptual and Logical Data Modeling
Lesson-10 Information System Building Blocks(2)
Systems Analysis Requirements structuring Process Modeling Logic Modeling Data Modeling  Represents the contents and structure of the DFD’s data flows.
CATEGORIES OF INFORMATION There are three main categories of business information,and these are related to the purpose for which the information is utilized.
Lesson-20 Data Modeling and Analysis(2)
PROCESS MODELING Transform Description. A model is a representation of reality. Just as a picture is worth a thousand words, most models are pictorial.
Review Questions Model-driven development techniques emphasize the drawing of models to help visualize and analyse problems, define business requirements,
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Lecture Fourteen Methodology - Conceptual Database Design
Data Modeling Entity - Relationship Models. Models Used to represent unstructured problems A model is a representation of reality Logical models  show.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Modern Systems Analysis and Design Third Edition
Lesson-7 Players in the Systems Game
Lesson-19 Data Modeling and Analysis
Karolina Muszyńska Based on
System Analysis and Design
Conventional Files Versus the Database
Lesson-21Process Modeling Define systems modeling and differentiate between logical and physical system models. Define process modeling and explain its.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education 4-1.
SYSTEMS ANALYSIS. Chapter Five Systems Analysis Define systems analysis Describe the preliminary investigation, problem analysis, requirements analysis,
BIS310: Week 7 BIS310: Structured Analysis and Design Data Modeling and Database Design.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Entity-Relationship Design
Computer System Analysis Chapter 10 Structuring System Requirements: Conceptual Data Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 9.1.
Describing Methodologies PART II Rapid Application Development*
Chapter 9 Designing Databases Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Information Systems: Databases Define the role of general information systems Describe the elements of a database management system (DBMS) Describe the.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
Lecture 12 Designing Databases 12.1 COSC4406: Software Engineering.
10/3/2012ISC329 Isabelle Bichindaritz1 Logical Design.
1/26/2004TCSS545A Isabelle Bichindaritz1 Database Management Systems Design Methodology.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
5-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 4 Database Processing Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall 4-1.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
CIS 210 Systems Analysis and Development Week 6 Part II Designing Databases,
Databases Shortfalls of file management systems Structure of a database Database administration Database Management system Hierarchical Databases Network.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Midterm Review Information System Design. Topics Covered Chpt 8: Process Modeling Chpt 9: Feasibility Analysis Chpt 10: Systems Design Chpt 12: Database.
IFS310: Module 6 3/1/2007 Data Modeling and Entity-Relationship Diagrams.
Create Databases for Web Applications Database normalization. Classwork/Homework: determine teams for basic projects explain and enhance assignment.
1 6 C H A P T E R REQUIREMENTS DISCOVERY. 2 Chapter Six Requirements Discovery Define system requirements and differentiate between functional and nonfunctional.
Programming Logic and Design Fourth Edition, Comprehensive Chapter 16 Using Relational Databases.
Creating Databases Data normalization. Integrity and Robustness. Work session. Homework: Prepare short presentation on enhancement projects. Continue working.
Chapter 2 Relational Database Design and Normalization August
Information Access Mgt09/12/971 Entity-Relationship Design Information Level Design.
Systems Analysis and Design 8th Edition
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Main tasks of system analysis ? 1-study exit=sting information system 2-identify problem 3-spelify system requirement 4-asalysis decision ========= How.
Logical Design 12/10/2009GAK1. Learning Objectives How to remove features from a local conceptual model that are not compatible with the relational model.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 6 Modeling the Data: Conceptual and Logical Data Modeling.
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Data normalization. Integrity and Robustness.
System Design.
Lecture on Data Modeling and Analysis
Final Exam Review Geb Thomas.
Why Study Databases? Databases have incredible value to businesses.
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Presentation transcript:

Final Exam Review Geb Thomas

Information Systems Applications

Players in the Game System owners pay for the system to be built and maintained. System users use the system to perform or support the work to be completed. System designers design the system to meet the users’ requirements. System builders construct, test, and deliver the system into operation. Systems analysts facilitate the development of information systems and computer applications by bridging the communications gap that exists between nontechnical system owners and users and technical system designers and builders. IT vendors and consultants sell hardware, software, and services to businesses for incorporation into their information systems.

The Development Components

The FAST Development Process

Model-Driven Development

Rapid Application Development

Commercial Off-the-Shelf (COTS) Software Route

Requirements Analysis Phase in Which FoundCost Ratio Requirements1 Design3-6 Coding10 Development Testing15-40 Acceptance Testing30-70 Operation

The Ishikawa diagram is a graphical tool used to identify, explore, and depict problems and the causes and effects of those problems. It is often referred to as a cause-and-effect diagram or a fishbone diagram. Fishbone Diagram

Joint Requirements Planning (JRP) Joint requirements planning (JRP) is a process whereby highly structured group meetings are conducted for the purpose of analyzing problems and defining requirements. JRP is a subset of a more comprehensive joint application development or JAD technique that encompasses the entire systems development process. Participants Sponsor Facilitator Users and Managers Scribes I.T. Staff (These folks don’t contribute, unless spoken to)

Data Modeling

Entity Relationship Diagrams

Important Entity Concepts An entity is a class of persons, places, objects, events, or concepts about which we need to capture and store data. An attribute is a descriptive property or characteristic of an entity. Synonyms include element, property, and field. The data type for an attribute defines what type of data can be stored in that attribute. The domain of an attribute defines what values an attribute can legitimately take on. The default value for an attribute is the value that will be recorded if not specified by the user. Relationships Cardinality: minimum and maximum number of occurrences of one entity that may be related to a single occurrence of the other entity Degree: the number of entities that participate in the relationship.

Non-Specific Relationships

Another Non-Specific Relationship

Context Data Model MEMBER ORDER MEMBER TRANSACTION PRODUCT AGREEMENTPROMOTION responds to places binds is a has conducted generates features sells

Key-Based Data Model

Fully-Attributed Data Model

Data Normalization An entity is in first normal form (1NF) if there are no attributes that can have more than one value for a single instance of the entity. Any attributes that can have multiple values actually describe a separate entity, possibly an entity and relationship. An entity is in second normal form (2NF) if it is already in 1NF and if the values of all nonprimary key attributes are dependent on the full primary key—not just part of it. Any nonkey attributes that are dependent on only part of the primary key should be moved to any entity where that partial key is actually the full key. This may require creating a new entity and relationship on the model. An entity is in third normal form (3NF) if it is already in 2NF and if the values of its nonprimary key attributes are not dependent on any other non- primary key attributes. Any nonkey attributes that are dependent on other nonkey attributes must be moved or deleted. Again, new entities and relationships may have to be added to the data model.

Process Modeling

A Data Flow Diagram External Entity Data Store Data Flow Process

A Decomposition Diagram

Types of Events A function is set of related and ongoing activities of a business. An event (or transaction) is a logical unit of work that must be completed as a whole (as part of a function). An elementary process (or primitive process) is a discrete, detailed activity or task required to respond to an event. Usually, several such tasks must be completed to respond to an event.

Problems with DFDs

Illegal Data Flows

Database Design

Files Versus Databases File Information System Database (consolidated & integrated data from files) Information System Information System Information System Information System

Relational Databases

Structured Query Language (SQL) SELECT list_of_columns FROM tables[s] [WHERE search_conditions] SELECT * FROM products (* means all columns) SELECT ProductName, Unitprice * UnitsOnOrder as [Ordered Amount] FROM products WHERE UnitsOnOrder > 0 SELECT ‘The highest price is ’, max(unitprice) FROM Products

The Where Clause Comparison operators (=,,, and so on) Combinations or logical negations of conditions (AND, OR, NOT) –Where unitprice 2000 Ranges (Between, Not Between) –Where unitprice between 2000 and 5000 Lists (In, Not in) –Where state in (‘CA’, ‘IN’, ‘MD’)

Study Hard Good Luck