QR ATTENDANCE MOBILE APPLICATION
SECTION NO# 01
ASSIGNMENT NO# 05
ALEENA AAMIR | BSE171028 |
IZZA NOOR | BSE171034 |
NAWAL FATIMA | BSE171016 |
NAWAZISH TARIQ | BSE153088 |
Dec 30, 2019
SUBMITTED TO: SIR IBRAR ARSHAD
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Agile software development, Exercises of Software Engineering
Project agile development,,,,,,
Typology: Exercises
2018/2019
1 / 5
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Agile software development and more Exercises Software Engineering in PDF only on Docsity!
QR ATTENDANCE MOBILE APPLICATION
SECTION NO# 01
ASSIGNMENT NO# 05
ALEENA AAMIR | BSE171028 |
IZZA NOOR | BSE171034 |
NAWAL FATIMA | BSE171016 |
NAWAZISH TARIQ | BSE153088 |
Dec 30, 2019
SUBMITTED TO: SIR IBRAR ARSHAD
COMPARISON OF ALL THE AGILE PROCESS IN AGILE SOFTWARE DEVELOPMENT COURSE
Introduction:
In this report we will be discussing about all the agile processes that were discussed in this course and will compare each of the process with another and will determine their advantages and their pros and cons.
1. Waterfall Model:
Waterfall is heavyweight process. Waterfall model is a life cycle of software development in which we have five stages, including specifications, design, implementation, testing, and maintenance
Project Type:
Waterfall is a traditional model and the projects made using waterfall model are very complex and bigger and all the requirements must be known upfront.
Time:
Time required to build a project in waterfall model is usually long because of the complexity of product and to make sure that the product that is made is secure or we can say the products that are made using this model are sometimes very critical and each and everything should be close to perfect or all the effort will be lost.
Team:
Team members that make a product using waterfall model are usually large in number because of the complexity of the product and only those people work on these projects which have vast experience in the field of software development and are experts in the field or we can say have some good skill set.
Requirements:
Requirements in traditional model must be known upfront and must be clear before the start of working on a project. Importance of having requirements known is because in the traditional model products are very complex and critical and the development team and owner cannot afford any miscalculation in the product which will result in a disaster.
Constraints:
Waterfall is easy to understand and use and is used when quality is important. Requirements are stable in waterfall model and it is good for management control. It is used when we must make a new version of an existing product.
Software Prototyping Model:
Software Prototyping model is a heavyweight process. In this type of model, the developing teams build prototype for a product and this protype is evaluated by end users and the user sends a feedback if he likes it or finds a flaw in it.
Requirements:
Requirements are known in the Scrum from the start when the product owner takes part in the sprint planning meeting and the development team makes a product backlog of it.
Constraints:
In this process the product owners are also part of the team and the team members along with scrum master decide what to build and how to build in each meeting that is held during sprint planning meeting phase.
3. Extreme Programming:
Extreme Programming is a software development methodology in which we include software quality and its responsiveness so that it can change customers’ requirements.
Project Type:
In this process we don’t make a new project but instead we improve its quality and the way it performs some tasks and make sure that it responds to the tasks which are given to the software.
Time:
As we said above that we don’t make a new software instead we take some steps to improve its quality and the time it takes will vary according to the size of project that is being improved.
Team:
The team that performs these quality tasks is not that bigger because there is no need of having a bigger teams as these processes are involved in lightweight processes and teams are usually small in these projects which are made using lightweight process but we will say again that the team size may vary from project to project.
Constraints:
XP is all about testing and basically in this process the customers sit with the XP team when the team is developing the software, and this will reduce the risk of any fault occurring in the project.
Requirements:
Requirements in Extreme Programming are known from the start because it is used in large scale project and those projects have their requirements clear from start.
4. Feature driven development:
It is a agile software development process it uses short iteration model the basic purpose of its creation was to easily scale larger projects and larger teams.
Project Type:
In feature driven development bigger projects are covered the reason for this is because this process was developed to make sure that larger teams should be made in agile and it should cover complex projects.
Time:
In feature driven development work is done in the form of features of a project and each feature takes about one to four weeks to get complete but again the whole project may be completed according to the complexity of project.
Team:
In feature driven development team size is slightly bigger than other agile processes and it includes Project manager, Chief Architect, Development Manager, Domain Experts, Class Owners and Team Chief Programmers, making a slightly larger team capable of developing a software product.
Requirements:
In FDD requirements are considered as features and are known upfront and each requirement is focused individually and processed with importance that it may impact the whole systems functionality.
Constraints:
Feature driven development supports multiple teams that are working in parallel for the project all the aspects of a project are covered in this process this process is better for those teams in which experience varies from one member to another.
5. Kanban:
Kanban is not a software development process instead it’s an approach to change management for a project. It is alternative approach for agile development.
Project Type:
As we said above it is not used to develop a project but instead it’s an approach to change management for a project being developed but the projects that it works on or is being applied on those projects in which change is not that threating and is affordable.
Time:
Kanban reduces the time and costs for a project and has a feature of providing agility and adjusts accordingly when changes occur in a project. Kanban reduces the cycle of each process in a project and more work is done in less time.
Team:
The size of team in Kanban is mediocre and does not need a large team for applying the methodology of management in a project.
Requirements:
There are no requirements for a Kanban process as it’s an approach but for the projects that are being developed and Kanban is applied on have requirements clear and because of this reason change management process is applied on Kanban.