After introducing agile approach in 2001, several agile methods were founded over the last decade. Agile values such as customer collaboration, embracing changes, iteration and frequent delivery, continuous integration, etc. motivate all software stakeholders to use these methods in their projects. The main issue is that for using these methods instead of traditional methods in software develop...

In order to improve the development process of highintegrity systems, using formal methods, we consider how agile techniques may influence the Event-B formal method, and how Event-B may be used in a development that uses an agile approach. To examine the crossover between Event-B and agile methods we review the Disciplined Agile Delivery approach (DAD). The DAD approach is inspired by many stat...

Agile software development processes are best applied to small teams on small to medium sized projects. Scaling agile methodologies is desired in order to bring the benefits of agile to larger, more complex projects. One way to scale agile methods is via an architecture-centric approach, in which a project is divided into smaller modules on which sub teams can use agile effectively. However, a ...

maintenance is one of the systems which can play an essential role in the success of manufacturing and services systems. one of the most maintenance innovative approaches is agile maintenance. based on this approach, organizations integrate maintenance concepts with agility features such as: flexibility, agile and fast move, etc and also are trying to provide one hundred percent preparing equip...

Agile Model Driven Development (Agile MDD) is an approach that aims to combine Agile development and Model Driven Development (MDD). It is the intention of our research to analyse the impact and the challenges of combining Agile and MDD and try to improve this approach by increasing its adaptability by proposing a framework that facilitate Agile and MDD. This includes essential procedures, reco...

In this paper, we present a pattern-based software development method that preserves usability and security quality characteristics using a role-driven mapping of requirements analysis documents to architectural design artifacts. The quality characteristics usability and security are captured using specialized problem frames, which are patterns that serve to structure, characterize, and analyze...

While classical software engineering dictums separate the development of a system’s requirements from its design, practice has largely shown this to be either impractical or naive. Much of the design of large software-dependent systems comes from prior systems, and that knowledge affects the requirements for new systems. Even if prior systems do not directly determine new system’s requirements,...