OVU will deliver a complete cloud solution based on customer requirement. Our managed software development, independent software testing and professional services span across commercial software products, SaaS solutions and custom applications in enterprise, cloud, mobile and web development.

  • Domain Ontology: Business analyst will describe naming and definition of the types, properties, and interrelationships of the entities that fundamentally exist for a particular domain. This will simplify understanding of particular domain.

  • Requirements Scope: The scope and boundary of the proposed software solution is drawn based on business requirements and goals.

  • Stakeholder Identification: Identifying stakeholders such as customers, end-users, system administrators etc. is the next step in requirements analysis. This is one of the most important steps in the whole process as proper identification of stakeholders enables the business analyst to draw a road map for gathering requirements.

  • Requirements Gathering: Post identification of stakeholders, the tedious process of eliciting requirements follows. Based on the scope and nature of a particular software solution there can be multiple stakeholders. Interaction happens with stakeholder groups using various communication methodologies including in-person interviews, focus groups, market study, surveys and secondary research.

  • Typical Scenarios: Business analyst will figure out typical scenarios that must be considered while developing the product.

  • Atypical Scenarios: There may be some atypical scenarios that must be figured out before starting the development of the product. We will try to find these scenarios which may be related to the specific domain.

  • Feasibility Study: Our business analyst will do the feasibility study to make the product viable. Feasibility can be judged from two most important criteria i.e. cost and value. Feasibility studies, aim to objectively and rationally uncover the strengths and weaknesses of the proposed product, opportunities and threats present in the environment, the resources required to carry through, and ultimately the prospects for success.

  • Risk analysis is a process that involves “gathering data and synthesizing information to develop an understanding of the risk involved in development of the proposed product”.

  • Requirement Analysis: Once user data is gathered, structured analysis is carried out on this data to determine models. Usually use-cases are developed to analyze the data on various parameters depending on the larger goals of the software solution. We use requirements animation, automated reasoning, knowledge-based critiquing, consistency checking, analogical and case-based reasoning.

  • Software Requirement Specification (SRS): Once the captured data is analyzed these are put together in the form of a software requirement specification document (SRS) or a system requirement specification (SYRS) document. This document serves as a blueprint for the design or development teams to start building the solution on. It serves as a technical compendium of all the stakeholders’ needs including user requirements, system requirements, user interface and operational requirements.

  • Software Requirements Management and Validation: The final step of the requirements analysis process involves validating all elements of the requirements specifications document. Errors are corrected here and it can also accommodate minor changes to requirements of the proposed software solution.