The document compares prescriptive and agile software engineering approaches. Prescriptive approaches describe how software should be developed through defined processes and guidelines. They aim to facilitate planning, improve quality and control. However, they can be rigid and inappropriate for environments where requirements change rapidly. Agile approaches emphasize adaptability, speed, and informal processes suited for unpredictable environments. While prescriptive models strive for structure and control, agile prioritizes vales like communication and feedback to enable flexibility. The choice of approach depends on factors like requirement volatility and need for structure versus flexibility.

1. Muhammad MuzammilFederal Urdu UniversityIslamabad.pakmuzammil@gmail.comPrescriptiveVSAgileSoftware Engineering 1

2. Federal Urdu University, Islamabad.A set of interrelated activities which transforms input to outputs.A process is composed of activities. Software Process Models.

3. PrescriptiveAgileApproaches For Process modelsFederal Urdu University, Islamabad.

4. A model that describes how to do Provide Direction Follow some Laws or rules Use guidelines or framework to organize StructureAnd in what orderHow Software should be developedPrescriptiveFederal Urdu University, Islamabad.

5. Guiding Receives indirect support Developer and managers receives support through information Which help in project.Enforcing Receives direct support Mechanically interpreted by process enginesAim of Prescriptive ModelsFederal Urdu University, Islamabad.

6. Technology keeps changing

7. Technology keeps changingContains quickness, lightness, and ease of movementMentally quickNeed For Agile Approach: It is often difficult (or impossible) to predict as to how a software product will evolve over time Market conditions change, Users needs evolve, Technology keeps changingAgileFederal Urdu University, Islamabad.

8. From people point View: Emphasis on disciplineFrom Developer Point View: Lack of realizationDrawbacks of PrescriptiveFederal Urdu University, Islamabad.

9. prescriptive process has many predefined and ordered activities to be followed during developmentDefined process is suitable for predictable manufacturingAgile method promotes empirical rather than defined processesEmpirical processes are used for high change and unstablePrescriptive VS AgileFederal Urdu University, Islamabad.

10. Agile methods are more Principle-Based Prescriptive methods are Rule-BasedAgile project management is more than a set of practices – it is a mindsetPrinciple Based VS Rule BasedFederal Urdu University, Islamabad.

11. Generic framework for software process encompasses the followingCommunicationplanningmodelingconstructiondeploymentTo Be Prescriptive or Less PrescriptiveFederal Urdu University, Islamabad.

12. If a prescriptive process models strive for structure and other, are they inappropriate for a software (creative) world? If “less structures” models are used for software development will it be possible to coordinate and manage this work?When in doubt, be more prescriptiveTo Be Prescriptive or Less PrescriptiveFederal Urdu University, Islamabad.

13. Prescriptive models:Facilitating planningImproving system qualityImproving controlGuiding project teamsPrescriptive VS Agile Process ModelsFederal Urdu University, Islamabad.

14. Agile models:They are tending to be informal.They are emphasizing on maneurability, adaptability, and speed.They are appropriate for many types of projectsPrescriptive VS Agile Process ModelsFederal Urdu University, Islamabad.

15. Water fallXP,ASDAgileLean Thinking Prescriptive More Value, idea basedDiagram:Federal Urdu University, Islamabad.

16. WaterfallEach waterfall stage is assigned to a separate team to ensure greater project and deadline controlA linear approach means a stage by stage approach for product buildingchanging the software is not only a practical impossibilityExample:Federal Urdu University, Islamabad.

17. It is a low over-head method that emphasizes values and principlesBased on empirical rather than defined methods (Waterfall) Agile methodology means cutting down the big picture into puzzle size bits, fitting them together when the time is rightAgileFederal Urdu University, Islamabad.

18. AgileExtreme Programming (XP) is an excellent example of Agile methodology Communication between customers and other team membersSimple, clean designsFeedback given on Day 1 of software testingEarly delivery and implementation of suggested changesFederal Urdu University, Islamabad.

19. Which Approach to ChooseOnce a stage is completed in the Waterfall method, there is no going back With Agile, changes can be made if necessary without getting the entire program rewrittenAgile method has a launch able product at the end of each tested stage This is not possible for the Waterfall methodFederal Urdu University, Islamabad.

20. Which Approach to ChooseAgile adopt the customer change means customer happy with its new mind set. While in Waterfall model only on final deliverable which mean customer changing mind is not entertaining.At end we can say that waterfall is useful where project have prescribed value, where as agile methodology is use like web development project where changing made rapidlyFederal Urdu University, Islamabad.

21. Thank you Federal Urdu University, Islamabad.