Professional Documents
Culture Documents
Overview
Introduction to traditional and Agile
Methodologies
Introduction to Dual Application Model
Physical Application
Proposed frameworks and tools
Advantages and Disadvantages
Conclusion
Dual Application Model for Agile Software
Engineering
Introduction
Software development is problem solving.
Software
Development
Any Methodology
Any Domain
Any problem
Requireme
nts
Analysis
Design
Dual Application Model for Agile Software
Engineering
Traditional Software
Engineering
Traditional Software
Engineering
Disadvantages of Agile
In developing the software quickly and continuously
developers totally forget about the nonfunctional
requirements.
Speed
Persistence
Ease of use
Reliability
Load balancing (for servers)
Hardware or software Limitations
Dual Application Model for Agile Software
Engineering
Physical Application
10
11
Logical Application
( Domain experts or product
owners )
12
Physical Application(for
software developers)
Design and develop the functional requirements or
visible functionalities.
The decisions made in Logical Application becomes
inputs for the development of Physical Application.
Develop functionalities such that Logical Application
aims are met.
Develop a loosely coupled structure such that Logical
Application features can be tested individually in each
module
Consider all the non functional requirements
Application Model for Agile Software
Developer is expertDualhere
Engineering
not the product owners
13
14
Disadvantages of DAM
Approach
Takes more time then Agile and less time than
Traditional approach or waterfall approach
Need Expertise in making decisions for better
understand and estimation of the non
functional requirements
Need Skilled software developers to provide
quality and adapt to changes
Dual Application Model for Agile Software
Engineering
15
Thank you !!
16