Lecture 1: Review of the Software Engineering process

0.0(0)
studied byStudied by 0 people
0.0(0)
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/82

encourage image

There's no tags or description

Looks like no tags are added yet.

Last updated 1:35 PM on 1/20/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai

No analytics yet

Send a link to your students to track their progress

83 Terms

1
New cards

An engineering discipline whose focus is the cost-effective development of high-quality software systems

Software Engineering

2
New cards

An engineering discipline concerned with all aspects of software production from the early stages of system specification to maintaining the system after it has gone into use

Software Engineering

3
New cards

The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software

Software Engineering (per IEEE)

4
New cards

The first SDLC step where the user initiates a request, contacts a service provider, negotiates terms, and submits a written request

Communication

5
New cards

The phase where the software development team holds discussions with stakeholders to bring out and segregate as much information as possible on their requirements

Requirement Gathering

6
New cards

The step that analyzes if a project is financially, practically, and technologically feasible for the organization to take up

Feasibility Study

7
New cards

The step where developers decide a roadmap, choose a software model, and understand the software's limitations and impact on existing systems

System Analysis

8
New cards

The SDLC phase whose inputs are the requirements and whose outputs are the logical/system design and the physical/object design

Software Design

9
New cards

Also known as the programming phase, where developers write program code in a suitable language to create error-free executable programs

Coding

10
New cards

The phase where testing experts (not just developers) conduct module testing, program testing, product testing, in-house testing, and user-end testing

Testing

11
New cards

The stage involved in integrating software with libraries, databases, and programs from other software development teams

Integration

12
New cards

The phase where the software is installed on user machines, configured, and tested for portability and adaptability

Implementation

13
New cards

The phase that confirms software efficiency, involves user training via documentation, and includes timely updates and maintenance

Operation and Maintenance

14
New cards

The final SDLC phase involving archiving data, closing down the system, planning disposition activities, and terminating the system

Disposition

15
New cards

These serve as a guide for a systematic approach to software development

Software Process Models

16
New cards

Examples of these include the Waterfall model, Incremental model, Spiral model, RUP, the V model, and the Agile model

Software Process Models

17
New cards

A technical document describing a project's functionality, features, design, limitations, and goals, containing a use case suite and feature set

Software Requirements Specification (SRS)

18
New cards

In an SRS, these outline what the system must do

Functional Requirements

19
New cards

In an SRS, these outline how well the system performs its functions

Non-Functional Requirements

20
New cards

This forms the foundation of all software engineering layers, representing the organizational commitment

Quality

21
New cards

The "glue" that holds the technology layers together and enables rational and timely development; it forms the basis for project control

The Software Engineering Process

22
New cards

These provide the technical "how-to's," encompassing tasks like communication, requirements analysis, design modeling, program construction, testing, and support

Software Engineering Methods

23
New cards

These provide automated or semi-automated support for the process and methods; their integration creates a CASE system

Software Engineering Tools

24
New cards

The slide hints that in the first software engineering course, the primary focus was not on Tools, but on these two layers

Process and Methods

25
New cards

A collection of activities, actions, and tasks performed when some work product is to be created

A Process

26
New cards

Strives to achieve a broad objective (e.g., communication with stakeholders)

An Activity

27
New cards

Encompasses a set of tasks that produce a major work product (e.g., architectural design)

An Action

28
New cards

Focuses on a small, well-defined objective that produces a tangible outcome (e.g., conducting a unit test)

A Task

29
New cards

Establishes the foundation for a complete software engineering process by identifying framework activities applicable to all projects

The Software Engineering Process Framework

30
New cards

The framework activity whose intent is to understand stakeholder objectives and gather requirements before any technical work

Communication

31
New cards

The framework activity that creates a "map" describing technical tasks, risks, resources, work products, and a schedule

Planning

32
New cards

The framework activity where a software engineer creates a "sketch" or model to understand the big picture, architecture, and how parts fit together

Modeling

33
New cards

The framework activity that combines code generation and the testing required to uncover errors in the code

Construction

34
New cards

The framework activity where the software is delivered to the customer for evaluation and feedback

Deployment

35
New cards

Umbrella activities are applied throughout a software project to help manage and control these four things

Progress, Quality, Change, Risk

36
New cards

The umbrella activity that allows the team to assess progress against the project plan and take action to maintain the schedule

Software Project Tracking and Control

37
New cards

The umbrella activity that assesses risks that may affect the project outcome or product quality

Risk Management

