<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Fundamental Strategies for System Analysis - Slepi.NET</title>
    <link>http://slepi.net/entry/fundamental_strategies_for_system_analysis</link>
    <pubDate>Sat, 11 Oct 2008 18:52:01 -0500</pubDate>
    <description>System Analysis is a phase in SDLC, in which the process of gathering information about the current system (called the As-Is system), identifying and analyzing its strengths and weaknesses, is conducted. Expected deliverable of this analysis phase is a conceptual/logical design of the new system (called the To-Be system) which will be built (in the next phase - design phase) based on the requirements. Note that the term As-Is system here refers to any existing system whether it's computerized or not, thus it's not necessarily be about an installation of software packages or certain computer applications.
SDLC defines three fundamental strategies for system analysis, each strategy is not likely better than others but rather more suitable for certain type of projects or system requirements. It is the responsibility of a System Analyst to choose the most appropriate strategy for the project. All three strategies have the similarity in that they all cover all three processes described above. For a relatively complex system, it is common to complete the process in an iterative manner, going forth and back repeatedly in order to make better analysis.</description>
    <copyright>Copyrights 2008 Wiras Adi</copyright>
    <image>
      <url>http://www.slepi.net/images/slepinet-rss.png</url>
      <title>Fundamental Strategies for System Analysis - Slepi.NET</title>
      <link>http://www.slepi.net</link>
    </image>
  </channel>
</rss>
