PuzzleSystems doesn’t expect you to know exactly what kind of software you need, the manner in which it is to be developed and maintained. You simply need to contact us and express your ideas about the desired solution. PuzzleSystems project managers will analyze your business goals, outline the product and its objectives, and prepare a business proposal. We will also provide our suggestions and thoughts to your solution to help you.
Again: PuzzleSystems will treat you as a friend and will take the time and effort to work with you in order to guarantee your satisfaction.
Every project includes the complete product development life cycle from conception to solution. The process includes:
1. FUNCTIONAL SPECIFICATION
Analysis of the project requirements, product specification design and prototyping, discussion of project efforts, and signing of a business contract, including a Non-Disclosure Agreement (NDA); Our proposal is usually less than or equal to 15 pages.
2. ARCHITECTURAL DESIGN
The need for your system has been determined. Its desirable qualities have been stated in the functional specifications. The design of large systems is considered to be an art. To put some order into the chaos, we've established a few milestones. During the design process we focus on the part of the design essential to producing a core system and merely outline extensions to a more complete system. One of our major goals is to get your system working, even if it isn't the full system yet. Thus we determine what must go into a skeletal system and schedule the design of those components first.
3. DETAILED DESIGN
While the architectural design explains exactly how your system will work in terms of data flow and transformation, its module descriptions are not written so that programmers can write code directly from the design. The detailed design document provides the module definitions and the intermodular interfaces so that each module of the architectural design corresponds to a new set of modules containing the instructions to our developers that describe the input, output and processing to be performed by the module. These instructions are detailed and technical. They reference specific data formats and describe in detail the steps of any algorithms to be used.
4. TESTING
Testing is an important part of any of our software project. No matter how well our team members write programs, experience shows that errors are made. Errors are frequently made in the interfaces of modules written by different team members. Therefore, each module is tested individually and in combination with those it calls and those that call it.
5 DOCUMENTATION AND TECHNICAL SUPPORT
Manual is document that is a self-contained description of how to use the system. Software release and its delivery to the customer. Technical support of a product, release of updated products and new versions.
|
