-
81 build acceptance test
"A group of tests used to determine the health of a build at a high level. Typically, these tests exercise the core functionality to help team members determine whether further testing is worthwhile. They are run after the daily build to verify that compilation of source code has been built successfully and is ready for further testing." -
82 code review
"The process of assessing code to improve its quality and the capabilities of the development team. Types of code review include formal review, peer-based review, and third-party review." -
83 conceptual design
"A major stage in the design process, through which the project team translates the business requirements into a common language to be shared by users and developers, and describes the feature set and/or usage scenarios that the solution must encompass. Conceptual design is analogous to the rough sketches and scenarios created when designing a house. These are easily understood models jointly created by the customer and the architect." -
84 physical design
"The third major stage in the design process, in which the project team determines how to specifically implement the logical design. Physical design addresses the technology that will be used by the end user. The goal is to apply real-world technology constraints to the logical design, such as implementation and performance considerations. Physical design corresponds to a contractor's blueprints for the physical elements of a structure-wiring, plumbing, heating, and ventilation. The contractor's plans add detail to the architect's plans and reflect real-world construction constraints." -
85 master project plan
"A deliverable of the planning phase for a development project. It consolidates feature team and role plans. The master project plan includes a budget plan, capacity plan, communications plan, deployment plan, development plan, pilot plan, purchasing and facilities plan, security plan, test plan, and training plan." -
86 master project schedule
"A schedule that identifies all the project's activities and milestones, consolidating all team and role schedules. The master project schedule is a deliverable of the planning phase." -
87 project portal
The site used to store and present non-code work products and reports for a team project. -
88 project scope
The work agreed to and documented between the project sponsor and the project team in order to plan and deliver the solution. -
89 responsibility matrix
"A document that explicitly calls out the individual team members who are tasked with executing, reviewing, and approving work packages within a project." -
90 smoke test
"A group of tests used to determine the health of a build at a high level. Typically, these tests exercise the core functionality to help team members determine whether further testing is worthwhile. They are run after the daily build to verify that compilation of source code has been built successfully and is ready for further testing." -
91 trade-off matrix
"A tool for managing project trade-offs by portraying them in a matrix that reflects the three project variables (presented on the y axis) in the context of three decisions (presented on the x axis). The project variables are resources (people and money), schedule (time), and features (the product and its quality). These variables are sometimes presented as the trade-off triangle. The three decisions are whether to optimize, constrain, or accept a given variable. A change to one of the project variables requires that the team make a correction on one of the three sides to maintain project balance, including potentially the same side on which the change first occurred. For example, a decision to add a feature to a product may require that other features be removed if sufficient time and resources are unavailable to support their development." -
92 vision statement
A one- or two-sentence summary of the principle objectives of the project which can be used by any team member to help prioritize work and make project decisions. -
93 Common Structure Services
The mechanism in Team Foundation for describing a feature hierarchy. -
94 project vision
"The purpose, driving factors, and background for building the system. The goal of the project vision is to align the team around a central purpose." -
95 Work Item Query Language
"A loose variant of SQL that describes a query in the Work Item Tracking subsystem of Team Foundation Server using a syntax that contains SELECT, WHERE, COLUMN and SORT clauses. Query View is the user interface for defining work item queries." -
96 Microsoft® Office Project Web Access
"The Web browser–based interface of Microsoft Office Project that project team members and stakeholders can use to access and update information stored in Microsoft Project Server, without having to install Microsoft Project on their computers."Microsoft® Office Project Web AccessEnglish-Arabic terms dictionary > Microsoft® Office Project Web Access
-
97 enterprise-level project
"A major project that is related to an organization, such as a team coordination project or a project created to establish consistency across the organization." -
98 award certificate
A document presented to an individual or team in formal recognition of their effort or achievement. -
99 Test List Editor
"The window in Visual Studio Team System that is used to manage, execute, and control large numbers of tests and test lists." -
100 attachment link
A Team Foundation link between a work item and a file attachment.
См. также в других словарях:
team — team … Dictionnaire des rimes
Team B — was a competitive analysis exercise commissioned by the Central Intelligence Agency in the 1970s to analyze threats the Soviet Union posed to the security of the United States. Team B, approved by then Director of Central Intelligence George H. W … Wikipedia
Team 10 — Team 10, just as often referred to as Team X , was a group of architects and other invited participants who assembled starting in July 1953 at the 9th Congress of C.I.A.M. and created a schism within CIAM by challenging its doctrinare approach to … Wikipedia
Team OS/2 — is an advocacy group formed to promote IBM s OS/2 operating system. Originally internal to and sponsored by IBM, Team OS/2 is now a wholly grassroots organization following IBM s decision to de emphasize OS/2.BeginningsTeam OS/2 was a significant … Wikipedia
Team 10 — Team X Team X, Team 10 ou encore Team Ten (généralement prononcé en anglais /ti:m ten/ qui signifie « l équipe dix ») est un groupe d architecte issus du mouvement moderne ayant contribué à repenser l architecture et l urbanisme en… … Wikipédia en Français
Team X — Team X, Team 10 ou encore Team Ten (généralement prononcé en anglais /ti:m ten/ qui signifie « l équipe dix ») est un groupe d architectes issus du mouvement moderne ayant contribué à repenser l architecture et l urbanisme en rupture… … Wikipédia en Français
TEAM — Datos generales Origen Bratislava, Eslovaquia Estado … Wikipedia Español
Team 60 — Cuatro aviones Saab 105 del Team 60 realizando una exhibición aérea en 2007. Activa 1974 actualidad País … Wikipedia Español
Team — (t[=e]m), n. [OE. tem, team, AS. te[ a]m, offspring, progeny, race of descendants, family; akin to D. toom a bridle, LG. toom progeny, team, bridle, G. zaum a bridle, zeugen to beget, Icel. taumr a rein, bridle, Dan. t[ o]mme, Sw. t[ o]m, and… … The Collaborative International Dictionary of English
Team 10 — Team 10, Team X oder Team Ten war eine Architektengruppe, von 1953 bis 1981, die aus dem Congrès International d’Architecture Moderne (CIAM) hervorging und nach dem Zweiten Weltkrieg die dogmatischen Vertreter der klassischen Moderne, vorneweg Le … Deutsch Wikipedia
Team X — Team 10, Team X oder Team Ten war eine Architektengruppe, die von 1953 bis 1981 bestand. Gruppe von Architekten der 1950er und 1960er Jahre, die aus der CIAM (Congrès Internationaux d Architecture Moderne) hervorging und nach dem Zweiten… … Deutsch Wikipedia