MODULE 8-SOFTWARE REVOLUTION

                                              You may leave a response  :)

MODULE 7 - SOFTWARE QUALITY MANAGEMENT

WHAT IS QUALITY?  ---------> Quality of design

                                      ---------> Quality of conformance

                                      ---------> user satisfaction

DEFINITION                ---------> Management principles

                                       ---------> Required level of quality achieved

                                       ---------> Quality culture

SCOPE                           ---------> Large complex systems

                                        ---------> Documentation

 QUALITY DIMENSIONS AND FACTORS ---------> Efficiently

                                                                         ---------> Usability

                                                                         ---------> Maintability

                                                                         ---------> Realibility

ACHIEVING SOFTWARE QUALITY           ---------> Quality Assurance

                                                                        ---------> Quality Control

                                                                        ---------> Software Engineering method

                                                                        ---------> Project management technique

SQA GROUP ---------> Prepare SQA plan

                       ---------> Software process description

                       ---------> Review software engineering process

                       ---------> Audit desingnated software

                       ---------> Ensure work according to procedure

                       ---------> Record non compliance

SQA GOALS  ---------> Requirements quality

                        ---------> Quality control

                        ---------> Code quality

                        ---------> Design quality

MODULE 6 - VERICATION & VALIDATION

VERICATION & VALIDATION

Verification 
 -  the set of tasks that ensure that software correctly implements a specific function.

Validation 
 -  A different set of tasks that ensure that the software that has been built is traceable to customer requirements

Two principal objectives:

•    Discover defects in a system;
•      Assess whether or not the system is useful and useable in an operational situation.

Activities include :

Technical reviews

Quality and configuration audits

Performance monitoring

Simulation                                        SQA Activities

Feasibility study

Documentation review

Database review

Algorithm analysis

_____________________________________________________________________

Development testing

Qualification testing                                                 Testing         

Acceptance testing

Installation testing

SOFTWARE TESTING

- WHO TEST THE SOFTWARE ------­- DEVELOPER ( Understand the system BUT will test GENTLY & driven by ‘DELIVERY’)

                                                   -------- INDEPENDENT TESTER ( must learn about the system BUT          will attempt to break it and is driven by quality)

INTEGRATION TESTING

Incremental integration testing strategies:

• Bottom-up integration
• Top – down integration 
• Regression testing
• Smoke testing

VALIDATION TESTING


1)  Validation-Test Criteria:

• all functional requirements are satisfied,
• all behavior characteristics are achieved,
• all content is accurate and properly presented,
• all performance requirements are attained, documentation is correct, and
• usability and other requirements are met.

2)      Acceptance Tests

Alpha test – version of the complete software is tested by customer under the supervision of the developer at the developer’s site

Beta test – version of the complete software is tested by customer at his or her own site without the developer being present

SYSTEM TESTING

Types of system tests:

• Recovery Testing
• Security Testing
• Stress Testing
• Performance Testing
• Deployment Testing

TEST-CASE DESIGN

Software is tested from2 perspectives:

 ‘White-box’ testing 

focus on the program control structure (internal program logic).

-Test cases are derived to ensure that all statements in the program have been executed at least once during testing and all logical conditions have been exercised.

-Performed early in the testing process

 ‘Black-box’ testing

-Examines some fundamental aspect of a system with little regard for the internal logical structure of the software

-Performed during later stages of testing

DERIVING TEST CASES

      NOTES  : PLEASE DOUBLE-CLICK AT THIS DIAGRAM TO MAKE IT LARGE .TQ

MODULE 5 - IMPLEMENTATION AND CODING

MODULE 4 - SOFTWARE DESIGN

DESIGN PRINCIPLE

• ·         DESIGN ! = CODES
• ·         REVIEW TO REDUCE CONCEPTUAL ERROR
• ·         DO NOT REINVENT THE WHEEL
• ·         DESIGN PROCESS SHOULD NOT SUFFER FROM ‘TUNNEL VISION’

DESIGN EVALUATION

• ·         DESIGN Q IS PEOPLE SENSITIVE
• ·         DESIGN Q IS CHARGE SPECIFIC
• ·         DESIGN Q IS UNPRIDICTABLE
• ·         MODIFICATION AND MAINTENANCE TIME MORE IMPORTANT THAN CREATION   TIME

DESIGN CONCEPT

• ·         ABSTRACTION
• ·         ARCHITECTURE
• ·         PATTERN
• ·         SEPERATION OF CONCERN
• ·         MODULARITY
• ·         OO DESIGN CONCEPT
• ·         REFACTORING
• ·         DESIGN CLASSES

FOUR DESIGN ELEMENT

• ·         DATA OR CLASS DESIGN
• ·         ARCHITECTURE DESIGN
• ·         INTERFACE DESIGN
• ·         COMPONENT-LEVEL DESIGN

QUIZ 3

On 13 July 2011 on Wednesday during class time we had our quiz 3 based on module 4 (software design) and chapter 5 ( implementation and coding) . The format of our quiz is structure question and have 4 question that must we answer . This quiz takes 30 minutes for answer it and all student trying so hard to answer it . so study hard and smart for our next quiz :) GOOD LUCK !