V model in SDLC

8,766 views
8,399 views

Published on

Published in: Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
8,766
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
295
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

V model in SDLC

  1. 1. Edited By Jasour A.Obeidat Supervisor Dr.Hebah Nassir DeainInformation System Development – 1st Semester 2012-2013
  2. 2. Outline• “V” Model in Progress.• “V” Model illustration.• “V” Model Advantages.• “V” Model Disadvantages.• Comparison between “Waterfall” Vs. “V” Models.• Examples (Problem Scenario). Information System Development – 1st Semester 2012-2013
  3. 3. Outline• System Development Life Cycle SDLC.• “V” Model illustration.• “V” Model Advantages.• “V” Model Disadvantages.• Comparison between “Waterfall” Vs. “V” Models.• Examples (Problem Scenario). Information System Development – 1st Semester 2012-2013
  4. 4. Outline• System Development Life Cycle SDLC.• “V” Model in Progress.• “V” Model Advantages.• “V” Model Disadvantages.• Comparison between “Waterfall” Vs. “V” Models.• Examples (Problem Scenario). Information System Development – 1st Semester 2012-2013
  5. 5. Outline• System Development Life Cycle SDLC.• “V” Model in Progress.• “V” Model illustration.• “V” Model Disadvantages.• Comparison between “Waterfall” Vs. “V” Models.• Examples (Problem Scenario). Information System Development – 1st Semester 2012-2013
  6. 6. Outline• System Development Life Cycle SDLC.• “V” Model in Progress.• “V” Model illustration.• “V” Model Advantages.• Comparison between “Waterfall” Vs. “V” Models.• Examples (Problem Scenario). Information System Development – 1st Semester 2012-2013
  7. 7. Outline• System Development Life Cycle SDLC.• “V” Model in Progress.• “V” Model illustration.• “V” Model Advantages.• “V” Model Disadvantages.• Examples (Problem Scenario). Information System Development – 1st Semester 2012-2013
  8. 8. Outline• System Development Life Cycle SDLC.• “V” Model in Progress.• “V” Model illustration.• “V” Model Advantages.• “V” Model Disadvantages.• Comparison between “Waterfall” Vs. “V” Models. Information System Development – 1st Semester 2012-2013
  9. 9. System Development Life Cycle SDLC• System development process: Is a structure imposed on the development of a system product.• There are several models represent system product in it’s processes: - Waterfall Model - V shaped Model - EXTREM Programming - …etc. Information System Development – 1st Semester 2012-2013
  10. 10. “V” Model Illustration Information System Development – 1st Semester 2012-2013
  11. 11. “V” Model in Progress “Procedures”• The “V” Model begin with elicitation of system requirements in order to conceptualize the system.• Once the system concept is formed, requirements are further elicited, in order to specify detailed system requirements.Note: These system requirement are then allocated to system components. (e.g. H/W, S/W, firm works, and people) Information System Development – 1st Semester 2012-2013
  12. 12. “V” Model in Progress “Procedures”• The system is designed.• Once the system is designed the detailed software requirements are elicited.• Note : These software requirements are then used to design, construct, and test appropriate component of the system . Information System Development – 1st Semester 2012-2013
  13. 13. “V” Model in Progress “Procedures”• Eventually, all of the system components are integrated and tested when Evidence Exist? - That the resulting system meets requirements. - The system and its components are accepted. Information System Development – 1st Semester 2012-2013
  14. 14. “V” Model in Progress “Procedures”• The “V” Model integrates planning and execution of testing throughout the life cycle. During requirements elicitation and analysis Acceptance test planning Initiated -Executed prior to developing the system During design activities System Integration test planning -Executed after S/W coded Initiated and TESTED Information System Development – 1st Semester 2012-2013
  15. 15. “V” Model Advantages• Simple and easy to use.• Specific goals are defined for each phase.• Focus on preparing test plans early in the process which give it higher chance to success.• The user of the “V” Model participate in the development and maintenance. Information System Development – 1st Semester 2012-2013
  16. 16. “V” Model Advantages• The “V” Model provide a concrete assistance on how to implement an activity.• In each activity schema there are instructions, recommendations, and detailed explanation of the activity.• Appropriate for small development project in which requirements are well understood. Information System Development – 1st Semester 2012-2013
  17. 17. “V” Model disadvantages• Difficult to add or change requirements later in the development process.• “V” Model is inappropriate for complex projects.• The emphasize in test planning appears to reduce the risk but like the “Waterfall” model the “V” model risks in : - Time. - absence of careful planning. Information System Development – 1st Semester 2012-2013
  18. 18. Waterfall Model Vs. V Shaped ModelModel / Feature Waterfall Model “V” ModelRequirement Beginning BeginningSpecificationsCost Low ExpensiveGuarantee of success Low HighSimplicity Simple IntermediateFlexibility Rigid Little flexibleReusability Limited To some extentUser involvement Only at the beginning At beginningChange incorporated Difficult Difficult Information System Development – 1st Semester 2012-2013
  19. 19. Problem Scenarios• Example A:We received a requirement specification from aclient for developing a solution for their specifiedproblem in a domain we have little or no expertiseand obviously no experience of developing similarsolution. Information System Development – 1st Semester 2012-2013
  20. 20. Problem Scenarios• Example A: In “Waterfall Model”This Model is not suitable for using it in this case.Because :-Clients may not know the complete vision of the solution .- No expertise and experience on this domain which reflectthat we can’t gather complete requirements, and that leadsfor troubles due new findings. Information System Development – 1st Semester 2012-2013
  21. 21. Problem Scenarios• Example A: In “V” ModelThis is not suitable for using it in this case because: -It is similar to “Waterfall” model except of the added test phases at each level, so gathering will be an issue here too. -No working prototype will be available because there is not any incremental/ modular/ iterative approach. Information System Development – 1st Semester 2012-2013
  22. 22. ??? Information System Development – 1st Semester 2012-2013
  23. 23. Problem Scenarios• This is my Question???????We received a requirement specification from aclient for developing a solution for their specifiedproblem in domain. We have expertise andexperience of developing similar solutions Information System Development – 1st Semester 2012-2013
  24. 24. The End ! Information System Development – 1st Semester 2012-2013

×