Fall 2004

1
Green Gold Consulting Services

• Fall 2004
• MIS 161 Systems Development Life Cycle
• Wednesday, 600 850 PM, Section 2

Phase VI System Test ARCHY
2
Agenda

• Timeline
• Economic Feasibility Update
• Testing Plan
• Unit Tests
• Integration Tests
• System Tests

3
Topics Not Discussed

• Retesting
• Manual
• Performance Testing

4
Team Member Contribution

• Eric Duran Project Scheduler/Test Plan Designer
• Nick Storms Unit test
• Mike Phelps Integration and Systems Testing
• Michael Soldwisch Phase Leader
• Miguel Gutierrez Economic Feasibility/Business
  Value

5
About IS Solutions ARCHY

• Client
• ARC IT Department
• Project Champion Linda Jurgens.
• Providing IT support.
• System
• ARCHY
• Innovating current support ticket system.
• Using a web-based application for flexibility.

6
Timeline
7
Economic Feasibility Update
8
Business Value

• Business Need
• Why the system should be built?
• Functionality
• What will the system do?
• Expected Value
• Tangible Faster turnaround time
• Intangible Improved customer service

9
Business Value

• Special Issues or Constraints
• Working as students
• Future support of the system

10
Unit Tests

• White Box vs. Black Box
• Used Black box
• Assumed to be working properly

11
Unit Tests
12
Integration Tests

• User Interface

Testing each interface function
13
Integration Tests

• Use-Case

Tester tests each use case for functionality
14
Integration Tests

• User Interface

Testing each interface function
15
Integration Tests

• User Interface

Testing each interface function
16
Integration Test

• Interaction
• Test each process of the Class, Sequence, and
  Collaboration Diagrams in a step-by-step process.
• The test is used in portions where the system
  performs data processing.
• Still Underway

17
System Tests

• Requirements
• Tests that original business requirements are met
  and ensures that changes made to the system
  didnt create new errors.
• let the user create a ticket,
• do a custom search on the open and closed tickets
  and generate a report based on it
• send email confirmation on support tickets
  received,
• provide a way for clients to track the status of
  their tickets
• give the technicians and supervisor access to
  the system and assign or reopen tickets on the
  web

18
System Tests

• Usability
• Tests how convenient the system is to use.
• It makes sure that the software conforms to the
  look and feel that the users expect from the
  system.
• Easy to use
• Not overly complex

19
System Tests

• Security
• Tests disaster recovery unauthorized access.

20
System Tests

• Performance Testing
• Multiple log on supported
• Load test not performed

21
Questions, Comments, Concerns???
Any Questions?