Assignment # 01 Web Engineering – Spring 2022 Submitted by: Muhammad Zohaib Registration No: 18PWCSE1689 Class Section: B “On my honor, as student of University of Engineering and Technology, I have neither given nor received unauthorized assistance on this academic work.” Student Signature: ______________ Submitted to: Engr. Madiha Mushtaq 9 April 2022 Department of Computer Systems Engineering University of Engineering and Technology, Peshawar Describe which Process Model is best suited for Web-based System/Application development (keeping in view the requirements for a web application development process)? Note: Provide an example other than the Rational Unified Process (RUP). Introduction: The Agile methodology is so popular that some organizations are even using it for non-software-related projects. Agile is based on an incremental and iterative approach. Fast failure is a notable aspect of it, and Agile features ongoing release cycles. Each of these features small changes over the previous release, with the product tested with each iteration. A Scrum is a form of implementation of the Agile methodology that helps development teams structure complex project requirements. To complete assigned tasks, Scrum teams work in sprints, which is a period that lasts between 2 to 4 weeks. Daily Scrum meetings are organized to help the complete team monitor progress made up until that point. The one in charge of the Scrum team is known as the ScrumMaster. As usual, it’s their responsibility to keep the team on track for meeting the goal. Use cases: Practically any startup initiatives, when end users’ early feedback is required. Large projects that are easy to divide into small functional parts and can be developed incrementally over each iteration. Most of mid-sized projects in custom software development where business requirements cannot be confidently translated to detailed software requirements. Agile Pros: Capable of accommodating new changes or enhancements occurring during the development phase without a budget constraint. Fast development and testing allow for the recognition of existing gaps in the requirements or technologies being used. This makes easy to find alternative courses of action. Saves a great amount of cost and time thanks to the less documentation Engages projects managers and business stakeholders and gets their feedback consistently throughout the software development process Helps development teams identify and address minor issues before becoming problematic Agile Cons: Almost impossible to determine the total effort required at the very beginning of development for full-size and complex projects. Puts less emphasis on designing and documentation processes. High-risk when clients/end-users are unsure about requirements. Requires valuable resources. ------------------------------------------------------------------------------------------------