Chapter 7 Systems Analysis And Design PDF

Chapter 7 Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 1  Defining the System Architecture Chapter 7 Systems Analysis and Design in a Changing Wor...

Chapter 7 Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 1  Defining the System Architecture Chapter 7 Systems Analysis and Design in a Changing World 7th Ed Satzinger, Jackson & Burd Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 2  Chapter 7: Outline Anatomy of a Modern Information System Architectural Concepts Interoperability Architectural Diagrams Describing the Environment Designing Application Components Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 3  Learning Objectives Explain architectural concepts that influence system design, including ubiquitous computing and software, components, protocols, interoperability, and distributed architectures Describe and draw location, network, and deployment diagrams Describe a system’s environment by drawing architectural diagrams and answering key questions Design larger application components based on use cases and other analysis models Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 4  Overview An important part of new system development is choosing appropriate technologies Explain and provide a summary of technology and architectural concepts describe the details for the activity – Describe the Environment Describe the details for the activity – Design the application components Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 5  Activities of “Design System Components” Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 6  Anatomy of a Modern System – Computing Devices Server – manages shared resources and enables users and other computers access to these resources Personal computing devices or clients Desktops, laptops, tablets, smartphones… Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 7  Simplified architecture for application (Amazon.com) Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 8  Anatomy - Networks (1 of 2) Computer network – hardware, software, transmission media Internet backbone – High-capacity with high-bandwidth trunk lines and large high-speed computers Owned by governments and telecom companies Local area network (LAN) – Small network for a single site World Wide Web (WWW) All the interconnected resources accessed through the Internet Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 9  Anatomy - Networks (2 of 2) Uniform Resource Locator (URL) The identifier for the Web to locate a particular resource Hyperlink – The URL of a resource embedded within another resource Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 10  Anatomy – Software (1 of 3) Application software – programs that perform work for users Either a custom app or a Web-based application App – A custom program usually for a laptop or smartphone System Software – Behind the scene software, works as glue to hold everything together Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 11  Anatomy – Software (2 of 3) Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 12  Anatomy – Software (3 of 3) Web-Based Applications Uses a web browser Accessed through a URL Resides on a Web server Uses standard IP protocols Embedded Software Software apps or functions embedded within another app, such as within a browser or O/S Toolbars, Plug-ins, Widgets Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 13  Anatomy – Protocols Protocol A set of languages and rules to ensure communication and data exchange between hardware and software Network protocols Virtual Private Network (VPN) Creates a private network but on the Internet by using secure technologies and encryption Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 14  Anatomy – Software and Protocols Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 15  Anatomy – Web Protocols HTML (hypertext markup language) Protocol for the structure and content of a Web page XML (extensible markup language) An extensions of HTML that enables defining semantics of tags XML tags gain their semantics through meaningful naming, hierarchical structure, contextual relationships and data provided by attributes HTTP (hypertext transfer protocol) Defines format and content for transfer of Web documents between web clients and servers The mechanism by which web resources are requested and delivered over a network Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 16  It contains several methods also known as verbs that performs actions. Some of the most Common methods include: GET: Retrieve data or a resource POST: Submit data to a server PUT : Update or Replace a resource DELETE: Remove a resource HEAD: Retrieve headers only (no body content) Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 17  HTTPS (hypertext transfer protocol secure) Encrypted and secure http transfers It uses SSL/TLS encryption to protect data during transmission ensuring, confidentiality, integrity, and authentication (CIA trade) Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 18  Architectural Concepts It refers to the frameworks, tools, principles, and patterns used to design, develop, and manage applications and their underlying infrastructure It insures that the applications are scalable, secure, maintainable, and aligned with the business needs. Technology architecture Focuses on the underlying infrastructure that supports the application Includes HW, SW, networks, and integration systems Includes physical servers, cloud platforms and storage systems , virtualization , networking, security layers Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 19  Application architecture It defines the structure, components, and interactions of an application ensuring it meets functional and non-functional requirements Key elements include frontend, backend, APIs, and databases relational and NoSql When designing an application the technology and applications architecture must complement each other The technology architecture provides the infrastructure and tools, while the application architecture defines how the application is structured and interacts with the infrastructure Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 20  Software as a Service (SaaS) SaaS No software is installed on the user’s device Application services is accessed remotely User data is isolated and stored on common servers Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 21  Web Services Web service Software function that is executed with Web standards Access via a URL Inputs sent via the URL Executes remotely Data returned within a Web page Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 22  Distributed Architectures Client/Server architecture Software design with part of the application on a server and part on the client Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 23  Distributed Architecture Three-Layer architecture is a design pattern used in software engineering, particularly in distributed systems and web application Each layer serves a specific role, and together they help to manage the system's complexity, improve scalability, and separate concerns. Client/server architecture with application divided into view layer, logic layer, and data layer Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 24  Distributed Architecture View layer – is responsible for presenting the user interface and handling user interactions. It is the layer where users interact with the system. This layer focuses on how information is presented to the user and how input is captured from the user. Responsible for UI, user input handling, and output display logic layer –is where the business logic of the system resides. It is responsible for processing user requests, performing calculations, applying rules, and orchestrating the flow of data between the view and data layers Responsible for business logic, request processing, and data manipulation data layer –is responsible for managing and storing the system's data. It interacts directly with databases or other forms of persistent storage to save, retrieve, and update data. Responsible for Data management, data integrity, and data storage Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 25  Three Layer Architecture Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 26  Interoperability Interoperability The ability of an application to interact with other software The key aspects include technical, Semantic(data exchange consistently), syntactic (format and structure of data consist across systems, and organizational (policies and workflow) Important characteristic in current development projects Understand the environment Reuse software existing components (purchased or in-house) Build components considering interoperability Combine all components into a solution system Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 27  Describing the Environment (1 of 2) Key Questions to help describe accurately What are the key features of existing or new environment O/S, system software, networks, tools What are the external systems or DBMSs What kind of interaction What is the data What are the protocols What kind of security Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 28  Describing the Environment (2 of 2) Key Questions to help describe accurately What devices will be required Protocols for devices Security What APIs What user-interface technology will be used Where and who are users, and what skills What hardware and devices What client O/S will be used Security requirements What APIs are needed Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 29  Designing Application Components Application Component Boundaries Which components perform which functions How to group functions to build components Actors – what functions to particular actors use Shared data – what functions use the same data Events – what functions occur in common business events Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 30  RMO CSMS Application Architecture (1 of 3) Grouping by customer actor – part 1 Use case User/actor Domain class(es) Event(s) Group ProductItem, InventoryItem, Customer request while shopping by Create phone sale Phone sales representative A saleItem, Sale, SaleTrans phone ProductItem, InventoryItem, Customer request while shopping in Create store sale Store sales representative B saleItem, Sale, SaleTrans store Create/update Customer, phone or store sales Customer request or sale to a new Customer, Account, Address C customer account representative customer ProductItem, InventoryItem, Shipping, customer, management, Customer, representative, shipping, or Look up order status SaleItem, Sale, SaleTrans, Shipment, C phone or store sales representative management request ReturnItem Shipping, customer, management, Customer, representative, shipping, or Track shipment Shipment, Shipper, SaleItem C phone or store sales representative management request Customer, phone or store sales Create item return SaleItem, ReturnItem Customer requests return C representative Customer, phone or store sales Customer request while shopping Search for item ProductItem C representative online, by phone, or in store View product Customer, phone or store sales Customer request while shopping ProductItem, ProductComment C comments and ratings representative online, by phone, or in store View accessory Customer, phone or store sales Customer request while shopping ProductItem, AccessoryPackage C combinations representative online, by phone, or in store Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 31  RMO CSMS Application Architecture (2 of 3) Grouping by customer actor – part 2 Use case User/actor Domain class(es) Event(s) Group ProductItem, InventoryItem, Customer request usually after sale Fill shopping cart Customer D CartItem, OnlineCart completed ProductItem, InventoryItem, Empty shopping cart Customer Customer request while shopping online D CartItem, OnlineCart ProductItem, InventoryItem, Check out shopping Customer CartItem, OnlineCart, saleItem, Sale, Customer request while shopping online D cart SaleTrans ProductItem, InventoryItem, Fill reserve cart Customer Customer request while shopping online D CartItem, OnlineCart ProductItem, InventoryItem, Empty reserve cart Customer Customer request while shopping online D CartItem, OnlineCart ProductItem, InventoryItem, Convert reserve cart Customer Customer request while shopping online D CartItem, OnlineCart Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 32  RMO CSMS Application Architecture (3 of 3) Grouping by customer actor – part 2 Use case User/actor Domain class(es) Event(s) Group Customer, ProductComment, Customer request usually after sale Rate and comment on product Customer E ProductItem completed Customer request while shopping Provide suggestion Customer Customer, Suggestion E online Customer request while shopping Send message Customer Customer, Message E online Customer request while shopping Browse messages Customer Customer, Message E online Customer request while shopping Request friend linkup Customer Customer, FriendLink E online Customer request while shopping Reply to linkup request Customer Customer, FriendLink E online Customer, CustPartnerCredit, Customer request while shopping Send/receive partner credits Customer E PromoPartner online Customer request while shopping View ”mountain bucks” Customer Customer, Sale E online Customer request while shopping Transfer ”mountain bucks” Customer Customer, Sale E online Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 33  RMO CSMS Deployment Diagram Three-layer design with user components grouped by user functions Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 34  RMO CSMS Component Integration Subsystem integration and data flows Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 35  RMO CSMS Data Ownership Who “owns” the data System of record What system is responsible to maintain the data What system has a copy or can access the data Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 36  Summary (1 of 3) Anatomy of a Modern Information System Consist of computing devices, networks, software, and protocols Deployed as stand-alone software, network based, Web based Architectural Concepts SaaS – software as a service Web services Distributed architectures Client/server and three-layer architecture Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 37  Summary (2 of 3) Interoperability Getting all the components to work together Architectural diagrams Location diagrams Network diagrams Deployment diagrams Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 38  Summary (3 of 3) Describing the Environment External systems Technology architecture Key questions requiring answers Designing Application Components Application component boundaries Grouping functions into components System of record – who owns the data Systems Analysis and Design in a Changing World, 7th Edition - Chapter 7 ©2016. Cengage Learning. All rights reserved. 39