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, eae A. Concept Outline :Part-1 - 12€ B Long and Medium Answer Type Questions. 1-2c Parts (1-9C 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) ee Software Cha _SONCEPT OUTLINE : PaRT-1 + Software engineering : Software engineering is concerned with all aspects of computer-based development including hardware, software and process engineering, Software contains computer programs, operating procedure and | ‘associated documentation which is necessary for software | system, Software crisis : Software erisis is a set of difficulties or |_____ Problems encountered while developing software — 7] a ‘GEETT] What do you moan by software engineering? Discuss the objective / nim of oftware engineering. Sottware engineering 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" 2. Sofware enginceringis a discipline whose aim is the production of fault froe software that satisfies the users needs and thats delivered om time and within budget, It 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 ‘To understand user conceptual models and development of better specificationSoftware Engineering 1-86 (CSTTSem-4) i ‘Toimprove design language and reusable code 4 Tostiaty the users requirements . ‘Toachiove low maintenance and production cost {_Toprovide the software within budget and time vi. Toschieve high performance Bee ta] Explain the components of roftware, oR ‘What is principle aim of software engineering discipline ? Define software components. Principle aim of software engineering :Rofer Q.1.1, Page 1-20, 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 @ subset of software and it becomes software only if ‘documentation and operating procedure manuals are prepared, ii. Software documents : ‘Software documentation consist all the deseription, programs, graphics land instruction pertaining to design, ending, testing and preparations of softwar. Good software contain following type of documentations 1. Analysigand epecifcation 2 Design 3. Coding 4. Testing li, Operating procedure: 8 Operating procedure provide information about what the software is, how to work with it, how to install it on our aystem and how to ‘control al the setvities of the software, ‘> The main aim ofthis manual is to provide help to operating staff for producing desired output with the help ofthat particular software. © Iteanbe divided in two parts 1 User manual 2 Operational manuals LAC (CSAT-em-4) ee GueTS | Define the term software engineering. Discuss the various characteristics of software with examples. = Software engineerin [ARTU 2012-13, Maris 10) Refer Q. 1.1, Page 1-20, Unit-L Characteristics of software : ‘ ‘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. 5, But in manufacturing phase of hardware, a quality problem ean 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 ou 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. In case of hardware 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4 Dittrence between mle and software component Te] Wodaie T__Sotiware component tthe generic wenoing of |The generic meaning of (RAST iciesie | Septet meh e mae renee pee | wiaitonalresrction | prem meen wg «pects ‘neve 2 Module i ved to model the | Components are used to model a system in function lew. gystemin technical view ‘| Medvle is a partitioned | Component is a runtime entity | © sssteminta implementation (can be made up of modules), nite, independent task | independent runnable unit. | ‘esigument. Modules might ‘right oot be a component FTE eopinn tne toto ming statement “Software cogineering ine layered technsiog” (RRO He, a) ma 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 Reasons of software crisis : 1. Communication gap between end user and software developer, 2. Misinterpretation of razirement, improper problem defen, 20 ledge about end tne environment High software cost compare to hardware cost, 4 Changes in end user requirement increase the problem for developer. 5. Inaccurate scheduling and cot estimation of projec. 8. Datacolection and analysis isnot upto mark or not done timely. 2 8 Increase in sie of software, Increase in complesty of problem area. Results of software crisis: Poor quality of software. Late delivery of oftware ‘High cost compare to estimate cost. "Not able to moet current demand for which it should accommodate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 Pesfr the ree 2 Levalaicion “ome Tenn snirare qual tre reas ro eye tem factional cect ft hae scoring its functional requirement «pecification. a tat rales desi op en 2 Rete Arte apne ike ardor oF ince of Ero asin Reuss: I expan how weed rourenen Secor —_— «c_ Peat Start pray athecs with which away Porta Dytorunm compte ber tha one wich does system behave in situations not rureect input, hardware failure, las Soin verteedablity or ello the developers understands stem ane super evlaatyanguntesanta. 4 Pesformane Insofar egeerng performance ies with aera quel eprom ts operation, eterperabiity Can ytem operate wth another sytem A Wena: te ccs wheter she roerisethe sytem be verified 8 Tien te Eoiency ts tbe ety fsetware yates flit purges with cea of eeeny revoures sch as ie stooge, rol perce ability to deliver a system on time, ranean ch ‘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. “Anewer Software Development Life Cycle (SDL) 1. Software development lifecycle a diagrammatic representation which alse provides description of various phases and their sequence in ife ‘cycle of oftware product 2 Software 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 % Therequremont documentation is very important ast willbe the Automated eo ‘analysis: Ifthe requirements are expressed foundation forthe design of the software. in the form of structured o formal notations, then CASE tas can be . vee is Loe os sofware tequsémsnss pecicolll used to chock the consistency of the syatem. A requirements database Te requirements speci {Festa using 8 CASE tool that check the entire requirements the - latabare using rules of method or notation. The report of all iv. Requirements review ‘inconsistencies i identified and managed _ 8 The review proces iscarried out to improve the quality of the SRS. 1b Kemay also be called as requirements verification © Formaximum benefits review and verification should not be treated Segdiecreteactvty tobe done only atthe end of the preparationef §_Teshould be treated as continuous activity that is incorporated inl the elicitation, analvsis, and documentation,software Bagincerng i Tower | 2 a licication procedure A general elicit steps 2 a 4 5 Problems in requirement elicitation : WGaeRA | What is system documentation ? Explain in detail. = ‘The five typeof documentation manuals required by a system are: ‘ 25C(C8MT. — ion is the activity during whieh so re. expen and reveael rom al ei Requirement reirement are dove requirements tts source may be market anal spans techonage arused to invoe the user on the bass fev volvement required. system requirement documentation, custome jon procedure contain flowig rdentifving relevant source of information i, a Use b Customer € Determining what information is needed by asking questions. “Analyzing the gathered information, looking for implicatiog inconsistencies, or unresolved issues “7 Confirming our understanding of the requirements with the user. Creating requirement statements. Domain experts Uer ie unable explain his requirements Less knowledge of technology and may not consider what is posible Use of eitferent language by developer and user. Lack of sil in developer. User snot providing seme information due to some reason, Requirements are coming fom different sources. Sten dacanetation writen tet or strain that either ex ‘how system operates or how to use it. - Sytem asta Inderal be euro raps, sd instructions pertaining apie tothe design, amplementation, and operation Sratom design documentation: ‘The purpoue of this documentation sto provi pe cows provide technical details SS ecentcan be drivd feted prods anal ‘Sytem design documentation consist ofthe following: 2ac(cMTsem4) iw Software Requirement Specifications (SRS Formulation of the problem Fenibl Overview ofthe system, is sub aystem and ther interfaces ‘utput report and screen displays Input and source documents 6 Datadictionary software documentation : Software documentation consist of following Hardware specifieation : Description of equipment, peripheral levies, communication hardware 1h Spotem software specification : Description ofthe operating System fh other aystem software sochas DBMS, screen formatter, ems generator and communication software. . The problem andthe system models are essentially built into wind of analyt and direct aces ly translated fr the mind of the ana to 2 Formal approach / structured approach : © In structured analysis techniques, we use functional based ‘decomposition while modeling the problemsiititiinmal ene bed =) © Ri a en eects a act enentedmedeling wees approach it ch proba riod with espe to objets ‘eruceared analyst and design cechniques (SADT) Seed rie SA jnformation processing svSteMs En ceey eds tt pre dl eT napa el eee eT nemiirimdtmtal eal Th yt tent a ne ce eon Sarah «eee minceeroacic cl Teasers neti oe te en canes cat os 1 Themain eeu of Rmedelingisthe data items in the system and | ‘the relationship between them, designed 1 aims to create conceptual schema for the data from user perspective, ‘Que ZB] What is data Now diagram? Explain rules for drawing stood data flow diagrams, Taawor 1. data ow digram (DFD) ‘0a apical representation af the flow data thrvugh sate ene stanton 2 _ADFDalao known as buble cart has the purpose oflarifying system ‘equremenisand dentifing major traneormationg, Tis graphical tool bene it presets pceare 2120 (CMT Sem-4) Four simple notations are used to complete a DPD which a ie, Software Requirement Specifications (SRS) se ree follows Data flow : The data ow is ued to describe the mare of information from one part of the system to another part. Flows represent data sn notion. Itisa pipeline through which information ows Proceas : A circle or bubble represents 2 process that transforms incoming data to outgoing data, Process shows apart of the system that transforms inputs into outputs External entity A square defines 8 source oF destination of system, data, External entities represent any entity that rupplies or recive {nformation from the rystem but i sot a part ofthe system Data tore :The data store is used to collect dataat restr temporary repository of data, Itis represented by open rectangle General guidelines and rules for constructing DFDs 2 ry Choose meaningful names for processes and external entities [Number the processes ‘Avoid complex DED, Remeber that a DFD is not a Now chart. All names should be unigue ‘Make sure the DFD is internally consistent. Processes are always running, they do not start or stop. Alldats lows are named, [Numbers of processes at each evel should be small (not more than 7), [A pracess numbered in & DED is leveled into n processes then each new process is numbered pp... respectively All data flows entering or outgoing from contest DED process should ‘Als be maintained in ts leveled DED. should not contain loops Itshould not contain crossing lines ‘QueRi0.] Develop a level DED for the library managementSoftware Bagineerin DIAC CNT emg) ‘and ita rue: Refor Q. 29, Page 2-110, Unita, Data fow diagram aaa: Lene 1 DFD for Wray management wyaten ie Tor) tite and author of [trtiesser] See ewes ook nae a Gtihe user ‘eat | ein List of tites referring to the tape ig. 2103 ADFD dering implied ibrar information rete, In thi DFD, we have assumed two provers Laver a book User requests abe. 1 Retrieve the data rom database, hele, it of authors and at file “© Book issue and update the borrow list 2 Search oy topics Unerrequst atopic. 1s Retrieve data from database i, hit of ites and list of oes Display the ist f tes which are referring that apc. BHAT] whet is» ow chart 7 How is the flow charting Aechniques uneful for software development? (oertrere ts are sero.) faire Requirement Spmeictions RS Hele sam that represents an algorithm, workflow of hones of varioua kinds, and their order ry ve h yresentation illustrates » solution model to a given ‘This dageommatic problem: low charting techaive “ etna: lo chara ar ine werkig moe a ening 2 M ergeam and somtware ayeteros 2 Documentation: rogram de Pretng organizing, ri Soro oe craig: Pow chats ue the programme in writing the Coding: Per eek ich vrupponed oe aD THT Se TOAD Sretdeetitosly vbgging The errors in a program are detected ony afer ie * en iter ‘These errors are called bugs and the process ra debugging othe debasing a ttoling beating tod se uneul for software development in following sumentation consiat of activities, ach Mand maintaining all related records of execution on 2 comput ‘tremaving these errors is (tow chart acts aa impor f pictorial representation of a ‘1 i an excellent communication technique to 1 programmers/people program. Therefore, Captain the lie of program to ot 1 problem can be easily done 6 Analysis : Bective analysis of loi ‘rith the belp ofa related flow chart. 1. Testing : A flow chart is an important tool in the hands of « Frogrammers, which hes him in designing the test data for systematic esting of programs. THEFT] Distinguish between a date Now diagram und a flow chart with example. (ARITU 3012-15, Marks 05)21BC (CRIT-Sem.4) Flow chart Data flow diagram (DED) i Flow chart presents steps to complete a process Flow chart does not have any input from or output external 1 | Data ow dingrasn presents the flow of dota, Date flow diagram describes the path of data from external sour to internal | ae processing of data ix |The timing und sequence of the taking place i's particular | process is aply shown by a flow | order several process are | chart. takong place simultaneously ‘sot described by adata Dow gram 4 [Date flow diagram defines the functionality of system Data flow dingram is used to deseribe the path of data hat sill complete that proce | ‘Types of data Now diagrams area fallow Physical dataflow diagram a. Sytem flow chart © Logieal datadow diagram}, Data ow chart | «Document ow chart a 4. Prograsn flew chart DFD example for student administration Flow chart shows how to makes system function Flow chart is used in designing a proces Types of flow chart are as follows Software Requirement Specifications SKS) 216C(CHTT-Sem-4) Wigan, ‘Que RHE] What is entity relationship mode! ? Describe components of ER model. Anewer Entity relationship model diagram : ‘tsa detailed logical representation of the data fer an onganaation and uses ‘ree main constructs data entities, relationships, and their asociated axtributes. LL Entities: An entity iss fundamental thing ofan organization about which data ‘nay be maintained, An entity hos its owa identity, which distinguishes it from other catty. 2 Relationships : ‘Arelationshipic «reason for associating two entity types2arcicean. sNware Requirement Specifications (SHS) stra Bogner cart som) So “attributes a Ithas explicit linkages between entities 8 hens ope haresett tilganeccned iit Anal JE nthe ER model its posible to find a connection from one node al och ety Peeters ton ea tata intent fy se Se ere Spat a canbe Diandvantege oO see Set, Stent Name, Phone_ Number 2 ine it preeion 1D. Employee. Name, Address Limited relationship representation. ne . i Norepresentation of deta Gos glade! iv, Loss of information. How is « date dictionary useful during software Na Component name | Symbol Desrivion eens] 1 | ectange Hepeteni enya development? , ss at en data dictionsry definition ? Ellipses: Represents attributes ‘What is w data dictionary 3 |Diamends Represents relationship \ | “ ‘a. Data dictionaries are simple repositories to store information about datas doen DED lias Tine arts tsa * sets and entity sets to. 1b. Atthe requirements stage, the data dictionary should at least define | stn nate date tema to ensure thatthe calomer and developer weet ithe same deftione and terminologies [eae ieee eoesnts ltl acetone 5] Hepes 2 Melos, 1 The name ofthe data item ircal-explanatoy © [Dastaetipes | ¢-— 3] Represent dered 2 Aliases include other names by which hin data ite cae =a? | secon {eretample, DEO far Data Batty Opersor and DR for Deputy % rectar yresents weak entit eter. Deserta [Tagen re eter 4. Desert Parpose i tetul esrpinf wha he data TT = iteent ued ror why here | & [Prebeliaee rarest 4. Related data items capture relationships between data items Lt Tia relationship eet for example, total. marks must always equal to internal marks “ plus external marks. 5, Range of ales records ll pombe values, fr example, tal Fig: 2181 Components of ER diageas, : ‘marks must be postive and between Oto 100, 6, Data fows captare the names ofthe processes that generate or receive the data item, If ata item is primitive, then data structure definition/orm ‘captures the physical structure of the data item. 8 Ifthe data is itself a data aggregate, then data structure ‘defintion/orm captures the composition ofthe data itoms in term of other data items, 4 The mathematical operators used within the data dictionary ere defined in Table 2.15.1 TERETE] wat are the advantages and disadvantages of Et diagram ? Answer Advantage of ER digram: 1 Wiseman to understand with inal raining Teeter ‘uel cn be ue bythe database designer to communicate desan