Lesson 4 Flashcards

1
Q

a contract where one party (the Developer) agrees to develop a software application for another party (the Client).

A

Software Development Agreement

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

the one that you will use to detail any specifics that are not covered by the other sections of the software license agreement

A

Fine Details

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

include some information about maintenance, support, or refunds that will or will not be offered by your company through the agreement.

A

Site License

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

allow your customer to use the software on more than one computer but only at one location.

A

Site License

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

includes the price to be paid for the license, which you can define as a flat fee or a flat fee with yearly maintenance fees.

A

Terms of the agreement

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

it defines who the parties are that are entering into the agreement.

A

Parties involved

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

In this section, you will find information about when the agreement will go into effect, how long the terms of the agreement will be active for, and the type of agreement

A

General Information

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

an agreement between your company and your customers for use of the software you have the rights to

A

Software License Agreement

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

an ongoing fee paid for the right of use of the licensor�s intellectual property.

A

Royalty Fee

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

pays an upfront fee in conjunction with a royalty fee.

A

LICENSEE

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

receiving the intellectual property

A

LICENSEE

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

party providing the intellectual property

A

LICENSOR

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

a contract between two parties (the licensor and licensee) in which the licensor grants the licensee the right to use the brand name, trademark, patented technology, or ability to produce and sell goods owned by the licensor.

A

Licensing Agreement

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

are IP rights on confidential information which may be sold or licensed.

A

Trade secrets

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

signs used on goods that have a specific geographical origin and possess qualities, a reputation or characteristics that are essentially attributable to that place of origin.

A

Geographical Indications And Appellations

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

constitutes the ornamental aspect of an article.

A

Industrial Design

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

a sign capable of distinguishing the goods or services of one enterprise from those of other enterprises.

A

Trademark

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

the invention cannot be commercially made, used, distributed, imported or sold by others without the patent owner’s consent.

A

Patent Protection

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

has the exclusive right to prevent or stop others from commercially exploiting the patented invention

A

Patent Owner

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

an exclusive right granted for an invention, which is a product or a process that provides, in general, a new way of doing something, or offers a new technical solution to a problem.

A

Patent

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

protect the noneconomic interests of the author.

A

Moral Rights

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

allow the rights owner to derive financial reward from the use of their works by others; and

A

Economic Rights

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

covered by copyright range from books, music, paintings, sculpture and films, to computer programs, databases, advertisements, maps and technical drawings.

A

Copyright

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

a legal term used to describe the rights that creators have over their literary and artistic works.

A

Copyright

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

protected in law by, for example, patents, copyright and trademarks, which enable people to earn recognition or financial benefit from what they invent or create.

A

Intellectual property (IP)

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

creations of the mind, such as inventions; literary and artistic works; designs; and symbols, names and images used in commerce

A

Intellectual property (IP)

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

protects individuals from unauthorized processing of personal information that is (1) private, not publicly available; and (2) identifiable, where the identity of the individual is apparent either through direct attribution or when put together with other available information.

A

RA 10173, or the Data Privacy Act

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

established a National Privacy Commission that enforces and oversees it and is endowed with rulemaking power

A

Data Privacy Act 2012

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

Republic Act. No. 10173, Ch. 1, Sec. 2

A

Data Privacy Act 2012

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

comprehensive and strict privacy legislation �to protect the fundamental human right of privacy, of communication while ensuring free flow of information to promote innovation and growth

A

Data Privacy Act 2012

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

A box that sets a system scope to use cases. All use cases outside the box would be considered outside the scope of that system.

A

Sysem boundary Boxes

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

A line between actors and use cases

A

Associations

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

Stick figures that represent the people actually employing the use cases

A

Actors

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

Horizontally shaped ovals that represent the different uses that a user might have.

A

Use cases

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

should be used for optional and conditional behaviors that are not essential to the main goal of your use cases.

A

Extend relationships

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

should be used for common and mandatory behaviors that are relevant to the main goal of your use cases.

A

Include relationships

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

end result of most use cases - A successful diagram should describe the activities and variants used to reach the goal.

A

Goals

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

A specific sequence of actions and interactions between actors and the system. A system may also be referred to as a scenario.

A

System

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

must be external objects that produce or consume data.

A

Actors

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

can be a person, an organization, or an outside system that interacts with your application or system

A

Actors

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

users that interact with a system

A

Actors

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

the scope of your system

A

Use Case Diagram

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

Goals that your system or application helps those entities (known as actors) achieve

A

Use Case Diagram

44
Q

Scenarios in which your system or application interacts with people, organizations, or external systems

A

Use Case Diagram

45
Q

describe what the system does and how the actors use it, but not how the system operates internally

A

Use Case Diagram

46
Q

identify the interactions between the system and its actors.

A

Use Case Diagram

47
Q

describe the high-level functions and scope of a system.

A

Use Case Diagram

48
Q

summarize the details of your system’s users (also known as actors) and their interactions with the system

A

Use Case Diagram

49
Q

a general-purpose visual modeling language that is intended to provide a standard way to visualize the design of a system.

A

Unified Modeling Language

50
Q

quite adopted in software testing method especially in agile testing

A

Kanban

51
Q

originally emerged from Japanese word that means, a card containing all the information needed to be done on the product at each stage along its path to completion.

A

Kanban

52
Q

Online tool Storyboard can be used to store the stories. Several teams can use it for different purposes.

A

Online Storyboard

53
Q

This is a traditional way of collecting all the stories in a board in the form of stick notes to track daily XP activities. As this manual activity involves more effort and time, it is better to switch to an online form.

A

