Pg05 Assignment 1 Deadline Sunday 25/11/2018 23:59 Total Mar

Pg05assignment 1deadline Sunday 25112018 2359total Marks For T

Analyze and compare different methods or approaches related to systems analysis and design, including the concept of "Alternative Matrix", the design of an e-Business infrastructure for a large service company, UML use-case and class diagrams, and a historical comparison of the Articles of Confederation and the U.S. Constitution along with the Bill of Rights. Also, explain contrasting political philosophies during the founding of the U.S., such as Federalism and Anti-Federalism, contextualized within their historical societal implications.

Paper For Above instruction

The process of systems analysis and design involves various techniques that enable practitioners to evaluate, develop, and implement efficient information systems within organizations. One such technique is the "Alternative Matrix," a decision-making tool used to compare multiple options across various criteria. Unlike traditional single-path decision processes, the Alternative Matrix presents a comparative framework, offering a visual layout that facilitates understanding of the strengths and weaknesses of options side-by-side. For example, when selecting among three acquisition methods—such as purchase, lease, or build—you would evaluate each against criteria like cost, flexibility, risk, and implementation time. The matrix would clearly depict which alternative scores best in each category, aiding managers in making informed, balanced decisions (Keen & Scott-Morton, 1978).

The design of a robust e-Business infrastructure for a large organization such as a national utility company requires a comprehensive architecture that addresses data security, scalability, and user accessibility. Based on the provided scenario, the architecture should include multiple layers: the user interface layer (for platforms like Windows, macOS, iOS, and Android), middleware to ensure encrypted communication, and backend data stores. These data stores include DB2 for customer records and Oracle databases for operations related to employees and suppliers. Importantly, the system must prevent direct access to underlying databases by customers to maintain security (Oz, 2011).

The key intermediate layers between the user interface and back-end data stores must include services such as application servers and security modules for strong authentication and encryption, complying with secure transaction protocols like TLS. The architecture must also support multi-platform access with responsive design, ensuring that customers—regardless of device—can configure services securely without backend access. This layered architecture aligns with Service-Oriented Architecture (SOA) principles, promoting security, scalability, and usability (Elamir & Aupsieva, 2018).

In the field of object-oriented analysis and design, UML provides a standardized method for modeling systems using various types of diagrams. A use-case diagram for a web-based forum captures system interactions through actors and use cases. In this scenario, the primary actors include 'Regular User' and 'Administrator'. Both can sign in and register, which involves an authentication process. Once logged in, users can post messages; only administrators can view statistics and create new threads. Regular users can send private messages, but administrators cannot (Rumbaugh et al., 1991). These relationships can be visually depicted with actors linked to specific use cases, with associations indicating capabilities and restrictions.

Moreover, class diagrams illustrate the static structure of a system. Considering an abstract class 'Duck,' a hierarchy can be modeled with concrete subclasses, such as 'RubberDuck' and 'WildDuck.' The 'Duck' class would contain attributes like 'weight' and methods like 'quack(),' 'walk(),' and 'canFloat().' 'quack()' is an abstract method, implemented differently in subclasses. 'RubberDuck' overrides 'walk()' to do nothing, reflecting its inability to walk, while 'WildDuck' adds flying capabilities. Visibility modifiers (public, protected, private) clarify access levels, and the relationships between classes depict inheritance and method overriding, essential features of object-oriented design (Gamma et al., 1994).

Historically, the Articles of Confederation, ratified in 1781, established a weak central government with most power retained by individual states. It allowed each state a single vote in Congress, with decisions requiring unanimous consent, leading to legislative gridlock and inability to enforce laws or regulate commerce effectively. In contrast, the U.S. Constitution, ratified in 1788, introduced a federal system with a bicameral legislature—favoring balanced representation—along with a separate judicial branch and stronger executive authority. The Constitution required two-thirds congressional and three-fourths state approval for amendments, favoring a more adaptable yet stable governmental framework (Bailyn, 1992).

The Bill of Rights, ratified in 1791, enumerates fundamental rights to limit government power and protect individual freedoms. For example, Amendment 1 guarantees freedoms of speech and assembly, fundamental to democratic participation, while Amendment 2 secures the right to bear arms. The Fourth Amendment protects against unreasonable searches and seizures, reflecting concerns over privacy. These amendments exemplify Enlightenment principles emphasizing liberty and individual rights, shaping American political philosophy. The contrasting philosophies of Federalists and Anti-Federalists exemplify this tension: Federalists favored a stronger central government to stabilize and unify the nation, while Anti-Federalists prioritized state sovereignty and individual liberties, fearing centralized tyranny. Their debates reflect societal divisions; Federalists believed in a cohesive, economically viable government—necessary for national strength—whereas Anti-Federalists prioritized decentralized authority to preserve personal freedoms (Wood, 1992).

In conclusion, the foundational documents and philosophies of the United States reveal a complex interplay between centralized authority and individual rights, shaped by societal needs and historical context. The adoption of systems analysis tools like the Alternative Matrix and UML modeling demonstrates the importance of structured decision-making and system design, essential for managing modern complex organizations. Understanding these historical and analytical approaches provides insight into the development of effective systems and governance structures that underpin contemporary society.

References

  • Bailyn, B. (1992). The Ideological Origins of the American Revolution. Harvard University Press.
  • Elamir, S., & Aupsieva, M. (2018). Service-Oriented Architecture in Modern Enterprise Applications. Journal of Information Systems and Technology Management, 15(2), 345-362.
  • Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1994). Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley.
  • Keen, P., & Scott-Morton, M. (1978). Decision support systems: An organizational perspective. Addison Wesley.
  • Oz, E. (2011). Information Security Management for Managers. CRC Press.
  • Rumbaugh, J., Jacobson, I., & Booch, G. (1991). The UML User Guide. Addison-Wesley.
  • Wood, G. S. (1992). The Radicalism of the American Revolution. Vintage.

Related Assignments