final exam review geb thomas. information systems applications

34
Final Exam Review Geb Thomas

Upload: amber-hunter

Post on 17-Jan-2016

221 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Final Exam Review Geb Thomas. Information Systems Applications

Final Exam Review

Geb Thomas

Page 2: Final Exam Review Geb Thomas. Information Systems Applications

Information Systems Applications

Page 3: 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.

Page 4: Final Exam Review Geb Thomas. Information Systems Applications

The Development Components

Page 5: Final Exam Review Geb Thomas. Information Systems Applications

The FAST Development Process

Page 6: Final Exam Review Geb Thomas. Information Systems Applications

Model-Driven Development

Page 7: Final Exam Review Geb Thomas. Information Systems Applications

Rapid Application Development

Page 8: Final Exam Review Geb Thomas. Information Systems Applications

Commercial Off-the-Shelf (COTS) Software Route

Page 9: Final Exam Review Geb Thomas. Information Systems Applications

Requirements AnalysisPhase in Which Found Cost Ratio

Requirements 1

Design 3-6

Coding 10

Development Testing 15-40

Acceptance Testing 30-70

Operation 40-1000

Page 10: Final Exam Review Geb Thomas. Information Systems Applications

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

Page 11: Final Exam Review Geb Thomas. Information Systems Applications

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)

Page 12: Final Exam Review Geb Thomas. Information Systems Applications

Data Modeling

Page 13: Final Exam Review Geb Thomas. Information Systems Applications

Entity Relationship Diagrams

Page 14: Final Exam Review Geb Thomas. Information Systems Applications

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.

Page 15: Final Exam Review Geb Thomas. Information Systems Applications

Non-Specific Relationships

Page 16: Final Exam Review Geb Thomas. Information Systems Applications

Another Non-Specific Relationship

Page 17: Final Exam Review Geb Thomas. Information Systems Applications

Another Non-Specific Relationship

Page 18: Final Exam Review Geb Thomas. Information Systems Applications

Context Data Model

MEMBER ORDER

MEMBER TRANSACTION

PRODUCT

AGREEMENTPROMOTION

responds to

places

binds

is a

hasconducted

generates

features

sells

Page 19: Final Exam Review Geb Thomas. Information Systems Applications

Key-Based Data Model

TRANSACTION

Primary Key

Transaction-Reference-Number [PK1]

MEMBER ORDERED PRODUCT

Primary Key

Order-Number [PK1] [FK]Product-Number [PK2] [FK]

TITLE PROMOTION

Primary Key

Product-Number [PK1] [FK]Promotion-Number [PK2] [FK]

MEMBER ORDER

Primary Key

Order-Number [PK1]

MEMBER

Primary Key

Member-Number [PK1]

PRODUCT

Primary Key

Product-Number [PK1]

AGREEMENT

Primary Key

Agreement-Number [PK1]

PROMOTION

Primary Key

Promotion-Number [PK1]

features

is featured as

sold as

sells

places

binds

is a

hasconducted

respondsto

generates

Page 20: Final Exam Review Geb Thomas. Information Systems Applications

Fully-Attributed Data ModelMEMBER ORDERPrimary Key

Order-Number [PK1]Non-Key Attributes

Order-Creation-DateOrder-Fill-DateMember-NameMember-AddressShipping-Address-NameShipping-Street-AddressShipping-CityShipping-StateShipping-ZipShipping-InstructionsOrder-Sub-TotalOrder-Sales-TaxOrder-Shipping-MethodOrder-Shipping-&-Handling-CostOrder-StatusOrder-Prepaid-AmountOrder-Prepayment-MethodPromotion-Number [FK]Member-Number [FK]Member-Number-1 . Member-Number [FK]Ordered-Product-NumberQuantity-ShippedQuantity-BackorderedOrdered-Product-DescriptionOrdered-Product-TitlePurchased-Unit-PriceExtended-Price

MEMBERPrimary Key

Member-Number [PK1]Non-Key Attributes

Member-NameMember-StatusMember-Street-AddressMember-Post-Office-BoxMember-CityMember-StateMember-Zip-CodeMember-Daytime-Phone-NumberMember-Date-of-Last-OrderMember-Balance-DueMember-Credit-Card-TypeMember-Credit-Card-NumberMember-Credit-Card-Expire-DateMember-Bonus-Balance-AvailableAudio-Category-PreferenceAudio-Media-PreferenceDate-EnrolledExpiration-DateGame-Category-PreferenceGame-Media-PreferenceNumber-of-Credits-EarnedVideo-Category-PreferenceVideo-Media-PreferenceAgreement-Number [FK]Privacy-CodeEmail-Address

