No silver bullet
The objectives of this essay are to examine whether or not Brook’s original scepticism that “no single new development in the next ten years would give software developers an order-of-magnitude improvement in productivity, reliability, or simplicity” and “…future progress depends upon addressing the data” are reversible. We will discuss Brook’s original thoughts and we will try to give alternative solutions (if any). This essay, in general, accepts Brook’s thoughts as he worked on OS/360 one of the most known, for their size, software projects.Before we discuss what Fred Brooks is arguing, we ought to refer to the differences between software engineering and programming. These two concepts are, in fact, totally different. On one hand, programming is primarily a personal activity while on the other hand software engineering is essentially a team activity. In other words, a software engineering team, which is working on a project, may consist of many programmers. On the contrary, a programmer writes a complete program while a software engineer writes a software component that will be combined with components written by other software engineers to build a system. Furthermore, the component one
. . .
Some common words found in the essay are:
Software Engineering, Moreover Brooks, Fred Brooks, Analysis Software, , software projects, software engineering, Brooks OS/360, software crisis, Word Count, size software, silver bullet, delivered product, inherent nature software, size software projects, manage software projects, fred brooks, software development, addressing essence, software systems, os/360 size software, people level knowledge,
Approximate Word count = 1730
Approximate Pages = 7 (250 words per page double spaced)
|
 |
