Page 85 - DCAP405_SOFTWARE_ENGINEERING
P. 85

Software Engineering




                    Notes          prove it with code to show that your ideas actually work in practice and not just in theory Active
                                   stakeholder participation is critical to the success of your modeling efforts because your project
                                   stakeholders know what they want and can provide you with the feedback that you require. The
                                   principle of assume simplicity is a supported by the practices of creating simple content by
                                   focusing only on the aspects that you need to model and not attempting to creating a highly
                                   detailed model, depicting models simply via use of simple notations, and using the simplest
                                   tools to create your models. You travel light by single sourcing information, discarding temporary
                                   models and updating models only when it hurts. Communication is enabled by displaying
                                   models publicly, either on a wall or internal web site, through collective ownership of your
                                   project artifacts, through applying modeling standards, and by modeling with others. Your
                                   development efforts are greatly enhanced when you apply patterns gently. Because you often
                                   need to integrate with other systems, including legacy databases as well as web-based services,
                                   you will find that you need to formalize contract models with the owners of those systems. Read
                                   this article for a better understanding of how AM’s practices fit together.
                                   We would argue that AM is an agile approach to modeling, that at its core AM is simply a
                                   collection of practices that reflect the principles and values shared by many experienced software
                                   developers. With an Agile Model Driven Development (AMDD) (see Figure 5.4) approach you
                                   typically do just enough high-level modeling at the beginning of a project to understand the
                                   scope and potential architecture of the system, and then during development iterations you do
                                   modeling as part of your iteration planning activities and then take a just in time (JIT) model
                                   storming approach where you model for several minutes as a precursor to several hours of
                                   coding.


                                                What is MDD?
                                     Did u know?
                                     Model Driven Development (MDD) is an approach to software development where
                                     extensive models are created before source code is written.
                                                   Figure 5.4. Agile Model Driven Development (AMDD)





































          78                                LOVELY PROFESSIONAL UNIVERSITY
   80   81   82   83   84   85   86   87   88   89   90