mocremental Softiaare developrnent model. Pornd | out benifits cormpared to yooterfatl model —T am Build . 2 5) Cong) rgomain | Quid? [Rezatverents Ber — (Testing — Celene) 1 at e ui e > Cietognad)—Clesting }-> Cinpleerato) | fig’ Jncremental_madel. The incremental software model, also known as erative model” sy an approach to software developroent yohere the entire project is divided into smaller , manageable part called Increments. The development Parprotess ts dwided ir [multiple Uerotions with each ‘eration. buildingEe Ted of fate eve are some key advantage of the Tineemenkd model over waterfall rnodel {| ci ry Eavly delivery of funchonality ‘- The oan | model allows fer the early delivery | of Working __panctonality, vi) Flexibility and Adaptability |- The Inerementa Jmodel 's more flexible and adaptable | to changes 0 requrvernert . 4 I] | fi) | Jncreased Collaboraton !- The incremental model promotes increased blw developers » users and Stakeholders collaboration Phroughout — the development protes- Cont nuous “Improveroent With each ierahion, the incremental model promotes continuous improvement ani refinement the software.| B Osea ee ==. " _ move ah ee t) Define Software gineering Aloo explain Tyhe eseenhal attributes of O good Softwar. >) Software engineersing can be defined as the | Process of designing , creating and maintaining | GEN'software. TE involves copplying engineering pees bo | principle “Fo “develop sof bware That ™meels = | Specific needs and Pui forms tasks | CHectvely. Jt focuses on Using systematic | and organized Opp roaches to design, tode | and fest software, ensuring i+ usobil ty , ‘Essential athibutes of a good software are: [Functionality !- f) good software should pli iB inkrded purpose ard provide the desire functionality fo ynee! the user's requirement. i) Pliability y Reliability refers to The softwares Jability to consistently per forra ne eapecked and deliver Atturek resulds. Usability - Usability vefers to bow easily o intatively users can inka woth — the SoftwareDate os ae as velaks. fo how wells yesources , Sue) power. W)C fficieney = Cficiny ublizes Sys ee [the sofiware ; pr ot esssng Jas memory and V) | Seeunty * Security Be peey ; = ean dala, preventing unauthorized access. and parang Fhe inkegrity pt the 30 tware- gyepers TO NOW vi) | Mainteinability * Mai ntainabi lity CO enhang) | easily the Jot hoare can be rood if lor fired 2 62: Short noe on _functonal requiremen# and non - pandionol _ |, Sunctional requirements describe: What | the Software System Should do the + Fhe Aefine the~systems They Aescrile [speafic. Faaks it weeds . to perform , what the systm should do, fo met | He need of ON tk users, 1 ; Et, typi cally fo tus on the behaviour [en ~ functionality of the system 4 he thought of as the "nohat" can| \ ) —— as | lof the system Examples ’ |" The systm should be able 40 Process 1 online Payment” | ¥ || Non ~ functional requirement on +he other hand doting the qualities That the Systm or sofware should Possess. They | focus by eS othe systero should — perform Lor behave, yather than specific Features | They can be FhoughF a1 “how” of Fhe | syst. ‘ i | Examples + || The Systm. should tespond Fo user athom Tyoithin 9 Secondly . ) Al Explain Cocomo model Software Engineerio techmigue. Wdhat are the ctors = that” effect So] toare Pricing P- ) 2 |The CotoM0 model 7s a software cost estimation techniques used in sofware engineering, COLOMO stands dor Conshrudive.fm = = Cat Model “IT helps 1 estimating the effort, Hime ard vesourees yequtre to develop a software project The (OCOMO model eonsides Various feck > )) Poduel Factors “These factors are velakd fo the charackrisfes of the || Software being developed. They ‘clude things like the size of “Fhe Software, the compleni ty of the yottware. 1 i) [Platforrn fects © “These fackors arn veaked | to The environment in Which the [ Software vill be cleveloped and exceed _ iit) || Personrel Factors | These foefors are : related fo "the. skills and experience of Fhe evelopment team—< Fy] Size and Comppleni Ty ee Date Page we The factors that effect sof ume pricing The bigger and more Complex the software Project, the nore elon and wsesourtes if will» require, | which Can increase _ The pricing. iD | Platform and Technology + The choice of | Platferrn and technology can rMpact the aleve lopment effort. Some platforms mou have limitation or require speccalized . skilk, | whieh can affect the Pricing , Team skills and Gxperiene > ~The exper Hise and euperience. of the development team can influence the efticency and productivity of the project, wahich can impact Fhe” pr icing ,23 Hee Th RSS jagrom Cuplain $ of twa aw dhe —_+— 6 di ___ | mangement — oe ae ss [Esa takai] Managemen! reparation Vv TReies Planning a ee ic Preparation _ ] ey ee a Examination 4 Exit Evaluation [The software veview Process bb | systematic eyaluakon of a anak product to assess 1B quality , Cerrecines compliance Wi th Speci fieyelevant aspects . The Yrnain goa of | weweW process Ty fo Identify and | veekfy cal any defects before he | Sof fasay¢ ts released. FO users || The software review process typically | ' volves the following steps | + . : Dd Planning | + Defining the objectives , scope. and criteria for the review , and Sele cting the appropriate reviewers. an in) kick off fb Totroducing +the software to the veviewers, Providing Mecessary guialelres and setting O seview Schedule. 7) Trdividual Review - Each reviewer . examines @ software independently looking for defects jinconsistencies and adhere to standardy ar ee ) Reviews meetings 1 The reviewers come —; ' — & oe aa ee aeee eae — i together to Aiseass Fhely Findings E Share obievalion, , and ident fy | Critical vssues Thad reed attention, vy) [Fssue Pesolution | The idennzree 'sSues @ Kesoluy are assigned to appropriate teams for vesolution. i - 1, } e353 ONE vi) Follow-up | DFer the issu addressed, A. ye-veview may be tonducked- 4o ensure the effectiveness of correction Seftware reliability refers to the ability OF O software systero to puform i intended funcHons altho failure Over Oo specified pertod and under speci fic conditions. J+ means al the sofware noorhs as eupeckd doesn't crash oF © produce incorrect Tesul B-— SSS pera a are “To ensure Software reliabihhy , derveral Measures can be taken ! i] 1) | Testing = Thoroughly esting the Soffware | through Robniques Tike unit festing , [Systm Hsting and acceptance testing | to unover def and ensure «# | robustness. _ Fault Tolerance )- Building the Software [70 handle unexpeckd errors gracefully, Te that ¢F can continue fo funch’on without Causing Major disruptions. J oD) Monitoring Continuously monitoring the | software 17 veal- Hme +o oletedt any anomaliea » and taking appropriate ations +o prevent them from escalating Into foilures, iv Cro - Handling 1 Implementing He otive ona @yyvor - handling mechanbms ha Ca ue Ard handle errors gracefully ) Provids useful ‘formation fo users Ks]. — uali'ty Management. b . Ottvities and — processes aimed at ensuing that sof tware product meet oY onceed specified quality standard ~ | and user expectations. | Key aspects of quality Management i Planning » Defio'ng quality Objectias , establishing quality criferia C Planning achvities fo achreve and Qualify throughout the softwarett — riers cree iecinae tne traneameererrecer tmp rennmmmapensie Standards To prevent dof and ensure adherence 70 Quality requirements nt) 1G uality control i Monitoring and | Measuring — the quality of software roduc during — development : Identifying | clefeck Pom standard and toking | Conrechve othHom dy address them. iy) Confnu ous improvernent = Promoting a | Culture of angoing improvement by l| collecting feedbacks ~£, | What do you know about Software maintnance ? Eyplain also software yeveyse engineering , maintenane yefers +o the process of keeping a Software syakm in good — working condition afer it _ hos been developed. Just Ihe A car needs regular mantenane to run Smoothly, sofhoare alo requires eNQaing|| at | functon properly : | There are hen? typy 9 elt | malntnance acne |— 7 i ; 7 5: ean i Corvechive maintenance — This Tnvolves { That users [Bb fixing bugs 07 errors | encounkr rohile using the So | Its Ike Yepairing a Broken part ry | q tar T wy) P)doptive Mmoinkna nee GB Software nena ae to. be modified to adapt +o | Changes in i445 environment , Fy) Per fective mainknane | This Type of maintainance fotuses on Improving ies Software 's per forroanee Lefficene Or ~UWser experience. oaIv) Preventive mmainknance So f4wsave Mvolves _maling changu fo prevent future "| problems, alieak Reverse Engineering / Software Reverse Engineering ‘3 the | Process of analyzing a software Program to understand how it t works » even if the origina! source | code 2 not. avorlabe, Its Tike Frying | to figure out how oa machine or device works by examining it Closely. Sirmple analogy to undustand revene enyn, = Imagine you hove e& complex puzele, Tut the picture on The bor i ralssing . Reverse 2nginee ving *~oul tovolve Faking the puzzle apport , Studying —T esand then the individual feces fequre ] drying 40 yetpnsiaucd a p ; Obs ervatrOMs « is use engineering Purposes }e | Software works in order | Pokegratke it PMC tsues | i’) Compatibility = Wien working ait [elder Software +hat lacks Source code, yeverse engineering ean help make + cormpahble with newer 7 Cy bersecuas ty developer (Aghh F insphre also. used| v)| Innovation | Ry Yeverse engineering \| enr'sting sof Froare , developers can goin | ingig hk dat Inspive hem! Fo Creaqe i mew and improved version cormpkimentary ———“TT | tools, 4 4. | Differentiake bedweer) cohes'on and i | coupling . Suplain — their Types in | brief - -¥ | Cohesion vefers to. how well the | parts oy elemen&. inside & module | sHek Fogether and work towards Jo common goal . Tt measures |how . focused and organized! module | is internally . “Think of He Rea | team of people working on @ Tl Project — high eohesion means they are all closely collaborating ‘and Working on tasks that are closely yelaked “Fo Fhe — pacyect’s abyechve. |; uncttonal coheson ° “This — when | feneFor Ay souk 47 1s aaa related. Tere the element aie arranged in orae . ii) Sequential cohesion ' inside a module a lH nee av i Spe cific seque ')) Communicatonal Cohesion ~ the elements inside a module shave data o7 i Information wth each other \Fo Occormplih — [QO Common objective. Nv) Procedural Cohesion + This oceurs when | the elemenk inside ac module Ore vouped togethéy based 06 O° particular rocedure or operatto 0 pies peas__») Tempore ~ COhalon n Temporal to thot /Means dhe elernens Tnside oO lmmodule ate yeladed based on Hiring ov are entecuded tog ether within [ Speetfre dime, Coupling + i Coupling refers to how modules 07 | component Within o Software Systm lave Inderconnected fo ach other. Tt measures how closely they rely on one another, “Types of coupling ir Lovse coupling » Madules have —™*nimal }nter dependencies and are rela Bvely independent . Changes In one module have |i tHe tnpact on other module, and they can be modified or| Content Coupling This oceurs when changes tn one module I directly adduct, ofher module: | a iT I One module directly accesses OY | modifies the content [Frode ) Common coupling + In This’ Fype, youltiple modules shave a common l global data oy resource. v) Contre! coupling t Tt happens when one module controls the behaviour br ‘eteution of anomer Module by inform ation- assin gse explain Component desting and point a thre ad advonta ges of joptaare — Tnspechon lever Software fe sfin | Component desting also Known os “Tan Testing i vis a Fype Of Hshag | Pat focuses on Festing pdtvidual Parts of a goflwoare Syskm in Nyolaton. IF testing each separately to énsure Correctly and —meet the yequirements, involves | c omponent || work i Besived i} they | Advantages of Software I ae | Ove software Resting oe | Carly detection of problems !- ave inspection helps in finding problerns early 7 Fhe development prowss. THs Ike catehing mistakes ey cause bigger problemas -#)| Tost Savings j 2 SoFFware Yrspection 75 generally SY | ymare tos) — edfechyve compared ONY Sof Fware desting . By catching | earl through 1 entensive ding = rysues if yeduces the nee ksfing and yework lakr on. iv) Knowledge Sharing and “Inprovement Software inspecton — prommoks Kovledg.~ Shaving and Improvement within te | development deam , When rnultple | kom members parheipate in Fhe Inspec ! Process, they get .to learn from | each other and shaw thelr expertise.