1 / 15

planning design phase implementation phase

8 September 2010. planning design phase implementation phase. SCHEDULING. Scheduling . Put together minimal solution Start with external commitments Introduce internal milestones Focus on the risks Add next level of features where possible. Identify components Identify dependencies

king
Download Presentation

planning design phase implementation phase

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 8 September 2010 planning design phase implementation phase

  2. SCHEDULING

  3. Scheduling • Put together minimal solution • Start with external commitments • Introduce internal milestones • Focus on the risks • Add next level of features where possible • Identify components • Identify dependencies • Estimate (guess) • Prefer educated guess • Lay out assignments and time frames Process Within the Steps

  4. Use simple Excel spreadsheet (or equivalent) Project Plan for this project

  5. Questions project plan answers • What is Joe working on this week? • Who can help me if I run into trouble? • If I have to choose an activity to be late, which one will impact the project more?

  6. What needs to be in the plan? • All Deliverables • Code • Design • Test • Documentation • Learning • Presentation and demo prep • Reviews

  7. Reviews and Inspections • Why? • Developer can’t correct unseen errors • More eyes to catch problems • Earlier is cheaper • Integration fix typically 3-10 times the cost at design • Difference in terms • Review implies completed work, often reviewed by someone at a different level • Inspection implies peer review of work in progress

  8. Should we eliminate risk? Patton: Take calculated risks. That is quite different from being rash. Nehru: The policy of being too cautious is the greatest risk of all. Herodotus: Great deeds are usually wrought at great risks. The Net: No risk => no challenge

  9. Risks • “80% of software projects fail” • Standish Report (1995) • 16.2% completed on-time and on-budget with all features and functions as initially specified. • 52.7% completed and operational but over-budget, over the time estimate, and offers fewer features and functions than originally specified. • 31.1% cancelled at some point during the development cycle. • Sauer et al (2007) claim 67% “delivered close to budget, schedule, and scope expectations” with experienced project managers • Two types of risk • Avoidable • Unavoidable

  10. DESIGN: ARCHITECTURE

  11. Software Architecture • What is an architecture? • External view • What does that mean for software? • The highest level design • Often treated as top level of system design • not consistent

  12. Your Architecture • First level diagram How the components fit together • Later will study well-known architectures • Examples from last year…

  13. Virtual Reality for Stroke Patients

  14. Configs (Many) Templates (Few) Processor SAS Files Command Line Client GUI Client Interpreter Velocity Library Social Welfare Web Site

  15. Wireless Deployment

More Related