gramme Cask) “+ Documentation + "Procedures A Systematic Collection of - | Programme development bractices and techof gues - Software engineering 4s “Tmpertant becquse Shecitic oftware %8 needed Jn almost every Todestry . in tn every — Eel ai [business , ‘ond for _every funcHon: why (Study Software _ engineering eS CEE eee aa 0 lo develop a large 5 Software conly after Tearnin | Systematic _technfeves that are being ‘used in the tndustry. To effectively handle complexity %n a Scftware developn... | problem. : feo nieae - a =I oes e Not enough time eo = lack of knowledge @ wrong motivatten © Insufficient Commi tmentTita Glole rea ra \ i C Toprevement future loge —F Process Canagement” Blake x ; 9 [heving carve * eit } & = > iW it | | Characteritis of BoPware : t (| Seftuore doesint wear out Burn bhase T (wear oul phase: ait (iy [Bettwore WS ret manufadured. ity |) peeeseaatg of Component (i) [ste Ts flexible. i Categories of Software Appitcaiton Slo (198 word, M6 Team) (0:8, editors, drivers) (weather forecast etc.) CAutomatic machines, microwave ele (ERP — Enterprices resource) Coatabase , video games) - Today's general Gofrware Chebwork CHtme, 83,36 ete) Cmatiabs, Stmulators) [Syste Ble [Reale oles Embedded Sf ‘Tpustness SJ TPereanal Computer Sjeo ) Wireless | Web based 6fo Engh & Gcientifie sf mndatone and, deltviries Teamatitig t new ad" The verstons iof 6) achieve 1. - Product & Process G ‘catput of process | gfw process & product “metices D Froductitly & Effort module B S|& Components —& Castomtzed S| Tog, Sofhware ( divided ) ~ sprajed monager > =: Techateal teams: + Customers * Software life Cale Models” si development process” A process of di SIG déveicbment Werk into Smaller, parallel on S+ebS of Sub- browsses fe tmprove desian monegemert- TH also known a5 4 Sefrwore deveropment life cycle (Sdic) % Ae SOLE Ts represented gophically by raising various 2 fe eyce and Showing the transticn bhases « This grabtical model ts usually oy a textual description of vertous nes shat need 40 be carried out during re that phase can be considered Pere |< mrerra rooet ) pon [Reautrements analysis And Specification J “Design a cough ‘Unit testing (Integration a {_Sgstem testing oo - Feahosatnance on Operaten t || different 4 divide define al! ws n Feeutremente tn beginning net Sutfeble 40 access model any change working version - last met for large projeds Read projet 4 rarely Sequenifal | @acliest Soue approoch that was use for S]u develefom | example of Sevential model: So Ys alsa referred to 98 4 Mnear_ Seavential fife cycle mod: It 1s very Stmple 4s understand and use: In a waterfall model , each phase must be Gmpleted “vefore the next phase can begin:4 When Should you uso Ht? © Rotutoments are clear and fixed that may) not chy @ Tem am no ambigees reeviroment: (no confuse © Th fe gpod fo ce thie model when the echnolagy 1 teall_Underotocd: : > The Project 1s Short and Cost ts low © | Rick 1s Zero or minimum: TNeREMENTAL PROCESS MODEL ) ey eres * | Reostremens ore clear defined precisely i L, No confusion about réouirement - % Delivery of funcienolity | pases debencing upon +e prirorities of the done fh multiples / feecirements. of Every eycle Ly deliver the Semi compicte product | with oted functionality TT Lost cycle. $complete bf dim of Tem ig Iotted Fanctionaltty Quickly Tho Sasi Criteria or the to deliver fay TTERATIVE ENHANCEMENT moneL > || Phases $ Game phases a5 waterfall model bu they are present with less restriction _—| d u occur ty Samo order but ta Several cycles Reavirement® 3 — Majeur fanulrement are Speci fied by the customer at beginning || Tncompiote rearirements are never, a reason for multiple cycles Pritorities are the Reason for multible cycle t— os an ae - ae designs —7 TauT )—> § 187; one wow A aw ae:(pene be 0) “2A APPLICATION DEVELOPMENT ai oe : = {oven ace Get over) 1, “Anetall the Slo" + Acceptance’ testing + | Developed by 1am — Trateing of use Batld Ropi Betype | Gatatin f YRetined 5 [7 AS (ong 68 Ree, Arolfoed Ne | Lee jaint team of customer & developer undershards A reviews +he gathered reams L, putomated toote_may alse be used « castomer is present In every phase fmajeur goals of x0 motel) — 10 decrease the Hme taken and the cost treurrod te develp Software System To Hit the Cosh of acominodating change feovest Communication’ gapicbjico ust Reduce scandy developer _i esign—> coding —+ testing i bE Product to released moneren Ta ca _ cee mode) == rid)=} ae Evolutionary “model 4 combinalion of Tteratve and “Tneremoniel model of 60UC First Tmplement a few basic featire + “Treremental model - ‘and deliver to customer. Then build +he next pant unkl the desired System 1s “tally. realized. “Ueratve model 15 allows to ace: eater phases _This_model_ fs used tahen the “customers do not know __. 4h@_exad_projed reevirements beforehand «In __this_medel, @ prototype of the end product 1S first developed , tested and refined as ber _ | festomer feed back: fepeatediy Hill the final _ |} scroptence fesults thto \ 4 a Neer cecercred j £ Testing by Cosborrer) a ined asl Reoutrement gatherin eres A LC | @utck deciston | design Reto Ree, Mocorboratton ) as esting) 7 7 Cmaintanene a eae x I Te Rodis of The sptal ai ang pink represents the expenses (Cost).+ |/Transitfon phase — deliover sfeo trerement bo Y —__Santing) § Comma ion} Elaboraton J prensa. Gelection of Life cycle) —_ J Reavirement - Develebnment Feam 3 Users 3 Prajed ype ard assodahed Ask = i i The UPM having “Inception phase, Flebaraten phate, It Construction phase, Transitien bhas@ and preduchen phase i + freebtin wil vision document, use case rrodel Mal), Teta! process + “Ing to bulld Getta case Model + Eloberoffon — any | Ee otagram a comblete the use case mete! | : anelysie model, Sle orciter.. descibifon. | — ‘Sho Prototype twerkFlew, rfilestone come in Cloberalfon - + a a eer eo — al Rs Software Roavirement Specifi * Corattucfion — Integrate , test pions, test coses rode! = ——_—s dene In ronehucher- aai Problem “ Reavirement _ Fee analysis ses 1 engtcseting Reo, decumerta ten i 7 Ree, review oe ¢ verieatton | Reauitoment Eltettation iL TPeoutroments titctotfon % perhaps the mest difficult, { [reste error= prone and mest ‘Commusteation ‘Intensive [Sj developnment. Foundation 3 misunderstanding | conéiicks a Communication cc Etfedtive communication bles Costemer— developer Developer Questiong Customer resbords cross Ouedion’ Both ore efficient to fjoccar Regt, Engineer ad a5 mediator 6) It con be Succes nly through and eedive (ustorer ly throug develober partnership ea is needed 4a know what the users reali need | Reavitement eltatfon methods FS | Pew of them ore | listea below ¢ 4 Toterviews stemming Sessions & _faclttoted “Appicotin shed flaton Techrieve (CA Ai Qvaltty Function Peblegment (@FD) Sse case approach _ team Corred approach 3 LL, Both bos Should be, open inde. Skills tneie demcin G0 domatn difference _ uo customer and dovelebm.. | Fast is ‘team twork appreech. ex pedaons [ Atentn gto be bridge the gab ble undestandiog aod+ Goals of PAST deam = | Problem Ideniifeatfon e Geluffon reecirements: Propose elements of Solution a «| Negotiate different approacs 4 OF Cavdtty Finetion deployment) © OFO 4s Guatily management 4 techniave 2 Empbasts of @Po ts maximize the Customer Satisfaction + 60 helbs 4a achfeve Structured planatng of prod by_erebing development team _4o clearly Spedity cestemer need and expedatfons of predud? + [s _Tupes of reatromerts 2 known reeutrements § These requirements are So obvieus customer need pet Opiielty “State them unknown regutromente § Th Hits objective and goa! Of the bebosed Sefhuare are discussed with Hx custemer © und-eamt reoutroments $ Te Yneludes featucos tint Are beyend Customens exbeclaltons | do”? A FuncHfonal te@otremert Th defioes the Duality defines a system or ths aitrtbute of 4 Ses combonent Systern TH Spedfies “ what Ft placos constraints Bhould the s|u system on * How 6hould tne Slu systom fulfill I H | the FuncHonal reo. ?". Funetonal reaciroments + Specified by techni are Specified by User beoble. + 9s mandatory 2 Tt ts nat mandatory IH 95 also known of 4 context Diogtam. THs designed 4o be an abstrad view, Showing the System 95 9 Single process with Y4s_telatfonship te externa! entities Te te presents the entire system as o single bubble “sith Input and output data indicated by Incoming} eutgetag. arrocss Providing « bread view of the System and estecral entities Yn an easily digestible way. Because of || Ts Simplicitycondudted Yn order +o determine whether we are getng 4o Implement the) Sofware or not four Stages of Slw Projed management System: as gives a_concuuston of whether 40 go ahead |tstth proposed prajed as H ts practically feasible or te Step proposed projed here as it ts not right] Aeastble to dovelop or to think | onelyze about broposed _prajed_ a Characteristics of SRG ee cosre oo 8 Neri fabio 2 rambighous. + modifiable Complele tw Traceable Consistence 7 a Prtvorthy _ Feasibftly Study sone of the Stage among important | Nature of SRS What the Sofwere fs Supposed to do? ‘xterral Interface “How does the Softeare intend With People, system's hardware, other hardware and Sfes What ts the Speed avai labfity , reshonse tohat are the Considerations fer beriabtl Grredness, maintainability , Securtty elfabsitly ete Design constraints tmposed on an Tmblementattan & Bre there any reavired Standards fi effed, Implementation language, bolicies for_dotabose Integrity , resource (evits __cheratieg environment ete| | Reauirement management planntn Date: cceaviremert ell not change re matter, they detive trom the Core activis; “Nolatle Peevtrement Ceahfeh are MMely 40 change, muhioie reevtremends changes acc. to H System) L-5 ptppie effect The ‘pple effed metic Shows what fmbad changes + ‘HII have on tne rest of the System can be Used durtag |i matntdinence to keep He analyzing , So that Eng on c6eetremen's ering feams always have current ard Labbreved reauirements. Da Software Frejed size estimation technfevcs t an EsHimaifon of the Size of the sf 16 an essential “1 pork of Por oF Sfio prajed managements i helbs the brojed “manager to. her predia the effort and Hime hich util be needed 40 bifld the: “projet | Some of these are & [The units of Loc are Varlous measures are Used Tn prajed Size estimaiten- Lines of code _ Number of entities In ER-Diagram Tolal_number of processes In detailed _ = dato flow diagram Function points @ kloe ~~ Thousand Une of code oe NLoc - Non-comment lines of code 2° kos! 7 # || Loc counts the tole! number of lines of || Source code to. projec « oe iproduced from user’. pet oF view i G whet the User reretvo. from sj + lahat the user eeevest from 5| © | Focuses on what fancltoraitty Fo being deliovered TILE $ Internal fogiegl les aro External Interfaces jee | | i oo - AE |) A System hos S types of fundfonal unite 3- 4 || Internal Logical Files (ILA) 3 + The Conia! Info ar legicaily siclated daia thot 15 present utthtn the Systems: | évterna Inputs Ce) & datal Control tnfo that Comes From outside our eyttorn External outputs (£0) 3 3 dota that poes out of the System after generator IL External Enavires (€0) 5 i 5 Combfration of JP - ofp Resul gin dota i Tetrieval: ET |Eole@ 2 Transodianal furciond type WF | e1F 3 Data FuncHensl *ybe (COST ESTIMATIONS maton faa Statement that gives the value Gost Yncurred fo the eranutachuttng of "Finished goods: - - — Sn Sly cost esktmatfon : C model 7 : _ Stotic multivariable Static SInglevarable facial modelALL. Ghatfe Stngle varlable model & [Uses th meal fo efees an eamnon ty go the desired values Such a3 Cost, Hime and effort, 2 And these all debend_on the Same variable used as predictor like Sire # Lt Size # b & constants “Wwe have on exemple of 4he Static Single varfable model, kes SEL model — used for estimating Software prod | fovaten of this model is given below; i ul (ferson mentts ) (no. of page ) Cduratian | B04L 08° Ug Loe Effort 8 Amount of labor that will be reoutre4 4o complete a task Th ts peasured To person-months units Schedule & Atmply means the arrount af Hree Teavired for the Completion of the job Baste Cacamo model - E= a(ktoc)® fia INTERMEDIATE cocamo Tt frciudes 1 Cast predictors and the basic + Cocomo (Constructive cost Model’) 1s 0 regres: ston_madel hosed on Loc fe. Number of Ines of cade. _ | ef ang | dukorce of the Cocamo ¢ | Bthedule ff [1S moost drivers for Intermediate Cocomo are & The cost _deivers are grouped thio cate gorde { cna | compaler Athibutes 3 | Formulae 3- it Effort = Product attributes ¢ fred {us refobtrky — Database stze 7 Produat_Complerly = Execution Hme Constratads ~ Memory Storage onstrated ~ Virlual_ machine Co strat ot ___~ Computer turn-around fime- | Personal othtbutes 3 = Analyst Copabtltty _= Abpttcation experience = Programmers cpabtitty ~_vIchial_machine expefience | ___cprgremieg rgege. expen | pad obbaee fo = tredern programming _prasices = Use of Slaw tools - ~ Reautremert dovalapnment Schedule Duration = ci_Ce) ~}y module Subsyotem sp | RISK MANAGEMENT Types of Risks + Dependencies | Reautrement “Isstiec | Management Issues lack of knowledge lack of tasting Risk assesment R= Taentication R- Arelysis R- prioritization ragpment_ blaming R= renitering Re Relation:Date prose the designer plans ‘how? a Gottware cesign System Should be. developed In order to make Functional, Reliable, enderstandabie. medi fable and Jinables oe The purpose of design phase [te 9 problem given in SRS derumont: to_produce & Sola, Destante properiee af 4 rredolar Bystem thelude + coubting TYPED OF TF Bala expitag | a A goed design ull have low coupltr Should be carefully Specified th order to keep low value of COUPLING Best (Tow) * Passing of data . | Stamp Coubifng Control Coupling ft |__ External Coupling Each madule tog well defined Subsystem thar Ts potentially useful tn other appiteation Gormmen _couptin: JS Cemimen costing modules can be Separslely comptled and Stored In a rary. Module Coheston 3 SS i - “degree 4o which the Meddle Coupling i __Gupling is the measure ‘of the degree | behucon mredulee + loosely coupled Sbares @ great ded of dependents ne Ynferconmection At all> 4 Mtghly coupled fardionaliy related: © Shared dato Content Coupling worst (High) #_ are module mies eSion is 0 measure of the elements of Q module are tedule _coheston ond TYPES of COHESION ¢ An important design objective ie +> maximize the minimize the module Coupling - Functional Coheston + _ Seoventiql Ghesion Input of Yo Single Functional ont - X ouibute Same data which farm\ (i) Precedural (iy Commurtcational Cohesion = | Wiand oY bathe chante Ten the Same Inpat data af contribute towards tho Sime outbat data: Cohesion TH occurs Tn module whose Tnstructons although acomplich different tasks || get howe combined because there te 4 Specific oro Jn which the tasks te be completed _ Temporal Cohesion > Yoand ¥ both moat Perlorm [orcend the Same legteal Cohesion 2 cheraffon | Cctecidental Cohesion Yeand ¥ hove ne cencephual other than Stared codes Functfonal Cohesion Beeverkial Cohesion . | Communicatioral Cohesion “Procedural Coheston | | Temporal « wars Crate) jesign approach: [[A top down appraacn st __jmeans. [Sub-paris: | archttectural Strudture of the Siu System: jedule 4 Sima2 S-m2. ply refers 4o the “ decompos [means breating doun a componest nto Sub components “Tn athe op don approach, testing fakes place from top 4a the boHom which follows the Centre! flow pr_ ae BoHtem- vp Approach land the fem refers 4 the Synthesis. i Wats opiappraach [ta appostial et oh deur appreach | Botom-Up Approach ¥5 an Integration testing % “cahlch esting Fakes place from bottom fo up # {, - fs lower-level madules are tested K gher level modales then are tested [A hyped wiedel ts @ medel twhTch 15 develabed ‘Combing hue Weditional Medels of SOLC+ The base models can be anyone [tke q Spiral model, VAV model , Prototype model, ofc: h nea Date: Imodule A module 8 [meds fo the miaale: [a - AK SS ae module? medule 3 _ecdale 4 (Tuo type ahjed Oriented Design [ees PaneHon Gtiertad Design. Fanetfon oriented Design tea metho jo Slur design Whore she medel ts tocombosed nto a get of Toteracling Grits: or wedules Where aach OnE OF tmodule hi iy defined faneHon Th The system 16 a Date > a Dietfonari es,| + pate Dtdfonartes 3 4 data dietfonary lists al) data i elements appeaitng hn the OFD merc ata system, For examble £9 dala dieMonary entry may cantath sy the data grosspoy Consists of the ports fegularpay and overtimefay: he, 1 else Suite break Gnieol Flog ~ Leo ~ # "Pseudocode % normal engiish language, Contains form # | Th has 4 layers ¢- [| Suboystom layer | eless and objet lager Message layer the Ymplementaten = Decision Count tome ate Se@vential combonentae f Acittly Diagram "fF Reavest] Renve order out il { Grder accebied) > wna | O— [Prerer] (ie Dawe ff Geavence Dtogram A Sa@vence diagram Shous Whe Seaverice oF messages exchanged by the Saf af abjeds perfarm a cortatn task 7 _sbjeds are arranged horizertally across he dtagea =? Vertical dtmension represents Here — Ave | re, called a lifeline, is ottached to each object ct aéfor. + THe llfeltne becomes a brand box, called an activation box during the [ve acinatin bertads [& — ital slate/ Date! i t = Date TA Software metic ts a measure of Sft characteris lies tahich are measureable or count Planning work Hems measuring Froductivity Done: / 1 [to metfces con be clstitied nts fpo type as follows + These are the moasures of various, Produd mettces stp charaderisHes. of the || Glu, projed : [The tivo Tmpodari Slu chamdlerietics are. + Bite and Complerity of Soo @ _Duolity and Reltattitty of S[tor These are the measures of vartous Process Mehices ¢ oftware metices choraderisties of the sto development _ process: dynamte mekices They are used to measure the charadleristies af method Hechnioves, and tools that are ustng for dovele bing Software: Benotils of Software meirfces & I The goal of tracking ond analyting Glia melrices Te fo determine the Suslity of the jad oF urren' + SS el _ Size | Design Gentrol Flew tro, toeighted ste Slun Scion Te aa T memes Fogel ans t = | — as fo Money & ko! Loc Toten Fancion 94 betes Process. Improve: that Goality ¢ at that @ualtky and Predict the Goality ence: the sis developmen projet %8 Gnplete. © | TF makes the beHler contrel, Planing and } clear vicitl TH helps 40 Therease the proce+ | (alstead’s Slo mehices 4 Token Count & - + | According to Halstead's f° A computer rogram ts ay Considered 40 be a Gllectfon af tokens which moy i. _ clossified 98 elthee operators or operand + All sJw Science metrices can be define In terms of [hese baste Symtnls- L_sThese Symbols are called 95 a token “The baste measures are 4olel oken used N= Ni + Me | Program Difficulty $ —error-prenenes: (6) A number of Unlaue operator 8m program © = (m4/2)* Cora/ns) tire 3 Sno re L ried program length To denoted by N” N? = ndlogsnd + nalegan, [The folowing alternate expressions have been bublished [4 e6Himate program length 2 NG = legs(t1) 4 logara1) @ Ne = nix log.n2 + no x log2nd 2 Nes nd » Sort(n4) + maw sqrt (m2) 2 Ns = (ms togan) /2 =F) Program Valage(V) The ontd of measuroment of Volume fs the Standard vn for Size * bts” # | Peace leet Co) The value oF L “ranges bi? zero and one. Le vary Potentfal mfntmum Value - volume of most ¢ SucePnat ||__ program in ushich 9 fprageam can coded €SHmate pregram walye~ ———tevel| et entdered = rsernes 5 tancton —aedaration are ma {Comment 3) Weeat vartabl with the Bame name In different Tunclien are Gunted_ae_unleus aberander ~8) "FuncHen ais are Gnsidered as Sperators. 7) TRI Fhe Gobtng Gtatements do chile, it else Tela are considered ag aperatets: ~@) | Suitch case, break, continue are alsa Heated a8 eberabors TAI the reserved wards (ke rebut, delault, Gantnue ele are considered a5 aberators: i = — = | All tne brackets, commas & terminator are sidered a5 lene “Ore constdered | Sttudure & Ghudure vanable a6 covsidered ai " oberandé vA the heth direcived are Tanorod: a array. Strcknes L- - 6 eberators -