Midterm Flashcards

1
Q

What are the major SDLC phases?

A

1) Conceptual/Preliminary Analysis
2) Requirements
3) Design
4) Development or Implementation
5) Testing
6) Deploy

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

Whats the difference between a group and a team?

A

Group: two or more people who interact with each other to accomplish a goal.
Team: a group that works intensively together to achieve a common goal through
-Coordinated effort
-Common goals instead of individual goals
-Mutual accountability in addition to individual
-Complementary skills and interdependence
-Leadership shared among team members

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

What types of teams are there?

A

Hierarchal Teams, Chief Programmer Teams, Matrix Organization, and Democratic/Open-Structured Teams

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

What is the relational-economic view of motivation?

A

People are motivated by monetary considerations. Managers make all of the decisions. There are penalties to ensure compliance which results in fear. There are many levels of structure with limited span for control.

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

What is the social view of motivation?

A

People are motivated by social needs. The work is typically not meaningful in itself. Control is exercised through group pressure.

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

What is the self-actualization view of motivation?

A

Motivation comes from within one’s self. Managers typically frame a problem, not a solution. Organization structure facilitates by does not control. The rewards are intrinsic within the work.

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

Name Maslow’s hierarchy of needs

A
  • Self-actualization (Continued self-improvement and growth)
  • Ego (Status, recognition, prestige)
  • Social (Belonging and Acceptance)
  • Safety (safety from danger, deprivation)
  • Physiological (Water, food)
  • *The lowest unfulfilled needs act as the motivatior
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What makes up a good task?

A
  • Description of what is to be done
  • An estimate of how long it will take to complete
  • An identified responsible party to complete
  • Pre-constraints
  • Co-constraints
  • Post-constraints
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is a Covey Board?

A

A 4 quadrant table that lists what is “important vs. not important” and “urgent vs. not urgent”

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

What is a KanBan?

A

Often uses wipe boards or sticky notes: it shows what is “to do,” “doing,” and “done.”

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

What is a Gnatt Chart?

A

(Think Wrike) It shows the effort needed for each task as well as the dependancies that each task has on one another.

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

What is Brook’s Law?

A

“Adding people resources to a late software project makes it later.”

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

What do the number of month’s a project is going to take depend on?

A

The sequentiality of the tasks and the number of independent partitionable subtasks .

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

How does a large software project end up being a year late?

A

Answer: One day at a time…

  • Incremental slippages on many fronts eventually accumulate to produce a large overall delay.
  • Continued attention to meeting small individual milestones is required at each level of management.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What 3 things are part of the “triangle?”

A

time, resources, features

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

Concept

A

the problem

17
Q

Requirements

A

what we need to do to solve the problem

18
Q

Design

A

how we will solve the problem

19
Q

Construct

A

build the solution

20
Q

Test

A

verify that we have solved the problem

21
Q

Deploy

A

problem solved

22
Q

What are 5 types of requirements? (Give examples of each)

A

1) Functional Requirements (The system must…)
2) Non-Functional Requirements (quality attributes, constraints, performance goals, business rules)
3) Business Requirements (high-level objectives of the client)
4) User Requirements (define user goals or tasks)
5) Business Rules (not a software requirement per se, but impacts requirements)

23
Q

What is the Requirements Lifecycle?

A

Elicit, analysis, specification, verification

24
Q

How do you know if you have excellent requirements? What do they need to be?

A

Complete, Correct, Feasible, Necessary, Prioritized, Unambiguous, Verifiable

25
Q

What are SMART/SMART-CC requirements?

A
S: Specific
M: Measurable
A: Attainable
R: Realistic
T: Time-bound
|
C: Complete
C: Concise
26
Q

What do you need in a full use-case?

A

number, name, description, actors, triggers, pre-conditions, post-conditions, normal flow, alternate flows

27
Q

Describe a context diagram

A

A high-level diagram that shows the entire system and the data flows between it and external entities. The system is shown as a circle typically in the middle, and the outside entities/terminators that you are getting data from are rectangles with arrows showing data flow.

28
Q

Describe a data flow diagram

A

Data flow diagrams help us identify all of the functions of the system down to a very low level. It is simple yet abstract. It shows processes that transform data, external entities, data flows, and data stores. Processes communicate via data stores, not with each other directly.

29
Q

What are some characteristics of Agile scrum?

A
  • Self-organizing teams
  • Product progresses in a series of month-long “sprints”
  • Requirements are captured as items in a list of “product - backlog”
  • No specific engineering practices prescribed
  • Uses generative rules to create an agile environment for delivering projects
  • One of the “agile processes”
30
Q

What does the product owner of scrum do?

A
  • Define the features of the product
  • Decide on release date and content
  • Beresponsible for the profitability of the product (ROI)
  • Prioritize features according to market value
  • Adjustfeatures and priority every iteration, as needed
  • Accept or reject work results
31
Q

What does the scrum mater do?

A
  • Represents management to the project
  • Responsible for enacting Scrum values and practices
  • Removes impediments
  • Ensure that the team is fully functional and productive
  • Enable close cooperation across all roles and functions
  • Shield the team from external interferences
32
Q

What is a scrum product backlog?

A

The requirements and a list of all desired work on the project. It is ideally expressed such that each item has value to the users or customers of the product and is prioritized by the product owner and reprioritized at the start of each sprint.

33
Q

What are user stories?

A

They represent functionality that will be useful to the user and do not include technical details or jargon.