Also read the Boehm article on the spiral model, what makes this a better model?

Initial posting worth a max of 3 points, replies worth a max of 2 points

Reply to Post 1:

Humza Ansari:

One topic I found interesting in this weeks lecture was about information security. I knew that it was important to protect data from hackers, but I didn’t consider things such as natural disasters and human error. There are many things IS security can do to protect data but there is nothing that fully prtects it. Hackers will often find a way to steal data, people will always make mistakes, and people can’t control natural disasters. It think their role is very important and very difficult to maintain.

Reading the Boehm article I found a lot of familiar topics that coincide with SDLC. I was familiar with waterfall model but never heard of the spiral model until now. Some benefits of the model I found were that it is able to solve all sorts of problems and help existing software models. One advantage I found really useful was being able to reuse existing software for options in your system.

Reply to Post 2:

Yuktaben Shah:

There were a lot of interesting topics in chapter 12, but I mainly enjoyed reading about the Systems Development Life Cycle (SDLC), its activities, and the Development Process. The chapter explains each phase of SDLC in detail and how different IS professionals play a key role in the development process. Systems development is about developing and continuously supporting an information system. The SDLC comprises five activities, define the system, determine requirements, create components, implement, and maintain the system. Each of these activities is important in developing and ultimately implementing an information system. These activities are put together before a project development team is built, and other resources are invested. A development project team consists of business analysts, developers, IT analysts, a manager, etc. I believe SDLC plays an essential role in the systems development process of an information system. It’s interesting how analysts and developers support an information system.

After reading the Boehm article, I realized that some of its topics were similar to chapter 12. Before reading the article, I wasn’t familiar with the spiral model, but I learned about the spiral model in-dept through the article. The spiral model is a method of SDLC used for risk management, and it’s similar to the Waterfall model. When the spiral model is implemented into a system, the spiral model improves the systems’ overall productivity. The main advantages of the spiral model include flexibility, unlimited changes, risk management, beneficial for large projects, allows us to track progress, etc. The spiral model is used for difficult and costly projects by engineers and developers. Overall, the article was very helpful in learning about the spiral model.