Full text of ' DUDLEY KNOX LIBRARY NAVAL POSTGRADUATE MONTEREY, CALIFORNIA 93943 NAVAL POSTGRADUATE SCHOOL Monterey, California THESIS ATTACKING SOFTWARE CRISIS A MACRO APPROACH by Tahir N. Qureshi March 1985 Thesis Advisor: Clair A. Peterson Approved for public release; distribution is unlimited SECURITY CLASSIFICATION OF THIS PAGE (Whan Data Entered) REPORT DOCUMENTATION PAGE READ INSTRUCTIONS BEFORE COMPLETING FORM 1. REPORT NUMBER 2. GOVT ACCESSION NO. RECIPIENT'S CATALOG NUMBER 4. TITLE (and Subtitle) Attacking Software Crisis A Macro Approach 5. The quest for power in Nigeria gave birth to the most remarkable political crisis in the country. In the year 1967, Nigeria experienced her first Civil war that rendered many homeless and helpless. Till today, the country is still suffering from the impact of the war. Jun 6, 2017 - A presentation on Software Crisis Prepared By: Chandan Sharma Before we talk. The roots of Y2K problem can be traced back to 1960-80 when. Crisis, its causes, the present status and the possible solution to this crisis. Reconsidering the Software Crisis of the 1960s and the Origins of Software Engineering. Thomas Haigh. As the solution to the crisis. In a less widely discussed coda to the main story, a second conference held. Of the software industry. The software crisis was a major theme in two dissertations underway as Mahoney readied his initial. This report examines the software crisis from a systems engineer's viewpoint. It analyses the key areas of requirements specification, verification and validation and software re-use. It assesses some of the solutions to the crisis proposed by the software engineering community and highlights some of their problems and limitations from the. Causes And Solution Of Software Crisis In 1968 What Album. Case Against Judaism. Jews and ideas. Jews and media. Jews and wars. Jew fanatics. Jews and academia. Jews in history. Jews and frauds. Amid a summer where outrage over the busted New York City subway system has rained down like so much filth-water, the state Metropolitan Transit. TYPE OF REPORT a PERIOD COVERED Master ' s Thesis March 1985 6. PERFORMING ORG. REPORT NUMBER 7. AUTHORS Tahir N. CONTRACT OR GRANT NUMBER(«) 9. PERFORMING ORGANIZATION NAME AND ADDRESS Naval Postgraduate School Monterey, CA 93943 10. PROGRAM ELEMENT. ![]() PROJECT, TASK AREA » WORK UNIT NUMBERS II. CONTROLLING OFFICE NAME AND ADDRESS Naval Postgraduate School Monterey, CA 93943 12. REPORT DATE March 1985 13. NUMBER OF PAGES 86 14. MONITORING AGENCY NAME » ADDRESSf// e r zber'3 and o'~e r s 1 959]:ta -'ocess^g P'c f ess 3na 5;: 7E'2 -973] 1 Acnievement 2 Recognition 3 Work itself 4 Responsibility 5 Advancement 6 Salary 7 Possibility for growth 8 Interpersonal relations, subordinate 9 Status 10 Interpersonal relations, superior 1 1 Interpersonal relations, peers 12. Supervision, technical 13 Company policy and administration 14 Working conditions 15 Personal life 16. Job security 1 Achievement 2. Possibility for growth 3 Work itself 4 Recognition 5 Advancement 6. Supervision, technical 7 Responsibility 8 Interpersonal relations, peers 9 Interpersonal relations, subordinate 10. Salary 1 1 Personal life 12. Interpersonal relations, superior 13. Job security 14. Status 15 Company policy and administration 16. Working conditions The rank order of motivational factors in the survey of Herzberg and in Fitz-Enz survey are given in Table 1, which summarizes the differences in both. This summary also supports the results of Cougar- Zawacki [Ref. 27], which indicates high preference for growth amongst the data processing people. Growth was ranked seventh in Herzberg' s survey, whereas it is second in Fitz-Enz survey. The other major differences were that data processing persons are more strongly motivated by opportunities for technical supervi- sion, by peer relations, and by personal life. They are less strongly motivated by responsibility, salary, and status. Another interesting point is that these differences were more pronounced in case of software people than they were among other computer people. 231 Car Stereo Installation jobs available on Indeed.com. Apply to Installer, Installation Technician and more! Car audio installation keene nh jobs. 281 Car Audio Installation jobs available on Indeed.com. Apply to Installer, Installation Technician and more! Best Car Stereo Installation in Keene, NH 03431 - Sound Power, Mobile Audio Concepts, Interface, Mobile Car Pro Manchester, The Music Store Inc, Anywhere. 161 Car Audio Install jobs available on Indeed.com. Apply to Installer, Installation Technician, Technical Support and more! Sometimes managers assume that lack of performance implies lack of motivation, and of course they are wrong. 68 Nonetheless, what they do is that they then try to supple- ment the lack of inner driving force with a little outer driving force, just when the programmer is suffering from too much. They should understand that increasing driving force will first increase performance to a maximum, beyond which addition of further driving forces will soon drive the performance to zero. It has been observed in research that this rapid fall-off is more pronounced in complex tasks, and programming is a considerably complex task. For instance, programmers are pressed hard to find out errors in their programs, quickly. Consequently, they try hard for the rapid elimination of the errors but they do not succeed. In view of the findings of the surveys mentioned above, managers should keep in mind that the motivating factors for software people are different from those for other people. In the interest of having a better product, managers must give high priority to motivation of the software producers. WATCH OUT FOR THE COMPULSIVE PROGRAMMER In every computer center, one can find bright young men of disheveled appearance, often with sunken glowing eyes, sitting at computer consoles, their arms tensed and waiting to fire their fingers, already poised to strike, at the keys on which their attention seems to be riveted as a gambler's on the rolling dice. If not in such a situation, they sit at tables full of computer printouts. They work for twenty to thirty hours at a stretch. They are not much concerned about food, and they sleep a few hours and then go back to the computer. They are not much concerned about their hygiene and bodies, and about the rest of the world. When they are involved in any job, they exist only for the computers. These are the kind known as compulsive programmers. 69 The compulsive programmers are distinguished from the professional ones, as the the latter address themselves to the problem to be solved, whereas the former see the problem merely as an opportunity to interact with the computer. The ordinary professional programmer usually discusses his programming problems with others. He does considerable plan- ning before proceeding with the actual design and coding. He therefore, spends considerably less time on the computer, and may even allow others to key in his program. He is usually, organized and goes about doing his job systemati- cally with a slow and steady pace. If he encounters some errors in the program, he will get away from the computer and look for the errors and bugs in a peaceful, non- computerized atmosphere. He will allow others to run his program, and thus the time which he saves, he spends on documenting the program and doing other beneficial works. He regards programming as a means to the end, not as an end itself. Causes And Solution Of Software Crisis 1960 CorvetteHe gets satisfaction from solving a big problem, and not from bending the computer to his will. The compulsive programmer is usually a good technician. He knows every detail of the computer he is working on. He is often tolerated in computer centers because of his knowl- edge of the system and because he can write small programs quickly, in one or two sessions of say, twenty hours, each. His programs are used in the computer center after some time, but there is a drawback to that. Since he can hardly be motivated to do anything except programming, his programs are not documented. Therefore, he is the only one who can understand his own programs. Consequently, he is assigned to teach his programs to others. He is like a bank employee who doesn't do much for the bank and yet he is retained because he knows combination to the safe. Usually, he likes to work on large programs. Causes And Solution Of Software Crisis 1960 ChevyIn making such programs, he has ambitious but imprecise goals. For example, he would like to create a 70 new computer language or create a system which can make it easier for others to write super-systems. He has the convic- tion that all such projects require nothing but computers and programming. Of course, he has lot of such knowledge, but during the process, when knowledge from outside the computer world is required, he is stuck. The compulsive programmer spends almost all of his time, working on computer, but he doesn't call it working. Instead, he calls it 'hacking.' The dictionary meaning of 'to hack' is 'to cut irregularly, without skill or definite purpose; to mangle by or as if by repeated strokes of a cutting instrument.' As mentioned earlier, he does have enough skills, but he is without definite purpose. He does not believe in setting forth a plan and goals, because he has the technique, no doubt, but he lacks knowledge. Software systems can be built without plan and without knowledge, just as houses and buildings can be built in a similar manner. The important point here is that as the system becomes large, it also becomes unstable, when built in such a way. Eventually, it results in failure of the software and in extensive chaos. Free activities in san diego. There is therefore, a word of caution for the managers. If you want to avoid software failures, set objectives and goals, plan and design properly, and have plenty of documentation. In other words, managers! Causes And Solution Of Software Crisis 1960sWatch out for the compulsive programmer. STAFFING Software productivity varies from individual to indi- vidual. This high degree of variation is ideally suited to enhance productivity by using the right people. The question of having the right mix of people leads us to the staffing principles which should be followed by the managers with 71 regards to the software persons. Boehm discusses five basic principles of software staffing, which are as follows [Ref. These principles are as follows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |