Showing posts from September, 2022

Non Functional Requirements Component Type Applicability

Non Functional Requirements (NFR) define the constraints or the way Functional Requirements are implemented. NFRs are categorized as different types of constraints.  Those categories are great for the enterprise but don't really help determine which NFRs apply in any given Business Feature. One way to remedy this is to create a second type of categorization that identifies which NFRs apply for a given component type, The individual NFRs in a category may only apply to certain deployable types. Related Video: Blog (Related): Classic NFR Categorization NFRs are generally grouped with related constraints.  You can find a variety of categorization taxonomies with a quick internet search.  From Wikipedia: Non-functional requirements are often mistakenly called the "quality attributes" of a system. There

Remote work network complexity - VPNs, proxies, split tunnels.

The incredible increase in remote work, continually escalating security concerns, the shift to SaaS providers for office productivity, and exploding bandwidth demands have changed the way companies manage connectivity.  Companies are moving from  always-on network VPNs to a mix of cloud proxies and zero-trust models. Home users connect to all services via public internet connections. Corporations typically block this type of access via IP or geo-location blocking that limit access from corporate networks or remote sites.  Corporations extended internal hardware and security models by providing remote sites and remote users with corporate-owned machines that join the corporate network via VPN. The VPN bridge the local network to the corporate network. They appear inside the company similar to the way they do inside corporate facilities.  This provides all the benefits and risks associated with being inside the network. Remote machine and site breaches give the attacker broad access to

Scaled Agile - Functional Requirements, Features, Non Functional Requirements, Enablers

Value streams are composed of and managed as a set of  Business Features that  represent some unit of business value. Business  Features are defined in terms of Functional and Non-Functional requirements. Product   Owners define the  business requirements and acceptance criteria for a business feature .  Architecture and technical owners associate Non-Functional Requirements with the same Business Features. Functional Requirements and Acceptance Criteria  describe Features Product Owner's point of view.  Non Functional Requirements are a second requirement stream that defines the structure needed to support the Functional Requirements and thus the business system. As an example, the house building equivalent of FRs and NFRs could be the following: Functional Requirements would be the number of bedrooms, number of bathrooms, cabinet types, and the type and color of the flooring. Non Funct