Phase 3 - Task 1 Task Type: Discussion Board Deliverable Length: 400–600 words + 2 responses (100–200 words each) Points Possible: 75 Due Date: 1/25/2015 11:59:59 PM Primary Discussion Response is due by Wednesday (11:59:59pm Central), Peer Responses are due by Sunday (11:59:59pm Central). Primary Task Response: Within the Discussion Board area, write 400–600 words that respond to the following questions with your thoughts, ideas, and comments. This will be the foundation for future discussions with your classmates. Be substantive and clear, and use examples to reinforce your ideas. Library Research Assignment The next major phase in software development life cycle (SDLC) is testing. Quality assurance methods and testing help support this phase. Investigate the library and Internet for information on the various tests that should be performed at different junctures of development and integration. Research software-related quality assurance tools as well. · Compare and contrast at least 4 tests that occur between the span of development and final integration into a production environment (description of each and how they support overall quality of the system or application). · Why is software quality assurance important in system development? · What are some of the software quality assurance methods that you would embrace for ensuring quality in the application that you are developing, and why? Responses to Other Students: Respond to at least 2 of your fellow classmates with a reply of 100–200 words about their Primary Task Response regarding items you found to be compelling and enlightening. To help you with your discussion, please consider the following questions: · What did you learn from your classmate's posting? · What additional questions do you have after reading the posting? · What clarification do you need regarding the posting? · What differences or similarities do you see between your posting and other classmates' postings? For assistance with your assignment, please use your text, Web resources, and all course materials. Course Materials Phase 3 - Task 2 Task Type: Individual Project Deliverable Length: 2–3 new pages Points Possible: 100 Due Date: 1/26/2015 11:59:59 PM Weekly tasks or assignments (Individual or Group Projects) will be due by Monday, and late submissions will be assigned a late penalty in accordance with the late penalty policy found in the syllabus. NOTE: All submission posting times are based on midnight Central Time. Testing and quality assurance is also an important phase within the software development life cycle (SDLC); however, it can start as early as the design phase and continue into deployment. Planning for these during the design phase and executing during development and implementation is critical and could halt final deployment until discovered errors are corrected. Assignment For this assignment, you will develop a plan for at least 3 types of tests, and describe the quality controls that you pla.

1. Phase 3 - Task 1
Task Type:
Discussion Board
Deliverable Length:
400–600 words + 2 responses (100–200 words each)
Points Possible:
75
Due Date:
1/25/2015 11:59:59 PM
Primary Discussion Response is due by Wednesday (11:59:59pm
Central), Peer Responses are due by Sunday (11:59:59pm
Central).
Primary Task Response: Within the Discussion Board area,
write 400–600 words that respond to the following questions
with your thoughts, ideas, and comments. This will be the
foundation for future discussions with your classmates. Be
substantive and clear, and use examples to reinforce your ideas.
Library Research Assignment
The next major phase in software development life cycle
(SDLC) is testing. Quality assurance methods and testing help
support this phase.
Investigate the library and Internet for information on the
various tests that should be performed at different junctures of
development and integration. Research software-related quality
assurance tools as well.
· Compare and contrast at least 4 tests that occur between the
span of development and final integration into a production
environment (description of each and how they support overall
quality of the system or application).
· Why is software quality assurance important in system
development?
· What are some of the software quality assurance methods that
you would embrace for ensuring quality in the application that

2. you are developing, and why?
Responses to Other Students: Respond to at least 2 of your
fellow classmates with a reply of 100–200 words about their
Primary Task Response regarding items you found to be
compelling and enlightening. To help you with your discussion,
please consider the following questions:
· What did you learn from your classmate's posting?
· What additional questions do you have after reading the
posting?
· What clarification do you need regarding the posting?
· What differences or similarities do you see between your
posting and other classmates' postings?
For assistance with your assignment, please use your text, Web
resources, and all course materials.
Course Materials
Phase 3 - Task 2
Task Type:
Individual Project
Deliverable Length:
2–3 new pages
Points Possible:
100
Due Date:
1/26/2015 11:59:59 PM
Weekly tasks or assignments (Individual or Group Projects) will
be due by Monday, and late submissions will be assigned a late
penalty in accordance with the late penalty policy found in the
syllabus. NOTE: All submission posting times are based on
midnight Central Time.
Testing and quality assurance is also an important phase within
the software development life cycle (SDLC); however, it can
start as early as the design phase and continue into

