Quotation Midlet Council (QMC)

Slides:

Advertisements

Similar presentations

Absence Credit Tracking System April 10, Team Members: Joshua Allen Dave Kristensen Greg Ludwinski Samantha Ratnapuli.

Advertisements

Testing Relational Database

Academic Computing Stanford University Libraries Technical Overview.

Automatic Updates. The bottom left hand corner should say “checking for updates” every time you sign in.

Calendar Browser is a groupware used for booking all kinds of resources within an organization. Calendar Browser is installed on a file server and in a.

True IT Solutions For You 1 IT Solutions Software Development and Web Design.

Reference and Instruction Automated Statistics Gathering and Reporting System Members: Patrick Chen (pyc7) Soo-Yung Cho (sc444) Gregg Herlacher (gah24)

Development of a Web Based B&B Reservation System Elizabeth Gates 22July04.

Quality Assurance CS 615. Mission Statement The Quality Assurance team will provide assurance to stakeholders in CS-615/616 projects that their projects.

Mike Krajecki – Project, Design, and Presentation Manager Justin McMillan – Implementation Manager Joe Brunner – Requirements and Testing Manager Mohammed.

Agile Testing with Testing Anywhere The road to automation need not be long.

Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.

Default: Zoom 65% then screenshot. DB XStudio tests Launcher DB XStudio XAgent tests Backup DB tests Launcher.

NMS1.0(c) Copyright Final Year Project Demonstration Dublin City University 29 th May 2003 Team Members : David ReadeTimothy Kelly

Greg Andolshek Alex Koch Michael McCormick Team Lasso.

Web Trnsport – Beta Testing and Implementation TUG Roundtable Discussion Elizabeth Rodgers Info Tech, Inc. October 9, 2007.

Testing in Extreme Programming

M1G Introduction to Database Development 6. Building Applications.

End HomeWelcome! The Software Development Process.

Nobody’s Unpredictable Ipsos Portals. © 2009 Ipsos Agenda 2 Knowledge Manager Archway Summary Portal Definition & Benefits.

Bringing power of simulation to the public.

1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.

Project Overview Graduate Selection Process Project Goal Automate the Selection Process.

Testing in UP1 Testing as part of the Unified Process (UP)

Configuration Database MICE Collaboration Meeting 28, Sofia David Forrest University of Glasgow Antony Wilson Science and Technology Facilities Council.

Team Members Team Members Tim Geiger Joe Hunsaker Kevin Kocher David May Advisor Dr. Juliet Hurtig November 8, 2001.

Systems Analysis and Design

WSM Administrator Training. WSM Administrator Discussion of WSM Administrator responsibilities Discussion of WSM administrative interfaces Detailed discussion.

Our goal is to make a web based multi-user organizer that can be accessed via cellular devices. There are three main component for this project: A main.

TeamForge Andrew Nelson, Bishop Wilkins, Ky Le, and Yoshito Kosai.

Unified Distributed (UDub Mail) Life Cycle Objectives Sachin Pradhan Gabriel Maganis.

The Software Development Process

Database Server Concepts and Possibilities Lee Lueking D0 Data Browser Workshop April 8, 2002.

A Comprehensive WebCT Integration System Rob Phillips –Teaching and Learning Centre, Murdoch University James Strong –NetSpot Onno Benschop –ITmaze Mark.

 Architectural overview  Main APIs. getGames.php getGroupsLocations.php getGroupsScores.php getMessage.php getStreet.php getTime.php login.php sendMessage.php.

Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification.

1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.

© Rob Schlender & Hamed Esfahani StadiumFood Life Cycle Objective Review CSE 403, Project Proposal Rob Schlender & Hamed Esfahani.

GW ToDo A Task Manager CSCI 6442 Project Spring, 2016.

Final Fantasy ½: IOC Overview Team Q CSE 403 Winter ‘03 I’ve got something special for you.

