Slide background




Slide background




Application Development

RCS has more than 20 years of experience in Application Development activities. This includes projects of varied size from 20 days effort to more than 20 person years of development life cycle. RCS has necessary tools, resources, process and infrastructure to carry out such projects. The life cycle would be tailored to customer requirement and project execution would be fully transparent. Agile, Iterative, Waterfall and V life cycle model were extensively used to execute these projects.

RCS has talented pool of experts for developing applications in both traditional Waterfall based SDLC as well as the Agile practices like Scrum, RUP (Rational Unified Process), TDD (Test Driven Development). A rich set of processes allow the teams to pick and chose and tailor them in accordance with the Project execution methodology selected. The development is done through the phases of requirements analysis, design, implementation, testing, integration, and maintenance.  The RCS Project Management framework is an extension of the PMI project management lifecycle. RCS’ emphasis is on planning, tight control on schedules and cost variance.

Our Agile Methodology

  • Storyboarding
  • Prioritization
  • Sizing
  • Release Planning
  • Iteration Planning
  • Tracking
  • Retrospective
  • Sprint Planning Meeting
  • Daily Scrum Meeting
  • Sprint Review Meeting
  • Sprint Retrospective Meeting

Why Agile?

  • Decreased time to market
  • Adaptability to changing requirements and priorities
  • Increase probability of success
  • Higher visibility of progress
  • Reduces risk
  • Delivers business value early and in increments

Our RUP Approach

  • Use case analysis
  • Class, Sequence, Collaboration and Activity Modeling
  • Architecture Prototyping
  • Test planning and execution
  • Change Request management
  • Iteration planning
  • Deployment Planning
  • User documentation
  • Support planning

Why RUP?

  • Requirements not clear when project starts
  • Can deliver what the customer wants
  • Issues are discovered early in the project
  • Improved Risk management

Test Driven Development (TDD) is an advanced technique of using automated unit tests to drive the design of software and force decoupling of dependencies. The result of using this practice is a comprehensive suite of unit tests that can be run at any time to provide feedback that the software is still working. This technique is heavily emphasized by those using Agile development methodologies.

TDD Cycle

  • Add tests
  • Run all tests and see if the new one fails
  • Write some feature code
  • Run the automated tests and see them succeed
  • Re-factor feature code
  • Run the automated tests and see them succeed
  • Repeat/iterate

Why TDD?

  • Feedback that each component is still working
  • Unit tests act like documentation and
  • don’t go out-of-sync
  • Forces analysis and design before coding
  • Encourages better design like loose coupling
  • Re-factor with confidence
  • Regression safety net
  • Reduced debugging time