Gives you an opportunity to consider preventative measures to include security checks during the requirements gathering phase of a software project.

Instructions: First, consider the following statements:

Only fools rush in

$.$

Measure twice, cut once.

Look before you leap.

What do all these sayings have in common? They

$$

re all about thinking before acting. In the world of software development, this tenet applies to both software requirements gathering, and more recently, to including security considerations from the very beginning of the project. This week, you've learned about misuse cases. A misuse case allows you to put yourself in the shoes of an attacker and consider ways to break

$/$

infiltrate the software system based on the current system design. This is one of the ways that analysts are now using to try to include preventative measures in software development projects.

Secondly, take some time to thoughtfully reflect on this week's assigned reading and then construct a

$3$

$-$

$5$

$$paragraph response answering the following questions

$($

be sure to reference your sources

$-$

$$textbook$,$ other

$-$

$$to support your statements and opinions

$)$

:

$($

$1$

$)$

$$What are

$1$

$-$

$2$

$$advantages of using misuse cases as part of the development process? Give examples

$($

real or fictional

$)$

$$to support your ideas.

$($

$2$

$)$

$$Can you think of another way

$($

other than misuse cases

$)$

$$to include security considerations in the software development process?