3. deployment. Planning for these during the design phase and
executing during development and implementation is critical
and could halt final deployment until discovered errors are
corrected.
Assignment
For this assignment, you will develop a plan for at least 3 types
of tests, and describe the quality controls that you plan to
perform quality assurance.
The project deliverables are as follows:
· Update the System Requirements, Design, and Implementation
Specification title page with the new date.
· Update the previously completed sections based on the
instructor's feedback.
· Test and Quality Assurance Plan
· Develop a plan for unit testing. Include specific application
functions that will be tested and how the tests will be
conducted.
· Develop a plan for system testing. Include areas that you will
test within both the application and a system as a whole and
how errors will be tracked and reported.
· Develop a plan for user acceptance testing. Include key
stakeholders who should perform the test and how they will
record any issues that they find.
· Develop a quality assurance plan. Include specific quality
assurance methods or control, what their purpose is, and in
which phase they will be utilized.
· Name the document "yourname_IT425_IP3.doc."
Please submit your assignment.
For assistance with your assignment, please use your text, Web
resources, and all course materials.
Course Materials
Presentation

4. Testing and Quality Assurance Components
Testing and Quality Assurance Process
Testing and quality assurance are an important phase within the
systems development life cycle (SDLC). The following is an
overview of this phase of the development and implementation
process:
· Types of testing:
· Unit or component test: This is testing that is conducted on
individual components of a system, such as a piece of code,
program, or module, to check that the functions that each
component is supposed to perform are correct.
· Integration test: This is testing is conducted at a subsystem
level, or a set of components, to make sure the functions or the
processes that they support are functioning properly.
· System test: This is testing is usually conducted after several
other phases of testing have been completed, including
component or unit testing, user interface testing, integration
testing, and so forth. This is a complete test of both software
and hardware specifications.
· User acceptance test: This is testing that is conducted by the
customer to ensure that it meets the specified requirements by
satisfying the acceptance criteria.
· Other types: These can include beta tests, compliance tests,
conversion tests, interface tests, performance tests, and many
others.
· Test planning components and guidelines:
· Test cases: These are scripts for the tests that will occur.
· Acceptance criteria: These are established from requirements
in measurable or testable terms.
· Quality: This includes goals such as reliability, efficiency,
accuracy, and ease of use.
· Methodologies: These are types of tests and environments
where the tests will be performed.
· Testing environment: This includes the hardware, software,
and test tools required for performing the tests.
· Testers: These are the personnel who will conduct the tests.

5. · Error reporting and tracking: This is a mechanism to record
and track errors.
· Completion criteria: These are requirements that must be met
for sign-off on the particular test phase.
· Detailed test schedule: This is a detailed project plan for
testing.
· Testing life cycle steps:
· Requirement phase: This includes tests that are tied to
requirements.
· Test planning phase: Tests are planned in parallel with project
planning.
· Test analysis phase: This is where people analyze the tests that
are needed.
· Test design phase: This is where people design tests in
parallel to system design.
· Test verification: This is where people verify that the test
scenarios or case designs provide full test coverage.
· Regression testing: This is where people verify that the
individual components work together as a system.
· Test execution phase: This is where various tests are run.
· Result analysis phase: This is where people evaluate the
results of the test.
· Bug tracking and reporting phase: In this phase, any errors
need to be recorded and tracked.
· Rework phase: This phase fixes the errors that need to be
fixed and retested.
· Final test and implementation phase: This is the final system
test in operation before go-live, and it includes another test
once you are live.
· Quality assurance components:
· Standards: These are the standards surrounding
documentation, reviews, coding, comments, and testing.
· Tools and techniques: These are the tools that ensure that
quality standards are met.
· Measures and metrics: These are the measurements and
metrics to track how the quality standards are being met.

