Aprosoft - Requirement Engineering

Home | Sitemap | Career | Contact Us

Process & Practice » Requirement Engineering

Increasingly, IT industry is realizing the importance of the requirements process as a key element of software development and Software Engineering. Requirements analysis involves (1) defining user requirements, (2) defining product requirements, and (3) performing analysis to define, derive and understand requirements. Aprosoft provide requirements analysis services to support the development of operational system concepts, to define the requirements for systems functionality, and to assess the feasibility of systems deployment.

Primary Requirement Analysis
This is the first stage where we establish primary requirements of customer project and determine its goals and objectives through project specifications. After analyzing technical, operational and financial feasibilities of the project with the stake holders, we provide a project plan and budget estimates for the future stages of development for the software.

Comprehensive Requirement Analysis
Once the project is accepted, we usually have multiple conference calls / meetings / email communications as necessary with customer team to get detailed understanding of IT requirements and its scope. Our team then prepares comprehensive requirement analysis, and with your consent, detailed requirement analysis document is signed to its effect. Subsequently, our skilled software engineers recommend suitable software and operating system choices available in the market depending on your business needs taking your employees’ expertise & software resources into consideration, so as to optimize your IT investment in a resourceful way.

Methodology
Aprosoft utilizes a structured analysis approach combined with the Use Case driven methodology to visualize and document requirements, which includes Use Case models, Use Case description and Activity diagrams. During the high level design phase, based on the artifacts created, we will find and build all components which cover all functions of the project. Next, we move to the application prototype phase.

Traceability
Requirements evolve throughout the systems lifecycle, due to design decisions, subsequent corrective actions, client feedback, and systems implementation outcomes. As a result, new requirements may be derived or existing requirements updated based on the consideration of cost and time constraints, technological limitations, risks, and other factors. Once requirements are developed and subsequently changed, they need to be properly managed. Aprosoft analysts generate and maintain baseline requirements documents as well as a volatility document that reflects all changes to any requirement. We are able to track the history of every requirement, providing end-to-end requirements traceability. We have experienced software engineers familiar with providing traceability for software and systems. We provide traceability analysis of legacy systems which will identify any problems with the documentation.