![]() ![]() ![]() This type of error is common in parameter inter- faces, where parameters may be of the wrong type or be passed in the wrong order, or the wrong number of parameters may be passed. ■ Interface misuse A calling component calls some other component and makes an error in the use of its interface. Some object-oriented sys- tems have this form of interface, as do client-server systems A return message includes the results of executing the service. Message passing interfaces These are interfaces in which one component requests a service from another component by passing a message to it. Objects and reusable components have this form of interface. Procedural interfaces These are interfaces in which one component encapsu- lates a set of procedures that can be called by other components. This type of interface is used in embedded systems, where sensors create data that is retrieved and processed by other system components. Data is placed in the memory by one subsystem and retrieved from there by other subsystems. Shared memory interfaces These are interfaces in which a block of memory is shared between components. Methods in an object have a parameter interface. Parameter interfaces These are interfaces in which data or sometimes function references are passed from one component to another. If a software product or app is very cheap, users may be willing to toler- ate a lower level of reliability.ġ. ![]() In a competitive environment, the company may decide to release a program before it has been fully tested and debugged because it wants to be the first into the market. Marketing environment When a software company brings a system to market, it must take into account competing products, the price that customers are willing to pay for a system, and the required schedule for delivering that system. Consequently, more thorough testing of later versions of the system may be required. However, as a software product becomes more established, users expect it to become more reliable. When a new system is installed, usersmay tolerate failures because the benefits of use outweigh the costs of failure recovery. They are not surprised when their software fails. User expectations Because of their previous experiences with buggy, unreliable software, users sometimes have low expectations of software quality. For example, the level of confidence required for software used to control a safety-critical system is much higher than that required for a demon- strator system that prototypes new product ideas. Software purpose The more critical the software, the more important it is that it is reliable. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |