chapter 5 Flashcards
software Process
concrete proces of software developement
software Processmodel
formal/precise definition of software development
order of activity
methods,equipement,techniques needed
lebenszyklusmodell
determination of the essential types of development activitie
s its dependencies
why there are different life cycle models
development projects can present structurally diverse requirements,
code and fix model
writing code and fixing errors
with no prior phase for analysis design and planning
negative
unstructured code, not maintainable,
difficult bug fixing no documentation
waterfall model
it has clear phase, software anforderung->analysis->entwurf->programing->testing->
there is also feedback
benefits of using waterfall model
it has clear phase and clear responsibility
implementation after analysis of problems
disadvantage of waterfall model
doesnt account for iterative development driven by insights
phases cannot overlap
over abstraction
EMPHASIS ON fully elaborated documents
spital model
identification of goals contrainits alternative
risk management (Assesment treatment evaluation)
testingt and developement
review
advantage and disadvantage os spiralmodel
regular review at intervals
potentially redefining the process flow
flexibility errors are elimit
nachteil
management high
for small projects
Prototypes
usage
throw away prototypes
evolutinary increment prototypes
implementation of prototypes
horizontal and vertical prototypes
horizontal prototype
implement only specific layer of the system
ve
vertical prototypes
implement selected part of the target system fully accross all layer
prototyping Modells
vorteil- geeignete werkzeuge schnell erstellt werden
increase creativity
intense feedback from end user
reduction of develompment risk
negative
part of the product
v model
horizantal for time
vertical for details of developement
mix of warerfall model
advantage of v model
quality ensurence
clear distinction between constructive and evaluate activity
disadvantage
testing is able after implementation
no insight gaining through iteration
v model bund
it is a software process model that provides precise guidelines and specifically defines activities roles
v model
basic idea. process is divided into four areas of activity
->system dev
Quality Assurance
Project magement
configuration management
v model 95
is too much basically
v model xt
tailoring
every has a use
v model bund vorteil
integration of se qs km pm
identifikation of roles and definition
it sees a lot of aspects
nachteil complex and training
