GSES Good Software Engineering System Technologies

1
GSES Good Software Engineering System Technologies

• Airline Reservation System (ARS) Project
• Software Quality Plan

Guy Davis Samuel Lee Eileen (Xiaozheng)
Wang Simon (Ming) Zhou
2
Quality Plan Overview

• dX approach
• Mission critical System
• Web security

3
Three roles in QA

• Developer
• Unit test is written before the code
• Ensure the code quality
• Customer
• On site customer
• Acceptance tests
• Rapid feedback
• Ensure that the system meet requirements
• QA
• Work with developer and customer to ensure the
  the quality of functionality delivered

4
Communication

• Frequent, short meeting
• Frequent feedback by short term iteration.
• An open workspace

5
Risk Management

• Anticipate changes and ensure that the associated
  risks are controlled. According to dX, should
  prioritize each use case card. High risk use
  cases are given higher priority.
• Agile methods emphasis on tests, integration,
  and flexibility are benefits for these types of
  critical, reliable, and safe systems.

http//fc-md.umd.edu/projects/Agile/statement_3.ht
m
6
Programmer
7
Team
8
Customer
9
(No Transcript)
10
Infrastructure Quality

• Determine quality goals and targets
• Application server
• Database
• Operating system
• Hardware (servers, interfaces, networking)
• Application of testing and evaluation standards
• Audit and review of testing processes

11
Application Server Quality

• Performance
• Load testing to meet worst-case scenario
• Fault-tolerance and redundancy
• Availability
• Compatibility
• With database, OS, utilities, network interfaces,
  etc...
• Security

12
Database Quality

• Availability
• Reliability (data integrity)
• Off-site transaction replication
• Security
• Performance
• Clustering of servers
• Load testing at end of each iteration

13
Operating System Quality

• Compatibility
• Performance

• Security
• Stability/Reliability

14
Hardware Quality

• Fault-tolerance/redundancy
• Secondary data-centre, hot-standby
• Vendor support
• Physical security
• Is data-centre secure?
• Networking component quality
• Covers all interfaces to reservation system

15
Deployment

• Running the new system with the old system in
  parallel for couple weeks
• Before the deployment, the user training will be
  done
• The IT support will be helping with the
  deployment training
• Help Desk should also be setup to handle calls
  after the deployment

16
User Acceptance Test

• Approach
• Tests are created from user stories.
• Customer specifies scenarios to test.
• User story is not completed until they passed the
  user acceptance tests
• Responsible Party
• Customers
• Developers
• Network Specialists
• QA

17
User Acceptance Test (Cont.)

• Tools
• GUI
• Commercial Tool
• Run once to establish a golden copy
• E.g. TestWeb
• Code
• Programmer write the code
• E.g. JUnit
• Spreadsheet
• Represent tests in a spread sheet for repeated
  tests
• Manual
• Write down the procedures and plan on paper and
  then follow the steps manually

18
Training

• Targeted at different audiences
• General User
• Technical Support Staff
• Managers
• Advance Users

19
Disaster Recovery

• Hardware Redundancy
• Duplicate copy of software or applications
• Backup of data
• A backup site
• Assign teams to different roles and
  responsibilities

20
Questions