Process Model Used
In my project, I have used
waterfall model. This model is used when requirements are well defined and
reasonably stable, and in my project ‘Library Management System’ all the
requirements are well defined.
The waterfall model, sometimes
called the classic life cycle, suggests a systematic, sequential approach to
software development that begins with customer specification of requirements
and progresses through planning, modeling, construction and deployment,
culminating in on-going support of the complete software.
I have defined activities and
represented them into seperated process phases. All the stages overlap and fed
information to each other. It is not a simple linear model but involves a
sequence of iterations of development activities.
This model is appropriate for my
project as I had ample of time for designing it, so the time constraints were
not there. This model generally takes more time to complete the software life
cycle as when a stage completes it is signed off and development goes onto the
next stage.
No comments:
Post a Comment