Saturday, March 8, 2014

Non-Functional Requirements Analysis

Requirements structure – (From BABOK® Guide v2.0)

  • Business Requirements
  • Stakeholder Requirements
  • Solution Requirements
    • Functional Requirements
    • Non-functional Requirements ***
  • Transition Requirements

What Are Non-Functional Requirements?

Capture conditions that do not directly relate to the behavior or functionality of the solution Instead, they describe environmental conditions under which the solution must remain effective or qualities that the systems must have Quality or supplementary requirements

Can include requirements related to:

  • Capacity
  • Speed (Response time, Throughput)
  • Security
  • Availability
  • Scalability
  • … and more

What Is Requirements Analysis?

Describes how business analysts prioritize and progressively elaborate stakeholder and solution requirements in order to enable the project team to implement a solution that will meet the needs of the sponsoring organization and stakeholders

  • Includes non-functional requirements

Involves analyzing stakeholder needs to define solutions that meet those needs, assessing the current state of the business to identify and recommend improvements, and the verification and validation of the resulting requirements

  • Includes non-functional requirements

What Is Non-functional Requirements Analysis?

BABOK® Guide v2.0, section 9.17

The purpose of non-functional requirements is to describe the required qualities of a system, such as its usability and performance characteristics. These supplement the documentation of functional requirements, which describe the behavior of the system.

Categories (ISO 9126)

  • Reliability
  • Performance Efficiency
  • Operability
  • Security
  • Compatibility
  • Maintainability
  • Transferability


  • Include one or more measures of success
  • How do we know we met the requirement
  • Requires to adequately test requirement


  • The system shall …


Importance – Why Bother?

Essentially describe the target quality of the system, so …

Missing non-functional requirements (missing quality) impacts every functional requirement

  • Could affect adoption
  • Could be compliance issues
  • Careful! Too much could impact time and cost

Often require technical expertise

  • Could be done by System Analysts

Source: IIBA Vendor Showcase Webinar Series

Monday, January 14, 2013

10 Best Practices for BPM Implementation

Today i had the chance to read an article by Talend that summarizes simple yet efficient strategies to a successful BPM implementations that i think its worth to share, and here is my review:

Business Process Management implementation has many immediate and long-term benefits, a poor start can jeopardize the overall success of the mission. The following steps and guidelines will help ensure the success of your organization's BPM implementation while minimizing the possibility of any potential setbacks.

  1. Model How You Actually Work: When deploying BPM in your organization you must establish a starting point or what is known as AS-IS process/diagram of how people are currently working. moreover in order to determine which process to improve it is important to observe the realities of their environment.
  2. Think Big, Start Small:
    • It is best to start with a smaller, more easily manageable project that will produce measurable results while keeping the larger focus in mind.
    • The first implementation should be one in which real improvement actually makes a difference to the organization.
    • No one will be impressed if the first application of BPM results in "improvements" like better handling of useless or truly unimportant tasks.
  3. Involve All Project Stakeholders: Who Should own the BPM Project? who are your major stakeholders?
    • It is important that any BPM deployment integrates seamlessly into your organization's existing IT infrastructure, therefore IT gurus in your organization are one of the stakeholder roles.
    • Business Users or Functional owners are the people who actually know how the process works.
    • Lastly the end users who will eventually use the deployed application.
  4. Choose the Tool Based on Needs
  5. Choose a Champion to Lead the Way
  6. Establish Milestones
  7. Provide Deliverables Promptly
  8. Encourage Collaboration
  9. Measure Results Step-by-step
  10. Use Professional Services When Necessary

For further reading you can download the article from

Monday, May 28, 2012

Introduction to BPM

This is a short interesting video for those who want to know What is BPM - Business Process Management?

Enjoy this Introductory video about BPM

Tuesday, May 15, 2012

Quote i liked today

“We can chart our future clearly and wisely only when we know the path which has led to the present.” – Adlai E. Stevenson

Thursday, June 17, 2010

New Zealand 7s 2010 day two - video

for those who are looking for good quality rugby videos enjoy this one

i am looking for Day one when i get it i’ll post it here

Monday, May 31, 2010

Our Office Goldfish Aquarium

These are the resent photos of our aquarium, we got it for 2 months now… the fish are healthy and its very relaxing to have an aquarium in the office.

IMG_2911 IMG_2912 IMG_2913 IMG_2914 IMG_2915