Frequently Asked Questions

What is your big advantage?

We have a complete software engineering process and online repository, fully traceable to CMMI Level 2 and most of Level 3. Projects using the Shell Method have passed multiple audits and assessments.

Do you work on-site? Will you need an office space at our facility?

We do periodic meetings on-site, but the bulk of our work is accomplished over the Web. We won't need office space at your facility.

Will you need access to our intranet?

Sometimes. It depends on the project. For legacy application documentation efforts, sometimes the only way to exercise the application or gain access to the development repository is through direct login behind the firewall. In those cases, we'd need access. For new design efforts, our normal infrastructure works, so we generally don't need intranet access unless your security folks are concerned about application design information being hosted outside your intranet.

How fast can you execute a project?

Generally, the speed of execution is determined by the speed of client response, particularly in reviewing and approving project artifacts. For example, one client had a QA review staff that averaged 12 business days to perform each review. Based on the number of modules in the system and the number of artifacts per module, we calculated the project would incur an additional 15 months of delay as compared to a normal review cycle of two days. The client's management fixed that problem fairly quickly.

Does your documentation conform to standards?

Different clients have different standards. Sometimes they're self-imposed, sometimes they're imposed by their regulatory environment, but standards simply don't exist as far as many clients are concerned. Where client standards are in place, we train your personnel to produce documentation to conform. Most of the time that's not the case, so we use our Shell Method structure, which traces to CMMI and IEEE standards and practices.

Do you support agile development methodologies?

Yes. Our Shell Method software engineering process specifies tight, rapid lifecycle iterations, which is one of the hallmarks of agile work. Some developers advocate abandoning documentation, but that's not really what agile methodologies are all about. All modern methodologies, from Agile to Waterfall, specify that someone has to sit down and write real documentation, especially if the system has to pass audit. For lighter weight implementations where the focus is on rapidly specifying a system, but without the need to satisfy auditors, we can provide training and mentoring in Agile Specifications.

Do you support high rigor lifecycles such as specified by NQA-1?

Yes. The Shell Method software engineering process fulfills all the requirements of high-rigor lifecycles, with full process definitions, stage deliverable requirements, and online deliverable reviews with digital signatures. All artifacts are traceable to specific requirements defined by the regulator, and full requirements traceability is integrated into the process. The process is fully documented and proceduralized, and has passed multiple audits at this level.