Skip to content

Requirements for Software Archi­tects – Part 3

This blog article discusses the key requirements for software archi­tects, highlighting the impor­tance of agile methods, stake­holder engagement, and advanced techniques like BDD. It empha­sizes collab­o­ration between archi­tects, analysts, and product owners to achieve successful project outcomes.

Read More

Requirements for Software Archi­tects – Part 2

iSAQB-blog-Requirements-Part2-WEB

This blog article outlines key requirements for software archi­tects, highlighting the need for agile requirements engineering, addressing functional and non-functional requirements, managing complexity, and ensuring effective commu­ni­cation and imple­men­tation of architecture.

Read More

Maintaining an Overview

iSAQB-blog-Maintaining_an_Overview-WEB-v2

The article “Maintaining an Overview” by Dr. Peter Hruschka and Dr. Gernot Starke empha­sizes the impor­tance of having a struc­tured overview in software projects to effec­tively manage detailed requirements, suggesting a method to prior­itize archi­tec­turally signif­icant requirements early on.

Read More

Act, Don’t Whine:

In many consulting projects over the last few years, we have seen devel­opment teams complain about two things: that they suffer from a lack of good requirements or that they have not received important requirements or have received them much too late. They then blame requirements engineers, business analysts, or product owners who “didn’t do…

Read More

Stay Up-to-Date with the iSAQB® Newsletter!

Scroll To Top