Secure Software Development

5 Responses to Requirements Gathering

1. How To Remove Friction From Your Version Control Experience « Secure Software Development says:

   2013-02-18 at 13:02

   [...] done with your current work item (user story or whatever you want to call it) when it’s coded, all the tests pass, and the code is [...]

   Reply
2. Software Development and Lifelong Learning « Secure Software Development says:

   2012-09-10 at 13:02

   [...] has many distractions, though, like Getting a Story [...]

   Reply
3. Abuse Cases « Secure Software Development says:

   2012-08-13 at 13:06

   [...] case models are best created when use cases are: during requirements gathering. It’s easiest to define the abuse cases after the regular use cases are identified (or even [...]

   Reply
4. Visualizing Code Coverage in Eclipse with EclEmma « Secure Software Development says:

   2012-07-09 at 13:20

   [...] it takes time to write code, writing less code means you’ll be more productive (finish more stories per [...]

   Reply
5. Behavior-Driven Development (BDD) with JBehave, Gradle, and Jenkins « Secure Software Development says:

   2012-07-02 at 13:08

   [...] are great for developers, since they provide quick and unequivocal feedback about whether the story is done. Not only the main success scenario, but also alternate and exception scenarios can be [...]

   Reply

Please Join the Discussion Cancel reply

Enter your comment here...

Fill in your details below or click an icon to log in:

Email (required) (Address never made public)

Name (required)

Website

You are commenting using your WordPress.com account. ( Log Out / Change )

You are commenting using your Twitter account. ( Log Out / Change )

You are commenting using your Facebook account. ( Log Out / Change )

Cancel

Connecting to %s

Notify me of follow-up comments via email.

Notify me of new posts via email.