csci 387 final

Question 1

design patterns

Answer 1

observer, adapter, bridge, singleton, strategy

Question 2

observer is

Answer 2

behavioral

Question 3

strategy is

Answer 3

behavioral

Question 4

singleton is

Answer 4

creational

Question 5

adapter is

Answer 5

structural

Question 6

bridge is

Answer 6

structural

Question 7

regression testing

Answer 7

check that changes have not broken previously working code by re-running all tests

Question 8

distributed software architectural patterns

Answer 8

master-slave, two-tier client-server, multi-tier client-server, distributed component, peer-to-peer

Question 9

pros and cons of master-slave

Answer 9

Pros: good for use in real-time systems where it is important to meet processing deadlines

Cons: not good for systems where it is not easy to predict the distributed processing that is required/where processing can be easily localized to slave processors

Question 10

pros and cons of two-tier client-server

Answer 10

Pros: simplest form; simple to manage the clients

Cons: heavy processing load on both the server and the network (thin client model), new versions of the application have to be installed on all clients (fat client model)

Question 11

pros and cons of multi-tier client-server

Answer 11

Pros: avoids problems with scalability and performance from thin-client, avoids problems of system management from fat-client

Cons: you have to decide what services should be included in each layer

Question 12

pros and cons of distributed component

Answer 12

Pros: allows system designer to delay decisions on where and how services should be provided, flexible and scalable, allows resources to be added as required, possible to reconfigure the system dynamically

Cons: more complex to design than client-server systems (difficult to visualize and understand), standardized middleware for distributed component systems has never been accepted

Question 13

pros and cons of peer-to-peer

Answer 13

Pros: takes advantage of the computational power and storage of a large number of networked computers

Cons: lack of central management is a security concern

Question 14

what are the layers to arrange in client-server?

Answer 14

database, data management, application processing, presentation

Question 15

software as a service

Answer 15

a way of deploying applications as thin client-server systems, where the client is a web browser - owned and managed by a software provider

Question 16

SaaS examples

Answer 16

microsoft 365, google apps, dropbox

Question 17

Facebook (is/is not) SaaS

Answer 17

is not

Question 18

What is WSDL?

Answer 18

(Web Service Definition Language): allows a service interface and its bindings to be defined (what operations the service supports, how the service is accessed, where the service is located)

Question 19

the “what” of WSDL

Answer 19

interface specifying what operations the service supports

Question 20

the “how” of WSDL

Answer 20

binding; maps the abstract interface to a concrete set of protocols

Question 21

the “where” of WSDL

Answer 21

describes the location of a specific web service implementation

Question 22

what is SOAP?

Answer 22

a message exchange standard that supports service communication

Question 23

what is RESTful?

Answer 23

REpresentational State Transfer

An architectural style based on transferring representations of resources from a server to a client

Question 24

advantages and disadvantages of RESTful

Answer 24

Advantages of RESTful: CRUD operations, data is exposed and accessed using URL
Disadvantages of RESTful: not good for complex interfaces, no standards for the interface, implement your own infrastructure

Question 25

SOLID principles

Answer 25

``` single responsibility open-closed liskov substitution interfae substitution dependency inversion ```

Question 26

single responsibility principle

Answer 26

a class should have only one reason to change

Question 27

open-closed principle

Answer 27

extend the behavior of a module without changing it (should be closed for modification but open for extension)

Question 28

liskov substitution principle

Answer 28

subtypes must be substitutable for their base types (functions should be able to use objects of derived classes without knowing it)

Question 29

interface substitution principle

Answer 29

clients should not be forced to depend on methods they do not use

Question 30

dependency inversion principle

Answer 30

high-level modules should not depend on low-level modules but both should depend on abstractions; abstractions should not depend on details but details should depend on abstractions

Question 31

how to apply SRP

Answer 31

new class

Question 32

how to apply OCP

Answer 32

abstraction of class/method

Question 33

how to apply LSP

Answer 33

extend base class?

Question 34

how to apply ISP

Answer 34

add an interface for classes to implement as needed but let the abstract class only include the general methods

Question 35

how to apply DIP

Answer 35

connect dependencies through an interface

Question 36

a risk can affect (3 things)

Answer 36

product, project, business

Question 37

4 different components of risk management

Answer 37

identification, analysis, planning, monitoring

Question 38

risk planning has 3 stages

Answer 38

avoidance, minimization, contingency