BUS 630 ANALYSIS OF THE CURRENT SYSTEM

Part II ANALYSIS OF THE CURRENT SYSTEM Performance Analysis Transaction: Throughput: Response Time: Anticipated Growth: Problem: Cause: Effect: Opportunity: Benefit: Constraint: Possible Improvements: Information and Data Analysis The outputs are listed and identified as follows: Output: Format: Frequency: Problem: Cause: Effect: Opportunity: Benefit: Constraint: Possible Improvements: Data Analysis. Data analysis describes the degree to which data is redundantly stored within the system, the ease (or lack thereof) of access to data (e.g. how easy or difficult it is to produce information and outputs from the data), and the accuracy and consistency of stored data. The stored data are listed and identified as follows. Data Stored: Number of records: Anticipated growth: Medium: Organization: Problem: Cause: Effect: Opportunity: Benefit: Constraint: Possible Improvements: Economic Analysis Economic analysis examines the system for cost problems (e.g. excessive costs or insufficient cost controls) or cost reduction opportunities. It can also be used to present budget constraints. . Problem: Cause: Effect: Opportunity: Benefit: Constraint: Possible Improvements: Control and Security Analysis Controls analysis examines how the system ensures that it is properly operating. Security analysis is concerned with both facility and data security. The system was examined both for excessive controls and lack of controls. Controls are measures taken to eliminate mistakes and tampering. Controls can also have performance implications. Problem: Cause: Effect: Opportunity: Benefit: Constraint: Possible Improvements: Efficiency Analysis Efficiency analysis is sometimes confused with economic analysis. Efficiency analysis examines the system for problems and opportunities related to how resources (e.g. people, facilities, money, etc.) are being used. Efficiency problems and opportunities usually target resources that could be better used (not eliminated). Problem: Cause: Effect: Opportunity: Benefit: Constraint: Possible Improvements: Service Analysis Service analysis takes on several forms. The following list is not exhaustive: Processing and data accuracy (manual and computer). Especially for computerized systems, is data being properly edited prior to file updates? Reliability of the system. Are transactions and situations handled consistently? Recoverability of the system. Especially for computerized systems, is data being periodically backed up? Maintainability of the system. Especially for computerized systems, has the system been properly maintained? Can it be maintained? How good is the documentation? Ease of use. For both computerized and manual systems or subsystems, is the system easy to learn and use? Flexibility. Are the situations or conditions that the system cannot handle? Coordination. Do the people in the system appear to coordinate their activities? Do actions or decisions ever contradict? Do people understand how their fellow workers interface to their jobs? Customer and/or employee goodwill or morale. Problem: Cause: Effect: Opportunity: Benefit: Constraint: Possible Improvements: describe possible solutions to problems or ways to fulfill opportunity> Miscellaneous Analysis Part III RECOMMENDATIONS Recommendations and Proposal < This section should include: Facts about the business requirements Define the document and data storage for the new system Define and document essential inputs needed for an improved system Define and document essential outputs needed for an improved system Define and document the business processes for an improved system Define and document the geographic support requirements for an improved system Develop a comprehensive business requirements statement that will guide the future project phase.> Schedule for Completion of Definition Phase <(GANTT charts.)> Conclusion Briefly describe your findings, usually to confirm that the problems and opportunities are worthy of solution.>