SEFE

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

1/41

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.

42 Terms

1
New cards

Architectural Design

A critical step in software engineering that defines the structure of software systems, facilitating stakeholder communication and system analysis.

2
New cards

Repository Pattern

Data in the system is managed in a central repository accessible by all components to ensure shared data access.

3
New cards

Client-Server Pattern

System functionality is organized into services provided by separate servers which clients access for functionality.

4
New cards

Software Design

A creative activity where software components and their relationships are identified based on customer requirements.

5
New cards

Implementation

The process of realizing the software design as a working program.

6
New cards

Build or Buy Decision

Choosing whether to develop custom software or to purchase off-the-shelf systems that can be adapted.

7
New cards

Design Model

A representation showing objects, classes, and the relationships between them.

8
New cards

Design Pattern

A reusable solution to a commonly occurring problem in software design.

9
New cards

Abstraction Level Reuse

Reusing knowledge about successful abstractions in software development.

10
New cards

Object Level Reuse

Reusing objects directly from a library.

11
New cards

Component Level Reuse

Reusing collections of objects and classes.

12
New cards

System Level Reuse

Reusing entire application systems.

13
New cards

GNU General Public License (GPL)

A reciprocal license requiring software that uses GPL-licensed code to also be open source.

14
New cards

GNU Lesser General Public License (LGPL)

Allows linking with open-source code without needing to publish your own source.

15
New cards

Berkeley Standard Distribution (BSD) License

A non-reciprocal license that does not require publishing changes and allows proprietary use.

16
New cards

Testing

A process aimed at determining whether a software program meets specified requirements and discovering defects.

17
New cards

Defect Testing

Focuses on identifying incorrect or undesirable software behavior.

18
New cards

Verification

The process of determining if the product is built according to specifications.

19
New cards

Validation

The process of ensuring the product meets user needs.

20
New cards

Software Inspections

An analysis technique used for validating software without requiring execution.

21
New cards

Development Testing

Testing conducted during development to find errors and defects.

22
New cards

Unit Testing

Testing of individual components in isolation.

23
New cards

Component Testing

Testing interfaces between combined units.

24
New cards

System Testing

Testing the complete integrated system functionality.

25
New cards

Release Testing

Testing conducted by a separate team on a complete system version before it is released.

26
New cards

User Testing

Testing conducted by actual users to evaluate the system in their environment.

27
New cards

Alpha Testing

Testing performed at the developer’s site with internal users.

28
New cards

Beta Testing

A release made available to a select group of users for feedback before full launch.

29
New cards

Acceptance Testing

Conducted to determine if the software is ready for deployment.

30
New cards

Regression Testing

Testing to ensure that changes haven’t disrupted previously working functionality.

31
New cards

Software Evolution

The process of managing and implementing change in existing software systems.

32
New cards

Fault Repair Maintenance

Modifications made to fix errors in software specifications, design, or implementation.

33
New cards

Adaptive Maintenance

Adjustments made to accommodate changes in the operating environment.

34
New cards

Functional Maintenance

Changes made to satisfy new requirements.

35
New cards

Software Maintenance Costs

Costs associated with making changes to software, often exceeding development costs.

36
New cards

Legacy Systems

Older systems that are still in use but may require updates or replacement.

37
New cards

Project Management

The process of planning, executing, and overseeing software development projects.

38
New cards

Risk Management Process

The steps taken to identify, evaluate, and mitigate risks in a software project.

39
New cards

Risk Identification

The process of recognizing potential risks that could affect a project.

40
New cards

Risk Analysis

Evaluating the likelihood and impact of identified risks.

41
New cards

Algorithmic Cost Models

Mathematical functions used for estimating the cost of software projects.

42
New cards

COCOMO 2 Model

An empirical cost estimation model based on historical project data.