Objectives: Introduction Over View of System Analysis and Design



Download 0.94 Mb.
View original pdf
Page137/140
Date13.11.2023
Size0.94 Mb.
#62581
1   ...   132   133   134   135   136   137   138   139   140
ms-04
b. Functionality
It is a definition of the facilities, performance, and other factors that the user requires in the finished product. All such information comes from the user. The following are key questions to consider
1. Do the input transactions, files, and reports contain the necessary data elements
2. Are all the necessary computations and processing performed according to specifications

1. Capacity

ii.Capacity refers to the capability of the software package to handle the user’s requirements for size of files, number of data elements, volume of transactions and reports and number of occurrences of data elements. All limitations should be checked.
Flexibility
It is a measure of the effort required to modify an operational program. One feature of flexibility is adaptability, which is a measure of the ease of extending the product.
Usability
This criterion refers to the effort required to operate, prepare the input, and interpret the output of a program. Additional points to be considered are portability and understandability. Portability refers to the ability of the software to be used on different hardware and operating systems. Understandability means that the purpose of the product is clear to the evaluator and that the package is clearly and simply written, is free of jargon, and contains sufficient references to readily available documents so that the reader can comprehend advance contents.
Security.

It is a measure of the likelihood that a system’s user can accidentally or intentionally access or destroy unauthorized data. A key question is how well can one control access of software or data file Control provides system integrity.

Performance.
It is a measure of the capacity of the software package to do what it is expected to do. This criterion focuses on throughput, or how effectively a package performs under peak loads. Each package should be evaluated for acceptance on the user’s system. The language in which a package is written and the operating system are additional performance considerations. If we plan to modify or extend a package, it is easier if it is written in a language that is commonly known to programmers. Likewise, if the package run only under a disk operating system and the installation is under a full operating system, then either the package will have to be upgraded to the larger operating system or the system downgraded to handle the package as is. In either case, the change could be costly and counterproductive.

Download 0.94 Mb.

Share with your friends:
1   ...   132   133   134   135   136   137   138   139   140




The database is protected by copyright ©ininet.org 2024
send message

    Main page