©) studocu Software Engineering QuantumB.TECH. (CSE & CS) SIXTH SEMESTER (DETAILED SYLLABUS) Software Engineering (KCS-601) Course Outcome (CO) Bloom's Knowledge Level (KL) ‘At the end of course, the student will be able to col Explain various software characteristics and analyze different software Development Models Ki, Ke co2 Demonstrate the contents of a SRS and apply basic software quality assurance practices to ensure that design, development meet or excved applicable standards, Ki,Ke O38 ‘Compare and contrast various methods for software design Ka, Ka co4 Formulate testing strategy for software systems, employ techniques such as unit testing, Test driven development and functional testing. cos Manage software development process independently as well as in teams and make use of Various software management tools for development, maintenance and analysis, DETAILED SYLLABUS. 310) Unit Topic Proposed Lecture Tntroduction: Introduction to Software Engineering, Software Components, Software Characteristics, Software Crisis, Software Engineering Processes, Similarity and Differences from Conventional Engineering Processes, Software Quality Attributes. Software Development Lite Cycle (SDLC) Models: Water Fall Model, Prototype Model, Spiral Model, Evolutionary Development Models, Iterative Enhancement Models. 08 Software Requirement Specifications (SRS): Requirement Engineering Process: Elicitation, Analysis, Documentation, Review and Management of User Needs, Feasibility Study, Information Modelling, Data Flow Diagrams, Entity Relationship Diagrams, Decision Tables, SRS Document, IEEE Standards for SRS. Software Quality Assurance (SQA): Verification and Validation, SQA Plans, Software Quality Frameworks, ISO 9000 Models, SEI-CMM Model. 08 Software Design: Basic Concept of Software Design, Architectural Design, Low Level Design Modulaization, Design Structure Charts, Pseudo Codes, Flow Charts, Coupling and Cohesion Measures, Design Strategies: Function Oriented Design, Object Oriented Design, Top-Down and Bottom-Up Design. Software Measurement and Metrics: Various Size Oriented Measures; Halestead’s Software Science, Function Point (FP) Based Measures, Cyclomatic Complexity ‘Measures: Control Flow Graphs. os Vv Software Testing: Testing, Objectives, Unit Testing, Integration Testing, Acceptance Testing, Regression Testing, Testing for Functionality and Testing for Performance, TopDown and Bottom- Up Testing Strategies: Test Drivers and Test Stubs, Structural Testing (White Box Testing), Functional Testing (Black Box Testing), Test Data Suit Preparation, Alpha and Beta Testing of Products. Static Testing Strategies: Formal Technical Reviews (Peer Reviews), Walk Throug! Code Inspection, Compliance with Design and Coding Standards. 08 Software Maintenance and Software Project Management: Sofware as an Evolutionary Entity, Need for Maintenance, Categories of Maintenance: Preventive, Corrective and Perfective Maintenance, Cost of Maintenance, Software Re- Engineering, Reverse Engineering. Software Configuration Management Activities, Change Control Process, Software Version Control, An Overview of CASE Tools. Estimation of Various Parameters such _as_Cost,_Bilorts, 08 ‘Curiculum 8 Evaluation Scheme CS & CSE (V & VI semester unloaded by Mohit Rajput boy (mohitajputboy2911 @gmal.com) aStudy \ STUDYZONEADITYA.COM (www.studyzoneaditya.com wiww.stu. yzonea itya.com ENGINEERING ALL CONTENTS Books, Quantum, Typing Notes, Handwritten Notes, Practical File's And All Engineering Study Materials Available Here. For more details visit and follow touch to icons below G studyzoneaditya.com B.TECH STUDY ZONE Wi Voulube . STUDY (ZONE wy Brece STUDY ZONE 2y Mohit Rajput boyIntroduction Pe nn sown (BC to 1-80) f introduction t Softwar Engineering Software Components Software Chareteritis Software Crise A. Concept Outline Part ae B Long and Medium Answer Type Questions ac Part on f Software Bnginsering Processes 1 Similarity and Differences from Conventional Bngincering Processes Softicare Quality Attributer | Softwar Deseipment Life Gye (SDLC) Models: Woterfall Mode tena Spiral Mode! Evolutionary Development Model s erative Enhancement Model A. Concept Outline Part 2 9c B. Long and Medium Ansuer Type Questions 1 TAC Catt Sema) L2CWC8T-Sem-4) CONCEPT OUTLINE : PART. ] + Software engineering : Software engineering is concerned | ‘with all aspects of computer-based development including. hardware, software and proces engineering, * Softsrare contains computer program, operating procedure and fssocinted documentation which i necessary for software system | > Saferare eva Setware erin et faites | problems encountered while developing software ‘GT | win ao you sean by satwrare engineering? Diese the objective ein of wftware engineering, Software engineering: 1 According to Boehm, Software engineringisthe practi appliation fof scientific Knowledge in the design and construction of computer ‘programs and associated documentation required to develop. operate Sed maintain the” free software tat oat and within badge. ‘3. Ideals with cost ffetive solutions to practical problems by aplying seentic knowledge 4 Software engineering isthe application of methods and scientific Knowledge tn ereate practical enst-effectve solutions forthe design, ‘construction, operation and maintenance of sotware Objective / aim of software engineering: To understand waer conceptual models and development of better specication Downloaded by Mohit Rajput boy (mohitrajputboy281 t@gmail. com)Software Engineering ‘To lmprove design language aed renee coe ‘Tosatiaythe wre’ reqiremen reduction cas “Twachieve lw maintenance ane pr ‘To provide the software within dest and time, ‘To chiewe high performance. TET] Explain tne components of software. wie] = What is principle aim of software engineering discipline ? Define tattrare components Principle aim of software engineering : Refer Q.1., Page 1-2C, Unit Components of software : LSet of programs: Program :A program isa st ofinstruction. 1 isa callection of sourcecode and objets code. Hxampler of aml) programe ere factorial ef umber or print a sequence of umber up to realm 2A program is a what of sofware and it becomes software ony if Gncuomntaton nad operating procedure mani are prepares. Software documents: Softwar documortation const ll he deserption, programs, graphics ‘and instruction pertaining design, coding esting and preparations of ‘aware Good sftware contain following type of documentations 1 Analysis and specification 2 Design 3 Ceding 4 Toning Operating procedure: Operating procedure provide information about what the software show to work witht how to install i uo our system and how to ‘otro he setts oF the satware ‘The main aim ofthis manual isto provide helpto operating staf for preci desited output with th help ofthat particular software © Tteanbe divided in two parts: 1 User manual 2 Operational mane 14c(carrsem-) ‘TEETH | Define the term software engineering. Discuss the 1. Engineering / developing and manufacturing both are logically diferent in working pattera and providing end product 2. While for geting good quality of either hardware or software 3 ood design incompulaory 3. But in manufacturing phase of hardware, « quality problem ca Intredoce proper attentions ot paid at Use ue of manafaeturng thence a product in manufactured it eannet be modified easly 4. While this type of problom door not exist i ease of software as it ‘an be easily modified and errors can be removed at the same Software does not wear out : 1. In introduction stage of bath hardware and software, there are chances of high fstore rate, 2. Defects are corrected and then fallure rate is reduced and steady ‘S._Incabe of hardware after sometime this failure rate start rs ‘gain a the hardware parta begin to wear outwith me which tas ‘caused by cumulative effet f dust, sudden temperature change ‘highvtow), vibration aad other environmental ssslades Hardare Sonware Wear out Infant mortality Failare rte Failure eatized Flag. LALAPailure curves Downloaded by Mohit Rajput boy (mohitrajputboy281 t@gmail. com)PiCSAT.Sem-4) Software Bagincering ae form a tub ike harware in elation with ti Sav tab curve 4 Thafare ate torre hich eso ie eee these tre are Ae 9 sme undiscovered Fc to era crc he eve become lal and er nce rte uni features bere obaolete which seated curve 6 nal racic thal curve pole becuse sare eRe iit bsomesdtorarate a eqs sme muitennce Change) {i Mostnotware scustom-buil rather than beingastembled from ing componente 1 Nomedaye industries are moving towards component bated aarp nh ncaa are manta Sirens 2. The pe of den ues sont sendy manufctared hardware ‘net wale he market 41 Sethe designer can cnenirate on rly innovative slement of deen 4 Wile sitar in designed a pr the eairement tte wer 5 Arthecimeoesgning sofware, the developers to design and ‘epoment oftware clement nel away Ua hey mayb eae iinany ifort programe (6 Forexample, GUT is build using reusable component which canbe sued tn develop other merise. ie, Software is intangible: 1 Intangibie praducte are those products which we cannot touch and ‘howe quality cannot be measured rntil the whale product heckod 2 Forexample. small software program which is uted to generate telephone bill annot be said ok by only checking that, it staking the correct inp an cuntomer name, addres, number of lea and STD eallete, vt is cheked hat it prodiing correct output in ‘required format. ‘WoT ] expla why wvfiware system that a wel in areal ‘ericevireument mun chang r booms progreetey ear ssf: (ATU 2015-16, Mari 1) == 1 Systems mut change or become progresively less useful fora number ofremens 1-8C(CRIT-Sem-4) Introduction The presence of the system changes the ways of working in ite ‘environment and this generates new requiementn If these ae fot satsied, the wefulness of the ayatem declines The business in which the aystem is wsed changes in response to market forces and this also generaten new sytem requirements <¢ The oxtemal legal and piel environment forthe rystem changes and generates new requirement 1-25 (CT Sem.4) soteae Fagen a software em Difference betwee ‘Traditional engineering in based ‘on mathematice, aience and, | ‘empirical knowledge 7 | Softeare eneineerine wom ecience and eerscenstract | Traditional engineers construct foo real abstract) artefacts, | real artefacts fiware engineering, | In traditional engineering, two ther ae two maa concer | main concerns for product are (itise eet of development | cost of production and reliability land reliability which are | measured by time to failure. | measured by the number of cerwors per thousand lines of ee —___ — 4 | Software engineers often | Traditional engineers generally ‘apply new and untested | try 10 apply known and tested | comments insofware projects. principles and limit the use of untested innovations to only those necessary to create a yroduct that meets its __| requirements, | Some traditional engineers save long-ranged problems that ‘eosure for centuries, 5 | Software engineers ‘rphasize projects that will lvefor years. ‘GEETHA] esplain Rapa Application Development (RAD) model. 1-26 ¢ (CS1T-Bem-4) Following are the various phases of the RAD mode! 1 A Process modeling usiness modeling = fa Thebuniness rode forthe product under development edeaiged in terms af flow of information andthe distribution of information between various business channels, b Avcompiete business analysis is performed to find the vital 1b. Theattributesof all datasets and the relation between these data objects are identified and defined. ‘a. The data object sets defined in the data modeling phase are ‘converted to establish the business information flaw eedad to ‘achieve specie business objectives as per the business model 1b. Process descriptions for adding, deleting. retrieving r modifying » data object are given, Application generation :The actual system is built and ceding is done by using automation tolsto convert process and data modeainto actual rotaypes. ‘Tecting and turnover: The overall testing time is reduced in the RAD model as the prototypes are independently tested during every iteration 1b However, the data flow and the interfaces between all the components need to be thoroughly tested with complete text coverage (ARTU 2013-15, Marke@@) ‘Aaewer 1 Rapid Applicaton Deelpment (RAD is software development sola Us we isin planangin oon of opi pretepn. Tate RAD nie te nical tule are developed in paralelas Date an ar intngrte to me the epee proc fre product delivery, sia — - 1A i dine en di ald and int anos ‘serves of short, iterative developement eyeles. : a a —s toni oy altar Downloaded by Mohit Rajput boy ([email protected])2895 1-27 C (CIT Som-4) stware Bonen — ETRE ae carson of stare pose? (RTO 201677, Marka] eshte prs charaeii er ret ent tbe rc ed Undertnalhe poesdetition ea pensar caret hate progea ver wcmenst aie 1 EI pccseriecinteofunesgcted robles? ay te pes eae! nach wa ht oes errs 6 a eee tiy renin prot res «. Mumutneuey Can te proves evolve to eft ehanging Malena regerenents or eid process improvements? “6 Rapidity: How fast canbe the proces of delivering a system from a ‘even speciation be eompleted 1. Supportability :To what extent can CASE tols support the process YERY IMPORTANT QUESTIONS Following questions are very important, These questions ‘maybe asked in your SESSIONALS ax well as | UNIVERSITY EXAMINATION. 1. Discuss software engineering and ite components sma Refer Q 11 aniQ 12 @.2. What is software crisis? Diseuse main reasons and result of software crisis. awe Helor Q1.7 9. Differentiate between software engineering process and ‘conventional engineering process, ame: Kefor Q 1 Q4. Write short mote on waterfall model ame Fler Q 112 1-280 (CSIT-Sem-4) eae Introduction Q.5. Explain spiral model aa ‘aaa Refer Q 118 Q.6. What are software process models ? ‘awe Refer Q. 1.22 600 Downloaded by Mohit Rajput boy (mohitrajputboy281 t@gmail. com)ACKCRTTem-A) —_ Software Requirement Specifications SRS) PART: Requirement Engineering Process Ebcitation, Analyos, ‘Documentation, Review and Management of User Needs, Feasibility Study Software Requireme Specifications (S} CONGEPT OUTLINE : PART-1 ~« Requirement elicitation : I: is the process during which | oftware requirements are discovered, expressed and revealed from ayetem requirements «+ Requirement analysis: Tt is the activity during which the | reusement gathered during elicitation ar anajaed for eonBicte ambiguities, Inconsistencies, missing requiresent + Documentation: Its the activity which is written atthe end = Engineering Process Elicitation ee Sfemment ctatonandana octet «easly tayo termine wheter developing ae See ‘product is financially and technically feasible { Peaibly Study {3 yand A.Concept Outline Part socom B. Long and Medium Answer Type Questions enters B>1OE 10 ‘Que2i. | Discuss the significance of requirement engineering. ‘Ano, write the various steps of requirement engineering wth proper explanation. Modeling “+ Data Flow Diagrams + Bovty Relationship Dingrams * Decision Tables '+SRS Document + IEEE Standerds for SRS A. Concept Outline Part 2 B. Long end Medium Answer Type Questions sees, BNO) engineering: 1. Requirmentenginseringis the proces of determining user expectations fura.ew or modified product. 2 These user expectations, called requirements, must be quantifiable, relovant and detailed, Parts {Software Quality Assurence + Verification and Validation yi 5 SR OM x Soeocr aoa mpnenmsensacsim tic Pas Sepa: Qui Eat erentha nit enmemanauconneis Requirements snalysisis.an important aspect of project management 5. Requirements analysis involves frequent communication with system ‘users to determine specifi feature expectations 5. Ms yoalistocreate a requirements specification tha is complete, irreek, sand understandable te both customers snl developers. BAC (CST Sem-4) Downloaded by Mohit Rajput boy (mohitrajputboy281 t@gmail. com)“ ‘ik, Requirements documentation: 2-9C(CSIT-Sem.4) cesnerrng: gar suape ae sow in FE 21 ns Z 4. Croc process steps of Feguirement engineering, Fe 21 Requirements citation torn ken as gathering of resirements ‘eeuremente are deified with the help of customer and SShagrens prceen ovale Requirements analysis "te renurenentaranalysedinonder to dentifyineoosstencig, Secnoniommcte We dnt equrenent intern ofrelationahieandalvorese cat any » ® ‘This iste ed product of requirements elicitation and analy ‘The requirement documentation is very important ast willbe the {oundaion forthe design ofthe software, Th document i Kowa as software requirements specification | ‘sks ‘The eview process iscarved out to improve the quality ofthe SES. may alo called ne roqirementsverifieation Forms berets eva and verification oul ot be tend aga decree actvty tobe dan ony tthe end ofthe preparationet Swe 4 Tt should be tested as cvatinuous activity that is imcorporated it BACICNATSem-4) Sofware Requirement Specifications SKS, GaeEa | What is the significance requirement ‘engineering ? What are the requirement validation techniques ? Taewer | Significance of requirement engineering : Refer Q.21, Page 2-2. Ua Use of requirement engineering Requirement engineering is used ia 1 Determining the feasibility of producing a particular product a prt of ‘the preduct ine Determining the production, testing. and deployment ofthe particular produc Determining the evolution ofthe product ine that is, the incorporation ‘fchanges that result from that preduet development Product rpecific ‘requirements often "grow up" to become product line requirements if ‘hey can be slightly fenerlized or if they pop up in more than ome roduc Tha is the primary mechanism for the evolution of software Product lines ver tbe ‘Requirement validation technique 1, Test ene generation: In thistechnique, the various tess are developed for requirements. The requirement chock can be carved out sth following Verifisbitity :Isthe requirement renlisticlly testable ? Comprehensibility: Is the requirement properly understoud ‘Traceability: Is the origin of requirement clearly stated? Adaptability : Can requirement be changed without a lange impact on other requirements? ‘created using A CASE tol database using rules of ‘censstencies fe idetitied that checks the entire requirement ‘method or notation, The report of and managed Downloaded by Mohit Rajput boy (mohitrajputboy281 t@gmail. com)atic sarap BC. ag “ Pr tet or : a Tease may be atom requirement docomentation, cust ‘market analysis 4 emnatecngges are used te iawave te user onthe bast eg involvement required titction procedure: teeral elicitation procedure contain log sep 1 identifying relevant source of nformation i, «Une Customer Domain experts 2 Determining what information is needed by asking questions, 2. Analyzing the gathered information, looking for implication inconsistencies, or unresolved isis i 4 Confirming our understanding of the requirements withthe usr, Creating requirement statements Problems in requirement elicitation : 1 User isunsble to explain his requirements, 2 Less knowledge of technology and may nat consider what i posible 8. Use offre language by developer and user. 6 Lack of sills in developer Use snot providing sme information du to some reason, Requirements are coming from different sources. WeeRA | What is system documentation ? Explain in detail. mer] 1 Sten dianentatninwrn entrain ta er ovoyten eraser owe 4 System documentation inckudas all the descriptions, graph xen os ric, or ‘tecwcimprannbedee mpleoner, odep "ere ys of cuentas mana required bya atem System design documentation : ve “s 1 Br of th doment ato iat provide th ‘the system at top level, ge a“ bie tet cane dere fromthe ea product analy Stem dein dementain ot of he low aacicsnrsem) lk Software documentat Sonqare Requirement Specieations SHS) ormlotion ofthe problem Fensibiity nse verview ofthe system, ts subsystem and ther interfaces ‘output report and sereen displays Input and xouree documents 6 Datadictionary mm : Software documentation consist of following a. Hardware devices comm System software ree al one sytem ftvare cho DEMS specification : Description of equipment, peripheral runcation hardware ‘specifieation : Description of the operating screen formatter ‘fet enerator and communication sofware ‘e. Application software specification : Description of each ‘pplication program. File design or database design : Description ofeach file used io ‘Batem ts acess method and its organization. operation documentation: Its oa isto hep the operation eal ran Params proper order, dtibut the Output. and handle the errore iver come during execution of programs, It consist ofthe following ‘Multiple system flowcharts with supportive narratives : Description of ech program, its purpose, andthe exceution ofthe rogram. 1 Operation procedure for each program : Description of input red and its format, He required, output produced, error Conditions and operators required ete 1. User reference documentation: It consists ofthe following ‘Objectives of documentation :It provides outline of the purpose and wre of the document. by Input documents It covers complete lst and samples fll the {input documents used by the system & Output reports and sereen display: It contain the complet ist ‘and sample cf al report, with thr froquencies and distributions, fod examples of screen displays. 4. Processing logice and error conditions :It provide outline of rocrasng logic foreach output report, error conditan et: System maintenance staff documentation It isthe list of compater department staff members who would be contacted incase ofany robles: that the user cannot rect TRIBE rr cert nts soo an gue of exer weds Downloaded by Mohit Rajput boy (mohitrajputboy281 t@gmail. com)softmare Pines wer | Review of user needs ea preset vcves people remot en and ental er 1 for anomalies and omissions They check the requirement Fer eee process may’ be managed in the SAME WAY a8 propa inspections vot itray be organized asa broader activity with deen A chong dierent parts ofthe document, ponte chek ineing atts are performed in user needs review 1 Pianarevew Neview meeting Folow-ap actions 4 Document after review 5 Understudy © Checking for redundancy 7 Completeness 8 Consistency 8 Aap 10, Canformation of standards Management of user needs: Management of user needs isthe process of documenting, analyzing, ‘racing promticirg and agreeing oo requirements and then entling ‘change and commsnicating torelevant stakeholders. Its continuous proces throvghout a projet A requtemeat is capability to which a project outeome (product or service) should confor ‘The purpose of management of user needs is to engure that an ongaization documents, verifies, and meets the needs ad expectations ofits customers and internal or external stakeholder Following activities are performed in management of user needs Investigation Fess Design Construction and test ‘Requirements change management Release PAC ICRTT Sem) Softmare Reqirement Specfentions 5K GecTa | wnat do you mean by eeibilty stay? Explain various aaper ofeuibilty and important steps that ae carried ut daring (he tensibility study phase ‘Aoswer Teaibilitystady isthe analysis of sks, cost and benefits eating to Tectomies,technology and user operat Thc output of feasibility sty isa document known as fasibiity stay report ‘The report must answer the following key querions i. Will the new eystem provide a better way todo job ? ii What he proposed system will do? ti What wil be the estimated cost of proposed system ? je. What wil be the benefits from proposed system ? “4 There aresevera typesot feasibility dopendng on the aspect they vers Some important feasibility is as follows ‘a. Technical feasibility : The technical feasibility study basically ‘enters on alternatives for hardware, software and desig approach toetermine the functional aspect of system, ‘Operational feasibility: Operational feasibility isa measure of bier people are able to work with system. This type of feasibility demands if the system wil work when developed and installed ‘& Reonomical feasibility : Economical feasibility is « measure to find wut whether itis economically worthwhile te invest ia the ‘projec. Cost benefit analysisis carried out todetermine exnoanical feasiity. ‘The feanibility study involves following eight steps : Forma project and appoint a project leader. Prepare system flow chart. Bnumerate potential candidate system, ‘Describe and identify the charactrities of candidate systom. Determine and evaluate perfurmance and cost effectiveness of each candidate stem. (6. Weight system performance and cost data 7. Select best performance system, '8_Prepare and report final projet directive management. Que27 | Explain the cost henefit analysis to determine the ‘cconomic feasibility onthe basis of direct cost, indirect cost, tangible Denefite and intangible benefits. Downloaded by Mohit Rajput boy (mohitrajputboy281 t@gmail. com)