2 (40 Points) Software Design Specification You are going to develop a software

Question

2 (40 Points) Software Design Specification You are going to develop a software application for administering the lending of books at a public library in San Antonio. A person must be a member of the San Antonio's library and must be in good standing that is, not any any outstanding fines or overdue books-to borrow books. A book may be borrowed up to three weeks at a time. A book loan may be renewed if the book is returned before the loan's due date and if no other library member has requested the book. If a book is returned after the loan's due date, the borrower will be charged a fine of half a dollar for each late day. Fines are paid to the library staff at the circulation desk, where books are returned. A library member can use any computer to log on to the system by entering his or her user ID and password, to search for books, to request to reserve books, and to renew book loans. The system will authenticate the member and check his or her standing before processing book search, book reservation, and book renewals. 2.1 (15 Points) Suppose you are going to use layered style of architecture to design the library system. Provide an architecture design diagram for the library system to show the layers and the communications among layers. Name each layer and the sub-components in each layer

Explanation / Answer

2.2)Answer:

Layered architecture is suitable for developing library systems.The online Library System is a client-server based system, which contains the following layers: user interface, internet/LAN communication, functional service, and data storage layers.

The most common architecture pattern is the layered architecture pattern, otherwise known as the n-tier architecture pattern. This pattern is the de facto standard for most Java EE applications and therefore is widely known by most architects, designers, and developers. The layered architecture pattern closely matches the traditional IT communication and organizational structures found in most companies, making it a natural choice for most business application development efforts.

omponents within the layered architecture pattern are organized into horizontal layers, each layer performing a specific role within the application (e.g., presentation logic or business logic). Although the layered architecture pattern does not specify the number and types of layers that must exist in the pattern, most layered architectures consist of four standard layers: presentation, business, persistence, and database). In some cases, the business layer and persistence layer are combined into a single business layer, particularly when the persistence logic (e.g., SQL or HSQL) is embedded within the business layer components. Thus, smaller applications may have only three layers, whereas larger and more complex business applications may contain five or more layers.

->Each layer of the layered architecture pattern has a specific role and responsibility within the application. For example, a presentation layer would be responsible for handling all user interface and browser communication logic, whereas a business layer would be responsible for executing specific business rules associated with the request. Each layer in the architecture forms an abstraction around the work that needs to be done to satisfy a particular business request. For example, the presentation layer doesn’t need to know or worry about how to get customer data; it only needs to display that information on a screen in particular format. Similarly, the business layer doesn’t need to be concerned about how to format customer data for display on a screen or even where the customer data is coming from; it only needs to get the data from the persistence layer, perform business logic against the data (e.g., calculate values or aggregate data), and pass that information up to the presentation layer.

->One of the powerful features of the layered architecture pattern is the separation of concerns among components. Components within a specific layer deal only with logic that pertains to that layer. For example, components in the presentation layer deal only with presentation logic, whereas components residing in the business layer deal only with business logic. This type of component classification makes it easy to build effective roles and responsibility models into your architecture, and also makes it easy to develop, test, govern, and maintain applications using this architecture pattern due to well-defined component interfaces and limited component scope.

Related Questions

Navigate

• Browse (All)
• Browse 2
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.