Weakness of Traditional Systems Development Life Cycle (SDLC)

Almost the same as any other industry standards, system development life cycle has advantages and disadvantages. The surplus is the sequential steps that allows system developers to focus on the I step first, and after moving to the next step. For beginners this approach is very useful. But there are some disadvantages as a result and these sequential steps, including:

1. Too wasteful, and in terms of both cost and time, when there are changes when the system has been developed. This is due to a change in one phase will result in a later stage. Thus, the SDLC must be implemented with the assumption that each stage should not be mistaken.
2. SDLC is a method that requires a structured approach to follow all the steps there. If developers want a faster manufacturing process by eliminating one or more steps then the result is a system built to fail.

Phase Maintenance

The last step and the SDLC in which the system at this stage systematically improved and enhanced. Results and this stage is that the new version and the software that has been made. Improvements made can be very varied levels, starting and improving a crash program to function again until the addition of modules that a new program in response to changing user needs.

Step-by-step maintenance system comprising:

1. Use of System. That is using the system in accordance with the functions of their respective duties for the operation or daily routine.
2. Audit System. Namely to use and formal research to determine how well the new system can meet the performance criteria. This sort of thing is called the review after the application and can be performed by an internal auditor.
3. System Maintenance. Ie monitoring for routine checks so that the system is still operating properly. In addition, to maintain recency system at any time if the environment changes or modifications to the design of software systems.
4. Repair System. Ie do repairs if the surgery goes wrong (bugs) in program or design flaws that were not detected when the system testing phase.
5. Improved System. Ie making modifications to the system when there is potential for improvement as the system running for some time, usually the potential for increased system is seen by the manager and then forwarded to the specialist information for managers as desired modifications.

Phase Implementation

In the fifth stage of the SDLC, there are some things to do, namely:

1. Testing, the test results of the program code has been generated and the physical design phase. The purpose of testing is twofold. And the system developers, should be ensured that the program code are made freely and syntax and logic errors. And the user side, the resulting program should be able to resolve the existing problems on the client and the new system should be easy to administer and understood by end users.
2. Installation. After graduation testing program, the software and hardware will be installed on the client organization and formally put into use to replace the old system.

Phase Design

Design phase are the phases of change is still a concept needs to system specifications are nil. Stages of system design can be divided into two stages, namely the logical design (logical design) and the stages of physical design (physical design). As for differences, and both can be described as follows:

Logical design
Logical design is the design phase of the SDLC and where all the functional features and analysis phases of the system chosen and described separately and later on the computer platform used.

Results and these phases are:
a. Functional description of the data and processes that exist in the new system.
b. A detailed description and specification of systems, including:

• Input (what data is to be input).
• Output (what information is being output).
• Process (what are the procedures that should be executed to transform inputs into outputs).

Logical design phase usually produces several documents, including document data model, process model document, the draft table, hierarchy between modules, to interface design and systems that will be created.

Physical design
In this section, the logical specification is converted into the detail of technology where programming and system development can be resolved. At this stage the activity and the coding is done The output of this system are:

a. Technical description, the choice of software technology and hardware used.
b. A detailed description and specification of the system include:

• Program modules
• The files
• Network Systems
• System software

At the design stage, there are some major activities carried out, namely:

1. Design and integrate the network.
2. Designing the application architecture.
3. Designing the user interface.
4. Designing the system interface.
5. Designing and integrating the database.
6. Create a prototype for detail and design.
7. Designing and integrating the control system.

Phase Analysis

The third phase of the SDLC is the phase Analysis. The phase Analysis is the phase at which the system being studied and the system running the proposed replacement. System described in this stage running, problems, and opportunities are defined, and general recommendations for how to improve, enhance or replace the proposed system is running. The main objective and the analysis phase is to understand and document business needs and requirements of new systems and processes. There are six main activities in this phase:

1. Collection of information
The initial step in the analysis stage is to collect information about how the business processes that exist in the old system running. Then determined at points where any business process that has the problem that can be solved by information systems. And weaknesses are identified and repaired old systems with new systems.

2. Defining the system requirements
And weaknesses of information systems is obtained, then the system analysts to define what is actually needed by the old system to overcome the problem. This is what is referred to as system requirements. Often these needs will change the total overall business processes on the old system, but sometimes it just changes the addition of several new procedures.

