Model Driven Development With Uml

By Author: Sherry Roberts
Total Articles: 573

Model Driven Development with UML
Model-driven development is an approach used in representing software development life cycle as a modeling and model transformation activities (Software Engineering Competence Center, 2013). MDD’s purpose of introduction was to move the focus of developers from pure coding t analysis as well as making system development independent of the system development platform. It allows a system model to have a transformation to achieve the desired programming language on the needed particular platform. That leads to better portability and interoperability. We can also refer to the methodology as a model-driven software development or model-driven architecture (Rouse, 2007).
Scope creep
While MDD is an increasingly popular software development approach, the impact it has on the development process in large scale in the industrial practice is not yet clear (Heijstek & Chaudron, 2010). From the research conducted by the two, they discovered that scope creep is more likely to occur whereby late changes take place with a call for extensive rework.
Risk management
CORAS provide a framework for risk assessment of critical systems focusing on security in the computer systems (Houmb, n.d). It offers guideline on how to go about in providing model-based risk evaluation and mitigation. It allows for analysis and identification of risks at each process of iteration. One has the ability of choosing, designing, analyzing and composing part of a system or system as a whole according to a particular Risk Management ODP viewpoint for all iterations. That allows early risk identification and mitigation of risks in the software development.
 
Integrating a Development Model(s) into a Project Management Plan
Project management and project planning are essential to a project. Most of the projects have complicated dependencies regarding the tasks to accomplish, that the less experienced project managers always underestimate. Well-defined development process that is repeatable is one of the building blocks of a successful project (Gnatz et al., n.d). The model-driven development with UML ease project planning by offering a model of clear milestones, description of activities to perform in and the noting down of all activities to carry out in a development project. In the model-driven development with UML, every project plan should adopt development model. The types include descriptions and formal specifications that make the project process with a project plan obvious and straight forward.
Ethics and the Systems Analyst
The system analyst in model-driven development has a task to inspect the values in the software and the graphic user interface so as to realize the design of the system (Adman, 2000). All the models drawn have to adhere to the user specifications and needs that are acceptable according to the code of ethics.
Observational fact-finding
In model-driven development, observational fact-finding includes seeing the system in action to get additional perspective and a better understanding of system procedures. From the findings, you are able to create models that can best solve the problem at hand. You are able to use a model-based development technique that is most appropriate for that situation in thwarting the problem that exists with the current system as observed.
 
Fact Finding using Surveys
The technique of fact finding as applied in the model-driven development involves developing questionnaires on the current information workflows and UMLs. The users of the system or the staff are the ones to fill the questionnaire after which they return it to the researcher. The method is not reliable as the some of the stakeholders may not provide the required information or they may be busy and thus ignore the questionnaire. It should have the supplement of other fact finding techniques such as observation.
Use Cases
Use cases in model-driven development are UML element for capturing the requirements of a system (Sparx Systems.com, 2010). Each UML element represents a user’s goal when interacting with the system. The scenario below shows the use case diagram in a bank ATM system. ATM banking system

Customer
Choosing Information Technology projects
You first of all do an overview of the possible projects for Information technology. Then next you do the envisioning whereby its goal is to identify the scope of the system and architecture for addressing it. You carry out the initial requirements modeling where you identify some high-level requirements and the extent of the release (your intention for the new system). You then develop the initial architecture modeling, defining the design which has good chance of working. You do the iteration modeling followed by model storming where the team members meet and share opinions, then you then do the coding.
 
System analysis data modeling
Data modeling is a description of how the data should be useful to meet the requirements given by the end user (Mallikaarachchi, n.d). To carry systems analysis data modeling, you start with analyzing the situation. You gather the requirements in the process and then you design a proper data model.
Preventing project failure
• You should target all the goals of model-driven development.
• Only use one modeling dimension that fulfills the objective of model development.
• Focus on generation of new artifacts as software systems are always changing.
• Use the general purpose language like UML that keeps the focus on the goal has usage for.
• Not testing the model as this is cumbersome art the model level.

 
References

Adman, P. (2000). Journal of information technology, 15(): 39-51.
Gnarz, M. et al. (n.d) Towards an integration of process modeling and project planning.
Heijstek, W. & Chaudron, M. (2010). The impact of model driven development on the software architecture process.
Houmb, S. (n.d).
Mallikaarachchi, V. (n.d). Information systems analysis.
Software Engineering Competence Center (2013). Getting Started with Model Driven Development and Domain Specific Modeling.
Sparx Systemes.com (2010). Writing use case scenarios for model driven development.

Carolyn Morgan is the author of this paper. A senior editor at Melda Research in 24 hour custom essay. if you need a similar paper you can place your order for a custom research paper from already written essay.

Author is associated with MeldaResearch.Com which is a global Custom Essay Writing and Term Paper Writing Company. If you would like help in Research Papers and Term Paper Help you can visit Custom Writing Service