外文翻譯---軟件和軟件工程-在線瀏覽
2025-07-31 08:39本頁(yè)面
【正文】 igned for each application and had a relativelylimited software(.,programs developed to be sold to one or more cunstomers) was in irs infancy . Most software was developed and unltimately used by the same person or organization. You wrote it, you got it running, and if it failed, you fixed it. Because job mobility was low, managers could rest assured that you’d be there when bugs were encountered. Because of this personalized software environment, design was an implicit process performed in one’s head, and ation was often nonexistent. During the early years we learned much about the implementation of puterbased systems, but relatively little about puter system engineering .In fairness , however , we must acknowledge the many outstanding puterbased systems that were developed during this era. Some of these remain in use today and provide landmark achievements that continue to justify admiration. The second era of puter system evolution (Figure ) spanned the decade from the mid1960s to the late 1970s. Multiprogramming and multiuser systems introduced new concepts of humanmachine interaction. Interactive techniques opened a new world of applications and new levels of hardware and software sophistication. Realtime systems could collect, analyze, and transform data form multiple sources, thereby controlling processes and producing output in milliseconds rather than minutes. Advances in online storage led to the first generation of database management systems. The second era was also characterized by the use of product software and the advent of software houses. Software was developed for widespread distribution in a multidisciplinary market. Programs for mainframes and miniputers were distributed to hundreds and sometimes thousands of users. Entrepreneurs from industry, government, and academia broke away to develop the ultimate software package and earn a bundle of money. As the number of puterbased systems grew, libraries of puter software began to expand. Inhouse development projects produced tens of thousands of program source statements. Software products purchased from the outside added hundreds of thousands of new statements. A dark cloud appeared on the horizon. All of these programsall of these source state mentshad to be corrected when faults were detected, modified as user requirements changed, or adap
畢業(yè)設(shè)計(jì)相關(guān)推薦
鄂ICP備17016276號(hào)-1