System Development Life Cycle

Secondly, we move to the analysis stage where a detailed investigation is carried out in order to ascertain the strengths and weaknesses and to produce a requirement list for the new system.

What errors or problems will the new system have? The third stage is component design. For component design, we have to design the database and determine hardware specifications. The fourth stage is implementation. During this stage you have to build system components and conduct tests to see if it works properly.

Our objectives in this project deal with the existent problems of the current system and what should be accomplished to solve them.

IS development processes are the number of keys that involving in the development processes and referrers as the phrases of the systems development life-cycles, which is a traditional processes used to develop information systems. Some researchers has described that the basic task is playing a crucial role on the performance of successful build and maintain information systems. In fact, there are several projects that have been failure or success at the early phrases because of the disaster of making determination. For instance, the key stakeholder factor will have different responsibilities and engage in the successes or failure of the project. This relates to the efficiency communication processes such as consistent, accurate and timely

There are many ways to develop an Information system, which is very complex. The systems development life cycle (SDLC) provides an overall efficient framework for managing the process of system development. Various organizations use information systems to support all kind of processes that a business needs to carry out its functions. There are different kind of information system and each has its own life, and system developer describe this idea as life cycle of system. During the life of an information system, it is first conceived as an idea; then it is designed, built, and deployed during a development project; and finally it is put into production and used to support the business. Projects during

A system development lifecycle (SDLC) is a general process for developing information systems. It provides a

SDLC stands for the systems development life cycle. It 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. There are five steps to the SDLC, which are planning, analyze, design, implementation, and maintenance. The Boehm- Waterfall Software engineering methodology relates to SDLC because it contains stages that hold stages of system requirements, software requirements, preliminary and detailed design, implementation, testing, operations, and maintenance. SDLC and the Boehm-Waterfall methodology are both very similar, however the Boehm-Waterfall is a more detailed methodology and also includes validation at each stage where SDLC does not have any of those advantages.

At the conclusion of the requirements phase, the team has agreed upon the needs of the business and what must be required of the new system. The next step in designing and implementing the new system is determining the processes that will be applied to the data and graphically representing them in a model using structured analysis techniques. Process models are used to identify and document the portion of system requirements that relates to data. Processes are the logical rules that are applied to transform the data into meaningful information. During this phase, data flow diagrams are required to show how the data will move through the system. The systems data flow and data stores are then documented in the data dictionary, which is used

Systems Development Life Cycle (SDLC) or sometimes just (SLC) is defined by the as a software development process, although it is also a distinct process independent of software or other information technology considerations. It is used by a systems analyst to develop an information system, including requirements, validation, training, and user ownership through investigation, analysis, design, implementation, and maintenance. SDLC is also known as information systems development or application development. 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

Systems Implementation is the fourth of five stages in the systems development life cycle (SDLC). In the previous stage, systems design, you developed a physical model that included data design, user interface, input and output design, and system architecture. Now you will begin systems implementation tasks, including application development, testing, documentation, training, data conversion, system changeover and post-implementation evaluation of the results. At the conclusion of the systems implementation stage, user will be working with the system on a day-to-day basis, and you will focus on system operation, security and support, which is the final stage in the SDLC.

A life cycle in system analysis is a term used to describe a process for planning, creating, testing, and deploying an information system. The systems development life-cycle concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both.

System requirement are the specification that define the functions or performance to be provided by a system logically and physically. The objective of identifying the system requirement is to understand the business functions and develop a system with the necessary specification that will meet those functions. To develop any system the systems analyst needs to collect facts and all relevant information to identify or clarify what the organization wants out of the system to accomplish their objectives or goals.

Prior to Zachman, organizations often introduced information systems technology in direct response to a perceived need by the organization such as the automation of a particular job function (Bernard, 2011). As Bernard notes, this became increasingly problematic as organizations evolved as did their need for integration and communication between their system implementations. Systems developed to meet business requirements on a case by case basis often using proprietary vendor products which eventually led to heterogeneous collection of disharmonious systems (Bernard, 2011).

Though many people interchange system engineering models and software engineering life cycle models, they are defined as two different approaches to software development. System engineering is the technical and technical management process that results in delivered products and systems that exhibit the best balance of cost and performance. As the program progresses from one phase to the next one, so does the system engineering process. It deals with the overall management of engineering project during their life cycle. Its main focus is knowing what the clients and end users wants and needs are satisfied and developing just that all the way through the system’s entire life cycle. Whereas, on the other hand, software engineering focuses on the quality of the product or system, how cost effective it is, is it done within the time-constraints given, whether it is easy to maintain and enhance, and does it work as the requirements defined. Its main focus is on delivering a product that meets the requirement specifications. There are so many models to choose from, as it all depends on what the project needs and entails. Depending on the requirements, allows for the choice of what mode to use.

Businesses rely heavily on their information systems for decision making, an essential component of organization management. Information systems serves several purposes in a business, ranging from transactions and assisting leadership with difficult strategy formulation. Advances in computer-based information technology in recent years have led to a widely variety of systems that managers are now using to make and implement decisions (Alter, 1976). In today’s businesses, systems development is a process of examining a business situation to analyze better procedures and methods to stay competitive. System development life cycle (SDLC) methodologies are promoted as means of improving the management and control of the software development process, structuring and simplifying the process by specifying activities to be done and techniques to be used (Russo, 1995). Every businesses have different types of projects that have different requirements. Therefore, businesses must choose the SDLC phases according to the specific needs of the project. There are different types of SDLC. These are Waterfall Model, V-Shaped Model, Prototyping Model, Spiral Model, Iterative Incremental Model, and Extreme programming (Agile development) (Sami, 2012). Each of the models has different level of risks and benefits to cope with the project requirements. This paper will discuss the processes of System Development Life Cycle methodologies that makes it excessively formal and rigid and