Katherine Grace M.

Garcia BAMC 3-1

SDLC is the process of creating or altering systems, and the models and methodologies that people use to develop these systems. Systems Development Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project SDLC according to Elliott & Strachan & Radford (2004), SDLC originated in the 1960s,to develop large scale functional business systems. Maintenance ,investigation, implementation, analysis and design System Investigation First stage of the cycle wherein the system analyst finds the cause/ root of the problem. System Analysis - gathers the requirements for the system - includes a detailed study of the business needs of the organization. System Design - overall plan or model for the system. - Shows how the system will fulfill the plan/objective System Implementation & Maintenance - the designs are translated into code. . In maintenance, system may be revise or modified

System Analysis System Design SYSTEMS ANALYSIS

y

the analysis of the problem that the organization will try to solve with an information system

It consists of: Defining the problem

y y y

Identifying its causes Specifying the solution Identifying the information requirements SYSTEMS ANALYST

y y

Creates a road map of the existing organization and systems, identifying the primary owners and users of data in the organization Describes the existing hardware and software that serve the organization DEFINING THE PROBLEM

y y y

By examining documents, work papers, and procedures Observing system operations Interviewing key users of the systems SPECIFYING THE SOLUTION FEASIBILITY STUDY

y y

Part of the systems analysis process Determines whether that solution is feasible, or achievable, given the organizations resources and constraints 3 AREAS OF FEASIBILITY

y y y

Technical feasibility Economic Feasibility Operational feasibility TECHNICAL FEASIBILITY

Whether the proposed solution can be implemented with the available hardware, software, and technical resources ECONOMIC FEASIBILITY

Whether the benefits of the proposed solution outweigh the costs OPERATIONAL FEASIBILITY

Whether the benefits of the proposed solution is desirable within the existing managerial and organizational framework

SOLUTION ALTERNATIVES
y y y

To do nothing, leaving the existing situation unchanged To modify or enhance existing system To develop a new system INFORMATION REQUIREMENTS

A detailed statement of the information needs that a new system must satisfy; identifies who needs what information, and when, where, and how the information is needed SYSTEMS DESIGN

Details how a system will meet the information requirements as determined by the system analysis INFORMATION SYSTEMS DESIGN

y y

Overall plan or model for that system An exacting and creative task demanding imagination, sensitivity to detail, and expert skills 3 OBJECTIVES

Systems designer is responsible for considering alternative technology configurations for carrying out and developing the system as described by the analyst Designers are responsible for the management and control of the technical realization of systems Designer details the system specifications that will deliver the functions identified during systems analysis y IMPLEMENTATION AND MAINTENANCE y IMPLEMENTATION y "The system or system modifications being installed and made operational in a production environment. The phase is initiated after the system has been tested and accepted by the user. This phase continues until the system is operating in production in accordance with the defined user requirements" (DOJ, 1). y The real code is written here. Involves installing. y MAINTENANCE y It includes all the activity after the installation of software that is performed to keep the system operational. Fixing bugs. y During the maintenance phase of the software life cycle, software programmers regularly issue software patches to address changes in the needs of an organization, to correct issues relating to bugs in the software or to resolve potential security issues. Throughout the maintenance phase, designers address

y y

y y y y y y y y y y y y y

issues that are discovered to prevent any hindrance to the expected performance of the software or to add increased functionality to the software. TYPES OF MAINTENANCE Corrective maintenance: Reactive modification of a software product performed after delivery to correct discovered problems. Corrective dealing with errors found and fixing it Adaptive maintenance: Modification of a software product performed after delivery to keep a software product usable in a changed or changing environment. Adaptive dealing with changes and adapting in the software environment Perfective maintenance: Modification of a software product after delivery to improve performance or maintainability. Perfective accommodating with new or changed user requirements which concern functional enhancements to the software Preventive maintenance: Modification of a software product after delivery to detect and correct latent faults in the software product before they become effective faults. Preventive concerns activities aiming on increasing software maintainability and prevent problems in the future

PROTOTYPING Prototyping Prototyping the process of producing a prototype. Prototype provides the developers and potential users with an idea of how the system in its completed form will function. Types of Prototype Type I prototype eventually becomes the operational system Type II prototype a throwaway model that serves as the blueprint of the operational system Development of Type I Prototype 1. Identify the user needs The system analyst interviews the user to obtain an idea of what is required from the system. 2. Develop a prototype The system analyst, perhaps working with other information analysts, uses one or more prototyping tools to develop a prototype o Integrated application generator is a prewritten software system that is capable of producing all the desired features in the new system (menus, reports, screens, a database, and so on).

