软件开发中的架构步骤 [英] Architectual steps in Software Development

问题描述

我有一个非常基本的问题。说，我将构建一个软件解决方案。我必须在项目的总生命周期内了解UML图。在项目的生命周期中，UML图的确切顺序应该是什么？

此外，使用的是哪些不同的模型（域模型，数据模型等），  在构建软件时？如果我遵循这种建模方法，我是否需要再使用UML？

问候

ronit_rc

解决方案

Hello romit_rc，

UML图总是有助于沟通您的设计。与UML相比，域和数据模型是高级模型。因为在域模型中，您可以设计业务域的元素，例如交易。这些元素没有
来匹配类和东西。 

这里有UML给你的帮助。您可以在UML类图表等中设计域的元素。在那里，您可以使用依赖项，函数等对真实类进行建模。通过这个图表，您可以轻松地看到"大图"。

另一方面，数据模型描述了如何在SQL中存储数据如何在SQL中构建和命名表数据库以及关键字段，索引，约束等等。 UML可以帮助你。

在我看来，最有用的UML图是用于建模和设计类的类图，以及用例来展示用户如何与系统交互以及您的应用程序中发生了什么用例非常适合与客户讨论worflows
和任务，以确保你所说的相同。

UML有很多图表所以选择适合你的场景或者客户需求。

希望有帮助，

问候

本杰明

Hi,

I have a very basic question. Say, I am going to architect a software solution. I have to go throgh the UML diagrams in the total lifetime of the project. What should be exact sequence of UML diagrams in the life time of the project?

Also, what are different models (Domain model, Data model etc.),  which are used while architecting a Software? If I follow the this modelling approach, should I require to use UML any more ?

Regards

ronit_rc

解决方案

Hello romit_rc,

UML diagrams are always helpful to communicate what your design is. Domain and Data models are High-Level Models compared to UML. Because in a Domain Modle you desgin the Elements of your Business Domain like Trading for example. These elements don't have to match classes and stuff. 

Here comes UML to your help. You Design the elements of your Domain in UML Class Diagramms or the like. There you model the real classes with thier dependencies, functions and so on. With this diagramm you can easily see the "big picture".

The Data Model on the other hand describes how you store your data in example how you build and name your tables in the SQL Database and what are the key fields, indexes, constraints and so on. UML can help you here to.

In my opinion the most usefull UML Diagrams are the Class Diagrams for Modeling and Designing your classes and the Use-Cases to show how the Users interact with your system and what happens inside your Application. Use Cases are great to discuss worflows and tasks with your customer to make sure you are talking about the same.

UML has many Diagrams so pick the ones suitable for your scenarios or customer needs.

Hope that helpds,

Regards

Benjamin

这篇关于软件开发中的架构步骤的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！