1. Software Development Life Cycles (SDLC) BY Touseef Tahir

2. Process • Project • Software engineering • System engineering SDLC-Software development life cycle

20. Write a report on Extreme programming, formal methods, agile software development life cycles. • Deadline : 12-09-2011 • Email: touseeftahir@ciitlahore.edu.pk • Email subject:? Zero Assignment 1

35. The spiral model

38. A process that • Identifies a risk of business loss • Assesses the risk’s potential impact • Determines how to handle the risk • Protects physical assets from damage • Protects nonphysical assets from software, network-related risks Risk Management

41. Use Prototypes • Evolutionary prototypes • Throw-away prototypes • Phases • Requirements planning • RAD design workshop • Implementation • Why to use RAD • Quick development of software Rapid application development

45. RUP is a method of managing OO Software Development • It can be viewed as a Software Development Framework which is extensible and features: • Iterative Development • Requirements Management • Component-Based Architectural Vision • Visual Modeling of Systems • Quality Management • Change Control Management The Rational Unified Process

46. Online Repository of Process Information and Description in HTML format • Templates for all major artifacts, including: • RequisitePro templates (requirements tracking) • Word Templates for Use Cases • Project Templates for Project Management • Process Manuals describing key processes RUP Features

47. The Phases

48. Recognizes the reality of changing requirements • Casper Jones’s research on 8000 projects • 40% of final requirements arrived after the analysis phase, after development had already begun • Promotes early risk mitigation, by breaking down the system into mini-projects and focusing on the riskier elements first • Allows you to “plan a little, design a little, and code a little” • Encourages all participants, including testers, integrators, and technical writers to be involved earlier on An Iterative Development Process...

49. Allows for software to evolve, not be produced in one huge effort • Allows software to improve, by giving enough time to the evolutionary process itself • Allows interim progress to continue through the stubbing of functionality • Allows for the management of risk, by exposing problems earlier on in the development process An Incremental Development Process...

50. Each iteration is risk-driven • The primary goal of each iteration is to slowly chip away at the risk facing the project, namely: • performance risks • integration risks (different vendors, tools, etc.) • conceptual risks (ferret out analysis and design flaws) Goals and Features of Each Iteration