Question

Dwight Eisenhower said “Plans are worthless, but planning is everything” - relate this saying to the software development life cycle.

Answer 1

Answer:-

yes plans are worthless but planning is everything in software development life cycle

Planning and Analysis is the most important stage of SDLC. Many companies only spend 10-15 % on these two phases and in the end they fail because they didn't plan and analyze the product that was needed to invent.

Spending more time on these two phases would decrease the failing overtime and reduce expenses by producing a needy product or service. This stage MUST NOT be ignored to generate more business and desired results.

Plan. “What do we want?” In this stage of SDLC, the team defines the requirements of the new software and determines the cost and resources required. It also details the risks involved and provides sub-plans for softening those risks. In this stage, a Software Requirement Specification document is created

Planning for the entire life-cycle of software development is necessary if you are going to deliver complex non-trivial systems.

The diagram below shows one way of approaching the life-cycle. Reviewing the entire cycle will help to avoid extra work, avoid misunderstandings, make it easier to put corrections in the field and ultimately retire the system.

Seeing ‘the big picture’ gives you a better idea earlier on as to the resources you will require (money, time, personnel, expertise, tools, approvals, etc). Looking at the entire cycle beforehand would save most large enterprises a lot of time, trouble and money because a significant portion of projects that would have gone ahead (and failed) will be cancelled.

If nothing else, an SDLC gives you common names and language to use on the team and a map of where things belong in time and space

SDLC works by lowering the cost of software development while simultaneously improving quality and shortening production time. SDLC achieves these apparently divergent goals by following a plan that removes the typical pitfalls to software development projects. That plan starts by evaluating existing systems for deficiencies. Next, it defines the requirements of the new system. It then creates the software through the stages of design, development, testing, and deployment. By anticipating costly mistakes like failing to ask the end user for suggestions, SLDC can eliminate redundant rework and after-the-fact fixes.

• If you really want to learn about the SDLC and the software process and how the software is built in the industry, then choose a SDLC and follow it strictly. A SDLC would give you a set of guidelines which would gradually build your software. You need to define the time frame in which you would want to finish your project and divide the work accordingly. There are several papers in the academia which can help you in choosing a SDLC. Since you are still in college, I would suggest you adopt an agile methodology such as Scrum or Kanban.
• The first and foremost step is to gather and analyze the requirements. This requires identifying the stakeholders, conducting interviews and trying to come out with what is required. If you do not have a client, then the team can brainstorm together on what can be the features you would like in your software. The key is to think from a consumer perspective and not from a developer perspective. Develop Use Case diagrams and UI mockups to finalize the features. Once you have a set of features, derive the architecture of your software. There are several types of software architectures and you might want to look what is best for your software given the features you want to develop. Try to keep your architecture independent of the programming language to be used. At this point, you might start thinking about the language and the technologies you would like to use. Do the implementation as per the methodology your SDLC says. Agile would require you to divide your features into sprints/increments and develop one sprint/increment at a time. Do the testing and bug-fixing when implementation is done. You need not worry about support for a college project.