6. · Controls and sign-offs: These are the controls that are in place
to not exit a phase until the final sign-off and approval.
References
Exforsys, Inc. (2008). SQA planning standards. Retrieved
from http://www.exforsys.com/tutorials/sqa/sqa-planning/1.html
Kekare, H. (2011). Types of software testing. Retrieved from
the Buzzle Web site: http://www.buzzle.com/articles/types-of-
software-testing.html
Activity
Software Test Plan Template
Click here for a variety of templates designed around software
testing. The Test Plan Template can be modified to fit any
project. Once the documents are downloaded, the colored text
will guide you through the process of each section of the
template.
There are other templates that may be useful for the testing
phase of any software implementation.
Reference
The Software Tester. (2009). Software testing templates.
Retrieved from http://www.the-software-
tester.com/templates.html
Activity
Software Test Plan Template
Click here for a series of tutorials on quality assurance. The
tutorials begin at the bottom of the page and cover the steps that
are needed to put together a quality assurance plan that includes
the appropriate standards.
Review the tutorials in the SQA Planning and SQA Planning
Standards sections.
Reference
Exforsys, Inc. (2008). Software quality assurance training.
Retrieved from http://www.exforsys.com/tutorials/sqa/software-
quality-assurance-training.html

7. Activity
Future of Software Testing
Click here to view a podcast discussing the evolution and future
of software testing methods.
Reference
Shostack, A. (2013). Future of software testing [Video].
Retrieved from the Informit Web
site: http://www.informit.com/podcasts/episode.aspx?e=0bad6f6
5-fcff-4730-8044-43df7cd421fb
Activity
Quality Assurance Process
Click here to view a video explaining the phases of quality
assurance and testing. This video discusses the initiation,
planning, and execution phases.
Reference
Magenic Tech. (2011). Quality assurance and testing: Our
method - process[Video]. Retrieved from the YouTube Web
site:http://www.youtube.com/watch?v=v8nP8W7DhJ0
Article
Testing Life Cycle
Testing is an important phase within the software development
life cycle (SDLC). The testing life cycle should include the
following steps:
· Requirement phase
· Test planning phase
· Test analysis phase
· Test design phase
· Test verification
· Regression testing
· Test execution phase
· Result analysis phase
· Bug tracking and reporting phase
· Rework phase
· Final test and implementation phase

