CIS 359 test 2 study guide

CIS 359 test 2 study guide - CIS 359 test 2 study guide...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
CIS 359 test 2 study guide Study Guide Monday, March 24, 2008 10:36 AM SDLC Terms / Concepts System modeling User System Diagram- is icon based, clearly describe user familiar system interfaces/ controls, a gentle introduction to formal system specifications Menu Tree- based on commonly used GUI control interfaces, focuses on actions/commands available to the user, categorizes and groups related system functions System Flow Chart- ISO system components, focuses on relationships between data and software components, identifies configuration management items that must be maintained and controlled. Subsystem- allow more focus on related operations in the context of the whole Data modeling Hierarchical Model - relationship based on parent/child, organizational chart, family tree Network Model - relationship based upon association, telephone network, network of friends or business associates Relational Model- relationships based upon informational content, shared/common descriptive characteristics, identifying facts, formally consistent table structure. Formal mathematics for information operations, relational algebra/calculus, non-procedural relational languages (SQL, QUEL, QBE) Attribute- columns representing simple facts, are atomic, "clusters" based on functional dependency Instance- rows representing related facts, must be "distinguished" in a table Relational Table- tables, attributes, keys, instances Projection- copying columns from tables Selection- copying rows from tables, limited to "join compatible" attributes Join- building new rows by copying rows from two tables based on shared information
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Atomic- attributes are atomic Join compatibility - all connections are based on table Functional dependence- clusters attributes based on functional dependency Key - logically connect information Primary Key - uniquely distinguish rows in a table Foreign Key - identify rows in another table for the purposes of joining Cardinality- relationships associate information found in two or more tables and define cardinality of relationship Normalization- normal forms confirm that the structure of the relational tables protects against various anomalies in retrieval/ update First normal form- all attributes are "atomic", no repeating groups Second normal form- all non-key attributes are determined by the primary key of that table, if the primary key is composite: the whole key Third normal form- There are no "transitive" relationships in any table, dependencies are on the primary key only. Project modeling Risk - Risk=stress, change in controlled risk= improved efficiency and effectiveness, manage risk by avoiding surprises Task - clearly identified units of work, person+"money" +time= task accomplished, tasks prepare the groundwork for other tasks, tasks cannot begun until the groundwork is laid Time and Materials, Two Times Materials, Project Status Chart, Pert Chart - identifies project work in tasks, defines the precedence and dependency of tasks, determines
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 04/07/2008 for the course CS 359 taught by Professor Wagspack during the Spring '08 term at Bentley.

Page1 / 6

CIS 359 test 2 study guide - CIS 359 test 2 study guide...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online