1. Scalability is one of the quality attributes of a software system. Explain five tactics of scalability of the hospital information system. You should provide a detailed critical analysis of your tactics relevant to the hospital information system. [Note: you can formulate your own tactics] 2. With reference to Question 1, identify an architectural pattern which can suit the operation of the hospital. You are expected to write about the identified architectural pattern in the context of the hospital information system. You shall write only ONE architectural pattern. Ideally, the architectural pattern should be compatible with the tactics explained in Question 1.

1. Scalability is one of the quality attributes of a software system. Explain five tactics of scalability of the hospital information system. You should provide a detailed critical analysis of your tactics relevant to the hospital information system. [Note: you can formulate your own tactics] 2. With reference to Question 1, identify an architectural pattern which can suit the operation of the hospital. You are expected to write about the identified architectural pattern in the context of the hospital information system. You shall write only ONE architectural pattern. Ideally, the architectural pattern should be compatible with the tactics explained in Question 1.

Fundamentals of Information Systems

9th Edition

ISBN:9781337097536

Author:Ralph Stair, George Reynolds

Publisher:Ralph Stair, George Reynolds

Chapter8: System Acquisition And Development

Section: Chapter Questions

Problem 3.2CTQ: A safety-critical system is one whose failure or misuse may cause human injury or death. Given that...

See similar textbooks

Similar questions

Software architecture is often compared to the architecture of buildings as a conceptual analogy. In a few statements respond to each one of the following: What are the strong points of that analogy? What is the correspondence in buildings to software architecture structures and views? What is the correspondence in buildings to patterns? What are the weaknesses of the analogy? When does it breakdown?
In the context of the design and development of software, what is the main distinction to be made between cohesion and coupling?
In context of Software Architecture: Consider "Library management System" as your case study, Mention the choice of "architectural pattern" for your case study and justify completely the choice of the pattern.
The primary distinction between a software modelling approach and a software development process is that the latter places greater emphasis on the former. Here, you can see how the two work together to create television of the highest quality. Is it reasonable to discuss a UML model in this context?
What particular goal does the effective application of formal approaches seek to achieve? It is highly advised that at least four justifications for the use of requirements be provided while designing software.
For our case study, we will be the architects assigned the task of constructing the design elements for a system that can be used to manage courses/classes for an organization (Iqra) that specializes in providing training. Let us name the system that we will be designing as the Learning Management System. The organization offers a variety of courses in a variety of areas such as learning management techniques and understanding different software languages and technologies. Each course is made up of a set of topics. Tutors in the organization are assigned courses to teach according to the area that they specialize in and their availability. The organization publishes and maintains a calendar of the different courses and the assigned tutors every year. There is a group of course administrators in the organization who manage the courses including course content, assign courses to tutors, and define the course schedule. The training organization aims to use the Learning Management System…
In the context of the design and development of software, what is the relationship between the concepts of cohesion and coupling?
The flexibility with which object-oriented analysis and design may be employed, for example in the case of system analysis and design, is an additional benefit. Object-oriented analysis and design has numerous advantages, and this is one of them.
In the context of the design and development of software, how do the ideas of cohesion and coupling relate to one another in terms of their respective roles?
Consider the following example: As a software developer, you have been tasked with developing a hospital patient control program. Everything is explained to you right away, and the system requires a high level of dependability. In your perspective, which process model would you propose for this kind of software? In addition to giving compelling reasons in favor of your suggested process model, the description of the recommended process model should be precise and succinct, with the assistance of a visual.
142. Phase that establish design representations that serve as basis for RAD's construction activity is a. communication b. modeling c. planning d. deployment
Consider the following hypothetical situation: As a software developer, you have been tasked with developing a hospital patient control program. Everything is outlined in advance, and the system requires a high level of dependability. Which process model, in your view, would you propose for this kind of software? Along with giving compelling reasons in favor of your suggested process model, the description of the recommended process model should be precise and succinct.