SDP5 - Final [Part-1]

Question

The term _____ was coined in 1968 as a response to the desolate state of the art developing quality software on time and within budget

Answer 1

Software engineering

Answer 2

Software Development Models

Answer 3

Subroutine

Answer 4

Machine code

Answer 5

Hexadecimal code

Answer 6

A string of 0s and 1s

Answer 7

A hexadecimal code

Answer 8

An opcode mnemonic

Answer 9

A decimal code

Answer 10

A string of 0s and 1s

Answer 11

Groups of instruction combined into words and abbreviations

Answer 12

A mathematical formula

Answer 13

A logical formula

Answer 14

An internals diagram

Answer 15

A context diagram

Answer 16

A sequence diagram

Answer 17

A functionality scenario

Answer 18

Herman Hollerith

Answer 19

Charles Babbage

Answer 20

Claude Shannon

Answer 21

John Von Neumann

Answer 22

Charles Babbage

Answer 23

George Boole

Answer 24

Claude Shannon

Answer 25

John Von Neumann

Answer 26

a decision not to modify the system

Answer 27

a process that will run as part of the system

Answer 28

an argument that drives system design

Answer 29

a goal for actors the system interacts with

Answer 30

a diagram that shows what the system does

Answer 31

DOES, RISKIEST FIRST, TWO-FOUR WEEKS

Answer 32

DOES NOT, RISKIEST FIRST, LEFT OPEN

Answer 33

DOES, HIGHEST CUSTOMER VALUE FIRST, TWO-FOUR WEEKS

Answer 34

DOES NOT, HIGHEST CUSTOMER VALUE FIRST, TWO-FOUR WEEKS

Answer 35

Sequence diagram

Answer 36

Component diagram

Answer 37

Activity diagram

Answer 38

Class diagram

Answer 39

None of the above

Answer 40

The server may not scale to 1000 users

Answer 41

The code for the sort algorithm is overly complex

Answer 42

We do not adequately understand our customer’s needs

Answer 43

The system is working fine, but if we try to change anything it seems to always break something else

Answer 44

Speaks to experts who study user interfaces; Build prototypes; Talk to users;

Answer 45

Limit the functionality the users can customize to minimize the interface

Answer 46

Make sure the back end of the system works pretty well before presenting the user with the interface to avoid confusing the users with bugs and getting bad interface advice

Answer 47

Class Diagram, Sequence Diagram, Component Diagram

Answer 48

Class Diagram, Collaboration Diagram, Use Case Diagram

Answer 49

Use Case Diagram, Sequence Diagram, Class Diagram

Answer 50

Use Case Diagram, Sequence Diagram, Deployment Diagram

Answer 51

Both a and b

Answer 52

Both b and c

Answer 53

Both c and e

Answer 54

A sequence diagram is used to model a sequence of activities associated with a use case.

Answer 55

A sequence diagram is used to model a sequence of messages exchanged among objects.

Answer 56

A sequence diagram is used to model a sequence of transitions among objects in a use case.

Answer 57

United Models for Languages

Answer 58

Universal Modeling Language

Answer 59

Unified Modeling Language

Answer 60

United Modeling Language

Answer 61

UML is a combination of notations. UML supports modeling multiple views of software. UML has evolved over time.

Answer 62

UML was created by the OMG

Answer 63

Activity diagrams, Component diagrams, Construction diagrams

Answer 64

Component diagrams, Action diagrams, Sequence diagrams

Answer 65

Class diagrams, ER diagrams, Action diagrams

Answer 66

Canonical diagrams, Activity diagrams, Sequence diagrams

Answer 67

Class diagrams, Sequence diagrams, Use Case diagrams

Answer 68

Image:

1 (binary/octet-stream)

Answer 69

Image:

2 (binary/octet-stream)

Answer 70

Image:

3 (binary/octet-stream)

Answer 71

Image:

4 (binary/octet-stream)

Answer 72

Helps ensure that objects are highly reusable.

Answer 73

Requires that methods that are present in base classes must also be present in the derived classes.

Answer 74

Helps ensure that objects are easy to extend without requiring change to the original object.

Answer 75

Requires that object interfaces only include methods that will be needed by most implementers.

