Skip to main content

Certified Enterprise Architect Professional (CEAP) - Module 10: Design for NFR's

The difference between functional and non functional requirements is depicted below:

functional  - > think scope, how system must work?

non functional -> think quality, how system should perform?

Functional requirements define what a product must do and what its features and functions are. Nonfunctional requirements describe the general properties of a system. They are also known as quality attributes.

NFRs describe system properties or attributes that are not directly tied to specific functions but instead govern how a system performs under certain conditions.

 NFR attributes:

  • performance
  • security
  • scalability
  • error handling
  • useability
  • maintainability
  • availability
  • portability
  • interoperability
  • efficiency
  • compliance
Key responsibilities of architects in managing NFRs:
  1. Define the system's non-functional requirements and documenting NFRs
  2. Analyzing the impact of NFRs
  3. Prioritizing NFRs
  4. Trade-off analysis
  5. Designing for NFRs
  6. Validation and verification
  7. Continuous improvement

How to manage NFRs in enterprise architecture:
  1. Identify and document NFRs
  2. Prioritize NFRs
  3. Integrate NFRs into design
  4. Monitor and measure NFRs

Example:
A non-functional requirement (NFR) in enterprise architecture could be something like "The system must be able to handle 10,000 concurrent users with a response time of under 2 seconds during peak hours," which specifies the performance and scalability needed for the system to function effectively under high load, rather than defining a specific feature or functionality. 

Examples of NFRs in enterprise architecture:
Performance:     Response time, throughput, peak load capacity 
Scalability:     Ability to handle increasing user load or data volume 
Security:     Access control, data encryption, vulnerability management 
Reliability:     System uptime, fault tolerance, disaster recovery 
Maintainability:     Ease of updating, debugging, and modifying the system 
Usability:     User interface intuitiveness, accessibility 
Availability:     System uptime percentage, planned maintenance windows

Labels:

Comments

Post a Comment

Popular posts from this blog

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir...
Post a Comment
Read more

Delivering a project within budget

 Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...
Post a Comment
Read more