Stage 4: Building or Developing the Product
In this stage of SDLC the actual development starts and the product is built. The programming code is generated as per DDS during this stage. If the design is performed in a detailed and organized manner, code generation can be accomplished without much hassle.Developers must follow the coding guidelines defined by their organization and programming tools like compilers, interpreters, debuggers, etc. are used to generate the code. Different high level programming languages such as C, C++, Pascal, Java and PHP are used for coding. The programming language is chosen with respect to the type of software being developed.
Stage 5: Testing the Product
This stage is usually a subset of all the stages as in the modern SDLC models, the testing activities are mostly involved in all the stages of SDLC. However, this stage refers to the testing only stage of the product where product defects are reported, tracked, fixed and retested, until the product reaches the quality standards defined in the SRS.Stage 6: Deployment in the Market and Maintenance
Once the product is tested and ready to be deployed it is released formally in the appropriate market. Sometimes product deployment happens in stages as per the business strategy of that organization. The product may first be released in a limited segment and tested in the real business environment (UAT- User acceptance testing).Then based on the feedback, the product may be released as it is or with suggested enhancements in the targeting market segment. After the product is released in the market, its maintenance is done for the existing customer base.
- Design Tools
- IBM Rational Rose
- MS Visio
- MS Office
- Argo UML
- Magic Draw
- Rational Software Architect (IBM)
- Project Management tools
- MS Project
- MS Office
- Customized Project Management tracking tools - for metrics
- Configuration Management Tools
- IBM ClearCase
- VSS
- SVN
- AccuRev
- Git
- Java development tools (IDE)
- IBM's VisualAge for Java development
- Borland's Jbuilder for Java development
- Eclipse is from IBM
- Nebeans is from Sun/oracle
- Spring source tool (STS)
- IntelliJ from Idea
- Rational Software Architect (IBM)
- Code Review Tools
- Code Collaborator
- Cast
- Eclipse
- Sonar
- Microsoft development tools (IDE)
- Visual Studio
- Application Servers
- Jboss
- Glassfish (Open Source)
- Apache Geronimo Applications Server
- IBM - WebSphere Application Server
- BEA WebLogic Server
- Web server
- Apache Web Server (65% applications are hosted on apache)
- Internet Information Server (IIS) - 15% applications are hosted on IIS.
- Nginx from Nginx hosts around 12% of applications.
- GWS from Google (5%)
- Zeus Web Server
- iPlanet Web Server
- Roxen Web Server
- Jigsaw
- JRun
- Sambar Server
- Sun Java System Web Server
- Portal Server
- Websphere portal server
- Oracle WebCenter
- Adobe LifeCycle
- Middleware tools
- Mule ESB
- IBM Tivoli
- Snaplogic
- Dell Boomi
- SOA Based tools
- SalesForce
- Amazon Web Services (AWS)
- Windows Azure
- BPM Modeling tools
- JBPM
- Activiti
- WPS Websphere process server
- Build Tools
- Apache Maven is the build engine
- Rake
- Ant +Ivy
- Gradle
- Gant
- Buildr
- Agile Project Management Tools
- Rally
- Jira Agile
- Redmine
- Extreme Planner
- VersionOne
- TargetProcess
- AgileTrack
- Bamboo
- Testing Tools
- QTP/UFT
- RFT
- Test Manager
- Selenium
- Concordian
- JMEter
- Jprofiler
- Jprobe
- Loadrunner
- Defect Tracking Tools
- JIRA
- ClearQuest
- Rally - Online service for agile project management, requirements and test case management, and defect tracking. Consulting for agile project management. Located in Boulder, Colorado, USA
- BugZilla
- Continuous Integration
- Hudson
- Cruise Control
- TFS (MS First Sight)
- Hot deployments
- JRebel
- Collaboration tools
- Zipline,
- Basecamp
- Sharepoint
