Interested to Buy Any Domain ? << Click Here >> for more details...
what us software development life cycle explain briefly
- 3 Answers
- 11069 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 |
how to manage the requirement if it is included after Requirement specifications phase
John weight twice as much as Marciua. Marcia weight is 60% of Bob's weight. Dave weight s 50% of lee weight 190% of john weight. Which of these 5 person weight the least?
what happens if we didnt close cursor in a cobol/db2 program
what did u do in the sap sd project ?how did u maping your client business?plz i need help....
Q1. Why a bug can't be fixed?
I have COG-132, COG-112 Latest Dec-2009 dump. If anybody need these dumps. Please send me a mail to certcert2009@gmail.com.
Can you make 120 with 5 Zeroes?
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
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.
Give me an e.g. of Low Severiority and low priority?
what are the most frequent requirement tracking and management tools available
who are the stake holders in gathering requirement of a new product
Requirement Management 
