Pm 3 approach

230 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
230
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Pm 3 approach

  1. 1. Project Mgmt. Project Approach
  2. 2. Project Approach • Choosing Technology – Stand alone / Distributed Apps. – Usage of Web technologies – Response Time – .NET / Java / Mobile /Open Source – Usage of tools – Size of data – Information Security Req. – Interfaces with outside (XML)http://www.radiantminds.co.in
  3. 3. Project Approach • Process Models – Waterfall Model – V-Process Model – Spiral Model – Component based development – S/w prototyping – Incremental Delivery – Agile S/w Development – Global Delivery Modelhttp://www.radiantminds.co.in
  4. 4. Process Models • Waterfall Model – When requirements are well defined – Sequence of activities – No scope for iteration • Disadvantages – Project span (timelines) – No end client interaction – Business need change – Dependency on earlier stagehttp://www.radiantminds.co.in
  5. 5. • Feasibility Study • User Requirements1 • Analysis • System Design(High / Low)2 • Coding • Testing / Documentation3 • Installation
  6. 6. Process Models • V Process model – An elaboration of waterfall model – More stress is given on testing – Activity goes in parallel – Testing and development team works as independent units • Disadvantages – Iterations are not possible – Communication is criticalhttp://www.radiantminds.co.in
  7. 7. Process Models • Spiral Model – Iterative in nature – Scope for correction at each stage – More client friendly – Results can be seen in-between • Disadvantages – Proper planning is required – Management skills are must – Timely communication is the keyhttp://www.radiantminds.co.in
  8. 8. Process Models • Prototyping – When requirements are evolving – More user involvement – Can get feel of the apps. – Corrections can be done easily – Prototype sign-off is possible – Testing and Dev team gets clear idea – Helps in lower level design – 35% changes are cosmetic in naturehttp://www.radiantminds.co.in
  9. 9. Process Models • Incremental Delivery – Followed by Microsoft (Versioning) – Feedback from early versions is incorporated in new version – Smaller sub projects are easier to control – Releases & Patches ? – Version controlling and Release management is the keyhttp://www.radiantminds.co.in
  10. 10. Process Models • Agile S/w Development – Very good for small projects – High user involvement – Results can be seen almost every day – Immediate feedback from the user – Application gets well tested about the functionality – High level of communication happenshttp://www.radiantminds.co.in

×