Управлять IT-проектами, как играть в регби
http://www.youtube.com/watch?feature=player_embedded&v=kdhfyJnHqPU#
пʼятниця, 23 грудня 2011 р.
Test Engineer Professional positions and responsibilities
Junior Test Engineer
Responsibilities:
∙ Ad-hoc Testing, Functional Testing, GUI Testing
∙ Bug Finding and Tracking
∙ Test Case Development
∙ Requirements Analysis/ Testing
Test Engineer
Responsibilities:
∙ Ad-hoc Testing, Functional Testing, GUI Testing
∙ Bug Finding and Tracking
∙ Test Case Development
∙ Requirements Analysis/ Testing
∙ Test Report Development
∙ Traceability Matrix Development and Tracking
∙ Junior Test Engineer Leading
∙ Test Team Leading (1-3 Junior/Test Engineers)
Senior Test Engineer
Responsibilities:
∙ Ad-hoc Testing, Functional Testing, GUI Testing
∙ Bug Finding and Tracking
∙ Test Case Development
∙ Requirements Analysis/ Testing
∙ Test Report Development
∙ Traceability Matrix Development and Tracking
∙ Test Team Leading ( 1- 5 Junior/Test Engineers)
∙ Test Plan Development
∙ Test Project Management
∙ Communication with Customer/ Dev Team
QA Engineer
Responsibilities:
∙ Ad-hoc Testing, Functional Testing, GUI Testing
∙ Bug Finding and Tracking
∙ Requirements Analysis/Testing
∙ Test Team Leading ( 1- 5 Junior/Test Engineers)
∙ Required Test Documentation Development
∙ Test Project Management
∙ Communication with Customer/ Dev Team
∙ Test Process Development and Controlling
∙ Risks Monitoring
Senior QA Engineer
Responsibilities:
∙ Testing
∙ Bug Finding and Tracking
∙ Requirements Analysis/Testing
∙ Test Teams Leading
∙ Required Test Documentation Development
∙ Project Management
∙ Risks Mitigation, Monitoring and Management
∙ Project Process Tracking and Improvement
Responsibilities:
∙ Ad-hoc Testing, Functional Testing, GUI Testing
∙ Bug Finding and Tracking
∙ Test Case Development
∙ Requirements Analysis/ Testing
Test Engineer
Responsibilities:
∙ Ad-hoc Testing, Functional Testing, GUI Testing
∙ Bug Finding and Tracking
∙ Test Case Development
∙ Requirements Analysis/ Testing
∙ Test Report Development
∙ Traceability Matrix Development and Tracking
∙ Junior Test Engineer Leading
∙ Test Team Leading (1-3 Junior/Test Engineers)
Senior Test Engineer
Responsibilities:
∙ Ad-hoc Testing, Functional Testing, GUI Testing
∙ Bug Finding and Tracking
∙ Test Case Development
∙ Requirements Analysis/ Testing
∙ Test Report Development
∙ Traceability Matrix Development and Tracking
∙ Test Team Leading ( 1- 5 Junior/Test Engineers)
∙ Test Plan Development
∙ Test Project Management
∙ Communication with Customer/ Dev Team
QA Engineer
Responsibilities:
∙ Ad-hoc Testing, Functional Testing, GUI Testing
∙ Bug Finding and Tracking
∙ Requirements Analysis/Testing
∙ Test Team Leading ( 1- 5 Junior/Test Engineers)
∙ Required Test Documentation Development
∙ Test Project Management
∙ Communication with Customer/ Dev Team
∙ Test Process Development and Controlling
∙ Risks Monitoring
Senior QA Engineer
Responsibilities:
∙ Testing
∙ Bug Finding and Tracking
∙ Requirements Analysis/Testing
∙ Test Teams Leading
∙ Required Test Documentation Development
∙ Project Management
∙ Risks Mitigation, Monitoring and Management
∙ Project Process Tracking and Improvement
понеділок, 28 листопада 2011 р.
четвер, 17 листопада 2011 р.
Гибкое тестирование: практическое руководство для тестировщиков ПО и гибких команд.
Лайза Криспин, Джанет Грегори
Гибкое тестирование: практическое руководство для тестировщиков ПО и гибких команд.
Часть I. Введение
Глава 1. Что такое гибкое тестирование?
Глава 2. Десять принципов гибкого тестирования
Часть II. Организационные проблемы
Глава 3. Сложности, связанные с культурой
Глава 4. Логистика команды
Глава 5. Перенос типичных процессов
Часть III. Квадранты гибкого тестирования
Глава 6. Назначение тестирования
Глава 7. Технологически-ориентированные тесты для поддержки команды
Глава 8. Бизнес-ориентированные тесты для поддержки команды
Глава 9. Инструментарий для бизнес-ориентированных тестов,
Глава 10. Бизнес-ориентированные тесты, критикующие продукт
Глава 11. Критика продукта с использованием
Глава 12. Резюме по квадрантам тестирования
Часть IV. Автоматизация
Глава 13. Причины и препятствия к внедрению автоматизации тестов
Глава 14. Стратегия автоматизации тестирования
Глава 15. Действия тестировщика при планировании выпуска или темы
Глава 16. Сдвиг с мертвой точки
Глава 17. Запуск итерации
Глава 18. Кодирование и тестирование
Глава 19. Завершение итерации
Глава 20. Успешная поставка
Часть VI. Итоги
Глава 21. Ключевые факторы успеха
Гибкое тестирование: практическое руководство для тестировщиков ПО и гибких команд.
Часть I. Введение
Глава 1. Что такое гибкое тестирование?
Глава 2. Десять принципов гибкого тестирования
Часть II. Организационные проблемы
Глава 3. Сложности, связанные с культурой
Глава 4. Логистика команды
Глава 5. Перенос типичных процессов
Часть III. Квадранты гибкого тестирования
Глава 6. Назначение тестирования
Глава 7. Технологически-ориентированные тесты для поддержки команды
Глава 8. Бизнес-ориентированные тесты для поддержки команды
Глава 9. Инструментарий для бизнес-ориентированных тестов,
Глава 10. Бизнес-ориентированные тесты, критикующие продукт
Глава 11. Критика продукта с использованием
Глава 12. Резюме по квадрантам тестирования
Часть IV. Автоматизация
Глава 13. Причины и препятствия к внедрению автоматизации тестов
Глава 14. Стратегия автоматизации тестирования
Глава 15. Действия тестировщика при планировании выпуска или темы
Глава 16. Сдвиг с мертвой точки
Глава 17. Запуск итерации
Глава 18. Кодирование и тестирование
Глава 19. Завершение итерации
Глава 20. Успешная поставка
Часть VI. Итоги
Глава 21. Ключевые факторы успеха
вівторок, 11 жовтня 2011 р.
Web Application Security Testing
.
Web Application Security Testing themes.
1. Vulnerability Analysis
2. Source Code Analysis
3. Penetration Testing
3.1. Pen Test Strategies
3.1.1. Targeted testing
3.1.2. External testing
3.1.3. Internal testing
3.1.4. Blind testing
3.1.5. Double blind testing
3.2. Issues of Input Validation
3.2.1. The Blackbox Testing Technique
3.2.2. SQL Injection Vulnerabilities
3.2.3. Code and Content Injection
3.2.4. Server Side Includes (SSI)
3.2.5. Miscellaneous Injection
3.2.6. Path Traversal and URIs
3.2.7. Cross Site Scripting
3.3. Session Security Issues
3.3.1. Cookies
3.3.2. Session Security and Session-IDs
3.3.3. Logic Flaws
3.3.4. Binary Attacks
4. Fuzz Testing
5. Obfuscation
6. Architectural Risk Analysis
Web Application Security Testing themes.
1. Vulnerability Analysis
2. Source Code Analysis
3. Penetration Testing
3.1. Pen Test Strategies
3.1.1. Targeted testing
3.1.2. External testing
3.1.3. Internal testing
3.1.4. Blind testing
3.1.5. Double blind testing
3.2. Issues of Input Validation
3.2.1. The Blackbox Testing Technique
3.2.2. SQL Injection Vulnerabilities
3.2.3. Code and Content Injection
3.2.4. Server Side Includes (SSI)
3.2.5. Miscellaneous Injection
3.2.6. Path Traversal and URIs
3.2.7. Cross Site Scripting
3.3. Session Security Issues
3.3.1. Cookies
3.3.2. Session Security and Session-IDs
3.3.3. Logic Flaws
3.3.4. Binary Attacks
4. Fuzz Testing
5. Obfuscation
6. Architectural Risk Analysis
понеділок, 10 жовтня 2011 р.
Java для Тестерів Програмного Забезпечення
Урок 1 - Введение - Java для тестировщиков
Урок 2 - Java для тестировщиков
Урок 3 - ООП - Java для тестировщиков
І так далі.............. там багато уроків...
а ось тут вони зібрані послідовно -> Java для тестировщиков
Урок 2 - Java для тестировщиков
Урок 3 - ООП - Java для тестировщиков
І так далі.............. там багато уроків...
а ось тут вони зібрані послідовно -> Java для тестировщиков
понеділок, 3 жовтня 2011 р.
пʼятниця, 30 вересня 2011 р.
Requirements. Вимоги. Зразок змісту документу з коментарями.
1. Introduction
1.1 Purpose
Identify the product whose software requirements are specified in this document, including the revision or release number. Describe the scope of the product that is covered by this SRS, particularly if this SRS describes only part of the system or a single subsystem.
1.2 Document Conventions
Describe any standards or typographical conventions that were followed when writing this SRS, such as fonts or highlighting that have special significance. For example, state whether priorities for higher-level requirements are assumed to be inherited by detailed requirements, or whether every requirement statement is to have its own priority.
1.3 Intended Audience and Reading Suggestions
Describe the different types of reader that the document is intended for, such as developers, project managers, marketing staff, users, testers, and documentation writers. Describe what the rest of this SRS contains and how it is organized. Suggest a sequence for reading the document, beginning with the overview sections and proceeding through the sections that are most pertinent to each reader type.
1.4 Product Scope
Provide a short description of the software being specified and its purpose, including relevant benefits, objectives, and goals. Relate the software to corporate goals or business strategies. If a separate vision and scope document is available, refer to it rather than duplicating its contents here.
1.5 References
List any other documents or Web addresses to which this SRS refers. These may include user interface style guides, contracts, standards, system requirements specifications, use case documents, or a vision and scope document. Provide enough information so that the reader could access a copy of each reference, including title, author, version number, date, and source or location.
2. Overall Description
2.1 Product Perspective
Describe the context and origin of the product being specified in this SRS. For example, state whether this product is a follow-on member of a product family, a replacement for certain existing systems, or a new, self-contained product. If the SRS defines a component of a larger system, relate the requirements of the larger system to the functionality of this software and identify interfaces between the two. A simple diagram that shows the major components of the overall system, subsystem interconnections, and external interfaces can be helpful.
2.2 Product Functions
Summarize the major functions the product must perform or must let the user perform. Details will be provided in Section 3, so only a high level summary (such as a bullet list) is needed here. Organize the functions to make them understandable to any reader of the SRS. A picture of the major groups of related requirements and how they relate, such as a top level data flow diagram or object class diagram, is often effective.
2.3 User Classes and Characteristics
Identify the various user classes that you anticipate will use this product. User classes may be differentiated based on frequency of use, subset of product functions used, technical expertise, security or privilege levels, educational level, or experience. Describe the pertinent characteristics of each user class. Certain requirements may pertain only to certain user classes. Distinguish the most important user classes for this product from those who are less important to satisfy.
2.4 Operating Environment
Describe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software components or applications with which it must peacefully coexist.
2.5 Design and Implementation Constraints
Describe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies; hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards (for example, if the customer’s organization will be responsible for maintaining the delivered software).
2.6 User Documentation
List the user documentation components (such as user manuals, on-line help, and tutorials) that will be delivered along with the software. Identify any known user documentation delivery formats or standards.
2.7 Assumptions and Dependencies
List any assumed factors (as opposed to known facts) that could affect the requirements stated in the SRS. These could include third-party or commercial components that you plan to use, issues around the development or operating environment, or constraints. The project could be affected if these assumptions are incorrect, are not shared, or change. Also identify any dependencies the project has on external factors, such as software components that you intend to reuse from another project, unless they are already documented elsewhere (for example, in the vision and scope document or the project plan).
3. External Interface Requirements
3.1 User Interfaces
Describe the logical characteristics of each interface between the software product and the users. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message display standards, and so on. Define the software components for which a user interface is needed. Details of the user interface design should be documented in a separate user interface specification.
3.2 Hardware Interfaces
Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device types, the nature of the data and control interactions between the software and the hardware, and communication protocols to be used.
3.3 Software Interfaces
Describe the connections between this product and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint.
3.4 Communications Interfaces
Describe the requirements associated with any communications functions required by this product, including e-mail, web browser, network server communications protocols, electronic forms, and so on. Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms.
4. System Features
This template illustrates organizing the functional requirements for the product by system features, the major services provided by the product. You may prefer to organize this section by use case, mode of operation, user class, object class, functional hierarchy, or combinations of these, whatever makes the most logical sense for your product.
4.1 System Feature 1
Don’t really say “System Feature 1.” State the feature name in just a few words.
4.1.1 Description and Priority
Provide a short description of the feature and indicate whether it is of High, Medium, or Low priority. You could also include specific priority component ratings, such as benefit, penalty, cost, and risk (each rated on a relative scale from a low of 1 to a high of 9).
4.1.2 Stimulus/Response Sequences
List the sequences of user actions and system responses that stimulate the behavior defined for this feature. These will correspond to the dialog elements associated with use cases.
4.1.3 Functional Requirements
Itemize the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user to carry out the services provided by the feature, or to execute the use case. Include how the product should respond to anticipated error conditions or invalid inputs. Requirements should be concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder to indicate when necessary information is not yet available.
Each requirement should be uniquely identified with a sequence number or a meaningful tag of some kind.
REQ-1:
REQ-2:
4.2 System Feature 2 (and so on)
5. Other Nonfunctional Requirements
5.1 Performance Requirements
If there are performance requirements for the product under various circumstances, state them here and explain their rationale, to help the developers understand the intent and make suitable design choices. Specify the timing relationships for real time systems. Make such requirements as specific as possible. You may need to state performance requirements for individual functional requirements or features.
5.2 Safety Requirements
Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the product’s design or use. Define any safety certifications that must be satisfied.
5.3 Security Requirements
Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied.
5.4 Software Quality Attributes
Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.
5.5 Business Rules
List any operating principles about the product, such as which individuals or roles can perform which functions under specific circumstances. These are not functional requirements in themselves, but they may imply certain functional requirements to enforce the rules.
6. Other Requirements
Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.
Appendix A: Glossary
Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS.
Appendix B: Analysis Models
Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.
Appendix C: To Be Determined List
Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they can be tracked to closure.
1.1 Purpose
Identify the product whose software requirements are specified in this document, including the revision or release number. Describe the scope of the product that is covered by this SRS, particularly if this SRS describes only part of the system or a single subsystem.
1.2 Document Conventions
Describe any standards or typographical conventions that were followed when writing this SRS, such as fonts or highlighting that have special significance. For example, state whether priorities for higher-level requirements are assumed to be inherited by detailed requirements, or whether every requirement statement is to have its own priority.
1.3 Intended Audience and Reading Suggestions
Describe the different types of reader that the document is intended for, such as developers, project managers, marketing staff, users, testers, and documentation writers. Describe what the rest of this SRS contains and how it is organized. Suggest a sequence for reading the document, beginning with the overview sections and proceeding through the sections that are most pertinent to each reader type.
1.4 Product Scope
Provide a short description of the software being specified and its purpose, including relevant benefits, objectives, and goals. Relate the software to corporate goals or business strategies. If a separate vision and scope document is available, refer to it rather than duplicating its contents here.
1.5 References
List any other documents or Web addresses to which this SRS refers. These may include user interface style guides, contracts, standards, system requirements specifications, use case documents, or a vision and scope document. Provide enough information so that the reader could access a copy of each reference, including title, author, version number, date, and source or location.
2. Overall Description
2.1 Product Perspective
Describe the context and origin of the product being specified in this SRS. For example, state whether this product is a follow-on member of a product family, a replacement for certain existing systems, or a new, self-contained product. If the SRS defines a component of a larger system, relate the requirements of the larger system to the functionality of this software and identify interfaces between the two. A simple diagram that shows the major components of the overall system, subsystem interconnections, and external interfaces can be helpful.
2.2 Product Functions
Summarize the major functions the product must perform or must let the user perform. Details will be provided in Section 3, so only a high level summary (such as a bullet list) is needed here. Organize the functions to make them understandable to any reader of the SRS. A picture of the major groups of related requirements and how they relate, such as a top level data flow diagram or object class diagram, is often effective.
2.3 User Classes and Characteristics
Identify the various user classes that you anticipate will use this product. User classes may be differentiated based on frequency of use, subset of product functions used, technical expertise, security or privilege levels, educational level, or experience. Describe the pertinent characteristics of each user class. Certain requirements may pertain only to certain user classes. Distinguish the most important user classes for this product from those who are less important to satisfy.
2.4 Operating Environment
Describe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software components or applications with which it must peacefully coexist.
2.5 Design and Implementation Constraints
Describe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies; hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards (for example, if the customer’s organization will be responsible for maintaining the delivered software).
2.6 User Documentation
List the user documentation components (such as user manuals, on-line help, and tutorials) that will be delivered along with the software. Identify any known user documentation delivery formats or standards.
2.7 Assumptions and Dependencies
List any assumed factors (as opposed to known facts) that could affect the requirements stated in the SRS. These could include third-party or commercial components that you plan to use, issues around the development or operating environment, or constraints. The project could be affected if these assumptions are incorrect, are not shared, or change. Also identify any dependencies the project has on external factors, such as software components that you intend to reuse from another project, unless they are already documented elsewhere (for example, in the vision and scope document or the project plan).
3. External Interface Requirements
3.1 User Interfaces
Describe the logical characteristics of each interface between the software product and the users. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message display standards, and so on. Define the software components for which a user interface is needed. Details of the user interface design should be documented in a separate user interface specification.
3.2 Hardware Interfaces
Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device types, the nature of the data and control interactions between the software and the hardware, and communication protocols to be used.
3.3 Software Interfaces
Describe the connections between this product and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint.
3.4 Communications Interfaces
Describe the requirements associated with any communications functions required by this product, including e-mail, web browser, network server communications protocols, electronic forms, and so on. Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms.
4. System Features
This template illustrates organizing the functional requirements for the product by system features, the major services provided by the product. You may prefer to organize this section by use case, mode of operation, user class, object class, functional hierarchy, or combinations of these, whatever makes the most logical sense for your product.
4.1 System Feature 1
Don’t really say “System Feature 1.” State the feature name in just a few words.
4.1.1 Description and Priority
Provide a short description of the feature and indicate whether it is of High, Medium, or Low priority. You could also include specific priority component ratings, such as benefit, penalty, cost, and risk (each rated on a relative scale from a low of 1 to a high of 9).
4.1.2 Stimulus/Response Sequences
List the sequences of user actions and system responses that stimulate the behavior defined for this feature. These will correspond to the dialog elements associated with use cases.
4.1.3 Functional Requirements
Itemize the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user to carry out the services provided by the feature, or to execute the use case. Include how the product should respond to anticipated error conditions or invalid inputs. Requirements should be concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder to indicate when necessary information is not yet available.
Each requirement should be uniquely identified with a sequence number or a meaningful tag of some kind.
REQ-1:
REQ-2:
4.2 System Feature 2 (and so on)
5. Other Nonfunctional Requirements
5.1 Performance Requirements
If there are performance requirements for the product under various circumstances, state them here and explain their rationale, to help the developers understand the intent and make suitable design choices. Specify the timing relationships for real time systems. Make such requirements as specific as possible. You may need to state performance requirements for individual functional requirements or features.
5.2 Safety Requirements
Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the product’s design or use. Define any safety certifications that must be satisfied.
5.3 Security Requirements
Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied.
5.4 Software Quality Attributes
Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.
5.5 Business Rules
List any operating principles about the product, such as which individuals or roles can perform which functions under specific circumstances. These are not functional requirements in themselves, but they may imply certain functional requirements to enforce the rules.
6. Other Requirements
Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.
Appendix A: Glossary
Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS.
Appendix B: Analysis Models
Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.
Appendix C: To Be Determined List
Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they can be tracked to closure.
Матриця Прослідковування планування розробки Тест Кейсів
Матриця Прослідковування планування розробки Тест Кейсів повинна допомогти максимально покрити кожну Вимогу необхідними Тест Кейсами.
четвер, 29 вересня 2011 р.
Матриця Прослідковування покриття Вимог Тест Кейсами та Тестуванням
Requirements Traceability Matrix
пʼятниця, 26 серпня 2011 р.
Процес Тестування Програмного Забезпечення
1. Аналіз/Тестування Вимог до Продукту
2. Планування Тестування
3. Дизайн Тестів
4. Розробка Тестової Документації
5. Виконання Тестування
6. Аналіз Результатів та Покращення Тестування
7. Перетестовування
8. Звітування
9. Завершення Тестування
2. Планування Тестування
3. Дизайн Тестів
4. Розробка Тестової Документації
5. Виконання Тестування
6. Аналіз Результатів та Покращення Тестування
7. Перетестовування
8. Звітування
9. Завершення Тестування
пʼятниця, 29 липня 2011 р.
Характерні Ознаки Якості ПЗ
Quality Attributes
Availability
Efficiency
Flexibility
Installability
Integrity
Interoperability
Maintainability
Portability
Reliability
Reusability
Robustness
Safety
Testability
Usability
Availability
Efficiency
Flexibility
Installability
Integrity
Interoperability
Maintainability
Portability
Reliability
Reusability
Robustness
Safety
Testability
Usability
середа, 2 лютого 2011 р.
Defect/ Bug/ Fault, Error/ Mistake, Fail, Failure
Defect or Bug or Fault: A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g. an incorrect statement or data definition. A defect, if encountered during execution, may cause a failure of the component or system.
Error or Mistake: A human action that produces an incorrect result.
Fail: A test is deemed to fail if its actual result does not match its expected result.
Failure: Deviation of the component or system from its expected delivery, service or result.
If someone makes an error or mistake in using the software, this may lead directly to a problem - the software is used incorrectly and so does not behave as we expected. However, people also design and build the software and they can make mistakes during the design and build. These mistakes mean that there are flaws in the software itself. These are called defects or sometimes bugs or faults. Remember, the software is not just the code; check the definition of soft-ware again to remind yourself.
When the software code has been built, it is executed and then any defects may cause the system to fail to do what it should do (or do something it shouldn't), causing a failure. Not all defects result in failures; some stay dormant in the code and we may never notice them.
*ISTQB Glossary
Error or Mistake: A human action that produces an incorrect result.
Fail: A test is deemed to fail if its actual result does not match its expected result.
Failure: Deviation of the component or system from its expected delivery, service or result.
If someone makes an error or mistake in using the software, this may lead directly to a problem - the software is used incorrectly and so does not behave as we expected. However, people also design and build the software and they can make mistakes during the design and build. These mistakes mean that there are flaws in the software itself. These are called defects or sometimes bugs or faults. Remember, the software is not just the code; check the definition of soft-ware again to remind yourself.
When the software code has been built, it is executed and then any defects may cause the system to fail to do what it should do (or do something it shouldn't), causing a failure. Not all defects result in failures; some stay dormant in the code and we may never notice them.
*ISTQB Glossary
Підписатися на:
Дописи (Atom)
Публікації
