Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
Module1.docx
Скачиваний:
1
Добавлен:
22.11.2019
Размер:
28.4 Кб
Скачать

6.Project: Management Processes?

Project Management: Requirements Analysis, Project Planning (what, when and how), Project running accordingly plans, Project group staffing, Tasks assignment, Progress monitoring, Reporting to customer and management, Status meeting conducting, Continuous communication with customers, Reporting monitoring

QA Management: Requirements Analysis, Test process planning (what, when and how), Together with PM – project planning, Project metrics establishing, QA team staffing and management, Tasks assignment, Progress monitoring, Bug Tracking tool configuring, Product quality evaluation, Project documentation review, Monitoring of project processes quality. Problems stating;

Requirements Management: Requirements collecting and analysis, Fixing requirements in the specifications, Registering requirements in the tracking tool, Traceability definition, Control of requirements implementation, readiness status, Change management, Initially – change management definition

Configuration Management: Project environment design and : repository structure and permissions, Tools to be used, Tools configuration, Resources needed, Version control (code, docs, etc), Changes tracking, Control of defined rules following.

7.What is Iteration?

Repeat of the same set of actions or One pass through the cycle.

8. On-Project QA – variants of organization

Centralized (functional org structure), Team-based (project org structure), Hybrid (matrix org structure).

9. Feasibility Study, PoC

Feasibility studies aim to objectively and rationally uncover the strengths and weaknesses of an existing business or proposed venture, opportunities and threats as presented by the environment, the resources required to carry through, and ultimately the prospects for success.

PoC- A proof of concept (POC) or a proof of principle is a realization of a certain method or idea(s) to demonstrate its feasibility.

10. Rfp/Vision/Proposal

A request for proposal (RFP) is a solicitation made, often through a bidding process, by an agency or company interested in procurement of a commodity or service, to potential suppliers to submit business proposals. It is submitted early in the procurement cycle, either at the preliminary study, or procurement stage. The RFP process brings structure to the procurement decision and is meant to allow the risks and benefits to be identified clearly up front.

Vision - A Vision Document is a software process document that describes the overall 'vision', or plan, for a particular piece of software. It defines the stakeholders view of the product to be developed, specified in terms of the stakeholders key needs and features.

Proposal - A business proposal is a written offer from a seller to a prospective buyer. Business proposals are often a key step in the complex sales process—i.e., whenever a buyer considers more than price in a purchase.

11.Milestone, Deadline, Delivery, Release

Milestone -in project management, a milestone is a synchronization point. Major milestones mark the transition of a project from one phase to another.

Deadline - A time limit or deadline is a narrow field of time, or particular point in time, by which an objective or task must be accomplished. In project management, deadlines are most often associated with milestone goals. Release - A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.

In agile software development, a release is a deployable software package that is the culmination of several iterations. Releases can be made before the end of an iteration.

Project deliverables. In each of the different types of iterations Smart suggests to deliver additional products that will help drive your project to success. These products might include well know deliverables such as a project proposal and non-functional requirements. Although none of these product are actually mandatory in a Smart project, they are considered good practice, and over the years have been produced in numerous Smart projects. Using these standard suggested products, organizations get an even better grip on the projects at hand. Note that emphasizing the existence of other project deliverables besides working software (in smart use cases) does not mean projects become less agile.

12. QA&Testing activities in Project

Test Planning-> Test Approach/Strategy Test Plan

A test plan documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements. A test plan is usually prepared by or with significant input from Test Engineers.

Test Design > Test Case

In software engineering, test design is the act of creating and writing test suites for testing a software.

Test Automation > Auto-Tests

 test automation is the use of special software (separate from the software being tested) to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.[1]Commonly, test automation involves automating a manual process already in place that uses a formalized testing process.

Testing and Bug Tracking > Bugs, Test Summary Report

QA Management > Project Standard Documents, Metrics, Reports

Соседние файлы в предмете [НЕСОРТИРОВАННОЕ]