EXAMINATION AND ISSUES AMONGST TRADITIONAL

AND AGILE WEBSITE ADVANCEMENT TECHNIQUES

By
Anees Ahmad Zafar
2015-GCUF-120101

Thesis submitted in partial fulfillment of

the requirements for the degree of

MASTER OF SCIENCE
IN
INFORMATION TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

GOVERNMENT COLLEGE UNIVERSITY, FAISALABAD

2017
 DEDICATED

TO
My Graceful and Polite PARENTS

&
All Family Members
Who live in my mind and soul
Whose love is more precious
Than pearls and diamonds
Who are those whom I say my own
Whose love will never change
Whose prayers will never die
 DECLARATION

The work reported in this thesis was carried out by me under the supervision of Ms.
Rabia Saleem Department of Information Technology, GC University, Faisalabad,
Pakistan.
I hereby declare that the title of thesis EXAMINATION AND ISSUES AMONGST
TRADITIONAL AND AGILE WEBSITE ADVANCEMENT TECHNIQUES and
the contents of thesis are the product of my own research and no part has been copied
from any published source (except the references, standard mathematical or genetic
models /equations /formulas/protocols etc). I further declare that this work has not
been submitted for award of any other degree /diploma. The University may take
action if the information provided is found inaccurate at any stage.

Signature of the Student

Name: Anees Ahmad Zafar
Registration No: 2015-GCUF-120101
 ACKNOWLEDGEMENTS

All praise to ALMIGHTY ALLAH, the most merciful and the most compassionate and his
Holy Prophet ‘MUHAMMAD’(Peace) be upon him) the most perfect and exalted among and
even born on the surface of earth, who is, forever a torch of guidance and knowledge for the
humanity as a whole.

The work presented in this manuscript was accomplished under the inspiring guidance,
gorgeous assistance, constructive criticism and enlightened supervision of Ms Rabia Saleem
Department of Information Technology GC University, Faisalabad for his skillful guidance,
constructive criticism, masterly advice, valuable suggestions and sympathetic behavior for the
completion of this manuscript.

I feel highly privileged to take this opportunity to express my heartiest gratitude and deep
sense of indebt to my worthy supervisory committee, Sir.Tahir Abdullah and
Sir.ShahbazNazir Department of Information Technology GC University, Faisalabad under
whose kind and scholastic guidance, keen interest and constant encouragement.

Words are very important to convey thoughts and thanks, the words are impossible to find to
thank our Father and whole family for their prayers and encouragement for us and for our
work.

Finally, I apologize if I have caused anger of offence to any body and the errors that remain in
the manuscript are mine alone.

Anees Ahmad Zafar

 CERTIFICATE BY SUPERVISORY COMMITTEE

We certify that the contents and form of thesis submitted by Anees Ahmad Zafar,
Registration No. 2015-GCUF-120101 has been Found satisfactory and in accordance with the
prescribed format. We recommend it to be processed for the evaluation by the External
Examiner for the award of Degree.

Signature of Supervisor ………………….

Name: ……………………………………..
Designation with Stamp…………………..
Member of Supervisory Committee
Signature ………………………………….
Name: ……………………………………..
Designation with Stamp……………………
Member of Supervisory Committee
Signature ………………………………….
Name: ……………………………………..
Designation with Stamp…………………….

Chairperson
Signature with Stamp……………………….

Dean / Academic Coordinator

Signature with Stamp…………………………

Director of Distance Learning Education

Signature with Stamp…………………………

 CERTIFICATE BY THE RESEARCH SUPERVISOR

I certify that the contents and form of thesis submitted by Faisal Maqbool,
Registration No. 2015-GUCF-120150 has been found satisfactory and in accordance
with the prescribed format .I recommended it to be processed for the evaluation by the
External Examiner for the award of degree.

Supervisor
____________________

Coordinator __________________
 Table of Contents

1 Introduction .......................................................................................................... 12

1.1 Background ................................................................................................... 13

1.2 Objectives ...................................................................................................... 14

1.3 What is the software life cycle model? ......................................................... 16

1.4 What is the software process model? ............................................................ 17

1.5 Research inquiries: ........................................................................................ 19

1.6 Regions and restrictions ................................................................................ 19

1.7 Structure and exploration strategy for postulation ........................................ 20

1.7.1 Structure of the postulation .................................................................... 20

1.7.2 Research Method ................................................................................... 22

2 A overview of Conventional Programming Advancement Process Models ........ 24

2.1 TraditionalProgramming improvement.process models ............................... 24

2.2 Waterfall process show ................................................................................. 28

2.2.1 Prerequisite definition ............................................................................ 29

2.2.2 Planning Framework and Programming ................................................ 30

2.2.3 Implementation and unit tests ................................................................ 30

2.2.4 Combination and frame test ................................................................... 30

2.2.5 Operation and support ............................................................................ 30

2.3 Pros and Cons of waterfall show ................................................................... 30

3 Variety of tight methods ....................................................................................... 32

3.1 Advanced Nimble Programming Union and the LTTE Manifest ................. 32

3.2 Agile strategies .............................................................................................. 33

3.3 Extreme Programming (XP).......................................................................... 34

3.3.1 XP process phase ................................................................................... 36

3.3.2 Partitions and homework in XP ............................................................. 38

 3.3.3 XP behavior ........................................................................................... 39

3.3.4 Ease of use XP ....................................................................................... 44

3.4 Scrum ............................................................................................................ 45

3.4.1 Scrum internship .................................................................................... 46

3.4.2 The Scrum Group's Parts and Obligations ............................................. 48

3.4.3 Scrum installation .................................................................................. 49

3.4.4 Break through the crash ......................................................................... 49

3.5 Together, the process (RUP) has been assembled......................................... 54

3.5.1 Form process procedures ....................................................................... 55

3.5.2 RUP Measurement of the work process................................................. 57

3.5.3 Best Practices of RUP ............................................................................ 59

3.5.4 Share and responsibility in RUP ............................................................ 60

3.5.5 RUP ease of use ..................................................................................... 62

4 Agile techniques in Programming Improvement.................................................. 63

4.1 Difference between custom and temporary programming enhancements .... 63

4.2 Project achievement or disappointment rate of Customary and Lithe

undertakings ............................................................................................................. 67

4.3 Success factor in the coordinated enterprise ................................................. 74

4.3.1 Prerequisites and Client inclusion .......................................................... 77

4.3.2 Disable correspondence ......................................................................... 77

4.3.3 Continuous incorporation and preliminary test...................................... 79

4.3.4 Small discharge ...................................................................................... 80

5 Exchange and conclusions .................................................................................... 81

5.1 Discussion ..................................................................................................... 81
5.2 Conclusion..................................................................................................... 82
5.3 Future Study .................................................................................................. 83
6 Refrences .............................................................................................................. 85
 LIST OF FIGURES

Figure 1: Structure of the Thesis .................................................................................. 21

Figure 2:Programming process .................................................................................... 25

Figure 3a: Software development life cycle ................................................................ 27

Figure 4:The Waterfall exhibit steps............................................................................ 29

Figure 5: XP Process .................................................................................................... 35

Figure 6:Cycle in XP_advancement_process .............................................................. 37

Figure 7: The Scrum Process ....................................................................................... 46

Figure 8: RUP phases and workflows .......................................................................... 55

Figure 9: Comparison between RUP roles................................................................... 61

Figure 10: Requirement categories .............................................................................. 72

Figure 11: Agile project success rate. .......................................................................... 73

Figure 12: Guessed achievement factors ..................................................................... 75

Figure 13: Lithe correspondence cycle. ....................................................................... 78

Figure 14: The correspondence estimation of various methods .................................. 79

 List of Tables

Table 1: XP practices .................................................................................................. 43

Table 2: XP practices by 5-A model ............................................................................ 44

Table 3: Terminologies used in Scrum Communications ............................................ 54

Table 4: Difference between agile and traditional software development. ................. 67

Table 5: Success and failure rates of Agile and Traditional projects. ......................... 68

Table 6: Comparison rate of Agile and Traditional project. ........................................ 69

Table 7: Achievement and Disappointment of Worldwide Ventures. ......................... 71

 LIST OF ABBREVATIONS

DK Development Kit
GUI Graphical User Interface
RQ Research Questions
RUP Rational Unified Process
SCM Software Configuration Management
SDLC System Development Life Cycle
SRS Software Requirement Specifications
SQA Software Quality Assurance
UML Unified Modeling Language
V&V Verification and Validation
XP Extreme Programming
UC Use Case
SA Software Architecture
LD Logical Diagram
CS Conceptual Schema
E-Business Electronic Business
E-Commerce Electronic Commerce
 ABSTRACT

The increasing expansion and complexity of Web applications poses new

challenges for software developers. As a result, several development methods
for this class of application have been proposed in the last years. However, the
majority of these methods only support the project stage satisfactorily. We can
easily notice some problems related to the form of functional and information
aspects are handled in conjunction. Besides, development methods for Web
applications give very few attention for the conception, planning, testing and
client evaluation stages. This paper presents such problems, presenting a
comparison study of Web applications methods based on their main features
and supporting mechanisms. Considering the fact that most of the methods
have limitations, we present a case study based on a Web portal in order to
describe advantages and disadvantages of some selected methods.
1 Introduction_
1.1 Background_

These days, products used in any field in products, products, training, sports are being
trusted because the rapid improvement in innovation, allies need to refresh all
products and business needs in the product. Institutions have done a test for product
development organizations.

The Association needs its professional programming over time with financial
planning, and due to the adjustment of the business process, government needs
change, which creates problems for a better group. Because it is extremely difficult
and costly and improvised in terms of productivity and wind expense, with plans to
slow down and end with cost-effective expenses.

Lastly, keep in mind the objectives of these problems in product development.

Improvement programming should be used to improve product improvement
institutions for success strategy. Improvement of light, there is a change in any stage
of product development, and it is the cause of effective technology.

Comparative programming process and their past development is comparable and

disappointment is coming with many product-making organizations who do not work
and who is not. How is the development of these two unique ways of insight (the best
practices and the face of past development and frustration) these programs? It may be
that, each of these programming supports close cooperation between upgrades and
business groups, rather than improve programming groups' stores, rather than
compelling the data generated in the region; Go to the programming parts of the
operating parts instead of the specified vehicle; instead of changing the necessary
conditions by the customer, instead of changing the desired conditions by the
customer, the "cast-in-stone"; and groups Versatile organizational status

