Implementing the Waterfall Model for Online Pharmacy Software

This report analyzes the Waterfall Model within the context of software development, specifically for an online pharmacy. The assignment begins by introducing the Waterfall Model, highlighting its sequential nature and the various phases involved, including requirements gathering, design, implementation, testing, and maintenance. The report details the activities within each phase, such as gathering requirements from the hospital, designing the website's architecture, coding, and performing verification tests. It also outlines the different types of testing, like functionality, usability, and security. The report then discusses non-functional requirements like availability, load testing, and performance testing, along with functional requirements such as online patient forms and transaction details. The report concludes with references to relevant literature on the Waterfall Model, providing a comprehensive understanding of the software development life cycle and its application.

Running head: LIFE CYCLE
Life Cycle
Name of the Student:
Name of the University:
Author note:

1LIFE CYCLE
1. The life cycle model for the project:
The life cycle model that has been chosen for the project is the waterfall model.
This is one of the easiest model in the development phase of the software. It is a
sequential model which divides the phases of development into several parts for
performing the activities and operations on the particular phases. The entire requirement
of the project is understood clearly with the help of this phase.
One of the major discredit of using this model is, this project is not a complete
project and waterfall model does not allow changes after completion of one phase.
2. Activities of the waterfall model:
There are 6 phases in the waterfall-model and they includes requirements, design,
implementation, testing, deployment and maintenance phase.
Requirement stage:
 Specific requirements are identified.
 The information regarding the software are gathered from the hospital.
 Certain documentation regarding patients requirements are done from the
in-store pharmacies or online sources.
Design stage:
 The blueprint of the online pharmacy is developed.
 The entire design of the webpage is demonstrated such that the
functioning like the log-in ids and passwords, and other functionalities are
well explained. 1
 A language is chosen for developing the code.
1 Ruparelia, Nayan B. "Software development lifecycle models." ACM SIGSOFT Software Engineering Notes 35,
no. 3 (2010): 8-13.

2LIFE CYCLE
Implementation:
 In order to successfully design the blueprints, codes are developed.
 Proper coding languages, that are chosen in the designing phase is
implemented.
Verification:
 This is done in order to check whether the website is performing as
planned, whether the patients log-in, passwords, registration form and etc.,
are working properly or not.
Maintenance:
 The maintenance team is continuously working on monitoring the
performance of the E-website in order to check the patients’ portal for
vulnerabilities and protection against them.2
3. The proposed website will be tested by following 8 steps: Functionality testing (in this
testing phase the functions of the website will be verified to decided whether it is
working properly or not, testing of links, URLs, forms, cookies and so on), usability
testing (in this testing phase, all the aspects of the proposed website will be verified like
site navigation and many more), interface testing (three areas of the website will be tested
application, database server and the web server), database testing (all database regarding
functions will be checked), compatibility testing (browser compatibility testing will be
done in this phase), performance testing, security testing (authorization and encryption
2 Petersen, Kai, Claes Wohlin, and Dejan Baca. "The waterfall model in large-scale development." In International
Conference on Product-Focused Software Process Improvement, pp. 386-400. Springer, Berlin, Heidelberg, 2009.

3LIFE CYCLE
will be tested in this phase) and lastly crowd testing (ability of multitasking of the
website)
4. Non-functional requirements:
 Availability: this is done to check the availability of the information to the
patients or how they will be represented.
 Load Testing: this is done with multiple patients trying to access the
website at the same time. The effectiveness of the website can be checked.
 Performance Testing: The efficiency of the website is verified by
calculating the time between the form-fill-up and confirmation mail.
5. Functional requirement:
 The form for filling up the details of the patients online.
 The confirmation mail for the patient’s verification.
 The details of the transaction including the credit details, addresses and few other
crucial details of the patients.

4LIFE CYCLE
References:
Petersen, Kai, Claes Wohlin, and Dejan Baca. "The waterfall model in large-scale development."
In International Conference on Product-Focused Software Process Improvement, pp.
386-400. Springer, Berlin, Heidelberg, 2009.
Ruparelia, Nayan B. "Software development lifecycle models." ACM SIGSOFT Software
Engineering Notes 35, no. 3 (2010): 8-13.