Scribd
Upload
50 views85 pages

Software Engineering

very useful

Uploaded by

Pushpanjali Singh
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
50 views85 pages

Software Engineering

very useful

Uploaded by

Pushpanjali Singh
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
Pumuisien ey: Apmis one Sereter Quant Page Prt. L4d) ave Soo Stes Indra Are, iat chants 201010, Pe 0120-1605 aqme Woe msuatipege tls Ip ap Fakes Dn ne Da ce: Us, Est Robtas Naga. Shubdara, Deb © Au Rens ResenveD ; Neer the peblstoe mey he praca or amet wang fo by any mans toot poiaion infomation contin in hs work i derived rom sources teteved obereable very efor hs en made ensue accucy,homevernetber the publisher nor the authors earn the aur o completeness of any inormaton pubis here and nether the publisher nor the authors tallbenoponble for any ers, omisions, or damages Software Engineering (CST : Sem & 6) 1° Balin: 2070.11 Edition 2011-12 3° ition : 2012.18 4° Baition 2010.14 5° Baton 2074.15, 6° ition : 2015-16 7 Edition : 2016.17 8° Bition : 2017.18 Price: Rs, 90- on = CONTENTS Ses UNIT; INTRODUCTION (-1Cw 128g, lntrwhacion to Software Engineer, Sftwate Companens Softens Characteristics, Software Cris, Software Engineering Brocton ‘Slay and Diterences ren Conventional Experi Prt, Software Quality Altai. Senet Orvelopenet ile ise GOLE) Models: Water Fall Model, Prototype Model. spial Model, Evolutionary Development Models, leranve Enhancement Moxie LUNTTII; SOFTWARE REQUIREMENT SPECIFICATIONS RS) @1Cw2416) Requirement’ Engineering, Process: Elicitation, Analysis ‘Decumentaon, Review and Management of User Nee, Study, Information Modeling, Data Flow Diagrams, Entity Relationship Diagrams, Decision Tables, RS Decument IEEE Standards for SRS" Sofware Quality Assurance SOA). Venison Sn Validation, SQA Plans, Software Quality Framencrks 150 9000 Models SE-CAM Ste UNITIII: SOFTWARE DESIGN G1Cw3360) Basic Concept of Software Design. Architectural Desgn, Low Level Design Movularvation, Dean Stuctur Curt Pasa Cakes fess ‘Guat Coupling an Caeser Measures, Design Setnges Fares ‘Gren Design Object Onened Oesg Top Down an Bote Up Desig Sofware Measurement ant Mets Various See Orci Measures. Holestad's Software Science, Function Point FP) Based Measure, Cheomatc Complexity Measures Conte Pw Gap UNIT:IV: SOFTWARE TESTING 1Ct0433.0) Testing Objectives, Unit Testing, integration Testing. Acceptance Testing, Regression Testing, Testing or Functor and fsting for Tecformance, Top-Down and Battom Up Testing statepe Test Divers and Test Stubs Structural Testing (Wt Bon Teen, Functional Testing (Black Box Testing Test Bata Sat Preparation, Alpha and Beta Testing of Produ Static Testing States Formal Technical Reviews (Pee Reviews), Wale Thrvgh: Code Inspection Compliance with Design and Coding Standards UNIV: SOFTWARE MAINTENANCE AND SPM. (5-1 Cto'5-31.C) Sforare a an Evelutionary Ent, Ned for Maiatarce,Categnes of Maintenance Preventive, Cortive and Perketve Matera Cont of Maintenance, Software Re Engineering. Reverse Engineering Software Configuration Management Activites Change Cot Process, Software Version Control. An Overview of CASE Tole Estimation of Various Pararnters sch 3: Cnt, ons Shadule Duration: Constructive Cost Models (COCOMO), Resource Allecation Model, Software Risk Analysis ant Management ‘SHORT QUESTIONS ($0-1Ct09.18C) ‘SOLVED PAPERS (2012-18 T0 2016-17) (SPACIOSPABC) Introduction Part smuimnne (n2C to 1-8C) Introduction to Softwore Engineering Software Components Software Characteristics Software Crisis, fl A. Concept Outline :Part-1 - 12€ B Long and Medium Answer Type Questions. 1-2c Parts (1-9€ to 1-270) ‘Software Bnainsering Processes + Similarity and Differences from Conventional Engineering Processe Software Quality Attributes Software Development Life Oyele (SDLC) Models : Waterfall Model Prototype Model Spiral Model Evolutionary Development Model erative Enhancement Model A. Concept Outline :Part.2 B Long and Medium Answer Type Questions LAC CSN Sem-4) 1-20(CSIT-Sem-4) \ Inkroduetion Trtroduction to Sofas Software Cha CONCEPT GUTLINE + PARTY * Software engineering : Software engineering is concerned waa peed hae aed eee aes hardware, software and process engineering. + Sdheawtmucpactpeg Se inggmetare ed | aera — 7] WRB asa tit sctenive engineering? Deca the objective / nim of oftware engineering. Software enineering 1 According to Bochm, “Software engineering isthe practial application of scientific knowledge in the design and construction of computer programs and associated documentation required to develop, operate ‘and maintain them" 3. Tt deals with cost effective solutions to practical problems by applying scientific knowlede, Software engineering is the application of methods and scientific knowledge to create practical cost-effective salutions for the design, construction, operation and maintenance of sftware. Objective aim of software engineerin i. To understand user conceptual models and development of better specification 1-6 (CST -Sem-4) Bae ta] Explain the components of raftware, oR ‘What is principle aim of software engineering discipline ? Define software components. Principle aim of software engineering :Refer Q.1.1, Page 1-2C, Unit Components of software : i. Set of programs Program :A program isa set of instruction 1 It isa collection of source code and objects code. Examples of small programs are factorial of number or print a sequence of number up to sven limit. A program is a subset of software and it becomes software only if ‘documentation and operating procedure manuals are prepared, ji Software documents : hice of 1. Analysigand epecifcation ~ 2 Design 3. Coding 4. Testing ‘The main aim ofthis manual isto Ip to operating staf for rodcing desired output with the help ofthat particular sofbware. © Iteanbe divided in two parts 1 User manual 2 Operational manuals AC (CSMT-Sem-4) GueTS | Define the term software engineering. Discuss the various characteristics of software with examples. al Software engineering : Refer Q. 1.1, Page 1-20, Unit-L Characteristics of software : [ARTU 2012-13, Maris 10) ‘Software is developed or engineered, it is not manufactured in classical sense : 1. Engineering / developing and manufacturing both are logically different in working pattern and providing end product. 2. While for getting good quality of either hardware or software a good design is compulsory. 3, But in manufacturing phase of hardware, a quality problem can introduce ifproper attention isnot paid atthe time of manufacturing ‘as once a product is manufactured it cannot be modified easily 4. While this type of problem does not exist in case of software as it can be easily modified and errors can be removed at the same movement Software does not wear out : 1. In introduetion stage of both hardware and software, there are chances of high faihure rat. 2 Defects are corrected and then failure rate is reduced and steady state comes. Incase ofhardware after some time this failure rate start rising seinas the hardvarepartabegin to wear ot with ime wich nas ‘aud by cumulative effect of dust, sudden temperature chan (highow, vibration and otherenvironmental muiadien Hardware Software Wear out Tnfant mortality Failure rate deatized Fig. 1.8.1, Failure curves, Software Bngineering Cras ‘world environment must change or become progressively less useful 1-50 (CST Sem. form a tub like cation with 4 Thisfailre rate of hardware in relation wil Curverwbich i liacalled “bath tub curve” 5 Incase of software, these failure are due to some undiscovered, tn amt gone erers are correted the curve become lat and ceruinus a the sare rte tits features become obsolete which irealled idealized curve {6 Inreal practice this ideal curve isnot posible because software snot near out hut it becomes deteriorate and requires some tuaintenance changes) {ik Mort software is custom-built rather than being assembled from ‘existing components 1 Nowadays industries are moving towards component based ltsembly of product whieh mean all products arenot manufactured tthe same place 2 This type of design uses some already manufactured hardware clement available in the market So that designer can concentrate on truly innovative element of design 4 While wftware is designed as por the requirement of the use. 5. Ath time of designing soRware, the developer tres to design and implemen software element in such away that they may be reuse inmany diferent programs {6 Forexample, GUI is build using reusable component which an be ued te develop other menus iss Software is intangible: 1 Intangible products are those products which we cannot touch and vwhoue quality cannot be measured entil the whole product is checked 2 Forexample. a small software program which is sed to generate telephone blleannot be said ok by only checking that, it staking the correct input as customer name, address, number of local and ‘STD calete, unt it ischecked that iis producing correct output in required fort Explain why a software system that is used in a real (AKTU 2018-16, Marks =a Systeme mut changer become progressively less sefl fora number 1-00 (C8IT-8em-4) fa. The presence of the mystem changes the ways of working in ita nvireament and thin generates new requirements Ifthese are eer natiafed, the usefulnese of the rystem declines. bb The business in which the system is used changes in response to market forces and this also generates new system requirements Theexternal legal and poltieal environment for the sytem changes and generates new requirements 4 New technologies become available that offer significant bref tnd the aystem must change to take advantage of them Software change is very important because organizations are now completely dependent on their software systems and have invested millions of dollars in these systems. ‘Their systers are eitcal business aes and they must invest in system change to maintain the valve ofthese assets. A key problem for organizations is implementing and managing change to their legacy systems so that they continue to support their business ‘operetions ‘There are « numberof different strategies for software change Software maintenance : Changes to the software are made in response to changed requirements but the Fundamental structure ofthe software remains stable, This s the most common approach used te system change. Architectural transformation :This sa more radical approach to sofware change than maintenance as it involves makig significant changes to the architecture of the software syst-m ‘Most commonly, systems evolve fram a centralised, datacentric architecture tclient-server architecture. ©. Software re-engineering: This is differen from other strategies in that no new functionality is added to the system. Rather the system is modifed to make it easier to understand and change System re-engineering may involve some structural modifications brut dors not usually involve major architectural change GEETE | Discuss the following in briet : i. Software characteristics li, Difference between module and software component ‘eevee | Software characteristics : Refer 1.3, Page 1-40, Unit-1 ‘Software Engineering i Difference between module and software component Module is a partitioned | systeminto implementation ‘unite, independent task | i ‘esigument. Modules might ‘right oot be a component ewer | Saftware developmen stall layered teluology Tht mies to develop saftware, one will have tego from one layer to another. ‘Thelayers are related sndeach layer demands the fulfillment ofthe previous layer Big. 16.18 the upward Dowchart ofthe layers of software development, Fig. 14. Software engincering i divide int following four layers: L Aquality focus Any engincering approach must rest on quality The “Bed Rock" that mppors software engineering is quality foes. 2 Process: 4 Foundation for SE is the process layer. 1-8C (CAT-Sem-4) Introduction SE process it the GLUE that hols all the technology layers together ‘and enables the timely development of computer software It forms the base for management control of software project. 3 Methods: ‘a. SE methods provide the “Teehniesl Questions” fr balding eotware. bb. Methods contain abroad array of tasks tht include communication requirement analysis, design modeling, program construction tecting and support. 4 Tools: ‘4 SE tools provide automated or semi-automated support for the “Process” and the “Methods” 'b. ‘Tools are integrated so that information ereated by one tool can be used by another. QueLT | What is software crisis 7 Discuss main reasons and results of software crisis, ‘Anewor Software crisis is ase of difficulties or problems encountered while developing software a tee Dennen eta nten eater der Decay eatecteteen estar taker Mahe et Sai non omen cnn Beat sl sede Pape ee 1.90 (C8ATSem-4) + Software engineering process It sa set of activities that leads to the production ofa software product + Conventional engineering process :Itis structured logical approach to develapa stable final product + Software quality : It the conformance to imple tated ‘apetina and performance requirements, explicitly documented evelopment standards and implicit characterises that are ‘expected toll professionally developed software + Software development life cycle : It represents number of identifiable stages under whieh software gacs during is fe. 1-100 (C81T-Sem-4 loeradction Difference between software engineering process and conventional ‘engineering procers Pe ie 1, [Fosdatins | Based campeter | non nants fet ead Ear | st Tnnovation Replication Dutlding ‘or development efforts, hanging old desig to [_ ald new features. z Few software Many of conventional WEBTI] ovtneconveatinal engineering presses. How i ‘uterat fom ftvaeenginering ponenee’? a) Conventional Process is a structured logical approach to develop astabl final prot % Conventional engineering process utes the software tons to design asd salve their oom epetem 3 Therefore, developed electronic implementation end testing document gues through analysis, sigh Dhases just lke software engineering age engineers manage tore comnts | sarioctarog | (Bey alae ented on = ______. jastages "| Wor Explain software quality attributes, _ a Define sttwarequaity. Setar uty ltt nd racic tt ea try ha deste te desi ‘tenbutes of software products It is concerned with following “ene 1 Conran cca 1-11 €(CSATSem-4) Software Engineering = = 2 Fitness for the purpose 8 Levelof satisfaction quality attributee area flows a intnonally corect fit behave according to 1 Correctness: Aste erMcune rear spesexinn a tat rales desi op en 2 Rete Arte apne ike ardor oF ince of Ero asin Reuss: I expan how weed rourenen Toone 4 Porae Stare toprtat ite acs toro on sm Saeed reestandabiity ow wld the developers understand nyt ane super evlaatyanguntesanta. 4 Pesformane Insofar egeerng performance ies with aera quel eprom ts operation, saperabiy Cana sytem ceperate wth ante sytem At vesmabiestcucks wether the propertin ste system be vr 8 Tien te Eoiency ts tbe ety fsetware yates flit purges with ree nomenon emu ich ne erage ‘Pawan hae prorat does system behave in situations not rureect input, hardware failure, las ithe ease with which asoftware ier other than one for which it ability to deliver a system on time, ‘oe Lad | Whatssottware quality? What are three dimensions of oftware quality? Explain briefy, _ [ARFUB0IS-14, Maes 05) ‘ARTU 2016-16, Marke 19) ‘Answer Software quality : Refers Q.19, Page 1-100, Unit-1 Thrce dimensions of software quality are : L. Quality of design : I is the extent to which the design reflects prodoct or ervice that satisfies customer needs and expectations. All ‘the necessary characteristics should be designed into the product oF service at the outset AC (CST Sem-4) Tinea 2 Quality of conformance : Iti the extent to which the product or service conforms ts the design standard The design has tbe fathfaly reproduced in the product or service | Quality of use : It is the extent by which the user is able to secure tontinuity of use from the product or aervice, Products need to have a low cont of ownership, be safe and reliable, maintainable in se, nd ceaty to use Que Lil.] Explain Software Development Life Cycle (SDLC) Discuss various activities during SDLC. 1 eh also ‘and their sequence in life 2 Softwar life eyele represents numberof identifiable stages under which software goes duringits life ‘We have different ie cycle mode and disadvantages each one have its own advantages 4. We ean choose any one of them on the basis of 1. Development speed Product quality i, Projet visibility iv. Administrative overhead Risk exposure Phases of software development life cycle models: Requirement definition (system analysis and system specification) ‘System and component (software) design i. Implementation and unit testing i. Integration and system testing Operation and maintenance Software Bagineering ] Tey 1 (eree| 4 Fig. 111.1. Software development lf pele model nd product ofeach phase The output of roqurement definition is software requirement specification (SHS) document. 1h The output of system and software design is entity relationship TER) cungram, dota flow diagrarn DPD), low chart te

You might also like