Coding Phase
The LLD document contains all the details for a programmer to convert it into a working program. Designed in the right way, the job of the developer is to convert the pseudo code into a programming language in the specified platform. The developer will be givenspecific guidelines that tell how to code. This guideline includes the naming convention of procedures, variables, commenting methods etc. As per the guidelines, the developercodes and at the end of the coding, he/she compiles the program unit.
By compiling and correcting the errors, all syntax error and removed. Syntax errors are the easy ones to rectify. The logical errors in the programs are the difficult ones toidentify and then rectify. By logical error, we mean, the program behaves in a way, that itis not expected to behave. The role of testers is to identify the logical errors at variousstages.
Testing
*This section provides only a shorter version of the testing techniques.
Testing is the process of evaluating a system or application, to check whether the application meets all requirements of the client and to detect the errors.
Generally testing can be classified into static testing and dynamic testing.
Again Dynamic Testing is classified into two types: Structural Testing (or) white box , Functional Testing (or) Black Box testing.
Static Testing
Verification activities fall into the category of Static Testing. Static testing refers to testing something that’s not running. It is examining and reviewing it. i.e., to check whether the work done meets the standards of the organization. Reviews, Inspections and Walk-throughs are static testing methodologies.
Example: The specification is a document and not an executing program. When we read it to find out the issues, it is considered as static testing.
Dynamic Testing
Dynamic Testing involves working with the software, giving input values and checking if the output is as expected. These are the Validation activities. Unit Tests, Integration Tests, System Tests and Acceptance Tests are few of the Dynamic Testing methodologies.
Techniques used are determined by type of testing that must be conducted.
• Functional ("black box") testing.
• Structural (usually called "white box") testing.
Black box testing involves looking at the specifications and does not require examining the code of a program. Tests that examine the observable behavior of software as evidenced by its outputs without referencing to internal functions is black box testing. It is not based on any knowledge of internal design or code and tests are based on requirements and functionality. Nowadays there are automatic code generation tools and code re-use becomes more prevalent, analysis of source code itself becomes less important and functional tests become more important.
Black box testing is easy as it is based on system’s response for a given user’s input. If we know the business functionality of the product, we can do black box testing. On the other hand, white box testing requires programming knowledge to know the internals of the code. Also it is time consuming. So only a developer can become a white box tester.
Unit Testing
Soon after the program is corrected for syntax errors, the program has to be checked for logical errors, at the unit level. Programs may have simple user inputs or outputs thru screens or reports. The inputs must be validated for their format, data type, boundaryconditions etc. Also, the elementary functionality of the program must be verified. Inmost of the cases, the programmers themselves will do this unit testing. Many inputs will be verified in this way and the program unit will be checked for the basic functionality in this phase.
If there are any problems while doing this testing, the programmers will debug theprogram and the bugs will be fixed and will be tested again for the bug fix. While doingthe unit testing, that particular unit need not wait for another unit to be completed. It canbe tested independently. Unit testing is also termed as component testing. For example, if we need to test a java class and method, even without any screen, the programmer can test the same. Thus any piece of code, that can be independently executed, can be independently tested as well. This is termed as unit testing.
Integration Testing
When all the individual program units are tested in the unit testing phase and all units are clear of any known bugs, the interfaces between those modules will be tested, toestablish that they communicate to each other property via the specified APIs and thusthey can be integrated into an application. The integration test may be performed by theindependent testers or by the development team members.
System Testing
After all the interfaces are tested between multiple modules, the whole set of software is tested to establish that all modules work together correctly as an application or system or package. This is again performed by independent testes. The testers will have to dothe system testing as though they are the end users of the application. Systems testing includes special testing methods like performance testing, interoperability testing,stability testing etc.
Acceptance Testing
After the software product is tested by the SDU in 3 different stages (unit, integration and system), the client will test it, in their place, in a near-real-time or simulated environment.This establishes that the software meets the requirements of the end user. This testing is carried out as though they are using the system in their real office, to mimic the realtime scenarios.
Implementation Phase/Support
This Phase will provide users with the documentation and training required to use the system effectively. Data Conversion will only occur once, but user documentation will be required. Deployment of the product will be carried out, on the hardware that is going to be used in production (on live systems). Deployment itself requires careful planning. Once the product is deployed, initial data will be populated, user training will happen.
Release to Production and warranty Period
When the clients to the acceptance testing and finds no problems, then they will accept the software and now they have to start using the software in their real office. It may be a real bank for a banking application. During the acceptance testing also, there may be some bug fixed done to the software. Before the software is put into production (real time environment), the SDU must release the latest versions of the software, which has no known bugs to the client. This may be in a CD or tape or an Internet download. The clients will then install the latest software in their production system and will start using. This is called go-live process.
In the same way every product has a guarantee period software also has a warranty period. Normally it will be a 60-day or a 90-day warranty period for most kinds of software. Depending upon the complexity and size of the software the warranty period may be extended or shortened. During this warranty period, in case of any problems, the SDU has the responsibility to rectify the problem, at no charges. Again, it depends upon the contract, whether to charge for the fix or not and may vary from industry to industry.
Maintenance Phase
After the warranty period, the software enters the maintenance phase. During the maintenance phase, 3 things happen to the software. They are :
• Bug fixing
• Upgrade
• Enhancement
During the maintenance phase, because of some untested scenarios, the software may give errors or logical problems. This has to be fixed. This is same as any other bugfixing. This is similar to any repair works done to a vehicle, by its owner.
In the software field, the software versions are constantly changing and the applications may have to keep themselves upgraded to the newer versions of the software. Forexample, the anti-virus software must be constantly upgraded to address new viruses,which come very day. If the operating system version charges, it may necessitate tointroduce some changes in the programs. So, this kind of upgrade works to the existingsoftware applications, because of operating system or environmental changes or hardware changes may have to be incorporated.
Any software is not all complete and there are enough rooms to add new features to anexisting software. For example, today the railways reservation system may not be in theinternet; but tomorrow there may be a need to go in the internet way. So, new modulesare to be added to the existing system to address this. This is enhancement.
After some time, the software may become obsolete and will reach a point that it cannotbe used. At that time, it will be replaced by another software which is superior to that. This is the end of the software. The software will reach its end, when the maintenance cost of the software becomes more than the new software available. Software can become obsolete when the company does not upgrade it to work on new environments such as databases or operating systems. When the software becomes incompatible with the environment, users will move on to another software, dumping the existing one.
No comments:
Post a Comment