Download
1 / 28
280 likes | 392 Views
End of Semester Presentation. Common Test Case Project. Agenda. Introduction Project Plan Common Test Case Identification – Updates Test Case Comparison System – Updates Risks Reflections Plan for the Fall Semester. Introduction. Team Members Dilip Narayanan Gaurav Jalan
E N D
End of Semester Presentation Common Test Case Project
Agenda • Introduction • Project Plan • Common Test Case Identification – Updates • Test Case Comparison System – Updates • Risks • Reflections • Plan for the Fall Semester
Introduction • Team Members • Dilip Narayanan • Gaurav Jalan • Nithya Janarthanan • Client • Jason Weighley, Rail Control Systems, Bombardier Transportation • Mentors • Eduardo Miranda, Associate Teaching Professor, ISR • Vijay Sai, Software Engineering Institute • External Consultants • Prof. Anthony Tomasic • Frederick Pfisterer
The Problem FAT Testing Division V&V Testing Division I see that there are a lot of test cases common to FAT and V&V . If only I can identify the common test cases !!! FAT Test Document V&V Test Case Document
I don’t have to write a new test case FAT Match Found This is reducing 20-30% of my costs Are there any test case that are similar to the one I am going to write now ? Match not Found I have to write a new test case V&V
Project Overview • Customer Goals: To help Bombardier testing division to identify at least 20% of the common test cases between their test groups • Academic Goals: To formalize the BT Testing domain and organize information in a more searchable and retrievable manner
Project Plan • Dilip – can u update the visio dig u made last time to reflect the latest milestone plan? • milestone plan and/or milestones along timeline (like the one nithya made for last mentor meeting) • Nithya – can u put ur timeline plan taking into accnt the updated macro plan? • say why 2 tracks • - Why no usual software processes not applicable to our project?
Why two plans?? • Customer Track • Identify common test cases between the two testing groups before October • Suspects a commonality of at least 20% • Solves the problem at hand. But not repeatable • Academic Track • Provide a repeatable solution for comparing the test cases between the two testing groups. • We should identify the common test cases by manual comparison to acquire domain knowledge. But we can stop identifying once we are comfortable with the domain.
Status – CTCI (assigned to G) • Graphs from mentor meeting (no need for individual test cases per week graph – cumulative shud suffice) • - by products of ctci (ask eduardo how to say this in mppcuz things like no tcs for VA and VA integral mode in VNV are pretty serious) • - domain learning (??) • - or we cud elaborate what we have done toward each milestone
Test Case Comparison System - Updates • Technical Research – Identification of suitable approaches • Literature Review • Mentor Meetings • Meetings with Subject Matter Experts • Areas of Research • Natural Language Processing • Text Processing Systems • Vector space models • Ontology • Hybrid Approach
Context Based Approach Evaluation • Identify the approach Usage Context and Evaluation goals • Plan the Evaluation • Form Evaluation Team • Identify stakeholders • Select an approach • Estimate effort and Schedule • Develop Model Problem • Develop hypothesis • Develop criteria • Design model solution • Implement and evaluate solution against criteria • Analyze the results against approach Usage context
Technology is a good fit Technology is not a good fit
Plan for the Fall Semester • Completion of Common test case Identification • Verification and validation of the selected approach to provide the solution for identifying common test cases
Meeting process • Agenda • All agenda items are time-boxed • Buffer time = 15% of total duration • Ideas list • To do list • Notes/decisions/etc. • Scribe uses a shared Google doc and projects it
Reflections • Customer Communication • Lack of Clarity of project Scope • Roles and Responsibilities • Lack of a proper Process for each activity • Ineffective Meetings • Lack of a plan • Activity based planning
Lessons Learnt • Deadlines for the tasks • Sending across a deliverable on its deadline irrespective of the status of completion • Well- defined roles and responsibilities is important • Importance of having a Macro Plan
Questions for the mentors, etc. • Do we have anything for mentors?
How we are tracking • G thinks that this slide can be removed. Or if not, at least put it up in bkup slides. • - for ctcii think v dont need to say how v track cuz its too trivial • - v can say something on how we are tracking tccs
Processes (we shud delete this) • D and G agreed to remove this slide. Need N’s opinion. • brief and generic overview of some of our processes – I don’t think this is reqd as we don’t really have any other processes except for CTCI and for Meetings • CTCI process we shud put in the bkup slides.
CTCI Process • I’m not sure if this is reqd even for bkup • Explain manual comparision diagrammatically, trying to de-emphasize the manual aspect of this process
