The Profile Includes Assignments for various Esteemed Customers.Successfully Completed Web Development Projects.

Home | Support | Contact us

Client Quotes

I basically wrote the code and the specs and documentation for how the client and server talked to each other.

Case Studies

Successful implementation of the initially difficult but ultimately rewarding changes

Requirement Analysis

"A Description of the resources required for the project and how they will be utilized"

Requirements Analysis in Axis Convergence Pvt.Ltd is the process of understanding the customer needs and expectations from a proposed system or application and is a well-defined stage in the Software Development Life Cycle model. Requirements are a description of how a system should behave or a description of system properties or attributes. It can alternatively be a statement of ‘what’ an application is expected to do.

In Axis Convergence Pvt Ltd. Software Requirements Analysis Process covers the complex task of eliciting and documenting the requirements of all these users, modeling and analyzing these requirements and documenting them as a basis for system design. Software Requirements Analysis are critical to software project success. Requirements Engineering is an emerging field which deals with the systematic handling of requirements.

Conceptually, requirements analysis includes three types of activity:
Eliciting requirements:

The task of communicating with customers and users to determine what their requirements are. This is sometimes also called requirements gathering.

Analyzing requirements:

Determining whether the stated requirements are unclear, incomplete, ambiguous, or contradictory, and then resolving these issues.

Recording requirements:

Requirements might be documented in various forms, such as natural-language documents, use cases, user stories, or process specifications. Requirements analysis can be a long and arduous process during which many delicate psychological skills are involved. New systems change the environment and relationships between people, so it is important to identify all the stakeholders, take into account all their needs and ensure they understand the implications of the new systems. Analysts can employ several techniques to elicit the requirements from the customer.

Types Of Requirements:

Customer Requirements :

Statements of fact and assumptions that define the expectations of the system in terms of mission objectives, environment, constraints, and measures of effectiveness and suitability (MOE/MOS).

Architectural Requirements:

Requirements might be documented in various forms, such as natural-language documents, use cases, user stories, or process specifications.

Structural Requirements:

Structural requirements explain what has to be done by identifying the necessary structure of a system.

Behavioral Requirements:

Behavioral requirements explain what has to be done by identifying the necessary behavior of a system.

Functional Requirements:

Functional requirements explain what has to be done by identifying the necessary task, action or activity that must be accomplished. Functional requirements analysis will be used as the top level functions for functional analysis.

Non-functional Requirements:

Non-functional requirements are requirements that specify criteria that can be used to judge the operation of a system, rather than specific behaviors.

Design Requirements:

The “build to,” “code to,” and “buy to” requirements for products and “how to execute” requirements for processes expressed in technical data packages and technical manuals.

Derived Requirements:

Requirements that are implied or transformed from higher-level requirement.