cecs 343 final

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/44

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

45 Terms

1
New cards

method

Acceptable calls (atm machine - accept card, read card, etc)

2
New cards

interface

signature (name, parameters , return type)

3
New cards

Client object

sends message asks for service

4
New cards

Server object

provides service returns result

5
New cards

composition

use variables that reference other objects (diamond) has a

6
New cards

inheritance

inherits common properties (arrow) is a

7
New cards

process-oriented

what to do next which way to flow

8
New cards

object oriented

break up into tasks

9
New cards

dependency relationship

a connection between classes where one relies on the functionality of another.

10
New cards

generalization relationship

a connection that defines a hierarchy, where one class is a specialized version of another, inheriting attributes and behaviors.

11
New cards

association relationship

a connection between classes that allows them to communicate and interact without implying a dependency.

12
New cards

ocp(open closed) principle

classes should be open for extension but closed to modification

13
New cards

liskov substitution

derived classes must be substitutable for their base classes

14
New cards

isp

principle states that no client should be forced to depend on methods it does not use.

15
New cards

dip(dependency inversion)

the principle that depends on abstractions, not concretions, to reduce coupling between modules.

16
New cards

synchronous operation

two bubbles are connected directly

17
New cards

asynchronous operation

teo bubbles connected by data store

18
New cards

good implementation

Readability

•Maintainability

• Performance

• Traceability

• Correctness

• Completeness

19
New cards

method size

should be less than 50 lines when possible

20
New cards

4 phases of debugging

1. Stabilization/reproduction (output is a

minimal test case that causes the error,

don’t need to look at code)

2. Localization (find in code)

3. Correction

4. Verification

21
New cards

golden rules of user interface design

  1. place user in control

  2. reduce the users memory load

  3. design consistent user interface

22
New cards

software arch

a set of high-level decisions that determine the structure of the solution. Not a phase of devolpment. Software architecture provides a set of well-known solutions that are proven to work for similar

problems

23
New cards

module decomposition veiw

top down refinement

24
New cards

dependency veiw

how parts relate to eachother

25
New cards

components

processing element that do the work, input into output

26
New cards

connectors

enable communication between components, pipe data streams

27
New cards

interfaces

connection points on connecters and components

28
New cards

configurations

arrangements of connectors and components that form an arc

29
New cards

bugs estimate

10-50 every 1000 lines

30
New cards

one fp =

60 lines of oop code

31
New cards

fps per person one month estimate

12 fps

32
New cards

errors per fp analysis and design review

3

33
New cards

errors per fp unit and integration testing

4

34
New cards

inspection

visual review of product

35
New cards

review

meeting where project is presented

36
New cards

walkthrough

lead through products and ask questions

37
New cards

annual cost of defects in us

59 billion

38
New cards

rework dev cost

44 %

39
New cards

Fagans six major steps

Planning

2. Overview

3. Preparation

4. Examination

5. Rework

6. Follow-up

40
New cards

5 types of reveiws

Management Reviews

• Technical Reviews

• Inspections (Formal Peer Review)

• Walk-throughs

• Audits

41
New cards
42
New cards
43
New cards
44
New cards
45
New cards