SDLC

What is the most important step of the SDLC? Why?

Questions by kaliterin

Showing Answers 1 - 33 of 33 Answers

sagar bandari

  • Jun 30th, 2008
 

An organization to develop an application, they follow the certain rules and regulations to develop software application, rules and regulations are described proces is SDLC. it contains 6 phases
1. business analyst gathers the requirements from client, and prepare the brs document. and product management team will prepare the snap shots based on the requirements.

2.based on the brs documents, pm and tl prepare the hld and lld design documents.

3.based on the HLD AND LLD developers develop the actual source code.

4.if the build is ready and stable then testers will do the test the functionalities of an application.

5.after the completion of testing qa and product team push the application into production side.

6.after the product is deployed, developed company will maintain the product for a particular duration.

golfnut1400

  • Jul 1st, 2008
 

Every Company that creates SW follows a SDLC but we all know they are all are not the same from company to company.  Some may follow the traditional waterfall and others follow Agile or Lean.  Since this question is open ended, the logical answer would be all phases of the SDLC is of equal importance.  The art and science behind releasing a quality product will depend how each company will able to handle the risks at each phase of the SDLC.

psrvasanthi

  • Jul 10th, 2008
 

requirement phase is very important bcoz w.r.t the application requirements  nly we need to test the appliocation from design phase to release phase hence analysis of the requirement given by the client should be verified thoroughly.

santy7in

  • Sep 1st, 2008
 

Hello?kaliterin,

I think you already got the answer, as mentioned by me friends Requirement gathering is sensitve area. 

Until and unless you know the customer expection its difficult to make them happy.

After that a regular reviews should be done on all the proccess followed and to be followed.

The next sensitive area is Implementation, if product is huge and has got more endusers.

nag786

  • Feb 6th, 2009
 

SDLC Software Development Life Cycle is a systematic way of developing a software product/Application using some company based standards and models. It has different phases and each phase is a base for the next phase and every phase is important one.

These phases are

Software Initiation Phase
Company Project Managers, Business Analysts, Leads etc peoples make some initial plans for the proposed project based on clients requests and demands, budget, cost, resources etc.


Requirement and Analysis Phase
BA and Leads will collect business requirements, what system is going to do what its not supposed to do what are real end user wants etc kind of things are gather and made as business requirement/specifications.? This requirements are possible or not/ feasible or not etc.
What are SW/HW requirements what are resources and etc

Design Phase

Team Leads and Architects will design the system High level design they will make and developers make Low level design documents
Define how the system should be like the Database design, network design etc.


Development Phase
SW developers and other analysts develop the code in any programming language or SW. SW Coding is done here


Testing
All the QA people test the developed code in different testing methodologies and testing types and find bugs and communicate the defects to the team and make sure the defects got fixed and retests them. And ensure the system is bug free.


Implementation and maintenance/Development and maintenance phase
System is moved to the production or to the real users. for the
customers and if any additional requirements are added or system is upgraded then all the people will work on that issue and implement it and maintains the system.

Thanks
Nagaraja Goud Emagowda
Ever

kurtz182

  • Dec 6th, 2009
 

I agree with those who say all phases of the Software Developement Life Cycle are important. In fact, as I review each of the phases, it becomes clear that all are almost equally important. Here's why:

1) Without the Software Initiation Phase, there would be no business case for the software application.  The project would never get off the ground.

2) Without the Requirement and Analysis Phase, there would be no business requirements from which to produce the software application.  Skipping this phase will add significant cost to the project and could easily produce an application that has little value to the company. 

3) Without the Design Phase, there would be no system architectural or programming structure or guidelines from which to produce the software application.  Skip this phase is like trying to pound a square peg into a round hole.  It simply won't work.  The development effort will become too costly without this up-front planning.

4) Without the Development Phase, there would be no coding activity to produce the software application.  Need I say more?

5) Without the Testing Phase, there would be no means to ensure the application releases to production with acceptible quality.  Companies that have taken this path no longer exist.

6) Without the Implementation Phase, the application would never reach production and customers would never use it.  Wait!  Isn't that why this application is being produced?

7) Without the Maintenance Phase, any problems users experience with the application would never receive attention.  Ok, if you want to select a least important phase, perhaps this is it.  Yet, it still seems very important to me.

Hmmmm.  So which phase in the Software Development Life Cyclle do I consider to be most important?  I'm afraid this world will never know.  

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions