Waterfall Methodology for the Doneslouching.com Project
The scope of the project of developing the website doneslouching.com is clear along with the clear requirements, and hence, the use of Waterfall project development methodology is suggested. The waterfall method indicates a Sequential Development Process where a particular phase begins only after the end of the previous phase (Andrei et al., 2019). All the phases of the waterfall method are carried out sequentially, and hence, it is possible to deliver software within a fixed time. The details of the chosen software development methodology are presented in the following diagram-
Figure 1: SDLC (Waterfall)
(Source: Prepared by the author using MS Visio)
As indicated in the above figure, in this methodology, the end of one phase indicates the beginning of the next; therefore, only after completion of the requirements analysis phase, the design phase starts and so on (Balaji & Obaidy, 2016). Since the requirement of this project is clear, the choice of this methodology is justified.
The project life cycle indicates the steps that a project manager is required to consider for successful project management and delivery. A project life cycle generally has four phases, which are presented in the following diagram-
Figure 2: Showing the Project Lifecycle
(Source: Prepared by the author using MS Visio)
As indicated in the above figure, the four phases of a project lifecycle are initiation, planning, execution and closure (Akinsola et al., 2020). Along with that, every phase of this project requires appropriate monitoring and control to ensure the successful delivery of the website on time.
The details of all the actors associated with the project and the system are presented in the following table-
|
Actor |
Category |
Type |
Description |
|
Farmer |
Primary |
Human Actor |
This is a primary actor who will be subscribing to the website to get the necessary manpower for fruit picking activities. |
|
Fruit Picker |
Primary |
Human Actor |
This is another primary actor who will be responsible for volunteering the fruit picking activities and receiving payment for the same or gifts from the farmer. |
|
Gift Manager |
Secondary |
Human Actor |
This actor is responsible for providing gifts to those fruit pickers who are not taking any payment but are helping the farmers with fruit picking. |
|
Administrator |
Abstract |
Non-human actor |
This is a non-human yet one of the most important actors. This actor is accountable for all the works related to managing website’s smooth operation, through regular back up of data, upgradation and easier data recovery. |
Table 1: Showing the details of the Actors associated with the system
The use case diagram showing the main functionality of the doneslouching.com website is presented as follows-
Figure 3: Illustrating the Use Case Diagram
(Source: Prepared by the author using MS Visio)
The above picture presents a detailed description of the use cases associated with the operations of the website doneslouching.com.
The use case description associated with all the use cases represented in figure 3 is presented in the following tables-
|
Use Case Number |
1 |
|
Use Case Type |
Base |
|
Use Case Name |
Registers |
|
Actor Involved |
Farmer |
|
Associated Data Sources |
Contact Details, Farm Details and Tax |
|
Associated User Interface |
Registration |
|
Pre-Conditions |
NA |
|
Post-Conditions |
Subscription |
|
Detailed Description |
A farmer is required to register to the website to enrol themselves in the subscription process. |
|
Normal Course of Events |
|
|
Alternate Course |
Farmers directly select from the associated pickers. |
|
Use Case Number |
2 |
|
Use Case Type |
Base |
|
Use Case Name |
Approves |
|
Actor Involved |
Farmer |
|
Associated Data Sources |
Requested schedule by the fruit pickers |
|
Associated User Interface |
Registration and Subscription |
|
Pre-Conditions |
Both farmer and fruit pickers need to register |
|
Post-Conditions |
Approval of the schedule |
|
Detailed Description |
The farmer is responsible for the approval of the schedule requested by the fruit picker. |
|
Normal Course of Events |
|
|
Alternate Course |
The schedule is approved by the system based on the dates requested by the farmer. |
|
Use Case Number |
3 |
|
Use Case Type |
Base |
|
Use Case Name |
Manage Account |
|
Actor Involved |
Fruit Picker |
|
Associated Data Sources |
Data related to the schedule of their visit |
|
Associated User Interface |
Registration to the website |
|
Pre-Conditions |
The fruit picker needs to register on the website. |
|
Post-Conditions |
The schedule request will be accepted or rejected. |
|
Detailed Description |
The website will allow all the fruit pickers to easily manage their accounts. |
|
Normal Course of Events |
|
|
Alternate Course |
The administrator can also take the responsibility of account management. |
|
Use Case Number |
4 |
|
Use Case Type |
Base |
|
Use Case Name |
Select/schedule |
|
Actor Involved |
Fruit Picker |
|
Associated Data Sources |
Calendar data |
|
Associated User Interface |
Registration and Account Management |
|
Pre-Conditions |
The fruit picker needs to register on the website |
|
Post-Conditions |
Volunteering for the fruit picking activities |
|
Detailed Description |
The fruit picker is allowed to select a schedule for fruit picking and can also request a schedule. |
|
Normal Course of Events |
|
|
Alternate Course |
The system admin can schedule the fruit picking activities. |
|
Use Case Number |
5 |
|
Use Case Type |
Base |
|
Use Case Name |
Registers |
|
Actor Involved |
Fruit Picker |
|
Associated Data Sources |
Personal and contact details |
|
Associated User Interface |
Registers |
|
Pre-Conditions |
NA |
|
Post-Conditions |
Account management, payment, gifts |
|
Detailed Description |
In order to volunteer for fruit picking, the fruit picker first needs to register to the website. |
|
Normal Course of Events |
|
|
Alternate Course |
The fruit picker can directly contact the farmer. |
|
Use Case Number |
6 |
|
Use Case Type |
Abstract (include) |
|
Use Case Name |
Contact details |
|
Actor Involved |
Farmer |
|
Associated Data Sources |
Registration |
|
Associated User Interface |
Registration Page of the Website |
|
Pre-Conditions |
Registration |
|
Post-Conditions |
Accepting/Rejecting the Picker’s schedule |
|
Detailed Description |
While registering to the website, the farmer is required to provide their contact details. |
|
Normal Course of Events |
|
|
Alternate Course |
The registration process may not involve providing contact details to access the website. |
|
Use Case Number |
7 |
|
Use Case Type |
Abstract (include) |
|
Use Case Name |
Farm Address |
|
Actor Involved |
Farmer |
|
Associated Data Sources |
Registration |
|
Associated User Interface |
Registration Page of the Website |
|
Pre-Conditions |
Farmer’s Registration |
|
Post-Conditions |
Accepting/Rejecting the Picker’s requested schedule |
|
Detailed Description |
While registering to the website, the farmer is required to provide their farm address so that it is easier for the pickers to identify the location. |
|
Normal Course of Events |
|
|
Alternate Course |
The registration process may not involve providing the farm details. |
|
Use Case Number |
8 |
|
Use Case Type |
Abstract (include) |
|
Use Case Name |
Tax Details |
|
Actor Involved |
Farmer |
|
Associated Data Sources |
Registration |
|
Associated User Interface |
Registration Page of the Website |
|
Pre-Conditions |
Farmer’s Registration |
|
Post-Conditions |
Accepting/Rejecting the Picker’s requested schedule |
|
Detailed Description |
While registering to the website, the farmer is required to provide their tax details so that it is easier for the pickers to identify the location. |
|
Normal Course of Events |
|
|
Alternate Course |
The farmers can provide their tax details only during payment. |
|
Use Case Number |
9 |
|
Use Case Type |
Base |
|
Use Case Name |
Data Backup |
|
Actor Involved |
Administrator |
|
Associated Data Sources |
Farmer and picker's data |
|
Associated User Interface |
Website interface |
|
Pre-Conditions |
Farmer and picker providing data |
|
Post-Conditions |
Smooth system functionality |
|
Detailed Description |
The administrator is responsible for regular data backup. |
|
Normal Course of Events |
|
|
Alternate Course |
Data backup is not done. |
|
Use Case Number |
10 |
|
Use Case Type |
Base |
|
Use Case Name |
Recovery |
|
Actor Involved |
Administrator |
|
Associated Data Sources |
Farmer and picker's data |
|
Associated User Interface |
Website interface |
|
Pre-Conditions |
Data Backup |
|
Post-Conditions |
The smooth functioning of the website |
|
Detailed Description |
Data recovery in the responsibility of the administrator in times of any disaster. |
|
Normal Course of Events |
|
|
Alternate Course |
Data recovery facility is absent on the website |
|
Use Case Number |
11 |
|
Use Case Type |
Base |
|
Use Case Name |
Upgrade |
|
Actor Involved |
Administrator |
|
Associated Data Sources |
Farmer and picker's data |
|
Associated User Interface |
Website interface |
|
Pre-Conditions |
Data Backup |
|
Post-Conditions |
The smooth functioning of the website |
|
Detailed Description |
The administrator is responsible for the regular upgrade of the website. |
|
Normal Course of Events |
|
|
Alternate Course |
The website upgrade will be done only when required. |
|
Use Case Number |
12 |
|
Use Case Type |
Base |
|
Use Case Name |
Allocated Gift |
|
Actor Involved |
Gift Manger |
|
Associated Data Sources |
Payment details of the Pickers |
|
Associated User Interface |
Work scheduling and payment of the pickers |
|
Pre-Conditions |
No payment is given to pickers |
|
Post-Conditions |
The farmer decides the gift |
|
Detailed Description |
The gift manager is responsible for allocating gifts for the pickers. |
|
Normal Course of Events |
|
|
Alternate Course |
No gift is allocated for the picker if they wish not to accept payment. |
|
Use Case Number |
13 |
|
Use Case Type |
Abstract |
|
Use Case Name |
Bank Details |
|
Actor Involved |
Picker and Gift Manager |
|
Associated Data Sources |
Payment of the Picker |
|
Associated User Interface |
Website interface |
|
Pre-Conditions |
Picker providing bank details |
|
Post-Conditions |
Picker accepting payment |
|
Detailed Description |
The gift manager checks if the picker has any bank details. The absence of bank details indicates that the picker has not accepted any payment. |
|
Normal Course of Events |
|
|
Alternate Course |
No gifting options are available. |
Table 2: Showing the details of all the use cases
References
Andrei, B. A., Casu-Pop, A. C., Gheorghe, S. C., & Boiangiu, C. A. (2019). A study on using waterfall and agile methods in software project management. Journal Of Information Systems & Operations Management, 125-135. Retrieved from: https://www.rebe.rau.ro/RePEc/rau/jisomg/SU19/JISOM-SU19-A12.pdf
Akinsola, J. E., Ogunbanwo, A. S., Okesola, O. J., Odun-Ayo, I. J., Ayegbusi, F. D., & Adebiyi, A. A. (2020, July). Comparative analysis of software development life cycle models (SDLC). In Computer Science On-line Conference (pp. 310-322). Springer, Cham. Retrieved from: https://link.springer.com/chapter/10.1007/978-3-030-51965-0_27
Balaji, S., & Obaidy, M. A. (2016, March). Project characteristics used for methodology selection to develop the software project. In 2016 International Conference on Electrical, Electronics, and Optimization Techniques (ICEEOT) (pp. 3570-3573). IEEE. DOI: 10.1109/ICEEOT.2016.7755370. Retrieved from: https://ieeexplore.ieee.org/abstract/document/7755370
To export a reference to this article please select a referencing stye below:
My Assignment Help. (2022). Project Development Methodology And Use Case Description For Doneslouching.com. Retrieved from https://myassignmenthelp.com/free-samples/mis605-systems-analysis-and-design/sequential-development-process-file-A1DDE66.html.
"Project Development Methodology And Use Case Description For Doneslouching.com." My Assignment Help, 2022, https://myassignmenthelp.com/free-samples/mis605-systems-analysis-and-design/sequential-development-process-file-A1DDE66.html.
My Assignment Help (2022) Project Development Methodology And Use Case Description For Doneslouching.com [Online]. Available from: https://myassignmenthelp.com/free-samples/mis605-systems-analysis-and-design/sequential-development-process-file-A1DDE66.html
[Accessed 19 August 2024].
My Assignment Help. 'Project Development Methodology And Use Case Description For Doneslouching.com' (My Assignment Help, 2022) <https://myassignmenthelp.com/free-samples/mis605-systems-analysis-and-design/sequential-development-process-file-A1DDE66.html> accessed 19 August 2024.
My Assignment Help. Project Development Methodology And Use Case Description For Doneslouching.com [Internet]. My Assignment Help. 2022 [cited 19 August 2024]. Available from: https://myassignmenthelp.com/free-samples/mis605-systems-analysis-and-design/sequential-development-process-file-A1DDE66.html.
WhatsApp
