Table of Contents
Important Aspects of the Case Study
In the context of the case study, the challenge associated with the courier service is addressed with an apt solution. All the way through that one is able to solve similar types of challenges faced by the customers with immediate effect. This helps in the building of confidence amongst them and explains the customer’s experience associated with the system’s functionality and its interface uses.
The courier application’s overall functionality as well as non-functioning specifications are elaborated in this case study. ECC is instrumental in offering a faster as well as a secure alternative in the direction of delivering items when compared with its competitors.
The Courier Company’s strategy and the whereabouts of the application's working are mentioned in context of this case study. This describes the ways the customers as well as the delivery agent will log in after the courier’s order. They also mention that the request needs to be allocated in the direction of the nearest agent to ensure faster processing as well as the sending of relative information. It will also help the customers with the calculated cost details and estimated delivery time (Srivastava, Bhardwaj & Saraswat, 2017).
The end features associated with user’s variety includes the below-mentioned ones:
System development life Cycle
Hardware or software systems are much needed to maintain the functionality in the direction of undergoing a phase of development that is viewed in a multi-step process of iteration. 7 SDLC phases are used in the direction of providing a formal framework as well as refers to the meaning that explains those steps involved in program’s construction (Lakshmisri, 2017).
This step refers to the procedure of designing the systems. It is a beginning strategy for a business project associated in the direction of obtaining capital that expands on the basis of infrastructural change or service enhancement (Srivastava, Bhardwaj & Saraswat, 2017).
System Analysis and Requirements
During critical situations, an alternative solution identifies as well as evaluates the findings with the best match associated with a project's goals (ultimate). It refers to the teams that find the project or solution as a practical specification. This study refers to a method that takes place (Schön, Thomaschewski & Escalona, 2017).
The 3rd step is instrumental in defining in detail, the required types of specifications, features as well as operations that accomplish the functional aspect associated with the proposed system.
The 4th step starts, when a programmer, network software engineer, or developer is entitled to carry out the main work project.
Integration and Testing
The 5th step is instrumental in including the system’s development as well as associated with the system’s testing conducted by Quality Assurance specialist.
The sixth step refers to the place in which most of the software coding is written. Moreover, this step includes the newly created program and its implementation.
Operation and Maintenance
This stage refers to finishing touches that are given to systems to enhance performance, by adding a new feature that helps to remove bugs or is instrumental in adding additional user requirements.
Adaptive and Predictive Approaches
Solutions associated with Adaptive SDLC’s suit potential projects with major design or ambiguity to decide on the item of expectation as these projects require a change in customer’s demands.
The adaptive SDLC technique is faster than predictive approaches associated with SDLC (Azanha et al., 2017).
The key predictive SDLC’s approach is concerned with the production as well as the end product’s requirements maintenance. Making it project perfect for the final product with a clear vision of all requisite specifications that are specified as well as understood (Lakshmisri, 2017).
The predictive approach can highly be restrictive, which forces developers throughout the life cycle in the direction of maintaining strict standards. In view of the fact that the job sequence already being predetermined any type of future modifications can cost high as well as time-consuming.
Limitations and usefulness (Predictive approach)
Changes in regard to specific specifications of project are merely not are possible. The condition in context to what the final deliverable product will be very well known. This is important because any future improvement at the end of the project is very hard and costly to subject in a predictable way.
Projects need to work in a registered manner toward their successful completion (Kyeremeh, 2019).
The predictability is liked and wanted by the developer to get a good picture of the possible / expected combination in advance. This is not the best SDLC model with complex projects. Predictive SDLC is not eligible for complex projects involving variable specification or the final product's uncertainty (Gonçalves, 2018).
Limitations and usefulness (Adaptive Approach)
There is no clear idea of how the final product will turn out to be, the adaptive approach can be subjected when the project is innovative and exploring in nature. Employees work at a flexible pace with the fast operational industry. This requires visible customer or user interaction spread across all SDLCs requiring frequent changes to be made at the right time for production, resulting in less documentation (Kyeremeh, 2019).
To develop a courier application Agile approaches will be used in this given scenario
Strategic AGILE methodology facilitates continuous creation and testing imitation associated with the development of life cycle based software project (Campbell et al., 2016).
Properties indicate toward the consumer’s opportunity to view the product in advance and frequently make decisional changes in the project. The error at the center of the project can be corrected. The smart Agile Approach advises to expand and repeat in software design. The manufacturing process is repeated and the repetition takes place within a few weeks (Vohra, 2017).
The agile methods mentioned above will choose the SCRUM method.
SCRUM’s agile development process subjects on the ways a project can be carried out within an environment that is team-based. SCRUM refers to action within a production team which is committed as well as supporting encouraging small teamwork consisting of 3 functions, as well as their outlined duties (Alliance, 2017).
A repository of specifications monitored with information in regards to the specification's number or (user stories) that are in need to be met related to each update. The brand Manager maintains as well as prioritizes these aspects by circulating them to the scrum team. The team requests new requirement those are added, deleted, or altered (Hoda & Noble, 2017).
In context to the ECC case study Interviews as well as prototyping techniques are preferred it will ask the stakeholders below mentioned questions:
Functional and Non Functional Requirements
Non Functional Requirements
Alliance, A. G. I. L. E. (2017). Agile Practice Guide This book. Project Management Institute.
Azanha, A., Argoud, A. R. T. T., de Camargo Junior, J. B., & Antoniolli, P. D. (2017). Agile project management with Scrum. International Journal of Managing Projects in Business.
Campbell, J., Kurkovsky, S., Liew, C. W., & Tafliovich, A. (2016, February). Scrum and agile methods in software engineering courses. In Proceedings of the 47th ACM Technical Symposium on Computing Science Education (pp. 319-320).
Gonçalves, L. (2018). Scrum. Controlling & Management Review, 62(4), 40-42.
Hoda, R., & Noble, J. (2017, May). Becoming agile: a grounded theory of agile transitions in practice. In 2017 IEEE/ACM 39th International Conference on Software Engineering (ICSE) (pp. 141-151). IEEE.
Khmelevsky, Y., Li, X., & Madnick, S. (2017, April). Software development using agile and scrum in distributed teams. In 2017 Annual IEEE International Systems Conference (SysCon) (pp. 1-4). IEEE.
Kyeremeh, K. (2019). Overview of System Development Life Cycle Models. Available at SSRN 3448536.
Lakshmisri, S. (2017). System Development Life Cycle Models. International Journal of Creative Research Thoughts (IJCRT), ISSN, 2320-2882. Available at SSRN: https://ssrn.com/abstract=3674368
Schön, E. M., Thomaschewski, J., & Escalona, M. J. (2017). Agile Requirements Engineering: A systematic literature review. Computer Standards & Interfaces, 49, 79-91.
Sharma, S., & Hasteer, N. (2016, April). A comprehensive study on state of Scrum development. In 2016 International Conference on Computing, Communication and Automation (ICCCA) (pp. 867-872). IEEE.
Srivastava, A., Bhardwaj, S., & Saraswat, S. (2017, May). SCRUM model for agile methodology. In 2017 International Conference on Computing, Communication and Automation (ICCCA) (pp. 864-869). IEEE. DOI: 10.1109/CCAA.2017.8229928
Vohra, V. (2017). Risk Management in System Development Life Cycle (SDLC). International Journal, 5(3). Available online at: www.ijarcsms.com
Remember, at the center of any academic work, lies clarity and evidence. Should you need further assistance, do look up to our Computer Science Assignment Help
Proofreading and Editing$9.00Per Page
Consultation with Expert$35.00Per Hour
Live Session 1-on-1$40.00Per 30 min.
Doing your Assignment with our resources is simple, take Expert assistance to ensure HD Grades. Here you Go....