Story Cardboard

54
Q

is a tool in Agile software development used to capture a description of a software feature from a user’s perspective.

A

User Story

55
Q

advocates frequent “releases” of the product in short development cycles, which inherently improves the productivity of the system and also introduces a checkpoint where any customer requirements can be easily implemented.

A

eXtreme Programming (XP)

56
Q

very helpful when there is constantly changing demands or requirements from the customers or when they are not sure about the functionality of the system

A

eXtreme Programming (XP)

57
Q

aims at increasing speed of software development and decreasing cost

A

Lean Software Development

58
Q

based on the principle “Just in time production”.

A

Lean Software Development

59
Q

includes domain walkthrough, design inspection, promote to build, code inspection and design

A

Feature Driven Development (FDD)

60
Q

focused around “designing & building” features. Unlike other agile methods, FDD describes very specific and short phases of work that has to be accomplished separately per feature

A

Feature Driven Development (FDD)

61
Q

Frequent delivery of product becomes the active focus

A

Dynamic Software Development Method (DSDM)

62
Q

users are required to be involved actively, and the teams are given the power to make decisions

A

Dynamic Software Development Method (DSDM)

63
Q

a Rapid Application Development (RAD) approach to software development and provides an agile project delivery framework

A

Dynamic Software Development Method (DSDM)

64
Q

The activities performed in this phase are deployment into the user environment, post- deployment reviews and reflections are performed.

A

Wrap up

65
Q

Team updates and refines the release plan

A

Cyclic Delivery

66
Q

Implements a subset of the requirements through one or more program test integrate iterations

A

Cyclic Delivery

67
Q

Integrated product is delivered to real users - Review of

A

Cyclic Delivery

68
Q

Review of the project plan and adopted development methodology

A

Cyclic Delivery

69
Q

Various activities involved in this phase are creating a development team, performing a preliminary feasibility analysis, developing an initial plan and fine-tuning the development methodology.

A

Chartering

70
Q

wait lng hindi ko pa nalagay to

A

Crystal Methodologies

71
Q

manages its own work and organizes the work to complete the sprint or cycle

A

Scrum Team

72
Q

creates product backlog, prioritizes the backlog and responsible for the delivery of the functionality at each iteration

A

Product Owner:

73
Q

responsible for setting up the team, sprint meeting and removes obstacles to progress

A

Scrum Master

74
Q

in empowering the development team and advocates working in small teams (say- 7 to 9 members).

A

Scrum

75
Q

derived from activity that occurs during a rugby match

A

Scrum

76
Q

an agile development method which concentrates specifically on how to manage tasks within a team-based development environment

A

Scrum

77
Q

both development and testing activities are concurrent, unlike the Waterfall model

A

Agile Methodology

78
Q

promotes continuous iteration of development and testing throughout the software development lifecycle of the project

A

Agile Methodology

79
Q

Evaluation of software by customer, includes identifying and monitoring risk such as schedule slippage and cost overrun.

A

Evaluation

80
Q

It includes testing, coding and deploying software at the customer site.

A

Engineering

81
Q

s Identification of potential risk is done while risk mitigation strategy is planned and finalized

A

Risk Analysis

82
Q

estimating the cost, schedule and resources for the iteration, understanding the system requirements for continuous communication between the system analyst and the customer

A

Planning

83
Q

adds functionality for the additional requirement in every-increasing spirals until the application is ready for the production phase.

A

Software Engineering Team

84
Q

starts with a small set of requirements and goes through each development phase for those set of requirements.

A

Spiral Model

85
Q

a combination of rapid prototyping and concurrency in design and development activities.

A

Spiral Model

86
Q

adopts the best features of the prototyping model and the waterfall model

A

Spiral Model

87
Q

helps the team to adopt elements of one or more process models like a waterfall, incremental, waterfall

A

Spiral Model

88
Q

risk-driven process model

A

Spiral Model

89
Q

It consists of a series of activities carried out by Testers methodologically to test your software product.

A

Software Testing Life Cycle

90
Q

It is the sequence of activities carried out by Developers to design and develop highquality software.

A

Software Development Life Cycle

91
Q

an extension of the waterfall model in which testing is done on each stage parallel with development in a sequential way

A

V Model

92
Q

highly disciplined SDLC model in which there is a testing phase parallel to each development phase.

A

V Model

93
Q

is known as the Validation or Verification Model

A

V Model

94
Q

Once the system is deployed, it goes through the testing phase

A

Test

95
Q

Coding of software is done during this stage

A

Build

96
Q

Some high-end functions are designed during this stage

A

Requirement Gathering

97
Q

Requirement and specification of the software are collected.

A

Requirement Gathering

98
Q

done in steps from analysis design, implementation, testing/verification ,maintenance

A

Incremental Model

99
Q

process of software development where requirements are broken down into multiple standalone modules of software development cycle

A

Incremental Model

100
Q

Once the system is ready to use, you may later require change the code as per customer request

A

Maintenance

101
Q

Deploy the application in the respective environment

A

Deployment

102
Q

Test the software to verify that it is built as per the specifications given by the client

A

Test

103
Q

Plan the programming langauge for example Java, PHP, .net or database like Oracle, MySQL, etc. Or other high-level technical details of the project

A

Design

104
Q

Detailed requirements of the software system to be developmed are gathered from client

A

Requirement Gathering

105
Q

each phase must be completed before the next phase can begin with no overlap between the phases

A

Waterfall Model

106
Q

A sequential model that divides software development into pre-defined phases.

A

Waterfall Model

107
Q

Who Introduced the Waterfall model

A

Winston Royce