PRODUCTPrimary Key

Product-Number [PK1]Non-Key Attributes

"Universal-Product-Code (Alternate Key)"Quantity-in-StockProduct-TypeSuggested-Retail-PriceDefault-Unit-PriceCurrent-Special-Unit-PriceCurrent-Month-Units-SoldCurrent-Year-Units-SoldTotal-Lifetime-Units-Sold

VIDEO TITLEPrimary Key

Product-Number [PK1] [FK]Non-Key Attributes

ProducerDirectorVideo-CategoryVideo-Sub-CategoryClosed-CaptionedLanguageRunning-TimeVideo-Media-TypeVideo-EncodingScreen-AspectMPA-Rating-Code

AUDIO TITLEPrimary Key

Product-Number [PK1] [FK]Non-Key Attributes

ArtistAudio-CategoryAudio-Sub-CategoryNumber-of-Units-in-PackageAudio-Media-CodeContent-Advisory-Code

GAME TITLEPrimary Key

Product-Number [PK1] [FK]Non-Key Attributes

ManufacturerGame-CategoryGame-Sub-CategoryGame-PlatformGame-Media-TypeNumber-of-PlayersParent-Advisory-Code

TRANSACTIONPrimary Key

Transaction-Reference-Number [PK1]Non-Key Attributes

Transaction-DateTransaction-TypeTransaction-DescriptionTransaction-AmountMember-Number [FK]Order-Number [FK]

TITLEPrimary Key

Product-Number [PK1] [FK]Non-Key Attributes

Title-of-WorkTitle-CoverCatalog-DescriptionCopyright-DateEntertainment-CategoryCredit-Value

MERCHANDISEPrimary Key

Product-Number [PK1] [FK]Non-Key Attributes

Merchandise-NameMerchandise-DescriptionMerchandise-TypeUnit-of-Measure

PROMOTIONPrimary Key

Promotion-Number [PK1]Non-Key Attributes

Promotion-Release-DatePromotion-StatusPromotion-TypeProduct-NumberTitle-of-Work

AGREEMENTPrimary Key

Agreement-Number [PK1]Non-Key Attributes

Agreement-Expire-DateAgreement-Active-DateFulfillment-PeriodRequired-Number-of-Credits

MEMBER ORDERED PRODUCTPrimary Key

Order-Number [PK1] [FK]Product-Number [PK2] [FK]

TITLE PROMOTIONPrimary Key

Promotion-Number [PK1] [FK]Product-Number [PK2] [FK]

is featured as

features

sold as

sells

places

binds

is a

hasconducted

respondsto

is ais ais a

is ais a

generates

Page 21: Final Exam Review Geb Thomas. Information Systems Applications

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.

Page 22: Final Exam Review Geb Thomas. Information Systems Applications

Process Modeling

Page 23: Final Exam Review Geb Thomas. Information Systems Applications

A Data Flow Diagram

External Entity

Data Store

Data Flow

Process

Page 24: Final Exam Review Geb Thomas. Information Systems Applications

A Decomposition Diagram

Page 25: Final Exam Review Geb Thomas. Information Systems Applications

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.

Page 26: Final Exam Review Geb Thomas. Information Systems Applications

Problems with DFDs

Page 27: Final Exam Review Geb Thomas. Information Systems Applications

Illegal Data Flows

Page 28: Final Exam Review Geb Thomas. Information Systems Applications

Database Design

Page 29: Final Exam Review Geb Thomas. Information Systems Applications

Files Versus Databases

File

File File

File

InformationSystem

Database (consolidated & integrated

data from files)

InformationSystem

InformationSystem

InformationSystem

InformationSystem

Page 30: Final Exam Review Geb Thomas. Information Systems Applications

Relational Databases

Page 31: Final Exam Review Geb Thomas. Information Systems Applications

Structured Query Language (SQL)

SELECT list_of_columnsFROM 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

Page 32: Final Exam Review Geb Thomas. Information Systems Applications

The Where Clause

• Comparison operators (=, < , >, < >, and so on)• Combinations or logical negations of conditions

(AND, OR, NOT)– Where unitprice < 5000 and unitprice > 2000

• Ranges (Between, Not Between)– Where unitprice between 2000 and 5000

• Lists (In, Not in)– Where state in (‘CA’, ‘IN’, ‘MD’)

Page 33: Final Exam Review Geb Thomas. Information Systems Applications

Study Hard

Good Luck

Page 34: Final Exam Review Geb Thomas. Information Systems Applications