Jence develops software from Requirements Specification. A requirements document is a text document in which the customer writes in detail what the software is all about. NineSTEP also helps write the requirements document. In simple words, we design, develop, test and deliver software based on requirements specification without having you write a single line of code!
Our expertise range from Service Oriented Architecture (SOA), Web Services, Mobile Devices and Real-Time Embedded Systems. If you are looking for linking web services to embedded systems, Jence has a solution for you.
If you have a requirements specification, call us for an evaluation. Even if you do not have a requirements spec, we may help you write one.
For a dynamic company, software requirements are always changing. Jence brings the right expertise to deliver software based on customer requirements by recognizing and then fixing problems ahead of time. This reduces cost for the customers and for us.
At Jence Software, we implement ideas to fully functional software. By following our 9 simple steps explained below, you can make your ideas to reality.
Communication. This is the most important part. Communicate with us in any way convenient to you. We must understand your idea, so we will send messages back and forth to understand. You can present your idea confidentially to this website by (1.1) e-mail, (1.2) Call and talk to use about your idea. Send your emails to sales@jence.com. Our core compitency is developing SOA based software using jence.
Requirements Documents. As we commuicate, we write the requirements of your software in a running document, usually in PDF format, which is reviewed by you. At this point, you can modify the document to make any changes. You may write your requirements document yourself and send it to us. This may expedite the development process. For small projects, the requirements document is prepared at no cost. For large projects, there is a fee to be paid for this service.
Price It. After you review the document, if you believe that the requirements document is accurate and you would like to proceed with the development of the software, we will quote a price to develop the software and an approximate delivery time. Prices are paid upon completion of each modules. There is a requirement to pay 10% Advance payment to start the project. Upon completion of each module, the payment for that module have to be paid to continue the development process. The final payment is paid in the Maintenance step (Step 8).
Design. At this stage we write the design documents and pass it to you again for your review. You may do design changes at this point. If you have existing libraries, you may ask us to use those instead of us rewriting the libraries. Similar decision could be made with classes and modules. Based on the pricing model, there is a fee to be paid at the design stage. All fees will be listed in the Pricing document.
Implementation. This is the lengthy stage where we implement the design. The status of the implementation is updated on a weekly basis to our customers. Libraries, modules, and objects are developed at this stage. Implementation is conducted in modules. After completion of each module, a module fee have to be paid as will be shown in the pricing document.
Testing. As usual with software, we do extensive in-house test of the software before delivering the sotware for on-site testing. Any bugs found during this phase is immediately fixed. There is also a module testing fee to be paid at this stage as will be indicated in the pricing document.
Integration Test. In this phase, customers do the alpha and beta testing under their true environment. Any bug fixes at this stage will be fixed and will be given the hightest priority. Any dues must be paid at this time. Integration is the most important stage. Upon completion of this stage, 95% of the payment is already made. The remaing 5% is paid in the maintenance stage. For some projects 100% payment at this stage is required.
Maintenance. This is the software maintainance period during which bugs are fixed as they are reported. This usually leads to cleaner software. According to the pricing document, there will be a bug fixing period of 30 to 90 days. During this period, the customer test the software in order for us to fix the software so that the software is cleaner and has less bugs. It is required for the customer to pay any remaining balances at this time.
Upgrade. Additional features, functionality, interfaces and any other changes to the software is considered as updates. A software already delivered to the customer may be enhanced by adding more features are called updates. The customer requests for updates for their existing software and we note the required updates and regenerate a new software requirements document taking the loop back to Step 1, the Communication stage.
NineSTEP methodology is observed during the whole software life cycle. So, the end result is a robust software. An example of a Ninestep is given below. A company named XYZ, Inc is interested in using a custom payroll management system and contated Jence to develop one. At Step 1 (Communicate), XYZ, Inc discusses in detail over the email or phone and give us an overview of what the software is about. As XYZ get more serious about Jence developing the software for them, they ask us to join a meeting to build a requirements document (Step 2, Requirements). The Jence and XYZ team up with their developers and designers and generate a requirements specification of the project. During the requirements stage, pricing is also calculated and an overview design is done. Once Jence and XYZ agrees that the first version of the requirements document is done, the Jence team works on a pricing, which takes it to step 3 (Pricing). A pricing proposal is sent to XYZ for their approval. Once the document is signed by both parties (sometimes after negotiation), that make up a binding contract between the two parties. Pricing document details pricing for each step and each modules. At step 4 (Design), Jence will design the technical aspect of the project. This will create a design document, a running document during the whole project cycle. At step 5 (Implement), the design is implemented, and sometimes design is changed to as they become necessary and the design document is updated. At step 6 (Test), the implementation is tested for correctness. And at step 7 (Integration), integration testing is done with the help of the customer by installing the software in customer's server or PC. During this stage all bugs identified by users will be fixed. At step 8 (Maintain), software maintenance is done for 30 to 90 days based on the contract. Any upgrades of the software may be requested at step 9 (Upgrade).