Jinisys Software Inc. offers IT Consultation and provides full life-cycle of extensive Software Development solutions that fits with your business and delivers value to your customers.
Our software development services address the needs of vertical market such as hotel, restaurant, retail, healthcare and transport. We have other services that can also be integrated with our software products.
Our method and approach are based on agile software development processes and the technologies that we use are widely accepted and used.
- Requirement Elicitation
- Plan Formulation
- Software Testing
- Maintenance and Debugging
Software Development at Jinisys:
To find out more about how Jinisys Software can help you Contact Us today.
What is Custom Software Development For Us?
Step 1: Requirement Elicitation
Analyze Client Requirement.
This phase of software development converts your abstract ideas as a customer in to structured document that clearly exhibits the requirements of the software. The sales team spent time with you and your staffs discussing about the various aspects of what you would like to see in the developed system. Brainstorming, interviews, questionnaires and observations are few techniques used to come up with a sound requirement study.
Scooping and Feasibility Analysis.
At this point once the preliminary discussion is complete, the understanding of the requirements is scooped up and the scope of the project is defined. Evaluation plays a key role at this point; wherein the cost effectiveness of the project is examined and alternative solutions and estimates are suggested to you as a customer if required. All the parameters are reviewed by you and the sales team to ensure that the expectations are set right between the both parties.
Client’s Business Goal.
Client’s business objectives are studied before suggestions about solutions are made by the sales team. Analyzing the problems faced in the business process is the other side of the same coin. Discussing with employees and studying the competitors are two techniques used to come up with a system that suits you and fits in your budget. These small discussions and questionnaires in between go a long way in developing a system designed to solve all your problems keeping your goals in mind.
Meeting the expectation of the user is highly important for the success of software. For this the sales team spends time understanding the working requirements of the end users and discusses about different aspects of the interface. This also involves discourses on the limitations of the current system if you are using one. An in-depth study is conducted in this phase to avoid any roadblocks in the coming phases. The functions and operations expected from the application are completely understood at the end of this phase.
Step 2: Plan Formulation
This phase begins with the production team going through the requirements and understanding it. The aim of this phase is to ensure that the developer has a clear understanding of what you would like to see in the end. A high level design of the software is prepared in this section. It displays high level components and connectors of the system; which helps in giving an overall view of the software to be built. The architecture design of the software to be built is also decided in this stage.
In this part the database design and the user interface design is dealt with. This involves listing out the components involved and their purpose. Diagrams are used to clearly represent the functions and operations of each component in these designs. The basic UI design helps in understanding the layout of the pages and defines the scope of the implementation of the same.
At this point the expected behavior of the software is studied and document. This document is a reference for three sets of people. Developers read this to understand what the overall behavior of the system and to make the technical design document; testing team understands what they require to test for and create test cases based on this; and the stakeholders get a view of the system they would be getting shortly. All the functional parameters are defined and the scope of the system is described in detail to avoid any misunderstanding.
This is where you get to see a basic model of your system. You get to view you user interface and basic working modules. You get to give your feedback and make changes if required. The changes to be made are noted and all the documents are revisited and updated to reflect the changes.
Step 3: Implementation
Design at this stage involves a detailed description of functionalities of the system. Flow charts and data flow diagrams are used to show the components and their relationships. The attributes and operations of each component are defined to the dot. It also contains information about the attribute names and data types. Pseudo code is included wherever applicable. The output of this stage produces the detailed design document which all the technical details of the software. This document is important to keep track of the implementation details. It gives the coder step by step understanding of how the system should be built.
This is where your system begins to take form. The developer works on putting your database and the software components in place and gets them working. Your software now begins to take shape in small modules. The development is divided in two or more modules depending on the complexity of the software. Every module is developed and tested individually by the developer. The technical design document is referred to ensure all the expectations are met.
Step 4: Software Testing / QA
Integrate and Regression Testing
All the modules are integrated together to give your software the final form. Any issue in this phase is handled by the developers. Once the integrated system begins to function, the software is passed on to the testing part of the production team. At this point, testing begins keeping the test cases created as the reference. Every test case is document with expected result and the result of the system. If the result shown by the system is different from the expected output a fault or error is logged.
This section involves going through all the documents from the beginning and verifying if all the requirements have been met. Any deviation is logged as a defect of the system. This gives the whole process a triple check of meeting the client requirements and leaves barely any space for errors or unpleasant surprises for you as the end users.
The errors, faults and defects are worked upon by the developers. The changed code is then updated to the latest version of the software. Step by step your software is taken to what it should be like. Once all the bugs are fixed your software is now ready.
Step 5: Deployment
Once the software is ready, a date is decided upon by the production team based on discussions with you and depending on this they create the deliverables. The deliverables include deployable files and the project documents. The production environment is prepared for deployment. Intimations regarding downtimes and the installation are communicated to the required stakeholders and users.
Deployment takes place in the production environment. And the installation is said to be complete once the new system is up and running in the business environment. A round of testing is done to check the working of the system. Communication about the installation is sent.
At this stage, the end users are given classroom and hands-on training on how to use the software. Documents are also prepared and circulated for reference purposes. You are accustomed to the look and feel of the new system during this phase. These training are provided to avoid any confusion when performing business activities. The documents provided can also be used for training new members in the future.
Step 6: Maintenance
This stage tackles any issues that happen in the production environment. The errors are corrected and fixes are deployed in production. These focus around improving the performance and usability of the system. The developers and testers work closely during this period to ensure the fixes provided are correct and are not disturbing the system in anyway.
Feedback about the software is important to know the comfort level of the end user with the software. This opens opportunity for future enhancements to improve the software.
The support team is just a call or mail away from addressing your issues. They help rectify issues in production. In some cases they also provide minor fixes for smooth running of the production environment. Other maintenance related activities are also performed to enhance the efficiency of the system.