The document is a Software Quality Assurance Plan (SQAP) for the Smith Jones Rapid Transit (SJ-RT) project. It outlines the SQA roles, standards and processes that will be followed, including in-stage audits, stage exit reviews, and verification and validation of requirements. The SQA consultant will audit project deliverables and work products at key milestones to ensure quality.
This document discusses various aspects of project scheduling and risk management for software projects. It covers topics such as defining tasks, critical path analysis, earned value analysis, identifying risks, estimating risk probability and impact, and mitigating risks. The key aspects are determining the schedule using techniques like CPM, tracking progress through earned value analysis, and taking a proactive approach to risk management by identifying, analyzing, and developing plans to address potential risks.
Cole ready aim fire impact!- status impact analysis - nasaNASAPMC
The document discusses status impact analysis, a technique for analyzing schedule changes from one status period to the next. It identifies activities whose durations have increased, predecessors have been added, or milestones have been delayed. This focuses the project team on direct causes of schedule impacts. The status impact report can be generated quickly, saving time compared to manual analysis. It enhances and confirms other schedule analysis methods like earned value management and Monte Carlo simulation.
This document outlines the configuration management plan for the NexGen Project. It describes the roles and responsibilities for configuration management, including the Configuration Control Board, Project Sponsor, Project Manager, Configuration Manager, Lead Engineers, and Engineers. It also describes the processes for configuration control, the Configuration Management Database, configuration status accounting, and configuration audits to track changes throughout the project lifecycle.
The document discusses various aspects of software project management including project planning activities like estimation, scheduling, staffing, and risk handling. It describes different project organization structures like functional organization and project organization. It also discusses different team structures like chief programmer teams, democratic teams, and mixed teams. The document emphasizes the importance of careful project planning and producing a software project management plan document. It also discusses considerations for staffing a project team and attributes of a good software engineer.
121 r 85 - quality assurance systems for concrete constructioMOHAMMED SABBAR
This document provides guidance for developing a quality assurance system for concrete construction projects. It recommends that the system involve identifying quality objectives and incorporating them into a quality assurance plan. This plan is then implemented through quality assurance programs by the various project organizations. The system is intended to be flexible enough to account for differences in project size, complexity, owner needs, and skills of involved parties. It provides a framework for administrative aspects, developing a quality assurance plan, and elements of quality assurance programs.
CDS Construction Execution Process ^0 StrategyRobert Doig
The document outlines the key stages and milestones in developing a construction execution plan for an engineering project from early design through construction completion. It includes: 1) Defining the work breakdown structure and construction areas in early design; 2) Developing construction planning documents like the quality plan and execution strategy in front-end engineering design; 3) Contractors providing detailed cost estimates, schedules and execution plans before starting construction; 4) Contractors reporting on progress, quality and costs during construction; and 5) Completing construction and turning the project over once complete. The overall process focuses on work planning, quality control, and performance monitoring to deliver the project on schedule and budget.
The document discusses key aspects of software project planning including process planning, effort estimation, schedule and resource estimation, and quality planning. It emphasizes that effective project management is important for project success. Project planning aims to create a plan to meet commitments by defining processes, estimating effort, creating a schedule and milestones, and defining quality objectives and risk plans. Estimation models like COCOMO are discussed for estimating effort based on project size and characteristics.
This document discusses various aspects of project scheduling and risk management for software projects. It covers topics such as defining tasks, critical path analysis, earned value analysis, identifying risks, estimating risk probability and impact, and mitigating risks. The key aspects are determining the schedule using techniques like CPM, tracking progress through earned value analysis, and taking a proactive approach to risk management by identifying, analyzing, and developing plans to address potential risks.
Cole ready aim fire impact!- status impact analysis - nasaNASAPMC
The document discusses status impact analysis, a technique for analyzing schedule changes from one status period to the next. It identifies activities whose durations have increased, predecessors have been added, or milestones have been delayed. This focuses the project team on direct causes of schedule impacts. The status impact report can be generated quickly, saving time compared to manual analysis. It enhances and confirms other schedule analysis methods like earned value management and Monte Carlo simulation.
This document outlines the configuration management plan for the NexGen Project. It describes the roles and responsibilities for configuration management, including the Configuration Control Board, Project Sponsor, Project Manager, Configuration Manager, Lead Engineers, and Engineers. It also describes the processes for configuration control, the Configuration Management Database, configuration status accounting, and configuration audits to track changes throughout the project lifecycle.
The document discusses various aspects of software project management including project planning activities like estimation, scheduling, staffing, and risk handling. It describes different project organization structures like functional organization and project organization. It also discusses different team structures like chief programmer teams, democratic teams, and mixed teams. The document emphasizes the importance of careful project planning and producing a software project management plan document. It also discusses considerations for staffing a project team and attributes of a good software engineer.
121 r 85 - quality assurance systems for concrete constructioMOHAMMED SABBAR
This document provides guidance for developing a quality assurance system for concrete construction projects. It recommends that the system involve identifying quality objectives and incorporating them into a quality assurance plan. This plan is then implemented through quality assurance programs by the various project organizations. The system is intended to be flexible enough to account for differences in project size, complexity, owner needs, and skills of involved parties. It provides a framework for administrative aspects, developing a quality assurance plan, and elements of quality assurance programs.
CDS Construction Execution Process ^0 StrategyRobert Doig
The document outlines the key stages and milestones in developing a construction execution plan for an engineering project from early design through construction completion. It includes: 1) Defining the work breakdown structure and construction areas in early design; 2) Developing construction planning documents like the quality plan and execution strategy in front-end engineering design; 3) Contractors providing detailed cost estimates, schedules and execution plans before starting construction; 4) Contractors reporting on progress, quality and costs during construction; and 5) Completing construction and turning the project over once complete. The overall process focuses on work planning, quality control, and performance monitoring to deliver the project on schedule and budget.
The document discusses key aspects of software project planning including process planning, effort estimation, schedule and resource estimation, and quality planning. It emphasizes that effective project management is important for project success. Project planning aims to create a plan to meet commitments by defining processes, estimating effort, creating a schedule and milestones, and defining quality objectives and risk plans. Estimation models like COCOMO are discussed for estimating effort based on project size and characteristics.
Planning Phase Part I - Project Phases and Lifecycle PlanningEmanuele Della Valle
This document provides an overview of the planning phase and project lifecycles for software projects. It discusses the typical phases of a project including concept exploration, requirements, analysis and design, development, integration and testing, and deployment. It also describes different lifecycle models like waterfall and iterative development. The document is intended to teach project managers about establishing a project plan and selecting an appropriate lifecycle model.
This document discusses software quality infrastructure components and procedures and work instructions. It provides details on:
- The need for standardized procedures to efficiently perform tasks and communicate between teams.
- A conceptual hierarchy from international standards to organizational policies to procedures to work instructions.
- The contents and organization of procedures manuals and work instruction manuals.
- Training, certification, and performance follow-up of staff to ensure conformity with standards.
- Software configuration management including identifying software configuration items, controlling changes, and releasing versions.
This document summarizes an enterprise excellence project to reduce spending on repairing and scrapping temporary management equipment. The project charter establishes reducing total repair and scrap expense as the goal. A core team is defined and tollgate reviews are scheduled for defining, measuring, analyzing, improving, and controlling the process. Stakeholder needs are identified, including the need for clear repair/scrap criteria and invoice processes. Next steps include creating a measurement plan and assessing process improvements. The tollgate review for measuring the process is scheduled for January 26th.
This document provides an overview of software project management and processes at Infosys. It discusses how Infosys uses a project database, process capability baseline, process assets, and body of knowledge to build an infrastructure for project planning and management. This infrastructure aims to capture lessons learned from past projects to help plan and execute new projects more effectively. The document also describes Infosys' standard development process and how projects tailor this process.
The WBS is the touchstone of all work activities, cost, schedule, and technical performance on the program.
It describes technical, process, and programmatic deliverables over the life of the program
It describes how these deliverables are related through a well formed tree structure – parents and children – defined by MIL-STD-881C
It describes how costs are assigned to this work and these costs roll up to their parents in Control Account and CLINS to the Performance Measurement Baseline (PMB)
CCI PM Processes (within PMP Process Groups and Knowledge Areas)Pamela Garrett
The document outlines the key knowledge areas and processes for project management. It provides guidance on activities for each process group (initiating, planning, executing, monitoring/controlling, closing) within each knowledge area. This includes developing proposals and plans, executing work, monitoring costs and quality, and closing out the project. Stakeholder management and communications are emphasized throughout the project life cycle. Risks and procurements are also planned for and managed.
The document discusses various software project metrics that can be used at different stages of development. It describes function-oriented metrics like function points which measure functionality delivered and are language independent. It also discusses object-oriented, use-case oriented and quality metrics like defects per KLOC and maintainability. Defect removal efficiency is introduced as a measure of quality assurance activities in filtering defects.
This document provides a project management plan template for the SmartVoice project. It includes sections on the project management approach, scope, milestones, schedule, change management, communications, cost, procurement, scope, schedule, quality, risk, staffing, resources, cost and quality baselines, and sponsor acceptance. The project manager, Joe Green, will be responsible for managing the project according to this plan and its subsidiary plans. The project involves developing new voice recognition software and will be completed when the software and documentation are transitioned to production.
This document discusses software maintenance. It defines software maintenance as the modification of a software product after delivery to correct faults, improve performance, or adapt to changes. Approximately 40-70% of software costs are for maintenance over the 5-10 year lifespan of a product. Maintenance includes correcting errors, enhancing capabilities, removing obsolete features, and optimizing performance. The goals of maintenance are to fix bugs, enhance functionality, update the software, and adapt it to environmental changes. The majority of maintenance work is perfective and adaptive in nature. The document outlines best practices for development and management to improve maintainability.
The document outlines the 10 step process for project planning according to PRINCE2 methodology. The 10 steps include: 1) selecting the project, 2) identifying objectives and scope, 3) establishing infrastructure, 4) analyzing characteristics, 5) identifying products and activities, 6) estimating effort for each activity, 7) identifying risks, 8) allocating resources, 9) reviewing and publicizing the plan, and 10) executing the plan through lower level planning as the project progresses. Each step provides detailed guidance on tasks to complete the planning for a project according to PRINCE2 standards.
Link Resources Inc. has experience providing technical support services to various DOE sites and contractors,
including LANL, INTEC, Fluor, BWXT Y-12, and others. Some examples of the support provided include
conducting readiness assessments and operational readiness reviews, evaluating compliance with conduct of
operations requirements, and monitoring project operations to provide guidance on safety, quality and efficiency
improvements. Link also developed transition plans and cost estimates to support proposals for new contracts at
sites like the Portsmouth Gaseous Diffusion Plant.
Bindu Sharma is seeking a position as a Program Manager and has over 10 years of experience successfully managing projects exceeding $2M in contract value and over 15 engineers. She currently works as a Program Manager for OnRule, where she manages regulatory compliance projects for clients, and has previously worked as an Engineering Program Manager and Project Coordinator. She is a certified PMP with a Master's degree in engineering.
This document discusses project time management. It begins by outlining the importance of completing projects on time to meet customer needs and match resource availability with project progress. Some key challenges to project time management are then presented, including delays, changes to plans, and availability of labor and materials. Specific time stealers like regulatory delays are also called out. The remainder of the document focuses on best practices for project time management, including defining activities, sequencing activities, estimating durations and developing the project schedule and baseline. It emphasizes using tools like critical path methodology to determine float and identify the critical path. The importance of controlling the project schedule is also stressed.
This document discusses project scheduling for software engineering projects. It covers key topics such as:
- The importance of scheduling for establishing a roadmap and tracking progress on large, complex software projects.
- Basic principles of software project scheduling including compartmentalizing work, indicating interdependencies, allocating time and resources, and assigning responsibilities.
- Methods for defining tasks, networks, and timelines to plan and track schedules.
- Techniques for monitoring schedule performance such as status meetings, milestone tracking, and earned value analysis.
- Factors that influence schedules such as risks, changing requirements, estimates, and technical difficulties.
Dennis Kozich has over 30 years of experience in quality assurance and project management roles in the nuclear power industry. He holds multiple certifications including Certified Quality Auditor, Certified Manager of Quality/Organizational Excellence, and Certified Project Management Professional. His resume details his work history starting with the US Navy and then roles at nuclear power plants, engineering firms, and as a consultant providing quality assurance and project management services to various nuclear projects.
This document discusses project scope management. It defines project scope as the work involved in creating project deliverables and processes. Scope management ensures stakeholders agree on what will be delivered. Good scope management is important for project success and prevents common causes of failure like improper scope. Key scope management processes include scope verification, where the scope is formally accepted, and scope change control to manage any changes to the project scope. The document provides examples of scope planning tools like the scope statement and work breakdown structure used to define deliverables and divide work into manageable components.
Process Certification Implementation Presentationmdmilward
The document summarizes Hamilton Sundstrand's implementation strategy for process certification (Six Sigma) at their Windsor Locks, Connecticut facility. Key aspects included establishing a process certification council and steering committees to oversee the effort. Standard work, procedures, systems and infrastructure were developed to support data collection, analysis and reporting. Training programs were implemented to develop black belts and green belts across internal operations and supplier sites. The results were reported as reductions in cost of poor quality, variation and improvements in customer satisfaction scores and certification levels.
Pmo, project objectives and project life cyclesSoftServe
This document discusses project objectives and project life cycles. It defines goals as high-level statements of what a project aims to accomplish, while objectives are concrete statements of what a project aims to achieve. Objectives should be specific, measurable, achievable, relevant and time-bound (SMART). The document also discusses different types of project objectives and compares project life cycles with software development life cycles. It provides examples of various software development life cycle models including waterfall, prototyping, rapid application development, spiral, adaptive/agile models like Scrum and extreme programming.
This document provides an overview of the project management lifecycle, which consists of 5 phases: 1) Project Origination, 2) Project Initiation, 3) Project Planning, 4) Project Execution and Control, and 5) Project Closeout. It describes the key tasks and objectives of each phase, and explains how the project management lifecycle works alongside a project's specific lifecycle to manage the project from start to finish. The project management lifecycle is the same for all projects, while the specific project lifecycle may differ depending on the type of product or service being developed.
Tuli eServices follows an Agile development process optimized for globally distributed projects. They deliver features monthly through demonstrable and tested releases. When a client provides requirements, Tuli analyzes and discusses to finalize specifications before development begins. Features are prioritized and grouped into planned monthly releases. Risks are monitored and the client is updated on progress regularly through communication channels like weekly status calls. Version control of code and bug tracking tools are used. Testing occurs throughout development against defined requirements and plans.
This document discusses software process models and the software development life cycle (SDLC). It describes the key components of a software process including development, project management, configuration control, and process management processes. The document then explains popular SDLC models like the waterfall model, prototyping, iterative development, and agile processes. The waterfall model is discussed in detail, outlining its sequential phases and advantages like being simple and systematic, while also noting disadvantages like inability to adapt to changes and late delivery.
Agile lifecycle handbook by bhawani nandan prasadBhawani N Prasad
The document summarizes the Scrum agile software development lifecycle, which consists of three phases: pre-game, development iterations, and post-game. The pre-game phase includes pre-planning, architecture/design, and sprint planning. The development phase involves iterative sprints of 1-4 weeks. Each sprint includes analysis, design, coding, testing, and daily scrums. The post-game phase involves product integration, testing, documentation, training, and deployment. The overall process is iterative and incremental, with working software delivered in each sprint.
Planning Phase Part I - Project Phases and Lifecycle PlanningEmanuele Della Valle
This document provides an overview of the planning phase and project lifecycles for software projects. It discusses the typical phases of a project including concept exploration, requirements, analysis and design, development, integration and testing, and deployment. It also describes different lifecycle models like waterfall and iterative development. The document is intended to teach project managers about establishing a project plan and selecting an appropriate lifecycle model.
This document discusses software quality infrastructure components and procedures and work instructions. It provides details on:
- The need for standardized procedures to efficiently perform tasks and communicate between teams.
- A conceptual hierarchy from international standards to organizational policies to procedures to work instructions.
- The contents and organization of procedures manuals and work instruction manuals.
- Training, certification, and performance follow-up of staff to ensure conformity with standards.
- Software configuration management including identifying software configuration items, controlling changes, and releasing versions.
This document summarizes an enterprise excellence project to reduce spending on repairing and scrapping temporary management equipment. The project charter establishes reducing total repair and scrap expense as the goal. A core team is defined and tollgate reviews are scheduled for defining, measuring, analyzing, improving, and controlling the process. Stakeholder needs are identified, including the need for clear repair/scrap criteria and invoice processes. Next steps include creating a measurement plan and assessing process improvements. The tollgate review for measuring the process is scheduled for January 26th.
This document provides an overview of software project management and processes at Infosys. It discusses how Infosys uses a project database, process capability baseline, process assets, and body of knowledge to build an infrastructure for project planning and management. This infrastructure aims to capture lessons learned from past projects to help plan and execute new projects more effectively. The document also describes Infosys' standard development process and how projects tailor this process.
The WBS is the touchstone of all work activities, cost, schedule, and technical performance on the program.
It describes technical, process, and programmatic deliverables over the life of the program
It describes how these deliverables are related through a well formed tree structure – parents and children – defined by MIL-STD-881C
It describes how costs are assigned to this work and these costs roll up to their parents in Control Account and CLINS to the Performance Measurement Baseline (PMB)
CCI PM Processes (within PMP Process Groups and Knowledge Areas)Pamela Garrett
The document outlines the key knowledge areas and processes for project management. It provides guidance on activities for each process group (initiating, planning, executing, monitoring/controlling, closing) within each knowledge area. This includes developing proposals and plans, executing work, monitoring costs and quality, and closing out the project. Stakeholder management and communications are emphasized throughout the project life cycle. Risks and procurements are also planned for and managed.
The document discusses various software project metrics that can be used at different stages of development. It describes function-oriented metrics like function points which measure functionality delivered and are language independent. It also discusses object-oriented, use-case oriented and quality metrics like defects per KLOC and maintainability. Defect removal efficiency is introduced as a measure of quality assurance activities in filtering defects.
This document provides a project management plan template for the SmartVoice project. It includes sections on the project management approach, scope, milestones, schedule, change management, communications, cost, procurement, scope, schedule, quality, risk, staffing, resources, cost and quality baselines, and sponsor acceptance. The project manager, Joe Green, will be responsible for managing the project according to this plan and its subsidiary plans. The project involves developing new voice recognition software and will be completed when the software and documentation are transitioned to production.
This document discusses software maintenance. It defines software maintenance as the modification of a software product after delivery to correct faults, improve performance, or adapt to changes. Approximately 40-70% of software costs are for maintenance over the 5-10 year lifespan of a product. Maintenance includes correcting errors, enhancing capabilities, removing obsolete features, and optimizing performance. The goals of maintenance are to fix bugs, enhance functionality, update the software, and adapt it to environmental changes. The majority of maintenance work is perfective and adaptive in nature. The document outlines best practices for development and management to improve maintainability.
The document outlines the 10 step process for project planning according to PRINCE2 methodology. The 10 steps include: 1) selecting the project, 2) identifying objectives and scope, 3) establishing infrastructure, 4) analyzing characteristics, 5) identifying products and activities, 6) estimating effort for each activity, 7) identifying risks, 8) allocating resources, 9) reviewing and publicizing the plan, and 10) executing the plan through lower level planning as the project progresses. Each step provides detailed guidance on tasks to complete the planning for a project according to PRINCE2 standards.
Link Resources Inc. has experience providing technical support services to various DOE sites and contractors,
including LANL, INTEC, Fluor, BWXT Y-12, and others. Some examples of the support provided include
conducting readiness assessments and operational readiness reviews, evaluating compliance with conduct of
operations requirements, and monitoring project operations to provide guidance on safety, quality and efficiency
improvements. Link also developed transition plans and cost estimates to support proposals for new contracts at
sites like the Portsmouth Gaseous Diffusion Plant.
Bindu Sharma is seeking a position as a Program Manager and has over 10 years of experience successfully managing projects exceeding $2M in contract value and over 15 engineers. She currently works as a Program Manager for OnRule, where she manages regulatory compliance projects for clients, and has previously worked as an Engineering Program Manager and Project Coordinator. She is a certified PMP with a Master's degree in engineering.
This document discusses project time management. It begins by outlining the importance of completing projects on time to meet customer needs and match resource availability with project progress. Some key challenges to project time management are then presented, including delays, changes to plans, and availability of labor and materials. Specific time stealers like regulatory delays are also called out. The remainder of the document focuses on best practices for project time management, including defining activities, sequencing activities, estimating durations and developing the project schedule and baseline. It emphasizes using tools like critical path methodology to determine float and identify the critical path. The importance of controlling the project schedule is also stressed.
This document discusses project scheduling for software engineering projects. It covers key topics such as:
- The importance of scheduling for establishing a roadmap and tracking progress on large, complex software projects.
- Basic principles of software project scheduling including compartmentalizing work, indicating interdependencies, allocating time and resources, and assigning responsibilities.
- Methods for defining tasks, networks, and timelines to plan and track schedules.
- Techniques for monitoring schedule performance such as status meetings, milestone tracking, and earned value analysis.
- Factors that influence schedules such as risks, changing requirements, estimates, and technical difficulties.
Dennis Kozich has over 30 years of experience in quality assurance and project management roles in the nuclear power industry. He holds multiple certifications including Certified Quality Auditor, Certified Manager of Quality/Organizational Excellence, and Certified Project Management Professional. His resume details his work history starting with the US Navy and then roles at nuclear power plants, engineering firms, and as a consultant providing quality assurance and project management services to various nuclear projects.
This document discusses project scope management. It defines project scope as the work involved in creating project deliverables and processes. Scope management ensures stakeholders agree on what will be delivered. Good scope management is important for project success and prevents common causes of failure like improper scope. Key scope management processes include scope verification, where the scope is formally accepted, and scope change control to manage any changes to the project scope. The document provides examples of scope planning tools like the scope statement and work breakdown structure used to define deliverables and divide work into manageable components.
Process Certification Implementation Presentationmdmilward
The document summarizes Hamilton Sundstrand's implementation strategy for process certification (Six Sigma) at their Windsor Locks, Connecticut facility. Key aspects included establishing a process certification council and steering committees to oversee the effort. Standard work, procedures, systems and infrastructure were developed to support data collection, analysis and reporting. Training programs were implemented to develop black belts and green belts across internal operations and supplier sites. The results were reported as reductions in cost of poor quality, variation and improvements in customer satisfaction scores and certification levels.
Pmo, project objectives and project life cyclesSoftServe
This document discusses project objectives and project life cycles. It defines goals as high-level statements of what a project aims to accomplish, while objectives are concrete statements of what a project aims to achieve. Objectives should be specific, measurable, achievable, relevant and time-bound (SMART). The document also discusses different types of project objectives and compares project life cycles with software development life cycles. It provides examples of various software development life cycle models including waterfall, prototyping, rapid application development, spiral, adaptive/agile models like Scrum and extreme programming.
This document provides an overview of the project management lifecycle, which consists of 5 phases: 1) Project Origination, 2) Project Initiation, 3) Project Planning, 4) Project Execution and Control, and 5) Project Closeout. It describes the key tasks and objectives of each phase, and explains how the project management lifecycle works alongside a project's specific lifecycle to manage the project from start to finish. The project management lifecycle is the same for all projects, while the specific project lifecycle may differ depending on the type of product or service being developed.
Tuli eServices follows an Agile development process optimized for globally distributed projects. They deliver features monthly through demonstrable and tested releases. When a client provides requirements, Tuli analyzes and discusses to finalize specifications before development begins. Features are prioritized and grouped into planned monthly releases. Risks are monitored and the client is updated on progress regularly through communication channels like weekly status calls. Version control of code and bug tracking tools are used. Testing occurs throughout development against defined requirements and plans.
This document discusses software process models and the software development life cycle (SDLC). It describes the key components of a software process including development, project management, configuration control, and process management processes. The document then explains popular SDLC models like the waterfall model, prototyping, iterative development, and agile processes. The waterfall model is discussed in detail, outlining its sequential phases and advantages like being simple and systematic, while also noting disadvantages like inability to adapt to changes and late delivery.
Agile lifecycle handbook by bhawani nandan prasadBhawani N Prasad
The document summarizes the Scrum agile software development lifecycle, which consists of three phases: pre-game, development iterations, and post-game. The pre-game phase includes pre-planning, architecture/design, and sprint planning. The development phase involves iterative sprints of 1-4 weeks. Each sprint includes analysis, design, coding, testing, and daily scrums. The post-game phase involves product integration, testing, documentation, training, and deployment. The overall process is iterative and incremental, with working software delivered in each sprint.
The document discusses elements that should be included in development and quality plans for software projects. It provides details on what should be covered in each plan, including deliverables, milestones, risks, resources, and testing. The development plan should define project scope, schedule, roles and tasks, while the quality plan outlines goals, reviews, tests and configuration management. Both plans are major elements for meeting standards like ISO29110 and CMMI. The document uses examples to illustrate how elements in each plan can be specified, such as deliverables tables, review activities, and test cases.
The document discusses the Software Development Life Cycle (SDLC) and Software Testing Life Cycle (STLC). It describes the various phases of SDLC like requirements gathering, analysis, design, coding, testing, and deployment. It then explains the stages of STLC in more detail - requirements analysis, test planning, test case development, environment setup, test execution, and test closure. Finally, it provides definitions related to the bug life cycle and its flow chart.
This document discusses software quality assurance (SQA) systems. It describes six main components of an SQA system: pre-project, project life cycle, infrastructure for error prevention/improvement, management, standards/certification/assessment, and organization. It also discusses SQA considerations like software complexity, classification of SQA components, and factors to consider when constructing an organization's SQA system.
Introduction To Software Quality Assuranceruth_reategui
The document discusses software quality assurance (SQA) and defines key terms and concepts. It outlines the components of an SQA plan according to IEEE standard 730, including required sections, documentation to review, standards and metrics, and types of reviews. It also summarizes approaches to SQA from the Software Capability Maturity Model and the Rational Unified Process.
The document discusses software development lifecycles and strategies. It describes:
1) Common lifecycle activities like planning, development, testing and maintenance. Different models can be used depending on the product.
2) Solution strategies are developed to determine the nature of possible solutions and provide a framework for design and implementation. The best strategies are developed by trained groups using techniques like brainstorming.
3) The phased lifecycle model involves a series of defined activities with inputs, processes, and outputs at each phase. Resources are required to complete each defined phase.
The document discusses various aspects of planning and managing the software development process, including:
1) Developing a solution strategy and selecting a software life cycle model to provide a framework for the project.
2) Common software life cycle activities like planning, development, testing, and maintenance.
3) Using milestones, documents, and reviews to improve project visibility and management.
4) Organizing development tasks and teams using different structures like project, functional, and matrix formats.
The document describes a software development process that consists of four phases: inception, elaboration, construction, and transition. Each phase has milestones and deliverables. Statuses are reported through a project management system to track progress, communication, tasks, and milestones. Testing follows a V-model where testing is integrated throughout development.
The document describes the development process used by Classic Informatics Private Limited which includes defining requirements, planning and designing, application development, testing, debugging, and deployment. Key aspects of the process are prototyping, modular releases, periodic client updates, checklists, a defined architecture, common libraries, knowledge management, and task/bug tracking. A separate section outlines the quality control process which involves quality planning, testing according to test plans and cases, fixing bugs, and regression testing until all issues are closed.
This document provides a project management plan for the SmartVoice project at Total Software Incorporated (TSI). It includes sections on the project management approach, project scope, milestone list, schedule baseline and work breakdown structure (WBS), change management plan, communications management plan, cost management plan, and other key areas. The plan establishes roles and responsibilities, defines the project scope, outlines the schedule and milestones, and provides guidance on managing changes, communications, costs, and other critical aspects of the project to help ensure its successful execution.
The document provides a project charter and plan for upgrading Middlesex School's Sage Millennium fundraising software from version 7.7 to 7.9 Service Pack 2. The project has 7 phases: 1) planning, 2) analyzing the current system, 3) implementing and testing a new system, 4) reviewing new functionality, 5) training users, 6) going live with the new system, and 7) optimizing post go-live. The project aims to have the new system online by the end of the fiscal year on July 15, 2012.
The document discusses project closure and the importance of project closure analysis. It defines project closure analysis as a process to analyze what went well and what didn't on a project in order to improve future projects. Key information like effort, size, defects, risks, and lessons learned are captured in a project closure report and stored in a process database to benefit future projects.
The document discusses the various components of software quality assurance (SQA) systems that can be classified into six main classes: pre-project quality components, project life cycle components, infrastructure error preventive and improvement components, software quality management components, standardization, certification and SQA assessment components, and organizing for SQA – the human components. It provides details on various SQA activities like reviews, expert opinions, software testing, software maintenance, and ensuring quality of subcontractors' work. It also discusses documentation control and configuration management as important SQA components.
Stepwise Project planning in software developmentProf Ansari
The following activities are:
Identify objectives and practical measures of the effectiveness in meeting those objectives.
Establish a project authority
Stakeholder analysis – identify all stakeholders in the project and their interests
Modify objectives in the light of stakeholder’s analysis
Establish methods of communication with all parties
2.4
Are you thinking to craft a good PPT on project execution? Not to worry! We have come up with the project execution PowerPoint presentation slides that will help you build up your key program deliverables. Using our project management PPT designs, you can promote your business plan by specifying project quality management, work plan, etc. Furthermore, these control execution PPT graphics have been incorporated by highly qualified designers & with extensive research. Furthermore, our project development presentation illustrations cover all the related templates such as project progress summary, issues management, line chart, clustered column chart and many more. What more do you expect? In addition to this, execution plan PowerPoint designs can also be used for similar topics such as program documentation, execution plan, earned value management, risk analysis matrix, resource allocation, critical path method, product benefit realization, program charter, and responsibility assignment matrix. So without wasting your time, just grab our PowerPoint Visuals. Evaluate concepts with our Project Execution PowerPoint Presentation Slides. Be able to assess the depth behind it.
This document outlines procedures for reviewing a 3D model at various milestones throughout a project. It establishes formal reviews at 30%, 60%, and 90% completion to ensure the model incorporates the latest design inputs and meets requirements. Weekly reviews are also required to track progress and address comments. The objectives are to check for functionality, engineering requirements, constructability, and interfaces between disciplines. Requirements and expectations are defined for each review milestone. All relevant stakeholders must participate in the reviews.
The document discusses the Software Testing Life Cycle (STLC) process. There are 6 major phases in the STLC model: requirement analysis, test planning, test case development, test environment setup, test execution, and test closure activities. The goal of the STLC is to ensure software quality goals are met by conducting a sequence of testing activities. Key steps include understanding requirements, creating test plans and cases, setting up testing environments, executing tests, and closing out testing upon product delivery.
3 Simple Steps To Buy Verified Payoneer Account In 2024SEOSMMEARTH
Buy Verified Payoneer Account: Quick and Secure Way to Receive Payments
Buy Verified Payoneer Account With 100% secure documents, [ USA, UK, CA ]. Are you looking for a reliable and safe way to receive payments online? Then you need buy verified Payoneer account ! Payoneer is a global payment platform that allows businesses and individuals to send and receive money in over 200 countries.
If You Want To More Information just Contact Now:
Skype: SEOSMMEARTH
Telegram: @seosmmearth
Gmail: seosmmearth@gmail.com
Digital Transformation and IT Strategy Toolkit and TemplatesAurelien Domont, MBA
This Digital Transformation and IT Strategy Toolkit was created by ex-McKinsey, Deloitte and BCG Management Consultants, after more than 5,000 hours of work. It is considered the world's best & most comprehensive Digital Transformation and IT Strategy Toolkit. It includes all the Frameworks, Best Practices & Templates required to successfully undertake the Digital Transformation of your organization and define a robust IT Strategy.
Editable Toolkit to help you reuse our content: 700 Powerpoint slides | 35 Excel sheets | 84 minutes of Video training
This PowerPoint presentation is only a small preview of our Toolkits. For more details, visit www.domontconsulting.com
Zodiac Signs and Food Preferences_ What Your Sign Says About Your Tastemy Pandit
Know what your zodiac sign says about your taste in food! Explore how the 12 zodiac signs influence your culinary preferences with insights from MyPandit. Dive into astrology and flavors!
Event Report - SAP Sapphire 2024 Orlando - lots of innovation and old challengesHolger Mueller
Holger Mueller of Constellation Research shares his key takeaways from SAP's Sapphire confernece, held in Orlando, June 3rd till 5th 2024, in the Orange Convention Center.
Taurus Zodiac Sign: Unveiling the Traits, Dates, and Horoscope Insights of th...my Pandit
Dive into the steadfast world of the Taurus Zodiac Sign. Discover the grounded, stable, and logical nature of Taurus individuals, and explore their key personality traits, important dates, and horoscope insights. Learn how the determination and patience of the Taurus sign make them the rock-steady achievers and anchors of the zodiac.
Building Your Employer Brand with Social MediaLuanWise
Presented at The Global HR Summit, 6th June 2024
In this keynote, Luan Wise will provide invaluable insights to elevate your employer brand on social media platforms including LinkedIn, Facebook, Instagram, X (formerly Twitter) and TikTok. You'll learn how compelling content can authentically showcase your company culture, values, and employee experiences to support your talent acquisition and retention objectives. Additionally, you'll understand the power of employee advocacy to amplify reach and engagement – helping to position your organization as an employer of choice in today's competitive talent landscape.
SATTA MATKA SATTA FAST RESULT KALYAN TOP MATKA RESULT KALYAN SATTA MATKA FAST RESULT MILAN RATAN RAJDHANI MAIN BAZAR MATKA FAST TIPS RESULT MATKA CHART JODI CHART PANEL CHART FREE FIX GAME SATTAMATKA ! MATKA MOBI SATTA 143 spboss.in TOP NO1 RESULT FULL RATE MATKA ONLINE GAME PLAY BY APP SPBOSS
FIA officials brutally tortured innocent and snatched 200 Bitcoins of worth 4...jamalseoexpert1978
Farman Ayaz Khattak and Ehtesham Matloob are government officials in CTW Counter terrorism wing Islamabad, in Federal Investigation Agency FIA Headquarters. CTW and FIA kidnapped crypto currency owner from Islamabad and snatched 200 Bitcoins those worth of 4 billion rupees in Pakistan currency. There is not Cryptocurrency Regulations in Pakistan & CTW is official dacoit and stealing digital assets from the innocent crypto holders and making fake cases of terrorism to keep them silent.
At Techbox Square, in Singapore, we're not just creative web designers and developers, we're the driving force behind your brand identity. Contact us today.
Navigating the world of forex trading can be challenging, especially for beginners. To help you make an informed decision, we have comprehensively compared the best forex brokers in India for 2024. This article, reviewed by Top Forex Brokers Review, will cover featured award winners, the best forex brokers, featured offers, the best copy trading platforms, the best forex brokers for beginners, the best MetaTrader brokers, and recently updated reviews. We will focus on FP Markets, Black Bull, EightCap, IC Markets, and Octa.
An introduction to the cryptocurrency investment platform Binance Savings.Any kyc Account
Learn how to use Binance Savings to expand your bitcoin holdings. Discover how to maximize your earnings on one of the most reliable cryptocurrency exchange platforms, as well as how to earn interest on your cryptocurrency holdings and the various savings choices available.
LA HUG - Video Testimonials with Chynna Morgan - June 2024Lital Barkan
Have you ever heard that user-generated content or video testimonials can take your brand to the next level? We will explore how you can effectively use video testimonials to leverage and boost your sales, content strategy, and increase your CRM data.🤯
We will dig deeper into:
1. How to capture video testimonials that convert from your audience 🎥
2. How to leverage your testimonials to boost your sales 💲
3. How you can capture more CRM data to understand your audience better through video testimonials. 📊
LA HUG - Video Testimonials with Chynna Morgan - June 2024
Qa plan1
1. SJ-RT
Smith Jones Rapid Transit
Software Quality Assurance Plan
February 1997
U. S. DEPARTMENT OF ENERGY
Replace with appropriate organization name
2. qa_plan1.doc ii 02/27/07
Change Control Page
The following information is being used to control and track modifications made to this
document.
1) Revision Date: mm/dd/yy
Author:
Section(s):
Page Number(s):
Summary of Change(s):
2) Revision Date: mm/dd/yy
Author:
Section(s):
Page Number(s):
Summary of Change(s):
3. qa_plan1.doc iii 02/27/07
Title Page
Document Name: Smith Jones Rapid Transit (SJ-RT)
Software Quality Assurance Plan (SQAP)
Publication Date: February 2007
Revision Date:
Contract Number:
Project Number:
Prepared by: M. Polo
Approval: __________________________
L. DaVinci, XX-XXX
5. qa_plan1.doc v 02/27/07
Preface
Document Version Control: It is the reader's responsibility to ensure they have the latest
version of this document. Questions should be directed to the owner of this document, or the
project manager.
Document Owner: The primary contact for questions regarding this document is:
G. Garibaldi DOE Software Management
Phone: (301) 999-9999
ccMail: G. Garibaldi at Lotus-01
Internet: g.garibaldi@hq.doe.gov
Privacy Information
This document may contain information of a sensitive nature. This information should not be
given to persons other than those who are involved in the SJ-RT project or who will become
involved during its lifecycle.
Please note: the statement above is for demonstration purposes only. There is no privacy
information included in this example document.
6. qa_plan1.doc 1 02/27/07
1. Introduction
This Software Quality Assurance Plan (SQAP) sets forth the process, methods, standards, and
procedures that will be used to perform the Software Quality Assurance function for the Smith
Jones Rapid Transit (SJ-RT) project. The SQAP follows the DOE Software Engineering
Methodology (SEM), modified to accommodate the project model adapted for the SJ-RT project.
1.1 Purpose and Scope
This SQAP provides a foundation for managing the SJ-RT software quality assurance activities,
and is based on project activities and work products as documented in the SJ-RT Project Plan.
This plan:
• Identifies the SQA responsibilities of the project team and the SQA consultant
• Defines SJ-RT reviews and audits and how they will be conducted
• Lists the activities, processes, and work products that the SQA consultant will review and
audit
• Identifies the SQA work products
1.2 Reference Documents
Reference materials used to develop the SJ-RT SQAP include:
• DOE Software Engineering Methodology, March 1996
• ANSI/IEEE Standard for Software Verification and Validation Plans
• Software Engineering Institute, SQA Key Process Area
1.3 Project Checkpoints (Stage Exits)
Each stage of development will have at least one formal checkpoint called a stage exit. When a
stage has been successfully exited, it indicates that all draft deliverables due to date have been
completed, all outstanding issues have acceptable action plans, and there is a sound plan for the
remainder of the project (detailed for the next stage). The project's designated approvers (sign-
off authorities) must provide a written position of concur/non-concur at stage exit. All affected
functional areas involved in the project also participate in and can provide input to the stage exit.
7. qa_plan1.doc 2 02/27/07
2. SQA Description
2.1 SQA Roles and Responsibilities
The following chart defines the SQA roles and responsibilities of the members of the project
team and their function at stage exit.
Note: Due to staffing fluctuations, if a particular person is unable to fulfill his/her
responsibilities, it will be the responsibility of the manager overseeing that area to
ensure a replacement, with appropriate skills and experience, on a timely basis.
Role Name Org. SQA Responsibility
Stage Exit
Function
QA
Manager
V.
Domenico
DOE
Software
Mgmt.
Manages the Quality Assurance
function.
Approve
(delegated
to QA
consultant)
System
Owner
M.
Raffaello
HR-XXX Helps define product quality
expectations. Represents
procurement users. Determines
final acceptance of SJ-RT.
Approve
QA
Consultant
G.
Garibaldi
DOE
Software
Mgmt.
Audits and approves project
deliverables from QA
perspective. Reviews plans and
deliverables for compliance with
applicable standards. Provides
guidance and assistance on
process matters.
Approve
Project
Manager
A.
Michelangelo
Software
Develop_
ment
Ensures implementation of
quality activities. Coordinates
resolution of issues. Provides
regular and timely
communications.
Conduct
Project
Manager's
manager
A.
Dante
Software
Develop_
ment
Monitors implementation of
quality activites. Receives
reports on SJ-RT quality efforts.
Resolves conflict across
organizations.
Approve
8. qa_plan1.doc 3 02/27/07
2.2 Required Skills
The Quality Assurance consultant must be able to review iterations of the Project Plan and
lifecycle work products to determine adherence to DOE and industry standards, as modified and
documented in the Project Plan, and provide expert assistance on project management practices
and software development process related matters.
This position will work independently from the development team to ensure objective audits of
the work products as they are being developed and objective reviews of project management
processes and stage exits.
9. qa_plan1.doc 4 02/27/07
3. Audits and Reviews
3.1 Standards
The SJ-RT Project Plan will follow the DOE Software Engineering Methodology (SEM)
standard and the DOE Project Plan Example. All lifecycle work product standards are
documented in the SJ-RT Project Plan. They include the following:
• ANSI/IEEE Guide to Software Requirements Specifications
• IEEE Guide to Software Design Descriptions
• IEEE Standard for Software User Documentation
3.2 In-Stage Audits and Reviews
Quality Assurance for this project will include at least one audit of all current draft deliverables
and selected work products in each stage of development. The reviews will assure that the
established system development and project management processes and procedures are being
followed effectively, and exposures and risks to the current Project Plan are identified and
addressed.
In-stage reviews, hereinafter referred-to as In-Stage Assessments (ISA), will be performed and
documented by the SJ-RT Quality Assurance consultant, in accordance with the DOE SEM In-
Stage Assessment Process Guide.
The following diagram depicts the In-Stage Assessment process flow for all SJ-RT development
stages:
10. qa_plan1.doc 5 02/27/07
In-Stage Assessment Process
┌─────────────────┐
│ SCHEDULE │ Secure agreement
│ THE │ on assessment
│ ASSESSMENT │ date
│ │
└────────┬────────┘
?
┌─────────────────┐
│ │ Development deliverables
│ RECEIVE │ Updated project plan
│ DELIVERABLES │ Walkthrough minutes
│ │ Other applicable items
└────────┬────────┘
?
┌─────────────────┐
│ CONDUCT │ Audit deliverables
│ THE │ Review project plan
│ ASSESSMENT │ Review other items
│ │ Formulate assessment
└────────┬────────┘
?
┌─────────────────┐
│ │ Assessment of risk to
│ PREPARE │ project plan
│ FINDINGS │ List of concerns
│ │ Recommendations
└────────┬────────┘
?
To Project Manager
Each deliverable and/or selected work product will be audited to make judgements as to the quality and
validity of the deliverable or work product. The assessment will include any verification or validation
activities performed since the last In-Stage Assessment. The reviewer will document the results of the
assessment using the In-Stage Assessment Report described below.
An issue will be logged if there is a problem without a visible plan for resolution. Once a list of issues
has been compiled, it will be reviewed with the project manager to see if any new or additional
information might mitigate or eliminate any of them. Remaining issues must be addressed with an
action plan from the project manager. Issues from an In-Stage Assessment near the end of a stage might
become "qualifications" to the current stage exit.
11. qa_plan1.doc 6 02/27/07
An assessment of risk to the schedule for both the next stage and the remainder of the project,
from the ISA reviewer's (QA consultant) perspective, will also be provided. Risk categories are
as follows:
Low - Potential or existing problems must be addressed to avoid an impact to the
current Project Plan. This would also apply if no issues were identified.
Medium - Problems exist that have a high probability of impacting the current Project
Plan or other dependencies.
High - Serious problems exist (without an acceptable plan to resolve) that have a
high probability of impacting user acceptance, the current Project Plan, or
other dependencies.
12. qa_plan1.doc 7 02/27/07
In-Stage Assessment Report
Project Name__________________________________________________________________
Stage of development Date_______________________
Reviewer Phone________________________
No. Issues/Concerns: Resolved
_________________________________________________________ ________
_________________________________________________________ ________
_________________________________________________________ ________
_________________________________________________________ ________
_________________________________________________________ ________
_________________________________________________________ ________
_________________________________________________________ ________
_________________________________________________________ ________
_________________________________________________________ ________
_________________________________________________________ ________
Assessment of risk to schedule:
Low Medium High
G G G For the next stage
G G G For the remainder of the project
13. qa_plan1.doc 8 02/27/07
3.3 Stage Exit Reviews
A Stage Exit is the vehicle for securing the concurrence (i.e., approval) of designated individuals
to continue with the project and move forward into the next stage of development. The
concurrence is an approval (sign-off) of all draft deliverables, including the Project Plan, and
selected stage work products produced to date. The deliverables and work products (if any) are
assured via the In-Stage Assessment process described previously. The Stage Exit indicates that
all qualifications (issues and concerns) have been closed or have an acceptable plan for
resolution.
The purpose of a Stage Exit is to:
• Allow all functional areas involved with the project to review the current Project Plan. This
includes, at a minimum, a detailed plan for the next stage, and high-level plans for the
remainder of the project.
• Provide a forum to raise qualifications (issues and concerns) if issues exist that will impact
the Project Plan.
• Ensure an acceptable action plan exists for all qualifications raised.
• Obtain concurrence on current stage draft deliverables, and to begin the next stage of
development.
With any software development/integration project, lifecycle stages may overlap as activities of
the new stage are beginning and activities of the previous stage are completing.
The Stage Exit process begins with a notification to the extended development team that a stage
exit has been scheduled. The process ends with the receipt of concurrence from the designated
approvers to proceed to the next stage. Concurrence indicates that all known issues have an
acceptable plan for resolution.
The following are the minimum inputs to the Stage Exit process:
• System development lifecycle deliverable(s)
• Current project plan
• Issues to be addressed (generic)
• Concurrence/qualifications from the approvers
• Issues that remain open from the last In-Stage Assessment
14. qa_plan1.doc 9 02/27/07
The following diagram depicts the Stage Exit process flow:
┌─────────────────┐
PLANNING │ │ Stage exit milestones
STAGE │ PLAN PROJECT's │ defined in the SQAP for
│ STAGE EXITS │ each stage
│ │
└─────────────────┘
┌─────────────────┐
ALL │ SCHEDULE │ Schedule exit for the
STAGES │ CURRENT │ current stage; notify
│ EXIT │ participants (memo)
│ │ │
│ └────────┬────────┘
│ ?
│ ┌─────────────────┐
│ │ DISTRIBUTE │ Distribute current proj.
│ │ CURRENT │ plan and other items
│ │ PROJECT │ needed to evaluate stage
│ │ PLAN │
│ └────────┬────────┘
│ ?
│ ┌─────────────────┐
│ │ │ Receive positions and
│ │ RECEIVE │ qualifications (if any)
│ │ POSITIONS │ from participants
│ │ │
│ └────────┬────────┘
│ ?
│ ┌─────────────────┐
│ │ │ Prepare plans to resolve
│ │ PREPARE │ qualifications (if any
│ │ ACTION PLANS │ were raised)
│ │ │
│ └────────┬────────┘
│ ?
│ ┌─────────────────┐
│ │ │ Present plans addressing
│ │ CONDUCT │ qualifications and
│ │ CLOSURE MEETING │ secure concurrence
│ │ │
│ └─────────────────┘
│
?
Each approver will respond to the SJ-RT Project Manager using the Stage Exit Position
Response form shown on the next page.
15. qa_plan1.doc 10 02/27/07
Stage Exit Position Response Form
Project name: Smith Jones Rapid Transit (SJ-RT)
Project stage:
Return form to: A. Michelangelo, Project Manager
Return by:
Position:
GConcur.
Proceed with the project according to the current Project Plan.
GConcur with qualifications.
Issue(s) exist. The project can proceed according to the current Project Plan if there is an acceptable action
plan for each issue by the stage exit meeting.
GNon-concur.
Significant issue(s) exist. The project should not proceed to the next stage until the issue(s) is resolved.
Qualifications (issues):
Approver: ______________________________________
(please print)
Signed: Date ______________
16. qa_plan1.doc 11 02/27/07
3.4 Peer Reviews
A minimum of one Structured Walkthrough (or peer review) will be performed on each lifecycle
deliverable.
17. qa_plan1.doc 12 02/27/07
4. Verification and Validation of Requirements
Verifying SJ-RT requirements at the end of the Preparation stage will establish the proper basis
for initiating the Software Design stage activities. The Functional Requirements Document
(FRD) must contain, at a minimum, documentation on the essential requirements (functions,
performance, design constraints, and attributes) of the software and its external interfaces.
The following IEEE definitions apply in this SQAP:
verification: The process of determining whether or not the products of a given stage of the
software development cycle fulfill the requirements established during the previous stage.
validation: The process of evaluating software at the end of the software development
process (acceptance testing activity in the Testing stage) to ensure compliance with software
requirements.
The term requirements encompasses the areas of hardware, user interface, operator, software
interface, functionality, performance, communications, security, access, and backup and
recovery.
4.1 Verification
The following activities will be performed as part of requirements verification:
• Produce a traceability matrix tracing all FRD requirements back to system objectives in the
SJ-RT Objectives Statement and forward to Software Design elements.
• Evaluate FRD requirements and relationships for correctness, consistency, completeness,
accuracy, readability and testability.
• Assess how well the FRD satisfies the SJ-RT system objectives.
• Assess the criticality of requirements to identify key performance or critical areas of software.
18. qa_plan1.doc 13 02/27/07
4.2 Validation
The following activities will be performed as part of requirements validation:
• Plan acceptance testing, including criteria for:
• compliance with all requirements
• adequacy of user documentation
• performance at boundaries and under stress conditions.
• Plan documentation of test tasks and results.
• Execute the Acceptance Test Plan.
• Document acceptance test results.
19. qa_plan1.doc 14 02/27/07
5. SQA Milestones
Based on the draft SJ-RT Master Schedule as of February 1997, following are the SJ-RT project
activities and work products that the QA consultant will review and audit:
Stage In-Stage
Assess.
Date
Stage Exit
Date
Deliverable
(date delivered)
Work Product
(date completed)
QA Activity
Planning 03/03/97 03/07/97 Project Plan
(02/24/97)
Project Schedule
(02/24/97)
ISA Process -
(review processes & audit
contents)
Preparation 04/08/97 04/08/97 Functional
Requirements
Document
Acquisition Plan
Installation Plan
Revised Project
Plan
ISA Process -
(review processes & audit
contents)
Software Design 05/29/97 06/05/97 Functional
Design
Document
Security Plans
Training Plan
Sys. Test Plan
Acceptance Plan
Conf. Mgmt. Pln.
Conversion Plan
Traceability
matrix
Revised Project
Plan
ISA Process -
(review processes & audit
contents)
Trace design components
to requirements
Trace requirements to
design components
Programming
and
Integration
09/25/97 09/30/97 Site Installation
Plan
System
documentation
(draft)
Revised Project
Plan
ISA Process -
(review processes & audit
contents)
System
Testing
and
Acceptance
12/04/97 12/22/97 Test results
System
documentation
(final)
Operational
system
Revised Project
Plan
ISA Process -
(review processes & audit
contents)