With many automotive organizations transforming development efforts towards agile methodologies, the need to redefine and establish security, safety, and quality standards and testing methods is more important than ever. How do we fit safety and security planning and tools into the adaptive development and rapid delivery practices of agile teams?
In this second one-hour webinar you'll learn how to:
- Integrate security and compliance testing with agile development
- Provide context for fast triage and remediation
- Create policies for code management in integrated testing environments
In an Agile environment, release cycles may be measured in days rather than weeks, making testing for security and compliance more challenging. Agile requires frequent testing and rapid, continuous feedback. Shipping code to a separate group for testing, and receiving results days later, will break the Agile model. To be successful in an Agile environment, compliance and security testing and feedback must be integrated with the rest of the Agile team.
Note, with Agile, “Release to Market” doesn’t always mean an external release, Potentially shippable increment, or PSI, and minimum viable product (MVP) are two terms used to describe what may or may not be released to customers.
When we examine the process, testing is brought in throughout the development lifecycle, rather than waiting until the development is complete. For this reason, testers are typically part of the Agile teams, and testing user stories are built into the backlog from the outset of the sprint, or iteration.
http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences
An example of unintended behavior introduced via a supplier.
http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences
An example of unintended behavior introduced via a supplier.
http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences
An example of unintended behavior introduced via a supplier.
http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences
An example of unintended behavior introduced via a supplier.
http://www.edn.com/design/automotive/4423428/Toyota-s-killer-firmware--Bad-design-and-its-consequences
An example of unintended behavior introduced via a supplier.