Objectives: Introduction Over View of System Analysis and Design
What is Requirements Determination
Download 0.94 Mb. View original pdf
|
| 6.2 What is Requirements Determination Requirements determination involves studying the current business system to find out how it works and where improvements should be made. Systems studies result in an evaluation of how current methods are working and whether adjustments are necessary or possible. These studies consider both manual and computer methods, they are not merely computer studies. A requirement is a feature that must be included in anew system. It may include away of capturing or processing data, producing information, controlling a business activity, or supporting management. The determination of requirements thus entails studying the existing system and collecting details about it to find out what these requirements are. Since systems analysts do notwork as managers or employees in user departments (such as marketing, purchasing, manufacturing, or accounting, they do not have the same base of acts and details as the managers and users in those areas. Therefore, an early step in analysts, investigation is to understand the situation. Certain types of requirements are so fundamental as to be common inmost all situations. Developing answers to a specific group of questions (to be discussed in this section) will help you understand these basic depending on whether the system is transaction – or decision – oriented and whether the system cuts across several departments. For example, the need to inform the inventory manager of an unusually large order that is forthcoming underscores the importance of linking the sales, purchasing, and warehouse departments. 6.2.1 Activities in requirement Determination It is helpful to view requirements determination through the three major activities of requirements anticipation, requirements investigation, and requirements specification. 6.2.1.1 Requirements Anticipation Having had experience in a particular business area or having encountered systems in an environment similar to the one currently under investigation will influence systems analysts study. They may foresee the likelihood of certain problems or features and requirements fora new system. As a result, the features they investigate for the current system, questions they raise, or methods employed maybe based on this familiarity. Requirements anticipation can be a mixed blessing. On the one hand, experience form previous studies can lead to investigation of areas that would otherwise go unnoticed by an inexperienced analyst. Having the background to know what to ask or which aspect to investigate can be a substantial benefit to the organization. On the other hand, if a bias is introduced or shortcuts are taken in conducting the investigation, requirements anticipation is a problem. We will point out guidelines for structuring an investigation around basic questions to avoid the undesirable consequences of requirements anticipation. Download 0.94 Mb. Share with your friends:
|