Information Technology Reference
In-Depth Information
In a big organization for a given product, usually there are lots of different people
who are working within a group/team for which an organized effort is required to
avoid repetition and to get a quality end product. A software process is required to be
followed, in addition to coordination within a team(s), that will be elaborated further
in PSP or TSP (Chapter 10).
Typically, for big and complex projects, there are many teams working for one
goal, which is to deliver a final quality product. Design and requirements are required
to be specified among the teams. Team leaders 2 along with key technical personnel
are responsible for directing each team to prepare their team product to interface with
each other's requirements. Efforts are required to coordinate hardware, software, and
system level among these teams as well as for resolving issues among these team
efforts at various levels. To succeed with such a high degree of complex projects, a
structured design process is required.
2.2
WHY SOFTWARE DEVELOPMENTAL PROCESSES?
Software processes enable effective communication among users, developers, man-
agers, customers, and researchers. They enhance management's understanding, pro-
vide a precise basis for process automation, and facilitate personnel mobility and
process reuse.
A “process” is the building element of any value-added domain. In any field, pro-
cess development is time consuming and expensive. Software development processes
evolution provides an effective means for learning a solid foundation for improve-
ment. Software developmental processes aid management and decision making where
both requires clear plans and a precise, quantified data to measure project status and
make effective decisions. Defined developmental processes provide a framework to
reduce cost, increase reliability, and achieve higher standards of quality.
Quite often while dealing with larger, more complex, and safety-oriented software
systems, predictable time schedules are needed. Without adopting a software process,
the following may not happen 3 :
- Improved communication among the persons involved in the project
- Uniform procedure in public authorities and commissioned industry
- Insurance of better product quality
- Productivity increase because of the reduction of familiarization and training
times
- More precise calculation of new projects cycle time using standardized proce-
dures
- Less dependencies on persons and companies
2 Usually Six Sigma Belts in our context.
3 The V-Model as the Software Development Standard—the effective way to develop high-quality
software—IABG Industrieanlagen—Betriebsgesellschaft GmbH Einsteinstr. 20, D-85521 Ottobrunn,
Release 1995.
Search WWH ::




Custom Search