Discussion Topics 1

.

Write a page for each discussion topic and provide each with references separately

Discussion Topic 1Q1

Microsoft issued the Windows ME operating system. What was the impact of this ‘rush to market’ software product on users and Microsoft’s reputation? Explain.

Discussion Topic 1Q2

Software is developed using ‘use cases.’ Use cases are in place to describe how the software under development interacts with a user or another software product. Discuss the importance of ‘abuse cases’ in the software development lifecycle.

Discussion 1

.

Respond to this colleagues (BELOW): (Half a page and please, provide a reference )

Discussion Topic

Software is developed using ‘use cases.’ Use cases are in place to describe how the software under development interacts with a user or another software product. Discuss the importance of ‘abuse cases’ in the software development lifecycle.

Post from colleague 2

As software is developed, there are many steps that the developers will go through, to make sure the development of the software is successful. During the lifecycle, in creating the software, there needs to be a step where the developers need to see how the software can be abused. During this step, developers will look at the software and see how it can be attacked. The developers will need to get into the attacker’s shoes and ask themselves, what would they be after, if they were to attack this software. The whole point of this step is to figure out what is the worst that I can done to this software, where it could cripple it, and even cripple the company that made it and uses it.

Implementing the security features in the software comes toward the end of the development of the software. If they miss a security issue, it will be harder to patch it once the software has gone live and was attacked. Therefore, this step in the lifecycle is very important in the development of the software.

Hope, P., McGraw, G., & Antón, A. I. (2004). Misuse and abuse cases: Getting past the positive. IEEE Security & Privacy, 2(3), 90-92