COMPARISON OF SDLC MODELS ANDBI-DIRECTIONAL TRACEABILITYMATRIXPresented by: Faiza Yousuf
Friday, April 20, 2012WHAT IS SDLC? It is a structure for developing software products and includes processes, methods and tools and is totally dependent on the nature of software product. It is a systematic and disciplined approach which follows a defined sequence of steps and produces required deliverables. Following are the different models used for software development. 2
Friday, April 20, 2012PROBLEM SCENARIOS Example A: We received a Requirement Specification from a client for developing a solution for their specified problem in a domain we have little or no expertise and obviously no experience of developing similar solution. Example B: We received a Requirement Specification from a client for developing a solution for their specified problem in a domain we have expertise and experience of developing similar solutions. 7
Friday, April 20, 2012WATERFALL MODEL IN BOTH SCENARIOSExample AThis model is not suitable for using it in this case because: Client may not know the complete vision of the solution. Because of no expertise and experience on this domain, we wont be able to gather complete requirements in one go and hence the project will get into trouble due to new findings and change in scope.Example BThis model can be used in this case because: If requirements are clear and properly analyzed, this approach is easy an well controlled. Phases are executed and completed at once and will provide the relevant output at the end of each phase. 8
Friday, April 20, 2012SPIRAL MODEL IN BOTH SCENARIOSExample AThis model can be used in this case because: This model has the qualities of prototype model and it works on scope evaluation which is quite useful in this scenario. Risk Analysis is provided throughout the life cycle which will help in terms of implementing new solution and exploring a new domain.Example BThis model can be used in this case because: It can be used in complex and critical projects. Combines strengths of both waterfall and prototype models so it is both easy to control and less rigid in 9 nature.
Friday, April 20, 2012INCREMENTAL MODEL IN BOTH SCENARIOSExample AThis model can be used in this case because: It allows early start for the modules for which requirements have been cleared, without waiting for requirements of the whole project. It allows parallel development with multiple teams and with one team working on the first module, second team can buy sometime for the R&D on an unclear set of requirements as the increments comes by sequence.Example BThis model can be used in this case because: Due to previous experience and expertise, proper modules can be form with teams working parallel on different increments (modules), which will eventually decrease projects timeline. After every increment, the projects big picture becomes more 10 visible.
Friday, April 20, 2012V- MODEL IN BOTH SCENARIOSExample AThis model is not suitable for using it in this case because: It is almost similar to the waterfall except of the added test phases at each level, so requirement gathering will be an issue here. No working prototype will be available because there isnt any incremental/modular/iterative approach.Example BThis model can be used in this case because: We would know the most scope of the project and can use this rigid approach to deliver the solution. Test planning and execution is emphasized in early project phases. 11
Friday, April 20, 2012CONCLUSION The above discussion clearly shows the scenarios in which different models may or may not benefit the solutions stakeholders. Ideally, the vision for the solution must be clear before initializing the project but in most of the cases, client doesnt know his own requirements properly and thus relies on IT consultants abilities of shaping up understandable and concrete requirements. 12
Friday, April 20, 2012BI-DIRECTIONAL TRACEABILITY MATRIX 14
EXAMPLE OF BI-DIRECTIONAL TRACEABILITY Friday, April 20, 2012 MATRIXRequirements Source Requirement Design Element Code Function Test CaseBusiness Rule # 1: User User Registration Use Cases/ Process 1. Is_user 1. User should be able to registercan register itself on the and Login Module Flow Diagrams for 2. Is_newuser itself on the website.Website and login itself. User Registration 2. Email address should be and Login unique. 3. User should be able to login after providing correct credentials.Business Rule # 2: User Online Buying Use Cases/Flow 1. Product_Stock 1. Ensure before checking outcan buy different Module Diagrams for 2. Product_Price that the product is in stock.products online. Online Buying 3. Product_Delivery 2. Checkout the product, add in Module cart and provide delivery information. 3. Pay dues online by different payment gateways. 4. Product record is updated automatically 15