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

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

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Bucket System project estimation

 The Bucket System is an Agile estimation technique that uses predefined buckets to group tasks or user stories by size, complexity, or effort.  Each bucket represents an estimate range, such as small, medium, or large.  The Bucket System is a group activity that helps align the team's understanding of work effort and complexity.  It's a good technique for quickly estimating a large number of items with a medium to large group of people. The effort of small, medium, or large bucket size arrived by team based on T-shirt sizing, PERT estimation or Planning Poker. Each bucket represents a level or an estimate range (e.g., small, medium, large). The team compares user stories to one another and places them into the appropriate buckets. This process is a group activity, promoting discussions and aligning the team's understanding of work complexity and effort. To use the Bucket System: Set up a row of cards, or buckets, with values in the Fibonacci sequence or other metho...
Post a Comment
Read more