Soft Eng | Finals Flashcards

1
Q

it describes its major components, their relationships (structures), and how they interact with each other

A

architecture of a system

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

it includes several contributory factors such as Business strategy, quality attributes, human dynamics, design, and IT environment

A

Software architecture and design

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

it serves as a blueprint for a system

A

SOFTWARE ARCHITECTURE

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

It provides an abstraction to manage the system complexity and establish a communication and coordination mechanism among components

A

SOFTWARE ARCHITECTURE

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

Software Architecture defines a ____ to meet all the technical and operational requirements, while optimizing the common quality attributes like performance and security

A

structured solution

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

it involves a set of significant decisions about the organization related to software development and each of these decisions can have a considerable impact on quality, maintainability, performance, and the overall success of the final product

A

software architecture

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

it provides a design plan that describes the elements of a system, how they fit, and work together to fulfill the requirement of the system

A

software design

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q
  • To negotiate system requirements, and to set expectations with customers, marketing, and management personnel.
  • Act as a blueprint during the development process.
  • Guide the implementation tasks, including detailed design, coding, integration, and testing.
A

software design

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

it comes before the detailed design, coding, integration, and testing and after the domain analysis, requirements analysis, and risk analysis

A

software design

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

The primary goal of the ____ is to identify requirements that affect the structure of the application

A

architecture

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

it reduces the business risks associated with building a technical solution and builds a bridge between business and technical requirements

A

a well-laid architecture

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

Software architecture is still an emerging discipline within software engineering

A

limitations

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

it sits at the technical core of software engineering and is applied regardless of the software process model that is used

A

software design

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

it produces a data design, an architectural design, an interface design and procedural design

A

design task

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

it transforms the information domain model created during analysis into the data structures that will be required to implement the software

A

data design

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

data objects and relationships defined in the

A

entity relationship diagram

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

they are objects or concepts that represent important data. they are typically nouns, e.g. customer, supervisor, location, or promotion

A

entity

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

it exists independently from other entity types. they always possess one or more attributes that uniquely distinguish each occurrence of the entity

A

strong entities

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

it depends on some other entity types. they don’t possess unique attributes (primary key) and have no meaning in the diagram without depending on another entity

A

weak entities

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

they are meaningful associations between or among entities. they are usually verbs, e.g. assign, associate, or track

A

relationships

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

they are connections that exist between a weak entity type and its owner

A

weak relationships or identifying relationships

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

they are characteristics of either an entity, a many-to-many relationship, or a one-to-one relationship

A

attributes

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

they are those that are capable of taking on more than one value

A

multivalued attributes

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

they are attributes whose value can be calculated from related attribute values

A

derived attributes

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

it illustrates an association between two tables. in the physical data model, it is represented by stylized lines

A

relationship

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

it refers to the maximum number of times an instance in one entity can be associated with instances in the related entity, and the minimum number of times an instance in one entity can be associated with an instance in the related entity. they are represented by the styling of a line and its endpoint, as denoted by the chosen notation style

A

cardinality and ordinality

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

samples of association

A

one
many
one (and only one)
zero or one
one or many
zero or many

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

At the architecture level, ____ is the process of creating a model of the information represented at a high level of abstraction (using the customer’s view of data)

A

data design

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

an alternative solution adds on additional layer to the data architecture

A

data warehouse

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

a separate data environment that is not directly integrated with day-to-day applications that encompasses all data used by a business

A

data warehouse

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

the business IT community has developed data mining techniques, also called ____, that navigate through existing databases in an attempt to extract appropriate business-level information

A

knowledge discovery in databases (KDD)

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

it defines the relationship between major structural elements of the software

A

architectural design

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

it can be derived from the system specification, the analysis model, and the interaction of subsystems defined within the analysis model.

A

architectural design representation

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

it describes how the software communicates within itself, with systems that interoperate with it, and with humans who use it

A

interface design

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

it implies a flow of information (e.g., data and/or control) and a specific type of behavior

A

interface

36
Q

they provide much of the information required for interface design

A

data and control flow diagrams

37
Q

at the component level, the software engineer must represent data structures, interfaces, and algorithms in sufficient detail to guide the generation of programming language source-code

A

procedural design

38
Q

it defined in the entity data flow diagram/flowchart

A

procedural design

39
Q

it occurs after data, architectural, and interface designs have been established

A

Component-level design or procedural design

40
Q

it defines the data structures, algorithms, interface characteristics, and communication mechanisms allocated to each software component

A

component-level design

