Post on 14-Jan-2016
Honours Project Proposal
Service Oriented Architecture for Software Traceability System
Fadzai Muvuti & Ntheye Lungu
Overview
o Traceability• Importance• Problems
o Current Approach
o Our Approach
o Goals/Aims
o System Overview
o Expected Outcomes
o Project time line
o Contributions
o Summary
Traceability
““Requirements traceability refers to the ability Requirements traceability refers to the ability to describe and follow the life of a requirement , to describe and follow the life of a requirement , in both a forwards and backwards direction.”in both a forwards and backwards direction.”
[Gotel and Finkelstein, 1994][Gotel and Finkelstein, 1994]
““An SRS is traceable if the origin of each of its An SRS is traceable if the origin of each of its requirements is clear and if it facilitates the requirements is clear and if it facilitates the referencing of each requirement in future referencing of each requirement in future
development or enhancement documentation.”development or enhancement documentation.”
[IEEE Standard 830-1998][IEEE Standard 830-1998]
Importance of Traceability““You can’t manage what you can’t trace.” You can’t manage what you can’t trace.”
[Watkins and Neal, 1994][Watkins and Neal, 1994]
o Often mandated by standards or contractso Benefits listed in literature include:
• Improved software quality• Impact analysis and change control• Monitoring the process• Verification• Prevention of knowledge loss
Problemso Various stakeholders require/produce
different information (requirements/artifacts)
o Huge amount of information must be tracked and maintained
o Time-consuming and expensive to capture relationships manually
o Specialized tools must be used
o Heterogeneous artifacts
Current Approach
• Current tools– Doors – [Telelogic]– RequistePro – [IBM]
• Solutions still under research– Machine learning – [City University, London]– TraceM – [University of Colorado]– XML Conversion based tool – [City University,
London]
Our Approach
o Our focus is developing a Traceability solution using Web services technologies.
Why web services““Machine to machine interaction.” Machine to machine interaction.”
[W3C][W3C]
o Benefits:• Built on Industry standards• Allows software to interoperate across
programming languages, platforms and Operating Systems
• Structured way to format data• Standard means to describe what the service
does and make the service available to others
Project Goals/Aims
o Ubiquitous traceability solution, with the following features:• Published as a Web Service • Support for SRS from multiple source types• Provide impact analysis on requirements change. • Project-grading functionality based on pre-defined
metrics. • Searchable archive of academic and industry-
related papers and publications.
LIS
TE
NE
R
Project Setup/
Configure
Documentarchive
ProjectGrading System
TraceImpact
Analysis
RequisiteProDocumentconverter
Service Registry
Service Requestor
Service Provider
Service Oriented Architecture
[publish]WSDL;UDDI
[bind]
[find]WSDL;UDDI
Network
PC/Mac/Unix
web services
method calls
conforms to
soap messages
HTTPHTTP
SOAPSOAP
UDDIUDDI
WSDLWSDL
based on
Protocol stack
Integration server
Conceptual System
Expected Outcomes
o Document Converter - Ntheye
o Project Creation/Configuration - Ntheye
o Requisite Pro - Fadzai
o Academic Reference Lookup - Fadzai
o Project Grading System - Ntheye
o Impact Analysis - Fadzai
Step 0Allocated ProjectStep 0Allocated Project
Step 9Evaluation of SystemStep 9Evaluation of System
PreStudy Elaboration Development Refinement
>Approval of project Spec.
Step 13Supervisor:
Demonstrate Project
Step 13Supervisor:
Demonstrate Project
Conclusion21/05 05/08
Step 1Analysis & ResearchStep 1Analysis & Research
Step 2Project definitionStep 2Project definition
Step 3Evaluation of
Expectations
Step 3Evaluation of
Expectations
Step 4Project ProposalStep 4Project Proposal
Step 5Project
Presentation
Step 5Project
Presentation
16/08
Step 8Implementation &
Deployment of beta version
Step 8Implementation &
Deployment of beta version
Step 6Report: Definition & TheoryStep 6Report: Definition & Theory
Step 7Report: DesignStep 7Report: Design
Step 10Final Implementation &
Testing
Step 10Final Implementation &
Testing
Step 11Report: Outline and Final
Draft
Step 11Report: Outline and Final
Draft
Step 12Report & Poster - Hand inStep 12Report & Poster - Hand in
25/09 15/10
Step 14Final Project
Demonstration
Step 14Final Project
Demonstration
12/11
>Beta Version Running
>Final Submission
Report Write up.Report Write up.
>ProjectProposal
Project time line
Contributions
o We will implement a portable, re-usable requirements traceability solution using web services.
o Contribute to research on the portability of Traceability solutions using web services technologies.
Summary
o Traceability• Importance• Problems
o Current Approach
o Our Approach
o Web services
o Goals/Aims
o System Overview
o Expected Outcomes
o Project time line
o Contributions
o Summary
Questions?
Additional Material
Dynamicanalyser
Programbeing tested
Testresults
Testpredictions
Filecomparator
Executionreport
Simulator
Sourcecode
Testmanager Test data Oracle
Test datagenerator
Specification
Reportgenerator
Test resultsreport
oOracle “grading tool”