Answer 76

Helps make changing an object easier

Answer 77

Helps ensure that objects are highly reusable.

Answer 78

Requires that methods that are present in base classes must also be present in the derived classes

Answer 79

Helps ensure that objects are easy to extend without requiring change to the original object.

Answer 80

Requires that object interfaces only include methods that will be needed by most implementers.

Answer 81

Helps make changing an object easier

Answer 82

Helps ensure that objects are highly reusable.

Answer 83

Requires that methods that are present in base classes must also be present in the derived classes.

Answer 84

Helps ensure that objects are easy to extend without requiring change to the original object.

Answer 85

Requires that object interfaces only include methods that will be needed by most implementers.

Answer 86

Helps make changing an object easier

Answer 87

Helps ensure that objects are highly reusable.

Answer 88

Requires that methods that are present in base classes must also be present in the derived classes.

Answer 89

Helps ensure that objects are easy to extend without requiring change to the original object.

Answer 90

Requires that object interfaces only include methods that will be needed by most implementers.

Answer 91

Helps make changing an object easier

Answer 92

Helps ensure that objects are highly reusable.

Answer 93

Requires that methods that are present in base classes must also be present in the derived classes.

Answer 94

Helps ensure that objects are easy to extend without requiring change to the original object.

Answer 95

Requires that object interfaces only include methods that will be needed by most implementers.

Answer 96

Helps make changing an object easier

Answer 97

It takes too long to create the diagrams.

Answer 98

Good UML tools are too expensive.

Answer 99

It is not a language known by most non-developers.

Answer 100

Its use is incompatible with the goals of domain modeling.

Answer 101

The diagrams require you to include too much detail.

Answer 102

Person 1.2---------Contact

Answer 103

Person *--------1.2Contact

Answer 104

Person 2----------*Contact

Answer 105

Person *----------2Contact

Answer 106

Describes how the software being created interacts with elements in its environment.

Answer 107

Can be based on a use case diagram.

Answer 108

Might show the Internet.

Answer 109

Describes what is in and what is outside the scope of the software project.

Answer 110

All of a-d

Answer 111

Component diagrams show all potential interactions among a group of components whereas sequence diagram shows the interactions involved in response to a particular kind of request

Answer 112

There is very difference, they are just two different ways of viewing component

Answer 113

In component diagram the components use a rectangular shape with the component icon in the upper right corner but no component icon appears in sequence diagram

Answer 114

Component diagram represent the code whereas sequence diagram represent behavior

Answer 115

Subsystem elements have critical differences from components, which must be represented.

Answer 116

Subsystem elements and component elements are not substantially different so there is no need for them.

Answer 117

Component elements have important aspects that are not representable using the provided subsystem element notation.

Answer 118

Both a and c

Answer 119

None of the above

Answer 120

A component diagram shows a configuration of the system at a given moment.

Answer 121

A component diagram shows all potential interactions among components in a view.

Answer 122

A component diagram can show instances of classes.

Answer 123

Both a and b

Answer 124

Both b and c

Answer 125

A class diagram shows a configuration of the system at a given moment.

Answer 126

A class diagram shows all potential interactions among components in a view.

Answer 127

A class diagram can show relationships between java interfaces and other classes.

Answer 128

Both a and b.

Answer 129

Both b and c.

Answer 130

A class diagram for a module always has three components.

Answer 131

A class diagram shows relationships among code units.

Answer 132

A class diagram supports analyzing behavior of complex protocols.

Answer 133

Lollipop symbol is used to represent provides interfaces.

Answer 134

Socket symbol is used to represent provides interfaces.

Answer 135

Class and components diagrams are always very similar.

Answer 136

Identifying public and private members of a class.

Answer 137

Identifying which classes depend on other classes.

Answer 138

Discussing how the system will behave.

Answer 139

Discussing how to add newly required functionality to the system.

Answer 140

Both a and d

Answer 141

Contains a description of other related patterns.

Answer 142

Can be useful describing how a software problem was solved by a developer.

Answer 143

Is a general reusable solution to a commonly occurring problem within a given context in software design.

Answer 144

Gives examples of code that used the pattern.

Answer 145

Both a and c.

Answer 146

All of a-d.

