Modeling chicken soup (1)

zhaozj2021-02-16  52

Modeling chicken soup

WinBoy20 is compiled from www. sdmagazine.com

We hope to successfully create a software model. But how to become a great modeling, how to start? Please apply some of the following key principles in the software project to get immediate results.

1, people-oriented

Software is produced - no user, software is just a bit collection without any meaning. Many software experts are very deep in their occupations because they will focus tightly in technology. Indeed, components, enterprise Java Beans (EJBs) and agents are very interesting, but if your software is difficult to use or do not meet user needs, these technologies have nothing to do. It is necessary to take a certain amount of time to study the software requirements and user interfaces that users understand.

2, understand why design

The best designer uses most of the time modeling, occasionally writing source code. This increases the rationality of their design.

3, modest quality

You can't know what you know, even more enough things need to be struggled. Software development is a complex labor because development tools and development technologies are always constantly changing. This process is just a person impossible to fully understand. You can learn some new knowledge every day - in software development, you may be more - of course, you have to choose modest.

4. Demand is a requirement

If you don't have any needs, there is no need to write software. Successful software is in a predetermined time, within a predetermined cost, meets its users' needs. If you don't know what needs, your project guarantee will fail.

5, requires very little change, but you often change their understanding

Object Toolsmith's Doug * Smith likes: "Analysis is a science, design is an art." He is just a "correct" model - fully demonstrates all questions - many "correct" models - they provide a good solution for solving problems.

Demand seems to often change, because your collection work is not good enough, not what they actually change. You may say that users can't clearly tell you what they need, but collecting demand is your job; you may say that a group of newcomers have never done your past work, but you should communicate with them from the first day; you may Will complain that your organization does not provide a good way to communicate with our customers, but this means that senior management does not really support your project. You may complain about new laws, but you should pay attention to what changes have undergone outside the environment; you may also complain that your competitors put forward a new concept, but why isn't your organization mentioned first?

Examples with changes in demand, but you don't have a good collection of needs.

Continued 2001-12-1

For more information, see China Soft Test League: www.cnitunion.com China Soft Test League

转载请注明原文地址:https://www.9cbs.com/read-28087.html

New Post(0)