The meaning of the word is lightweight. According to the principle of simplicity and
speed, according to the Flowers and High Samarrors (2001) (basic programming of
smart programming), the basic objective of smart technology is the assistant (client
and engineers working together with the closest lettering) Anything but difficult and
learning learning, stored around) Exercise (last minute improvement)

Clever use of fraudulent techniques runs in 2001, when improving 17 different types
of programming and upgraded efficient programming unions. Some of the basic
objectives of this announcement are as follows:

 Satisfy customers with programming time

 Welcome to product changes in product development or development
development.
 Programming is important to meet the needs of the customer
 Support for agent designers

1.2 Objectives

The purpose of this study is to further show how programming progress is the
technique that is to show subjects in the waterfalls. For this reason, the product
expenditure plan and the late expired. This work is also focused on the performance
variables of some strategies and reflected techniques. How to reduce simple tech
programming problems? The interrelationship between traditional and coordinated
techniques has also been discussed in principle.

There are five parts in the work. The primary part of the theory is about the
presentation that targets postulation, research, expansion and obstacles, which are the
basis of information.

Principle simulation and structure The second part of the theory provides an overview
of the problems in the strategy using the traditional programming technique progress
and the usual program improvement process cascade shows. The inconvenience of
favorable conditions and waterfall technology is shown in this section. In the second
part the questionnaire has been clarified the main question of work. In the third
section of the work, three clever techniques have been explained in a similar part of
the three elements about the power elements efficient strategy. The second research
question of the theory has been clarified in the third part. The fourth part of
postulation focuses on the distinction between traditional program improvement and
efficient program progression and how soft strategies are used to reduce cost and time
in product improvement. The discussion is discussed in the fourth part of the study of
the frustration of efficient and traditional activities. The fourth section shows the third
and fourth research studies of the work, five sections of dialogue and conclusions will
be presented and future work has also been examined in this section.

 Start / Plan System: Where do the systems come from? In most cases, the
two new potential systems replace or supplement existing information
processing systems, whether they are already automatic, manual or informal.
 Need for analysis and specification: A new software system is likely to
solve, its operational capability, its desired performance characteristics, and
the resource infrastructure needed to support system operations and
maintenance.
 Functional or prototype specification: Recognizes and prepares formally
compiled objects, their properties and relationships, the functions that change
these objects, the obstacles to system behavior, and so on.
 Partition and select (vs. reuse v): Requirements and has functional
specifications, divide the system into manageable pieces, which reflect the
logical subsystems, and then define a new, existing or reusable software
system matches the required parts .
 Architecture Design and Configuration Specification: The system defines
the interconnection and resource interfaces between subsystems, components,
and modules that are suitable for their extended design and global
configuration management.
 Detailed component design specification: Defines the procedural methods
by which data processing in a component module is converted to an output
provided by the required input.
 Component implementation and debugging: Adds the previous
specifications to the implementation of the source code and validates their
basic operation.
 Integration of software and test software systems have confirmed the
overall integrity of the architectural configuration and compatibility modules
 and implemented is under consideration by the processing interface by
confirmation of completion and Confirm interconnection against their
specifications and Validate the performance of systems and subsystems
against requirements.
 System documentation review and distribution: Packaging and
streamlining the systemized document and system development details
recorded in the User Guide, suitable for system delivery and support.
 Deployment and installation: Install distributed software in the local
computing environment, operating system settings and configure the user's
privileges to use and ensure the viability of the basic system operation to
provide guidelines for performing Diagnostic tests of cases Make
 Training and Experience: Provide instructional aids and guidance to system
users to understand the capabilities and limitations of the system to effectively
use the system.
 Software Maintenance - Maintain the useful operation of a system in your
host / target environment by providing requested functional enhancements,
repairs, performance enhancements, and conversions.

1.3 What is the software life cycle model?

Software life cycle model either a descriptive or normative characterization that is

how it should be developed or how the software should be developed that describes a
descriptive model story that has been developed a special software model system
descriptive of software development To understand and improve processes, or
empirically reminiscent recall models TIS, CROSSOR, ESCOI, 1988) can be used as
a basis for construction. A reminder template determines how the new software
system should be developed. Systematic models are used as guidelines or frameworks
for organizing and organizing software development activities, and in what order. In
general, it is easy and more common to explain a systemic life cycle model for the
development of software systems, which is possible because most of these models are
intuitive or reasoned. This means that many very effective descriptions describing the
implementation of a software system can be ignored, later generalized or deferred to
be taken into account. Certainly, cause concern for the development parameters of
various types, in different programming languages, the relative validity of this life
cycle model, while developing a variety of application systems such as, etc. However,
during the development of educational models, software engineering equipment or the
use of any environment is also used for work and package development techniques.
On the other hand, descriptive life cycle models, specialty.

As such, they have a clear reason for the big down and are more difficult: to inspect
the data in the entire life cycle of a software system or should collect, time to measure
several times over the years. In addition, the descriptive models are system specific
and are generalized only by systematic comparative analysis. He therefore suggests
that the reminder software will focus on the target model the life cycle, unless there is
no available observation information in sufficient quantity, which is available for
common sense clearly describes the descriptive life cycle model.

These two characteristics show that there are many different goals for making
software life cycle models artistic. These features work as one

 Guidelines for planning, planning, employees, budgeting, planning and

management of software projects on time of organization, location and
computing environments.
 Line of procedure framework for preparing documents to be delivered to
clients.
 Software tools will be best suited to determine the tools and methods to
support the activities of different life cycles.
 Framework for analyzing or estimating allocation and resource consumption
patterns over the software lifecycle.

The basis of empirical studies to determine which software affects productivity, cost
and overall quality.

1.4 What is the software process model?

Unlike software lifecycle models, software process models often represent a network
sequence of activities, objects, modifications, and events that symbolize software
development strategies. Such models can be used to develop more precise and formal
details of the software lifecycle activities. Their power is generated by the use of
sufficiently rich notations, syntax, or semantics, which are often suitable for
computing. The software process network can be thought of as representing several
interconnected work streams. Strings represent a non-linear verb that creates and
converts computational objects (resources) into intermediate or finished products.
Non-linearity means that the sequence of actions is indeterminate, is repeated can be
multiple / can accommodate parallel options, as well as being ordered to account for
partially progressive progress. work actions in turn are likely to see the non-linear
sequences of primitive actions reflecting nuclear units of computer tasks such as
selecting the use of a user or mouse or keyboard, inputting menu.. Work strings can
be used to mark sequences of sequential or descriptive actions. What provincial work
streams should be completed and in what order are planned. For example, for object-
oriented software design activity, a series of jobs may include the following
workarounds:

 Develop an informal specification of system history.

 Identify objects and their properties
 Identify object operations
 Identify the interface between objects, attributes or operations
 Apply operations

Of course, the actions of the order gradually object-oriented software several

iterations and race invitation of non-procedural primitive action progressed the design
might be necessary. Other tasks involved in assembling or working in strings are
divided into strings and into the production of a network or composite network (Kling
1982). Web Production is the "organizational generation system" that transforms
computing, cognitive, organizational, and other resources into assembled, integrated,
and useful software systems. Therefore, production is forged, a system developed,
used and maintained. However, the chain of normative tasks and operations can not
be guaranteed can formally all situations or emerging in the real world of 5-foul-up as
idiosyncratic forecasting software development (Bendifallah 1989 mid-1990). Thus,
any software production site will be realized in a certain way.
Expression work is a kind of unpredictable task that occurs when a task is insufficient.
It is something else to pass the flow of production chains to restore progress on
everything and disarticulated working range, or an open non-deterministic sequence
of measurements. Thus, descriptions of narrative task chains were made to illustrate
current events and emerging situations as people struggle to follow a planned
workflow.

Software development conditions, including joint work action that people be a

software system, or interact with other people who may be ble to change the current
situation will affect whether or not you have a change of the system is the odd gold
quota Taking care of their usual needs . This joint working hypothesis has also been
called software mobility.

1.5 Research_Inquiries:

Four research questions (RQs) follow, which can cover the above mentioned
objectives of the postulation.

RQ1: What are the problems with traditional programming upgrade strategies (such as
waterfalls)?

RQ 2: What are the theoretically coordinated strategies for improving programming?

RQ3: How to separate the coordinated techniques and traditional strategies (such as
waterfalls) in program improvements?

RQ4: How skilled strategies are reduced by improving programming?

1.6 Regions and restrictions

"Since the beginning of the programming or the design control framework, it is

concerned about all parts of the programming generation, in particular to get the
frame after use." Programming design products for organizations to meet their needs.
Definition The programming is clearly a very large area, which can cover many
processes and steps of the building.
There are several strategies for improving the program: some of the strategies are
considered a great technique, unlike other techniques and other methods. The current
theory focuses on the shortcomings of the traditional program reform, which depends
on financial planning and the timetable. The work is similar to focusing on new
technologies for product design and how coordinated strategies overcome the
problems of traditional programming.

According to the conventional waterfall, the modular programming is limited to the

construction and the skilful strategies, as there were convincing articles and clever
techniques for testing the waterfall strategy.

1.7 Structure and exploration strategy for postulation

1.7.1 Structure of the postulation

Figure 1 shows the structure of the postulation.

Figure 1: Structure of the Thesis
The first part Product Improvement Waterfall thesis of technology and has made
clear using traditional strategies to present intelligent technology in the subject,
providing foundation information on how to submit a coordinated and why. In this
area the structure and research strategy is defined for the purpose of postulation,
inclusion and theory of examination, conclusion and conclusion.

The second part of the work deals with the development of waterfall corrections.
Waterfall lifestyle is clear and the nectar shows the focus and obstacles technology
cascading towards the end.

The third part of the work on the light requires walking strategies, such as an efficient
programming upgrades organization, as the latest man is strong, with a light solid
strategy, three basic agile techniques extraordinary programming (XP). The scram and
normal-bound process (RUP) was clarified; Phases, parts and obligations when the
process can be used.

The fourth part This is the sketched display of the contradiction between wise and
usual programming enhancements, company success and disappointment rate
presented here is the fourth section, company success and desperation, easy-footed
worldwide to indicate a part of the key factors There are clear strategies involved in
coordinated work time and time Reduce costs.

The fifth part of the work deals with discussions and results. The total outline of the
theory is displayed in this field.

