We Follow a Multi-Phased
Approach Phase 0: Strategy (Optional)
In many cases, our clients desire our assistance in determining
the most effective use of technology within a specific business initiative, product,
online service or topline process before moving forward with development projects.
Our Strategic Technology Consulting practice provides this service. Phase I: Planning for
Success - Research, Analysis, Proposal
During this early
stage, we learn as much as possible about your business and the project requirements.
We then scope the project and prepare a proposal. The proposal addresses your
target market or deployment environment, and any project schedule constraints
or technical issues. This phase positions us to suggest a solution and describe
our working relationship. Our Project Manager’s first
responsibility is to work with our sales force during the bidding process to create
an accurate and complete statement of work. The bidding team anticipates
any necessary resources and their estimated optimal assignment times and duration
on the project. This results in a smooth project kickoff and a head start on engagement
success. The next step is a proposed
project plan including task dependencies. Our Onsite Project Managers will
often work with you during this step to perform business analysis or infrastructure
planning for technology deployment. Next are the completion of project
requirements and the creation of specifications. Depending on your
needs, our Project Manger works here with some combination of your staff, our
senior engineers, or our Strategic Technology Consultants. Our standard engineering process
begins with a Marketing Requirements Document(MRD). This document can be
supplied by our clients or produced by Saral based on client input. The MRD is
end-user oriented for interactive systems, stating the overall expected user
experience within the target environments. For non-interactive systems, the
MRD focuses on the constraints of the external hardware or software environment. The MRD is input for our Functional
Specification (FS). The FS is a top-level description of the internal primary
system components, their functionality, interfaces, data structures, and access.
The FS often includes discussion of global issues such as:
- Time
synchronization and identity
- Security,
stability, and scalability
- Fault
tolerance, bandwidth, and latency
- Transactions,
queuing, and data management
The FS is input for the Component
Design Specifications (CDS). The number and complexity of CDS documents are
a directly related to the size and complexity of the system. CDS documents themselves
can be simple guidelines for interface or internals programming, or they
can be detailed object-oriented specifications conforming to the Uniform
Modeling Language and referencing standard design patterns. The CDS often discusses
issues such as: - Memory
usage, instantiation/initialization, and persistence
- Concurrency
(multi-processing and multi-threading)
- Asynchronous
input/output and resource pooling
- Our
process can also cover specialized areas such as Database Architecture and Risk
Analysis.
The final step in the planning
phase is a review of the statement of work and the proposed project plan relative
to a now more complete understanding of the project scope and available base technologies. Phase II: Efficient Project
Execution
As design, engineering, quality, and documentation professionals
are brought on and off the project, our Project Managers orchestrate the efficient
allocation and interaction of resources. During this phase, our Project Managers
pay very close attention to the correlation of resource usage and quality
work-product creation. We divide each project into
a number of sub-projects depending upon their functionality or use-case. These
sub-projects are then developed concurrently using state-of-the-art Rapid Application
Development (RAD) tools and follow an iterative development cycle going through
analysis, design, coding and testing. The sub-projects are then integrated together
and system level development and testing are then performed to see the project
through to completion. The Project Manager is responsible
for accurate and fair billing, whether on an hourly or milestone basis.
Our senior engineering staff performs periodic reviews of work product
to identify any potential problem areas. This avoids costly late corrections and
rework. During implementation, we continue
to work closely with you to build your solution. Throughout the implementation
phase, we will keep you apprised of project status, issues, and decisions. We
stay focused on meeting your requirements. We have a proven track record of working
together to complete projects successfully for our clients. After the GUI design stage ,
SARAL provides fully interactive proto-types that can be demonstrated to your
potential customers or investors , before getting down to code implementation. Phase III: Project Completion
Often we enter the project completion phase helping you manage
"alpha" and "beta" programs, including trial customer feedback.
After final work product corrections are made, we perform a complete project
handoff, making sure that you are in a solid position for successful launch.
Project handoff can include training of your technical or support staff. At project completion, SARAL
continues to be a resource to our clients. Depending on your needs we can provide
technology transfer, training, periodic maintenance, or plans for next stage development.
We value our clients, and strive to establish long-term working relationships.
Our project managers are committed
to their key role in building a partnership you'll view as a strong contributor
to your competitive advantage. Technology Transfer We give you the knowledge necessary
to control and manage the product after completion. By developing a comprehensive
understanding of your problem from the beginning, we can better understand
your requirements at hand-off time. Depending on your needs, we can provide
you with training, ongoing maintenance, and a cont. | 
SERVICES