What is the structure approach called for developing software and information systems?
Systems Development - Overview of systems and design, System development management life-cycleSystems development is the procedure of defining, designing, testing, and implementing a new software application or program. It comprises of the internal development of customized systems, the establishment of database systems, or the attainment of third party developed software. In this system, written standards and techniques must monitor all information systems processing functions. The management of company must describe and execute standards and embrace suitable system development life cycle practise that manage the process of developing, acquiring, implementing, and maintaining computerized information systems and associated technology. Show
System development methodologies are promoted in order to improve the management and control of the software development process, structuring and simplifying the procedure, and standardizing the development process and product by stipulating actions to be done and methods to be used. It is often implicitly presumed that the use of a system development methodology will increase system development output and excellence. System Development Management Life-cycleIt is maintained in management studies that effectual way to protect information and information systems is to incorporate security into every step of the system development process, from the initiation of a project to develop a system to its disposition. The manifold process that begins with the initiation, analysis, design, and implementation, and continues through the maintenance and disposal of the system, is called the System Development Life Cycle (SDLC). Walsham (1993) stated that system development life cycle is an approach to developing an information system or software product that is characterized by a linear sequence of steps that progress from start to finish without revisiting any previous step. It is one of the oldest systems development models and is commonly used (Walsham, 1993). According to Dennis, Wixom, and Tegarden(2009) �the systems development life cycle is the process of understanding how an information system (IS) can support business needs by designing a system, building it, and delivering it to users� . The SDLC model is basically a project management device that is used to plan, execute, and control systems development projects (Whitten and Bentley, 1998). System development life cycles are usually deliberated in terms of the conventional development using the waterfall model or the prototyping development spiral model. Major objectives of systems development lifecycle are to ensure that high quality systems are delivered, provide strong management controls over the projects, and maximize the productivity of the systems staff. In order to fulfil these objectives, the systems development lifecycle has many specific requirements that include being able to support projects and systems of various scopes and types, supporting all of the technical activities, supporting all of the management activities, being highly usable, and providing guidance on how to install it. Phases of System DevelopmentA system development project comprises of numerous phases, such as feasibility analysis, requirements analysis, software design, software coding, testing and debugging, installation and maintenance.
phases of the system development cycle Whitten and Bentley
(1998) recommended following categories of system development project lifecycle:
There are many different SDLC models and methodologies, but each usually consists of a series of defined steps such as Fountain, Spiral, rapid prototyping, for any SDLC model that is used, information security must be integrated into the SDLC to ensure appropriate protection for the information that the system will transmit, process, and store. System development life-cycle models (Source: Conrick, 2006))
Waterfall ModelThe Waterfall Model signifies a traditional type of system development project lifecycle. It builds upon the basic steps associated with system development project lifecycle and uses a top-down development cycle in completing the system. Walsham (1993) outlined the steps in the Waterfall Model which are as under:
the model's development schedule Fountain model: The Fountain model is a logical enhancement to the Waterfall model. This model allows for the advancement from various stages of software development regardless of whether or not enough tasks have been completed to reach it. Prototyping Model: The prototyping paradigm starts with collecting the requirements. Developer and customer meet and define the overall objectives for the software, identify whatever requirements are known, and outline areas where further definition is mandatory. The prototype is appraised by the customer/user and used to improve requirements for the software to be developed. Iteration occurs as the prototype is tuned to satisfy the needs of the customer, while at the same time enabling the developer to better understand what needs to be done. Major Advantages of this Model include
Main drawbacks of this model are that Prototyping is typically done at the cost of the developer. So it should be done using nominal resources. It can be done using Rapid Application Development tools. Sometimes the start-up cost of building the development team, focused on making the prototype is high. Once developers get proper requirements from client after showing prototype model, it may be useless. It is a slow process and too much involvement of client is not always favoured by the creator. Figure: different phases of Prototyping model Uses of prototyping:
Rapid Application DevelopmentThis model is based on prototyping and iterative development with no detailed planning involved. The process of writing the software itself involves the planning required for developing the product. Rapid Application development focuses on gathering customer requirements through workshops or focus groups, early testing of the prototypes by the customer using iterative concept, reuse of the existing prototypes (components), continuous integration and rapid delivery. There are three main phases to Rapid Application Development:
RAD Model RAD is used when the team includes programmers and analysts who are experienced with it, there are pressing reasons for speeding up application development, the project involves a novel ecommerce application and needs quick results and users are sophisticated and highly engaged with the goals of the company. Spiral Model: The spiral model was developed by Barry Boehm in 1988 (Boehm, 1986). This model is developed to Spiral Model to address the inadequacies of the Waterfall Model. Boehm stated that “the major distinguishing feature of the Spiral Model is that it creates a risk-driven approach to the software process rather than a primarily document-driven or code-driven process. It incorporates many of the strengths of other models and resolves many of their difficulties" (1988). A Spiral Model the first model to elucidate why the iteration matters. Spiral model is an evolutionary software process model which is a grouping of an iterative nature of prototyping and controlled and systematic aspects of traditional waterfall model. As originally proposed, the iterations were usually 6 months to 2 years long. Each phase starts with a design goal and ends with the client reviewing the progress. Analysis and engineering efforts are done at each phase of the project. The spiral model consists of four phases:
Major benefits of this model include:
Main drawbacks of this model are as under:
The spiral model is normally used in huge projects. For example, the military had adopted the spiral model for its Future Combat Systems program. The spiral model may suit small software applications. Phases of spiral model Incremental model: Incremental model is a technique of software development in which the model is analysed, designed, tested, and implemented incrementally. Some benefits of this model are that it handles large projects, it has the functionality of the water fall and the prototyping model. It is easier to manage the project as it is broken down into smaller pieces, changes can be done through the development stages and errors are easy to be identified. Disadvantages of this model are that when remedying a problem in a functional unit, then all the functional units will have to be corrected thus taking a lot of time. It needs good planning and designing. Increment model of SDLC There are numerous benefits of integrating security into the system development life cycle that are as under:
Strengths of System Development Life Cycle
Weaknesses of System Development Life Cycle
To summarize, the systems development life cycle is a theoretical model which is used in project management. It explained various phases involved in an information system development project, from an initial feasibility study through maintenance of the completed application. SDLC system life cycle is a step by step systematic approach from planning to testing and deployment of the project. There are some rudimentary phases that are firmly followed in the order as analysis, designing, coding, testing and implementation. Different SDLC models are used to develop numerous projects. What are the approaches to information system development?An information system development consists of six important stages, it is system survey, needs analysis, design, implementation, testing, change and maintenance.
What is the structured approach called for developing software within an organization?The Software Development Life Cycle (SDLC) is a structured process that enables the production of high-quality, low-cost software, in the shortest possible production time.
What is the structured approach called for developing software and information systems quizlet?The SDLC is a structured step-by-step approach for developing information systems.
What are the two approaches to system development?The predictive approach to the SDLC is used for projects that are well understood and low risk. The adaptive approach to the SDLC is used for projects that are not well understood and are higher risk. Adaptive SDLCs are more iterative and allow the project team to adapt the project to changing circumstances.
|