The sixth part is about future research.

1.7.2 Research_Method

The mentoring test strategy is to be used as part of this work, the use of a subjective
research that is measured is not necessarily measured in this article or approaches
subjective research overview writing, data innovation and exceptional programming
designing inquire for the articles that are in different Books. Specific books with
programming, assessment and estimation identified IEEE and Scopus Google has
used some points common programming advances cascade strategy, cyclic techniques
and playful strategy of stories, variable performance techniques of light feet, reduced
time and cost in coordinated strategies, and items collected on very low discharge and
similar cafes.
2 A overview of Conventional Programming Advancement
Process Models

In this part the primary research question of the thesis is clarified.

2.1 Traditional_Programming_improvement.process
models

The model of processes to improve programming is used for everyone. The product
show is an unbalanced product type that speaks from a specific point of view and
gives incomplete process data.

The programming process is a structure of exercises related to all the most important
products.
 Figure 2:Programming process

Figure 2 explains the product process and we can see that in the production process
involves such exercises in which the work is involved, the performance of these
orders is called growth and expectations, and there is the focus of the SQA . . The
programming is called Super Programming because it meets the necessary
requirements, including the SQA, Programmatic Program Management (SCM) and
Evaluations. Umbrella exercises are free from all workplaces
From now on, there are many product formats used to improve programming, as
shown in .There are several processes that are almost identical in each process. These
steps have been recorded below.

 Software determinations: Here the usefulness of the product is characterized

and the requirements on the operations of those functionalities are
characterized.
 Software outline and usage: The product which can finish the required
particular can be created.
 Software approval: The product ought to fulfill the client, implies the product
ought to play out every one of the assignments for which it is created.
 Software advancement: The product must be prepared to meet the changing
client require.

In its improvement life cycle, a product element is either in the organization or in the
phase of eradication. The original startup phase of the hold item on hold is where the
necessary conditions for the product are deposited. Given these requirements, the
beginning of all the remnants (structure, usage, combination and sending) of product
advancement is the final step of the settlement product article. Steps at the level of
operation and maintenance as shown in Figure 3A begin to eradicate.

Once an organization presents a programming element in its collaboration, then this

product is present for some time with some changes and the association can not do its
work physically. With the progress of time, there are many changes in a similar
programming element and the product continues for succession programming, and
either parts or entire frames fall in the elimination phase, and thus another cycle life
begins.

As it appeared in the sense of 3B, the staging of the old frame was changed to a new
frame and the second life cycle of the frame begins. The old frame works so far until
new frames start working.
Figure 3a: Software developme

nt life cycle
 Figure 3b: Programming improvement life cycle

In Figure 3B, the scaffolding of the old structure becomes the platform of the new
framework in Figure 3A, and then, a similar programming improvement cycle begins
for all remaining steps of progression. .

2.2 Waterfall process show

There are many traditional models for programming progress such as cascading
shows, incremental enhancements, re-use of programming, and so on. The main
model introduced to improve programming was a demonstration of cascading
programming progression, which was familiar with the description of product design
practices in 1970. As the SDLC cascade is a successful model for programming
design, in which the stage of progression of the product is in an arrangement, when a
phase is finished, it is stored and the same finite phase changes in the contribution for
the next phase. .

Cascading performance is a traditional programming progression process that is

typically used in most programming improvement initiatives. It is a continuous
model; As a result, a signal of the beginning of the next movement to complete an
exercise system. This is named after the cascade because process flows start
effectively with one phase, then down, the next. This forms a structure for improving
programming. Some models of models exist, each using specific characteristics for
each step.

The cascade show displays a systematic movement, in which you need a special
movement plan and schedule before you start. See Figure 4
 Figure 4:The Waterfall exhibit steps

Figure 4 in the next area is obvious. Figure 4 is clarified with emphasis on Basil's
(2012) programming book.

2.2.1 Prerequisite definition

The stage is essentially called the required phase (SRS). In this course, product
preparation has clearly ended. In this internship, the executive and business
investigators announced the useful and non-utilitarian needs of the product. Utility
requirements are generally derived from product use cases (CUs). UC shows the
cooperation of structures with customers. The unprivileged prerequisite requirements
have limitations. Non-pragmatic requirements are not a problem with the product; It is
concerned with the properties of programming, such as care, versatility, stable quality,
execution, etc.
2.2.2 Planning Framework and Programming

The normal engineering of the structure is established by specifying the requirements

for the equipment or programming structure in the frame and structure of the product
structure. Product engineering separates the product design and its design phase, the
product design (SA) is created, the theoretical model of the database (CS) and the
sensitive graphic (LD) are drawn, the interface graphical user (GUI) The structure is
characteristic.

2.2.3 Implementation and unit tests

The total configuration of the programming has been changed to a PC program. This
phase of the whole frame of the structure has been changed in the next part of the
world.

2.2.4 Combination and frame test

In the process of becoming valid after the internship solution between coordination
and structural testing. In this course, the entire structure is tested and tested, which
was declared in the pre-condition phase. This internship is called Confirmation and
Acceptance (V & V) Internship We and V are the first time a process and the product
is ready for delivery.

2.2.5 Operation and support

The last period of improvement of the programming is the platform of operation and
maintenance. During this phase, the object expressed by finding the errors after the
operation of the product is changed. Errors are increased

2.3 Pros and Cons of waterfall show

As stated, cascading performance has fewer priorities than vulnerabilities

The benefits of cascading performance are given below.

  Sufficient documentation is the favorable situation for the second part.
Structure is the favorable position for the new part.
 Simple and easy-to-use programming improvements show.
 Everyone has a normal result, which is easy because of the flexibility. One
step at a time between improvements
 These clear requirements are defined for the company.

The bottlenecks of the cascade show are given below.

 Some essential things can happen after the mandatory requirement that are
gathering the scene and causing problems.
 Prestigious problems in any phase have not been fully explained in a similar
step.
 There is no idea of commitment for the different steps (parceling)
 The new customer requirements are extremely expensive and cannot be
balanced in the current product version.
 Estimating time and expense for each step is extremely difficult. There is no
model before the completion of the life cycle
 In the final phase of the progress tests
 If the test examines some problems, that's why the setting is exceptionally
difficult.
 High risk throughout the lifecycle of advancement.
 Not defined for the arrangement of questions.

In this part the second research question of the thesis has been clarified.
3 Variety of tight methods

The principle of programming is to provide customers with the best of both worlds.
View an advanced programming life cycle (SDLC). In order to achieve high quality
customer satisfaction and the achievement of SDLC

In recent years, considerable progress has been made in the field of programming by
introducing new technologies in this field. Over the last 25 years, the area of
programming upgrade strategy has greatly improved. Several strategies for product
progress have been presented, some of these techniques have been rejected, an
important part of these techniques, with some changes

In 1970, reported primary waterfall upgrade. Be that as it may, Royce relied on the
fact that the cascade show is not enough for product development because it is an
effective improvement of programming. In fact, even Royce ensured that the dynamic
strategy would be useful for programming improvements among the product and
progress stages.

Due to the advancement in the field of the Web and exceptional e-business (e-
business), due to the inevitability of commercial and traditional programming
strategies. Draftfase programming techniques are however very favorable for the
future.

3.1 Advanced Nimble Programming Union and the LTTE

Manifest

The use of the progress strategy has been developed and developed. In order to
overcome these problems, in 2001, 17 people from different organizations had set
standards for the development of game standardization.

1. Our most important solution is to meet the needs of customer.

2. The need for welcome changes, even in progress. Integrated processes make
changes for the benefit of the customer.
 3. For a while, give programming of recurring jobs with short periods of
welding.
4. Trade and designers collaborate through work every day.
5. Build activities around induced people, give them the land and they must take
care of the business.
6. The most productive and successful strategy for transmitting data and
discussions on group improvement.
7. Required work schedule PF Advance
8. Anticipated owners, designers and customers should have the ability to keep
continuous time for the proper improvement of the Agile process.
9. Ongoing reflections on special size and planning skills.
10. Simplicity - The function of improving measurement measures is fundamental.
11. Better engineering, prerequisites and planning of self-sorting group.
12. Overall, the group thinks this point is clearer than the compilation of tunes and
revises its conduct as needed.

The motivation behind the Light Pad Manifest Standards was the basic goal.

 Individuals and connections on processes and tools

 Work on the complete programming of the documentation
 Joint effort of the customer by contractual transaction
 Respond to change after an arrangement.

3.2 Agile strategies

Key technical results important in flickering basic skillful strategies and the need to
focus on the ability, the best time to start are to tell them and collect comprehensible
and critical to make the products imaginable quickly for Feek back than meet.

As stated in the art, it is said that it has the following programming properties

 Increase: little discharge programming with fast cycle.

 Cooperative: Customers and designers are in close correspondence.
 Simple: simple to learn and all-around stored
  Adaptive: This can force change in any phase of improvement.

Defective technology, performance and quality In addition, the requirements and

configurations of effective techniques are customizable and can change at any stage of
the improvement phase. Litheh's programming improvement techniques include
insignificant documents, prototypes and iterative progress, like many documents. As a
signal of qualified signal change in the technical requirements, the programming
messaging continues to work with traders and designers.

In the dynamic programming process, there are special properties that influence
programming to accelerate. Qualities in the effective management process

 Modularity in the promotion process.

 Informative with small cycles for quick confirmation and empowerment.
 Insisted in half to a year and a half
 The error process is under development, each movement unforgettable.
 Adapted to new dangers imaginable
 Incremental processing approach that allows working with small holes.
 Infected and incremental approaches limit risks.
 People organized the process
 Collaborative and open style of work

Only three accomplished techniques (extraordinary programming, melee, balanced

process and process) will be considered from the coordinated strategy above the
theory. Segments with these strategies were outlined in 3.3, 3.4 and 3.5.

3.3 Extreme Programming (XP)

After the problems (with the advancement cycle) the technical improvements were
made by the usual use which, because of the effective programming after the future,
presents hundreds of countless different paths on the previous files. Inadequate
Programming (XP) is a lightweight programming solution designed by the user.
XP has presented a better approach for improving programming and producers in
general, to host exchange, unsurprising logical strategies and that different we have
compared to the account of strong oral connection, programming of games, robotic
tests, the total code of the property and the description of the company Presented.
Figure 5 shows the XP process

