Requirements, Design, Architecture

Question 1

7 activities for requirements gathering

Answer 1

inception

elicitation

elaboration

specification

validation

negotiation

management

Question 2

what is requirements inception?

Answer 2

identify the client’s problem, users, and needs

Question 3

what is requirements elicitation?

Answer 3

to figure out what the user wants in a software system

Question 4

what is requirements elaboration?

Answer 4

to refine and get more detailed wants/needs from the clients/users

Question 5

what is requirements specification?

Answer 5

a formalization of the wants

Question 6

what is requirements validation?

Answer 6

figure out the metrics for customer approval

how can we show that we have built something to the customers liking

Question 7

what is requirements negotiation?

Answer 7

resolves conflicts over cost, time and scope and find an appropriate balance

Question 8

what is requirements management?

Answer 8

determine who is tracking the requirements, and the people responsible for certain requirements

Question 9

8 requirements modeling approaches

Answer 9

scenario approach (paragraph based)

class approach

event-state behavior approach

data approach (db and functions acting on it)

data flow architecture (like assembly line)

OO analysis

Reusable focus

UML

Question 10

What are CRC cards?

Answer 10

Class responsibility collaboration cards. They detail the functionality of a class and everything that class interacts with

Question 11

3 types of classes

Answer 11

entity classes

boundary classes

controller classes

Question 12

what is an entity class?

Answer 12

a class that acts a wrapper for data

Question 13

what is a boundary class?

Answer 13

a class that manages communication with the outside

Question 14

what is a controller class?

Answer 14

a class that performs actions and tasks

Question 15

describe an a sequence or poll diagram

Answer 15

each pole is a class and the lines between them represent communication between the design classes

Question 16

whats does FURPS stand for?

Answer 16

functionality
usability
reliability
performance 
support

Question 17

5 design class types

Answer 17

UI class (front end)

business class (user domain classes)

process class (CS level classes that support business classes)

persistent class (like a database)

system class (things like logging, networking etc.)

Question 18

8 Architectural Styles

Answer 18

data centered (use DB)

data flow (sequential)

call & return (function calls)

RPC (remote procedure call)

OO (with agents, data, and methods)

layered (embedded systems)

MVC (model view controller)

others

Question 19

what is SOLID

Answer 19

single responsibility

open-closed principle

Liskov substitution principle

interface segregation

dependency inversion

Question 20

What is S in SOLID

Answer 20

single responsibility

a given function/class/module whatever has a single overall functionality

Question 21

What is O in SOLID

Answer 21

open-closed principle

code is open to extension but closed to modification

Question 22

What is L in SOLID

Answer 22

liskov substitution principle

any derived class instance should be able to be used in place of a parent class instance. When so, the derived class should act as a parent class

Question 23

What is I in SOLID

Answer 23

interface segregation

when a module interacts with a helper, the helper should have a wrapper API for these interactions that only exposes the information the module needs while hiding any other information that it doesn’t

Question 24

What is D in SOLID

Answer 24

dependency inversion

any interactions or dependencies that a module has with a helper should be through a helper API (or abstraction) and not the helper itself

“depend on abstractions not concretions”

Question 25

4 UI rules

Answer 25

don’t make the user work hard

use user domain concepts and names

similar things should look the same throughout

always show system progress

Question 26

6 UI design issues

Answer 26

response time
user help
error handling
command labeling
accessibility
internalization

Question 27

Coplein definition of design pattern

Answer 27

a pattern that solves a problem, its a proven concept, the solution to the problem is not inherently obvious, shows the structure between the parts, simple to understand

Question 28

3 types of design patterns

Answer 28

creational (to make things)

structural (to help simplify relationships)

behavioral (to with responsibilities)