Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

test

No description
by

Tuğba Karakaş

on 14 October 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of test

How to Improve Quality and Productivity Using Software Best Practices (Standards) 6 step approach Step-1 Determine the organizational business objectives
Profit
Non-profit
Core Product
Type of software to be produced.
Business
Web
Medical
Shrink Wrap Step-2 Map the present software engineering process to a maturity model and assess efficiency.

What process is being used today?

What process provides the most benefits to the organization? Step - 3 Perform a minimal assessment of where the organization is at on the maturity scale by process

Establish a standard rating form

Have 4 or 5 knowledgeable persons rate each process

Summarize sheets and obtain a quick assessment

If the organization is at the bottom of the maturity model, go to step 4; otherwise proceed to the appropriate step. Step-4 Select rudimentary software engineering standards. Typical ones are:

ISO 9126: Software Product Evaluation-Quality Characteristics and Guidelines for Their Use.

IEEE 829: Software Test Documentation

IEEE 830: Software Requirements Specification

Implement

Assess the process in 12 months Step-5 Select Software Engineering “framework” standards

Life Cycle: ISO/IEC 12207 Software life Cycle Processes

Process Improvement: ISO/IEC TR 15504 SPICE

Quality: ISO 90003 Part 3-Guidelines for the Application of ISO 9001 to the Development, Supply, and Maintenance of Software.

Implement

Assess the process in 12 months
Select Software Engineering unique process standards

ISO 14102: Evaluation and Selection of CASE
(Computer-Aided Software Engineering) Tools

Implement

Assess the process in 12 months Step-6 ISO/IEC 9126 Software engineering —

Product quality is an international standard for the evaluation of software quality.

The fundamental objective of this standard is to address some of the well known human biases that can adversely affect the delivery and perception of a software development project.

These biases include changing priorities after the start of a project or not having any clear definitions of "success."

By clarifying, then agreeing on the project priorities and subsequently converting abstract priorities (compliance) to measurable values (output data can be validated against schema X with zero intervention), ISO/IEC 9126 tries to develop a common understanding of the project's objectives and goals. The standard is divided into four parts:

quality model

external metrics

internal metrics

quality in use metrics. The quality model presented in the first part of the standard, ISO/IEC 9126-1, classifies software quality in a structured set of characteristics and sub-characteristics as follows:

Functionality
Reliability
Usability
Efficiency
Maintainability
Portability Internal metrics are those which do not rely on software execution (static measure) External metrics are applicable to running software. Quality in use metrics are only available when the final product is used in real conditions.
Ideally, the internal quality determines the external quality and external quality determines quality in use. A document describing
the scope,
approach,
resources,
and
schedule of intended testing activities. It identifies
test items,
the features to be tested,
the testing tasks,
who will do each task,
and
any risks requiring contingency planning.” a requirements specification for a software system – is a complete description of the behavior of a system to be developed and may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints), and are sometimes referred to as "ilities". Introduction
Purpose
Definitions
System overview
References
Overall description
Product perspective
System Interfaces
User Interfaces
Hardware interfaces
Software interfaces
Communication Interfaces
Memory Constraints
Operations
Site Adaptation Requirements
Product functions
User characteristics
Constraints, assumptions and dependencies
Specific requirements
External interface requirements
Functional requirements
Performance requirements
Design constraints
Standards Compliance
Logical database requirement
Software System attributes
Reliability
Availability
Security
Maintainability
Portability
Other requirements Software life cycle processes is an international standard for software lifecycle processes. It aims to be the standard that defines all the tasks required for developing and maintaining software. process with minimum coupling and maximum cohesion alım
tedarik
geliştirme
işletme
bakım acquisition
supply
developement
operation
maintenance bu 5 süreci faaliyetlere böler, faaliyetleri de görevlere böler
ve gerçekleştirilişleri üzerine şartlar koşar.
8 işlem süreci belirler. Belgeleyiş,
kurulum yapısı yönetimi,
kalite güvencesi,
doğrulayış,
ortak inceleyiş
ve sorun çözüş bunun yanında 4 kurumsal süreci belirler Yönetim
Altyapı
Geliştiriş
Eğitim address to capability ISO/IEC 15504 Information technology — Process assessment, also known as



