Assignment Task

Questions

1. A healthcare provider was looking to develop a new electronic records management system that would enable them to more efficiently manage patient records and improve the quality of care. The provider`s IT team had experience using the Waterfall software development life cycle model in the past, and so they decided to use this model for the new project.

The project began with a requirements gathering phase, followed by a design phase where the team created detailed specifications and mockups of the system. This was followed by a coding phase where the team implemented the system according to the specifications, and then a testing phase to ensure that the system met all of the requirements.

As the project progressed, the team began to encounter several challenges. First, they found that the requirements they had gathered at the beginning of the project were incomplete and that they needed to go back and gather more information from the end-users. Second, the design phase took longer than anticipated, and as a result, the coding phase was delayed. Finally, when the system was tested, several issues were discovered that required significant rework to fix.

In the end, the healthcare provider was disappointed with the final outcome of the project. The system did not meet all of the requirements, and it was delivered much later than originally anticipated. Upon reflection, the IT team realized that the Waterfall model was not the best choice for this project. They had assumed that the requirements would be stable and that they could complete each phase of the project before moving on to the next. However, in reality, the requirements were subject to change, and this had a significant impact on the project timeline.

a) What could have led to the healthcare provider`s decision to develop a new electronic records management system?

b) Justify the provider’s IT team’s choice of the waterfall model for this project. As part of your justification, elaborate this model.

c) What steps were involved in the requirements gathering phase of the project, and how were the requirements determined?

c) What steps were involved in the requirements gathering phase of the project, and how were the requirements determined?

d) What challenges did the team face during the coding phase, and how did they overcome them?

e) How was the testing phase conducted, and what criteria were used to determine if the system met all the requirements?

f) Did the new electronic records management system meet the healthcare provider`s expectations and improve the quality of care?

2. You are working on an office automation project in the printing industry. The system to be developed is meant to support the work of journal editors. The management objective for this project is to save labour costs; the editors’ objective is to improve the quality of their work

In the development of this project you may opt for two strategies. The first strategy is to start a thorough analysis of the user requirements, after which the system is built according to these requirements. The second strategy starts with less complete requirement analysis phase, after which a pilot version is developed. This pilot version is installed in a few departments. Further development of the system is guided by the gained experience in working with the pilot version.

• What would you do if you were the manager? Discuss possible ramifications of these opposing objectives on the project.
• Critically outline the pros and cons of both strategies described above. Which strategy do you favour?

3. A leading bank is looking to develop a mobile banking application that allows users to access their accounts, view their transaction history, and transfer funds. The bank wants the application to be available on both iOS and Android platforms, and to be easily extensible to support new features and functionality in the future

The bank`s development team need to ensure that the application is designed to maximize code reuse and portability, so that it can be deployed on both iOS and Android platforms with minimal platform-specific customization. They also need to ensure that the application can be easily extended in the future to support new features and functionality.

a) What were the challenges faced by the development team in developing the mobile banking application?

b) What best practices did the development team adopt to ensure maximum code reuse and portability across different platforms and environments?

c) Why is modular design important in maximizing code reuse and portability?

d) How did the development team take into account the unique requirements and constraints of each target platform in the design and implementation of the mobile banking application?

e) How did the adoption of best practices by the development team lead to a positive user experience for the mobile banking application?

f) How might the bank extend the mobile banking application in the future using the modular design and abstraction principles adopted by the development team?