Figure 5: XP Process
Five steps in the process of the XP investigation phase, step system, cycle for step,
product ion phase, apache phase, and death phase.

3.3.1 XP process phase

There are five stages of extraordinary programming and it has been clearly used.

Investigative Platform: The investigative platform is one of the most important

stories in the subject's history. At the same level, enterprise groups acquire their own
devices and know the tools and innovations they will use in their work. Each device
and its innovations will be tested and tested. This phase is based on the nature of the
software engineer, which is used for innovation. Normally, the ideal opportunity to
check is half a month or a month.

Organizing the forum: Understanding the understanding of the situation and the
situation. The estimation of time and time for each story is completed by the software
engineer. The arrangement takes a few days and the primary discharge takes place
around two months.

Emphasis on the discharge step: There are some things in this course that you can
do. Some points of the scene are made before the main discharge. Each focus is
included in the exam, to prepare the framework, organize tests and test parts. After the
accent, there is a coherent solution. In the middle, the primary cycle is done and the
engineering of the entire structure is also done. The stories are used by the customer
after the final focus on the build frame at the end of the customer's life is ready.

Production level: This step is the customer who gives the customer experience and
the performance of the structure is verified. In this process, new changes can be found
that can be used in the current dump. This process is one of the most extreme. The
past happens in this phase

Maintenance internship: After the arrival of the main thrust, the customer receives
the structure. These courses are part of the structure of the art position, and they are
essential for the client. Frame creation has reduced speed and changes in group
structure.
This is the last period of advancement. During this phase the client is completely
satisfied and there is another story to improve. In this course, the practical and non-
functional requirements have been exhausted. Between this step, the final documents
of the structure are not found in the engineering, the outline and other details in the
code. Between these phases, it can be assumed that if the structure is not relevant to
the plan

As in the XP strategy, it has been said that the increase has increased in the process,
giving the customer the continuous arrival of the cycle for the customer to complete
the meeting. See Figure 6

Figure 6:Cycle in XP_advancement_process

In Figure 6, the way stories change on the cycle and work modules in the XP upgrade
process is shown. The process processes and organizes the new story, breaks the
story, and the coding process is completed and later, the test (income to join and test)
is done. This is the result of the test process, which is "no". We will have the
opportunity to do this, if the story is complete, then the story is filled and the structure
is tested.

3.3.2 Partitions and homework in XP

In these areas, there are specific periods of agencies and there are homework. Talk
about the parties and their tasks together

Software Engineer: The most essential part in the XP enhancements that prepares the
test and changes the programming code for customer stories. One of XP's
accomplishments is the exchange of software engineers and other affiliates. The main
duty of the software engineer is to make the code direct and positive.

Client: The client is a person who prepares and enters XP stories and practice tests. In
the utility test, the client can see the outline of something else that has been
underlined. The customer is cautious to meet the same needs

Analyst: Customers create useful tests and analysts help them write tests. The main
responsibility of the analyst is to run tests and give test results. Analysts maintain
similar test instruments.

Trackers: The tracker is part of a checker that is used to check the evaluation made
by the group between the arrangement of the tracker. The estimate may be more likely
to be approximated and the tracker may receive an advance opinion. Trackers
examine the importance of the day and the role of the author.

Mentor: The person in charge of the whole process takes care of managing one of the
people in the group. Mentor XP has a good understanding of the process

Expert: One of the external parties has a particular understanding and helps partners
in some issues.
Chef: The manager is also called a huge manager and he sits on the option. The
observer reflects on the enterprise of entrepreneurs, with colleagues of an observer, no
one becomes an attempt to deal with the issues of close correspondence.

3.3.3 XP behavior

XP was found in the current year as a result of its established procedures (Williams
and Upchurch, 2001) XP Hans is selected from the current best strategy (Beck 1999)
See Table 1 below.

Practice_> Details_>

Close correspondence amongst software engineer and client. Client

Planning_game chooses the

timing of the release and the programmer estimates the effort for
story.

The product ionization of the straightforward framework in brief

Short.release time of around 2 to 3 weeks.

The new forms are discharged no less than consistently..

Metaphor_++ A short portrayal of how the framework will function. The
. framework is characterized by a representation

of set of representation between the client and software engineers.

Straight.forward_
design point is the easiest conceivable plan for usage at the present minute.

The unit test are run ceaselessly before coding and the utilitarian
Testing_+__ test being composed

by the client

Improving the code structure while saving its capacity. Evacuating

