“They canbe differed in features: [> Development controls software speciation. May be large scale but controllable that fon the customer or [_meunewenrcaTueRNG | SOFTWARE DESIGN CODING IMPLEMENTATION ——~ OPERATIONS & MAINTENANCE iesac sess beforehan Sees and personnel etc. The project te Hoss Se scetnle and resources accordingly. Sete Design:vaya sotareErinering (se Incremental | spiral Model | Rad Mode, Model__| development | Large Te cam [Small Team Appropriate | = Limited Low Time boxed ©f sofware process? What are the types of software Easy velopment model? Explain in data -) ER fa recess (UP). f \) Intemedite oat ae \ y eda larav development mode? Esplin, | Promotes Easily ntal development model work? Explain, Maintainability Maintained trfall model and incremental development model ©f RAD model with Spiral Model rototyping Development Model (©) RAD Model | |compieton ot | Af Jeoding phase {iterationa ayurs™ Software Engineering (BSe Try ‘aie Sofware Development 51 INTRODUCTION: Chapter 5 Agile Software Development vreotucion ge Mes pn-rven and age Deveoonent 54 Bereme Progaming : 55 _Agle Proje Management (Sou Proms) 5:5 Sclng gle Mebedts “= Question Bank for Sef Practice | rolonged and the final software is ecified, lopment processes are designed to produce useful software snot developed as a single unit but asa series of increments, with ling new system functionality lopment, Scrum, Agile Development and extreme programming these are the few approaches wed to develop the Rapid Developmen sjseme. There are some fundamental characteristics: (2) The processes of specification, design, and implementation are interleaved. There is no detailed system specification, and design documentation is minimized or ‘generated automatically by the programming environment used to implement the system. The user requirements document only defines the most important8 we (5) ‘System user interfaces ae offen developed wing t S cpproch ore eh frag and cts so Pe geen 8 pe ma een eee wally change "api tp sencston devant he Pn ave working sftate Guy ntomess, whe can then propose new and changed requirements to be included in Ps “s Fhe best-known agile method is extreme programming, long lived software. They are best suited in both the software being ment process. Wherever iminate complexity from neat 4 agile methods is reflected in the agile manifesto that 96] and cannot take fll part in the “peat ‘agreed on by many of the leading developers of these methods. This manifesto focuses (@) Individual team Soe aed “a me! LS of agile methods, and therefore not interact well with ¢ Indiciduals nd interactions over fad lets a ‘suitable personalit + Working sftzre oer comprehensive documentation + Caster callbraton ve coiac negotiation + Responding to change ovr felling a plan53. BALANCING BETWEEN AGILE AND PLAN-BASED APPROACH: To decide on the balance between a plan-based and an agile approach, you have ts answer a range of technical, human, and organizational questions: 60 DEIEESEE SS Age Sotware Development ooo systems that require larger development teams so a plan-driven approach may have to be used, (@) What type of eystem is being] Sy developed? (5) What is the expected system life[Longilifetime systems may require more time? a ‘design documentation to communicate the| original intentions of the system developers to| the support team. (6 What technologies are available to| Agile methods often rely on good tools to] support system development? __|keep track of an evolving design {is the development team|If the development team is distributed or i ? o How organized: teams _| (6) How good are the designers and|If you have a team with relatively low skill] programmers in the development |levels, you may need to use the best people to team? o (9) Is the system subject to external regulation?tps Software Engineering (BSc Try Je model which consists of repeating the following re life cycle model can be likened to producing software by successive » sofware Engineering (8Sc | ely to encounter software | ines of code), and ea mare than eb ilu 0 map te) e ie fe whether to continue with a fu spiral. If i : plans are drawn up for the next phase of the project. The main difference between the spiral model and other software process models is: A cyde of the spiral begins by elaborating objectives such as performance and functionality. Altemative ways of achieving these objectives and the constraints {imposed on each of them are then enumerated. Each alternative is assessed against each, ‘objective and sources of project risk are identified. The next step is to resolve these risks by information gathering activities such as more detailed analysis, prototyping and staulation. Once rots have been sseased, wane development lb eed sat tome by a, planning activity for the next phase of the process.vipers Stare Engineer (BSe py ‘gle Software Development ined due to it | issue aoe ‘sendReminder acceptP aymer credit period ‘SendReceipt Fig 104 Object-oriented architectural model of an in-Voice processing system, ) Object-oriented ae jon where you fg oeaition where you decompose a system ino a set of A irda mod ctr yen coe itn cs Seo a f Invoices Fig, 10.5: Function Oriented Pipelining 10.5 CONTROL STYLES: To work as a system, sub-systems must be controlled so that their services are delivered to the right place at the right time. Control models atthe architectural level are concerned with the control flow between sub-systems.controlled sub-systems execute sequenti © The call-retum model: This is the fami control start atthe top of a subroutine ‘passes to lower levels in the tree. The subroutine mi y S sequential systems. (ovels shows the routines from th GS) Fig. 107 10.6 REFERENCE ARCHITECTURE: [Network | Data link | Physical | _[ Physical |_| _Phypical ‘Communications mediums oa where a The common archit si igement routine itectural structure can be reused when hc new eden] | easiest Spc ee of domain-specific architectural model: is This is usually implemented as a case normally normally used fo communieate domain concepts and compare or evaluate pssie(1) nat are oe advantages of Arcitectual Desig? Which factors ave dopendat spective of architectural design? Explain. {@) Explain the folowing modular decompostion styles: (i) Object-oriented decomposition (6) Describe the various supportive contro styles of sofware systems. ‘oranization styes of architectural design’ Explain in bret ble during the veg User Interface Design TEE EEEshee main pes of SHS aysern whose result in injury, loss of {2 Saety-ritcal systems failure may cal sytems Teen example ofa safety-critical system i g Me serious environmental ies manufacturing plant roe failure may result in the failure of system fora P a tical systems: A syste Meson acy, An eagle ot # ots whose failure may result in very high cost, Sission-ritcal syStem 1S & navigg The met ery wiry dependabisty is the most important emergent Property °° are sev ‘ (2) The system shall perform reliably and deliver the correct amount of insulin to using well-tried techniques rather than newer techniques that have not been subjet ‘counteract the current level of blood sugar. extensive practical experience. Failure of the system could, in principle, cause excessive doses of insulin to be delivered and this could threaten the life of the user. It is particularly important that ‘overdoses of insulin should not occur,Figure: 156. Interface Testing. rated ‘Assume that components A, B and C have been integs em The testcase ae not applied to the ind terface of composite component created by combining the 154 TEST CASE DESIGN: that test the system. The goal of process is to create a set of test cases that are ef that execute that features, document the expected outputs or outpu possible, design an automated check that tests that the actual and e the same. (a) Requirements based testing: Where the test cases are designé ata time, response time per order should be less than 2 sec. (positive, negative, both), partition test cases by the magnitu, Test case design is a part of system and component testing when we design the test ive in discovering program defecs } and showing that the system meets its requirements. To design a test case, we selecta feature of the system or component that we are testing. We then select a set of inpus requirements. This is mostly used at the system testing requirements are implemented by several components. It includes functional tess and also non-functional attributes such as performance, reliability or usability Consider the requirement for order management system. Assume that its ordet entry function has been tested are: it must be able to handle at least 1000 custome In general, when des Signin from the requirements then teen structure testing. should start wit Add moce a ith the highest level tests Tailed tests using position and the test case desi nde | 155 TEST AUTOMATIO; Testing is an expensiv testing tools were among arange of facilities and there w, it ranges and where expected outputs are There are various approaches that we can take to test the case des est the system eas systen () Partition testing: Where we identify input and output partitions and design tet So that the system executes inputs from all partitions and generates outputs in! partitions. Partitions are group of data that have common characteristics such a5 All events arising from choosing items on a menu, partition test cases by OF Partition test cases by the number signe they “al ide of operands (lars Figure 15,7: Software Testing Toolsie Chapter 8 quirement Engineering Process cen software Enineetng (BSc Requirement Engineering Process 6.1 REQUIREMENT ENGINEERING PROCESS: developed together. _| 92 __ FEASIBILITY STUDY: “The goal ofthe requirements en a, | Th es four high-level requirements ng sub-processes. These are concerned with assessing, = =Vipua's™ Software ockbench is an integrated set of tools to supp’ Jeware testing Wo (b) Test data generator: rates predictions or prototype systems. 1 Compares the results o! ence between them. Provides report definition and ge 10 a program to count the number (@ Oracle: Gen program ve (@) File compat and reports (e) Report generat (® Dynamic analyser. Adds code thas been execu! Kinds of simulat program is to execute. f program tests with p (g) Simulator. Di simiilate the machine on which the Bees ™ the testing tors may be provided. Target simulators Chapter 16 Softw, are Measurem, ene ea 16.2 Size-Oriented Metrics 16.3 Function Oriented Metrics 16.4 Function Point Metrics 16.5 Extended Function Point Metrics Question Bank for Selt-Practice SSS‘vigua's™ Software Engineering (BSc rr) ‘Sodio-Technical System the rapid delvery and deployment of new systams often more important to ‘detailed functionality of those systems. approaches used to develop & Rapid development systoms? Explain (1) Explain why ‘han (@) plan how the princes undering agle method lead © the accelerated developmen. ‘and deployment of sofware. 9? Explain. Jes of Agile Methodology? Explain. J yment Approach. ‘Development approach ean be balanced for the development? (7) How plan driven and Agile Explain How do Extreme Programming pt Extreme programming expresses user requirement rammer to develop a better understanding ‘dtficuties with test-frst development? acices reflect Principles of Agile Methods? Explain. ts as stores, with each story written on a 3 development helps the prog . remenis, What are the potential yf (11) Explain Pair Programming (12) Describe Agile Project Management. oR Explain Sprint Cycle ofthe Scrum Process. \What are the problems in scaling-out agile methods in large technology companies? Expla, rite short note on: (@) Age Method. (0) Exveme Programming UNIT - IT Chapter 6 Socio-Technical System SSSSS55—————————ee 6.1 Essential Characteristics of Soclo-Technical System 6.2 Emergent Systems Properties 63 System Engineering 6.4 Components of System such as Organization, People and Computers 6.5 Dealing with Legacy Systems = Question Bank for Self-Practice2 we via Steer Engng 4:1 _ ESSENTIAL CHARACTERISTICS OF SOCIO-TECHNICAL SYSTpy4,__ $2°2Téchica Sytem nal policies s and regulates * Easential characteristics of socio-technical systems are as follows: (1) They have emergent properties that are properties of the system as a whoj rather than associated with individual parts of the system. Emergent propertig Gepend on both the system components and the relationships between them. 4 this is so complex, the emergent properties can only be evaluated once th | Re c em. It depends on | P technical system component, its operators and its operating ervionanent System components and hence change its emergent behavior. (@) The extent to which the system supports organizational objectives does not jt ~ * depend on the system itself. It also depends on the stability of these objective aaa co ee ENGINEERING the relationships and conflicts between organizational objectives and how peop Sofware Elecwonic | [Mechanical engineering | | engineering | | engnearing in the organization interpret these objectives. New management may reinterpt the organizational objective that a system is designed to support, and | successful system may then become a failure’ 62 EMERGENT SYSTEMS PROPERTIES: There are two types of emergent properties: (1) Functional emergent properties: Appear when all the parts of a system together to achieve some objective. For example, a bicycle has the functi property of being a transportation device once it has been assembled from. (@) Non-functional emergent properties: Relate to the behavior of the system if inctional properties are exe make the system unusable. Some users may not need some system function, vFed with software but also with hardware and the system's the system may be acceptable without them. However, a system that is } eaiaeploatnes ‘and its environment. cor too slow is likely to be rejected by all its users. Examples of some properties aresofware Ensneeting (8S My eoring PTOCeSS aNd the vies ngin« the syst disciplines pepe rnderstanding De ot COMPONENTS OF SYSTEM SUCH AS ORGANIZATION, PEOPLE 64 AND COMPUTERS: ip deliver some ‘are influenced other peopl ystems that are intended to hel the system are people Who tand the organizational he achieved and system may be rejected. Human and organization: system's environment that affect the system design include: (a) Process Changes: If the system needs to change the work processes in cxpanization environment then it is needed to give training to the people. (2) Job Changes: It may be possible to change the people's work in the system due their desl in the process. This may be happened with managerial position, wi reciuces thei status ©) Organizational changes: Complex system may suffer from the political p structure inthe organization. So that it may need further changes in the pt accordingly tie aan. socal and onpanzatinal factors are often critical in deter a system successfully meets its objectives. Unfortunately, predicting ssocio-Technical System this system. If the (which may run on business risk if the rep ‘Support eee ‘Application software sonware ms -| System hardware, processes Figure 62: The logical parts of a legacy system and their relationships (1) System hardware: In many cases legacy systems have been written for mainframe bordware that is no longer available, that is expensive to maintain and that may not be compatible with current organizational IT purchasing policies, (2) Support software: The legacy system may rely on a range of support software from the operating system and utilities provided by the hardware manufacturer through to the compilers used for system development.