Module 7: System Design and

Architecture
Dr. Eman Nasr
1
Learning Objectives
1. Understand the purpose of the design phase and list design
documents
2. Discuss software acquisition alternatives and select the best
one
3. Describe the basic components and configurations of an IT
system
4. Explain the implications of operational, cultural, political,
and security considerations on system’s design

2
Mapping to the Course
• Feasibility Analysis – Chapter 1
• Managing an IT Project – Chapter 2
Planning

• Requirements Analysis – Chapter 3

• Use Case Analysis – Chapter 4
• Process Analysis/Modeling – Chapter 4
Analysis • Data Analysis/Modeling – Chapter 5

• Physical System Design – Chapter 6

• Architecture Design – Chapter 7
Design • Interface Design – Chapter 8

3
 Moving from Analysis to Design
• Technical details of the system -> how the system to be built
• Create system blueprint that will satisfy system requirements
• Design documents: physical process and data model
• Acquisition of hardware and software needed

* Architecture Design
Functional System Document System
requirements Requirements * H/W & S/W specs Specification
* Interface Design

4
System Acquisition Strategies
Pros Cons
Custom Development
• Custom
Get exactly what we want Requires significant
New system built consistently with existing technology and May add to existing backlogs
standards May require skills we do not have
development Build and retain technical skills and functional knowledge in-
house
Often costs more
Often takes more calendar time

• Purchased Allows team flexibility and creativity

Unique solutions created for strategic advantage
Risk of project failure

package Packages (purchased or obtained from ASP or SaaS)

No need to “reinvent the wheel” for common business needs Rarely a perfect fit
Tested, proven product Organization processes must adapt to software
• Outsourced Cost savings
Time savings
Reliance on vendor for maintenance and future
enhancements
Development Utilize vendors’ expertise
Some customization may be possible
Will not develop in-house functional and technical skills
Unique needs may go unmet
May require system integration
Outsourced Development
Hire expertise we do not have No opportunity to build in-house expertise
May save time and money Reliance on vendor
Lower risk Future options limited
Security-potential loss of confidential info
Performance based on contract terms
5
Developing Our Options
• Start by collecting information
 What tools and technologies are needed for a custom
development project?
 What vendors make products that address the project
needs?
 What service providers would be able to build this
application if outsourced?

Copyright ©2019 John Wiley & Sons, Inc. 6

Request for Proposals (RFP)

• Solicits proposals from vendor, developer, or service provider

• Explains the system to be built and criteria for selecting among applicants
• Request for Information (RFI) -- a shorter and less detailed version
• Request for Quote (RFQ) – use when you just need a price

Copyright ©2019 John Wiley & Sons, Inc. 7

Typical RFP Contents
• Description of desired system
• Special technical needs or circumstances
• Evaluation criteria
• Instructions on how to respond
• Desired schedule
• Other information that will help the submitter to make a
more complete or accurate proposal

Copyright ©2019 John Wiley & Sons, Inc. 8

 Acquisition Strategy Selection Factors
When to Use Custom When to Use a When to Use Outsourcing
Development Packaged System
Business need The business need is unique. The business need is The business need is not core to
common. the business.
In-house In-house functional and technical In-house functional In-house functional or technical
experience experience exists. experience exists. experience does not exist.
Project skills There is a desire to build in-house The skills are not strategic. The decision to outsource is a
skills. strategic decision.
Project The project has a highly skilled The project has a project The project has a highly skilled
management project manager and a proven manager who can project manager at the level of
methodology. coordinate vendor’s efforts. the organization that matches
the scope of the outsourcing
deal.
Time frame The time frame is flexible. The time frame is short. The time frame is short or
flexible.
9
Copyright ©2019 John Wiley & Sons, Inc.
Developing an Alternative Matrix
• Combine several feasibility analyses into one matrix
• Include technical, economic, and organizational feasibilities
• Assign weights to indicate the relative importance of the
criteria
• Assign scores to indicate how well the alternative meets the
criteria

Copyright ©2019 John Wiley & Sons, Inc. 10

Sample Alternative Matrix

* This denotes how well the alternative meets the criteria. 1 = poor fit; 5 = perfect fit.
Copyright ©2019 John Wiley & Sons, Inc. 11
Architecture Design

