Objectives: Introduction Over View of System Analysis and Design
Download 0.94 Mb. View original pdf
|
- Navigate this page:
- 7.2 Modularization
| 7.1 Introduction: The design translates the system requirements into ways of operationalizing them. The design is a solution, a “ how to “ approach, compared to analysis, a what is orientation. The design phase focuses on the detailed implementation of the system recommended in the feasibility study. Emphasis is on translating performance specifications into design specifications. The design phase is a transition from a user- oriented document to a programmer-oriented document. 7.2 Modularization: One way to plan anew system is to focus on each functional subsystem as a separate entity or application area. Using such an approach, each application area is treated as if it were totally independent. There is minimal sharing of information and systems processes between areas. For example, it two major systems efforts were being simultaneously undertaken. One in the order department & the other in the accounts section. The orders affect the amount of receivables, amount of receivables affect customer’s credit, validate the order and much more. From an applications point of view, the order processing subsystem should be designed to meet accounts receivable functional requirements and vice versa. However, there would be no need to review each application area for common internal processes. Both the systems would be performing certain same steps in each of their systems individually. The modular systems approach divides each application area into a number of smaller units called modules. These modules may apply to a particular application, or they maybe common to two or more application areas. Modules maybe used only once, or they maybe used several times during the processing of an application. Breaking up of a problem into smaller manageable parts is certainly beneficial. The advantages of modularization are- 1. It can speedup the systems process in general & the computer programming function in particular. 2. It eliminates unnecessary duplications. 3. It can result in higher quality because of the concentrated effort devoted to the development of common modules. 4. It provides better control over the total system project, since work can be segmented and assigned in smaller, more controllable units. 5. It more efficiently maintains the system as a correction atone place rectifies the entire problem. 6. It allows flexibility as additional features maybe added later. 7. Small parts of the system can be tested separately. Certainly these factors present a strong argument in favor of the modularization. However there are certain limitations to it as follows- 1. Numerous unique application requirements which must be incorporated in common modules. If a single module is to accommodate all situations, it will become very large & complex. 2. Many systems, changes for particular application areas. Many times a high rate of change means a high rate of potential error. When these changes and errors affect common modules, the negative consequences can be widespread. Modular systems design is best viewed as one aspect of a broader planning issue, but it is not a required step in the design process. The analyst, based upon the in-depth understanding of problem, specifies the level of modularization. Files: The data is stored in files according to user requirements. Some records are processed daily whereas other are updated at random. Depending upon the way the data will be used, the file is organized. Download 0.94 Mb. Share with your friends:
|