Review of the Different Types of SDLCs

Review of the Different Types of SDLCs - Review of the...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
Review of the Different Types of SDLCs Overview of the Systems Development Process | The V-Model of Systems Development | Types of Information Systems | Developing Information Systems and the SDLC | Structured SDLC Models | Alternative Approaches to Improving Development | | Object Oriented Analysis and Design | Agile Methodologies | Study Tools Creating a new information system for a business is a major project. Often, millions of dollars and months or even years of effort by dozens or sometimes hundreds of people will be invested in such a project. Sometimes, the company may buy a ready-made system, rather than develop a new one from scratch. Even so, selecting the right system, adapting it to fit the company's unique needs, and getting it up and running will usually be costly and time- consuming. Projects like these can't be handled lightly. Only a disciplined, organized approach can have a reasonable chance of success. Over the years, information systems experts have defined standard ways to organize and manage the complex process of building or acquiring a new system. These standard approaches are called Systems Development Life Cycle , or SDLC models. As a future business analyst, the SDLC model your organization uses will determine how you do your job and how your work fits together with the work of others in the overall systems development process. This week we will cover TCO 1 - Analysis: Students should be able to identify, explain and analyze the components of the Systems Development Life Cycle. The ability to compare and relate the structured, object oriented, and Agile life cycles is expected. Overview of the Systems Development Process The systems development process can vary greatly, depending on the business organization, the type of system, and the specific project. Nevertheless, there are some common elements that are nearly always important. 1. The process begins when someone makes a formal request to consider developing a new system or to make major changes to an existing system. 2. If the request appears to have merit, it will be assigned to a business analyst (that may be you) who will work with the requester and others to refine the request into a more concrete, well-defined project proposal. 3. The proposal will be considered by management and, if it is approved, the project will be assigned a priority, allocated resources (budget, people, and equipment), and given a schedule. An important part (perhaps the most important part) of any project is determining, in detail, exactly what the new system needs to do. This is called gathering the requirements for the system . Gathering requirements is like deciding where you need to go before you start out on a long trip. Gathering requirements , organizing and understanding them , and writing them down in usable form , are some of the primary responsibilities of the business analyst in the systems development process. After the requirements have been gathered, understood, and documented, the new system can be designed.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page1 / 5

Review of the Different Types of SDLCs - Review of the...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online