System Development Life Cycle
What is a system? In simple terms, a system a way of doing things. Businesses and other organizations need to have systems to cope with their business activities like orders, accounts, payroll, of systems. When they create products, programmers follow the process - or life cycle- that is similar to the (incentive information systems, the system has a cycle:
- It is created.
- It has a useful life
- it gets old and retires when no longer useful.
System analysis is down before creating a system or improving the existing system, is a of steps by a person, called the systems analyst, to create new A system is developed in various stages. This process is called the system development life cycle (SDLC). The basic stages of an SDLC are discussed here.
Phase 1: Needs Analysis. Needs analysis is the stage when a need or problem is identified and understood. this early stage, the programmer looks at the program design to see what the user needs for an interface and starting pong and what the user needs the program to do. Typically, the end-user should have a top of input in the needs analysis stage. Once the programmer determined the program's starting and stopping points, he or she can begin to design the code.
Phase 2: Program Design. The program design is the stage at which programmers begin roughing out the logic they will use when the actual coding begins, Many tools are used in the program design process, although programmers often rely on whiteboards and the backs of napkins. Three of these design tools arc IPO charts (for programming), circles and message pipes (object-oriented programming), and pseudocode.
Phase 3: Development, Development (also called coding) involves writing and testing source code. The software development phase is similar to the system life cycle's development phase, but instead of determining the system's overall layout, the programmer writes the code that implements the user's The programmer might write source code in a text editor and then compile the code, or he or she may use a visual editor and errors. Syntax errors violate the rules of the programming language. Finding syntax errors is relatively easy because the computer or interpreter will point them out to the programmer. Logic errors, actual mistakes in the algorithm, are more difficult to find and may not even show up until weeks or months after the program has been implemented. The process of identifying and eliminating these errors is called debugging,
Phase 4: Implementation. Implementation involves installing software and allowing to test it. This step often includes a lot of documents, both inside the code and in the form of manuals for the users. Many programmers also will tell you that they do most of their debugging at this stage,
Certainly, the implementation stage is when any misconceptions the programmer had about the code are found and fixed.
Phase 5: Testing, Before the new system, is used, it is thoroughly tested.
This is done in four stages:
- They should be tested using data which do not contain any errors and check if it produces the correct result.
- Some known errors should be introduced into the data to check how the computer processes it.
- The output obtained is verified to ensure that the results are as expected.
- The extreme data should be entered in order to ensure that the range checks are included as a part of the validation process.
Phase 6: Evaluation, Systems are monitored in order to ensure that the user is satisfied with its performance. On completing the implementation of a project, it should be reviewed periodically to that it is its objectives, The best-known way for evaluating a solution is by asking the users of the system. They will be able to judge if the system has the capability to do what they want it to or it needs any improvements. A user questionnaire is given to find out what the users think of the system. The answers to the questionnaire are used for improving or modifying the system.
Phase 7: Maintenance. Maintenance starts as soon as the program is installed. Work continues on products for several reasons. Some minor bugs may not have been fixed at the time the program was released. The programmers also may add major new functioning, in response to either market demands or user requests. This is the longest phase of the program development life cycle, sometimes spanning many years.

0 Comments