Greenfoot / JF_V02_S03_L12
.pdf
Creating an Inventory of Java Fundamentals
Project Plans for Global Teams
•At a technology company, project plans may be based on a 24-hour day as opposed to an 8-hour day because teams are global. When one programmer’s day ends another programmer’s day begins.
•Large projects may have 6-10 different project plans that roll-up into one master project plan.
•Large plans with many team members demand that tasks are completed on time.
–Delays can cause a ripple effect on the overall project.
–One person’s delay could impact the whole team’s work and schedule.
21Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Creating an Inventory of Java Fundamentals
Project Plan Components
•Project plans should include:
–Task list
–Task duration (start and end dates)
–Task resources
–Task dependencies
Task |
Start |
End |
Resource |
Dependency |
|
Design |
15-Nov-2011 |
30-Dec-2011 |
Chris |
Scenario Design |
|
Actors |
|||||
|
|
|
|
22Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Creating an Inventory of Java Fundamentals
Quality Assurance (Q/A) Stages
Software testing activities or stages include:
1 |
Requirements Analysis |
2 |
Test Planning |
3 |
Test Case Development |
4 |
Environment Setup |
5 |
Test Execution |
6 |
Test Closure Cycle |
23Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Creating an Inventory of Java Fundamentals
Quality Assurance Tasks
Software |
Definitions |
Tasks |
||
Testing Stage |
||||
|
|
|
||
Requirements |
Requirements analysis is a |
• |
Listing type of tests to perform |
|
Analysis |
process for determining user |
• |
Prioritizing and focusing tests |
|
|
expectations. Helps a quality |
• |
Automation feasibility |
|
|
assurance engineer design an |
|||
|
overall plan to ensure the |
|
|
|
|
program is working as designed. |
|
|
|
Test Planning |
Test planning is an actual stage |
• |
Writing test plan strategy |
|
|
where all of the various types of |
• |
Selecting test tools |
|
|
tests are defined. This includes |
|||
|
|
|
||
|
hardware tests, software tests, |
• |
Estimating time required for testing |
|
|
and usability tests. |
• |
Training |
|
|
|
|||
|
|
|
|
|
24Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Creating an Inventory of Java Fundamentals
Quality Assurance Tasks
Software |
Definitions |
Tasks |
|
Testing Stage |
|||
|
|
||
Test Case |
Test case is a set of conditions |
• Creating tests |
|
Development |
or variables with which a test |
• Identifying test data and baseline |
|
|
engineer will determine if a |
data |
|
|
software program is working |
||
|
|
||
|
properly. Having a set of |
|
|
|
scenarios helps multiple quality |
|
|
|
assurance engineers complete |
|
|
|
all of the same tasks when |
|
|
|
testing. The stage for setting up |
|
|
|
the environment is very |
|
|
|
important. The overall test plan |
|
|
|
may define many different |
|
|
|
environments in which quality |
|
|
|
assurance engineers do their |
|
|
|
testing. |
|
25Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Creating an Inventory of Java Fundamentals
Quality Assurance Tasks
Software |
Definitions |
Tasks |
||
Testing Stage |
||||
|
|
|
||
Environment Setup |
|
• Setup hardware and software |
||
|
|
|
environment |
|
Test Execution |
Test execution is the execution |
• |
Execute test plans |
|
|
of the same test against many |
• |
Document results |
|
|
parts of a software program |
|||
|
• |
Retest fixes |
||
|
(interface, business logic, web |
|||
|
layer, etc.) This can include both |
|
|
|
|
manual testing and automated |
|
|
|
|
testing. Automated testing takes |
|
|
|
|
longer to set up but it is often |
|
|
|
|
used for programs that need |
|
|
|
|
100% reliability. |
|
|
|
|
|
|
|
|
26Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Creating an Inventory of Java Fundamentals
Quality Assurance Tasks
Software |
Definitions |
Tasks |
|
Testing Stage |
|||
|
|
||
Test Cycle Closure A test cycle is a set of defined |
• Qualitative and quantitative |
||
|
start and stop points in a quality |
customer reporting |
|
|
assurance program. There may |
|
|
|
be many test cycle closures. A |
|
|
|
test cycle closure allows |
|
|
|
programmers time to fix the |
|
|
|
bugs that were documented |
|
|
|
during the test cycle. |
|
|
|
|
|
|
27Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Creating an Inventory of Java Fundamentals
Examples of Software Testing Variations
Software Testing Variations |
Tasks |
|
|
|
|
Change the Environment |
• |
Change the operating system. |
|
• |
Change the browser. |
|
• Change the display settings. |
|
|
• |
Change the fonts. |
Change the Execution |
• |
Change the keystrokes used. |
|
• Change the capitalization used. |
|
|
|
|
|
• Start, stop, and pause the execution. |
|
Change the Data |
• |
Input numbers when characters are expected. |
|
• |
Input characters when numbers are expected. |
• Input symbols and varied amounts of data input.
28Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Creating an Inventory of Java Fundamentals
Terminology
Key terms used in this lesson included:
•Quality Assurance testing
•Requirements analysis
•Test case
•Test execution
•Test cycle
29Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Creating an Inventory of Java Fundamentals
Summary
In this lesson, you should have learned how to:
•List and define Java Programming terminology
•Recognize and label Java programming constructs
•Identify incorrect Java programming syntax
•List programming tasks to design and implement a game using Java
•List five variations to include in programming Q/A tests
30Copyright © 2012, Oracle and/or its affiliates. All rights reserved.