Design submission template

This document provides an overview of software process models and Scrum methodology. It defines a software process model as a description of the sequence of activities carried out in a software engineering project. The key activities include specification, design & implementation, validation, and evolution. Scrum is introduced as an agile software development framework. It utilizes short development cycles called sprints, daily stand-up meetings, product backlogs to track requirements, and emphasizes self-organizing teams and adaptive planning. The benefits of Scrum are discussed as improved productivity, quality, and ability to manage changing requirements.

This document provides instructions for using Visual Studio Team Foundation Server 2013 to manage an agile project. It discusses setting up agile teams, creating a product backlog and sprints, and using branching and merging for feature development. The document walks through visualizing branches and changesets and merging code changes between branches for main, release and development.

This document provides training materials for HP ALM 11.0 for test leads and testers at AMD. It outlines the objectives of the training, which is to provide an overview of the key features and functionality of ALM 11.0 based on roles. It also demonstrates the installation process, differences from the previous version (QC 9.2), and how to use various modules in ALM 11.0 like test plan, test lab, and defects. The training agenda covers topics like the ALM environment, best practices for each module, and how to create libraries and baselines.

The document discusses the principles of agile driven development, including that projects have become shorter but more complex, requiring a user-centric approach. It outlines the agile manifesto which values individuals, working software, customer collaboration and responding to change over documentation, contracts and strict plans. Key principles of agile include open communication, incremental changes and rapid feedback. Success requires teamwork, quality assurance, resolving dependencies, and software integration and availability through continuous builds. A combined approach uses both rolling wave and agile planning with high-level milestones and detailed iterations.

The document discusses the agile software development methodology of Extreme Programming (XP). It provides an overview of XP, including its values, practices, and roles. It notes that XP focuses on communication, simplicity, feedback, and courage. Key practices include pair programming, user stories, planning games, and frequent small releases. The document also covers challenges and lessons learned with adopting XP.

The document discusses various design smells that negatively impact software quality attributes like reusability, changeability, understandability and extensibility. It covers different categories of design smells including abstraction smells, encapsulation smells and modularization smells. Some examples of specific smells discussed are missing abstraction, leaky encapsulation, broken modularization etc. The document emphasizes the importance of addressing design smells through refactoring to improve design quality and reduce technical debt.

Microsoft Application Lifecycle Management (ALM) integrates governance, development, and operations from idea to retirement. Microsoft's ALM platform focuses on implementing process with minimal overhead, planning and managing projects, and aligning roles across the lifecycle. It allows reporting across project boundaries. The platform provides process templates, tools for planning and visibility, and ensures user comfort by allowing work in familiar tools. It aims to create happy teams and enable success throughout the application lifecycle.

The document discusses the software development life cycle (SDLC) and different SDLC models. It describes the waterfall model as a traditional sequential model where each phase must be completed before the next can begin. The key phases outlined are requirements collection, feasibility study, design, coding, testing and installation, and maintenance. The document notes both advantages of the waterfall model in producing a stable product when requirements do not change, and disadvantages in limiting flexibility and ability to incorporate new requirements.

Assure TotalView is an analytics solution for Application Delivery process. The solution enables end-to-end governance over your Application Lifecycle initiatives. Assure TotalView automatically collects relevant data from all of the operational tools that teams use in the Application Delivery process, and turns this data into meaningful metrics and dashboards for decision makers and stakeholders.