12
System Architecture
• Describes hardware, software and network components
• How will the software components be assigned to hardware devices
• Flows from non-functional requirements
• Main components:
 Distribution of system across computers
 Hardware needed
 Operating system
 Applications

13
Architectural Components
• Software System’s functions
1. Data storage
2. Data access logic
3. Application logic
4. Presentation logic
• Hardware Components
 Client computers
 Servers
 Network
14
Common Architectures: Client-Server
• Processing balanced between client devices and server(s)
Presentation logic  client
Databases and data access logic  server(s)
• Application logic  client or server or split
Thick/fat client: if most/all app logic is on client
Think client: if minimum app logic is on client
• Advantages of client-server:
 Scalable
 Flexible with system types
 Independent logic for app, data, presentation
 Decoupled failures 15
 Client-Server and Server-Based
Architectures: Examples

Image link
Image link Image link

Two-Tier Architecture Three-Tier Architecture n-Tier Architecture

e.g. ATM e.g. Web Applications workstation-based client, two web
servers, and different database
servers

16
 Cloud Based Systems
• Off-site third-part provided servers
• Delivering aspects of computing as a service:
• Hardware, networks, storage, services, and
interfaces
• Delivered over internet, based on user
demand
• Scalable, low investment cost, less training
• IoT

17
From Non-Functional Requirements to
Architectural Design

• Operational requirements
• Performance requirements
• Security requirements
• Cultural and political requirements

18
Operational Requirements
Requirement Definition Example
Technical Special hardware, software, and All office locations have always-on
Environment network requirements imposed network connection permitting
by business requirements real-time database updates
System The extent to which the system The system will read and write to
Integration will operate with other systems the main inventory database
Portability The extent to which the system The system must operate with
will need to operate in other mobile devices (Android and iOS)
environments
Maintainability Expected business changes to The system must accommodate
which the system should be new manufacturing plants
able to adapt

Copyright ©2019 John Wiley & Sons, Inc. 19

Performance Requirements
Requirement Definition Example
Speed Time within which the system Network transaction
must perform its function response time <= 4
seconds
Capacity Total and peak number of users Maximum of 2000
and the volume of data expected simultaneous users at
peak use times
Availability and Extent to which the system will be 99% uptime
Reliability available to the users and the performance
permissible failure rate due to
errors
20
Copyright ©2019 John Wiley & Sons, Inc.
Security Requirements
Requirement Definition Example
System Value Estimated business value of the A complete loss of all system data
Estimates system and its data would cost $20 million
Access Control Limitations on who can access Inventory item changes can be made
what data only by managers for items in their
own department
Encryption and Defines what data will be Data will be encrypted from the user’s
Authentication encrypted where and whether computer to the Web site to provide
authentication will be needed for secure ordering
user access
Virus Control Controls to limit viruses All uploaded files will be checked for
viruses before being saved in the
system
21
Copyright ©2019 John Wiley & Sons, Inc.
Cultural/Political Requirements
Requirement Definition Example
Multilingual The language(s) the system The system will operate in English,
users will need French, and Spanish
Customization Specification of what Country managers will be able to
aspects of the system can define new fields in the product
be changed by local users database to capture country-
specific information
Making Unstated Explicitly stating All weights will be stated in
Norms Explicit assumptions that differ pounds and in kilograms
from country to country
Legal The laws and regulations Personal customer information
that impose system cannot be transferred from
requirements European Union countries to US
Copyright ©2019 John Wiley & Sons, Inc. 22
Nonfunctional Requirements and the Architecture Design

Copyright ©2019 John Wiley & Sons, Inc. 23

Sample HW/SW Specification
Standard Client Standard Web Standard Standard Database
Server Application Server
Server
Operating • Windows 10 Pro • Linux • Linux • Linux
System
Special • Real Audio • Apache • Java • Oracle
Software • Adobe Acrobat Reader
Hardware • 1 TB disk drive • 8 TB disk • 8 TB disk drive • 32 TB disk drive
• Intel®-Core™ i5-8400 six drive • Xeon E5-4600 v4 • RAID
core processor • Xeon E5- • Xeon 28 core
• 22-inch LED Monitor 4600 v4 processor
Network • Always-on Broadband, • Dual 100 • Dual 100 Mbps • Dual 100 Mbps
preferred Mbps Ethernet Ethernet
Ethernet

Copyright ©2019 John Wiley & Sons, Inc. 24