38
New cards

The umbrella activity that defines and conducts activities required to ensure software quality

Software Quality Assurance

39
New cards

The umbrella activity that assesses work products to uncover and remove errors before they are propagated to the next activity

Technical Reviews

40
New cards

The umbrella activity that defines and collects process, project, and product measures. (Slide 38 lists 10 examples)

Measurement

41
New cards

From the list on Slide 38, this is an example of a measurement metric: "_________ Metrics" like those from Quality Assurance

QA Metrics

42
New cards

The umbrella activity that manages the effects of change throughout the software process

Software Configuration Management

43
New cards

The umbrella activity that defines criteria for work product reuse and establishes mechanisms to achieve reusable components

Reusability Management

44
New cards

The umbrella activity encompassing the creation of work products such as models, documents, logs, forms, and lists

Work Product Preparation and Production

45
New cards

The software engineering process should be agile and adaptable to these four factors

The problem, the project, the team, the organizational culture

46
New cards

Among the differences in adopted processes is the "Degree to which the _______ and other stakeholders are involved with the project"

Customer

47
New cards

The slide states that SEN02 will be about the process framework, quality focus, and the ________ control of software projects

management

48
New cards

One of the listed future discussion topics is "Process _________" which aims to enhance the software engineering process over time

Improvement

49
New cards

The module provides only one definitive, universal definition of software engineering

False

50
New cards

In the Communication phase, the request from the user can be verbal; a written request is optional

False

51
New cards

Requirement Gathering is performed solely by business analysts without developer involvement

False

52
New cards

The Feasibility Study assesses financial, practical, and technological feasibility

True

53
New cards

System Analysis only deals with the new system's features and ignores the existing systems

False

54
New cards

The two forms of output from the Software Design phase are "High-Level Design" and "Low-Level Design"

False

55
New cards

Coding and Testing are two distinct phases, and the same individuals typically perform both

False

56
New cards

Integration is only necessary for software that interacts with hardware components

False

57
New cards

Post-installation configuration is never required during the Implementation phase

False

58
New cards

The Disposition phase occurs when the software is first being designed and planned

False

59
New cards

The TCQ Triad is explicitly defined and explained in detail within this module

False

60
New cards

A well-written SRS has no bearing on the ultimate success or failure of a project

False

61
New cards

In the Software Engineering Layers model, "Tools" are depicted as the most important foundational layer

False

62
New cards

The software engineering process framework is a rigid, one-size-fits-all prescription

False

63
New cards

Umbrella activities, like Software Quality Assurance, are only performed at the end of a project

False

64
New cards

Measurement, as an umbrella activity, can include collecting metrics on customer satisfaction

True

65
New cards

The main reason given for needing to manage software projects is "because our teacher says so"

False

66
New cards

The module references specific textbooks by authors like Pressman and Tsui et al

True

67
New cards

Early discovery of program errors and applying their __________________ is key to reliable software

remedies

68
New cards

A Software Requirements Specification contains a use case suite and __________________ set

feature

69
New cards

Software engineering methods include modeling activities and other __________________

techniques

70
New cards

When tools are integrated so information flows between them, it establishes a system called ___________-aided software engineering

Computer

71
New cards

An action encompasses a set of __________________ that produce a major work product

tasks

72
New cards

The software project plan defines the software engineering work by describing the technical tasks, risks, resources, work products, and a work __________________

schedule

73
New cards

From the Measurement metrics list: "___________-Oriented Measurements" is item #5

Size

74
New cards

From the Measurement metrics list: "Defect ___________" is item #7

Metrics

75
New cards

From the Measurement metrics list: "___________ Request" is item #8

Pull

76
New cards

One difference in process adoption is the "Degree to which the ____________ organization and roles are prescribed"

team's

77
New cards

One question posed is: "How must people, process, and ____________ be managed during a software project?"

problem

78
New cards

A question asks: "How does a software team generate reliable estimates of effort, cost, and project ____________?"

duration

79
New cards

Another question asks about the importance of maintenance and ____________ for managers and practitioners

reengineering

80
New cards

One of the listed future topics is "Project ____________ and Scheduling"

Estimation

81
New cards

One of the listed future topics is "Maintenance and ____________"

Reengineering

82
New cards

The recap states that the process framework tries to establish its foundation with a number of main and ____________ activities

umbrella

83
New cards

One of the referenced textbooks is "Essentials of Software Engineering" by Tsui, Karam, and ____________

Bernal

Explore top flashcards