A. Requirements Gathering

We work very hard to understand the current business process followed by an organization, before proposing a solution to eliminate old manual activities and enhance the business further.

Our requirements gathering process involves:
1. Document Analysis: We analyze the documents received from our clients to understand their needs.
2. Interviews: Interviewing current employees, managers and users of the existing business system to understand more of the business process and needs.
3. Brainstorming: We brainstorm to refine the collected information, reach the best, most optimized solution.
4. Requirements Workshops: Requirements workshops are a powerful technique that we use for eliciting requirements further, if needed and approved by the client.
5.Prototyping: Prototyping is a technique we follow to build a quick and rough version of the desired system, to illustrate the capabilities of the system.

B. Analysis

In this step we start by analyzing the requirement document created previously by our teams, which is known as the BRR (Business Requirements Review) phase. Based on this review we produce a software requirements specification (SRS) document, aligning hardware and software requirements. The SRS covers the preparation necessary for the successful completion of the project, while setting an indication of the estimated time and cost of the entire project.

After an extensive feasibility study, by setting SMART objectives (Specific, Measurable, Accurate, Realistic and Time defined objectives), we produce 2 important documents at this phase:

1. User Requirements Document: This defines the features the system is expected to provide and the constraints under which it must operate for the users of the system.
2. System Requirements Document: This sets out the functional specification including system services and constraints, with more technical details, including the most suitable and convenient platform, network, system performance, and data communication requirements.