Exam 10/16 Flashcards

1
Q

What skills are needed as a Project Manager?

A
Communication/Good Listener
Organization/Time Management
Big Picture: Business goals and strategies
Delegate, MOtivate
Adaptive
Sales 101
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the five stages to managing a product?

A

Initiate, Plan, Monitor and Control, Implement, and Close

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What three things should be done in the initiation stage of a project?

A

SWOT
Feasibility
Sell to CFO

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the four types of feasibility that a project manager should look at?

A

Economic
Operational
Schedule
Technical

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the quadruple constraint?

A

Time
Scope
Cost
Quality in the middle as a factor of all three

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is SDLC?

A

Systems Development Life Cycle: Waterfall

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Waterfall Methodology

A
  1. Planning (Project initiation, Project Management)
  2. Analysis (What is the new system trying to solve about the current system?)
  3. Design (Logical Design, Physical Design)
  4. Implementation(Developed or Purchased)
  5. System
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Disadvantages of the Waterfall Methodology

A

Sequential process, cannot go back
No overlap in stages

Only works when:
Requirements are stable
Technology is well known and mature
Everything happens as one would expect
We have done this before

Many people use a modifed SDLC, CAN go back

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is the number one reason why projects fail?

A

Poor requirements management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are four alternatives to the SDLC?

A

Prototyping
Joint Application Design
Rapid Application Development
Agile Methodologies

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Prototyping

A

Designing a sample of a product and going back and forth between design and customer until it is perfect.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

RAD

A

Methodology to decrease design and implementation time
Involves: prototyping, JAD, CASE tools, and code generators

Requirements Planning ->
User Design -> <-
Cutover

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Agile Methodologies

A

Software development as fluid, unpredictable, and dynamic.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are the three main principles of Agile Methodologies?

A
  1. Adaptive rather than predictive
  2. Emphasize people rather than roles
  3. Self-adaptive processes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Data Model

A

A plan, or blueprint, for a database design.

Is more generalized and abstract than a database design.

It is easier to change a data model than it is to change a database design, so it is the appropriate place to work through conceptual database problems.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

ER-Model

A

A set of concepts and graphical symbols that can be used to create conceptual schemas.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Entity

A

Something that can be identified and the users want to track

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Entity Class

A

A collection of entities of a given type/ a description of the structure and format of the occurrences of the entity
i.e. Customer entity class

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Entity Instance

A

The occurrence of a particular entity
i.e. If customer was the class:

Instance:
John Doe
603-508-1158
j.doe@wildcats.unh.edu

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Attributes

A

Entities have attributes that describe the entity’s characteristics.
Attributes have a data type and properties

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Identifiers

A

Attributes that name, or identify, entity instances.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Composite Identifiers

A

Identifiers that consist of two or more attribute

23
Q

Relationship

A

How entities are associated with each other

24
Q

Degree

A

The number of entity classes in a relationship

25
Maximum Caridinalitiy
The maximum number of entity instances that *can* participate in a relationship.
26
Minimum Caridinality
The minimum number of entity instances that *must* participate in a relationship.
27
Parent Entity
Employe-|-|----------|-
28
Data Modeling Notation
a) ---------- Original ER Model b)--|------------------< Crow's Foot Model c) ---------------------1..* Viso Model
29
Identifying Relationship
If an entity depends on the parent entity for its existence, than it is an identifying relationship and it is identified by a SOLID line
30
Weak Entity
An entity whose existence depends upon another entity DOES NOT have to be an identifying relationship Can be ID-Dependent or Non-ID-Dependent
31
Subtypes
Sex ------> male -------> female This is exclusive, subtypes can be inclusive
32
Why do we have to capture cardinality of relationships?
Cardinality enforces business rules
33
Discriminator
Decides which subtype the person fulls into in an exclusive setting
34
Three types of anomolies
Deletion Anomaly: When we delete one row, the structure of this table forces us to lose facts about tow different things Insertion Anomaly: the structure of this table forces us to enter facts about different things when we only want to enter facts about one Update Anomaly: the structure of this table forces us to update multiple places
35
Normalization
Primarily a tool to validate and improve a design so that it satisfies certain constraints that avoid anomalies The process of decomposing relations with anomalies to produce smaller, well-structured relations
36
Functional Dependency
Occurs when the value of one or many attributes determines the value of a one or many secondary attributes.
37
Determinant
Attribute on the left side of a functional dependency
38
Composite Determinant
A determinant of a functional dependency that consists of more than one attribute (StudentName, ClassName) -> (Grade)
39
Unique Determinant
A determinant is unique in a relation if, and only if, it determines every other column in the relation
40
Key
A combination of one or more columns that is used to identify rows in a relation
41
Candidate Key
A key that determines all of the other columns in a relation
42
Primary Key
A candidate key selected as the primary means of identifying rows in a relation:
43
Surrogate Key
Arbitrary key value (propertyID)
44
Foreign Key
The primary key of one relation that is placed in another relation to form a link between the relations. Primary key of one side always put as foreign key in many side.
45
Referential Integrity
The foreign key must be in the primary key table
46
Boyce-Codd Normal Form
Every determinant is a primary key
47
Multi-valued Dependency
occurs when a determinant determines a particular set of values: Employee -> Degree Employee -> Sibling PartKit -> Part Always put them in their OWN relation
48
4th Normal Form
BCNF with no multi-valued dependencies
49
1st Normal Form
Meets the definition of a relation
50
2nd Normal Form
No partial dependencies
51
3rd Normal Form
No transitive dependencies
52
Partial Dependency
Part of a primary key determines another attribute, but not the whole key
53
Transitive Dependency
The primary key determines one attribute, and that attribute determines another attribute in the table
54
Difference between BCNF and 3NF
BCNF- All determinants HAVE to be unique