what us software development life cycle explain briefly
- 3 Answers
- 10000 Views
- I also Faced
- E-Mail Answers
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 |
Which company made 'Office Hindi' softwear?
HI Friends. this is balu. I am looking for testing job in chennai. If u know anything regarding job information. pls send a mail to me kool.balu@gmail.com
what is the different between all software models
how many check points required to freeze the requirements ? what and why ???
i am a student may i know mhat are the software companies providing industrial visit in chennai
how to manage the requirement if it is included after Requirement specifications phase
Find the 3 digits no. whose lat digit is the sqaure root of the first root of the first digits and second digit is the sum of the other two digits. And the number is divisble by 2,3,6,7. what is the number?
Host and Agent are the component associated with which tool?
Give me an e.g. of Low Severiority and High priority?
what are the major differences in requirement when compared among SW project requirement and Product requirement
in SW development who will be the owner of the perticular requirement and what is his responsibilities
Give me an e.g. of Low Severiority and low priority?
Requirement Management 
