DEFINING THE SYSTEM
ARCHITECTURE
WEEK 2 - SESSION 3 – 4
ISYS6843003 - ADVANCED INFORMATION SYSTEM ANALYSIS AND DESIGN
SUBJECT MATTER EXPERT
Ferdianto, S.Kon, M.MSI
Chapter 6
Systems Analysis and Design in a Changing World, 7th Ed - Chapter 7
©2016. Cengage Learning. All rights reserved.
OUTLINE
• Anatomy of a Modern Information System
• Architectural Concepts
• Interoperability
• Architectural Diagrams
• Describing the Environment
• Designing Application Components
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
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
ACTIVITIES OF “DESIGN SYSTEM COMPONENTS”
ANATOMY OF A MODERN
INFORMATION SYSTEM
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…
SIMPLIFIED ARCHITECTURE FOR APPLICATION (AMAZON.COM)
SERVER FARM
• Very large databases and very high use
ANATOMY - NETWORKS
• 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
ANATOMY - NETWORKS
• Uniform Resource Locator (URL)
• The identifier for the Web to locate a particular resource
• Hyperlink –
• The URL of a resource embedded within another resource
ANATOMY - SOFTWARE
• 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
ANATOMY - SOFTWARE
ANATOMY - SOFTWARE
• 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
ANATOMY - SOFTWARE
• 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
ANATOMY – SOFTWARE AND PROTOCOLS
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
• HTTP (hypertext transfer protocol)
• Defines format and content for transfer of Web documents
• HTTPS (hypertext transfer protocol secure)
• Encrypted and secure http transfers
ARCHITECTURAL CONCEPTS
ARCHITECTURAL CONCEPTS
• Technology architecture
• Computers, network computers and hardware, and system software
• Application architecture
• The software programs and their configuration
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
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
DISTRIBUTED ARCHITECTURES
• Client/Server architecture
• Software design with part of the application on a server and part on the client
DISTRIBUTED ARCHITECTURES
• Three-Layer architecture
• Client/server architecture with application divided into view layer, logic layer, and data
layer
• View layer – the user interface
• logic layer – program logic to implement the functions
• data layer – the functions to access the data
THREE LAYER ARCHITECTURE
INTEROPERABILITY
INTEROPERABILITY
• The ability of an application to interact with other software
• 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
ARCHITECTURAL DIAGRAMS
DIAGRAMS FOR SYSTEM ARCHITECTURES
• Location Diagrams
• Identify geographical placement of hardware,
software, and users
DIAGRAMS FOR SYSTEM ARCHITECTURE
• Network Diagrams
• How the application software is deployed across the hardware and system software
DIAGRAMS FOR SYSTEM ARCHITECTURE
• Deployment Diagrams
• How the components of a network are interconnected
DESCRIBING THE ENVIRONMENT
DESCRIBING THE ENVIRONMENT
• 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
DESCRIBING THE ENVIRONMENT
• 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
RMO ENVIRONMENT – EXISTING
• Current environment prior to new development
RMO ENVIRONMENT – PROPOSED
• More mobile devices and apps
• Web application software and content
• Social networking applications
• Security issues
• External hosting of portions
RMO ENVIRONMENT – PROPOSED
DESIGNING APPLICATION
COMPONENTS
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
RMO CSMS APPLICATION ARCHITECTURE
• Grouping by customer actor – part 1
RMO CSMS APPLICATION ARCHITECTURE
• Grouping by customer actor – part 2
RMO CSMS DEPLOYMENT DIAGRAM
• Three-layer design with user components grouped by user functions
RMO CSMS COMPONENT INTEGRATION
• Subsystem integration and data flows
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
SUMMARY
• 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
SUMMARY (CONT)
• Interoperability
• Getting all the components to work together
• Architectural diagrams
• Location diagrams
• Network diagrams
• Deployment diagrams
SUMMARY (CONT)
• 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
FINISH
