You are on page 1of 16

Dual Application Model

for Agile Software


Engineering
-Adel Al Sulami
Texas A&M University Corpus Christi

Dual Application Model


for Agile Software
Engineering
Presented in 47th Hawaii International
Conference on System Science
Appeared in IEEE 2014
By Ashley Aitken
School of Information Systems, Curtin
University of Technology
Dual Application Model for Agile Software
Engineering

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

Dual Application Model for Agile Software


Engineering

Traditional Software
Engineering

Dual Application Model for Agile Software


Engineering

Agile Software Engineering

Dual Application Model for Agile 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

Introduction to Dual Application


Model

Introducing the Dual Application Model(DAM)

The problems of traditional and agile software methodologies are


handled
Its Mix of both traditional and agile
Best practices from both the traditional and agile are combined
Takes less time than traditional models and more time than agile
model
Dual Application Model for Agile Software
Engineering

Dual Application Model(DAM


approach)
Logical Application

Physical Application

Designing the user interface


Capturing non functional requirements or implementing
technologies
Designing test cases for all the non functional requirements like
memory, one tier or multi tier applications
Architecture for mobile or web or desktop or embedded platform

Deciding the technologies for building and maintenance


Implementing version control tools to track the changes
Using optimized algorithms while development to achieve the best
results.

Dual Application Model for Agile Software


Engineering

10

Automatic Generation and


Reverse Engineering of Models
in Analysis or Design

Dual Application Model for Agile Software


Engineering

11

Logical Application
( Domain experts or product
owners )

Domain solution through software product


Decision of requirements, languages, models are made
Consider only the functional requirements
Developing of blue print and making decisions on
blueprint
Modelling the requirements and developing test cases
Designing the interphases and all the abstract modules
required for physical Application
Dual Application Model for Agile Software
Engineering

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

Advantages of DAM Approach


Higher Quality when compared to agile or
Traditional methods
Over all productivity which out weights the
extra efforts
Developed software is consistent and
complete
Dual Application Model for Agile Software
Engineering

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 !!

Dual Application Model for Agile Software


Engineering

16

You might also like