To SOA Architects: Pay attention to the waterfall Development Method

The vice president and R & D Director of Burton said that SOA development is already very difficult, but if you use waterfall development methods, it is very difficult to do well and it is difficult to obtain user needs.

California, San Francisco-Burton Company Anne Thomas manes, Vice President and R & D director, said: SOA Development It is already very difficult, but if you use the waterfall development method, it will be very difficult to do well, and it is difficult to obtain user needs.

Manes said at the "application architecture and Development: Building better software" meeting last week that waterfall development is actually not a methodology. This is just an out-of-date method, so you don't need to pay attention to the requirements and then rush to submit for testing. In large SOA Project This will have serious consequences.

She said that with a focus on iterative work and Modeling of requirements, a well-defined strategy for control is the method to avoid waterfall development.

Manes warning Developers And Architects: "We need to establish control over SOA. SOA is really difficult. It needs to change the way you think. You need to develop from robust control and support for a good programming methodology Culture Start with requirement, modeling, and rule compliance ."

She said that when SOA architects and developers focus on open source software, it is important to follow robust rules in application development. "Open-source software is really cool and free. However, there are also many poor open-source software projects. You need to establish a strong strategy for whether to use open-source software ."

She said that the use of waterfall development methods also limits the reuse of SOA, because individual programmers tend to focus on existing Service And then think that you can do better than this. The absence of methodologies and rules in the development and use of services makes reuse difficult to implement and "no innovation syndrome here ".

She did not mention that this approach was very simple, or there was a trick, or a single solution that analysts could recommend and architects could follow.

She said: "We need to overcome cultural and technical problems, not just old and bad application and overhead restrictions ." "I don't have a perfect solution to recommend to you. You can design them to suit your needs. Enterprise Culture ."

Chris Howard, analyst at Burton, said at a modeling conference that the problem was not addressed by the IBM Rational tool in the development team. He believes that developers may be intimidated by tools suddenly imposed on them.

Manes said that the transition from waterfall-based development to a more iterative methodology needs to make itself iterative and take into account the development and IT department culture.

In response to the question "How To Get Out Of waterfall development", she suggested starting from focusing on iterative development and focusing on modeling.

Howard suggested that, although this is often a problem that was later considered during software development, modeling is critical in many engineering projects in other industries. How can a boeing plane fly if it cannot be modeled?