WASE SQM

Lecture-6
Course No. : SEWP ZG661

Title : Software standards

& Inspection
DATE :6th Sep,2009

Prof.N.Prasanna Balaji
B.E(CSC),M.Tech(IT),MBA(OM),Ph.D(ERP)
LMCSI, LMISTE, MIEEE, MAIMA

email:[email protected]
 REPRESENTATIVE SOFTWARE STANDARDS

• Software Quality Assurance Plans

• Software Development notebooks
• Software development plans
• Software reviews and audits
• Software requirements
• Software design documentation
• Software test plans
• Software Quality Assurance reviews
• Software Configuration Management
• Problem reporting/corrective action
• Software Documentation
 Definitions

• 1.Authorative direction on what is to be done

– Policy: A governing principle, typically used as the

basis for regulations, procedures, or standards and generally
started by the highest authority in the organization.
– Regulation: A rule, law, or instruction, typically established
by some legislative or regulatory body with penalties for
noncompliance.
– Specification: The precise and verifiable description of the
characteristics of a product. A Process specification would
similarly define a method ,procedure, or process to be used in
performing a task. Specifications are often produced by technical
experts as part of a contractual agreement.
• 2. The characterization of how a task is to be performed
or the required characteristics of the result.

– Guidelines: A suggested practice, method, or

procedure, typically issued by some authority.
– Procedure: A defined way to do something ,generally
embodied in a procedures manual. Alternatively, as in
programs, a named portion of a computer program
that performs a specific task.
– Standard: A rule or basis for comparison that is used
to assess size, content, or value, typically established
by practice or by a designated standards body.
 3.4.0
TRW Software Development
Policies

S/W Integration, S/W Product

S/W Development
S/W Specifications Test, and
Practices Management and
and reviews Operations
3.4.1 Requirements Acceptance
3.4.7 Top-Down 3.4.11 Unit Test
Specification
Design 3.4.15 End Product
3.4.2 Requirements Plan
3.4.8 Unit
Review and Acceptance
Development 3.4.12 System
Acceptance
Folders Plan
3.4.3 Design Integration
3.4.9 Design Walk-
Specification 3.4.16 Documentation
Throughs And Test
(Preliminary)
3.4.10 Programming 3.4.16 Configuration
3.4.4 Preliminary 3.4.13 Accept,
Standards
Design Review Management
3.4.5 Design Test, Plan
Specification 3.4.17 Quality
and
(Detailed) Assurance
3.4.6 Critical Procedures
Design Review 3.4.14 User’s
Manual

TRW Software Product Standards

* Programming Standards * Documentation Standards * Naming and Numbering *Configuration Management
Procedures
 REPRESENTATIVE SOFTWARE PROCEDURES

• Auditing Software development notebooks

• Reviewing a Software development Plan
• Conducting Software Reviews
• Conducting software audits
• Reviewing Software requirements
• Reviewing Software design documents
• Reviewing software test plans
• Auditing the software testing process
• Conducting SOA reviews
• Performing Software Configuration Management
• Auditing Software Configuration Management Systems
• Handling Problem reporting/corrective action
• Auditing problem reporting/correction action systems
• Reviewing Software documentation
• 3. The ways in which tasks are accomplished

– Convention: A general agreement on practices,

methods, or procedures, typically arrived at by explicit
agreement.
– Method: A regular. orderly procedure or process for
performing a task, typically defined by an expert.
– Practice: A defined way to perform some activity,
generally involving a sequence of methods or
procedures designed to accomplish a specified result,
and typically established by technical specialties.
 Benefits of Standards

While there is little quantitative evidence

that supports the use of standards, Most
experienced software managers can cite at least
one standard that was key to a a program's
success. In the case of IBM’s OS/360,a standard
assembler language permitted cooperative
development by 13 laboratories in 6 countries.
The alter use of a standard higher-level language
(PLS) also saved a great deal of money in
development and support.
 Benefits of Standards

Thayer has surveyed software

managers to determine their views on the key
software problems and their most effective
solutions. Of all the solutions listed, the use and
enforcement of standards and procedures ranked
first. Not surprisingly, Thayer also found that
standards were most effective when the project
manager personally implemented them on a
project basis. While standards alone will not make
the difference between project success and
failure, they clearly help.
 IBM FSD SOFTWARE DESIGN PRACTICES
• Systematic Programming Practices
• Logical expression Prescribes mathematics-based techniques for
precise expression and reasoning that apply to all
phases of software development
• Program expressionDefines control, data, and program structure
recording program designs
• Program design Specifies a process of stepwise refinement for
recording structures program designs
• Program design Prescribes function-theoretic techniques for proving Verification
the correctness of structured program
• Systematic Design Practices
• Data design Specifies the use of abstract data objects and
operations in a high level design framework
• Modular design Defines techniques for designing synchronous
software systems based on state machines and design modules
• Advanced design practices
Software systems Defines a process based on state machine for creating
a Specification specification as the comer stone documentation of a
software system
Real-time design Defines a stage wise process for designing
asynchronous software to achieve correct concurrent
operation ,with optimization to meet real-time processing
requirement.
IBM FSD LANGUAGE RECOMMENDATION FOR CLASSES OF SOFTWARE
PRODUCTS

• Language Recommendation Class of Software

• High-order language (HOL) Program development and generation
Compiler/assembler
Link editor/loader
Utilities
Library Support
Data reduction
Applications
Program
HOL with assembly assist
development and generation

Hardware simulation
System simulation
Diagnostics
Assembly with HOL elements

Executive
Assembly

Data recording
/measurement
Microcode