Documents about Type Issues Defects
Week03_PR_F03a_T05
USC, CSCI 577
Excerpt: ... Problem & Issue Report as of 10/01/2003 * See QMP for Definitions Type Issues Defects Problem Reports New Opened New Closed 4 0 0 1 1 0 Old Closed 0 1 1 Current 5 1 1 Weekxx_PR_S02b_Txx.xls ...
|
|
Week10_PR_F05a_T06
USC, CSCI 577
Excerpt: ... Planning Configuration Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code development Test Deployment Total Injected 18 14 Removed 18 14 32 32 32 defects found through ARB feedback Internal Reviews involved general improvement Problem Reports as of 11/23/2005: * See QMP or Below for Definitions Type Issues Defects Problem Reports Definitions Issues Defects Problem Reports New Opened 0 0 0 New Closed 0 0 0 Current 1 0 0 0 1 2* 1 outstanding old issue closed- LOS tables *2 outstanding old problem reports Old Closed Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Forms to collect that information. In that case, this will be the total ...
|
|
Week09_PR_F05a_T06
USC, CSCI 577
Excerpt: ... xx_PR_S02b_Txx.xls # of Defects Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code development Test Deployment Total Injected Removed 0 0 No defects found in the week Internal Reviews involved general improvement Problem Reports as of 11/16/2005: * See QMP or Below for Definitions Type Issues Defects Problem Reports Definitions Issues Defects Problem Reports New Opened 0 0 2 New Closed 0 0 1 Current 0 1 0 0 0 3* 1 outstanding old issue - LOS tables *2 outstanding old problem reports Old Closed Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Forms ...
|
|
Week11_PR_F08a_T03
USC, CSCI 577
Excerpt: ... ded to remind the DEN member over the phone one day before submission so that either he DEN Member didn't upload his QMP till completes or he asks someone else to do on his behalf 1 date due in Draft DC Package 2 3 4 5 Defect Counts Type Issues Defects Problem Reports New Opened 0 0 0 New Closed 0 0 0 Old Closed 0 1 0 Current 0 0 0 "Problem reports" and issues generated since last report "Old" are those in "current" in the previous report Issues Defects Problem Reports Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Forms to collect that information. In that case, this will be the total number of Concerns provided by the reviewers. Concers can ...
|
|
Week02_PR_S08b_T07
USC, CSCI 577
Excerpt: ... type work is being undertaken. Number of templates is approximately 10 Weeks Active 1 1 3 4 1 Weekxx_PR_S02b_Txx.xls # of Defects Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code development Test Deployment Total Injected Removed Problem Reports as of mm/dd/yyyy: * See QMP or Below for Definitions Type Issues Defects Problem Reports Definitions Issues Defects Problem Reports New Opened 2/6/2008 New Closed 0 0 Old Closed 0 Current 0 Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Forms to collect that information. In that case, this will be th ...
|
|
Week01_PR_S08b_T07
USC, CSCI 577
Excerpt: ... being undertaken. Number of templates is approximately 10 Weeks Active 1 1 3 4 1 Weekxx_PR_S02b_Txx.xls # of Defects Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code development Test Deployment Total Injected Removed Problem Reports as of mm/dd/yyyy: * See QMP or Below for Definitions Type Issues Defects Problem Reports Definitions Issues Defects Problem Reports New Opened 2/6/2008 New Closed 0 0 Old Closed 0 Current 0 Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Forms to collect that information. In that case, this will be the total numbe ...
|
|
Week04_PR_S08b_T07
USC, CSCI 577
Excerpt: ... ekxx_PR_S02b_Txx.xls # of Defects Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code development Test Deployment Total Injected Removed Problem Reports as of mm/dd/yyyy: * See QMP or Below for Definitions Type Issues Defects Problem Reports Definitions Issues Defects Problem Reports New Opened 2/6/2008 New Closed 0 0 Old Closed 0 Current 0 Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Forms to collect that information. In that case, this will be the total number of Concerns provided by the reviewers. Concers can be an issue, a defect or neither (c ...
|
|
Week01_PR_F04a_T14
USC, CSCI 577
Excerpt: ... from the client Weekxx_PR_S02b_Txx.xls Problem & Issue Report as of xx/yy/zzzz * See QMP or Below for Definitions Type Issues Defects Problem Reports New Opened New Closed Old Closed Current Definitions Issues Defects Problem Reports Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Un In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Weekxx_PR_S02b_Txx.xls e "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). tool. You can also use the Review Forms to collect that information. In that case, this will be the total number of Concerns provided by the reviewers. Concers can be an issue, a de Weekxx_PR_S02b_Txx.xls wers. Concers can be an issue, a defect or neither (consider that reviewers might indicate false def ...
|
|
Week12_PR_F04a_T07
USC, CSCI 577
Excerpt: ... 3 4 5 6 1 5 3 n/a 6 Scalability of visualization clustering algorithm Personnel Loss Inappropriately Modify open source component User has minimal knowledge of downloading data User misuse of the proposed system Test the system with large data Prepare easy-to-understand document for future developer members Thoroughly study the open source component Provide training to the user on how to knowledge the data Training and user manual 4 8 4 1 5 Weekxx_PR_S02b_Txx.xls Problem & Issue Report as of 11/7/2004 * See QMP or Below for Definitions Type Issues Defects Problem Reports New Opened New Closed Old Closed 1 1 0 0 0 0 Current 0 0 Weekxx_PR_S02b_Txx.xls List of third-party components being considered for use in the system as of 12/01/2004 Component Name Component use in the system Black Box White Box Modify Code x x x x implementation of graph clustering algorithm Function of the component in the system Related components Dependency Interaction h3viewer Open Motif SQLite Fast Markov clustering algori ...
|
|
Week03_PR_F04a_T1
USC, CSCI 577
Excerpt: ... ng available time. Study reports carefully to design them in simple ways that reports can be shown on HTML format. Find and evaluate free component in early stage. Do research on existing system to decide whether we should build new system based on existing one or we build new one from scratch. Weeks Active 3 2 3 2 4 Tight schedule Complex report module 3 3 4 3 Current system complexity 3 Weekxx_PR_S02b_Txx.xls Problem & Issue Report as of 10/06/2004 * See QMP or Below for Definitions Type Issues Defects Problem Reports New Opened New Closed Old Closed 0 0 0 0 0 0 24 14 0 Current 0 0 10 Definitions Issues Defects Problem Reports Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Un In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Weekxx_PR ...
|
|
Week06_PR_F04a_T01
USC, CSCI 577
Excerpt: ... blems (Complex report module) Current system instability (Current system complexity) Personnel changes 6 6 5 5 6 6 - 2 7 - Human resources unavailability 2 1adf2118b71a531937063560902cc499e38071ed.xls Problem & Issue Report as of 10/24/2004 * See QMP or Below for Definitions Type Issues Defects Problem Reports New Opened New Closed Old Closed 5 0 0 17 5 13 22 5 13 Current 14 12 17 1adf2118b71a531937063560902cc499e38071ed.xls List of third-party components being considered for use in the system as of 10/24/2004 Component Name Component use in the system Black Box x White Box Modify Code Function of the component in the system Related components Dependency Interaction Java-MySQL database driver Apache Tomcat Provides the application web-server for the system Java SDK 1.4.1 Redhat Linux 9.0, Solaris 2.1, Windows 2003 Redhat Linux 9.0, Solaris 2.1, Windows 2003 JDK 1.4.x MySQL JasperReports Provices persistent data storage for the system Generate and display report on webpage Java-MySQL d ...
|
|
Week04_PR_F04a_T1
USC, CSCI 577
Excerpt: ... o work with main-role member to verify and review the artifact. Prioritize requirements. Negotiate with the client to have critical features implemented first. Low priority features will be implemented if having available time. Study reports carefully to design them in simple ways that reports can be shown on HTML format. Find and evaluate free component in early stage. Do research on existing system to decide whether we should build new system based on existing one or we build new one from scratch. Weeks Active 4 2 - Personnel shortfalls 1 3 4 2 3 Tight schedule Complex report module 4 4 5 4 Current system complexity 4 Weekxx_PR_S02b_Txx.xls Problem & Issue Report as of 10/13/2004 * See QMP or Below for Definitions Type Issues Defects Problem Reports New Opened New Closed Old Closed 0 0 0 66 59 0 66 59 14 Current 0 11 10 Weekxx_PR_S02b_Txx.xls List of third-party components being considered for use in the system as of 10/13/2004 Component Name Component use in the system Black Box x x Whit ...
|
|
Week05_PR_F04a_T14
USC, CSCI 577
Excerpt: ... with team to come with test assesment plan,also 1 go through documentation provided by AXIS Have 2 meetings a week so that everyone can convey information about their progress 1 2 na 3 na Conflicting Schedules between team mates Old system will be unavailable for lookup after 10/01 4 5 Study the old system before 10/01 and obtain documentation 5 about it Weekxx_PR_S02b_Txx.xls Problem & Issue Report as of 10/20/2004 * See QMP or Below for Definitions Type Issues Defects Problem Reports New Opened New Closed Old Closed 6 6 18 0 0 0 0 0 0 Current 0 0 0 Definitions Issues Defects Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Forms to ...
|
|
Week03_PR_F04a_T14
USC, CSCI 577
Excerpt: ... efinitions Type Issues Defects Problem Reports New Opened New Closed Old Closed Current Definitions Issues Defects Problem Reports Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Un In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Weekxx_PR_S02b_Txx.xls e "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). tool. You can also use the Review Forms to collect that information. In that case, this will be the total number of Concerns provided by the reviewers. Concers can be an issue, a de Weekxx_PR_S02b_Txx.xls wers. Concers can be an issue, a defect or neither (consider that reviewers might indicate false defects). Weekxx_PR_S02b_Txx.xls List of third-party components being considered for use in the system as o ...
|
|
Week02_PR_F04a_T1
USC, CSCI 577
Excerpt: ... arch on existing system to decide whether we should build new system based on existing one or we build new one from scratch. Study reports carefully to design them in simple ways that reports can be shown on HTML format. Find and evaluate free component in early stage. Weeks Active 2 2 2 Tight schedule 2 3 4 3 4 Current system complexity Complex report module 2 2 Weekxx_PR_S02b_Txx.xls Problem & Issue Report as of 09/26/2004 * See QMP or Below for Definitions Type Issues Defects Problem Reports New Opened New Closed Old Closed 0 0 0 0 0 0 0 10 0 Current 0 0 0 Definitions Issues Defects Problem Reports Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Un In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Weekxx_PR_S02b_Txx.xls e "Author" h ...
|
|
Week07_PR_F04a_T01
USC, CSCI 577
Excerpt: ... ort component (COTS) problems (Complex report module) Current system instability (Current system complexity) Personnel changes 7 7 5 5 7 6 6 3 7 7 Human resources unavailability 3 54e167dedbe9a9ea61479fefae6587427ba7a205.xls Problem & Issue Report as of 10/31/2004 * See QMP or Below for Definitions Type Issues Defects Problem Reports New Opened New Closed Old Closed 1 0 10 12 5 10 13 5 9 Current 5 9 15 54e167dedbe9a9ea61479fefae6587427ba7a205.xls List of third-party components being considered for use in the system as of 10/24/2004 Component Name Component use in the system Black Box x White Box Modify Code Function of the component in the system Related components Dependency Interaction Java-MySQL database driver Apache Tomcat Provides the application web-server for the system Java SDK 1.4.1 Redhat Linux 9.0, Solaris 2.1, Windows 2003 Redhat Linux 9.0, Solaris 2.1, Windows 2003 JDK 1.4.x MySQL JasperReports Provices persistent data storage for the system Generate and display report on ...
|
|
Week02_PR_F04a_T14
USC, CSCI 577
Excerpt: ... ised us that out project would not be following the MBASE guidelines but would be following the CAB,CAP,CAR guidelines.The TA later confirmed this fact Study the operation of the previous system and get the documentation from the client We will be speaking to AXIS clinical s/w about the access 1 No Yes 2 1 Yes No No Yes No Yes We went to client location to have a look at the new PATS system.We attended a training session organised by AXIS Clinical software Lack of Clarification About How To Evaluate the Come up with a plan on how this should be done and consult with the client. Some research about STS's criteria for Organization Between STS and its Vendor certifying its vendors is needed. 2 2 Weekxx_PR_S02b_Txx.xls Problem & Issue Report as of 09/28/2004 * See QMP or Below for Definitions Type Issues Defects Problem Reports New Opened New Closed Old Closed Current Definitions Issues Defects Problem Reports Issues are problems that the "Author" can not fix solely in the artifact or at that ...
|
|
Week04_PR_F04a_T14
USC, CSCI 577
Excerpt: ... cases 3 na BusinesscaseanalysisofPATS 4 na Oldsystemwillbeunavailableforlookupafter 10/01 Brainstormwithteamtocomewithtestassesmentplan,also 1 gothroughdocumentationprovidedbyAXIS discusswithclientthecostofacquisitionandmaintenanceof 1 PATS Study the old system before 10/01 and obtain documentation 4 about it 5 4 Weekxx_PR_S02b_Txx.xls Problem & Issue Report as of 10/13/2004 * See QMP or Below for Definitions Type Issues Defects Problem Reports New Opened New Closed Old Closed 10 10 8 0 0 0 0 0 1 Current 0 0 0 Definitions Issues Defects Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also us ...
|
|
Week01_PR_F04a_T1
USC, CSCI 577
Excerpt: ... decide whether we should build new system based on existing one or we build new one from scratch. Study reports carefully to design them in simple ways that reports can be shown on HTML format. Find and evaluate free component in early stage. Weeks Active 1 2 2 Tight schedule 1 3 4 3 4 Current system complexity Complex report module 1 1 Weekxx_PR_S02b_Txx.xls Problem & Issue Report as of xx/yy/zzzz * See QMP or Below for Definitions Type Issues Defects Problem Reports New Opened New Closed Old Closed 0 0 0 0 0 0 0 0 0 Current 0 0 0 Definitions Issues Defects Problem Reports Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Un In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Weekxx_PR_S02b_Txx.xls e "Author" has no control over ( Unavoid ...
|
|
Week05_PR_F07a_T01
USC, CSCI 577
Excerpt: ... ng COTS Glue Code development Test Deployment Total Injected 5 4 1 3 6 Removed 5 4 1 2 6 18 18 Problem Reports as of mm/dd/yyyy: * See QMP or Below for Definitions Type Issues Defects Problem Reports Definitions Issues Defects Problem Reports 10/17/2007 New Closed Old Closed Current New Opened Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Forms to collect that information. In that case, this will be the total number of Concerns provided by the reviewers. Concers can be an issue, a defect or neither (consider that reviewers might indicate false defects). Problem Description: List any problems team is experiencing. This includes things that ...
|
|
Week11_PR_F07a_T01
USC, CSCI 577
Excerpt: ... xx_PR_S02b_Txx.xls Top Project Risks as of 11/28/2007 This Week Last Week 1 1 Risk Description Commitment of Development Team Risk Mitigation Action Items Establish clear requirements and scope of hte project Weeks Active 2 2 Traning and Mentoring at client side post Project Get Opinion of an domain expert or case study Do interoperability analysis for the probable COTS Components Some extra time after the ARB will be given as mentioned by Prof. Brown and the development team will try to enhance the present MS Access based system with as many functionalities they can 3 4 4 0 Secure Donor data in database Schedule overrun for development Weekxx_PR_S02b_Txx.xls # of Defects Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code development Test Deployment Total Injected 3 0 0 3 0 3 Removed 3 0 0 3 0 3 9 9 Problem Reports as of mm/dd/yyyy: * See QMP or Below for Definitions Type Issues Defects Problem ...
|
|
Week10_PR_F07a_T01
USC, CSCI 577
Excerpt: ... eting notes b. c. d. Weekxx_PR_S02b_Txx.xls Top Project Risks as of 11/21/2007 This Week Last Week 1 1 Risk Description Commitment of Development Team Risk Mitigation Action Items Establish clear requirements and scope of hte project Weeks Active 2 2 Traning and Mentoring at client side post Project Get Opinion of an domain expert or case study 3 4 3 5 Absense of Domain Expert Secure Donor data in database Use COTS Do interoperability analysis for the probable COTS Components Weekxx_PR_S02b_Txx.xls # of Defects Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code development Test Deployment Total Injected 2 0 0 3 0 1 Removed 2 0 0 3 0 1 5 5 Problem Reports as of mm/dd/yyyy: * See QMP or Below for Definitions Type Issues Defects Problem Reports Definitions Issues Defects Problem Reports 11/21/2007 New Opened 0 5 New Closed 0 5 Old Closed 0 8 Current 0 5 Issues are problems that the "Author ...
|
|
Week04_PR_F07a_T01
USC, CSCI 577
Excerpt: ... isk Description Unstable and changing requirements Risk Mitigation Action Items Establish clear requirements and scope of hte project Weeks Active 2 5 Absense of Domain Expert Get Opinion of an domain expert or case study 3 4 3 4 Implementation of Security Measures Use COTS Traning and Mentoring at client side post Project Actively Involve primary users in development process 5 6 COTS Interoperability Issues Do interoperability analysis before COTS selection 6 8 Commitment of Development Team Appoint member from client side to present Development team Weekxx_PR_S02b_Txx.xls # of Defects Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code development Test Deployment Total Injected 3 7 Removed 3 7 3 3 Problem Reports as of mm/dd/yyyy: * See QMP or Below for Definitions Type Issues Defects Problem Reports Definitions Issues Defects Problem Reports New Opened New Closed Old Closed Current Issue ...
|
|
Week03_PR_F07a_T01
USC, CSCI 577
Excerpt: ... MP or Below for Definitions Type Issues Defects Problem Reports Definitions Issues Defects Problem Reports New Opened New Closed Old Closed Current Issues are problems that the "Author" can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author" has no control over ( Unavoidable Defect - e.g. change in the requirement). In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You can also use the Review Forms to collect that information. In that case, this will be the total number of Concerns provided by the reviewers. Concers can be an issue, a defect or neither (consider that reviewers might indicate false defects). Problem Description: List any problems team is experiencing. This includes things that have caused delays, rework or any other roadblocks to anticipated progress. No. Problem Description Proposed Solutions Is it COTS Related? (Y/N) 1 The tea ...
|
|
Week12_PR_F07a_T01
USC, CSCI 577
Excerpt: ... as of 12/04/2007 This Week Last Week 1 1 Risk Description Commitment of Development Team Risk Mitigation Action Items Establish clear requirements and scope of hte project Weeks Active 2 2 Traning and Mentoring at client side post Project Get Opinion of an domain expert or case study Do interoperability analysis for the probable COTS Components Some extra time after the ARB will be given as mentioned by Prof. Brown and the development team will try to enhance the present MS Access based system with as many functionalities they can 3 4 3 4 Secure Donor data in database Schedule overrun for development Weekxx_PR_S02b_Txx.xls # of Defects Project Mgmt. Requirements COTS Assessment Design Life Cycle Planning Configuration Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code development Test Deployment Total Injected 4 0 0 2 0 3 Removed 4 0 0 2 0 3 9 9 Problem Reports as of mm/dd/yyyy: * See QMP or Below for Definitions Type Issues Defects Problem Reports Definitions Issues Defects Pro ...
|