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

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

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...
Post a Comment
Read more

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more