Optimization is the process of transforming a piece of code to make more efficient (either in terms of time or space) without changing its output or side-effects. The only difference visible to the code’s user should be that it runs faster and/or consumes less memory. It is really a misnomer that the name implies you are finding an "optimal" solution— in truth, optimization aims to improve, not perfect, the result. Optimization is the field where most compiler research is done today. The tasks of the front-end (scanning, parsing, semantic analysis) are well understood and unoptimized code generation is relatively straightforward. Optimization, on the other hand, still retains a sizable measure of mysticism. High-quality optimization is more of an art than a science. Compilers for mature languages aren’t judged by how well they parse or analyze the code—you just expect it to do it right with a minimum of hassle—but instead by the quality of the object code they produce.
TABLE OF CONTENT
TITLE PAGE
ABSTRACT
ORGANIZATION OF WORK
TABLE OF CONTENT
CHAPTER ONE
1.0 INTRODUCTION
1.1 STATEMENT OF PROBLEM
1.2 AIMS AND OBJECTIVES
1.3 PURPOSE OF STUDY
1.4 SIGNIFICANT OF STUDY
1.5 SCOPE/DELIMITATIONS
1.6 LIMITATIONS/CONSTRAINTS
1.7 ASSUMPTION OF STUDY
1.8 DEFINITION OF TERMS
CHAPTER TWO
2.0 LITERATURE REVIEW
2.0 LITERATURE REVIEW
CHAPTER THREE
3.0 DESCRIPTION AND ANALYSIS OF THE EXISTING SYSTEM
3.1 FACT-FINDING METHOD/ METHODOLOGY
3.2 ORGANISATIONAL STRUCTURE/ORGANOGRAM
3.3 OBJECTIVES OF THE EXISTING SYSTEM
3.4 INPUT, PROCESS, AND OUTPUT ANALYSIS
3.4.1 INPUT ANALYSIS
3.4.2 PROCESS ANALYSIS
3.4.3 OUTPUT ANALYSIS
3.5 INFORMATION FLOW DIAGRAM
3.6 PROBLEMS OF THE EXISTING SYSTEM
3.7 JUSTIFICATION OF THE NEW SYSTEM
3.0 DESCRIPTION AND ANALYSIS OF THE EXISTING SYSTEM
3.1 FACT-FINDING METHOD/ METHODOLOGY
3.2 ORGANISATIONAL STRUCTURE/ORGANOGRAM
3.3 OBJECTIVES OF THE EXISTING SYSTEM
3.4 INPUT, PROCESS, AND OUTPUT ANALYSIS
3.4.1 INPUT ANALYSIS
3.4.2 PROCESS ANALYSIS
3.4.3 OUTPUT ANALYSIS
3.5 INFORMATION FLOW DIAGRAM
3.6 PROBLEMS OF THE EXISTING SYSTEM
3.7 JUSTIFICATION OF THE NEW SYSTEM
CHAPTER FOUR
4.0 DESIGN OF THE NEW SYSTEM
4.1 DESIGN STANDARD
4.2 OUTPUT SPECIFICATION AND DESIGN
4.3 INPUT SPECIFICATION AND DESIGN
4.3.1 FILE DESIGN
4.4 PROCEDURE CHART
4.5 SYSTEMS FLOWCHART
4.6 SYSTEM REQUIREMENTS
4.0 DESIGN OF THE NEW SYSTEM
4.1 DESIGN STANDARD
4.2 OUTPUT SPECIFICATION AND DESIGN
4.3 INPUT SPECIFICATION AND DESIGN
4.3.1 FILE DESIGN
4.4 PROCEDURE CHART
4.5 SYSTEMS FLOWCHART
4.6 SYSTEM REQUIREMENTS
4.6.1 HARDWARE REQUIREMENTS
4.6.2 SOFTWARE REQUIREMENTS
4.6.3 OPERATIONAL REQUIREMENTS
4.6.4 PERSONNEL REQUIREMENTS
4.7 IMPLEMENTATION
4.8 DESIGN STANDARD
4.2 PROGRAM DESIGN
4.2.1 PROGRAM FLOWCHART
4.2.2 PSEUDO CODE
4.3 CODING
4.4 TEST DATA/TEST RUN
4.5 USER TRAINING – AN OVERVIEW
4.6 CUTOVER PROCESS
4.0 DOCUMENTATION
4.1 THE USER DOCUMENTATION
4.2 THE PROGRAMMER DOCUMENTATION
4.7 IMPLEMENTATION
4.8 DESIGN STANDARD
4.2 PROGRAM DESIGN
4.2.1 PROGRAM FLOWCHART
4.2.2 PSEUDO CODE
4.3 CODING
4.4 TEST DATA/TEST RUN
4.5 USER TRAINING – AN OVERVIEW
4.6 CUTOVER PROCESS
4.0 DOCUMENTATION
4.1 THE USER DOCUMENTATION
4.2 THE PROGRAMMER DOCUMENTATION
CHAPTER FIVE
RECOMMENDATIONS, SUMMARY AND CONCLUSION
5.1 RECOMMENDATION
5.2 SUMMARY
5.3 CONCLUSION
REFERENCES
SOURCE LISTING
LIST OF FIGURES
RECOMMENDATIONS, SUMMARY AND CONCLUSION
5.1 RECOMMENDATION
5.2 SUMMARY
5.3 CONCLUSION
REFERENCES
SOURCE LISTING
LIST OF FIGURES
