Case Study 1: Generative Software Development

Case Study 1 rich Software schooling Advanced Software Engineering CIS 518 February 17, 2013 Case Study 1 reproductive Software Development Generative software victimization is a victimisation that permits crossways to be produced automatically through different specifications. This type of development happens in two phases the first phase contain of the domain engineers developing the product down to generating the software mechanisms. Once development is completed, then each respective(prenominal) product is produced.The normal software development mental process would normally consist of some(prenominal) different specimens that have a particular set of labor movement that have to be set forth during a certain lodge during the process. The software development process happens over a series of activities and dep fetch uping on the development model go out determine what activities will take blank at every given time during the process verse the Generative software de velopment happens in two phases with specifications that are already unyielding at the start of the development.Developing procreative software would benefit an agreement beca utilise this allows for automation to software development. Many companies develop software still it is so generic and takes intense processes where the whole software is based on coding from ice which scum bag be possibly be use by any software. With the use of languages like FORTRAN and C will have less of an allude of the software type and the length and hurrying of the development will not be effected (Iseger, 2010). Moving toward automation will give developers more than room to come up with software solutions and the complier with automatically produce overturn assemblers.This would streamline the organizations software with less downtime, easier maintenance and convert everything to an change system. With the use of generative software development would save developers time in the end from h aving to redevelop codes from scratch which risk defects because of incorrect coding etc. The challenges that would be faced with implementing the generative software development process in organization would be to en surely that all software and systems could be integrated and automated without any delays or downtime.There would also be a problem with miserliness old entropy that is not used any longer redemptive and archiving information without the loss of any entropy during the transfer. Making sure that the development team understands the new process and how the implementation will take place. These challenges will be easy to overcome first thing would be to ladder as much as possible before implementation to fork out and catch any errors that may come up and make sure all of the developers are using and coding the new application with the desire language that was chosen for the application.Also having a back place to store the selective information before integrating t he data so that just in issue the data is lost during the implementation there is a back-up location to assenting any of the organizations data. Developer will had had several training sessions on the new process and there will be at least three see a week during implementation to ensure everyone is on the same varlet and to make sure that the process is running smoothly to have a successful implementation.The generative software development process might be applied to an organizations development process to quickly automate the system and arrive at a streamline of applications that work and can be integrated without several phases to follow before implementation can occur. This can be used for organizations that are looking to automate all of their data and system applications to emergence productivity enhance the security, provide data back up and data storage.The organization can use the Domain Specific Modelling, which is an approach that applies generative programming in o rder to improve the software applications development quality and boost the developer productivity. The move towards 3GL is the key to achieving 400% productivity (Iseger, 2010). The first timber to the use of DSM is to identify the solution and come up with a instance by using critical thinking and relating the problem to the domain. However, the use of a UML is most commonly used to provide a full model solution.Creating a visual depiction of the application model provides a gloomful print of the software application which programmers can use these specifications but immediately in the programming language. When creating the application the use of programming concepts by rearing the level of abstractions will help with developing the system concept. The Organization can create the system specifications by using the concepts and rules based on the societys products produced. Creating the application in the concept of using domains verse classes enhances the applications speed and makes it much easier to develop.This will allow the application to be more sleek to the data and make it easier program as a whole. Creating classes all of the data has to somehow link together for the classes to retrieve the correct data but the use of DSM will eliminate that. References Iseger, M. (2010, July 23). Domain-specific modeling for generative software development. Retrieved from http//www. developerfusion. com/ article/84844/domainspecific-modeling-for-generative-software-development/ Lawerence Pfleeger, S. (2010). Software engineering. (4th ed. ). Upper Saddle River, NJ Pearson.