Table of Contants Software (USBTE- Sem4- Cong) + Syfabus Tope: Lev Paes Anas.5.23 | / Syed Tople: Sac Sota Erootg...6 28 S12 CM: Lev Pras, Aas $23 | 818 Seat Sate Enon 526 sii 526 | 8181. What Sony Testhg on 5 sn $24 | 5182 Peveb esns... sa saa 24 | 5153 satan sta sa sna S820 | 6 CR Ee _ = uatot Progam ols “ “S| ppt: See Une to Pape ot 4 Sylabus Tpke: oraictan WO Ops... $25 ee eae 514 lnrtton Deps. . 525 sna 5% ooIntroduction to Software Engineering and Process Models Syllabus Tople: Software 1.1 Software 3 (usere-s-17, Wn © Definition Computer software, or simpy softwar, is genetic term tht refers 10 a collection of dat or computer instrction that tell the computer how to work, in contrast tothe physical hardware from which he system {sb hat actually perfoms the work. = In computer science and. software engncring, computer software i all the infomation processed by computer ystems, programs and dat, = Compuer software includes computer programs, bis and reed no-erecutabe dt, such as elie documentation or digital medi Computer hardware and software require each other and neither canbe reais sed on ts own, ‘AL the lowest level, executable code consis of machine language instruction specific to an individual processor ypcaly a Centr Procesing Unit (CPU). Sofwar, Sofware engineering as layered approach and its characterises, typos of sofware. Software development framework, sotware process Famewor, process models: perspective process models, specalzd process models ‘Agi sotware development: Age process and is imprtance, exteme programming, Adapv sotware development, serum, Dynamic Systems Development Matha (OSM), crystal. Selectn err or sohware process model ‘A machine language consis of groups of binary values signifying processor instcton that change the state ofthe compte rom is preceding ste, For example, an instruction may change the vale stored in a paiculr storage lction in the computer - ameffect that isnot directly observable othe user. ‘An instruction may also Gide) causes someting (0 appear ona display ofthe computer system =a state change which shoud be visible othe user, ‘The processor caries ou the instctions inthe oder they are provided unless itis instrctedto “ump toa Afferent instr, ois interpted by the operating system ‘The majority of software is writen in high-evel Programming languages tht ae easier and more efficent for programmers to use because they are closer than machine languages to natural languages. Wightevel languages are translated into. machine Tangunge using compiler or an interpreter or «combination ofboth Software may also be writen in a low-level assembly Tnnguage, which bas strong corespondence to the ‘computers. machine language instructions and. is translated nto machine language using an assemble,Fig... : User interaction with application = Ave diagram shows how the wer interacts with pplication software on atypical desktop computer ‘The application software layer imeraces wih the ering stem, which in tum communists wih he hardware. The arrows indicate information flow 1.2 _ Nature of Software > (useTe-W-17) [0.1221 Explain changing nature of sotwar TTS | Nowadays the softwares ool emsins a proc it also becomes an merce for delivering a pod. = Asa produc, sofware is able to delve the computing tena which is basically embodied by computer Fardware or precisely we can sy, by a network of computers which one can access through local hardware. ~ Software is considered as an information transformer or rodacerimespective of wheter it resides within a smartphone or functions inside a mainframe computer. ~ Juste any transom vil, software can work asthe basis for the control of the computer (operating system), the transport of information (networks), and the generation and. management of ther programs (Goch as various software tos) = Teformaton delivery isthe mast important aspect of Iniroducton to Sofware Engg, & Process Modols cote, software can transform the dat also helps in improving the competitiveness of a business by managing the basins information, = A gateway is provided by software 1. worldwide information networks (eg. the Inert), and offer the way ogther information in several dtferet forms ~ Over the last halfsenny, significant changes are coscured inthe role of computer software. = _ Nowa the software hecmes mare sophisticated as well a complex because of various apts such as spectacular improvements in hardware performance, tremendous up gradations in competing architectures, huge enhancements in memory and storage capacity, and extensive diversity of extic input and output options ~ Sophistication as wel as complexity lads to amazing rests on soces of ystems ut hey may also lead 0 hug problems for those who want to develop complex systems, = Inthe economies ofthe indusiied word, the big software industry is considered as a dominant tr, = Inn exter er, sofware was developed individually [Now days an entire eam works for itn which every person is responsible for one pat of the technology hich is necessary to die complex application. 1.2.1. Defining Software > (sete -s-16) forza Dafne stare EGS Software can be defined in diferent ways 7 Definition J. Software ise of nsrution (computer programs) that when executed provide desied_ fetes, function, and perormane, J. Software is data sites tht enable the programs to adequately manipula infomation. 3. Software is descriptive information in both hard copy and virtual forms that describes the operation anus ofthe progams, sofware, To make any data more wef in TealSoftware Engineer = Now fo undestnd the software exactly we have 10 amine some characteristics of it which make it fret rom remaining human made things = Softwares considered as loge rather than a physical system clement, Hence, there are caress of sofware which ar significa diferent han those of handvar. ‘syllabus Topic: Characteristics of Software 1.2.2 Characteristics of Software D> (USBTE-W-14,W-15, $16, WIZ) f0.1.23 Stato any fourannbuts of good sofware. CECRIITT [0.1.24 Describe ie characters of software (0.1.25 State three characterises of sofware, 1. Sofware is developed or ngreered, iis ot manuacturedin the classical ynce aoe Fig. 1.2.1 : Characteristics of softw F 1. Softvare is developed or engnered; ls ot ‘manufactured inthe dasa sense = Even though there are some similares found in sofvare development and hardware manufacturing, toh the actives ae considered as fundamentally tere, ~ In both ofthe activites, good design is base for high quality, btn the process of manufacturing thee may ‘be quay problems in hardware which may not present incaseof software, (MSBTE «Som 4~ Compl _13 Iniroduetion to Sotware Engg. & Process Models ~ _Inbosh of the activites there is prominent dependency cm peopl but there i vas diflerence inthe relationship between people and work accomplished. The mai aim ofboth the actives is consuton ofa “product,” bt the perspectives arent same, Software costs are concentrated in engineering which inicats that its difficult to manage software projets similar to manufacturing projects 2 Sofware doesn't “wear out” > (useTe-s-18) Elaborate the sofware characteristic “Sotware oes not wear ou. = In case of hardware, the fuilre rites are high as compared to software eal init ie. Such failures are tainly concemed with design or manofacturing defects Ihis possible to comet the defects and drop the flue ate oa teay-stat level for some ime period = However after sometime prod, there is gai increase in the flue rte as there are cumulative eects of us, vibration, mishandling, tremendous high of low temperature, and. number of ther environmesial malas on components of hardware. In simple words, the hardware begins to wear out = Software des not hve any risks of such environmental maladies which ead to wea out of hardware, = Ineaty life of software there may be high failure aes because of undiscovered defects. However, these can be comected. = Now i is clear tht there i no possibilty of software wear out butt dos deteriorate, = Init life change is an integral pan of software. Whenever any change is made, there i possiiliy of nreduction of eors which increase he ale rate. ~ Before the software gets consistent stat by conection, any new change get introduced which again increases the fire ate, = Gratualy the lowes failure ate level stats wo increase which indicates thatthe software i deteriorating due 1 change,& Engaaerng MSETE Som Cong) Introduction to Software Engg. & Process Models ~ There is one important diference in hardware and sofware regarding wear aspect is that in case of hardware, a failed component can be replaced by spre as, Ths facility isnot aii in oftware as there ane no such sae pas, = Alte software fires point ut that thee san eon in design o inthe method by which the respective design was transformed into machine excitable code = Hence the sts of sofware maintenance which andes reps for change bas significantly moe complexity compared to hardware minenanc. > 3. Custom built software = Component rewsbity is an imponant aspect in software nds = tis esponsibility of software engineer to design and ‘nplement a sofware component in such away tht it shouldbe reused easy in many diferent rogram. = Latest reusable components summarize both data as well as the processing whichis applied 0 the dat, which helps the sofvare engineer to develop new plications from existing components, = For example, reusable components are_used in th evelopment of moe interactive ser interfaces that cable the generation of graphics windows, pull-down mens, as well as wide range of imerscton mechanisms, > 4 Eiicieney ~ Software is said tobe efficient iit uses the avaiable resources in the most efficent manner and produce ested est in ime manne. FS. Maintainabity = Weaslomer requirements changes, programmers need to modify the software to fulfill those requirement Sotware enginceing provides the ability to maintain the software Unough modifying the sofware rather than changing whol prodc ie hardware. > 6 Dependability ~ Dependability is the ability of the software that vides services which can be ted by users. = Dependbilty is the abiity of the software that provides services to fulfil he customers requirement, so that isl to aceve st of customers on the system, Syllabus Topi Types of Software —_—_——__ ee 1.23 Types of Software D (uSBTE -5-16,W-16, $-18) (0.1.27 State and explain any four types of sofware. [0.1.2.8 Describe any four categories of sofware o.129. abate any spe lobe, = Vinwaly on all compuerplafors, software can be grouped int few broad categories 2 Apa Stare ‘Product ine Sova 7. Atal ligence Sova Fig. 12.2: Software Categories FA System sotware = This is ast of programs wed to provide service to caer programs, Few of them such as compilers, editors, and file manogement ilies are wsed to process complex but stvctues. determinate information ~ Some other sysem software such as components of (5, several drivers, networking related software, and tlecommnizations proceso are generally used to process heavily indeterminate dat[aleceme ara SEE. Se on) 15 = Inall he situations the system software ara is broadly depends upon the interaction with computer hardware. tio software = These ar the stand-alone programs which are specially developed for pei busines needs = The Applicaton Software helps to process business or technical data in och 2 way that it should be useful to manage business operations as well as management or technical decision making. ~ With tational processing applications, one can also vse application software to keep contol on basness functions in realtime FA Engineeringcietie software ~ These types of software are characterized through the “number crnching”algritims, Thee are numberof cngnering sofware in various fields ik asronony, spoce shutle orbital dynamics, auinotve. sess analysis, automated manufacturing, molecular biology et. = However, thre are drastic changes in modem plications within the enginerngscientfic area as they are shin from rational numerical lors. F. Embedded stare = These a the software which are merged within leone devices and are used for the purpose of implementing and consoling the features aswell s fonctions forthe end ser aswel as sytem sel FS, Produtiinesotware = These software are developed to provide 2 parca functionality frase by several customers. = The focus of productline software may be on a resvicted marketplce like inventory contol applications or can focus on mass consumer markets such as word processing, spreaishets, graphics based applications, mokimedia, database management, and personal swell as busines financial pods OO TO OQ EE ererT-L|Ll!lUlC Irvoducton to Sotware Engg. & Process Models J 6 Web applications ~ These aplication ar also called as “WedApps. This {sa network-cemsc software extegory which covers large number of applications = In shoest form, WebApps are same as ofthe group of linked hyperext files which provides information through tes and Limited eraphics, = Nowadays the moder Webapps ae evolving into vironments of sophisicated computing which ofer stand-slone features, computing functions, a well as content to the end use. = lisalso posible to itgrte WebApps with corporate dabases and business applications + 1. Ariiaiteligence software = In these applications non-sumercal algorithms are seerally used for the purpose of solving complex pPoblems wich cannot be handled by computation or stighforward analysis There a varios aplication in this category such s nbs, mes, expen systems, afi near networks, proving theorem, pater muting tke image and oc. Syllabus Topic: Software Engineering as Layered ‘Approach 1.3 Software Engineering as Layered Approach > (WSBTE-$-15,W-15, $16, W-16, -17) (0.1.1. Explain sofware enginooring as a layered technology approach |a.1.32 Descibe the layered technalogy approach of software engineering EE (0.133 Explain sofware engnesing as 2 layered ‘echnlogy approach wit eat gram, | Software Engineering combines two cones, Software and Engineeting, a ee |(0.134 Descrbe 4 layers of sotwareengneeng = As we have already seen Softwares st of executed rogans related wo specific functional. Set of ‘excl insrction scaled as program. Software is more tan just a program code it also inclaes data strates wich allow programs to manipulate infomation, and documentionrelsed to sofvare put wich defines the functoaity and ridance for the user to use this sofware, Software engines design ad bil the sofware prod. 7 Engineering = Engineering isan application of tmowldge and well ened principles to develop prods. Software Enginering © Definition 1 Sotware Engioeering is the method of applying scintfc and technolo Lowldg, procedures and resto design, develp, and main he software root oR © Definition 2 ‘Anplyjiog wehoooge, scien, and admiisrave pric to designing, developing, tesig, and iui the sofware prod inorder meet easomen’ requests with bet quality of profut seemed 1s solvareEgierig. 13.1 Layered Approach > qusere-wsg Fig 131 : Layered Approach of software Technology 16 Invducton fo Stare Egg. & Process Mody Tis aprach sided no ayers: 1 Acquaiy Process = Anyegicring aprach mst ston the quality. ~The most impo aspect in sofware Engineering ig Quality Focus, 2. Proes = Foundion or SEsthe rcs Layer ~ SE proces is th GLUE tht lis al he technology yes ogee and enables the timely development of computer sate = Ttfoms tetas for maagenet conta of software oj. 3. Mateds ~ SE metals provide te “Tecscal Questions* for tuiig Sova = Matods coon a bral aay of tks tht inode conmasiaion quent sss design modeling, program costo esting a sepa. 4 Tools = SEtools provide amsted or seri-automated support forthe "Paces" andthe "Methods. Tools ar itp so tht information rested by one too canbe used by anher 132. Activites of Software Engineering J0.135 Enis Aces of SotwareEngesing. (2s) Software Enginceing incloks many activites as follows , © Undestnding he wer repent isthe fist st imporant atv in software engineering © According to the requiemens designing the syste and taking decisions, which futer leds to sucess competion of development of oda © Conscing the sofware product based upondesigns and decisions made eater is the next activin software engineering ‘0 Toverfy the performance and quality of software, testing software product is essential air software profuctis constructed by software engines. (© Providing maintenance for software product which isdeployed tothe customer 1.33 Need of Software Engineering [0.1.36 Explain need of Sotware Engineering. (2 Marks) = AS the technology changes, the user requirement and cavioarent on which software is working also changes. So every organization is raked based on the software engineering principles used by that organization, = Implementing and managing le size of softwar, programmer equies a specific method to modularize the tasks so that sie of sofware cart ham the software quay. Software engineering provides methodology for impleméning complex software systems wih high quali , Without any standard method or management, itis dificult to address defects in the produt and corect them as early as possible, Software Engineering provides this fnctionaliy, Exendng the previous software to add new functionality requies more cost in terms of tie to develop and ffs ken by people, as compare tothe proces of developing new software to provide hat funciona, Sofware engineering provides a way in hich software system can beable to sae as needed in fore, Syllabus Toplc : Software Development Framework 1.4 Software Development Framework [0.1.4.1 Wile nae on Sotware Developent Framework. (4 Marks) [alse ent SEES Cong 7 Invedcon o Sofware Engg & Process Mats = A software eninerng process isthe model selected for managing the creation of software from customer initiation to the release of the Gnshed profuct. The selected process typically involves methods such as Fig, LA: Software engineering process ~The software life cycle follows the sequential low in order to develop software. ~ Weill sce each and every stage ofthis life cyte in el in subsequent pias: (©, Requrement ubering nd analysis ~ Inthis phase stakeholders communicates with ewer and system wers to guher the business requirements like who will use the system? How user wil interact with the sytem? What should beth sytem input and ouput et, ~ Depending on these requirements, Requirement Specification Document (SRS) is prepared. i) Design = This phase makes use of outpat of requirement sthering phase i.e, requirement specification document san np. ~ Based on requirement specifications software design is Prepared. = Output of this phase is design specification which Specifies hardware and sofware requirements of system, Data Flow Diagram, foweharts etc are included by espn specification document pum[lea expo TS Conpi)_18 = Design spcifcwion ats as an input for inplementatoa ph. (i inplemetatn pase = Implemenaton phase of development proces decompses thst work into vars smaller prs calle modes. = These modules are asigned wo developmen team mmmbers nd acta codig state. ~~ Tisislonges paseo yt development. ~ Out ofthis pase is sxmal code using specific ‘programming language, > Gs) Testng = Tesing pas involves testing factual code of tem ‘gains requirements of wer in ore to ensure that system wil sts all nods of wer. ~ Various eng srtgies ued ae unit testing, system testing integration testing te. = Output of testing phase is conecte and modified sofvae code > 6) Deployment = _Inthis phase the syste is deployed at use’ for thru = In this phase customer ses te software and ive feedback to development team for any changes or dications insystemif any. (0 Maintenance ~ Once the software is deployed acta problems from ses perpetv wll comes up ti esponsibility of development tam to solv user's problems time to time This proces icles maintenance of tem. = Inthe phase some atonal fuctionty may need to din the application ser use’ requremen. 4144 Comparison with Conventional Engineering Process [2-142 Conpae Sofware engosrng with Conventional Process. _($Marks) trident Sofware Engg & Process Model, Software engineering has some siilr things a8 the frinciplesof conventions enineing Iris assumed that oftware engineering is associated the design of sofware or data processing product ang telogs to its problem solving doin, ining he clas of problems elated to software and dn processing. This idea is expanded by dravig siniarity fom the methods that ar gener sd in engineering is observed tha, us asthe famous sient method is wd in he field of scenic research, the steps of ngincerng design proces are used in the process of problem solving in he eld of engineerin. Following steps ae mostly epetve: (1) Problem formulation, (2) Problem analysis, (8) Search or aternatives, (8) Decision, (6) Specification, (6) nplemectation * his advised that these steps are aplsble othe fld of softare engineering aswell Sofware enginerng is considered a8 a result of inegraion of hardware and systems engineering, including ast of 3 Key elements - methods, tools and Procedures which fnciiate the manager o contol the roe of software development, ‘The methods give the tecica “how t's "for balding software; tools offer auomsted or semi-automated * suport for methods; and procedures describe the series of applying methods, the deliverables te cons, and the objectives Compared. to tadtonal engnerng. disciplines, software engineering demonstrates some remarable difereces 1 convention! aginering, one moves from an abstract design ta concrete product, On ther hand insofware engineing, one. moves from design to ceding Software Abstract |=» |More Abstract Code Engincring Design Manufacturing [Abstract |» |Conerete Products Engincring Design = The problem domains of software eninerng canbe anything, from word processing to real-ime contol and ffom games to robots. In const to another cogncesing discipline, i is therefore much large in scope and thus provides bigger challenges = Traiional manufacturing engineering that ormally emphasize mass production is loaded with preduction features, Ths, itis highly production concentrated. Software engineering, in conta, is inhereny design concentrate, = Product standardization assists in cost reduction in ‘manufacturing, whereas sucha possibly is remote in software enginering. The posiilty of process standardization however, is ver high nthe ater. ~ Conventional enginerng process makes the use of unlimited number of domain and application specific ideas which are proved, Sofware enginerng, in conrast, makes use of ited, but global concepts such as oops, conftons te, Syllabus Topic: Software Process Framework 1.5 Software Process Framework D (WSBTE - W-14, 5-15, W-15, W-16, $17) (0.1.5.1 What do you mean by process framework ? Explain with suitable diagram. [0.1.52 Explain he basic process framework acts. 10.153 Explain process tamework with suitable diagram, a sotareEngnesng(MSETE Sem 4—CompT) 19 Irvoducton to Saware Engg. & Process Models ‘The proces of framework consis if several activites which ar applicable tal ypesof projects. The software process framework is considered a5 a soup of various types of tk sets Inthe task ets there is cllecton of small work sks, Project milestones, work productivity as well as software quay assurance points ‘Common process framework Framework acts Fig. 15.1: Software process framework 15.1 Umbrella Activities ‘Typical umbrella actives are: Software project tracking and control This activity consists of acesing the project plan and comparing it withthe predefined schedule, This is done by the developmen eam. [there is no machin project plans and the predefined schedule then the necesary measures are taken 10 ‘maintain the schedule. Risk management Risk is considered as an event which may o may not cour Ifthe even occurs, thn it may leads to some unwanted outcome. Hence, there is need of proper risk management Software Quality Assurance (SQA) Software Quality Assurance isthe planned as well as systematic pte of actives which are necessary to provide an assurance of software quality. mm le5 Sofware USBTE - Sem 4 Conf) For example in the proces of software development, sever meetings are aranged at ech and every stage to find out the defects and ply improvement fr the purpose of producing good quality software. Formal Technical Reviews (FTR) FFIRis a meeting conducted by the echnical staf. ‘The main aim of such meeting is to detect problems ‘egardng quality and suggest improvements. ‘The technical person tkes customer point of view on ‘consideration to maintain the quality ofthe software. Measurement ‘Measurement involves the effort needed to measure the software, Is ificalto measure the software sraghforwadly. ‘Direct and indirect measures are used to measure it. Direct measures consist of cost, lines of code, size of sofware, Indirect measres like quality of software are measured ‘by some different factors. Hence, itis considered as an indirect measure of software. Software Configuration Management (SCM) It is used to handle the effect of change during the process of software development. Reusabilty management Itinvolves describing of the criteria regarding reuse of the product, ‘The quality of software can be considered as good ‘when it is found that the components of the software hich are developed for any specie applcaon are also seem tobe wsehl for developing ober types of applications. ‘Work product preparation and production Te involves the activites which are necessary to severe the documents, forms, lis, logs and wer manual foc the purpose of developing softwar. Introduction to Sofware Engg, & Process Modo ‘© Framework Activities = The Framework activites which we have already seq areas ollors (© Reguiemeet gathering and analysis Design © Implementation © Testing © Deployment © Maintenance —_____.. Syllabus Tope : Process Modes - Perspective Process Models 18 _ Prescriptive Process Models (0.15.1 Epkin Presctve Process Motels (4 Marks) ~The folowing framework activites ae performed inespectve of the process model selected by the crgaizaton, 1, Communication 2 Planing 3. Modelings 4, Construction 5. Deployment ~The name ‘prescrip’ is given because the mal prescribes a set of actives, ations, sks, quality assurance and change the mechanism for every project. 1.6.1 Waterfall Model D (useTe-s-6,w-17) [0.1.82 What is watefal model 7 State tho practical ‘tuations in wich itcan be use. CoFaquorot [Blemmets (MSBTE-Sem4—CompM)_ 1-11 7 kn Veet Fig. 16.1: Waterfall Model Waterfall model isthe fist approach used in software evelopment process. is lo called as classi fe cycle modelo iear seni model {In waterfall model any phase of development process teins ony if previous phasis completed. Requlrement Analysis, In hs phase all business requirement of system are gatbered and analysed by communication berween stakeboles and custome ruse, ‘At the end ofthis phase Requirement Specification Document (SRS) sereated Design Based on euiement specification document design of system sereated called software architecture, This blo prin of system representing sytem’ itera strc and behavior Implementation In implementation phase acti coding is constructed for software architecture using hardware and software requirement of system, tis esponsibility of developer. Verltcatlon Testing ‘Here coding or job done by developer is verified inst requirements of ser in oder to ensue that software wil sat al busines requirement of we Introduction to Sotware Engg 8 Process Models = Merthe socesslerfiaton sofas deployed at user's site for their use. 5, Malntenance = While using software if wer faces some problems, thea those problems must be solved time to time by development tam. This tsk comes under mantesance of software Maintenance also incldesading ew functionals in software as per we requirments, © Advantages of watertall model (Tes very simple to understand and easy to we. (Phases of watertall model do ot ovelp with each ober, i) eis wsefl for sal projects in which requirements re cleanly, (iv) Since development is linear it is easy to manage evelopment process. Disadvantages of waterfall model (Wis nose for lange projec (i) Nox sible fo project in which requirements are not clear intl. (Gi) System ot product is avaible only at the end of development proces. iv) tis very cl to modify system requirement inthe mide of development process. ‘Practical situations in which Waterfall model can be used = This model is used only when the requirements are ‘very wellknown, clear nd fined = Product efiitons sable ~ Technology is understood, = There are no ambiguous reurements = Ample resources with required expense ae avaiable freely = Theprojetis shor. ee i alll(USBTE - Sem: mt 1.6.2 Vode! (0.1..4_We noo on Vad (Marts) = In software developmen, the Vem epresens evelopment process that may be conrad an ‘tension of the waterfall mode, andi an examyle of the mere general Vee stead of moving down ina linear way the proces steps ae bent upward arte coing has, to form theta V shape. = The V-Model demonstrates the relationships between cach phase of the development life cycle and its associated phase oftesing ~The horizoml and vert ates represent time or Project completeness (ftiorigh) ant level of abstraction respectively, Fig. 16.2: V-Model = This model is basically divided ito two phases vetfcaton nd validion : 1.6.2(A) Verification Phases Inroducton to Sotware Engg & Process Model F 1, Regulrements Anayss = Inte requirements analysis phase, the frst te in the verification proces, the requirement ofthe sytem ae collected by analyzing the nee ofthe wer). = This phase is concernod with establishing what the ileal stem has to perform. However it does not ketene how the software wil be designed or built. ~ Usually, he users ae interviewed and a document called the wer reuitements documents generated. ~The wsr requirements document wil ically describe the systems function, interface, performance, data, security. et euiement as expect bythe ws = This wed hy business analysts to communicate thet understanding ofthe system othe users = The users carefully review this document 28 this document would sere a8 the guideline forthe system designers inthe stem design phase. = Thewseraceptance ests are designe in this phase, = There are illerent methods for gathering requirements ‘of toh soft and hard methdologies including, inerviews, questionnaires, document analysis, bseraton,throw-avay protons, usecase and sti and dynamic views with ses. FX System Deen = Sylems design i the phase where system engincers analyze and understand the business of the proposed system by saying the user requirements document = They figure out possibilies and tchnigues by which the user requirments canbe implemented. ~ Many ofthe requirements are no feasible, the wser is informed ofthe issue. A resolution is found and the wer requirement documents edited acodigly. ~The software speciicaton document hich serves as a turin forthe development phases generate = This document contis the general system ongniation, menu ctr, dita structures tc It ‘may also bold example business scenarios, sample windows, eps forthe beter understanding, ~ Other tchical documentation like entity diagrams, aa tionary wil as be prodced inthis phase. The documents for system testing are prepare =FA. Artectre Design = This phase of the desig of computer architecture and software architecture can also be refered to as high-level design = The baseline in selecting the architecture is hat it should realize all whch typically consis ofthe lis of mmoles, brief functionality of each module, thir interface reaionsips, dependencies, database tables, architecture diagrams, technology details et. = The integration testing design is cad out inthe particular pase. 4 Made Design = The module design phase can also be refered to as Aowrlevel design. The designed system is broken up into smaller units o¢ modules and each of them is cexpined so that tbe programmer can stat coding sire. = The low level design document progean speifiaton wl conan decid functional logic of tbe module in pewdo-cale © Dubus bles, with al ements, inclaing ther type and sie. o All imerface dels with complete API (Applicaton Programming Interface references, © Alldependency sues 0 Error message listings. ‘© Complete input and ourputs fora module. = The unittest design is developed in this stage 1.6.2{B) Validation Phases Fig, 1.64: Validation phases In the V-model, each stage of verification phase has 2 comesponding tage inthe validation phase. “The following are the typical phases of validation inthe VeMoel 1. Ut Testing Inthe V-Moel, Unt Tes Plans (UTP) are developed rng module design phase These UTPS are executed to eliminate bugs at code evel orunit evel. ‘A unit isthe smallest entity which can indpendenly xis eg, program module Unit testing verifies that the smallest entity can function corectly when isolated fom the rest of the codes 2 Integration Testing Integration Test Plans are developed ring. the Architectural Design Phase These tests verify that units created and tested independently can ccerist and communicate among themes. Tes results are shared wih customers tea. A System Tsing System Tests Plans are developed during System Design Phase. Unlike Unit and Integration Test Plans, System Test Plans are composed by lint’ asiness team, System Tes ensres that expectations from application developed are met. The whole application i tested for its functionality, inerdependency and communication System Testing verifies that functions! and non- functional requirement have been met, Load and performance testing, sess testing, repression testing et, ae subsets of stem sing. User acceptance Testing User Accepunce Test (UAT) Plans are developed during the Rguieents Analysis phase,orware Engeeing MSBTE Sem 4 Comp) = Test Pls ae composed by business users, UAT is performed in a user enviroment that resembles the Production enviroment, using relic dat, UAT vere that delivered sytem meets wer reuremest and systems ready for ws ine time, & Advantages of Vemode! 1, Thismodelis simple and easy to we. 2. The eng sctvies sch as plamig, est designing sae occured pie to coding. This avoids wastage of time. Hence it as beer chance of sucess compared 0 wate model. 3 Pouctve defect tacking that means the diagnosis of efetsis done ately stage, 4. Avoid the downward flow of the defets. 5. Tes considered as good for small poet in which requirements easly wderstood. Disadvantages of Venodel 1. This model is considered as very rigid and last exible 2 The developmest of sofware is done in the implementation phase hence no early procoypes regarding the software are produced. 3. Uther are changes in midway, then there is need to opdue the test documents aloog with repirement documents Incremental Process Models 0.1685. wite ncn ienent proces motel (4 Marks) ~The incremental ‘model applis the waterfall model incremental ~The sees of releases i refered to as “increments, With cach increment providing more functionality to thecastomes ~ After the fist increment, a core product i delivered, hich an already be used by the custome. Introduction to Sofware Engg, & Process Model = Based on customer feedback, a plan is developed for the next increments, and modifications are made soli This process continues, with increments being delivered until the complete product is delivered. The inet icp sao ue inh ai proces model. Dirmraer Drees Biecsergro srs Fig. 165 : Ieremental Model Following tai are common al te models 1, Communication helps to understand the objective. 2 Planning : required as many people (software teams) wrk on the sume project but diferent functions at same time ‘3. Modelling: involves. business modeling, data nodeling, nd process modelling 4. Construction : this involves the reuse of software ‘components an automatic code. S$. Deployment: tegration of lth increments © Characteristic of Incremental Model 1. System is broken down into many mini development projets. 2 Paria systems are ult ope the fina ster, 3. First acd highest priority requirement 4. The requirement of a ponion is foaen once the incremented portions developed. ‘Advantages of Incremental Model 1. Afr each iteration, regression testing. should be conducted, Dring ths testing, faulty elem oftheSota Engineering (MSBTE -Sem 4 ~ Cong software canbe quickly identified because few changes ae made within any ingle iteration, 2. is generally easier to test and debug than other meds of software development because relive smaller changes ae made ding each iteration, This allows for more targeted and rigorous testing of ach element within the overall product 4 Customer can respond to features and review the product for any neded or weful changes. 4,‘ product livery is faster and coats «© Disadvantages of Incremental Model 1. Resuling cost may exceed he cost ofthe organization 2. AS alton functionality i added to the proc, problems may aise related w system architecture which were ot evidetinevlirpotrypes 1.6.4 Difference between Waterfall Model and Incremental Mode! D (usBrE-$-15,Wet8, 1) [0.186 Dierentste betwen waerll model and Incremental model EEERIEESESSEEOETSD Parameter | Waterfall | Incremental Mode Model Sinpciy | Simple Intermedite Risk High Esily Involvement manageable Feeiiity 10 | Diffie Esy change User Only at | Imermedite involvement} bepinning Reabilty | Rigid Ls Fite Maintenance | Least Promotes maintainability Duration Long Very Long Irvoduction to Sotware Engg & Process Models Syllabus Toplc : Specialized Process Models 1.7 Specialized Process Models: = Special process models take on many of the characteris of one or more of the conventions models. However, specialized modes tend 10 be plied when ananowly defined software enginerng approach is chosen 1.74 Component - Based Development [0.1271 Expan component based development. (4 Marks) Commercial offthestelf (COST) software components, developed by vendos who ofr them as oducts canbe wed when sofware iste bul. ~ These components provide rgetd functionality with ‘wellefned interfaces tht enable the component o be integrated into the software, = The component-based development model incorporates many of the characteristics of the spiral model Its evolutionary in nate, demanding an iterative ‘approach othe creation of software ~ However, the model composts applications from repackaged software components. Modeling and constuction activites begin wih the ienifcation of «candidate components. = These components can be designed as citer conventional software modules or objectorented clases or packages of classes. ~ Regatless ofthe technology that is used to crete the components, the component-based development model incorporates following steps (implemented using an ‘evolutionary approach ): (© Available component-based products ae researched and evaluted for the application oman inqueson. (© Component integration sses re considered, (© Sofware architect is designed to accommedte the components. SRReeeeeereeSOreEE CEES E IEEE CEES SERSEIEREE CERES SEES IEEE OSECS SSE gEEESEEEESEEOOOOSofware Engineering (MSBTE - Sem 4 - CompT) ‘© Component ae inert into the achtestue, © Comprebesve testing is conducted to ensue oper functionality, The component based evelopment mode leads o sofware reuse, and reusily provides software engices with a rumer of measurable benefits. Based of sis of resbily, component based developmen an lead to reduction in development cycle tine, reduction ia. pject cot and. inceae_ in product, Akbough these sult area faetion cf te robustness of he eompent brary, tere is line question that wheter the component-based development made! provides significant damages for software engines. 1.1.2. The Formal Methods Mode! [0.1.72 Wt nolon Foral Metods Model. (4 Marks) = The formal metbods model encompasses a set of scivites tht ads to formal mathematical specification of computer softwar = Formal mecha enable a software engineer to specify, develop, and verify a compue-bused sytem by plying rigorous, mathematical tation = A variation on this approach is called cleanroom software engineering = When formal methods are used during development, they provide a mechanism for eliminating many ofthe problems that ae dffclt to overcome wing oher software engineering partion, ~ Ambigiy, incompleteness, and inconsistency canbe scoveed and conected mor esl, nt trogh ad oc review, but through the application of smuthematical analysis. When formal methods are used ding desig, they serve as a basis for program verification and therefore enable the software engineer to discover and comet errs that might terse go. undetected, = Although not a. mainsweam approsch, the formal methods model offers the promise of defect-free Introduction o Sofware Engg & Process Models software. Yet, conem about is applicability in a tosis envionment is ben expressed: (©The development of formal models is curently ite time consuming and expensive. (© Because only few software developers have the secesary background 10 apply formal metho, exes tings toured (© sdf o use the model a communication unsophisicated mechanism for lechicaly ceusomers, 1.7.3. Aspect-Oriented Software Development 10.173 Wite note on Aspect Oriented Software Development (4 Marks) Regardless ofthe software process that is chosen, the builders of complex software invariably implement a set of loaied features, functions and information content ~ These localized software charactrsis are modeled as components and then const within the comet of asysem architecture, = AS modem computer-based systems become more sophisticated and complex, cern concerns, customer required propenies or areas of technical intrest, span the emie architecture = Some concerns are high-level roeries ofa system; cabers affect functions o are systemic. When concerns cat across muliple system functions, feats, and infomation they ae often refened to as croscuting concer. ~ Aspertual requirements deine those crosscuting concems that have impact across the software axchitecte, Aspects are mechanisms beyond. subroutines. and inheritance for loaliing the expression of a rescuing concer. ~ Aspect Oriented Software Development (AOSD), often refered to as Aspect Oriented Programming (AOP), is 4 relatively new sofware engineering paradigm that WWprovides a process and methooloial approach for ‘lining, specifying, designing, and ”consctng axes = Adie aspect-oriented process has no yet matured However, itis ikly that sucha process will adopt characteristics ofboth he sil and concurrent process roel = The evolutionary natu ofthe spiral is appropri as aspects are defied and then constructed. The paral rue of concuret development is esenipl because aspects a engineered independealy of localized software components and yet aspects have a direct impact on these component 1.74 The Unified Process = Insome ways the onifid proces (UP) is an step to raw on the test features and charterisies of conventional software process modes, but charg them in a way tht implements many of the best ‘incils of age software development = The ified process recogins the imporance of ‘usiomer communication and steanlned methods fr deserting he customer's view ofaystem, = Ik emphasizes the imporant role of softvare ncitecue and helps the acitect focus onthe ight foal, such as understandably, reliance to future changes, andreas = 1 suggests a process flow that is iterative and incement, providing the evolutionary fel that is «essen ia moem software development. ——_______ Syllabus Tope :Aglle Software Development - Agile Process and its importance 1.8 Agile Software Development : Agile Process and its Important Ace > (ussre-s.ts,s-17 [0.1.8.1 Descibe Agle process models in deta [0.1.82 Whatisagle process ? [elearning STE-Sen4- cong) 17 Inveduton to Stare Engg. & Process Mos = Asi software development describes an approach to software developmen under which requirements and solutions evolve through the collaborative effet of selforanizing and crossfunctional teams and tit causlomers end us). = Te advocates adaptive planing, evolutionary evelopment, early delivery, and con! improvement, and it encourages rapid and feibe response to change. ~The erm Agile was popuaied in his context, by the Manifesto for Agile Software Developmen, = The values and principles opted inthis manifesto were derived fom and underpin a broad range of software development frameworks, including Scrum and Kantan = There is significant subjective evidence that adopting ‘gle practices and values improves the agility of software professionals teams and orgaizations, © Agle Software Development Values = Based on their combined experience of developing software and helping otbers do that, the seventeen signatories tothe manifesto prochimed that hy value: © Individuals and Inerations over processes and tools © Working Sofware over documentation comprehensive © Customer Colsoraton ove contract negoiation © Respontng to Changeover following plan = AS per the view of Scot Ambler (Canadian software ‘ngiee, consultant and autho) (© Tools and processes are important, bat it is more ‘porant to have competent people working together effectively © Good documentations seul in png people to understand ow the software is bit and how to Use it, but the man point of development i 1 reat software, not documenatin, © A contract is imporant but is no substnte forSotware| (USBTE Sem ‘working closely with cstomers to discover what they peed. . (© A projet plan is important, but it must not be to ‘iid to accommodte changes in tchalogy ot the envionment, sikebolers’ priors, and Peoples undesnding of the problem and its solution, 1.8.1 Aglity Principles / Features ‘> (WSBTE-W-16) 0.183 Wite any four feanres of Agle Soar ‘he Manifesto for Agile Software Development is teased cn weve principles: 1, Customer satisfaction by ely andcominous delivery of vaablsoftare 2 Wekome changing requemens, even in Ine deepest 3. Working software is debveredfoqunly (weeks ruber than mons) 4, Close, dl xoperioaberwen basins people and deeopes 4, Projets are bit aoand mated indivi, who shouldbe tasted 6 Frootofce convention is the best fom of communica (co cton) 1. Woking softwar iste pray measure of progress 4, Suite developmen, ble to minain a constant pe 9. Conizuus stain to techie excelence and goed design 10, Simpy isesenil 1, Best actiecures, equtements, and designs emerge from serpin ans 12, Reply, the tam reflects on how to become more effective, and adjusts scoingly 8 Introduction o Sofware E 8 Process Mody 1.82 Difference between Prescriptive Process Model and Agile Process Model D (usBTE-S-16, W-17) [0.1.84 Ditereniato between prescriptive process model ‘and ag process model (any four pins). |___SgvaE| Parameter | Prescriptive | Agile Process Mode Process Model Basicaim | Developed to | These models sats tring ower and | customer through soucture 10 the | erly and continous sofvare | dlivery, development proces. Fanctnaiy | ean Defines dint set accommodate | of sctvies, actions, changing | tasks, milestones, nd reqirements | work product that rere cogieerigh quality sofware Popuaty | Itismoe | Comparatively ess Popular. popular Examples [Waerfal | Scrum eXtreme rode, Programming (XP, Tncemental | Faure Driven ovels Development (FDD), Dynanic Systems Development Meth (SDM), Adspve Software Development (ASD) ‘Syllabus Tople : Extreme Programming 1.9 Extreme Programming [ects ean teem atone Popanning (eer section 1.9) (4 Marks) xem Programming (XP) ia software development methodology which i intended to improve software quality and responsiveness to changing. customer requirements,Stare Engineering (VSBTE - Sem 4— Compl) _ 1-19 = Asatype of agile software development, it advocates frequent releases” in shor development cycles, which is imended to improve productivity and introdace checkpoints at which new customer requirements can te aopted. = Ober elements of exteme programming inlade: programming inputs or ding extensive code review, nit testing of all code, avoiding programming of features until they are actully needed, a fat mangement stature, code simplicity and lary, expecting changes in the customers requirements as time passes and the problem is beter understood, and frequent communication with he custome and among roganmers = The methodology tke its name from the idea thatthe beneficial elements of tational software engineering protest taken to “entee” evel. = AS an example, code reviews are considered a ‘beneficial practice; taken tothe extreme, code canbe reviewed continuously, ie, the practice of pir Progamming, 1.9.1. XP Values ~ Extreme programming intally reeogned four ‘ales in 1999: communication simplicity, feedback, and counge. A Extreme Programming Exphined ‘Those five values ar described below. Fig. 19.1: XP values 1, Communication = Bulking software systems requires communicating system requirements tothe developers ofthe system. In Ineduction to Software foal sofware development mebodolgis, his sk isaccomplshed tough documentation, Process Models Exueme programming techniques can be viewed as methods for rapidly bailing and disseminating insttonal inowledge among members of a development team, ‘The goal isto give all developers shared view of the system which matches the view held by the wes ofthe system, To this end, exteme programming favors simple designs, common metaphors, collaboration of wer and Programmers, fequen verbal communication, and feedback, 2 Simpy Extreme programming encourages suing withthe simplest solution, Extra functionality can hen be aed Tater, . The ifference between this approach and more coavenonal system development methods is the focus on designing and coding forthe neds of today instead of those of tomorow, next week, or next month Thisis sometimes summed up asthe "You aren gonna teed i" (YAGND approach, Proponents of XP acknowledge the disadvantage that this can sometimes ental more effort tomorow to chang the sytem; ther claim i that this is ore than compensated fr by the vantage of not investing in posible fture requirements that might change before they become relevant, (Cong and designing fr uncertain fue requirements implies the risk of spending resources on something that might “not be needed, while perhaps delaying ‘crucial fetes, Relued to the “communication” value, simplicity in design and coding should improve the quality of commrizaton, A simple design wth vr simple code could be easily understood by most programmes inthe team,ri FA Peedback ~ Within exteme programming, feedback relates 10 Aiffeent dimensions ofthe system development: ~ Feedback from the system : by writing uni sts, or running periodic integration tess, the programmers have rc feedback from the state ofthe sytem afer plement changes. = Feedback from the customer : The funciona tess (aka accepance tess ae wen by the custome and the testers. Tey wil get conret feedback abot the curent state oftheir system, Tis review i planed ce in every two or tree welsso the custome can easly ster the evelopment = Feedback from the team : When customers come up ‘with new requirement inthe planing game the tam irl gives an estimation ofthe sme tha it wil take ‘oimplemen. = Feedback is closely related to communication and simplciy. Flows in the system are easily communicated by writing a unittest that proves a cena pice of ode wil beak. = The direc feedback fom the system tel prograrmers torecode tis pan, = A castomer is able to test the system periodically according to the functional requirements, known as user stores = Asper Kent Beck (American software engine nd the creator of exteme programming), “Optimism is an occupational hazard of programming, Feedback i the treatment” > 4 Courage = Several practices represemt courage, One is the commandment to aways design and code fr today and 1 for tomar. = This is an effort to avoid geting delayed indesign and requiring alot of efor to implement anything ele Courage enables developers to feel comfortable with sefacoring their code when necessary. = This means reviewing the exising syse ang ding it oth ute changes canbe implemeneg ore easly. ~ note example of courage is knowing when to throw code aay courage to remove source end that ig chsolte no mater how much fot was used to create that source code. = Ak, courage mans persistence: a progranmer migh te suck ona complex problem for an ene day, then solve the problem quickly the next day, but ony if they are persistent. FS Respect ~The respect value nlodesespet for others as wells select, = Programmers should never commit changes that break compilation, that make existing unit-sts fal, or that ‘terns delay the work oftheir pees. = Members respect heir own wok by always stiving for igh quality and seking for the best design for the solution at hand through refactoring ~ Adopting the four eae values least respect gained fiom others inthe eam, = Nobody on the team shold feel unappreciated. or ‘gored, This ensures high level of motivation and encourages loyalty toward the eam and toward the goal ofthe poet, = This vale is dependent upon the oter values, and is cvinted toward teamwork. 1.10 Other Agile Process Models = Ingeneral Exteme Programming (XP) is considered as the most widely used of al ail process models. = But tere are several agile process models which are in ‘se acoss the industry. Among them mest commonly wed a: ho Ronan nnn ASTE-Son Compl) 1-20 Invoduatin to Sofware Engg. & Process Model, |[lsat rgeting SETE-Sem 4 Cong) Introduction a Sotware Eng. & Process Models {) Adapive Software Develapment (ASD) (]) Ojai Str Develpent Mate (OSM Fig Lat: ele process models Syllabus Topic: Adaptive Software Development 1.10.1 Adaptive Software Development (ASD) fa.1.10.1 Wit note on ASD. (4 Marks) = Adaptive Sofware Development (ASD) has been roposed by Jim High smith and Sam Bayer asa tecbrique for the purse of developing complex sofware swells systems. = The msn focus of ASD is on human collaboration nd team eogaization = High sith dies an ASD “fe ec” which ince ttre imporant phases; speculation, collaboration, and leaing, Asoha gen Fegan en sea pet Homme =| Fig, 1102: Adaptive software development = In the proces of project development, adaptive cycle ‘lanting sconce in inal phase. = Adaptive cycle planing refers the important information regan proj inition sch 2s mssion statement of customer, important constant in the roject cho, delivery dates, ser description etc), and basi requirements which are necessary to define the set of release cycles (software increment) which wil be essen forthe projet. ‘Tere is always possilty of changing the cycle plan ven fit maybe completo perfect Depending onthe data obtained at the completion of the fist cycle, the review of plan is taken and is adjptd so tat planed work mast be compile with the realty in which an ASD teams working Collaboration is always used by the motivated people in such a way tht ther talent willbe mulled and centances the creative output beyond their absolute umber. This aproch is frequemly used in al agile methods, Butits not easy to implement the collaboration. Ie mosly defends upon communication and earwork, but it also focus on individualism, since individ! creaivity considered as an imporant aspect in qusere-s-7) i = Serum principles are mostly based on the agile (0.1102 Expinthetom sem SSTMBIIERIN | sess and help 10 pide activites regantng = Sum san agile framework foe managing Knowledge | development inside a process which incIndey work, wih an emphasis on software development. is | framework actives such as requirements, analy designed for teans of tee to sine members, who | design, eveutin, and delivery. ‘break their work info actions that can be completed | _ Jy aj) the framework activities, work tasks happen ihn ie Doreen ced “pinot | itn apes pte called api __ lasale fom | ] Tit tect PBs 4 Tope Pan works) Pratbacn Spt sactpec Fig. L103: Scrum Framework ~The work implemented ina sprints tired othe problem at hand ands defined an usualy lord in realtime by the respective Scum team, Fig 1.104: The scrum processSerum mosly fous on the use ofa bunch of software process pters which are proved elective fo projects wit resistive timelines, changing regiments, and tusinsscraly. All sch proces patems defines seve sets of development actions: : Backlog - a proitized list rearing project neds or features which offer business value fo the eustme.It is possible to ald items tothe backlog at ny tne. The respective product manager assesses the backlog and changes the pions as per neces Sprit -Inclades work units which ae necessary to sina requirement defined inthe backlog which shuld te incorporated in predefined tie-bor (asl hiny ays). Modifications (such as backlog work items) are not involved ding the srine, Therefore, team members are alowed by the pint to work ina short sem, bat sable environment ‘Scrum meetings - are short (usually fiten minutes) meetings conducted on daly basis by the Serum eam, ‘Three most imponant key questions which a asked and st be answered by al eam members are: 1. What you do since the last team meeting? 2 What obstacles are you encountering? 3 What do you plant accomplish bythe next team meeting? ‘A team leader, who is known as a Serum maser, andes the meting and evaluates the responses fom cach person, ‘The imponar use of Scrum meeting to the eam shat itcan uncover eta sues as early a posible. (One more benefit ofthese daily meetings i that they ead to “knowledge sociation” and thus encourage & seltorganinng tam soc. ‘Demos implement the software increment tthe clint side (cose) so that the newly developed functionality canbe demonsoted as wel as evalaed bythe custome, sofware Engineering (USBTE - Sem 4 ComilT) Inructon to Soave Engy& Process Models = isso poste that the demo may not able to coain all planned functional, but insead such factions which canbe eivered within the established time bor, ‘Syllabus Tople: Dynamic Systems Development Method (0SDM) 1.10.3 Dynami Systems Development Method (OSOM) 104 Expian the eon DSDM. (4 Mark) ~The DSDM (Dynamic Systems Developmen Method) isanagie sofware development approach which ofes 4 framewark fr the purpose of biting as well as ‘manning. systems which satfy the tight time cousins wth the help of nctemental praying in cooled poet envionment ~The DSDM philosophy is basically derived from an ‘updated version of the Pareto principle- itis possible to elves eighty percent of an application in testy percent ofthe tine. = DSDMisconsteed a an iterative software process in ‘which ll he iterations follow the eighty percent le, ‘Tht indiaes that, only adequate work is necessary for och increment for the purpose of fs ‘movement oth nest increment. iting = Tis possible to complete the leftover del er on when additonal business requirement are acquired or modifications have been requested as well as accommodated ~ The DSDM Consortium (website - ww.dsdmorg) is 4 worldwide group of associated companies which ‘inl take onthe role of “kepe” ofthe method. = An ale process model has been described the «consorium known as DSDM life cycle which describes thre disiilartrative eces, preceded by two more life yee ais: = Feasibility Study - sts the basic busines neds and constants connected with the application which isto be built and then checks whether the application isfeasible for the DSDM (Dynamic Systems Development Method) pees. Basiess study - ses the functional as well as informatio needs which wil emit the aplication to supply business val; a, desces the fnfanent plication arcitecure and reongizes the maintainability necessities forthe application. FFonctinal Model Heration~ generates a bunch of increment procxypes which are ue to demesite ‘uoctionality forthe customer ‘The main aim ding this iterative eee i oct moe reguremets by doing fedack fom wer as they exercise the proaye. Design and Build tration - revisits prtrypes bit inthe iteration offnctional model to make sre th all the prcoypes have ten engineered in way wich will enable itt give operational business vale for end wens. = Sometimes, fictional mel terain and design and ‘wi teration take place simanccsy. = Implementation = insdices te most recat software ‘cement into the operons envicamest ~ Inport pins ae: 1. Theincemen maybe incomplete 2 New requests for changes may come 2s the increments pt in place = Ineither case, DSDM development work canyon by the proces of coming back tothe factional model iteration aiviY = Itis pose to combine DSDM with XP to ofer a cbintion approach wich defines a concrete process model with he nats and bls practices (KP) whic are ecesary to bid sofware increments, Syllabus Tope Crystal 104 Crystal (4 Marks) Software Engineering (MSBTE-Sem4~ Corgi) _ 1.24 Inroucton Sofware Eng. § Process Model ~ Chyal metho’ aa fanily of metioologes (the CCsal fay) at vere developed by Alisa Corkum in te i 19%, ~ Theta coe fm ya of tly an interview of ans by Cobham, Cacktun's esearch showed ‘trea be erwin follow the formal retbaklogis ye ty sill vest succes Fe. ~The Cys fami Coca way of cataloguing ‘arty did hat ete pj ses = Cpl meta aw conde and described as “ihn meds” The we of the word (Cys ones fon he geste whe, in software terms the faces ar ferent view onthe “underlying” con of ines ands, ~The faces ae a repnaton of tehnigs, tol, send ands. = Mabobogy, ectigs, tied by Cokbu: © Methodology - set of elements (eg, practices, tool) and polices are © Teebiques - sill areas (eg, developing. use es) © Policies dictate oraizional musts Crystal methods are fous on: 1 People 2 Inerction 3. Community 4 Sis 5. Tats 6 Communications = Cockbum sys that Process, il import, shoud be considered afer the above asa secondary focus, The itea behind the Crysal Methods is tat the teams involved in developing software would typically have ‘arid skill and len sets and so the Process element is'ta major factor ffSotwaro Since teams can go about similar asks in diferent ways, the Crystal family of methodologies are very tolerant to this which makes the Crystal family one of the easiest agile methodologies to apply. = Inhis research, Cockbum defines behaviour of people inteams: © “People are communicating beings, dong best face-tofce, in person, with realtime question and answer.” (© “People have wouble acting consistently over time © “People ae highly varibl, varying from day to day and place to place (© “People generally want to be good citizens, ae ood at looking around, taking intiive, and doing ‘whatever is needet” to get the project to work” Syllabus Topic: Selection Criteria for Software Process Model 1.11. Selection Criterla for Software Process Model rte nota on “Selection Crea for Sohware Process Mode. (4 Marks) =. Project characteristic is measured in 0-10 rating. = Comparison tales ae design on tree project (Characteristic categories, Fig, LLL: Project categories 1. Projet Team = Whenever posible itis best to select the peopl forthe project team before selecting any SLC process model. inoorng (SATE -Som 4 125 Invosuction to Softwar Engg. & Process Models = The characteris of this team are important in the Selection process for which they are responsible for successful completion ofthe cycle Characteristics ofthe project team members (a) New to Problem Domain: are the majority of tam members new tothe problem domain ft the project? New tothe technology domain + are the majority of the team members new tothe techoology domain for the project? ‘ () New to Tools to be Used: ae the majority of team ‘member new tothe tools to be used on the project? ‘Any training avallabe: is thre taining availabe for the project team, ifreuired? (© Comfortable with Structure + is the team more comfonable wih structure than Nexiiliy? (@) Closely Track by Manager: will the project manager closely track the team’s progress? 2 User Commanity = The eatly project phase can provide a good understanding of the user the aser community’ and expected relationship withthe project team for duration ofthe projet. = This understanding will assist in selecting the appropriate model because some models are dependent on higher user involvement and understanding the projet. Characteristics of the User Community () Availabilty of user representative restricted or Uimited : wll the availability ofthe user repehensive be restricted o limited during the lifecycle? () User representative new tothe system definition: ae the user representatives new tothe system definition? (©) User representative expert in problem domaln : are the use representative exper in problem domain? (© User representative want to involve in SDLC : des the wser Want involve in al phases ofthe lifecycle?