Objectives: Introduction Over View of System Analysis and Design
Download 0.94 Mb. View original pdf
|
- Navigate this page:
- 6.2.7 User transaction Requirements
- 6.2.8 User decision Requirements
| 6.2.6 Identity controls In business situations that are well controlled either by management or process monitoring, determining whether an activity has been performed properly maybe no problem. But during the analysis stage, the analysts must examine control methods are there specific performance standards Who compares performance against standards How are mistakes caught How are error handled Are the errors excessive Weak or missing controls area an important discovery in any system investigation. In the vignette the beginning of this chapter, the failure of the two junior systems analyst to give proper attention to weak or mission controls when they studied receiving room activities had serious consequences. 6.2.7 User transaction Requirements Transaction – level systems captures, process, and store data fora reason. In an order system, for example, sale order form customers are processed so that specified item can be shipped. This simple procedure applies to every order that is received. Analysis’s assigned to work on an order entry system would want to know more about how these transactions are processed. To understand these transaction requirements they would undoubtedly ask questions such as the following What makes up the transaction being processed What initiates the transaction Who actually initiates the order For what purpose How often do order occur What volume is associated with each Are there different conditions that can affect how orders are processed What details are needed to process the transaction What information is generated What data is stored 6.2.8 User decision Requirements Decision, unlike transaction activities, may not follow a specific procedure. Routines are not as clear – cut, and controls maybe very vague. Decisions are made by integrating information in such away that managers can know what actions to take. Decision systems may focus on the past, the present, or the future. Some may support recurring decisions (such as merchandise pricing, while other are unique and do not recur such as the merger example used earlier. They may used data that originate inside the firm, such as through transaction processing, or outside, for example form trade associations or commercial sources (such as marketing research firms who sell information to organizations. In some cases, transaction data are processed to provide new information for decision making. For instance, summarized sales transaction data tell managers which products sell and which do not. Analysts investigating decision support systems should raise the same questions about timing and frequency discussed previously. But other questions should also be posed to determine decision requirements 1. What information is used to make the Decision 2. What is the source of the information Which transaction system produce the data used in the decision process Which data are required but do not result from processing transactions Which data originate from sources outside the organization 3. How would data be processed to produce the necessary information 4. How should the information be presented These questions also point out the relationship between transaction and decision systems. If transaction systems do not capture and store the data needed for decision, important information will be unavailable. Inventory systems capture details about ongoing ordering, receipt, sale, and shipment of items, the data they store are further processed to produce information periodically to analyze sales, determine pricing policy, or decide on marketing plan for product lines. This means (1) that analysts investigating decision systems must be aware of supporting transaction systems and (2) that effective decision systems require suitable transaction processing procedures to be place first. Download 0.94 Mb. Share with your friends:
|