Answer 147

Four authors of Book ‘Design Patterns - Elements of Reusable Object-Oriented Software’ are known as Gang of Four (GOF).

Answer 148

Gang of Four (GOF) is a name of a book on Design Patterns.

Answer 149

Gang of Four (GOF) is a Design Pattern.

Answer 150

None of the above.

Answer 151

This pattern creates object without exposing the creation logic to the client and refer to newly created object using a common interface.

Answer 152

In this pattern an interface is responsible for creating a factory of related objects without explicitly specifying their classes.

Answer 153

This pattern involves a single class which is responsible to create an object while making sure that only single object gets created.

Answer 154

This pattern is used when we want to pass data with multiple attributes in one shot from client to server.

Answer 155

Creational, Structural and Behavioral patterns

Answer 156

Executional, Structural and Behavioral patterns

Answer 157

Creational, Executional and Behavioral patterns

Answer 158

None of the above

Answer 159

This pattern builds a complex object using simple objects and using a step by step approach.

Answer 160

This pattern is used where we need to treat a group of objects in similar way as a single object.

Answer 161

This pattern hides the complexities of the system and provides an interface to the client using which the client can access the system.

Answer 162

This pattern is primarily used to reduce the number of objects created and to decrease memory footprint and increase performance

Answer 163

In this pattern a class represents functionality of another class.

Answer 164

In this pattern a request is wrapped under an object as command and passed to invoker object

Answer 165

This pattern creates a chain of receiver objects for a request

Answer 166

This pattern provides a way to evaluate language grammar or expression

Answer 167

Unit testing

Answer 168

Regression testing

Answer 169

Acceptance testing

Answer 170

System testing

Answer 171

Waterfall, Incremental, Spiral

Answer 172

XP, Scrum, Kanban

Answer 173

Waterfall, XP, Spiral

Answer 174

Spiral, V-Model, Scrum

Answer 175

Feasibility, Testing, Implementation, Requirement, Design

Answer 176

Feasibility, Requirements, Design, Implementation, Testing

Answer 177

Requirements, Feasibility, Design, Implementation, Testing

Answer 178

Testing, Design, Implementation, Feasibility, Requirements

Answer 179

Agile Processes

Answer 180

Traditional Process Models

Answer 181

Both answers are correct

Answer 182

None of the above

Answer 183

Pair programming

Answer 184

Test driven development

Answer 185

Design improvement (refactoring)

Answer 186

None of the above

Answer 187

A reasonable approach when requirements are well defined

Answer 188

A good approach when a working programs is required quickly

Answer 189

The best approach to use for projects with large development teams

Answer 190

An old fashioned model that is rarely used any more

Answer 191

A revolutionary model that is not used for commercial products

Answer 192

A reasonable approach when requirements are well defined

Answer 193

A good approach when a working programs is required quickly

Answer 194

The best approach to use for projects with large development teams

Answer 195

Ends with the delivery of the software product

Answer 196

Is more chaotic than the incremental model

Answer 197

Includes project risks evaluation during each iteration

Answer 198

All of the above

	Criado por Good Guy Beket mais de 6 anos atrás

Próximo

SDP5 - Final [Part-1]

Descrição

Resumo de Recurso

Questão 1

Questão 2

Questão 3

Questão 4

Questão 5

Questão 6

Questão 7

Questão 8

Questão 9

Questão 10

Questão 11

Questão 12

Questão 13

Questão 14

Questão 15

Questão 16

Questão 17

Questão 18

Questão 19

Questão 20

Questão 21

Questão 22

Questão 23

Questão 24

Questão 25

Questão 26

Questão 27

Questão 28

Questão 29

Questão 30

Questão 31

Questão 32

Questão 33

Questão 34

Questão 35

Questão 36

Questão 37

Questão 38

Questão 39

Questão 40

Questão 41

Questão 42

Questão 43

Questão 44

Questão 45

Questão 46

Questão 47

Questão 48

Questão 49

Questão 50

Questão 51

Questão 52

Questão 53

Questão 54

Questão 55

Questão 56

Questão 57

Questão 58

Questão 59

Questão 60

Questão 61

Questão 62

Questão 63

Questão 64

Semelhante