Exam 1

Question 1

what are the types of processes for developing software?

Answer 1

agile, xp, waterfall

Question 2

what is agile?

Answer 2

fast, iterative, early, cheap, working software at the end

Question 3

difference between validation and verification?

Answer 3

verification comes first. first find out if the software works ok. then check if the software meets the requirements.

Question 4

what is waterfall?

Answer 4

sequential. do it and then go to the next step. changes aren’t happening. need fixed requirements like the government.

Question 5

what are the waterfall model activities?

Answer 5

1. speak with client to create requirements.
2. planning
3. design
4. coding/implementation
5. testing
6. deployment
7. maintenance

Question 6

which is the most expensive step?

Answer 6

maintenance

Question 7

which takes a long time?

Answer 7

maintenance

Question 8

which is the hardest to do?

Answer 8

maintenance

Question 9

what is the difference between validation testing and acceptance testing

Answer 9

valid meets the requirements. acceptance in the customers environment

Question 10

dif b/w construction and implementation

Answer 10

construction - coding and testing

implementation - coding

Question 11

what is deployment

Answer 11

releasing the build tothe user

Question 12

what happened to waterfall? why all about agile?

Answer 12

want to make changes. reuse products.

Question 13

what is legacy software?

Answer 13

old software. DMV software. cant befixed or maintained.

Question 14

in group projects, the project manager keeps track of everything. what are the consequences of a poor decision?

Answer 14

repeat work, delays, cost more, falls apart

Question 15

what is scope

Answer 15

boundaries of the requirements of the project. what is in the system and what is out.like contract between customer. text and use cases.

Question 16

what is recovery testing

Answer 16

what happens after the crash? does the dataget saved?

Question 17

what is security testing>

Answer 17

try to find security holes in application

Question 18

stress testing

Answer 18

see how many users the system can support. find the breaking point.

Question 19

unit testing

Answer 19

check each small part. white box testing.

Question 20

black box testing

Answer 20

feed input. all you care about is output

Question 21

which comes first black box or white box?

Answer 21

white box testing

Question 22

what is scenario based testing?

Answer 22

create scenarios based on use cases and test them.

Question 23

what is quality?

Answer 23

meets all of the requirements if they exist.

Question 24

what are the rules of customers in agile developments?

Answer 24

meet with them a lot. make sure doing the job right. get feedback.

Question 25

what are the rules of end users?

Answer 25

customer pays you, end user uses the system

Question 26

what are the six steps of requirement engineering?

Answer 26

1. inception -ask questions 2. elicitation- what do they mean by what they say. 3. elaboration 4. negotiations - this requirement will take this long 5. specifications - requirements are concrete now 6. validation - run software against all the specifications

Question 27

what is user interface

Answer 27

what the user sees and interacts with, put user in control

Question 28

who is responsible to gather the requirements

Answer 28

developers

Question 29

who is responsible to prioritize requirements?

Answer 29

customer

Question 30

responsible to estimate the cost of requirement?

Answer 30

developers

Question 31

what different typeof software is there?

Answer 31

webapps, embeddedsystem, system software, driver, kernel, OS, legacy, cloud computing

Question 32

difference b/w software and hardware?

Answer 32

software developed. hardware wears out

Question 33

what is UML

Answer 33

unified modeling language. can model anything

Question 34

what is a requirement

Answer 34

a need. a demand of the customer.

Question 35

why are requirements important

Answer 35

what the customer wants. vague requirements can ruin requirements.

Question 36

requirements

Answer 36

needs; ex.- user login - functional

Question 37

non-functional requirements

Answer 37

if passwords contain special characters

Question 38

requirements types

Answer 38

security;usability

Question 39

how do you come up with nonfunctional requirements?

Answer 39

for each functional requirement, come up with 10-100 nonfunctional requirements

Question 40

what are requirements take form of

Answer 40

simple sentences

Question 41

what does the product have to agree with

Answer 41

the requirement list

Question 42

what is scope

Answer 42

what features are in and out

Question 43

what are problems of requirements

Answer 43

understanding change; scope

Question 44

how do you write down the functional requirements for projects

Answer 44

1. define users 2. the use cases 3. interactions between the end user and the system 4. non-functional requirements

Question 45

what is a use case

Answer 45

an interaction between user and the system

Question 46

primary actors

Answer 46

benefits directly from the system

Question 47

secondary actors

Answer 47

gives out benefit to the primary

Question 48

off stage

Answer 48

irs, nsa, police

Question 49

what form is a use case?

Answer 49

use cases are text

Question 50

what is uml

Answer 50

it is a use case diagram

Question 51

what is the software process

Answer 51

method to manage; life cycle; plan and steps to manage the life cycle of the project

Question 52

what is the generic process

Answer 52

1. understand the problem - ask questions; requirements ; analyze

Question 53

what is rup inception?

Answer 53

short step to establish a common vision and basic scope. end result is to determine whether or not to continue.