Software Engineering Flashcards

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

1/36

flashcard set

Earn XP

Description and Tags

Flashcards for Software Engineering Lecture Notes

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

37 Terms

1
New cards

Task Set

Defines the actual work to be done to accomplish the objectives of a software engineering action, including a list of tasks, work products, and quality assurance filters.

2
New cards

Process Pattern

Describes a process-related problem encountered during software engineering and suggests proven solutions.

3
New cards

Stage Patterns

Defines a problem associated with a framework activity for the process.

4
New cards

Task Patterns

Defines a problem associated with a software engineering action or work task.

5
New cards

Phase Patterns

Define the sequence of framework activities that occur within the process.

6
New cards

SCAMPI (Standard CMMI Assessment Method for Process Improvement)

Provides a five-step process assessment model that incorporates initiating, diagnosing, establishing, acting, and learning phases.

7
New cards

CBA IPI (CMM-Based Appraisal for Internal Process Improvement)

Provides a diagnostic technique for assessing the relative maturity of a software organization using the SEI CMM.

8
New cards

SPICE (ISO/IEC15504)

Defines a set of requirements for software process assessment to assist organizations in developing an objective evaluation of the efficacy of any defined software process.

9
New cards

ISO 9001:2000 for Software

A generic standard applicable to any organization wanting to improve the overall quality of their products, systems, or services, applicable to software organizations.

10
New cards

Software Process

A structured set of activities required to develop a software system.

11
New cards

Software Process Model

An abstract representation of a process presenting a description from a particular perspective.

12
New cards

Plan-driven Processes

Models where all process activities are planned in advance, and progress is measured against this plan.

13
New cards

Agile Processes

Process planning is incremental, making it easier to change the process to reflect changing customer requirements.

14
New cards

Prescriptive Models

Process models that advocate an orderly approach to software engineering.

15
New cards

Waterfall Model

Plan-driven model with separate phases of specification and development, heavily oriented toward documentation.

16
New cards

Incremental Model

A modification of the waterfall model where the project is divided into components developed separately and incrementally. where requirements are divided into multiple standalone modules of the software development cycle.

17
New cards

Spiral Model

A model where the process is represented as a spiral with loops chosen based on requirements, explicitly assessing and resolving risks.

18
New cards

Rational Unified Process (RUP)

An agile software development methodology that splits the project life cycle into four phases: inception, elaboration, construction, and transition.

19
New cards

Planning (PSP)

The activity isolates requirements and develops both size and resource estimates, with a defect estimate.

20
New cards

Team Software Process (TSP)

Build self-directed teams that plan and track their work, establish goals, and own their processes and plans.

21
New cards

Chief Programmer Team

A super chief programmer can divide a system into multiple components, small chief-programming teams can develop each component

22
New cards

Agile Methodologies

Family of software development methodologies that produce software in short iterations and allow for greater changes in design.

23
New cards

Short releases and iteration

Divide the work into small pieces. Release the work as often as possible

24
New cards

Change

Assumes that the requirements and environment will change

25
New cards

Agile Development

Driven by customer descriptions, recognizes short-lived plans, develops software iteratively with a focus on construction, and delivers multiple software increments, adapting to changes

26
New cards

Agility Principle

Satisfy the customer through early and continuous delivery of valuable software

27
New cards

Extreme Programming (XP)

One of the first and better-known Agile development methodologies.

28
New cards

Core values of XP

Frequent communication between team members and with customers. Simplicity in design and code. Feedback at many different levels. Courage to implement hard but necessary decisions.

29
New cards

Planning

Quick determination of features for next release. Try to get a working system quickly

30
New cards

Test-Driven Development

Ensure that testing is done continuously. Unit test. TDD acceptance testing

31
New cards

Design Improvement

Remove duplication, improve communication, simplify or add flexibility

32
New cards

Collective ownership

Establish ownership of code of whole team

33
New cards

On-site customer

include a real customer on the team

34
New cards

The Crystal Family of Methodologies

Is an agile software development methodology that cannot be adequate for all projects, and that the methodology to be adapted to the project.

35
New cards

Properties Of Crystal Clear

The 7 Properties of Crystal Clear: Written specs are not enough, Feedback early, feedback often.

36
New cards

Agile Unified Process

Iteration addresses Modeling, Implementation, Testing, Deployment, Configuration and project management, Environment management.

37
New cards

Kanban

It means billboard or visual board in Japanese. It is Derived from Toyota Production Systems.