IS1024 Project Team 7
| Вид материала | Документы |
- Point Team Services, входящий в состав ms project Server. Основные термины задача, 197.38kb.
- Project Expert 0, 587.79kb.
- Fast Street Team» Зимний Кубок клуба Fast Street Team по ралли-спринту «fst winter, 157.07kb.
- Microsoft Project Server. Microsoft Project Web Access Web-интерфейс для отчет, 98.46kb.
- Член Project Management Institute (pmi). Certified Senior Project Manager (cpm) Сертифицированный, 27.46kb.
- Software Project Management ) (базовый) по направлению: 511600 факультеты: фупм кафедра:, 41.85kb.
- Microsoft Project Portfolio Server Пример внедрения: решение, 374.46kb.
- Microsoft Office Project 2007-2010 программа, 121.65kb.
- Одним из лидирующих инструментов планирования бизнеса в условиях рынка, разработки, 42.42kb.
- Великий Новгород, ул. Псковская,, 12.23kb.
Test Case TC 1.0: Generating Reports Main Scenario
Introduction:
Identifier – TC 1.0
Owner/Creator – Group 7
Version – 2.0
Name – Generating Reports – Main Scenario
Requirement Identifier – UC 1.0
Purpose – Will test to ensure that validated data in BevDot can be used in generating the different reports requested by the various users.
Dependencies – Example data published in BevDot
Activity:
Testing Environment – Test will be performed on BevDot from example information from legacy system.
Initialization – User connected to BevDot via a GUI and request a report.
Finalization – BevDot pulls information from published tables and returns report to the user.
Actions – See steps in main scenario of Use Case UC 1.0
Input Data – Example data that would be found in legacy system.
Results:
Expected Results – User would request a report then BevDot would gather the information and return the report to the user.
Actual Results – Reports were generated successfully with fake data manually entered.
- ETL
Test Case TC 2.0: ETL process Main Scenario
Introduction:
Identifier – TC 2.0
Owner/Creator – Group 7
Version – 2.0
Name – ETL – Main Scenario
Requirement Identifier – UC 2.0
Purpose – Test will check to make sure data extracted from legacy system to data warehouse is performed correctly.
Dependencies – Raw data from legacy system
Activity:
Testing Environment – ETL needs to be installed on BevDot
Initialization – Extract data from legacy to begin ETL process.
Finalization – Cleanse data and place into tables.
Actions – See steps in main scenario of Use Case UC 2.0
Input Data – Example data that would be found in legacy system.
Results:
Expected Results – BevDot would extract, automatically validated data, transform, and cleanse data.
Actual Results – Data needed to be validated manually.
a. Extract data from legacy system into BevDot
Test Case TC 3.0: ETL process Extract Scenario
Introduction:
Identifier – TC 3.0
Owner/Creator – Group 7
Version – 2.0
Name – ETL – Extract data Scenario
Requirement Identifier – UC 3.0
Purpose – Test will check to make sure data is extracted from the legacy system into BevDot.
Dependencies – Raw data from legacy
Activity:
Testing Environment – ETL needs to be installed on BevDot
Initialization – Extract data from legacy to begin ETL process.
Finalization – Data finishes transfer and moves to next step in ETL process.
Actions – See steps in main scenario of Use Case UC 3.0
Input Data – Example data that would be found in legacy system.
Results:
Expected Results – BevDot would extract data from legacy system and be ready for next step in ETL process.
Actual Results – Data was indeed extracted from legacy system into BevDot.
- Automatically validate data
Test Case TC 4.0: ETL process Auto Validate Scenario
Introduction:
Identifier – TC4.0
Owner/Creator – Group 7
Version – 2.0
Name – ETL – Auto Validate Scenario
Requirement Identifier – UC 4.0
Purpose – Test will check to make sure extracted data is automatically validated.
Dependencies – Raw data from legacy system
Activity:
Testing Environment – ETL needs to be installed on BevDot
Initialization – Extracted data from legacy system will be validated.
Finalization – validated data will go into BevDot to be published into tables.
Actions – See steps in main scenario of Use Case UC 4.0
Input Data – Example data that would be found in legacy system.
Results:
Expected Results – BevDot would automatically validated data from legacy system.
Actual Results – Automatic validation failed and therefore required manual validation.
- Transform data to publish into tables
Test Case TC 5.0: ETL process Transform Scenario
Introduction:
Identifier – TC 5.0
Owner/Creator – Group 7
Version – 2.0
Name – ETL – Auto Validate Scenario
Requirement Identifier – UC 5.0
Purpose – Test will that validated data is transformed.
Dependencies – Validated data
Activity:
Testing Environment – ETL needs to be installed on BevDot
Initialization – Validated data will be transformed.
Finalization – Transformed data will be ready to for tables to be published.
Actions – See steps in main scenario of Use Case UC 5.0
Input Data – Example data that would be found in legacy system.
Results:
Expected Results – BevDot would transform the data validated from the ETL process.
Actual Results – Data from validation was successfully transformed.
- Publish Tables
Test Case TC 6.0: ETL process Publish Tables Scenario
Introduction:
Identifier – TC 6.0
Owner/Creator – Group 7
Version – 2.0
Name – ETL – Auto Validate Scenario
Requirement Identifier – UC 6.0
Purpose – Test will check to make sure transformed data is in tables and is published.
Dependencies – Transformed data in BevDot
Activity:
Testing Environment – ETL needs to be installed on BevDot
Initialization – Transformed data is put into tables ready to be published
Finalization – Tables are published.
Actions – See steps in main scenario of Use Case UC 6.0
Input Data – Example data that would be found in legacy system.
Results:
Expected Results – BevDot would publish the tables so they would be available from reports.
Actual Results – BevDot successfully published tables.
- Manual Validation
Test Case TC 7.0: ETL process Manual Validation Scenario
Introduction:
Identifier – TC 7.0
Owner/Creator – Group 7
Version – 2.0
Name – ETL – Auto Validate Scenario
Requirement Identifier – UC 7.0
Purpose – Test will check manual validation process.
Dependencies – Extracted data from legacy system
Activity:
Testing Environment – ETL needs to be installed on BevDot
Initialization – IT department receives message of failed automatically validation to begin manual validation.
Finalization – Data is validated to begin transformation.
Actions – See steps in main scenario of Use Case UC 7.0
Input Data – Example data that would be found in legacy system.
Results:
Expected Results – IT department would check all data that failed automatic validation to manually validated data.
Actual Results – IT department successfully validated data manually.
- Error Handling
Test Case TC 8.0: Error Handling - Main Scenario
Introduction:
Identifier – TC 8.0
Owner/Creator – Group 7
Version – 2.0
Name – Error Handling – Main Scenario
Requirement Identifier – UC 8.0
Purpose – Test will check error handling of BevDot
Dependencies – BevDot system
Activity:
Testing Environment – BevDot system
Initialization – IT department checks BevDot for error handling
Finalization – Errors are handle with the correct responses to errors.
Actions – See steps in main scenario of Use Case UC 8.0
Input Data – Example data that would be found in legacy system.
Results:
Expected Results – BevDot would handle errors with correct responses.
Actual Results – BevDot was successful with error handling
- Graphical representations of Reports
Test Case TC 9.0: Graphical Representations of Reports Scenario
Introduction:
Identifier – TC 9.0
Owner/Creator – Group 7
Version – 2.0
Name – ETL – Auto Validate Scenario
Requirement Identifier – UC 9.0
Purpose – Test will check that there is graphical representations of reports.
Dependencies – Published data in BevDot
Activity:
Testing Environment – BevDot system
Initialization – Reports will be gathered
Finalization – Graphical representation of the reports will be printed.
Actions – See steps in main scenario of Use Case UC 9.0
Input Data – Data in BevDot.
Results:
Expected Results – BevDot world produce graphical representations of reports.
Actual Results – Graphical representations were produced.
- Section 6.3 Features-to-Use Case
| | UC1.0 | UC2.0 | UC3.0 | UC4.0 | UC5.0 | UC6.0 | UC7.0 | UC8.0 | UC9.0 |
| FE1.0 | X | | | | | | | | |
| FE2.0 | X* | | | | | | | | |
| FE3.0 | X* | | | | | | | | |
| FE4.0 | X* | | | | | | | | |
| FE5.0 | | X* | | | | | | | |
| FE6.0 | | X | X* | | | | | | |
| FE7.0 | | X | X* | X* | | | | | |
| FE8.0 | | X | X* | X* | X* | | | | |
| FE9.0 | | | | | | X | | | |
| FE10.0 | | | | | | | X | | |
| FE11.0 | | | | | | | | X | |
| FE12.0 | | | | | | | | | X |
- Section 6 Use-Case to Test-Case
| | TC1.0 | TC2.0 | TC3.0 | TC4.0 | TC5.0 | TC6.0 | TC7.0 | TC8.0 | TC9.0 |
| UC1.0 | X | | | | | | | | |
| UC2.0 | | X | | | | | | | |
| UC3.0 | | X | X* | | | | | | |
| UC4.0 | | | X | X* | | | | | |
| UC5.0 | | | | X | X* | | | | |
| UC6.0 | | | | | X | X* | | | |
| UC7.0 | | | | | | | X | | |
| UC8.0 | | | | | | | | X | |
| UC9.0 | | | | | | | | | X |