Prototyping toolkit includes separate software systems, each capable of producing a portion of the desired system features.

1. Determine if the prototype is acceptable The analyst educates the user in prototype use and provides an opportunity for becoming familiar with the system. The user advises the analyst whether the prototype is satisfactory. If so, step 4 is taken; if not, the prototype is revised by repeating steps 1, 2, and 3 with better understanding of the user needs. 2. Use the prototype The prototype becomes the operational system. The approach is possible only when the prototyping tools enable the prototype to contain all of the essential elements of the new system. Development of Type II Prototype 1. 2. 3. 4. Identify the user needs Develop a prototype Determine if the prototype is acceptable Code the operational system The programmer uses the prototype as the basis for coding the operational system. 5. Test the operational system The programmer test the system. 6. Determine if the operational system is acceptable The user advises the analyst whether the system is acceptable. If so, step 7 is taken; if not, steps 4 and 5 are repeated. 7. Use the operational system The approach is followed when the prototype is intended only to have the appearance of an operational system but not when it is to contain all of the essential elements. Prototyping and the System Development Life Cycle For small-scale systems, prototyping can replace the system development life cycle. However, for large-scale systems or those that affect large organizational units, prototyping is incorporated into SDLC. For example, prototyping can be used in the analysis phase to help users define their information needs and in the design phase to evaluate alternative system configurations. The Attraction of Prototyping
y y y y y

Communications between the systems analyst and user are improved. The analyst can do better job of determining the users needs. The user plays a more active role in system development. The information specialists and the user spend less time and effort in developing the system. Implementation is much easier because the user knows what to expect. Potential Pitfalls of Prototyping

y y y

The haste to deliver the prototype may produce shortcuts in problem definition, alternative evaluation, and documentation. The term quick and dirty has been used to describe some prototyping efforts. The user may get excited about the prototype, thus leading to unrealistic expectations regarding the operational system. Type I prototypes might not be as efficient as systems coded in programming language. The computer-human interface provided by certain prototyping tools may not reflect good design techniques. Applications that are Good Prospects for Prototyping

High risk The problem is not well structured, there is a high rate of change over time, and the data requirements are uncertain.

Considerable user instruction The system features on-line dialogue between the user and a microcomputer or a terminal.
y y y y

A need for quick delivery An expected short use phase for the system An innovative system The system is on the cutting edge, either in the way that it solves the problem or in its use of hardware Unpredictable user behavior The user had no previous experience with such a system. Rapid Application Development RAD (Rapid Application Development) Coined by computer consultant and author James Martin. A methodology that has the same objective of speedy response to user needs as does prototyping but is broader in scope. Refers to a development life cycle intended to produce systems quickly without sacrificing quality. An integrated set of strategies, methodologies, and tools that exists within an overall framework called information engineering. Information Engineering (IE) name that Martin gives to his overall approach to system development, which treats it as firm-wide activity. The term enterprise is used to describe the entire firm. Essential Ingredients of RAD

Management especially top management should be experimenters, who like to do things a new way, or early adapters, who quickly learn how to use new methodologies. Management should be fully supportive of RAD and provide a work environment that makes the activity as enjoyable as possible. People Rather than utilize a single team to perform all the SLC activities, RAD recognizes the efficiencies that can be achieved through the use of several specialized teams. There can be teams for requirement planning, user design, construction, user review and cutover. Members of these teams are masters of the methodologies and tools that are required to perform their specialized tasks. SWAT Martin used this term for skilled with advance tools Methodologies the basic RAD methodology is the RAD life cycle, which consists of four phases: (1) requirements for planning, (2) user design, (3) construction, and, (4) cutover. These phases, like the SDLC, reflect the systems approach. Users play key roles in each phase, participating with information specialist. Tools RAD tools consist mainly of fourth-generation languages and CASE tools that facilitate prototyping and code generation. Fourth-generation languages enable information specialist or users to generate computer code without using a conventional programming language. Examples of fourth-generation languages are Natural, FOCUS, SQL. CASE

y y

y y

Stands for computer-aided software engineering A category of software that has the objective of transferring some of the systems development workload from the human developers to the computer. Categories of CASE

y y y

Upper CASE tool can be used by the firms executives when they engage in strategic planning Middle CASE tool can be used during the analysis and design phases to document the processes and data of both the existing and new system. Lower CASE tool used during the implementation and use phases to help the programmer develop, test, and maintain code. These tools are often referred to as code generators. Integrated CASE tool (ICASE tool) offers the combined coverage of the upper, middle, and lower CASE tools.