SE Final

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

1/48

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.

49 Terms

1
New cards

Architecture

Helps in stakeholder communication, system analysis, and large-scale reuse.

2
New cards

MVC

Architectural pattern that separates data, view, and controller; good for multi-view systems.

3
New cards

Layered Architecture

Functionality divided into layers, allowing for easier replacement but may impact performance.

4
New cards

Repository Pattern

Centralized data access pattern; effective for data-driven systems but poses a single point of failure.

5
New cards

Client-Server Architecture

Distributed services model where performance depends on network and servers are points of failure.

6
New cards

Performance (Architecture Impact)

Achieved by localizing operations in software design.

7
New cards

Security (Architecture Impact)

Enhanced through layered architecture.

8
New cards

Safety (Architecture Impact)

Obtained by isolating critical subsystems.

9
New cards

Availability (Architecture Impact)

Ensured through redundancy in system design.

10
New cards

Maintainability (Architecture Impact)

Improved through small, replaceable components in architecture.

11
New cards

Build or Buy Decision

Choosing between off-the-shelf products to reduce time/cost versus designing custom solutions.

12
New cards

Design Process

Involves object identification which is often hard and iterative.

13
New cards

Static Models

Models that represent the structure of a system.

14
New cards

Dynamic Models

Models that represent interactions within a system.

15
New cards

Observer Pattern

Design pattern used for synchronizing views when data changes.

16
New cards

Façade Pattern

Design pattern that simplifies interfaces for easier interaction.

17
New cards

Iterator Pattern

Standard design pattern for data access.

18
New cards

Decorator Pattern

Design pattern to add behavior to objects at runtime.

19
New cards

Implementation Focus

Emphasizes reuse, configuration management, and host-target setup.

20
New cards

Reuse Levels

Levels include Abstraction, Object, Component, System.

21
New cards

GPL License

Requires derived works to be open-sourced.

22
New cards

LGPL License

Allows linking without the obligation to open-source own code.

23
New cards

BSD License

Has no obligations to open source software.

24
New cards

Goals of Software Testing

To validate that requirements are met and to detect defects.

25
New cards

Types of Testing

Include development, release, and user testing.

26
New cards

Verification

Asks if we are building the product correctly.

27
New cards

Validation

Asks if we are building the right product.

28
New cards

Inspections

Static testing methods that find anomalies without code execution.

29
New cards

Automated Testing

Utilizes tools like JUnit for fast feedback in software testing.

30
New cards

Test Partitioning

Grouping similar inputs to enhance testing efficiency.

31
New cards

Guideline-based Testing

Testing that checks known patterns where bugs occur.

32
New cards

Interface Testing

Involves testing boundaries, null inputs, and invalid calls.

33
New cards

Use-case Testing

Simulates real-world usage scenarios for effective testing.

34
New cards

Test Driven Development (TDD)

A development approach where tests are written before the actual code is developed.

35
New cards

Regression Testing

The practice of re-running tests after changes to ensure no new defects are introduced.

36
New cards

Types of Maintenance

Include Corrective, Adaptive, and Perfective maintenance strategies.

37
New cards

Reengineering

Total overhaul of a system for better maintainability.

38
New cards

Refactoring

Continuous improvement of software without changing its external behavior.

39
New cards

Legacy System Strategies

Include Scrap, Maintain, Reengineer, and Replace options.

40
New cards

Maintenance Cost Factors

Include program age, team skill, and system complexity.

41
New cards

Project Success Criteria

Defined by being on time, on budget, and meeting expectations.

42
New cards

Project Risks

Include delays, staff issues, defects, and tool failures.

43
New cards

Risk Process Steps

Include Identify, Analyze, Plan, and Monitor.

44
New cards

People Management in Projects

Focuses on respect, honesty, inclusion, and cohesion to build better teams.

45
New cards

Project Plan Components

Includes risk plan, validation plan, schedule, and resources.

46
New cards

Scheduling Issues

Focused on task breakdown, dependencies, milestones, and delays.

47
New cards

Cost Estimation Methods

Include experience-based judgment and empirical models like COCOMO 2.

48
New cards

COCOMO 2 Models

Include models for application composition, early design, reuse, and post-architecture.

49
New cards

Effort and Duration Estimation

Utilizes formulas based on project size to estimate required staff and time.