Ashley Montebello Katie Githens Wayne Rowcliffe. Project Overview Create graduate student review system for ECpE department Review system is used by students.

MYSQL AND MYSQL WORKBENCH MIS2502 Data Analytics.

INTRODUCING VERSION 9 Advances. Enhancements. Balance.

CACI Proprietary Information | Date 1 PD² v4.2 Increment 2 SR13 and FPDS Engine v3.5 Database Upgrade Name: Semarria Rosemond Title: Systems Analyst, Lead.

Anytime, Anywhere Access Benefits Functionality Work Order Administration Dispatch Work Order Work Order Details New Work Order Additional Functionality.

Project Dragon Small Business Website Content Management System.

Group 3 CMPE Community Project. What is CMPE Community project? CMPE Community project aims to create a social web application to create an environment,

Presented by: K.AMARNATH Ht.no:10841f0045 Guided by: T.Suneetha.

Academic Computing Stanford University Libraries Technical Overview of CourseWork 3.0 January 2004.

© 2012 IBM Corporation 12/19/2013 Rational Team Concert – User Administration Bruce Besch.

Progress Apama Fundamentals

Internet Made Easy! Make sure all your information is always up to date and instantly available to all your clients.

Operating System Concepts

GGUS webportal – future plans

DATABASE SEARCH & REVIEW GETTING STARTED GUIDE FOR EMIS WEB USERS

mysql and mysql workbench

Software Documentation

SAP R/3 Data Archiving with PBS as Retrieval Method

Rick VanVelkinburgh and Jesse Collins. CSE403g

For Computer-Based Testing

SWEN 5230 Your Project Title

Testing and Test-Driven Development CSC 4700 Software Engineering

TJHSST Website Redesign

Initial Operational Capability

Scott Stocker November 18, 2002

CellBus Final Release.

For Computer-Based Testing

Team 21: Project Design Team Members: Nathan Staley Steven Murray

Presentation transcript:

Quotation Midlet Council (QMC) QuoteME IOC Overview Quotation Midlet Council (QMC) Jesse Collins, Hamed Esfahani, Troy Lambert, Rob Schlender, Rick VanVelkinburgh. CSE403g

White/Black box Testing White box: developers tested their own code, then team members tested each other’s code. Black box: Server side was tested mainly via browser. When no more server-side errors were found, the midlet was tested against the server until no more midlet errors were found (2 rounds). Automation: It was decided that automation would take more time than it would save. This proved to be true as the test-suite was small, testing was accomplished quickly, and few rounds were required.

Hallway testing The system was tested by new, unfamiliar users. Some few minor interface improvements were suggested. All these were implemented, save one due to time constraints. New users discover basic functionality easily, i.e. choose a category, read a quote. Expanded functionality is discovered and mastered in a reasonably short period of time. The interface could be argued over and improved forever. However, it is robust, to spec and ready for release.

Server-side IOC: Installation Covers (briefly) installation of supporting software, with links to ant.apache, java.sun, mysql. Installation on the Tomcat webserver. How to test/verify that the installation was successful. How to setup the db table. How to load the initial data file (provided). How to update the table with additional quotes.

Client-side IOC: Installation Installation instructions. List of supporting software, with appropriate links.

Support Personnel Database Administrator Webserver Administrator Quote Editor: hands off quote updates to DB admin. (Midlet support) Nextel and Nokia fight it out to see who gets to release and support the amazing QuoteME. 

Users Guides Midlet user’s guide in IOC. Servlet user’s guide at http://cubist.cs.washington.edu/~hamede/ Online servlet user’s guide includes QuoteME servlet javadocs, complete installation instructions, and support plan.

Ready for release Operational concept has been realized: User interface meets spec and performs well. Client/ server interface meets spec and performs well. All phases of testing are complete. We could always do more, but the product is suitably robust for the first release. Documentation is complete. Operational software is complete, packaged, and ready for release.