In the past few years, theres been a blossoming of a new style of software methodology, the name is agile methods. Agile methods is under the idea of guaranteed to software development have efficiently output of reduce the activities and products so far as possible along the way of developing. . Most software development is a chaotic activity, often seen as a the phrase "code and fix". Agile methods make the fussy process become easy so that increasingly more enterprise and folks opt for agile methods. In semester 2, we researched the knowledge about DSDM, XP, SSADM, RUP, ETHICS, CCMI. In this article I explore the reasons for agile methods and I am going to focus on evaluating the strengths and weaknesses of DSDM and XP. Because they are the mainstream agile methods lately and respectively present their process, characteristics, applicability and some other aspects about this two methods.
2. Definition
Dynamic Systems Development Method (DSDM) was developed by a UK consortium in the united kingdom in the mid-1990s. This view has been reinforced in the work of Jennifer Stapleton(1997). It really is a practitioner-based strategy and this consortium are involved in Rapid Software Development (RAD) development of software systems. DSDM developing very fast, English Xansa company released that DSDM and traditional development methods followed in productivity assessment from 1994 to 2001. Bottom line is after used DSDMthe output improved 202 %. This view has been supported in the work of Alistair Cockblum (2003). It explains all aspects in rapid development business centered environment.
XP(Extreme Development) is dependant on the development connection with a single writer and is aimed at developers, so it is a practitioner-based method. The first Extreme Programming project was started out March 6, 1996. Extreme Encoding is one of several popular Agile functions. It has already been shown to be very successful at many companies of all different sizes and industries worldwide. Don Wells, 1999
3. Advantages of DSDM
In the objectives aspect. In the eight guidelines of DSDM, we will get 'deliver on time ', DSDM assumes that 80 % of the answer can be developed in 20 % of the time that it would try produce the total solution to be able to shorten development times, at exactly the same time to provide that will have the biggest business profit first. Stapleton (1997, pp. 13) claims that ' a means of developing software systems that truly provide the needs of business '. Which means first advantages of DSDM is use time as shorten as is feasible and it will make the largest business gain first.
It is approximately truly understanding the needs of the business and delivering solutions that work - and delivering them as quickly so that cheaply as you possibly can(Stapleton, 1997, pp14), Therefore, we can find use DSDM not only fast, but cheap.
Staleton (1997, pp. 65) expresses that ' DSDM is more than anything about improving marketing communications between all functions mixed up in development of a system '. Developers can make more communications with who'll work with the system and the system must be maintainable after delivery. The other strength is it helps customers learn about the merchandise, and after delivery, programmers will maintenance the merchandise.
In the domain and concentrate on aspects. The advantages of DSDM are most easily applied in system, and it can be used in large task.
For techniques. Staleton (1997, pp. 14) states that ' DSDM details project management, estimate, prototype build, time box method, configuration management, evaluating, quality assurance, assignments and obligations (of both users and IT staff), team structure, tools surroundings, risk management, building for maintainability, the relationship between suppliers and purchasers'. DSDM use timeboxing, so end-user of DSDM can save time and money by becoming members of the Consortium. It could protect delivery remains being the focus and support the key project to realize the development promptly and make out with the good quality. It attentiveness is at the top priorities and everyone who connect about the job know how long to anticipate each other to take. MoSCow is one of the power in DSDM. It's rules is utilized for prioritising requirements. It really is an acronym that means must have, must have, can have, want, but won't have this time around. This order is vital, because they're sorting with the necessary degree. It can benefit you save enough time when you do assembling your project and easy to find what you ought to do within the deadline. Another strength is evolutionary prototyping, it used heavily in DSDM that is managed using documented analysis and it helps developers to communicate with people. In its conditions, users can operate the system more skilled. Workshop is another power of DSDM, it can make the different people who use the system to mutually and discuss what they would like to do about the machine. So that it can make decisions about the system quickly and accurately.
In scope aspect. The advantages of DSDM will be the development process is very exact. A given listing does have to be analyzed in exact order, it reduces the event of problems in the development process. Therefore it saves much time for development software.
The talents of productivity in DSDM are after developers produced a product, a larger number of documents will to make clear the product, and there are a few models and documents maintenance the product. It is very best for product. And a individual guides and training plans will get. It helps customer has learned how to use the merchandise and easily use the merchandise.
4. Strengths of XP(Extreme Programming)
Beck (2000, pp. 150) suggests that ' The practices and the rules work together with each other to create a synergy that is higher than the total of the parts. ' It using proven software development techniques in a tiny team, it helps you to save more human tool for company. And XP pay more attention to customer's requirements and the quality of the products. It reduce the job risk with appropriate routines.
The strengths of website and aim for in XP are it can solve specific business problem, such as jobs has hazy requirements. It could develop outsourced software, in-house development and fix-price deal software development.
For techniques, XP use of set programming, it improves code quality, developers to share knowledge easier and it reduces flaws in coding process. Use operate meetings to talk problems, it solves solutions more quickly, and adjust the team's work direction in short order, it helps you to save to much time for team, and can make more decision for the project. Designing can be used to describe requirements and create time estimates. It helps builders reduce faults and make designers knows what are they have to do and do not need to to do in development time.
Strengths of scope in XP, the planning is to take into account what problems will be appear in the development, and how to prevent them happen. It reduces the feasibility of unforeseen circumstances, Teamwork will helps teammates stocks their understanding about the task and to find the vulnerable dots of the task. Refactoring give programmers the to enhance their code, it helps the programmer understand the system better and makes the code readability. Maintenance can help the merchandise exert its function better.
The outputs are source code and associated device test. The advantages of XP are product test can points out code with test cases, make out up to date paperwork and it can helps imagine for new developers. The other strength is builders always work together in a little team, the development team will with good atmosphere.
5. Weaknesses of DSDM
The weakness of DSDM is the relatively high barrier to entry. Turning to DSDM is neither cheap nor fast, and takes a significant cultural move in any corporation. (Benjamin, J. 2004)
Staleton (1997, pp13) state governments that "A means of developing request systems that truly serve the needs of the business enterprise". It have not too much equirements for the grade of the product.
It only have interface rigorous business systems one request, and can solve business problems. I think it is so slim, such as it is not fit for other applications such as executive, so that it difficulties to be utilized when the target environment is not about business.
The groups that in DSDM should determine what methods will be used in work. It lacks in detail for coders. It only packaged ' good sense '. The iterative stages in DSDM is more boring.
6. Weaknesses of XP
The weakness of XP is the fact it only can be used in small group of developers two to twelve.
The aim of XP is too narrow that it generally does not to analysis the problems which will be happen in the foreseeable future and it hasn't any strategic evaluation of the necessity for the machine.
XP only specify a couple of techniques however, not lifecycle. It depends on set programming, but many programmers have found this way of working uncomfortable, it creates coders interdependence who interact, it also inhibit their thoughts and independent pondering ability, a lot more important could it be will make frequent interaction is exhausting. XP requires a solid and fast development environment, but many development surroundings can not achieve that expectations, therefore XP can not achieve the best result for the merchandise.
Quick design getting together with are too quick, because want to save time, it maybe makes a bad design decisions. Facet of XP that are difficult to look at are cooperation with others in the team, and using simple designs. There require overcoming people's inclination to avoid collaboration and introduce needless complexity in system structure. (Beck, 2000)
Any product is negotiable with the client, so that customer will feel very trouble. XP is too extreme and lacks scalability, it is too casual for most orgnisations.
7. Compare both methods
This two ways of function are very similar. They all for program development, both of these methods are all focus on shorten the development time and fast delivery, they all need teamwork and customers engagement in team.
There are some difference between DSDM with XP.
DSDM is primarily to provide a controlling platform for Rapid Program Development methodology. It is a platform for business centred development and it focuses on delivery of the business enterprise solution, rather than simply team activity. There are more clear define functions in DSDM. DSDM use timebox and MoSCow to make plan time. DSDM highly provide full lifecycle.
XP stresses client satisfaction. It lay stress on teamwork that managers, builders and customers are equal associates in a collaborative teaming and they'll work together to improve the quality about product. It used to develop the system as faster as possible and it should be has a little teams to discuss about the machine and makes a good working environment for designers. It's objective is thin, it only used to solve some problems about the customers' business needs of the merchandise which is never to analysis any problem about next level. Less clear define roles. XP use iteration planning conference to plan time. XP signals on job control rather than provide lifecycle.
4. Applicable contexts
DSDM can be utilized for the reason that contexts.
Projects that is approximately business. Interactive function embodiment through the user program, have clear individual group, no complicated calculation, if is a huge software, the function can be decomposed into smaller parts, time constrained, requirements not too detailed or set and requirements can be prioritised.
XP can be used in that contexts.
Projects that contain some specific problems need to solve, projects that are not constrained by a preexisting computing environment, task with obscure requirements and assignments with regular changes in requirements. Especially useful for uncertain jobs where change is expected;small band of programmers 2-12; need to have at least one consumer involved as well as programmers and have to be able to create automated unit and function checks.
5. Conclusion
These two methods aim to solve the solutions that providing good systems in short times. They all have their own benefits and drawbacks, but them still virtually identical, such as customer involvement, incremental change, speedy opinions mechanisms, fast delivery, both in a tiny team, and so on. Therefore I think if them work together, they should have very good impact. Because they may have show the same fundamentals and it will working on incorporating the relative strengths of DSDM and XP.
6. Analysis framework
DSDM
XP
1. Philosophy
Paradigm
Systematic
Scientific
Objectives
Make the development time as shorten as possible.
Helps people who use the system to learn and how to work with the machine.
Make the largest benefit for business
Make customer satisfaction.
To developed the machine with a good quality as soon as possible.
Domain
No complicated computation running a business problems and
Interactive function.
XP is proficient at to help team who work in the same group solve some specific business problems.
Target
It only can solve business problems and it program in interface rigorous business systems for all those task(small and big) in all company(small and big).
Embodiment through the user interface.
It needs a clear individual group.
There is a period limit.
If it is a huge application, it could be decomposed into smaller parts of function part.
XP is created for the project that with vague requirements, aren't constrained by a preexisting computing environment and project with regular changes in requirements. It really is fit for jobs that can be completed by two to twelve programmers. The sort of development are fix-price contract software development,
outsourced software and
in-house development.
2. Model
Structure Model and
Object-oriented Model
Spiral Model
3. Techniques and tools
Techniques
Timeboxing, MoSCoW, Evolutionary prototyping,
Workshop.
Courage, feedback, simpleness and
communication.
Planning, User reports. Stand up conferences, Designing, Spike alternatives, Refactor when possible, Coding, Match programming,
Integrate often, Trials and
Acceptance exams.
Tools
Common user interface,
Development tools,
Requirements management
tools,
Configuration management tools,
Project management tools,
Documentation tools,
Shared repository and virtual
operating environment.
Automated unit screening tools must be used in XP assessment process, this tools a simple requirement for an effective XP.
4. Scope
Feasibility review ;
Business review ;
Function model iteration ;
Design and build iteration ;
Implementation.
Exploration ;
Planning ;
Iterations to first release ;
Maintenance.
5. Outputs
The result is something that have many functions that gratify user requirements and have some documents to maintenance it and inform individual how to utilize it. The main product is working software of your anticipated quality. A different type of documents can describe the project and provides more documents and models to help individual maintenance the machine, to attain the effect of enhancing the grade of the merchandise.
The result is source code and associated. In another field, users and programmers are all can skilled use the technique. The product is working software.
6. Practice
DSDM originated by the UK consortium in the united kingdom in the mid-1990s. This view has been backed in the task of Jennifer Stapleton(2003). It is a practitioner-based strategy and this consortium are involved in Rapid Request Development development of software systems.
DSDM can help an orgnisation achieve a good level in the ability Maturity Model and it could be used in the TickIT.
XP task was started out March 1996. It really is an extremely popular Agile method. It's very fit for a little group of developers about two to twelve.
7. Product
The product is difference in various phase in DSDM.
Pre-project : pre-project statement.
Feasibility study : feasibility article, put together plan and risk log.
Business analysis : system
architecture definition
, development plan, prioritised requirements list, risk log.
Functional model iteration : useful model and review records, non-functional
requirements list, timebox
plans, implementation plan,
risk log.
Design and build iteration : timebox programs,
design prototypes and review data, tested system.
Implementation :
User documentation, supplied system, trained end user society, increment review.
Post-project : post
implementation review statement.
The romance between developers and customers that work together for their task.
Stories, Jogging code and Testing.
7. DSDM for Complete Solutions
Complete Alternatives is a rapid development company, and it give attention to sell a whole IT consultancy service for businesses. They have some branches in different cities and various country, with the fast development, CS's size is continually be expanded. However at the same time, some problems become more and more obvious, such as lack of communication in the business. Therefore I believe the method not only should be suit for CS company, but also can help CS solve some problem and make the company more better. I choose DSDM be used by Complete Alternatives.
DSDM has eight key points that focus on business need, deliver on time, collaborate, never compromise quality, develop iteratively, build incrementally from firm foundations, communicate consistently and evidently, demonstrate control.
CS primary process is to market an entire IT consultancy service for businesses. DSDM is about truly understanding the needs of the business enterprise and delivering solutions that work - and providing them as quickly so when cheaply as is feasible. (Stapleton, 1997, pp14) DSDM has one process is give attention to business need. They want delivery the product to customer promptly, and give the right price to customers. It is more important for CS. In DSDM project, it use MoSCoW and timebox for customer's requirements. As a result could it be can delivery products on-time and on -cost. Therefore DSDM can help CS save additional time and reduce development costs.
CS needs to software development and it must upgrade they technology to be able to sales more products. technology and processing is becoming an inseparable ingredient in the business world today. (Internet, 2006) DSDM is very suitable for the task that main purpose is software development. The main one concept of DSDM is develop iteratively, so that it can help CS constantly update the program and technology.
I think the issue-based job is to produce a completely communication in the inner of the business. Because there are poor communication in the internal of CS. Effective communication is essential to the success of any business. (Debbie Tullos, 2011) DSDM is more than anything about improving marketing communications between all people mixed up in development of system. (Stapleton, 1997, pp. 65) Inside the DSDM, there are two techniques that evolutionary prototyping and workshop, so it will helps connect continuously and plainly. Use both of these techniques can promote the communication between your internal personnel of CS. Moreover, workshop can promote teamwork between internal personnel, It could helps them improve their work efficiency. It is therefore best for CS.
Never compromise quality is one theory of DSDM, we all understands that CS is an enterprise company, so that quality is very important for it. If it cannot give a good quality product, customers will not to buy anything from CS company. Products to improve the grade of there are more customers will buy products from CS.
CS with the high speed development and it's size is constantly be broadened. So they'll continue to bolster their infrastructure in order to meet up with the broadband development requirements. This requirement eventually have the same view with the principle build incrementally from firm foundations which in DSDM. Infrastructure to bolster makes the business more secure of the development.
Through the highly collaborative and open team strategy, with a no surprises culture. issue has been stored to a minimum. (Timothy Fadek, 2010) A highly collaborative can make the work team more unity, more powerful plus more efficiency. "collaborate" is one of the rule in DSDM. Therefore, it'll makes more unity within the CS company.
Conclusion
I think DSDM method is actually be fit for Complete Solutions than XP. such just as the next aspects that applying, business, techniques, workers management, communication, teamwork and issue management. However, DSDM involve some weaknesses, such as without detail for builders and no more than packaged "good sense". Therefore, if to make DSDM and XP interact, there will have better effect.
