Architectural Design .1 Criteria THE RESULT AND THE EXPLANATION

4.4 Architectural Design 4.4.1 Criteria The architectural design of the dictionary application system represents a specific way of prioritizing design criteria. In this system, usable is the very important criteria. Maintainable and correctness also had high priority. Because the system was designed for interactive application, system will use the localhost in running website. Table 4.4 The priority of design criteria Criteria Very Important Important Less Important Irrele vant Easily Fullfield Usable √ Secure √ Efficient √ Correct √ Reliable √ Maintainable √ Testable √ Flexible √ Comprehensible √ Reuseable √ Portable √ Having considered the general object-oriented criteria and the specific condition, writer now can prioritize which criteria should govern design activity. Explanation: a. Usable, usefulness of the proposed system in accordance with problem. b. Secure, secure from unauthorized access. c. Efficient, efficiency from economic exploitation point of view. d. Correct, fulfilled the customer needs. e. Reliable, fulfilment of the results from the existing functions. f. Maintainable, the allocation of costs and repair a broken system. g. Testable, can be ascertained that the system developed according to the function. h. Flexible, ease of system modification. i. Comprehensible, effort required to obtain a clear understanding of the system. j. Reusable, The potential use of the system for other systems. k. Portable, can run the system in any platforms.

4.4.2 Components Architecture

Component architecture that the writer used is distributed data architecture, it’s based on attribute functionality and client has user interface, function and model. Figure 4.29 Component Architecture for dictionary application. Writer have the component “User interface”, which is responsible for searching, updating, translating, that let users interact with the system. The component “Functions” is responsible for providing system functionality. Functionality is provided to “User interface” as a set of operations on public classes.

4.4.3 Deployment Diagram

Deployment diagram using a centralized pattern, where user only handled the user interface. All request are implemented in user interface except update request. for update, user call to the server, where the server responds by carrying out the relevant function on model and all functionality reside on the server, and the users basically act like simple data storage. Figure 4.30 Deployment Diagram

4.5 Component Design