Capgemini Jobs opening for freshers in Bangalore

By admin on September 21, 2016

Company Capgemini

Website http://www.Capgemini.com

Eligibility Bachelor’s Degree

Experience Freshers

Location Kolkata

Job Role System Associate

JOB SUMMARY:

Company Profile:

Any Degree Fresher’s required for the position System Associate in Capgemini at Kolkata. Interested and eligible candidates who have strong skill sets on desired profile can apply online for the requirement with the link given below. Find the job description, eligibility criteria, exact venue and interview details for more information.

Capgemini Hiring Any Degree freshers 2016 for System Associate at Kolkata. Candidates who have completed Any Degree can apply for this job from Capgemini.
Accenture is a global management consulting, technology services and outsourcing company. Combining unparalleled experience, comprehensive capabilities across all industries and business functions, and extensive research on the world’s most successful companies, Accenture collaborates with clients to help them become high-performance businesses and governments.
the various generic work steps of system development methodologies were replaced with work steps based on various structured analysis or structured design techniques. SDM, SDM2, SDM/70 and Spectrum more notably evolved into system development methodologies that were based on the works of Steven Ward, Tom Demarco, Larry Constantine, Ken Orr, Ed Yourdon, Michael A. Jackson and others as well as data modeling techniques developed by Thomas Bachmann and Peter Chen. SDM is a top-down model. Starting from the system as a whole, its description becomes more detailed as the design progresses. The method was marketed as a proprietary method that all company developers were required to use to ensure quality in customer projects
During the SDM functional design phase called BD (Basic Design), design aspects were documented (out of phase) in detail for the later technical design DD (Detailed Design). This caused a gray zone of responsibility to occur between the two phases; the functional crew responsible for the data flows and process flows in the BD were making decisions that the technical crew later needed to code, although their technical knowledge wasn’t detailed enough to make those decisions. This obviously led to problems in collaboration between project teams during both the BD and DD phases. Because of the waterfall method of Go/No Go decisions at the end of each phase, the technical crew would have to make a formal Change request in order to make corrections in the detailed sections of the Basic Design. Such changes were often confusing for the customer, because these originated from the project team rather than directly from the customer requirements, even after a change freeze was put in place. Usually the customer was only allowed to produce requirements up to and including the functional design in the BD phase. After that, the customer had to wait patiently until acceptance testing in the Implementation phase.

Submit your resume - FreshersOpenings.in