3. Prioritize needs
In some cases, the need to obtain a very complete and complex. Availability of time and other resources to complete the whole requirement may not be sufficient. In this condition, then the analyst will prioritize the needs that are considered critical to be prioritized.

3. Develop and evaluate alternatives
One thing that analysts should not be forgotten is the second plan. After arranging and prioritizing needs, the analyst must prepare an alternative arrangement in case the need will be rejected by the client.

4. Review needs with management
The final step is to review existing requirements with the client, because the client the most out of their system needs.

Project Initiation and Planning

In this stage, potential Information System (IS) projects are described and presented arguments for continuing the project. Thorough work plan is also prepared to run the other stages. At this stage it is determined in detail the work plan that should be done, the required duration of each stage, human resources, software, hardware, and financial estimates. Usually those things outlined in the project implementation schedule. Preparation of planning because it is not easy steps to estimate the workload and duration of each stage and takes a fair amount of experience. Errors at this stage will not result in maximum profits, even losses. At this stage the role of an experienced manager of information systems is needed.

Project Identification and Selection

Constitute the first step in SDLC the overall information required by the system: identification, analysis, prioritization, and rearrange. In this stage there are some things that should be done, among them:

1. Identify potential projects. Potential and the project in question is how much profit who can be by, the duration of time available is insufficient to complete the project, and whether its resources are able to complete the project.

2. Classify and rank the project. If at the same time there are several projects that should be done at the same time it needs to be made classification and ranking of projects, and projects are most worthy to be done until the project is felt to be beneficial if done.

3. Selecting projects to be developed. If the classification and ranking has been established then the next step is to determine which projects should be done.

The resources involved are the users, systems analysts, and managers who coordinate the project. Activities are usually done at this stage include interviewing management of users, summarizes the knowledge gained, and estimate the scope of the project and documenting the results. This phase will produce a feasibility report contains the definition of the problem and summary of objectives and projects selected.

System Development Methodology

Some experts divide the system development process into a number of different sequences. But it will refer to the processes of the following standards:
1. Analysis
2. Design
3. Implementation
4. Maintenance

In its development, standardized processes were outlined in a method known as the Systems Development Life Cycle (SDLC) which is a common methodology in the development of systems that mark the progress of the analysis and design effort. SDLC phases include the following:
1. Project Identification and Selection
2. Project Initiation and Planning
3. Analysis
4. Design

• logical design
• physical design

5. Implementation
6. Maintenance

Understanding System Analysis and Design

System analysis is defined as how to understand and specify in detail what should be done by the system. While the system design is defined as explained in detail how the parts and information systems are implemented. Thus, the analysis and design of information systems (ANSI) can be defined as: complex organizational process in which computer-based information systems are implemented. Or it could be summarized as follows:

Analysis: defining the problem.

From requirements to specification.

Design: solve the problem.

From specification to implementation.

There is a key question, why the order of the stages in ANSI becomes very important. There are several specific reasons. First, the success of an information system depends on good analysis and design. Stages of the analysis will determine what should be problem solved on your organization. Errors in this phase will lead to the problem persists even though the information system has been implemented. While the design phase will determine what kind of system will function. Although at this stage of the analysis of the main problems has been mapped correctly, will result in failure of a design error problem solving by computer systems. Thus, these two steps is a crucial step for the development of the system.

Second, the ANSI method is a method long used to build conventional software. Thus, the validity of standard measures that have been tested. This method has also been used extensively in various industries (technology that has been tested).

Third, ANSI offers a new profession as an analyst. In the previous section, we discussed that a responsible stakeholder in the implementation of all phases of the ANSI is an analyst. With the industrial development of the information system is the system analyst and a career in the IT world, offers a lot of fun and challenges, as well as the salaries are not low. And the demand for systems analysts and expertise year after year have also increased. Systems analyst is a challenging profession because it combines many skills such as analytical skills, technical, interpersonal, and managerial. This can be seen and responsibilities of an analyst is based on ANSI approach, which includes:

1. How to build information systems.
2. How to analyze requirements and information systems.
3. How to design a computer-based information systems.
4. How to solve problems within the organization through information systems.