7. 1.analysis of project requirements :
1. input data and desired output
2. processing required to transform input to
output
3.cost benifit analysis
4.schedule of project
2.technical feasibility :
focuses on:
1. availability of software tools
2.availability of hardware
3.availability of skilled software professionals
8. at the end of this phase a feasibility
report is generated.
9.
10. 1.an SRS ( software requirement specification)
document is generated.
2. SRS is a formal document includes
performance, functional, software ,hardware and
network requirements of the project.
3.it acts as an agreement between development
team and customer .
14. implementing the design specified in
design document to an executable
programming language code.
15.
16. code is mapped against design document
test plan involves:
1. test case generation
2. testing criteria
3. resourse allocation for testing
17.
18. 1. handling errors that may exist in
software even after testing phase
2. implementation of new requirements
after software is deployed at customer
location.
21. uses linear approach ,
that means it provide no process
to go back to previous phase to
handle changes in the
requirement.
22.
23. 2. a prototype is generated acc to
requirements of software that tells
customer how the software is going to
function and to get better knowledge of
requirements.
until the customer approves the prototype ,
generating a new prototype is continued (
before finalizing and frozing the
requirements )
24. types of prototypes :
1. throwaway prototypes: those
prototypes that are eventually
discarded rather than becoming a
part of finally delivered software.
2. evolutionary prototypes: are those
that evolve into the final system
through iterative incoorperation of
user(ustomer) feedback.
25.
26. includes both iterative nature of
prototyping approach and linear
nature of waterfall approach.
example: evolution of windows
operating system from windows 3.1 to
windows 2000
27.
28. here the concept is same as spiral
approach but also includes
time of identifying
requirements,communication and
planning
29.
30. there are number of functional units ,
each containing group of similar tasks.
each functional unit is implemented
with an increment and final product is
acheived after all units are
implemented in the development
process.
33. 1. classes and objects
classes: an abstract data type that
contains set of attributes and functions.
object: instance of class
all the objects share same copy of
member functions ,but maintain a
seperate copy of the member data.
34. 2. inheritance :
sharing of attributes and behaviours
among classes based upon hierarchial
relationship.
35. 3. abstraction:
focuses on essential inherent aspects of
an entity ignoring its implementation
detdails .
