Problem anlysis

Introduction: The basic purpose of problem analysis is to get a clear understanding of the clients' and then the information of the users that what is really desired from the software, and what constraints on the solution.  Often customers and users do not understand or know all their needs, because the ability of the new system is not often fully appreciated.  Analysts must ensure that the real needs of the customers and the users are highlighted, even if they do not know them clearly.  That is, the analyst not only collects and organizes information about the organization and its processes, but also acts as an advisor who plays an active role in helping identify the needs of customers and users.  .

  The basic principle used in the analysis is similar to any complex work: split and win.  That is, split the problem into sub-problems and then try to understand every subtype and its connection to other sub-problems in an effort to understand the total problem.  Concepts of state and launch can sometimes be used effectively even in the division process.  A system represents some conditions about a state system.  Often, while using the state, a system is first seen as one of the many potential states, and then a detailed analysis is done for each state.  This approach is sometimes used in real-time software or process-control software.

  Various estimates received are combined to create an analysis for the entire system.  It is often easier to analyze the system from different perspectives, because it limits and scope for study.  In the rest of this section we will discuss some.  Methods of Problem Analysis  As the goal of analysis is to understand the problem domain, an analyst should be familiar with the various ways of analyzing and choose the approach that he thinks is most suitable for problem in hand.




Also read

REQUIREMENT PROCESS

from Technology development http://bit.ly/2VtPG9b