what us software development life cycle explain briefly
Answers were Sorted based on User's Feedback
Answer / tamilkudimagan.r
Software development life cycle consists of four phases.
That is,
1.Analysis
2.Design
3.Implementation and
4.Testing
1.Analysis: Define the goals.Gathering the requirements to
develope a software for customer satisfaction.Aanalyse that
how to use and design?.
2.Design: Detailed design the requirements as a structure.
3.Implementation: Implement the detailed design with
designed code.
4.Testing: Check the whether the software will work
properly or satisfies the customer expectation.
If it is satisfies the customer needs, that software
properly produced.
This is software development life cycle.
Is This Answer Correct ? | 10 Yes | 4 No |
Answer / girish
Requirement collection
feasibility study
design
develop
testing
implimentationinstallation
maintenance
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / guest
Requirement Analysis
High level design
low level design
construction & unit testing
system and integration testing
Acceptance
maintance
Is This Answer Correct ? | 4 Yes | 6 No |
I have COG-132, COG-112 Latest Dec-2009 dump. If anybody need these dumps. Please send me a mail to certcert2009@gmail.com.
what is meant by business rules ?
how many check points required to freeze the requirements ? what and why ???
from delhi mohammed-bin-tughlak transferred his capital to
Which SDLC model should we select to develop a payroll system for an organisation with employee strength 1000.? here every employee gets salary based on designation, experience and qualification.If possible please tell 1. funcional and non functional requirements 2. schedule for project completion. draw gantt and pert chart 3. estimate cost of project 4. complete SRS development 5. test plan document development
what happens if we didnt close cursor in a cobol/db2 program
what is purchase life cycle IBM maximo
what is the different between all software models
Guidewire
Write an email to the client when your project is going to be released but unfortunately many major bugs are found and your lead is absent on that day, now you are the leader of the group and you have to release the build.
what are the most frequent requirement tracking and management tools available
Q1. Why a bug can't be fixed?