is a set of technical standards documents for the computer software development process and related business management functions. The process dimension defines processes divided into the five process categories of: costumer/
supplier engineering management supporting organization For each process, ISO/IEC 15504 defines a capability level on the following scale: SPICE
(Software Process Improvement and Capability Evaluation -Determination-), Level Name
5 Optimizing process
4 Predictable process
3 Established process
2 Managed process
1 Performed process
0 Incomplete process The capability of processes is measured using process attributes. The international standard defines nine process attributes: 1.1 Process Performance
2.1 Performance Management
2.2 Work Product Management
3.1 Process Definition
3.2 Process Deployment
4.1 Process Measurement
4.2 Process Control
5.1 Process Innovation
5.2 Process Optimization Each process attribute is assessed on a four-point (N-P-L-F) rating scale:
Not achieved (0 - 15%)
Partially achieved (>15% - 50%)
Largely achieved (>50%- 85%)
Fully achieved (>85% - 100%). ISO/IEC 15504 provides a guide for performing an assessment.
This includes:
the assessment process
the model for the assessment
any tools used in the assessment ISO IEC 90003 explains how ISO 9001 2000 can be applied to software and related services. some parts from ISO 90003 4. Systemic Requirements and Guidelines
4.1 Establish a quality management system for software products
4.2 Document your software oriented quality system
4.2.1 Develop quality management system documents.
4.2.2 Prepare a quality management system manual.
4.2.3 Control quality management system documents.
4.2.4 Maintain quality management system records.
4.2.4.1 Prove that requirements have been met.
4.2.4.2 Prove that your operations are effective.
4.2.4.3 Establish a record retention approach.
5. Management Requirements and Guidelines
5.1 Support quality
5.2 Focus on your customers
5.3 Establish a quality policy
5.4 Perform quality planning
5.5 Control your quality system
5.5.1 Define responsibilities and authorities.
5.5.2 Appoint a management representative.
5.5.3 Support internal communications.
5.6 Perform management reviews
5.6.1 Review your quality management system.
5.6.2 Examine management review inputs.
5.6.3 Generate management review outputs. 6. Resource Requirements and Guidelines
6.1 Provide quality
6.2 Provide quality personnelresources
6.2.1 Use competent personnel.
6.2.2 Support competence.
6.3 Provide quality infrastructure
6.4 Provide quality environment 7. Realization Requirements and Guidelines
7.1 Control software product ralization planning
7.1.1 Use life cycle models to plan your work.
7.1.2 Carry out software quality planning.
7.2 Control customer processes
7.2.1 Identify your customers' software product requirements.
7.2.1.1 Identify customer related software requirements.
7.2.2 Review your customers' software product requirements.
7.2.2.1 Identify your organization's software product concerns.
7.2.2.2 Evaluate risks related to product requirements.
7.2.2.3 Appoint someone to represent the customer.
7.2.3 Communicate with your software customers.
7.2.3.1 Communicate with your software customers.
7.2.3.2 Communicate with customers during development.
7.2.3.3 Communicate during operations and maintenance.
7.3 Control software design and development
7.3.1 Plan product design and development.
7.3.1.1 Plan software design and development.
7.3.1.2 Plan review, verification, and validation activities.
7.3.2 Define software design and development inputs.
7.3.3 Generate software design and development outputs.
7.3.4 Carry out software design and development reviews.
7.3.5 Perform software design and development verifications.
7.3.6 Conduct software design and development validations.
7.3.6.1 Carry out software validation activities.
7.3.6.2 Carry out software testing activities.
7.3.7 Manage software design and development changes.
7.4 Control your purchasing function
7.4.1 Control purchasing process.
7.4.1.1 Control software purchasing process.
7.4.1.2 Control purchased parts and components.
7.4.2 Document product purchases.
7.4.3 Verify purchased products.
7.5 Manage production and service provision
7.5.1 Control production and service provision.7.5.1.1 Control software production and service.7.5.1.2 Control software build and release.7.5.1.3 Control software replication activities.7.5.1.4 Control software delivery activities.7.5.1.5 Control software installation activities.7.5.1.6 Control your software operations.7.5.1.7 Control software maintenance activities.
7.5.2 Validate production and service provision.
7.5.2 Validate production and service provision
7.5.3 Identify and track your products.7.5.3.1 Identify and trace software products.7.5.3.2 Use software configuration management.7.5.3.3 Establish a process to trace software.
7.5.4 Protect property supplied by customers.
7.5.5 Preserve your products and components.
7.6 Control monitoring devices 8. Remedial Requirements and Guidelines
8.1 Carry out remedial processes
8.2 Monitor and measure quality
8.2.1 Monitor and measure customer satisfaction.
8.2.2 Plan and perform regular internal audits.
8.2.3 Monitor and measure quality processes.
8.2.4 Monitor and measure product characteristics.
8.3 Control your nonconforming software products
8.4 Analyze quality information
8.5 Take required remedial actions
8.5.1 Maintain your quality management system.
8.5.2 Correct actual nonconformities.
8.5.3 Prevent potential nonconformities. ISO/IEC 14102:2008 defines both a set of processes and a structured set of CASE tool characteristics for use in the technical evaluation and the ultimate selection of a CASE tool. It follows the software product evaluation model defined in ISO/IEC 14598-5:1998. larger set of characteristics is organized into four groups:

characteristics related to life cycle process functionality;
characteristics related to CASE tool usage functionality;
general quality characteristics;
general characteristics not related to quality. This grouping provides a more manageable approach to the overall evaluation and selection process. The objective of the technical evaluation process is to provide quantitative results on which the final selection can be based. Measurement assigns numbers (or other ratings) to attributes of entities; a major activity of evaluation is to obtain these measurements for use in selection. The final selection results should aim to achieve objectivity, repeatability and impartiality. These objectives and the confidence in the outcomes will in part depend on the resources allocated to the overall evaluation and selection process. The user of ISO/IEC 14102:2008 is asked to deal with these issues at an early stage.To be widely acceptable, these CASE tool evaluation and selection processes must be of value to the users of CASE tools, and to the suppliers of CASE to the community at large. The information outlined in ISO/IEC 14102:2008 should lead to more cost effective selections of CASE tools and to a greater uniformity in how CASE tool functions and features are described. ISO 12207: Yazılım Yaşam Döngüsü Süreci

Yazılım Yasam Döngüsü, Gelistirme ve Sürdürülebilirlik yazılımları için tüm gerekli durumları açıklayacak bir standard olmayı amaçlar.

En az baglantı ile en cok birlesim

alımtedarikgeliştirmeişletme bakım

acquisitionsupplydevelopementoperationmaintenance

bu 5 süreci faaliyetlere böler, faaliyetleri de görevlere böler ve gerçeklesştirilisşleri üzerine şsartlar kosşar. 8 işslem süreci belirler..

Belgeleyiş,kurulum yapısı yönetimi, kalite güvencesi,doğrulayış,ortak inceleyiş ve sorun çözüş

bunun yanında 4 kurumsal süreci belirler

YönetimAltyapıGelisştirişsEgğitim
Full transcript