System development methodologies are promoted as a means of improving the management and control of the software development process, structuring and simplifying the process, and standardizing the development process and product by specifying activities to be done and techniques to be used. It is often tacitly assumed that the use of a system development methodology will improve system development productivity and quality. However, there is little empirical evidence to support this assumption. As we know that, Information System (IS) refers to a system of people, data records and activities that process the data and information in an organization, and it is includes the organization's manual and also the automated processes. Here all the development of IS are referring to the useful of standard selection of system development methodology. There are various types of information systems which successful implementation for the end users, for example: transaction processing systems, decision support systems, knowledge management systems, database management systems, registration system, payroll system, inventory system and office information systems. There are numerous types of system development methodologies such as AGILE, System Development Life Cycle (SDLC), Prototyping, Rapid Application Development (RAD), Joint Application Development (JAD), Computer Aided Software Engineering (CASE), Object Oriented or others.
System Development Life Cycle (SDLC)
SDLC stands for Software Development Life Cycle. A Software Development Life Cycle is essentially a series of steps, or phases, that provide a model for the development and lifecycle management of an application or piece of software. The methodology within the SDLC process can vary across industries and organizations, but standards such as ISO/IEC 12207 represent processes that establish a lifecycle for software, and provide a mode for the development, acquisition, and configuration of software systems. The intent of a SDLC process it to help produce a product that is cost-efficient, effective, and of high quality. Once an application is created, the SDLC maps the proper deployment and decommissioning of the software once it becomes a legacy. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release, and maintenance (response).
SDLC can be defined as the conceptual process of developing, maintaining or altering an information system from the time that the project is started through maintenance of the completed application. The SDLC process applies to the information system. There are many different SDLC models and methodologies, but each generally consists of a series of defined steps or phases. 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.
The purpose of SDLC
Systems Development Life Cycle or one of many variations on the name. What most Business Analysts can agree on is that the SDLC is a structured, standardized set of processes for developing and maintaining business solutions through the development life cycle of a project.
Software development efforts go through a series of detailed and iterative processes that are divided into initiation & planning, analysis, design & development and QA testing. These activities are often referred to as the SDLC.
There are many variations to the SDLC but they all share the same core activities:
1. What deliverables must be created? Deliverables or artifacts are items, tasks, documents, modules, etc. that are created for a new project or are the result of an existing project or process. Deliverables will vary in size based on the scope of a project or process. Deliverables must be documented and tracked by the BA during the life cycle of the project.
2. How will the...
Please join StudyMode to read the full document