Interview Questions for Business Analysts and Systems Analysts

Recent Interview Questions | Search | Subscribe (RSS)


If you were to group software requirements into levels, how might you group them?

Posted by MostafaElbarbary

Article Rating // 27474 Views // 1 Additional Answers & Comments

Categories: Business Analysis, Requirements Analysis (BABOK KA)


The Business Analysis Body of Knowledge® (BABOK®) defines the following levels of requirements:

  • “Business Requirements are higher-level statements of the goals, objectives, or needs of the enterprise.  They describe things such as the reasons why a project is initiated, the things that the project will achieve, and the metrics which will be used to measure success.
  • Stakeholder Requirements are statements of the needs of a particular stakeholder or class of stakeholders.  They describe the needs that a given stakeholder has and how the stakeholder will interact with the solution. Stakeholder Requirements serve as a bridge between Business Requirements and the various classes of Solution Requirements.
  • Solution Requirements define the characteristics of a solution that meets the Business Requirements and Stakeholder Requirements. They are frequently divided, particularly when the requirements describe a software solution, into:
    • Functional Requirements describe the behavior and information that the solution will manage. They describe capabilities the system will be able to perform in terms of behaviors or operations – a specific system action or response.
    • Non-Functional Requirements capture conditions that do not directly relate to the behavior of functionality of the solution, but rather describe environmental conditions under which the solution must remain effective or qualities that the system must have.  They are also known as quality or supplementary requirements. 
  • Implementation Requirementsdescribe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desire future state, but that will not be needed once the transition is complete” (Business Analysis Body of Knowledge® 2008).
BABOK and Business Analysis Body of Knowledge are registered trademarks owned by the International Institute of Business Analysis.
According to Ian Sommerville (1997) the software requirements types are:
  • User requirements: are written for customer in natural language and simplified diagrams which describe system features and services.
  • System requirements: are written as a contract between client and the contractor, and it is a structured document setting out detailed descriptions of the system services.
  • Software specification: A detailed software description which can serve as a basis for a design or implementation and are written for developers.
According to Karl E. Wiegers (2003) the software requirements levels or types are:
  • Business requirements: are written to represent the high level objectives and goal of the organization or stakeholders who want to build the system.
  • User requirements: describe the user goal which the user desires from the new system.
  • Functional requirements: specify the software functionality that the developers must build into the product to enable users to accomplish their tasks.
According to Suzanne Robertson and James Robertson (2006) the software requirements level or types are:
  • High-level requirements: are written to specify the business the product is intended to support
  • Business requirements: are written in a technologically neutral manner they specify what the product is to do for the work, not which technology is used to do it.
  • Product's technological requirements: are written by designer who adds those requirements needed to make the product work in its technological environment.
According to the Rational Unified Process the software requirements level or types are:
  • Stakeholder requests: are written in User language to capture all user requests.
  • Features: are written to capture all feature of the system under development.
  • Use cases: are written to capture functional requirements.
  • Supplementary requirements: are written to capture Non-functional requirements (Leffingwell 1999).


Business Analysis Body of Knowledge (version 2.0). 2008. International Institute of Business Analysis. pp 8-9.

Leffingwell, Dean & Don Widrig. 1999. Managing Software Requirements (First Edition). Addison Wesley.

Robertson, James and Suzanne Robertson. 2006. Mastering the Requirements Process (Second Edition). Addison-Wesley Professional.

Sawyer, Pete and Ian Sommerville. 1997. Requirements Engineering: A Good Practice Guide (First Edition). Wiley.

Wiegers, Karl. 2003. Software Requirements (Second Edition). Microsoft Press



srikanth posted on Friday, May 16, 2008 11:32 AM
Software requirement specifications contains

Use case ( functional requirements)
Non-functional reqirements (Includes performane engineering requirements, qualty standards and design standards).

Software Requirements Specification otline:

Software Requirements Specifications (SRS)
Cover Page
Revisions Page
Table of Contents
1.1 Product Overview
2.1 External Interface Requirements
2.1.1 User Interfaces
2.1.2 Hardware Interfaces
2.1.3 Software Interfaces
2.1.4 Communications Protocols
2.2 Software Product Features
2.3 Software System Attributes
2.3.1 Reliability
2.3.2 Availability
2.3.3 Security
2.3.4 Maintainability
2.3.5 Portability
2.3.6 Performance
2.4 Database Requirements

Only registered users may post comments.

Do your homework prior to the business analysis interview!

Having an idea of the type of questions you might be asked during a business analyst interview will not only give you confidence but it will also help you to formulate your thoughts and to be better prepared to answer the interview questions you might get during the interview for a business analyst position.  Of course, just memorizing a list of business analyst interview questions will not make you a great business analyst but it might just help you get that next job.



Select ModernAnalyst Content

Register | Login

Copyright 2006-2024 by Modern Analyst Media LLC