Refactoring}{- duplications,

enhance correspondence and make the code adaptable

Pair/123 At a similar time two developers are occupied on one PC.

Programming1+

Collective1_ The developer are free, anybody can change code whenever.

possession ;’

The prepared code is coordinated with the code base and joining
Continuous-=” test is completed to

Integration_+ check the code is working..

The greatest time for work is 40 hours in seven days. Two weeks
40_hours_week successive over
 times isn't permitted. On the off chance that it happens then it's an
issue to be understood.

On.location_custo
mer The client is accessible all the ideal opportunity for the group.

The software engineers need to compose the code as per the coding
Coding_standard principles

The programming region ought to be substantial. The match

Open Work programming ought to be in the middle

Space of the space

The group has some particular decides that ought to be trailed by

Just-rules each colleague, yet
 the standards can be changed by the prerequisite.

Table 1: XP practices

XP practices by 5-A

Level.of.Coverage Explained.by 5-A.Model Areas of improvement

Sufficient123456  Continuous. 5-A.model gives adequate

Integration
 Spike.12 coverage for rehearses

 Aggregate+code
possession12
 Analogy*---
 Open work
space21
 Coding1standard
 Re_factoring23
 Just_principles+

 Commitment.administratio
Clarified, yet  Planning Game n.
require support  Little_releases  Business*utility+
from other
theories  Combine software  Enhanced0process teach
 On location  Decision/making
customer  Effects of timely blunder
 Testing123. recognition
 Straightforward  Cost of progress bend
Design

Out of scope 40_hour_week Sustainable1pace1

Table 2:XP practices by 5-A model

Explained with the help of the XP repeats model 5-A in the table above 3. The scope
of the standard, "substantial" refers to hypothetical model That continues as XP mix
to complete repeats for help the Total code property, representation, instead of open
work, standard coding, refactoring, and the right direction - provides instructions.
"However, the clarified bottles require another hypothesis show the model XP That
does not give full support Repeat as the organization of pleasure, slightly combines
the programming of the release, the nearby customer, the tests and the direct plan Is.
Some of them are subject to change, and these upgrades are listed in the "Category of
Change". The out-of-grade segment shows that the model offers no viable help to XP,
such as a 40-hour week.

3.3.4 Ease of use XP

As XP technology shows, can be used as part of a business and there is no restriction

for that. In any case, XP technology can be used for small and medium enterprises.
The display of most of the practices in the system of Hussein et al That the XP can be
used in the work, while some have required a special exchange depending on the type.
3.4 Scrum

The use of Keenan as in the past, it is necessary to modify the process of improving
products much has been improved character programming process, for example,
intelligent strategies (Scrum) can extend the accelerated, high-performance vehicle
and elements The interaction between the life cycle must be carried out according to
the guidelines. An overview between the scrum and the XP-led agile strategies is
being adopted in the European programming advancement associations established
because of their established processes and stated that the bus is just beginning.

As noted in the first consideration of Skrom's progress, the structure dealt with the
reform process. Scrum approach is used to implement a mechanical observation
process to control the envisaged framework a way to examine ideas for better
adaptability to cope, adoptability and profitability why. As stated in the primary
motivation behind priorities, time allocation, ownership and innovation. This
approach will be used to advance the process of success and to improve the structure
of the process.

Their investigation revealed that the drum provides a lot of help for existing
programming design practices (such as testing in a union). There are several
administrative exercises in the flock, and infinities are developed and go further. The
melee process has been shown in Figure 7 below.
Srum process

Figure 7: The Scrum Process

The slam courses in the following segment have been explained in detail

3.4.1 Scrum internship

Preface, improvement (also called entertainment) and postgram. All know the Scrum
internships

Pre-game stage: With the preliminary phase two primary zones, the arrangement and
the engineering / state framework unusual.
The structure between the layout section is made to mean that the object is made
between that bit in which the principles are the usual common requirements. In
addition to the needs are organized and the execution of the work is estimated for
their execution. The ease of use of the mailing date and publication identifier of the
utility evaluation article is refreshing (usual update) with the need to have at least new
requirements and conditions prerequisites. In addition to the arrangement of the
clause, the addition of the meaning of additional groups is used in the equipment and
confirmation of the approval of different assets and so on and government funding.

The second part of the pre-games is an unusual engineering / state profile. In light of
the excess of engineering articles, there is an unusual situation of articles, seeing
articles and seeing things and recognizing things in the world and working for them.

Improve the course of said ends of similar entertainment courses (deadline): This
course progression of course, nothing to do with the discharge of advancement with a
specific time to meet the needs of quality time and spending plan needed.

The work will improve in panic. This framework has been prepared in terms of
vehicle review, planning, development, testing and training. In search of improvement
among the advancement of the administration, the time of progress, the nature of the
work, there are various events with groups for the investigation of the conceptions of
discharge. Various repetitive dashes are completed before the article is ready. In one
or more of the following, the course can be taken multiple times and an element.
Audit, audit and customer involvement, agreements and promotion of each series. All
articles run between the structure of the structure and the audit of its execution and in
the group are examined. Here are some of the issues discussed in the document and
presented in the following table.

Postgame (Conclusion): The postgame is the last step of the melee and is eliminated
when the required is over. There are no new things from the stage of improvement.
During this phase, the structure was prepared for the holidays. The alternative practice
of this course is reconciliation, comprehensive frame testing, ultimately the best
documentation and final discharge.
3.4.2 The Scrum Group's Parts and Obligations

Scrum groups are qualified to successfully deliver services. These melee groups are
underlined so as to be adaptable, innovative and beneficial. Scrum groups recount
objects incrementally and diverted

This melee group included Item Property, Advancement Group and Skrom Ace.

The owner of the item is one of the supporting elements of growing respect items and
furthermore the item owner is in favor of advancement cooperation.

This article is the responsibility of the owner of the item dealing intensively,
obviously before the reinforcement options, and requests for quotation (need) Point of
construction done accomplishment to the best goal and achievements, is the
development group This is similar to the task of the owner of the object has been done
to build the item well done, it is clear to all, and the guarantee of the article of the
group QA The Correction is guaranteed. Understand things in man, and what group
progress will be next (work).

The owner of the object is a single person; The property is a lot and it is about the
property, the choice of the landlord is final and everyone in the association has to
accept it and see.

The reform group includes such experts, who deliver the releasable commercials of
the "complete" element for the end of each race, the increase must be made by the
group in advance. The reform group is autonomous and produces more than a few
things. The Skrom group is associated with many practices, such as due diligence
estimates, accumulation of dashes, estimation of the element cache list. In addition to
exercising, the group can be included or expelled from the company. Depending on
the activities undertaken by the group of companies, fluctuations occur. The size of
the group is less likely to be higher than the growth group. It is possible that there is a
problem of coordination between colleagues and this process is clearly troubled.
Advancement Group is the highest of nineScream Ace has been accused of seeing that
the business continues to be scratched by Scrum. Scrum Ace is able to check the
progress of the job in the same way as the system. Skrom Ace has a close affiliation
with Advancement Group, Client and Administration. Skrom Ace can make
significant improvements to this process to enable the group to improve, improve
training and improve the group. Adds part of the administration to the AIS element

3.4.3 Scrum installation

Nervous programming is not a process or system of improvement; It's a lightweight

process, easy to understand and difficult to process, that can be used as part of a
complex breakthrough, but Scrum is a product upgrade process that can work better
with larger groups. small.

Scrum is viable in the field of self-discharge and joint ventures and joint efforts.

3.4.4 Break through the crash

Scrum uses different word spells between correspondence in the company. See Table
3 below.

Activity Description

Chicken---- Any one that has some enthusiasm for the undertaking yet have
no any formal Scrum duties and responsibility.

Step By Step Short meeting that each group held each day to check crafted by
Scrum each group part, check the work as indicated by the calendar and
plan for the following meeting.
Done///// In a run audit if something is accounted for as "Done" this
implies every one of the gatherings are commonly concurred
and something is finished by the association standard and rules.

Evaluated.work This is the time when the colleague gauges time left to finish the

.task.Remaining errand. This estimation is done toward the finish of consistently

when the group individuals are occupied on run build-up
errands.

Increment.123 Toward the finish of a run when the advancement group builds
up an item with usefulness and that can be shippable to the item
proprietor partners

Sprint3. Run is emphasis or one can state rehashing cycle of work that
can deliver an addition of the advancement item. The span of the
run is a

least of one week and a greatest of a month

Pig32. exercising one part out of the three Scrum parts Group, Scrum
Ace and

Item Proprietor.
Product23. Rundown of prerequisites that has been given need and
Backlog111 apportioned particular time Product for finish, the rundown can
be changed by business needs, or Backlog technology changes
and so forth.

Product1 Contains the useful and non-utilitarian prerequisites, issues that

Backlog.Thing have

Product been given need as indicated by the business needs and

conditions and is assessed. The exactness of estimations depends
of the need of the Item Overabundance Items Backlog Thing.

Item*-Owner The Item Proprietor is the individual in charge of making the

undertaking and its subsequent item intriguing to everybody in
the group.

Scrum3+ A component in the sport of rugby for taking care of business an

out-of-take care of business again into play.
Scrum-Master A individual who is in charge of the best possible usage of the
Scrum

process and usage of its greatest advantages

DashiBacklog It contains a rundown of undertakings for finishing a Run. Each

of the errand has a few particular time and somebody in the
group is in charge of the undertaking.

SprintbBacklog A errand characterized by the colleague to transform the Item

Task Excess things into a functional item.

Sprint*Planning meeting the arranging and estimations for the entire Run is done.
The meeting is conveyed in two parts each of four hours. In the
Meeting initial four hours the Item Proprietor exhibits the need of the
Item overabundance and in the second four hours the Group
designs how to finish the run.

Sprint---- It's around three hours meeting encouraged by the Scrum Ace
toward the finish of the dash and it is chosen what ought to be
.Retrospective changed or evacuated so that the next dash ought to be gainful.

Meeting
Sprint+Review+ It's a four hours meeting toward the finish of each Run where the
Meeting group

cooperation with Item Proprietor and the partners and talk about
the

Completed Run after the show of the Item Accumulation things.

It is

additionally talked about of what ought to be improved the

situation the following Run

Stakeholder-9 Anyone influenced from the undertaking is a partner, might be

somebody intrigued in the result of the undertaking

Team// A efficient gathering of gifted individuals in charge of the

overseeing

themselves to build up the item effectively and finish every one

of the Dashes

Time.2Box It's a particular timeframe that can't be stretched out and the
work is to be finished inside that particular time.
 Table 3:Terminologies used in Scrum Communications

The most important sentences were used as part of the correspondence between
Scrum colleagues. Each member of the Scrum group is one of those people who
understand words rather than words directly. By using these words in correspondence,
the time can be reduced and understanding can improve.

3.5 Together, the process (RUP) has been assembled

Appropriate Binding Process (ORP) is a product design process that recognizes

product improvement processes in the context of many companies and associations.
RUPs have used Bengal's (UML) offering together for different models that are used
as part of the reform process. Product associations can use ORs according to their
needs (Crookton, 2002)

As Ambler (2014) said that many people believe that there is a huge difference
between coordination and RUP, but it is completely off-base. RUP could be better if
you use it.It's possible that RUP can be used. Period of push for a maximum period of
one month. Concentration work should focus on programming. Use methods that can
affect the product of great capacity, such as before correction, coding traditions and
refactoring There should be a lot of attention and a lot of coordination. Include trading
partners, information experts and the quality of quality certification between reforms,
more Rapp can be expected to simplify

According to RUP, the tool is used to create tasks and to exclude responsibilities in
the advancement process. The main point of RUP is to meet the needs of customers

In another survey, OR was marked as a recurring progression process, in which each

of the following individuals has a commitment and an obligation to the client.
Additional requirements of the client as mentioned in the RUP system, which consists
of three primary sections: practice, part and ancient rarities. In all the functions, there
are all these three sections in the miscellaneous behavior which are based on the idea
of the enterprise. Each company has a collection of characters on the screen, and each
artist performs a particular task or exercise. In RUP programming, more than eighty
archaeologists, there are one hundred and fifty exercises and forty-five curved
sections.

3.5.1 Form process procedures

As stated in RUP, it can be divided into four phases, start, development, development
and progress. The fruits of each step begin the next phase when the previous step

Figure 8: RUP phases and workflows

Under RUP classes, the appropriate limit is explained to use together.

Four OR periods are the beginning stage, the stage of development, the stage of
development and the stage of change.

The course reflects the important date of the turn of the business between the start of
the work for the case of the firm that was created above the performance criteria, the
risk assessment, the valuation of the assets and the continuation from the program.
Between the beginning stage here in this stage the characters on the screen have been
distinguished and their structure is characteristic of their cooperation.

The use of vision, the original course file, the introductory case (20% finishing), the
danger case design, the design work, and many are starting to present many models of
gold.

The reference point of the original stage is the purpose of the life cycle.

One of the necessary internships is the collaboration phase, between this level, all the
engineering of the structure is produced. The problem is broken and a business has
been created. In this phase, the most used and recognized artists have been recognized
and painted. The engineering of the structure is produced and the model is made. To
ensure the necessary conditions between this level, the conditions, the engineering
and the work design stabilize.

Results of the development stage showcase (80% completed), Necessities,

programming illustration design, engineering models (execution) to review the
business case and risk list, tasks are designed using manuals client.

The real point of reference is engineering at the level of life.

The third phase is the development stage in which there is an application, called an
additional assembly phase. This is the main focus on the treatment of the property, the
cost of articles and articles in a timely manner. During this step, the test speed (alpha,
beta and various tests) is maintained as fast as possible.
The results of the development training include current articles, client manuals, and
exit documents.

The reference question for the development internship is the startup operation
capability

The fourth step is the stage in light of customer requirements, in which the article was
developed at the end of the client. Guides and support groups and clients prepare and
unload articles in advertising.

The result of the progression stage is the final arrival of the article.

The real success of the change phase is the last element

3.5.2 RUP Measurement of the work process

Where OR is considered one of two types of work processes, namely one of the
following:

In Figure 8, the work process, the work process, the work process, the work process,
and the work process.

Workflow process and work center process

Show a product Sie business engineers exceptional among other centers of work
processes and engineers that typical RUP through the offer through a second do (case)
and traceability Between companies and the model of programming. Boxes for
commercial use are registered in the company and are used as a contribution to the
legitimate promotion of the product.

What is the framework for explaining the main purpose of the work process
requirement and how to agree on the terms of the client and the engineers.
Prerequisites (useful utilities) are prepared using utility questions; These requirements
are then made and stored, in the additional details are not practical.
Approval of the framework for the implementation of the framework framework
framework between the review and the work process. Summary review and planning
work is done in the process.

The following components and the following are in use: An advantage of RUP is the
success of the segment and it creates the structure from top to bottom.

Between the repeated approach of the test process, which is the reason behind the
problems and the result of this problem. The tests are used for tests, tests and tests.
Communication is examined in the test work process and the coordination of the
following is confirmed that they work properly in the form of structure. The
requirements for which the framework was prepared and consulted are updated.
Defects are recognized between the test work process and the warranty before the
product is organized.

Compared to alternative work processes, there are points of interest in the systematic
work process. The product is unloaded remotely between the organization's work
process. Primary practice, setting up and customer support for the process of sending
and receiving products From time to time, the process is underway

Business Administration work process for the main part of the practical advancement
process. Practical principle organizing organization rules to practice managing risks
between work

Various old rarities are created by associates in the business, establishing and
changing the administrative work process that can be controlled by many people. At
the same time refreshing, moderate warning and many variations should not be in
dispute between these antiques. The process of this work was described as follows:
How to work in a parallel reform, how to do it for different places, and how to
computerize the construction process The installation and the change are a review in
the work of administration, When and by whom an old rarity changes
Natural work process for the advancement of equipment and processes for the
advancement group. The Advantage Pack (DK) provides rules, tools, and layouts that
are critical to the process.

There are too many chakras in the three stages of Rupa (expansion, development and
change).

Each of these courses can have at least two validations for their finishing

3.5.3 Best Practices of RUP

RUPs used in best practices for product improvement and best practices are known
for approved processes. RUP gives several tools, rules, layouts and so on.

In order to broaden the company's product realization, the product business is

understandable about certain practices that can be used for spectacular, financially-
inclusive solid time businesses. They call these practices the best practices

There are six fixed procedures for programming enhancements that grow iteratively,
section-based engineering, quality control, change control, need control, and scene
display.

Spry is based on improved programming; There are a few cycles inside the company
in the light walking process. In the repetition advancement configuration, the basic
idea is weak, as at least the test and in the meantime, the engineer and the client can
actually advance the screen in each loudness. The parts-based design separates useful
and reusable for the most part. Between the parts-based design, the structure has been
divided into several substructures and frames. The nature of the framework was
confirmed and the practical and non-useful requirements of the framework were
approved. The nature of the structure was confirmed in each cycle. The necessary
conditions between the progress of recruitments between all aspects of requirements,
planning and execution can be exchanged at any level between the trajectory of the
control cycle and the needs of the screen by keeping to mind that changes can change.
Can reallocate property, set requirements and exchange in emphasis and work with
understanding. The need to monitor how to obtain the necessary conditions, registers
and requirements describe these needs (practical and not useful) and these
requirements are mandatory. Graphic illustration and operation of visual display
engineering and frame segments gives. The visual representation of the frame is also
helpful in the expansion and setting of anything else.

3.5.4 Share and responsibility in RUP

OR is an iterative process of progression that can be separated into specific tasks and
obligations within the association. These parts and responsibilities depend on the
work done in the context of reflection and associations. Various on-screen characters
occur in the company. As far as parts and tasks in RUP are concerned, many analysts
have different ideas

ORs leave parts of the operation and there are about thirty parties. The basic parts are
Planner, Modeler, Setup Director, Outline Analyzer and so on

The review between the middle and the other is about 39 units that can be divided into
two classes of fundamental (13 shares) and trivial shares (26 shares) of RUP. These
useless parts do not mean that they are not important but cannot be left with them.
These parts can also be mixed. In Figure 9, examinations are observed between the
parts of ORs.
Figure 9: Comparison between RUP roles
In the RUP Figure group, the RUP group is one of the largest groups in the world. In
the developed model, parts of expert framework, programming model, user interface
manufacturer, race engineer and database provider have been developed. The duty of
these parts is mapped to the following residual parts.

3.5.5 RUP ease of use

Level Boyed can be obtained through the process set up by the associations. As a
general rule RUP can be used in the context of many organizations with some changes
in its process (adjustment)

ORs can be used as part of the small business cycle, and can be used in larger work
with larger groups and long article cycles. The OR process is effective in any job or
less or large. In this case, the third and fourth searches were clarified.
4 Agile. techniques in Programming Improvement

Due to the massive development of e-commerce (web-based enterprise) and web

accessibility, the implementation of each business is implemented to meet the needs
of businesses and businesses. Innovation in the aggressive market is growing at a fast
pace. Between the organizations, high rivalry has made a test to give information on
time and expense plans for product organizations. It is important to be aware that
professional organizations need to change the light on the fact that companies are
turning into business processes.

The development of the first stage of the project is not enough to advance the
programming model

To combat problems related to programming and market development, it is necessary

to make changes in the market. Agile strategies have been acquired that can be used to
reduce these problems, agile strategies, focusing on the most important features, are
exceptionally simple and delivering messages to the product. The necessary
conditions in the effective strategy are very favorable and can apply the necessary
changes in any phase of the improvement phase.

4.1 Difference between custom and temporary

programming enhancements

As has been indicated, there are many contradictions between the progress of writing
and the usual progress of programming. Customary Advancement uses a patented
approach to enhance programs and effective enhancements, using a versatile
programming progression technology. Advancing into the framework structure for the
development of a framework development framework (SDLC), when in effective
tactics. SDLC is exceptionally difficult and expensive, while the enhanced strategy
evolves at any stage of the improvement phase.

Point-to-point paradoxes are given in Table 4 between customary and coordinated

programming progress.
Activity+- Traditional.Development Agile.Improvement

Finish specifiable Programming quality is high,

frameworks, created by little groups by
utilizing the rule of change
Essential unsurprising and created with in configuration,getting
Hypothesis nitty gritty arranging criticism

also, testing after criticism

and make change.

Administration
Command.and.control Leadership.and.Joint.effort
Style

Learning
Explicit201. Tacit15.
Management

Communication.3 Formal 12. Informal125.

Evolutionary-conveyance
Improvement Cycle show display
Model (Waterfall,.winding etc.)

Bureaucratic, high Flexible and participative,

Hierarchical
formalized, targeting vast energizes social
structure organization collaboration, focusing on
little and medium
associations.

Permanent control on
Difficult arranging and strict
Troublesome and late testing
Quality control control. Troublesome and
design and arrangements,
late testing.
changeless testing

Interactive information
Client.requirements Detailed and characterized
before coding

Cost.of.restart High.+ Low03.

Advancement
Fixed Easily.variable
Direction

Testing. After coding is complete Every+emphasis

Involvement
Customer
Low.30. High032.0
 Nothing in particular Interpersonal abilities and
Extra capacities
basic knowledge of the
required from
Traditional Advancement business

Developer
Agile model

Size.of.project Large scale Low_and_medium scale

Oriented on design, with Agile, with cutting edge

some adequate capacities,
Developers.123 access to outer knowledge located and helpful

knowledgeable, helpful,
With access to learning,
Clients.2333 cooperative, agent and representative and enabled
empowered

Emergent, with quick

Requirements.22 Very steady, known in advan changes

Architecture11 Design for current and Design for current

 predictable necessities necessities

Not.Costly
Remodeling.0. Expensive

Group.Size Large group size Small group estimate

Venture.size Large venture size Small venture measure

Essential.objectives
Safety.High Quick.esteem

Table 4:Difference between agile and traditional software development.

4.2 Project achievement or disappointment rate of

Customary and Lithe undertakings

The achievement or disappointment of venture relies upon certain authoritative

achievement criteria, an undertaking is thought to be effective on the off chance that
it is conveyed on time and it meets the achievement criteria of the association. A task
is said to be tested on the off chance that it is conveyed on time however it's not as
indicated by the achievement criteria scope of the association; a venture is said to be
 fizzled if the group can't convey the product arrangement. In Table 5 achievement
and disappointment rates of nimble and conventional activities are displayed.

Projects. Successful. Challenged. Fail.

12.
Agile. 60. % 28. % %

17.
Traditional. 47. % 36. % %

Table 5::Success and failure rates of Agile and Traditional projects.

Success and failure rates of Agile and Traditional projects.

Table enabled 6 indicates that success is greater than that. The achievement rate is
75% The work of customary enterprises is more than the rate of desperation, qualified
companies. The desperation rate is 12% and the despair rate is 12%. About 36% of
traditional work is done, more than 28%.

The transaction is significantly higher than the average number of businesses in the
company's success rate. The success rate of light walking operations is higher than
normal performance and deception rates.
 Projects.11 Successful.123 Challenged.00 Fail.12

Agile.00 42.00% 49.00 % 9.00 %

Traditional.11 14.00% 57.00 % 29.00%

Table 6::Comparison rate of Agile and Traditional project.

Comparison rate of Agile and Traditional project.

As the rate of desperation in the world is falling because the opposition is growing in
business. Table 7 shows a ten-year observation of overall success, disappointment and
testing.

Year.0 Successfully Challenging Failure

2010.aa 33.00 % 41.00 % 26.00%

2008.aa 32.00 % 44.00 % 24.00%

2006aaa 35.00% 46.00% 19.00%

2004asa 29.00% 53.00% 18.00%

2002asads 34.00% 51.00% 15.00%

2000asa 28.00% 49.00% 23.00%

1998sas 26.00% 46.00% 28.00%

 1996.00 27.00% 33.00% 40.00%

1994.00 16.00% 53.00% 31.00%

Table 7:Achievement and Disappointment of Worldwide Ventures.

The main reason for the business is the direct result of an excessive amount of
anything else. As shown in Figure 10, 7% of presets are commonly used, in which
16% of needs are used, 65% of needs are never used by any means of fiction. (See
Figure 10)
 Figure 10: Requirement categories

Affirms that the success rate of qualified technology in higher advancement strategies
See photo 11
 Figure 11: Agile project success rate.

The completion rate of completed enterprises is about 72% and about 63% of
traditional activities. The ownership rate of information products is 63% and the
number of offshoring companies is 43%.
4.3 Success factor in the coordinated enterprise

Lightweight technology considers an important part of product realization, which is

spreading in this aggressive business situation. The realization of well-known
strategies is due to certain factors that were not used in the techniques of upgrading
previous programming (traditional techniques) or that were not yet used with the
mind.

Focus on certain variables to achieve coordinated programming improvements. Low

carrier schedule, increased degree of profitability (return on investment), increased
ability to expand with existing customer requirements, change in customer
prerequisite, expanded optimization capability with expanded business process.

The above progress factors reflect some areas of achievement of any business, for
example, short time, cost reduction, and broad quality achievement factors are divided
into two parts, the theoretical achievement of factors and Factors of the individual The
factors are given in Figure 12.
 Figure 12: Guessed achievement factors

Hierarchical elements include customer issues. Customer-related issues include

consumer loyalty goals, joint customer efforts, customer duties, customer support and
consumer loyalty, and low programming progress. Throughout the customer
improvement process is accessible, the customer is always moving forward and
improving the customer experience. In the late correction process, the time is as easy
as the progress group. Thanks to the coordinated efforts, there is a close
correspondence in the group. The diffusion of the group in the progression of agile
programming is centered. Well, there is no connection between them and they can
speak effectively about the problems. The unified group structure is an extraordinary
factor among the other achievements of the agile technique. The simple estimation of
the group in simple strategy is simple and simple: in this case, the adventure on the
ground is enormous, it is important that the group be divided into small groups in
order that the correspondence is simple. The small group's estimate in the company is
one of the achievements in the publication of light-Python programming.

Due to the corporate culture in the accomplished programming, the contribution of

customers and customers is a common effort, the official culture should be versatile
for changes. Other achievements are compared in the technical and technical aspects
of corporate culture. There is an extraordinary understanding and control among the
most essential achievements in the system and the control skills. Collective techniques
are prepared for each movement in the group meeting and this system is properly
controlled and controlled.

Factors of the general population include the qualification in playful techniques.

Colleagues must learn enough about the inputs and tools of their fields, which they
use in the context of the business. Colleagues have a great relational and relational
capacity and this is one of the key elements of spry programming development. The
personal qualities in the LTTE's strategies are well-informed about self-reliance and
autonomy. Correspondence and arrangement are among the most important elements
of progress in coordinated programming. In a light programming, the relationship
between colleagues and customers is very useful. In the agile technique, there is close
proximity between designers, operations, cylinders, customers and administration. In
the field of progress, social culture is practically like improving a culture in which the
association works. In the case where the general population in the life of the world is
connected to the world, they are simple, community-oriented and consider
responsibility for work. Working in such a culture is exceptionally productive. The
purpose of this study is to prepare and coordinate and improve understanding of this
topic. Colleagues know each other by sharing their data with each other

Closer to the point, some factors can be taken into account in effective programming
improvements. 4.3.1, 4.3.2, 4.3.3, 4.3.4 and 4.3.4
4.3.1 Prerequisites and Client inclusion

Requirements are laid down in skillful strategies and requirements are given at any
level of advancement and requirements are changed. In the light strategies collected
by the customer by the customer, paying attention to each of the requests of the
client's engineers and busy making the decision. Among the other causes of customer
support in the overall improvement of programming, carrying out agile projects is an
extraordinary one. The progress of this process is essential because of the progress
and progress of the process of progress and progress of the process. And in the next
cycle, a new pre-existing or changing thing can be balanced by a redefinition of
priorities according to the requirement. Due to the strong combination of customers in
the improvement process, customer and customer experience is high and low

4.3.2 Disable correspondence

The group estimate of companies in LTTE strategies is low and they are in close
contact with the customer. Therefore, there is a correspondence between colleagues
and customers and colleagues and they can not make this dynamic correspondence
between colleagues and customers is extremely important in creating the world's most
memorable consumer loyalty. Due to changing prerequisites among all high-weight
strategies, there is consistent correspondence throughout the cycle. He reduced
spending and time

In order to send messages for light walking, to understand, organize, organize, test
and execute programming, a proximity match is required for each step. The
intermediate and final steps required included three sub-courses in the churn cycle.
See photo 13
 Figure 13: Lithe correspondence cycle.

Figure 13, between the required level of the customer and the data provided by the
customer. At the intermediate level, the partners meet and talk about something else.
The progress group to the final level is looking at something else with the
customer.The primary importance of correspondence is given to the eyes for the white
board's eyes and the agile technologies have personal and individual discussions. See
Figure 14 below.
 Figure 14: The correspondence estimation of various methods

Demonstrate the adequacy of correspondence at different levels of correspondence

and correspondence in Figure 14. The viability of correspondence increases from
paper (frosted) to verbal, then from oral to video (hot).

4.3.3 Continuous incorporation and preliminary test

One of the main elements of the progression of the programming is tested in the field
of the valuation of the product, that this product is or not a product. An extension of
the programming increases the speed of programming, which is called the nonstop
mix, but it is indicated that it is usually. These mixtures are examined by a
mechanized form. Computerized texture Problems of participation in this process
decrease and the speed of advancement of the product increases.

4.3.4 Small discharge

Between light improvements, needs are needed. Some urgent things are needed and
they should be produced initially. Engineers have begun to think carefully about the
most urgent requirements and when they are finished, they give the product of the
product in order to profit and to enter the customers. Given a little discharge strategy,
the product is one of the high potential, the customer begins to take advantage of the
original product and it is not necessary. The product is on time because there is no
additional requirement, which can save a lot of time from the moment of
advancement.

In conjunction with the principle of convergence in the context of the design process,
it is important that the input.
5 Exchange and conclusions

5.1 Discussion

It is possible to discuss the subject of this article between this part of the general
essence of the principle. In this area, the manufacturer gives a complete picture of the
product improvement from Technological Development Technical Advancement
(SDLC) to new integrated programming correction strategies. Point of interest and
weaknesses of waterfall programming, agile and advanced coordination, for example
specific techniques, for example, extraordinary programs, drums and ORs were
discussed. Among the traditional and coordinated strategies have been said. Job
completion and the rate of despair are some examples of successful businesses in the
market.

The creation of the programming is a design control used for programming the
upgrades. Various organizations and associations need programming to maintain their
business and meet their expectations. In the early 1970s, product improvement
technology was used. In improving cascading programming, the phase is as follows:
The process is not complete until the social rehearsal product is ready. The problem of
stunt technology (which is a more important strategy than the last one). Similarly, the
waterfall was completed in the final phase of the progression process in the technical
test (unit test and frame test). Vehicles Traditional programming improvements are
extremely difficult and difficult to implement. There are many loads in the standard
correction of preferences, see Table 1

Web and e-business due to strong growth and a strong rivalry between the unions for
their business and is encouraged to increase their competitiveness in the light of
competition Thus, the faster conceivable programming associations is required.
business is constantly changing their business processes. To overcome each of these
problems, product organizations need as advanced programming as they can adapt to
changes and any progress may be required at any stage of product improvement.

The efficiency mechanism is very simple and focusing on the most essential
capabilities of the customer is to convey the message in an important way. In addition,
the conditions of use and configuration are exceptionally adaptable and can be
modified at any stage of the advancement. There is less documentation in the game
techniques, a prototype is used and the strategies are repeated and the focus is on each
point (ie, test, combination test and so on) and further. Clever programming has great
potential

In this thesis, three playful strategies were considered. The process of each strategy is
clarified in the subtle elements, some parts of these strategies are specified and further
where each of these techniques can be used.

In this thesis, the difference between strategies and customs in section 4.1 of this
principle has been presented and clarified in the light of various research articles. The
performance and disappointment of the techniques and techniques used in this study
were examined.

5.2 Conclusion

An important part of the business is the connection to software and any type of
commercial programming. Coming out of fate, we are going to Day 30 day tahun on
this so there was not a lot of rivalry in business there and organizations were using
their old innovation and the satisfaction of their business had the necessary
conditions. In comparison with the current circumstances where the company in the
world was not much, the product organizations were used for association purposes.
The company can be widely used (over several years) and the prerequisites there was
a significant number, and even the customers did not know they needed not
transmitted inside what matters companies and spending plan In a large proportion to
obtain customary programming improvement status has not been conducive to the
exchange, there is a connection hole has Between colleagues and customers, and
indeed colleagues Between, and settled a end-of-work plan-based programming
master plan, unclear cost estimates, and exchange Most of the extraordinary problems
and costly and tired failures were spent using standard improvement strategies.

Web and for organizations between the current situation due to the increase in e-
Business-of-the-main universal capital increase and use these organizations are due to
an exceptional rivalry Between the business organizations and why the
demonstrations As a result Innovation-driven business organizations will have to
evolve into a business model. These organizations need such programming that they
are adaptable as needed and Light cushion technology has been used in the
development of programming organizations and strategic strategies. I maintain that
the technical expertise is very effective and efficient, so there is no need to implement
it. There is a link between the customer and the designers, and further among the
engineers (colleagues). The product business is different in LTTE techniques

Emphasize Integrated technology products have been very adaptable to change the
conditions needed at any level in the advancement program, which is now the major
requirement of business worldwide. Is integrated in the product, in some cases,
coordinated strategies and no waste requirement is constantly combining and testing
in each phase of correction of the cycle due to the association of the customers in
phase of progress, and each bet within the framework of each type of product is used
by the product manufactured using spicy strategies, high efficiency, timely
information, and level of expenditure Yes, consumer loyalty was included.

Due to the use of procedures in the progression of programming, LTTE technology

offers high potential, which reduces the time and cost of programming creation. These
methods are a close joint effort, an adaptive framework and a programming
configuration, which are after the development of any phase of progress, continuous
incorporation and testing, short discharge, short work time and small group. business.

5.3 Future Study

Current theory is related to the relations and problems of customary and playful
techniques. What are the problems in advancing technological advancement and how
to use best practices using these light foot strategies. The theory focuses on the
contradictions between the traditional strategy (cascade) and the LTTE reform.

A similar report can be used as a part of the future, in which money is saved. The
information (requirements, new requirements, changing requirements, etc.) will be
given to the survey and the cost and time estimates will be improved for the
company's investigation and the item's design in light of the estimate of the survey.

The obligations of this thesis are as follows:

The theory of velocity is usual for the usual modular cascade programming and
coordinate strategies. Generally, the current thesis work has been constrained in the
context of the progress of the usual programming and spontaneous programming.
6 Refrences

1. Abrahamsson, P., Salo, O., Ronkainen, J., Warsta, J. (2002) ‘Agile

software development methods Review and analysis’, University of
Oulu, VTT Publications 478
2. Ahmad, F., Capretz, L.F. (2008) ‘Best practices of RUP in
software product line development’, International Conference on
Computer and Communication Engineering,IEEE Publication, PP: 1363 -
1366
3. Ambler, S. (2014) ‘Overcoming the Myths of IBM Rational Unified
Process (RUP) and Agile Development’ Available
at:http://www01.ibm.com/software/info/television/html/M649306B4750
2P68.html
4. Anderson, Beattie R., Beck, K. (1998) ‘Chrysler Goes to “Extreme” ’ ,
A case study, PP: 24-28
5. Awad, M.A. (2005) ‘A comparison between Agile and Traditional
Software Development Methodologies’, the university of Western
Australia
6. Bakal, R.M. , Althouse, J., Verma, P. (2012) ‘Continuous integration in
agile development: How agile methods, continuous integration, and test -
driven enhance designand development of complex systems’,
available at:
http://www.ibm.com/developerworks/rational/library/continuous -
integration-agile-development/continuous-integration-agile-
development-pdf.pdf
7. Bassil, Y. (2012) ‘A Simulation Model for the Waterfall Software
Development Life Cycle’, International Journal of Engineerin g &
Technology (iJET), ISSN: 2049-3444, Vol. 2, No. 5
8. Beck, K. (1999) ‘Extreme Programming Explained, Embrace Change’,
Addison Wesley
9. Bhalerao, S., Ingle, M. (2010) ‘Analyzing the modes of communication
in Agile Practices’, IEEE International Conference on Computer Science
and Information Technology, PP: 391-395
10. Bohem, B. (2002) ‘Get Ready for agile methods: with care’, Vol: 35,
IEEE Publication,PP: 64-69
11. Cao, L., Mohan, K., Peng Xu, Ramesh, B. (2004) ‘How Extreme does
Extreme Programming Have to be? Adapting XP Practices to Large-
scale Projects’, Proceedings of the 37th Hawaii International Conference
on System Sciences, IEEE Publication
12. Czarnacka-Chrobot, B. (2010) ‘The Economic Importance of Business
Software Systems Size management’, Fifth International Conference on
Computing in the Global Information Technology, IEEE Publication,
PP: 293-299
13. Devi, V. (2013) ‘Traditional and Agile Methods: An Interpretation’
Available at:
https://www.scrumalliance.org/community/articles/2013/january/traditio
nal-and-agile-methods-an-interpretation
14. Denzin, N.K., Lincoln, Y. S. (2011). ‘The SAGE Hankbook of
Qualitative Research’, 4th edition, USA: Library of congress cataloging-
in-Publication Data. PP 8-9.
15. Del Maschi, V.F. , Spinola, M.M. , Costa, I.A. , Esteves, A.L. ,
Vendramel, W. (2007)
16. ‘Practical Experience in Customization of a Software Development
Process for Small Companies Based on RUP Processes and MSF’,
Portland international Center for
17. Management of Engineering and Technology, IEEE Conference
Publication,PP: 2440-2457
18. Dobb, D. (2010) ‘2010 It project s success Rates’
,Availableathttp://www.drdobbs.com/architecture-and-design/2010-it-
project-success-rates/226500046
19. Fowler, M., Highsmith, j. (2001) ‘The Agile Manifesto’ available at:
www.drdobbs.com/open-source/the-agile-manifesto/184414755
20. Guo, F., Xia, B., Xue, F. (2011) ‘Analysis of Software Processes and
Enhancement for RUP’,IEEE 2nd
International Conference on Software
engineering and Service Sciences, PP: 295-298
21. Holmstrom, H., Fitzgerald, B., Agerfalk, P., Conchuir, E. (2006) ‘Agile
practices reduce distance in global software development. Information
system development’, Vol 23, Issue 3, PP: 7-18
22. Hussain, Z., Lechner M., Milchrahm, H. , Shahzad, S., Slany, W. ,
Umgeher,M. (2008) ‘Optimizing Extreme Programming’, Proceedings
of the International Conference on Computer and Communication
Engineering, IEEE Publication, PP: 1052-1056
23. Hanakawa, N., Okura, K. (2004) ‘A project management support tool
using communication for agile software development’, 11th Asia -Pacific
Software Engineering Conference, IEEE Publication, PP: 316-323
24. Hasnain, E., Hall, T., Shepperd, M. (2013) ‘Using Experimental Games
to Understand Communication and trust in Agile Software Teams’,6 th
International Workshop on Cooperative and Human Aspects of Software
Engineering , IEEE Publication, PP: 117-120
25. Hayata, T., Han, J. (2011) ‘A Hybrid Model for IT Project with Scrum’,
IEEE international conference on Service Operation, Logistics, and
informatics, PP: 285-290
26. IMB White Paper, (2003) ‘Using the Rational Unified Process for
small projects:Expanding Upon eXtreme Programming’, Available
at:ftp://ftp.software.ibm.com/software/rational/web/whitepapers/200
3/tp183.pdf
27. Juric, Radmila, (2000) ‘Extreme Programming and its Development
Practices’, Information Technology Interfaces, proceedings of the 22nd
international conference, IEEE publication, PP: 97-104
28. Jacobson, I. , Booch, G. , Rumbaugh, J. (1999) ‘Unified Software
Development Process’ , Addison-Wesley
29. Kruchten, P. (2000) ‘The Rational Unified Process: An Introduction’,
Addison Wesley
30. Kohlbacher, M., Stelzmann, E., Maierhofer, S. (2011) ‘Do Agile
Software Development Practices Increase Customer Satisfaction in
System Engineering Projects?’, IEEE international Conference, PP: 168-
172
31. Kähkönen, T. , Abrahamsson, P. (2003) ‘Digging into the Fundamentals
of Extreme Programming building the Theoretical Base for Agile
Methods’ Proceedings of the 29th EUROMICRO Conference, IEEE
Publications, PP: 273-280
32. Kessel, C. (2013) ‘Software History: Waterfall – The Process That
Wasn’t Meant to Be’available at:
http://ig.obsglobal.com/2013/01/software-history-waterfall-the-process-
that-wasnt-meant-to-be
33. Keenan, F. (2004) ‘Agile Process Tailoring and probLem analYsis
(APTLY)’, 26 th
IEEE international Conference on Software
Engineering, PP: 45-47.
34. Korkala, M. , Abrahamsson, P. , Kyllonen, P. (2006) ’ A Case Study on
the Impact of Customer Communication on Defects in Agile Software
Development’, IEEE Agile Conference, PP: 11-88
35. Kruchten, P. (2002) ‘Tutorial: Introduction to the Rational Unified
Process’, Proceedings of the 24 th International Conference on Software
Engineering, IEEE Publication
36. Lagerberg, L., Skude, T. (2013) ‘The impact of agile principles and
practices on large-scale software development projects’, Linkopings
university, SE-581 83 Linkoping, Sweden
37. Livermore, J.A. (2007) ‘Factors that impact implementing an agile
software development methodology’, PP: 82 – 86 IEEE Conference
Publications
38. Lindstorm, L., Jeffries, R. (2004) ‘Extreme programming and agile
software development methodologies’, information systems
management, Vol 21, Issue 3
39. Lyndsay, J. (2007) ‘Testing in an agile environment’, Workroom
Production Ltd, software testing papers
40. Manjunath, K. N., Jagadeesh, J., yogeesh, M. (2013) ‘Achieving quality
product in a long term software product development in healthcare
application using Lean and Agile principles’, conference location
Kottayam, IEEE publication, PP: 26-34
41. Misra, S. C., Kumar, V., Kumar, U. (2009) ‘The success factors of agile
software development’ available at:
 http://ww1.ucmss.com/books/LFS/CSREA2006/SER5088.pdf Miller, G.
G. (2001) ‘The Characteristics of Agile Software Processes’, The 39 th
international Conference of Object Oriented Languages and Systems,
Santa, CA, IEEE publication
42. Maciaszek, L., Liong B.L. (2005) ‘Practical Software Engineering A
Case Study Approach’, England, PP: 5-25
43. Monteiro, P. , Borges, P. , Machado, R. , Ribeiro, P. (2012) ‘A reduced
set of RUP roles to small software development teams’, International
Conference on Software and System Process, IEEE Publication, PP:
190-199
44. Mary Land, ‘Legacy Transformation’,available at:
http://doit.maryland.gov/SDLC/Documents/Legacy%20Transformation.
pdf
45. Nawrocki, J., Jasinski, M., Walter, B., Wojciechowski, A. (2002)
‘Exreme programming modified: Embrace Requirements Engineering
Practices’, IEEE joint international conference on requirement
engineering, PP: 303-310
46. Paetsch, F., Eberlein, A., Maurer, F. (2003) ‘Requirements
Engineering and Agile
47. Software Development’, IEEE international workshops on enabling
technologies: infrastructure for collaborative Enterprises, Twelfth IEEE
International workshop, PP: 308-313
48. Pressman, R. S. (2001) ‘Software Engineering’, United States: Thomas
Casson, PP: 19-23
49. Royce, W. (1970) ‘Managing the Development of Large Software
Systems’, Proceedings of IEEE WESCON 26, PP: 1-9
50. Rising, L., Janoff, N.S. (2000) ‘The scrum software development
process for small teams’, IEEE Journals and Magazines, PP: 26-32
51. Rational Unified Process, (1998) ‘Best Practices for Software
Development Teams’, Available At:
https://www.ibm.com/developerworks/rational/library/content/03July/10
00/1251/1251_b estpractices_TP026B.pdf
52. Rico, D. (2013) ‘Agile Methods Cost of Quality: Benefits of Testing
Early & Often’, available at:
http://www.slideshare.net/davidfrico/rico12z
53. Ruparelia, N.B. (2010) ‘Software Development Lifecycle Models’
available at:dl.acm.org/ft_gateway.cfm?id=1764814&type=pdf
54. Sulemani, K. A., Nasir, M.N. (2009) ‘Communication Support to Scrum
Methodology in Offshore Development’, Available At:
hhttp://www.bth.se/fou/cuppsats.nsf/all/cf379a3854ec1378c1257685004
2c941/$file/Communication%20support%20to%20Scrum%20methodolo
gy%20in%20Offshore%20projec t.pdf
55. Sommerville, L. (2011) ‘Software Engineering’, United States:
Edwards Brothers. PP:27-36
56. Salo, O., Abrahamsson, P. (2008) ‘Agile methods in European
embedded software development organizations: a survey on the actual
use and usefulness of Extreme Programming and Scrum’, Institute of
Engineering and Technology, PP: 58-64
57. Schwaber, K., Beedle, M. (2002) ‘Agile Software Development with
Scrum’, Upper Saddle River. NJ, Prentice-Hall
58. Schwaber, K., Sutherland, J. (2013) ‘The Definitive Guide to Scrum:
The Rules of the Game’,available at:
http://www.academia.edu/8370895/The_Scrum_Guide_The_Definitive_
Guide_to_Scrum _The_Rules_of_the_Game
59. Stoica, M., Mircea, M., Gkilic-Micu, B. (2013) ‘Software
Development: Agile vs.Traditional’, Informatica Economic , vol. 17
PP: 64-76
60. Sommerville, L. (2007) ‘Software Engineering’, 8 th edition, PP: 6-9
61. Stolberg, S. (2009) ‘Enabling Agile Testing Through Continuous
Integration’, Agile Conference, IEEE Publication, PP: 369-374
62. Wang Y., Sang, D., Xie, W. (2009) ‘Analysis of Agile Software
Development Methods from the View of Informationalization Supply
Chain Management’, 3 rd International Symposium on Intelligent
Information workshop , IEEE Conference Publication, PP: 219-222
63. Williams, L., Upchurch, R. (2001) ‘Extreme Programming for software
engineering education?’, 31st Annual IEEE Frontier in Education
Conference, PP: 12-17, Vol. 1
64. Xiaohua, W., Zhi, W., Ming, Z. (2008) ‘The Relationship between
Developers and Customers in Agile Methodology’, International
Conference on Computer Science and Information Technology, IEEE
Publication, PP: 566-572