07 March 2007

Software Engineering: Waterfall Development (Definitions)

"A method in which each stage is completed before the product is passed on to the next stage. Each stage is discrete and self-contained." (Jesse Liberty, "Sams Teach Yourself C++ in 24 Hours" 3rd Ed., 2001)

"The simplest sequential software process model, where the analysis, design, coding, and testing phases are done sequentially for the entire system." (Johannes Link & Peter Fröhlich, "Unit Testing in Java", 2003)

"A product development process that follows the sequence of analyze, design, code, and test. The underlying assumption is that each phase does not begin until the preceding phase is complete. There are no overlaps or iterations." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"A predictive development where each project phase flows into the next." (Rod Stephens, "Beginning Software Engineering", 2015)

"A methodical and linear approach to technical development. While rigorous, waterfall development usually implies going through an entire development lifecycle before deploying functionality to end users, and usually begins with business analysis. See Top-down development." (Evan Levy & Jill Dyché, "Customer Data Integration", 2006)

"An approach to software development in which the requirements, architecture, design, implementation, integration, and testing are sequentially defined." (Bruce MacIsaac & Per Kroll, "Agility and Discipline Made Easy: Practices from OpenUP and RUP", 2006)

"A sequential software development process in which progress is seen as flowing steadily downward (like a waterfall) through the phases of conception, initiation, analysis, design, development, testing, and deployment." (Mark S Merkow & Lakshmikanth Raghavan, "Secure and Resilient Software Development", 2010)

"A systems development methodology that dictates the completion of one activity before beginning the next." (James Robertson et al, "Complete Systems Analysis", 2013)

"The SDLC, so called because any one development activity must be done before the next activity can begin and because the output from any one level of activity becomes the input into the next level." (Daniel Linstedt & W H Inmon, "Data Architecture: A Primer for the Data Scientist", 2014)

"A development model that uses a series of waterfall cascades. Each cascade ends with the delivery of a usable application called an increment." (Rod Stephens, "Beginning Software Engineering", 2015)

"A linear and sequential development methodology where, for the product development part, product managers define all aspects of the product before it is given to engineering to create. There is no official role for feedback loops and flexible changes in waterfall development." (Pamela Schure & Brian Lawley, "Product Management For Dummies", 2017)

"A method of deploying software or systems in which development moves through a series of fairly well-defined stages. With large projects, once each stage is complete, it cannot be easily reversed, much as it is impossible to move up a waterfall. This traditional system engineering flow allows for a requirements-driven process that leads to assured and verified function. Note that although this indicates a linear sequence through the stages, the ability to iterate and propagate changes discovered in one facet to the others is typically observed." (William Stallings, "Effective Cybersecurity: A Guide to Using Best Practices and Standards", 2018)

No comments:

Related Posts Plugin for WordPress, Blogger...

About Me

My photo
IT Professional with more than 24 years experience in IT in the area of full life-cycle of Web/Desktop/Database Applications Development, Software Engineering, Consultancy, Data Management, Data Quality, Data Migrations, Reporting, ERP implementations & support, Team/Project/IT Management, etc.