Question

The question of this part analyzes the students’ understanding in analyzing the given scenario and use brainstorming to apply and reflect concepts studied in chapters 4, 5, 6, 7, 19 and 22 of IT242.

All software process models can accommodate the generic framework activities (communication, planning, modeling, construction, and deployment), but each applies a different emphasis to these activities and defines a process flow that invokes each framework activity in a different manner.

Answer:

1. Suppose you have been assigned, as a group, the tasks of project manager and software engineers to build the “EasyTravel” from scratch or maintain an existing old system that satisfies the majority of the needed functionality but breaks too often and has several defects. Which path do you choose, building from scratch or maintaining the existing old system? Explain your answer. (4 Marks)

2. If the customer needs to be fully satisfied with the website interface, what is the process model do you recommend for developing the scenario? Explain your answer. (4 Marks)

Answer 1

I would rather go for a new one where developing the new application will be better rather than fixing it several times as it hampers the business continuity. You need to make your application a stable one rather than fixing your application now and then to ensure business continuity. I know building and developing the new application will not only cost much but also new resources to build. But that is something which every business should emphasize of having a stable application. Even the older application is using old technologies which might become incompatible in several ways. So,it is better to go with the new application.

if the customer need to be fully satisfied with the website interface, it is better to go with the Agile methodology as the Software Development Life Cycle model. This actually helps the entire project to build the new application with ease. Even agile model will help in developing the project over the time and then deploying the project into the production environment after rigorous testing is done. This methodology ensures that every user stories or functionality should be implemented into the project.