IGNOU BCA 5th sem Solved Assignment - Which SDLC model best suits for the development of Student Admission System. Justify your selection

Which SDLC model best suits for the development of Student Admission System. Justify your selection by writing pros and cons of using the proposed SDLC model in comparison with any other SDLC model.

Ans .

Any logical process used by a systems analyst to develop an information system, including requirements, validation, training, and user ownership.

An SDLC should result in a high quality system that meets or exceeds customer expectations, within time and cost estimates, works effectively and efficiently in the current and planned Information Technology infrastructure, and is cheap to maintain and cost-effective to enhance.
While SDLC may be a specific process used in the IT world, its spirit can be found in any decision-making process in any arena. In most models of decision-making, there are four basic phases: Identification phase, Development of alternatives, Selection phase, and the Evaluation phase. SDLC incorporates five to six distinct phases, which utilizes the four previously mentioned phases. SDLC is a detailed model that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.  In every decision-making process, the players or participants can be as important as the process itself.   In some business decisions, not every member of the organization will be consulted before a decision is reached.   For example, a company trying to cut costs may decide to make changes without seeking every employee's opinion or approval. They may decide to change distributors for their office supplies to take advantage of lower prices.    However, in the System Development Life Cycle, all end-users affected should be part of the initial planning process.   System analysts and programmers are vital to the behind-the-scenes development.

To explore how the systems development life cycle is used in the enterprise, here are some additional resources:

Varying SDLC methodologies among development teams: Software development life cycle (SDLC) methodologies have their own advantages, tools and so forth. Expert David Christiansen explains why development groups should be allowed to embrace a variety of methodologies.

How use cases facilitate the SDLC: Why incorporate use case techniques into your software development lifecycle? Requirements expert Betty Luedke explains how use cases benefit the SDLC and how practitioners can get the most out of them

When to begin testing in the SDLC: Testing is one of the most important components of the software development lifecycle, but when to begin testing depends on a number of factors. Expert Mike Kelly discusses how certain issues affect the timing of testing in the SDLC.

The systems development life cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.

Various SDLC methodologies have been developed to guide the processes involved, including the waterfall model (which was the original SDLC method); rapid application development (RAD); joint application development (JAD); the fountain model; the spiral model; build and fix; and synchronize-and-stabilize. Frequently, several models are combined into some sort of hybrid methodology. Documentation is crucial regardless of the type of model chosen or devised for any application, and is usually done in parallel with the development process. Some methods work better for specific types of projects, but in the final analysis, the most important factor for the success of a project may be how closely the particular plan was followed.

In general, an SDLC methodology follows the following steps:

1.      The existing system is evaluated. Deficiencies are identified. This can be done by interviewing users of the system and consulting with support personnel.

2.      The new system requirements are defined. In particular, the deficiencies in the existing system must be addressed with specific proposals for improvement.

3.      The proposed system is designed. Plans are laid out concerning the physical construction, hardware, operating systems, programming, communications, and security issues.

4.      The new system is developed. The new components and programs must be obtained and installed. Users of the system must be trained in its use, and all aspects of performance must be tested. If necessary, adjustments must be made at this stage.

5.      The system is put into use. This can be done in various ways. The new system can phased in, according to application or location, and the old system gradually replaced. In some cases, it may be more cost-effective to shut down the old system and implement the new system all at once.

6.      Once the new system is up and running for a while, it should be exhaustively evaluated. Maintenance must be kept up rigorously at all times. Users of the system should be kept up-to-date concerning the latest modifications and procedures.