8. Resource Links
(http://www.youtube.com/watch?v=Vdm1Lh540LM&playnext=1
&list=PLDC2A0C8D2EC934C7&feature=results_video)
This tutorial video covers what a Test Plan / Strategy Document
is and how do you create one from scratch.
(http://www.youtube.com/watch?v=14BAMCL1mgo&list=PLDC
2A0C8D2EC934C7)
This video compares Software/System Development Life Cycle
(SDLC) to the Software Test Life Cycle (STLC).
(http://www.9000world.com/iso-9000-quality-
manual.html?gclid=CMvF3rneto0CFSCTWAodvwJgMg)
The ISO 9000 quality assurance standard is a good example of
quality assurance.
(http://www.critech.com/vv.htm)
Information on verification and validation of requirements
Phase 2 - Task 1
Task Type:
Discussion Board
Deliverable Length:
400–600 words + 2 responses (100–200 words each)
Points Possible:
75
Due Date:
1/18/2015 11:59:59 PM
Primary Discussion Response is due by Wednesday (11:59:59pm
Central), Peer Responses are due by Sunday (11:59:59pm
Central).

9. Primary Task Response: Within the Discussion Board area,
write 400–600 words that respond to the following questions
with your thoughts, ideas, and comments. This will be the
foundation for future discussions with your classmates. Be
substantive and clear, and use examples to reinforce your ideas.
Library Research Assignment
Translating detailed requirements into a design is the next very
important step. An integrated set of computer-aided software
engineering (CASE) tools can be very useful in modeling and
documenting a software application or system.
Investigate the library and Internet for information on at least 5
CASE tools such as unified modeling language (UML),
functional decomposition diagrams, data flow diagrams, object
diagrams, entity-relationship (E-R) diagrams, class diagrams,
and structure charts.
· Compare and contrast 5 of the CASE modeling tools by giving
a brief description, including strengths and weaknesses.
· Based on your research, which subset or individual CASE
modeling tool or tools do you plan to use to develop the design
for your project in this class, and why?
Responses to Other Students: Respond to at least 2 of your
fellow classmates with a reply of 100–200 words about their
Primary Task Response regarding items you found to be
compelling and enlightening. To help you with your discussion,
please consider the following questions:
· What did you learn from your classmate's posting?
· What additional questions do you have after reading the
posting?
· What clarification do you need regarding the posting?
· What differences or similarities do you see between your
posting and other classmates' postings?
For assistance with your assignment, please use your text, Web
resources, and all course materials.
Course Materials

10. Phase 2 - Task 2
Task Type:
Individual Project
Deliverable Length:
2–3 new pages
Points Possible:
100
Due Date:
1/19/2015 11:59:59 PM
Weekly tasks or assignments (Individual or Group Projects) will
be due by Monday, and late submissions will be assigned a late
penalty in accordance with the late penalty policy found in the
syllabus. NOTE: All submission posting times are based
on midnight Central Time.
At this point, you are ready to execute the next phase in system
development life cycle (SDLC), which is the design phase.
Exploiting the research that you have performed in this week’s
Discussion Board on the set of modeling tools, document the
design for the application project that you selected.
Assignment
For this assignment, you will use Visio Software Application to
develop the design employing the following computer-aided
software engineering (CASE) modeling tools:
· Use case
· Functional decomposition diagram
· Entity-relationship (E-R) diagram, data flow diagram (DF), or
class diagram
· Sequence diagram
· Mock-up or storyboard of the user interface screens
The project deliverables are as follows:
· Update the System Requirements, Design, and Implementation
Specification title page with new date.
· Update the previously completed sections based on the
instructor's feedback.

11. · System or Application Design
· Develop a high-level use case to represent the application as a
whole.
· Develop a functional decomposition diagram to show all of the
functions that the system or application will support.
· Develop an E-R diagram, class diagram, or a data flow
diagram that effectively represents the data that are required for
your application or system.
· Develop a sequence diagram to represent the timing of various
activities within the application or system.
· Develop a mock-up or storyboard for the high-level interface
screens.
· Name the document "yourname_IT425_IP2.doc."
Please submit your assignment.
For assistance with your assignment, please use your text, Web
resources, and all course materials.
Course Materials
Presentation
Development Model Comparisons
The following is a comparison of five computer-aided software
engineering (CASE) diagrams, including their components and a
description of their strengths and weakness:
Use Case Diagram
The use case diagram has the following components:
· It uses cases to show the sequence of actions.
· It shows actors, such as person, group, organization, or
external system that play a role in interactions within the
system.
· Associations or communications represent interactions
described by the model.
· System boundaries show the area for functionality and scope.
This diagram is described as a system or software development

12. life cycle (SLDC) with defined phases.
The diagram has the following strengths:
· It provides a very high level of representation of the system or
application as a whole, including scope.
· Is a very good communication vehicle for capturing user
requirements and communicating them to the users and
stakeholders.
The weakness of this diagram is that it requires other types of
diagramming techniques to provide the drill-down detail.
Object Diagrams
The object diagram can be described as a rapid application
development (RAD) that supports faster software development
and uses a quick requirements-gathering phase. It goes into
prototyping to further define requirements based upon user
feedback on the prototype.
The strength of this diagram is the time to market is greatly
reduced for graphical user interface (GUI) or Web-based
applications.
Because it is so quick, proper testing is not always conducted.
The prototypes are generally throw-away code.
The Data Flow Diagrams
The data flow diagram (DFD) has the following components:
· It uses squares or ovals to represent external entities,
terminators, sources, or sink.
· Circles or rounded rectangles represent processes within
system.
· Arrows represent data flows.
· Open-ended rectangles represent data stores.
Data flow diagrams illustrate the processes, data stores, and
external entities in a system and the connecting data flows.
Strengths of this model include the following:
· It models real-world entities and methods.
· It is excellent in supporting reuse.
· It uses class diagrams to represent the model.
To help the customers understand the requirements that they
share, this model is complex to develop.

13. Entity-Relationship Diagram
The entity-relationship diagram (ERD) has the following
components:
· Entities represent objects in the real world.
· Relationships represent connections between entities.
· An associative object type indicator can represent both an
object and a relationship.
· The subtype and supertype indicator represent subcategories
by a relationship.
Entity-relationship diagrams are a form of a network model to
represent the data within a system or application. Relationships
show how data are represented by entities and logically related.
The strength of this diagram shows the relationship between the
various entities within a system.
This diagram does not reflect sequence or activities within the
system—only the data.
Structure Charts
The structure chart has the following components:
· Boxes represent functions or modules.
· Lines represent the linkage between functions and modules.
This diagram is a top-down modular design that depicts
identifiable functions and the modules underneath or shows the
functional decomposition.
The strength of this diagram is to provide a way of decomposing
an application or system into manageable modules.
This diagram does not provide a lot of detail about the actual
functions that will be performed in the system.
Reference
Techopedia. (2013) Unified modeling language (UML).
Retrieved
from http://www.techopedia.com/definition/3243/unified-
modeling-language-uml
Activity
Computer-Aided Software Engineering Tools in the
Development Process

14. Click here to view a video defining computer-aided software
engineering (CASE) tools and how they fit into the software life
cycle development process.
Reference
Webb, P. (2009). Computer aided software engineering [Video].
Select Business
Solution
s. Retrieved from the YouTube Web
site: http://www.youtube.com/watch?v=hHvypTnvF5E
Activity
Computer-Aided Software Engineering Tool Diagrams
Click here to view a tutorial that starts with a use-case diagram
and elaborates on it into activity, class, sequence, and
communication diagrams. This is a great initial tutorial to help
understand the relationships of the various Unified Modeling
Language (UML) diagrams.
Reference
Kench, E. (2009). UML tutorial [Video]. Retrieved from the
YouTube Web
site: http://www.youtube.com/watch?v=RMuMz5hQMf4
Activity
UML Diagram Quiz

15. Click on the Web links below for a set of two interactive
quizzes that test UML knowledge. The user answers questions
by dragging components to the various diagrams, and the quiz
gives you real-time feedback and coaching if you get the wrong
answer.
The Home Page link gives you information on the site and the
quizzes.
The Quiz 1 and Quiz 2 links will take you to the respective
quizzes.
Reference
The Open University. (2013). iCMA quizzes on UML diagrams.
Retrieved from the OpenUniversity Web
site:http://www.open.ac.uk/opencetl/centre-open-learning-
mathematics-science-computing-and-technology/activities-
projects/assessment/icma-quizzes-uml-diagrams
Activity
Complete UML Tutorial
Click here for a tutorial that provides a better understanding of
Unified Modeling Language (UML). In addition to an overview,
building blocks, and modeling types, there are tutorials that
walk you through the creation of diagrams. These diagrams
include: standard diagrams, class diagrams, object diagrams,
component diagrams, deployment diagrams, use case diagrams,
interaction diagrams, state chart diagrams, and activity

16. diagrams.
The various topics as well as the diagram tutorials can be
accessed using the navigation bar on the left side of the Web
site.
Reference
TutorialsPoint. (2013). UML tutorial. Retrieved from the
TutorialsPoint Web
site: http://www.tutorialspoint.com/uml/index.htm
Article
CASE Tool Environment
Computer-aided software engineering (CASE) tools are a
collection of software that is used to automate the various
phases of the systems development life cycle (SDLC). The
following image shows various classifications of CASE tools
that can be used together or separately.
The CASE tool repository documentation and models are as
follows:
· Project management
· Analysis and design
· Modeling tools
· Documentation tools
· Prototyping tools
· Coding support
· Configuration management

17. · Query and report generator
· Backup and recovery
· Export and import
Article
Sample Use Case Diagram
The design phase of the system development life cycle (SDLC)
necessitates translating the detailed requirements into a design.
Computer-aided software engineering (CASE) tools are useful
in modeling and documenting this phase. One such CASE tool is
a use case diagram.
The image shows an
For this assignment, you will develop a plan for at least 3 types
of tests, and describe the quality controls that you plan to
perform quality assurance.
The project deliverables are as follows:
Objective: Examine the steps and types of testing and quality
assurance needed in software development.
Update the system requirements, design, and implementation
specification title page with the new date.

18. Update the previously completed sections based on the
instructors feedback.
Test and Quality Assurance Plan
1) Develop a plan for unit testing. Include specific application
functions that will be tested and how the tests will be
conducted.
2) Develop a plan for system testing. Include areas that you will
test within both the application and a system as a whole and
how errors will be tracked and reported.
3) Develop a plan for user acceptance testing. Include key
stakeholders who should perform the test and how they will
record any issues that they find.
4) Develop a quality assurance plan. Include specific quality
assurance methods or control, what their purpose is, and in
which phase they will be utilized.
will you need me to send the earlier assignments so you can
build on this one? The model was on "Make Reservation" in a
hotel reservation system