Systems Design
Information System
• Hardware – physical components of the computer and related devices.
• Software – program that enables a computer perform a specific task.
• Application software – enables a user perform a task
• System software or Operating System (OS) – which enables other software to run properly
• Database - organized collection of structured information, or data, typically stored
electronically in a computer system.
• Network - consists of multiple devices that communicate with one another.
• People
System Architecture
• Client-server architecture
- many clients (remote processors) request and receive
service from a centralized server (host computer).
• Thin vs. thick client
• Two-tiered, three-tiered, n-tiered client-server
• Server-based architecture
• Mobile-application architecture
Nonfunctional Requirements
• Creating an architecture design begins with the nonfunctional requirements
• Operational requirements
• Performance requirements
• Security requirements
• Cultural and political requirements
Hardware and Software Specification
• Describe what hardware and software are needed to support the application.
• Operating System
• Special Software
• Hardware
• Network
• Factors in hardware and software selection:
1. Functions and features
2. Performance
3. Legacy databases and systems
4. Hardware and OS strategy
5. Cost of ownership
6. Political preferences
7. Vendor performance
Hardware and Software Specification
User-Interface Design
Objectives:
• Explain the concept of usability with regard to the user interface.
• Describe several fundamental user interface design principles.
• Explain the process of user interface design.
• Explain ways to understand the perspectives of the users of the user interface.
• Describe ways to define the structure of the user interface.
• Explain the standards that should be established for the user interface.
• Describe various ways to prototype the user interface.
• Discuss ways to evaluate and test the user interface.
• Discuss special concerns associated with touch‐screen‐enabled user
interfaces.
• Be able to design a highly usable user interface.
Usability Concept
• Interface design is the process of defining how the system interacts with the
external entities (e.g., customers, suppliers, and other systems).
• Usability
- Easy to use
- Easy to learn
Principles for UID
Principle Description
The interface should be a series of areas on the screen that
Layout
are used consistently for different purposes
Users should always be aware of where they are in the
Content awareness
system and what information is being displayed.
Interfaces should be functional and inviting to users through
Aesthetics
careful use of white space, colors, and fonts.
Although ease of use and ease of learning often lead to
similar design decisions, there is sometimes a trade‐off
Usage level
between the two. Infrequent users of software will prefer ease
of learning, whereas frequent users will prefer ease of use.
Consistency in interface design enables users to predict what
Consistency
will happen before they perform a function.
Minimize user effort The interface should be simple to use.
Process of UID
Interface Structure Design
• Interface Structure Diagram (ISD) – used to show how all the screens, forms, and
reports used by the system are related and how the user moves from one to
another.
• Sitemap – useful tool to organize content
Interface Standards
• Interface metaphor – a concept of real world that is used as a model for the
information system.
• Interface objects – are fundamental building blocks of the system, such as the
entities and data stores.
• Interface actions - are common commands that will be employed by the users.
• Interface icons - are small pictures that will appear on command buttons as well
as in forms and reports to highlight important information.
• Interface template – defines the general appearance of all interface components
in the information system (screens, forms, and reports).
ID Prototyping
• Define the look
- Wireframe Diagram
• Define the flow
- Story board
• HTML Prototype
• Language prototype
Interface Evaluation/Testing
• Heuristic evaluation
• Walkthrough evaluation
• Interactive evaluation
• Formal usability testing
Touch-screen-user enabled interface
• Navigation elements
• Screen elements
• Standardized gesture interactions
Program Design
Objectives:
• Be able to revise logical DFDs into physical DFDs.
• Be able to create a structure chart.
• Be able to write a program specification.
• Be able to write instructions using pseudocode.
• Become familiar with event‐driven programming.
Physical DFDs
• Data Flow Diagram elements
1
• Physical DFDs vs. Logical DFDs
Process
1. Add implementation references
2. Draw a human-machine boundary
Data Flow
3. Add system-related data stores, data flows,
and processes D1 Data Store
4. Update the data elements in the data flows
5. Update the metadata in the CASE repository External Entity
Physical DFDs
Illustration:
• Whenever new patients are seen for the first time, they complete a patient
information form that asks their name, address, phone number, and brief medical
history, all of which are stored in the patient information file.
• When a patient calls to schedule a new appointment or change an existing
appointment, the receptionist checks the appointment file for an available time.
Once a good time is found for the patient, the appointment is scheduled.
• If the patient is a new patient, an incomplete entry is made in the patient file; the
full information will be collected when the patient arrives for the appointment.
• Because appointments are often made so far in advance, the receptionist usually
mails a reminder postcard to each patient two weeks before his or her
appointment.
Logical DFDs
Updated patient
1
Updated patient
information information
Receptionist Complete Patient D1 Patient Info
Information Form
Incomplete entry of
patient information
2 D1 Patient Info
Appointments Appointments
Receptionist Schedule/change an D2 Appointment File
appointment Available time
Booked appointment
3
Booked
appointment Notify the patient
Receptionist Booked D2 Appointment File
of booked appointment
appointment
Booked appointment
Patient
Physical DFDs
Updated patient
1 MySQL Record:
Updated patient
information information
Receptionist Complete Patient D1 MySQL: Patient Info table
Information Form
HTML
Incomplete entry of
patient information
2 D1 MySQL: Patient Info table
Appointments Appointments
Receptionist Schedule/change an D2 MySQL: Appointment table
appointment Available time
HTML Booked appointment
3
Booked
appointment Notify the patient
Receptionist of booked appointment Booked D2 Appointment File
appointment
HTML
Booked appointment
Patient
Systems
Implementation
Implementation
• Testing the entire system
• Formal user acceptance
• Systems documentation
• Database conversion
• System cut-over
• Cold turkey cut-over (“big bang”)
• Phased cut-over
• Parallel operation cut-over
Systems
Evaluation
Post-implementation Review
• Provides management with insights in ways to improve the process for
future systems.
• Provide auditors (both internal and external) with evidence regarding
the adequacy of SDLC in general and the risks associated with a
particular system.
Areas
• Systems Design Adequacy
• Accuracy of Time, Cost, and Benefit estimates
Systems
Maintenance
Systems Maintenance
• A formal process by which application programs undergo changes to
accommodate changes in user needs.
Controls and
Audit
Controlling New Systems Development
• Systems Authorization Activities
• User Specification Activities
• Technical Design Activities
• Internal Audit Participation
• User Test and Acceptance Procedures
Controlling Systems Maintenance
• Maintenance Authorization, Testing, and Documentation
• Source Program Library Controls
• Password Control
• Separate Test Libraries
• Audit Trail and Management Reports
• Program Version Numbers
• Controlling Access to Maintenance Commands
