Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Software Engineering > Phases of Software Engineering (Midterms) > Flashcards

Phases of Software Engineering (Midterms) Flashcards

Phases

1
Q

Phases of
Software
Engineering

A
  • Requirements Analysis
  • System Design
  • Validation
  • Evolution
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

REQUIREMENT
ANALYSIS ACTIVITIES

A

Eliciting Requirements
Analyzing Requirements
Recording Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

The task communicating with customers and users to determine what their requirements are. This is sometimes called Requirements Gathering.

A

Eliciting Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Determining whether the stated requirements are unclear, incomplete, ambiguous, or contradictory, and then resolved these issues.

A

Analyzing Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Determining whether the stated requirements are unclear, incomplete, ambiguous, or contradictory, and then resolved these issues.

A

Recording Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Two kinds of requirements

A

User Requirements
System Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

detailed description of what
the system should do including the software system’s functions, services, and operational constraints.

A

System Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

High-level abstract
requirements written as statements, in a natural language
plus diagrams, of what services the system is expected to provide to system users and the constraints under which it must operate.

A

User Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

The study considers whether the proposed system will be cost-effective from a business point of view.

A

Feasibility Study

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Describe what the system should do. Product features or functions that developers must implement to enable users to accomplish their tasks.

A

Functional Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Specify the characteristics of the system as a whole. A set of specifications that describe the system’s operational capabilities and constraints and attempt to
improve its functionality.

A

Non- Functional Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

It is the process of defining the elements of a system such as the
architecture, modules and components, the different interfaces of those components and the data that goes through that system

A

SYSTEM DESIGN

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Where you identify the overall structure of the system

A

Architectural Design

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Where you define the interfaces between system components.

A

Interface Design

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Where you take each system component and design how it will
operate

A

Component Design

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Where you design the system data structures and how these are to
be presented in a database.

A

Database Design

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Also called “Software Validation and Verification. refers to the process of evaluating software at the end of its
development to ensure that it is free from failures and complies with its requirements.

are we building the right product?

A

VALIDATION

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Defined as an incorrect product behavior.

A

failure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

refers to the process of determining whether or not the products of a given phase of a software development process fulfill the process established during the previous phase.

are we building the product right

A

Verification

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

STAGES IN THE TESTING PROCESS

A
  1. Development Testing
  2. System Testing
  3. Acceptance Testing/Alpha Testing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

-Each component is tested independently without the other sub systems.
-Components may be simple entities such as functions, objects, or classes

A

Development Testing

22
Q

-Concerned with finding errors that result from unanticipated interactions between components and component interface problems.
-Concerned with showing that the system meets its functional and nonfunctional requirements

A

System Testing

23
Q

May reveal errors and omissions in system requirements definitions

A

Acceptance Testing/Alpha Testing

24
Q

the final internal acceptance testing for your software.

A

Alpha testing

25
Q

The process of developing a software product using software engineering principles and methods is referred to as software evolution.

A

EVOLUTION

26
Q

This process changes to the original software, till the desired software is accomplished.

A

EVOLUTION

27
Q

PEOPLE IN THE
DEVELOPMENT

A
  1. Development Team
  2. End – users
28
Q
  • responsible in making the software
  • Build/create the software.
A

Development Team

29
Q

used/ utilize the system

A

End – users

30
Q

Understands the system

A

Analyst

31
Q

Defines the software architecture, components, modules, interfaces.

A

System Designer

32
Q

write codes of the system in a specific programming language

A

Programmer

33
Q

reviews faults and errors of the system

A

Tester

34
Q
  • Performs the daily task/operation of the organization
  • Concern: How does it work?
A

Operational Job

35
Q
  • Performs supervisory job
  • Concern: Physical Interface & Performance
A

Supervisor

36
Q
  • Provides finances and initiatives
  • Outputs/results
A

Executive

37
Q
  • management focused on
    providing confidence that quality requirements will be fulfilled
  • groups and external organizations which set standards to be followed
A

Quality Assurance (QA)

38
Q

is the total characteristics of an entity to satisfy stated and implied needs .

A

Quality

39
Q

if it is fit for use

A

Software Quality

40
Q

Three Perspectives of Software Quality

A

Quality of the Product
Quality of the Process
Quality in the context of System Environment

41
Q
  • relative to the person analyzing quality.
A

Quality of the Product

42
Q
  • failures of task are avoided
  • system development process is improved
A

Quality of the Process

43
Q
  • in terms of products/services provided by the business in which the software is used.
  • software adds value to the business
A

Quality in the Context of business Environment

44
Q

Characteristics of a well-engineered Software

A
  • Usability
  • Portability
  • Reusability
  • Maintainability
  • Dependability
  • Efficiency
45
Q

ease with which the user communicates with the system

A

Usability

46
Q

capability of the software to execute in different platforms

A

Portability

47
Q

ability to transfer from one system to another

A

Reusability

48
Q

ability to evolved and adopt change over time.

A

Maintainability

49
Q

characteristics of the software to be reliable, secure, and safe.

A

Dependability

50
Q

capability to use resources efficiently.

A

Efficiency

Software Engineering (7 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions