Step by Step UniT—I UNIT — I: SOFTWARE CRISES AND MYTHS Question 1: Discuss the software characteristics with the help of diagram. (S-17/7M) Question 2: What do you mean by evolution of software? What are the characteristic of software? (S-15/S-16/7M) (W-14/7M) a) Software Characteristics Software development is a logical activity and therefore it is important to understand basic characteristics of software. Some important characteristics of software are i) Software is Engineered, Not Manufactured Software development and hardware development are two different activities. A good design is a backbone for both the activities. Quality problems that occur in hardware manufacturing phase cannot be removed easily. On the other hand, during software development process such problems can be rectified. In both the activities, developers are responsible for producing qualitative product. {i) Software does not Ware Out In early stage of hardware development process the failure rate is very high because of manufacturing defects. But after correcting such defects the failure rate gets reduced. The failure Fate remains constant for some period of time and again it starts increasing because of environ- eo ern 1Mistakes or bugs in a program can be expensive in term: | Thus software should be delivered intenance of software is an activity that can be done 0 | ring the software to the customer. Any small change in software should n cause restructuring of whole software, This indicates thatthe design of software has po difficult to predict the exact time on which the soft dovelopment of software can lead to meet the given. ‘ow Production Costs: The software product should be cost effective. ce: The high performance software are expected to chia od and memory usage. ie same software in different systems and software, eeener’s myths? Explain the (W-15/6M) 2, Software Myths There are some misbe building software. For any sof them, Here are some typical myths: s in the software industry about the software and process| sre developer it is a must to know such beliefs and reality ab a) Management Myths ‘Managers with software responsibility, like managers in most diseiplines are ur ‘pressure to maintain budgets, keep schedules from slipping and improve quality. + Myth: Usinga collection of standards nd procadures one can build softwareportant than hardw is ae vy, yet the majority of (0 “Myth: Ifa project is outsourced to third party then all the worries of software building are over. Reality: When a company needs to outsource the project then it simply indicates that the company does not know how to manage the projects. Sometimes the outsourced projects gysomer nye 4 ‘A-customer who requests computer software may be a person at the next desk, a technicalStep by Ste 4 1g program is the only work product for the software project. working program/software is the major component of any software proj but along with it there are many other elements that should be present in the sof h as documentation of software, guideline for software support. ne of the most effective software quality assurance mechanisms can be applis from the inctption of a project, the formal technical review. Software reviews “quality filter" that have been found to be more effective than testing for finding classes of software defects : ‘+ Myth: There is no need of documenting the software project; it unnecessarily1. Collection of software engineering work tasks 2, Project milestones 3, Software quality assurance points Umbrella Activities ‘The umbrella activities occur throughout the process. They focus on project management, cking and control. The umbrella activites are 1, Software Project Tracking and Control: This is an activity in which software team can assess progress and take corrective action to maintain schedule. 2. Risk Management: The risks that may affect project outcomes or quality can be analyzed. si Software Quality Assurances These are activites required to maintain software quality “4, Formal technical reviews: It is required to assess engineering work products 10 uncover ‘and remove errors before they propagate to next activity. 5. Software Configuration Management: Managing of configuration process when #2(it Se, at starts with requirements gathering phase and then progresses gh analysis, design, coding, testing and support. Figure shows the waterfall model.s1 Sinpoo way surdoq Seo] BuysoL (6 -oseyd ve ssid oqo © 51 BIS aBAYOS us soa (utAppinb 3 9pI0 uy sesmmardanes uogewuawaydiat soysur uayo con a : 3 -amnyos Pappisuo ou ae Anguueee so Bu] pa Ken pe59,A sobewuerpesig +©} Som ssaooid ayy op soBenBium, SumuesToxd wi Jos Smears uewy soqey ‘sonbruyjoa) uoreiouss uno} Jo nq Bunvowo}duy) 30} ojisuodsay axe Sessoooud asou4s 1d om pou Bunlepow sseocugotrunyy 127[o1g xomyfogyiuproursug auvsufoy cm Spo ao Pu om ‘soto ole NEF zene Of ORL ; = so Sonmarsuedsax pun sojor ye ION :zporeaoy Aytenonpezuezo Komp se asa AN “E | ‘soxuorsno amp seanbar ome ew Souorsjna any pu sys yoofoud Koy HurAjiuapy a aqnpoiosyoofoud & gos oF uot om doy stosonb oso 01 uoMsuE ayy :;uaK Kq HOP 9q YM IEA -Z ‘4a pa oun ‘doa yo ump ayn Assn asodind ssottsng amy ‘Sh0N Ut PoImS HOM areAYos aK 0} suo SsauIENG Jo AxIHTEA om S89658 ‘same sq9 wosonb snp oy sau :padoqsnap Baa may om 5 ys, 2b “Wea aremyos: Jer Sis bof 09 4} sano Sud moqsOE ue apd sons on Bota usteye Sette 0 278 993 ep qeandde dud Hsia smog ‘std pofoxd mess a pus sonstoseae oid kay jo me ovr en opm jo ston yo AAA 288s SH SHSM UDichg seg ° par Id HHSM 51 1OUN4 {ZZ UoYsang,