41
Q

its intent is to translate the design model into operational software

A

procedural design

42
Q

the level of abstraction of the existing design model is relatively high, and the abstraction level of the operational program is low

A

procedural design

43
Q

four main element of data flow diagram

A

process
data flow
data store
external entity

44
Q

the activities carried out by the system which use and transform information. they are notated as rectangles

A

process/processes

45
Q

the data inputs to and outputs from to these activities. they are notated as named arrow

A

data flows

46
Q

the sources from which information flows into the system and the recipients of information leaving the system. they are notated as ovals

A

external entities

47
Q

it is where information is stored within the system. they are notated as rectangles

A

data stores

48
Q

The software is able to operate with other products that are designed for interoperability with another product

A

Compatibility

49
Q

New capabilities can be added to the software without major changes to the underlying architecture

A

Extensibility

50
Q

The software is resistant to and able to recover from component failure

A

Fault-tolerance

51
Q

The software can be restored to a specified condition within a specified period of time

A

Maintainability

52
Q

The resulting software comprises well defined, independent components. That leads to better maintainability

A

Modularity

53
Q

Printed material such as the box and manuals should match the style designated for the target market and should enhance usability

A

Packaging

54
Q

The software is able to perform a required function under stated conditions for a specified period of time

A

Reliability

55
Q

The modular components designed should capture the essence of the functionality expected out of them and no more or less

A

Reusability

56
Q

The software is able to operate under stress or tolerate unpredictable or invalid input

A

Robustness

57
Q

The software is able to withstand hostile acts and influences

A

Security

58
Q

The software user interface must be usable for its target user/audience

A

Usability

59
Q

it is the design of software applications, and websites with the focus on the user’s experience and interaction

A

user interface design or user interface engineering

60
Q

its goal is to make the user’s interaction as simple and efficient as possible, in terms of accomplishing user goals - what is often called user-centered design

A

user interface design

61
Q

assembling a list of the functionality required of the system to accomplish the goals of the project and the potential needs of the users

A

functionality requirements gathering

62
Q

analysis of the potential users of the system either through discussion with people who work with the users and/or the potential users themselves

A

user analysis

63
Q

development of the process and/or information flow of the system

A

information architecture

64
Q

development of wireframes, either in the form of paper prototypes or simple interactive screens

A

prototyping

65
Q

testing of the prototypes on an actual user

A

usability testing

66
Q

actual look & feel design of the final graphical user interface (GUI)

A

graphic interface design

67
Q

this phase is often a collaborative effort between a graphic designer and a user interface designer, or handled by one who is proficient in both disciplines

A

graphic interface design

68
Q

This is the most important thing you can possibly do. It enables your users to build an accurate mental model of the way it works, and accurate mental models lead to lower training and support costs

A

consistency

69
Q

UI Design Principles

A

 The structure principle.
 The simplicity principle.
 The visibility principle.
 The feedback principle.
 The tolerance principle.
 The reuse principle.

70
Q

it is the process of exercising a program with the specific intent of finding errors prior to delivery to the end user

A

testing

71
Q

it is conducted by the developer of the software and (for large projects) an independent test group

A

testing

72
Q

they are different activities, but debugging must be accommodated in any testing strategy

A

testing and debugging

73
Q

it refers to the set of tasks that ensure that software correctly implements a specific function

A

Verification

74
Q

it refers to a different set of tasks that ensure that the software that has been built is traceable to customer requirements

A

Validation

75
Q

the person who understands the system
but will test gently and is driven by delivery

A

developer

76
Q

the person who learns about the system
but will attempt to break it and is driven by quality

A

independent tester

77
Q

it moves outward along the spiral

A

testing progresses

78
Q

it begins at the vortex of the spiral and concentrates on each unit. It focuses verification effort on the smallest unit of software design-the software component or module

A

unit testing

79
Q

a testing where the focus is on design and the construction of the software architecture

A

integration testing

80
Q

a testing where requirements established as part of requirements modeling are validated against the software that has been constructed

A

validation testing

81
Q

a testing where the software and other system elements are tested as a whole

A

system testing

82
Q

it defines the role of software and leads to software requirements analysis come along to design and finally to coding

A

system engineering

83
Q

it is not testing but often occurs as a consequence of testing

A

debugging

84
Q

it begins with the execution of a test case

A

debugging process

85
Q

they are assessed and a lack of correspondence between expected and actual performance is encountered

A

results

86
Q

it attempts to match symptom with cause, thereby leading to error correction

A

debugging process