Software Consulting
Requirement Definition Services

The success of project implementation strongly depends on how precisely the target software requirements are defined.

Requirement definition is particularly important for large projects; especially where project completion within an allocated timeframe and budget is critical.

Stay within your project timeframe and budget

MIC consultants have extensive experience in providing our customers with professional project requirement-definition services.

We address all aspects of the customer's future solution when offering our help in developing solution requirement specifications. This includes, but not limited to, the customer's IT environment, requirements for future software upgrades, performance and scalability, hardware compatibility if required, and usability for end users. In the end, the customer receives a thorough project documentation package, eliminating typical offshore development risks.
 

Project documentation covers:

• complete project requirement specifications

• timeframe/ budget/ deliverables by phase

• risk description and risk mitigation strategies.

The Project documentation package ensures the customer receives the exact required functionality - no more, no less. The customer doesn't pay for developing redundant features, yet has the guarantee that all required functionality is covered.
 

Project documentation gives the customer full control over the project duration and budget:

• Clear project scope

• Effective control over project flow

• Complete project flow transparency

• Predictable deliverables at each project phase

• Control over project budget - day by day, phase by phase

• Project risk reduction

Project documentation ensures a customer has full control over the project timeframe, so a project will be delivered strictly on time and within the allocated budget.

How it works

MIC experts have proven experience in specifying project requirements off-site. Once a customer approaches us with the need to define project requirements, we assign a dedicated expert, or group of experts, to work on the customer's project.

In many cases, MIC consultants start working with only a general project idea, and finish by converting it to a complete package of project specifications: system scope, major functionality, nonfunctional requirements, and even software architecture.

One customer says: "MIC has the ability to turn an idea into reality in a very painless way; their comprehension of my idea and ability to put these into a workable project has saved many hundreds of hours in the development of our projects." (Neil Lasher, Trainer 1 Ltd.).

At MIC, requirement collection and definition and communication processes are polished and streamlined. All MIC analysts, architects, and project managers speak English fluently. MIC affords the customer a "local" understanding of project requirements at "offshore" prices. If required, MIC analysts and architects can visit a customer and gather project requirements on-site.

MIC engineers take a proactive role in working with our customers' business requirements. We offer multiple development scenarios. Our final goal is to work out a development scenario that brings the customer the highest value in terms of functionality gained and budget spent.

Below is a sample dialog between a customer and an MIC engineer, analyzing security requirements as one of the multiple aspects of the customer's software project.

SAMPLE DIALOG

Customer: I want MIC engineers to build security protection for my software system.

MIC: To define which kind of security protection best fits your company, we need to know if different users will have different access to the system functionality and data.

Customer: Yes. We have account managers, executives, and financial clerks, who all need to access different system modules (sales, finance, reports, etc). Executives should also be able to act as account managers. At the same time, account managers should only have access to their own client accounts.

MIC: Do you require access to your system from the Internet, or will it be operated within the corporate office only?

Customer: The system is intended for internal use only. No access from the Internet will be required.

MIC: In that case, the entire system will be deployed behind the firewall. We don't need to build extra protection.

We would like to offer plain password protection without data encryption of communication between client and server. We can also offer you other user authentication methods, such as biometric sensors or card-based access, but login/password implementation will cover your business needs sufficiently. This option will cost you less.

This is a simple and effective solution, yet it has one drawback. Somebody within your company could sniff out your network traffic and steal passwords. Would you like to have protection against this?

Customer: Yes, our company requires this kind of protection.

MIC: Very well, then all communication will be done using SSL protocol.

To summarize: in your case, we recommend using access control lists for data combined with role-based access to functionality. When logged in, your system users will be provided with a user interface customized according to their specific user roles. At the same time, a particular account manager will be able to work with his/her account database only. All network communication will be SSL encrypted.

If you need to define software requirements for your project, contact MIC. We do right the first time - professionally and within your timeframe and budget.

 Company - Products & Services - Technologies - Quality - Clientele - Contact Us - Feedback - Home

Site Map - Disclaimer, Privacy Policy