VStudio Team Dev 2008(英文版w/MSDN Prem)
点此进入淘宝搜索页搜索分类: 软件,按品牌,微软,开发工具,
品牌: 微软
编辑推荐特殊说明
本商品为预订商品，预计到货时间为2-6周，在您提交订单时需预付全部货款。页面报价仅限北京地区，非北京地区用户可拨打卓越亚马逊软件游戏负责人电话确认价格。
请您在提交订单之后务必拨打下面的电话与我们联系，我们将尽快为您联系供应商，安排进货与发货事宜。您通过我们网站订购产品，您的订单即成为购买产品的申请或要约，我们将发送给您一封确认订单的电子邮件，其中载明订单的细节，但只有当我们向您发送发货确认的电子邮件通知您我们已将产品发出时，我们对您合同申请的接受方成立。
卓越亚马逊软件游戏负责人联系电话：010-65690127、65690306；工作时间：周一至周五，9至18点。
产品参数·介质：软件
·操作系统：Windows XP/2003 Server/Vista
·英语：英语
·碟数：1
·格式：CD-ROM
·品牌：微软
·包装版本：普通包装
·版本：2008 英文版
·条形码：UEC-00006
·发行公司：微软（中国）有限公司
·出版社：微软
·语言：英语
包装清单1CD-ROM！
产品描述《VStudio Team Dev 2008》provides developers with an advanced set of tools to identify inefficient, insecure, or poor-quality code, specify coding best practices, and automate software unit testing. These tools help team members write better-quality code, reduce security-related issues, and avoid bugs later in the development lifecycle.
Visual Studio Team System 2008 Development Edition helps identify inefficient, insecure, and poor-quality code. It automates software unit testing and, with Visual Studio Team System 2008 Team Foundation Server, automates compliance with coding best practices. These tools help everyone on the team write better code, mitigate security risks, and deliver customer value in less time.
Microsoft Visual Studio Team System is an integrated Application Life Cycle Management (ALM) solution comprising tools, processes, and guidance to help all members of a development team improve their skills and work effectively together.
Identify the cause of failure
Immediately determine the cause of failed check-ins and obtain guidance fora ddressing the problems using new code correctness policies.
Address poor performance at the source
Discover the source of poor application performance and use integrated application profiling and tuning tools to diagnose, debug, and fix errors.
Automatically identify
Use the hotpath finder to automatically navigate to the code paths that are causing performance problems and gain guidance on how to fix and improve the efficiency of your code.
What's New in 2008
★Code Metrics: Identify complex and error-prone code.
★Custom code correctness policies: Communicate to a developer why the check-in policies failed and to provide guidance on how to pass the policy requirements.
★Hotpathing: Discover code paths that account for performance issues Performance baseline comparison: Compare performance baseline reports to identify the source of performance regressions.
★Code Analysis rules: Code Analysis is more accurate with new and improved rules.
Feature Highlights
★Static Code Analysis to improve code quality and security
★New Code Metrics to identify error-prone code
★Code Profiler to measure code performance and find performance bottlenecks
★Unit testing with code coverage to test code early and often and measure the effectiveness of your tests
★Check-in policies to ensure coding best practices
Microsoft's Solution for Application Lifecycle Management (ALM)
Building the right team and fostering a culture of continuous improvement is the foundation for success. You also need the right tools and processes in place for your team to do their best work. That's where Microsoft Visual Studio Team System can help.
Overcoming Application Development Challenges
Whether you're part of an application development team, or a business stakeholder who depends on IT for business-critical applications, you know first-hand some of the many challenges associated with application development. These challenges depend on the situation, but often include:
★Managing shifting business requirements throughout the project
★Communication gaps between project managers, developers and testers
★Adequately testing applications for quality and reliability
★Gaining visibility into project status to make trade-off decisions and to drive predictable project delivery
★Dealing with global development, regulatory and compliance challenges
These are not simple challenges to overcome; many are interrelated and involve multiple team members and stakeholders. By systematically improving capabilities across your team, you can achieve dramatic improvements in your project success rates, better mitigate risks and increase your overall impact to the business.
Visual Studio Team System can help your team overcome these challenges in the following ways:
Most software development teams use a number of stand-alone tools to manage the application lifecycle. Specifications and requirements are stored on file shares or SharePoint sites; tasks assigned to developers are managed using e-mail; bugs are tracked with spreadsheets; and source code resides in one or more version-control systems. With important information in so many different places, it's hard for team members to work together effectively, resulting in additional effort and the potential for miscommunication.
Integrated Team Server
Visual Studio Team System facilitates teamwide communication and collaboration by providing a unified repository for all project data, along with the tools to define, enforce, and automate desired processes. At its heart is Visual Studio Team System 2008 Team Foundation Server, which supports source code and version control, work item tracking, automated builds and quality checks, and more. Configurable process templates tie all team activity together, with changes in status gathered automatically as part of everyday workflows. Automatic notifications keep team members informed of key events, such as a failed build. And with all information in one place and tied together, all efforts are traceable back to initial requirements and all stakeholders have deep, real-time visibility into project status and quality.
Support for All Disciplines
Team System Team Foundation Server was designed to meet the needs of all members of the extended development team, not just software developers. Business analysts and architects can manage scenarios, requirements, and design documents; project managers and development leads can assign, track, and report on project status; database professionals can manage database schemas and deployment scripts; and testers can manage regression and load tests, determine test coverage, and keep a close eye on quality trends. The Visual Studio Team Explorer client provides all team members with a single point of access to all project artifacts and data, while a prebuilt, customizable SharePoint portal extends the same information to remote team members and other project stakeholders.
Key Benefits
By bringing all project artifacts, data, and status together in one place, Visual Studio Team System enables more effective team communication and collaboration. Defined and consistently enforced processes, full traceability, and built-in status reporting help maximize individual productivity, at the same time helping to ensure that the efforts of each team member remain well defined and aligned with the team's overall priorities.
Quality is often neglected during most phases of the development process. Instead, it is measured near the end of the process, when code is handed off to be tested. This approach often results in extra work and a slipping schedule as features thought to be complete are pushed back to developers for rework. Even if code passes initial QA tests, performance and scalability issues can remain undetected until software is deployed into production.
A Quality-Centric Tool Set
Microsoft Visual Studio Team System provides tools for ensuring quality throughout all phases of the application lifecycle, helping teams to deliver high-quality software faster and with less rework. From tracking requirements during planning to performance and load testing of the completed application, Visual Studio Team System provides the tools needed to ensure all aspects of software quality.
Focus on Quality Throughout the Application Lifecycle
The focus on quality begins during the planning phase, before the first line of code is written, when work item tracking helps thoroughly map scenarios to requirements. As architects design a solution that meets those requirements, tools such as the Application Designer, Distributed System Designer, and Deployment Designer help ensure that the solution will deliver the necessary performance, scalability, and manageability.
During development, before code is checked in, static code-analysis tools help prevent coding errors and potential security issues, while performance profiling and hot-path analysis help avoid potential performance and scalability problems. Developers can easily create unit tests to validate application and database objects, using code coverage analysis tools to determine the completeness of those tests. Tools for examining code metrics can gauge the complexity and maintainability of code.
QA engineers can begin writing test cases and load tests early, mapping them to work items and managing all test activity with Visual Studio Team System. As requirements change, full traceability between work items helps them ensure that test coverage remains complete. Prior to production deployment, comprehensive load-testing tools help QA engineers validate the application's performance and scalability as a whole.
Key Benefits
Visual Studio Team System enables development teams to ensure quality throughout all phases of the application lifecycle, not just near the end. Such an approach helps minimize the rework-and-retest "churn" that typically occurs near the end of each development iteration, during which tradeoffs on quality versus schedules must often be madeÑin turn helping to increase software quality, reduce time-to-market, and decrease overall development costs.
Development teams deal with many different types of work items, such as scenarios, use cases, requirements, developer tasks, change requests, test passes, and bugs. However, most teams lack a good way to manage all those work items, define the relationships between them, and trace those relationships and the effects of status changes throughout the application lifecycle. Through such capabilities, teams can better gauge progress toward goals and ensure that resources are not being wasted on unnecessary work.
Detailed Work Plans
Work item tracking in Microsoft Visual Studio Team System provides an efficient way to manage and monitor the status of all project-related activity. All projects have detailed work plans, with initial work items generated automatically based on process templates. Each work item typically has a title; a description; a team member to whom the work is assigned; and a current state, such as proposed, active, resolved, or closed. Work items can also have links to other work items, attachments, and custom fields.
Full Visibility and Traceability
With relationships between work items clearly defined and changes in the status of work items collected automatically, a team's progress-to-goals remains visible at all times, even as work is handed off among team members. For example, a business analyst may break down scenarios into requirements, which a development lead divides into tasks for developers. As developers finish the tasks, source codeÐcontrol policies require them to associate their checked-in code with work items. Because those change sets are associated with each build, as a new build passes QA tests, all stakeholders can see that, for example, 60 percent of the work required to meet all project requirements is now complete.
Key Benefits
Work item tracking provides an efficient way to manage the efforts of all team members, with full traceability back to initial project goals and real-time visibility into team progress. Team members will know how their assigned tasks are related to project goals as a whole, and project managers and leads can ensure that no unnecessary work is assigned. And because all changes to work items are logged and fully auditable, those same capabilities can help address complex compliance and regulatory requirements.
Another quality-related area where most teams see room for improvement is source code management and version control. One common issue is the integration of individual developer efforts into the official code base, which can result in the all-too-frequent "broken build"Ñand force QA resources to sit idle until the issues have been resolved and a new build is ready to test.
Comprehensive Version Control
Microsoft Visual Studio Team System helps solve these pains by providing a comprehensive, flexible, version-control system. This functionality is not a mere upgrade to Microsoft Visual SourceSafe version-control system; rather, the version-control capabilities of Visual Studio Team System Team Foundation Server were designed from the ground up to deliver the same scalability, performance, and reliability of its underlying data store, which is based on Microsoft SQL Server 2005 database software. Built-in tools aid in the migration of source code and change history from Visual SourceSafe.
Some key version-control features in Visual Studio Team System Team Foundation Server include atomic check-ins, which help maintain the integrity of source-code files, and policies that require developers to perform unit tests or static code analysis prior to checking in code and to associate all checked-in code with work items. Support for "shelving" code enables developers to store work in process on the server without checking it in, and a new "get latest on edit" feature checks for new code on the server when a developer starts to edit a local copyÑjust in case someone else has made changes since the code was checked out.
Powerful Build Server
Version control in Visual Studio Team System is complemented by its Team Build features, including support for continuous integration builds every time someone checks in code. Unit tests and build verification tests can be run as part of the process, and if the build or tests fail, designated stakeholders are automatically notified. Flexible build definitions also help reduce the time spent managing scripts for "official" builds, providing the ability to easily automate compilation, unit tests, static code analysis, virtual server configuration, Web site or Web services configuration, application installation, database deployment, test-data generation, and load tests.
Key Benefits
The version-control and Team Build features in Visual Studio Team System help teams ensure quality by enabling them to easily and frequently integrate the work of individual team membersÑand validate that the combined efforts work as expected.
Many development teams want an integrated solution for application lifecycle management but also want to avoid the lost productivity associated with having to learn new tools.
Make Use of Existing Tools and Skill Sets
Microsoft Visual Studio Team System facilitates adoption by enabling team members to use tools that are already familiar to them. Project managers can design an itemized list of work items, assign those work items to developers, and track their completion using Microsoft Office Project Professional, or they can use Microsoft Office Excel spreadsheet software to make global changes and quickly reassess priorities. Architects, software developers, development leads, database professionals, and testers can continue to use the Visual Studio integrated development environment, including Visual Studio 2008 Professional Edition or any of the Visual Studio Team System 2008 editions. Remote team members and business stakeholders can use Visual Studio Team System Web Access to take advantage of all Visual Studio Team System features.
Key Benefits
Visual Studio Team System helps reduce "soft" adoption costs by integrating with the desktop applications that people already know and use. Instead of having to learn new tools, all team members can continue to use the tools that help them be the most productive.
Regardless of the maturity of their processes, many development teams lack full visibility into the application lifecycleÑand thus they are unable to easily answer questions such as "Does the application meet all requirements?" and "Are we on schedule?"
Business Intelligence for Development Teams
Powered by an integrated Microsoft SQL Server 2005Ðbased data warehouse, the business intelligence features in Microsoft Visual Studio Team System provide the information needed to make informed, real-time decisions with just a click on a link. And because SQL Server Reporting Services is the engine underlying Visual Studio Team System business intelligence, teams can just as easily customize existing reports as they can create new ones.
One highly useful out-of-the-box report is Remaining Work, which provides a comprehensive view of all remaining work items, enabling development leads and project managers to easily see progress, identify bottlenecks, and, if necessary, reallocate resources. Another useful prebuilt report is Quality Indicators, which provides a combined view of unit test success rates, code coverage by unit tests, code churn, and active bugsÑall tracked over time.
Key Benefits
Visual Studio Team System provides the information needed to make informed, real-time decisions on iteration planning, test coverage, bug trends, project schedules, resource allocation, and moreÑin turn helping development teams to deliver on time and on budget, and to ensure that projects meet all requirements. Project managers and development leads can be ready for team meetings in minutes instead of hours, saving everyone the effort of having to manually communicate status, and can answer questions posed by external stakeholders and upper management on the fly.
Most development teams recognize the value of consistent processes. However, they may not have such processes, know what they need, or know how to get started. Teams that have established processes may find that the processes are not consistently followed, or that adherence requires significant manual effort. Few teams have matured to the point that they can consistently and effortlessly follow established processes and, even if they have, must still deal with issues such as reorganization, new regulatory or compliance requirements, and bringing new team members up to speed.
Defined and Consistently Followed Processes
Visual Studio Team System includes integrated process templates to help teams deliver predictable results, continuously improve and adapt, and more effectively collaborate and communicate. The process templates are fully integrated with other Visual Studio Team System features, such as work item tracking and source code control, providing both the ability to define desired processes and the means for all team members to productively work within those processes.
Visual Studio Team System includes two out-of-the-box process templates: Microsoft Solutions Framework for Agile Software Development and Microsoft Solutions Framework for CMMI (Capability Maturity Model Integration) Process Improvement. Each provides a set of predefined work items, HTML-based process guidance, a SharePoint portal, and a set of predefined reports. Templates for additional methodologies such as Scrum are available in the Visual Studio Team System Developer Center on MSDN, the Microsoft Developer Network.
Configurable and Adaptable Templates
Although prebuilt process templates can provide a strong head start, they're not hard-coded. Teams can tailor them to support their own processes or can define new templates from scratch. Either way, the Process Template Editor makes it easy to create new types of work items, specify content for a work item type, define which work items are automatically generated for a new project, and define the relationships between work item types. Teams also can customize process guidance, SharePoint portal layout, and reports.
Key Benefits
Visual Studio Team System can help development teams define, adopt, and enforce consistent processes. In turn, that improved predictability can help increase project velocity, accelerate development cycles, and facilitate more accurate estimation of those cycles, thereby helping teams to deliver results better, faster, and more consistently.
minimum_system_requirement_description
Clients (Visual Studio Team Suite and Editions):
Software requirements:
32-bit operating system:Windows XP Professional with Service Pack 2, Windows Server 2003, or Windows Vista
64-bit operating system:
★Windows Server 2003 Standard x64 Edition with SP1(WOW)
★Windows Server 2003 Enterprise x64 Edition with SP1 (WOW)
★Windows Server 2003 Datacenter x64 Edition with SP1 (WOW)
★Windows Server 2003 R2 Standard x64 Edition (WOW)
★Windows Server 2003 R2 Enterprise x64 Edition (WOW)
★Windows Server 2003 R2 Datacenter x64 Edition (WOW)
★Windows XP Professional x64 Edition (WOW)
★Windows Vista
Client software prerequisites:Internet Explorer 6.0 with SP1, Microsoft Office 2003 with SP1 or:
Microsoft Office 2007 system, MDAC 9.0, the Microsoft .NET Framework 2.0
Hardware requirements
Minimum: 2.0-GHz CPU, 512 MB RAM, 8-GB hard drive
Recommended: 2.6-GHz CPU, 1 GB RAM, 20-GB hard drive
Visual Studio Team Foundation Server Data tier
Software requirements:
32-bit operating system:
★Windows Server 2003, Standard Edition with SP1
★Windows Server 2003 R2 Standard Edition
★Windows Server 2003, Enterprise Edition with SP1
★Windows Server 2003 R2 Enterprise Edition
★Windows Server 2003 Datacenter Edition with SP1
★Windows Server 2003 R2 Datacenter Edition
★Windows Server 2008
★Team Foundation Server Data Tier does not support 64-bit operating systems on single-server deployments
64-bit operating system (dual-server deployment only):
★Windows Server 2003 Standard x64 Edition with SP1
★Windows Server 2003 Enterprise x64 Edition with SP1
★Windows Server 2003 Datacenter x64 Edition with SP1
★Windows Server 2003 R2 Standard x64 Edition
★Windows Server 2003 R2 Enterprise x64 Edition
★Windows Server 2003 R2 Datacenter x64 Edition
Hardware requirements
★Minimum: single processor, 2.2 GHz, 8-GB HD, 1 GB RAM
★The server that is running Team Foundation Server should have a reliable network connection with a minimum bandwidth of 1 Mbps and a latency maximum of 350ms.
★Recommended: See next section for details
Visual Studio Team Foundation Server Application tier
Software requirements:
32-bit operating system:
★Windows Server 2003, Standard Edition with SP1
★Windows Server 2003 R2 Standard Edition
★Windows Server 2003 Enterprise Edition with SP1
★Windows Server 2003 R2 Enterprise Edition
★Windows Server 2003 Datacenter EditionSP1
★Windows Server 003 R2 Datacenter Edition
★Windows Server 2008
★Team Foundation Server Application Tier does not support 64-bit operating systems.
Hardware requirements
Minimum: single processor, 2.2 GHz, 8-GB HD, 1 GB RAM
The server that is running Team Foundation Server should have a reliable network connection with a minimum bandwidth of 1 Mbps and a latency maximum of 350ms.
Recommended: See next section for details
Visual Studio Team Build
Software requirements:
32-bit operating system:Windows Server 2003 with SP1, SP2, Windows Server 2003 R2, or Windows XP Professional, .NET Framework 2.0
64-bit operating system:
★Windows Server 2003 Standard x64 Edition with SP1 (WOW)
★Windows Server 2003 Enterprise x64 Edition with SP1 (WOW)
★Windows Server 2003 Datacenter x64 Edition with SP1 (WOW)
★Windows Server 2003 R2 Standard x64 Edition (WOW)
★Windows Server 2003 R2 Enterprise x64 Edition (WOW)
★Windows Server 2003 R2 Datacenter x64 Edition (WOW)
★Windows XP Professional x64 Edition (WOW)
Hardware requirements
Minimum: single processor, 766 GHz, 8-GB HD, 256 MB RAM
Recommended: See next section for details
Visual Studio Team Foundation Server Proxy
32-bit operating system:
Windows Server 2003, Standard Edition with SP1
Windows Server 2003 R2 Standard Edition
Windows Server 2003, Enterprise Edition with SP1
Windows Server 2003 R2 Enterprise Edition
Windows Server 2003 Datacenter Edition with SP1
Windows Server 2003 R2 Datacenter Edition
Windows Server 2008
Team Foundation Server Proxy does not support 64-bit operating systems.
Hardware requirements
Minimum: single processor, 2 GHz, 40-GB HD, 2 GB RAM
The server should have a reliable network connection with a minimum bandwidth of 1 Mbps and a latency maximum of 350 ms.
Test rig
Software requirements:
Windows Server 2003 with SP1, Windows XP Professional with SP2, or Microsoft Windows 2000 with SP 4, Microsoft SQL Server 2005 Express Edition, .NET Framework 2.0
Hardware requirements
Minimum: single processor, 600 MHz, 1-GB HD, 512 MB RAM
Recommended: See next section for details
生产商联系信息微软（中国）有限公司
http://www.microsoft.com/zh/cn
800-820-3800
发行商联系信息微软（中国）有限公司
http://www.microsoft.com/zh/cn
800-820-3800
