a: IT-1" Software Process Maturity, Process Reference Models a uni (PART-B ESSAY QUESTIONS WITH SOLUTIONS |, SOFTWARE PROCESS MATURITY [LI Software Maturity Framework ai2. Define software process and software process models, Discuss in brief about software process improvement. answer # software Process Asofiware process consists ofa set of activities along with the ordering constraints, which specifies the proper ofthese activities for generating the desired output (or) a software process refers to a process that involves various issu {otechnical and management aspects of software development. functioning 1es related software Process Model Process model in general are idealization of process which are difficult to implement on real time basis. But idealization of process model will at as.a model for other software being developed resulting into reduction of chaos while developing software. Software process are abstract in nature and emphasizes on limited issues. There ae some speific process model which are very much useful in one context and less in the other.A software process model refers to the generic view of software process. [Generic view of] software model oe Definition] [ Development. | [Implementation ] - phase {phase hase rc iw fpr model : ‘Umbrella activities Figure ‘There are three generic phases of software engineering. They are as follows, 1. Definition phase . 2.» Development phase +3, Implementation phase 1.” Definition Phase ‘This phase emphasizes on problem understanding and planning of a software process model. The various activities performed inthis phase are as follows, (Analyzing the problem (ji) Formulating the problem (iii). System engineering (iv)_ Planning for the project. Development Phase . This phase emphasizes on providing solution to the issues that arse in the development by using umbrella activities. The _major tasks which are carried out are as follows, Designing the architecture Preparing algorithm of system (ii) Writing code forthe software program (iv): Testing the software. _ SPECTRUM ALL-IN-ONE JOURNAL FOR ENGINEERING STUDENTS Scanned with CamScannerTrmplementation PRsse se empha sch as deft removal ing the activit seit ane ay te pect a business and techie rakes ears that definition, developer agement, work sanagement, Project Mat a on and development prosess improvement, Software Process Improvement irmprovement i the inital step 10 “it is-a technique that considers see star ak 63 Foes a oe, contol and mescure i, Thus software pasess improvemen ee 10 achieve the desired output, Hence, cid that an effostive software process can be achieved ‘considering the relationships tools methods skills. training, People of required masks, ftware proves: taken by organizations inonder toachieve the required software capsbilities are as follows, 1. The current sams of developinent process’ processes rust be understond, ‘The vision of desired process must be developed. “desired process improvement actions must be hed based oa priority +The desired actions must be ak produce 2 specific plan, 5. The plan must be executed ba: The set accomplished inorder to sed on the committed - The primary objective $id MEASUFE and conttol the softens Brostts inorder to improve it.The process manny oN enables a user to define ascessment mathe Using whieh ScEetizaton can gather maturity stats. Besta th a Selves mansgements)sem that enables increatog ey ES Sasa £9 8510 provitizing the improvement Smucture specify the position of the process reece This the Grzanization can move to next level The wage ih Process maturity levels ate as follows, saree Level 1 : Initial This level is called as the adhoc level oxi level, This level focuses on defining formal pagal Process their work Beside this it also enables engage gee © lan Procedures for coding and testing. Monee this sefine this level alco iveor thie fmphssizes onthe improving the perfomance oh level are, WARNING: XeroxvProtdSiB Rg FORO E Bibi ani wi) ai) 0) Project Management rojee cent is a technique that foc. t management is | echniq) ect man i ents made by this techy, Se conmntments made By this fe ics see preparations, clear Fesponsibilitic, requires ager T penforace decla gement Oversight crsight is a technique that helps cr to review the developed plan Manai Management oversight software manager (0 approve it Quality Assurance surance isa process of managing the son eer assurance can be done by nominating vi fonnance of cach software activity like pl : Implementation and verification and creating independent report of the same. Change Control ate an efficient software by predi schedule term, establishi nt requirem and by maintaining stable development cycle, the requirement gets changed the designer must to incorporate those chang an when required Besides this, they must also focus on coding correcting the problems that are encountered in design and eode which gets encountered at development and test phase. Wchanges are not properly controlled, then designing, esting and implementation cannot be done properly thereby effecting the quality plan, le Process s. This level | process level by mastering the F state. At repeatable process level in be achieved by meeting the ‘The risks faced by the organizations are discussed below, A defined process fram Addressing the risk development proce technology ¢ Uestroy the hist ework must be capable of an curly stage of software » This is because, without san harm, affvet the process and ean historic (or) base on which onganization relies, Development of, : OF new ett Of new type product can lead to ereation have expen td tisks. ‘That is, « software team who ‘Ve experienc dleveloping compiler may encounter Problems in s, hedule: na entea : i Fal who have created a selt-contained programs may sierience intertnce and integration issies. This ean lead ‘destruction oF intuitive history of organization procece on, Similarly another es within of disruptive, make the process highly RB Kai uty LAADLI Waid LEGAL proceeding, Scanned with CamScannera UNIT-1. Software Process Maturity, Process Reference Models * isa ‘Beside this, the bi 58 i 10, Develop a ‘A process group is a group that focuses on specifying proces. tary stage of maturity, software oganatone mainly focuses on developing a work product rather than improvement. Hence organizations must develop ot establish process group that is responsible for providing, improvements within the software process, ‘Thus, the responsibilty of process group will be, : ie purpose of repeatable’ software proc L rocess Gi (i) Defining of development process (i) Determining new technologies and needed ‘opportuities. Advising on projects (iv) Performing quarterly management revi 2. Developing a Software Development Process Architecture or Cycle A software development process architecture or cycle ‘must be created inorder to represent technical and management activities that are needed to execute a development process. This architecture should fulfil all the desired organizational needs irrespective of the size ‘and nature of the project. Beside this, the development structure describe the structural decomposition of the development eycle into multiple task. Where each task specifies functional des ication procedures and task specifications. 3. Establish New Software Engineering Methods and Technologies Asetof software engineering methods and technologies method must describes about, (i) Design and code (ii) Formal design methods Gi)" Library control system (iv) Testing methods and (Prototyping. Level 3: Defined Defined procesé level enables the organization to achieve ‘major and continuous progress. That is, a software team can wspection oftware process. This | 2. Resource data base can be managed and maintained by developing a process database. This database must include the cost and yield data to safeguard against loss. helps in making data available for other projects to ensure process quality etc. 3. Process data can be maintained by developing sufficient process resources, Skilled professional must be assigned to monitor the data quality before maintaining in the database, providing guidance on interpretations ete. ance group must Be responsible for ‘quality of the product and informing it to the management if the desired quality is not met, 4, ty a Level 4: Managed Managed process also focuses on making considerable! essential software quality improvements. The drawback of managed process level is, it incurs high data gathering cost Eventhough they aire many potential measures together the data, they are very expensive to gather and maintain. The major problems that are encountered by managed level are, (i) Data gathering must be done carefully by defining each single of data in advance. . (ii) "Non comment, non blank lines and executable instructions are treated equally by assemblers. This lead to confusion among developers. ii) Management, test, documentatign incurs more costs. (iv) Process data cannot be used for performing comparisons among project and individuals. ‘Thus, the advancements that should be made by managed process to move to next level are, (i) Gather the processed data automatically. Userpective of the error and omission. i) Make use of process data so as to analyze the process, to modify it and also to improve it.” Leyel 5: Optimize In optimize provess level, the data is made available for processing, Process optimization is done at each level of process ‘maturity. I is done inorder to ensure the process quality and productivity. At this maturity level, the software development ‘manager are responsible for pa analyzing data that leads {o product improvement optimized level, 1, Errors are identified and corrected. Ueda ihe defined preons when they aren need or they |"2, Code and design inspections are performed, encountered any issue. This basie purpose isto verify the wt det a eesinia “sfivare osess sed roprove i The steps taken’by defined | °° Tesing's done to cover the errors that are uncovered, '0¢e85 level to move to next level are as follows, 4. Weak entities of the proces’ are identified and replaced. 1. the cost and quality, parameters must be identified of | 5, Wentiieation is done to,ensure whether the needed Process measurements.T identify the costs teetootvay Ie edo {nd benef ofall the activites major proses, error 7 ore reton Cel eccon met cot 6, Effectiveness of process measured, i |. SPECTRUM ALL-IN-ONE JOURNAL FOR ENGINEERING STUDENTS. ah Scanned with CamScanner18 a SOFTWARE PROCESS AND PROJECT MANAGEMENT UNTU-HYDER, ; Q14. What Is the need for process optimization? Discuss the people involved in optimizing process. Answer t : Need of Optimizing a Software Process A software proce must be optimized due to the following reasons, 9%. 10. 1 improves the quality of large and complex code. W enhances the productivity of the system being developed, Mreduces the size of current system being developed. I makes the process of testing easy, It provides idvancement in software quality. Walso improves the quality of system being developed. 1 produces large volume of new code, Menables software manager to understand how to assist People/customers in need. It provides people with required support. Hallows software organization to improve the maturity process, People Involved in the Optimizing Process An optimized software process is mostly dependent on quality of people implementing it, An effective optimizing Process assist people in the following three ways, 3. I enables software managers to understand the people needs and assist people/customers in needs, It provides people with required support. It enables software professionals to communicate with stnall, comipetitive and numerical terms. It defines software framework that enables software professionals to emphasize the work performance and improve ___ 1.1.2 Principles of Software Process Change Q15.. Describe the principles of software process Answer + - change and TSP. OR Discuss the principles of software process change. OctiNov.20(R16), Gea) (Refer Only Topic: Baste Principles of Software Process.) Model Papers, 2(a) Dec.-19(R16), 02 Basic Principles of Software Process The six basic principles of software process change are as follows, he 1. Changes Pertaining to Software Process Must bi Developed from Top This principle suggest that, changes per software process can be doné based on the of senior management. That is, management t focus on providing long term improvement by, @ — Understan a (i) Monitoring progress. ii) Analyzing the performance, ning to wlership 4 fact Anwone f0Und cit. Besides this, the software managers magi gy Bay setting priorities, supply of resources ang kin continuous support to the users. Heng, the changes involved in a software progeny from the top of the software cycle, it Involve Every Software Professionals ‘This principle of software process suggest thy ‘ so engineering is a process that involve team «150% ork, people who gets involved in software process sufficient knowledge of software engineerin, in creating a mature.structured efficient a software process. Moreover, each team mem support each other inorder to improve and sofware process. Hence, the people who a; eT 8. Tisha nd cengy ber ny execute g Ie invol ip improvement process can gain huge benefits an). even achieve progress. Changes can be Done Efficiently Based on Goal, Knowledge of the Existing Process This principle suggest that effective changes can be by analyzing the goals and knowledge of the cv Process. The software engineer must coristantly track of the process when required. Changes Must be Continuous ‘This principle: suggest that, management team mi recognize that changes are static. Changes pertaining! softwate process must be constant and their adjus must be done periodically depending on the task relationship. This enables a software team to leam skills and solve multiple problems. Software pr change can be done based on the following. (@ Changes which are reactive makes the sot Process difficult, Gi)_Defects can be improved at every stage ofso process, Prevention of crisis is much better than its Changes about Software Process can be Reta with Continuous Effort and Periodie Reinforce Improvemé; Investment This principle su, improved by, 0 Performing continuous planning CC) "Involving dedicated people ii) Managing time” nt in Software Process Needs '88est that, a software process ') Capital investment, For answer refer Uni Process (T3p). "UPI, Q5S, Topic: Team Scanned with CamScanneryo Tpiscuss the common misconceptions about até. Sofware process. answer? common Misconceptions of Software Process The following are the misconceptions of software pees 1, Beela with Analyzing the Firm Requirement Sofware process basically focuses on gathering the ofware requirement. Thus, gathering of essential software Sirements is the essential and basic step of software SRacering. The requirements that arc gathered must’ be ‘Senged not only based on the demand of firm but also on Sxomers viewpoint. Besides this, the change in software Seultements can be done depending on the progress of Suware.-The process of change begins as soon as the ‘piements are gathered. This process continues until the iEplementation phase gets processed. This scenario is tsially followed by organization following small scale cogams. However, requirement cannot be stated easily by inge scale programs. Software development is a incremental process that sepsis small incremental steps. At each step of development, dzails of requirement and implementation are completely sized. Here, the misconception is that, software developers. tesically thinks that gathering of requirement is a customers jpband the development process does not begin until they are ‘fined explicitly. The misconception about the above concept canbe summarized as follows, {) Customers does not generally have idea of what requirements are needed or required. (@) Initial requirements are often wrongly collected and canchange. (i) A link must be established until the application and work gets processed (or) until the current job gets completed. 2 If Test is Performed then it is OK Testing of large and complex programs requires émplex operating environments. This is because, testing isa teliable system indicator that ensures software quality. Testing is mainly done inorder to identify the designing and coding ‘Tors that leads to program failure. Software testing makes the Program error free independent of type of testing being done, However, if large program contains errors then testing cannot ‘completely thus, it leads to an unreliable system. To ‘oid such situations the following must be done. -Abigh quatity software process must be developed, (i) An error free program must be developed based on complex system. ui1_ Sofware Provess Maury, Process Reference Models 1.9 ablish to limit the ‘A defect free process must be est complex high reliable progra 1g must be done on the program. Software test cy) (¥) Recognize and develop a large defect-free program so as to manage and improve the software process. 3. Quality of Software can't he Measured Software quality measure the effort of quality oF 1 progess being developed. However, there is no specific measure that specify the programming quality. Quality improvement depends on the amount of effort made in improving the software quality. Software quality improvement ‘must be done inorder to avoid social and economic damage that arises due to huge error with in the code. Besides this, software quality improvement also enables users to prevent and remove errors. Ths inital step here is to define the purpose of software quality improvement. This enables a user to find the terrors which resides with in the system and set the ultimate goals. ; 4, Software Problems are Technical Technical software problems are not high priority problems. Since most of the software problems will be at maturity level I/level 2. Their focus must be to create an orderly process and allow people to efficiently operate it. Besides this, low-maturity organizations focuses on controlling the changes, recovering the defects and performing later enhancements. Such organizations produce products with unpredictable cost and marginal quality. However, most of the common software problems gets solved before time by constantly reinventing the solutions for disordered and unmanaged process. Here, the misconception is that inspite of using improved languages, environment and tools, some of the technical software problems like cost, schedule and quality remain unchanged. 5. Involve Better People Software.engineering is a important software development process. Hence most organizations must try to involve senior executives in the development of software process. This is because highly experience programmer have the capability of providing accurate information error free software code, adequate facilities, well defined methods and procedures. However, the misconception here is that since errors are made by software professionals they must be responsible for the loss. 6. Managing Software is a Different Process Software enginecring is considered as different from ‘other engineering fields due to the following reasons. (i) Itis difficult than other engineering processes. iy ctimes does not involves senior managers and nals with sufficient experience thereby making the software process ineffective. J SPECTRUM ALL-IN-ONE JOURNAL FOR ENGINEERING'STODENTS *vi9% ‘OMIA Scanned with CamScannerre solutions fii) _ incurs high cost thereby : fe (Mraiscoer the systems problems very Ta Si docs not fallow any stable physical principles ou aive software management diseiplin. fy ua ue at provides software em element th: ( Tinsonist y hiding the implement iamctonaiies to end users by hiding the implementa based on view point of eustomers. (vi) Integrates various system elements together. (vill) Tis considered as a black-art by most of the non= software practitioners. Ths is because, it does no software managers to solve any problem on their own. G17. Describe a strategy for implementing software process. Answer t Strategy for Implementing Software Process ‘To implement software process change, software takes tw forms. |. Software professionals intially considers the changes as immutable, incapable and technically insoluble, However to solve such problems they include detail Procedures, standards, ules ete ‘The management does not understand the real software Problems, However, an effective change in software process eme ploys the following three phases, 1. Unfreezing 2. Moving and 3. Freezing. In software process, unfret for to understand the sofiwate proble of software change can be done based is considered as the best "ms. The implementation. on the following, 1, Champions, Agents and Sponsors (3) Champion sponsors, il) Launches the change program, (f¥) Maintains focus on achievin Champions have less eh () Agents w the desired goals, ance for success, carrying out chan, Phase. They are responsible for, ("Specifying the resources, Gi) Assigning the task, 3)” Making caso senior management ete, | should be sclected bas; ‘Agent! consideratio : (They must be responsible for carrying, process. ble of understand res ‘hey must be capal land (ii) ae ical and political software proble (iii) They must respect the people with whoin , Si idence of manag, iv) ‘They must gain the confi ~~ © fils store ‘that they will act with coo; acceptance. (©) Sponsors Sponsoring is a process where senior mana, recognize the value of work and sponsor it. The proes, of sponsoring is done with the help of resources x official backing mechanisms. After sporing, the tas champions are done based on which the chai can be initiated. 2. Change of Elements In software engineering planning, implementation communication are considered as key elements of effective change. Planning phase focuses on inclu ponsible for developing a compet plan‘and ensuring its acceptance. After this, the stot implementation phase can be discussed, Here, some initia efforts must be applied to mini 8 Atthe end, proper communic fo maintain the project progress. @ Gi) Git) (WY) Establish dedi rocess i 8essment Principiessment? Discuss Software Process Assessment Software Process asse formed by s Ware an et is = oF software mena 8Anization st 8 typicat soview pote Sottware professonaty hige i®™ is done by team Praren Petience. It is condueteg' SS DiBh train, aasese Professional and my; vn ‘nagement abo Operations. Bes, the overall sottwar reviewers can exai <8 Of improving | * local and outside , Anjo fond gut is UABLE to tang ie Scanned with CamScannerFa iT-t_ Software Process Maturity, Procoss Roferonco Modes Goniware process assessments main purpose Is wo deter inet i vii ates rowenta pies i go pao senescent, These vine o eet eabls eal solar mangge an fein aston tei operons By providing puidange to them on 2 improverens st he dan sessment Peps ‘Thebisic assessment principles enables competent team, sound leadership as well 8 the cooperative onganization to se the sftvare proces, The various sofware assent Frese discussed below, 1, Hentify the process model needed for performing as sessment gy Recognize the requirement with strict confidentiality, 5, Involve highly experienced senior manager 4A. Respect the view of people working in an organization ‘with open mind. 5, Concentrate on actions, 1, Identify the Process Model Needed for Performing Assessment Software process assessment defines a standard process model which enables an organization to review a process based ‘he vision specified by the users. This enables a user to com pareassessment processes with the organizational process. The process maturity model provides a framework to perform the Comparison among various processes, However, the team that perform assessment must have extensive software experience. This is becaus ment pro- cess gts easly degenerated into loosely directed exploration. ‘Asthe team member of assessment mostly focuses on specific considerations rather than complete assessments. Moreover, if the assessment team gets divided into small individual groups then there are huge chances of considering all the key topics. But, this may result in creating multiple views of software operations which in turn leads to reduction in likelihood of a result, Thus, to avoid such problems assessment must be done by keeping common view of the designed software process, Hence, software assessment process model. act as a basic 0 explore the software process. It addition to this, it also act as a framework to setup problem priorities using which the complete assessment team ean work in collaboration with each other can address on the key issues and recommendations 2. Recognize the Requirement with Striet Con “This assessment principle suggest that, assessment must be done inorder to improve the software process ‘based on sreanizations viewpoint. This type of review must be done by hiding the problems from higher management, Even though i isyery dul to maintain trict confidentiality particular he tigher executive wants to see the results but also assessment team must tr to maintain strict confidentiality. This is because, identiality (® Confdentaity allows assesors to discuss the levels of organization. . Gi) Confidentiality is needed at organizational level sos specify the professionals that their comments: would not be attributed. SPECTRUM ALLIN-ONE JOURNAL FOR ENGINEERING STUDENTS | wd Anvolve Highly Expertence Sento avolved in assesment process Senior manager must be nites tothe organization ivsthey are capable of ssiining, process assessment, local manager are responsible f ing, approvals to soltware commitinents, Hesides thi ilvo responsible for acknowledging the corporate Where as, the ¥ of senior manager isto handle Liple projects tio ‘cations, This helps in eliminating, project disruption, simplify assessment ar nd t0 promote consecutive action plan andl impler senior manager is refered to as site manager. The site manager ie responsible for performing assessments based on the Follow upaetion plans. This plan ineludes the work that must be done with priority, Moreover, the site manager must participate 1m (i) Performing reviews periodically ements pi shem, Here (i) Assigning qualified people for work (iii) Analyze the progress of the action plans. 4. Respect the Views of Péople Working in Organization with Open Mind Software assessment is process carried out by group of remote experts. That is, in large and complex organization is considered as a review that is done to improve the overall software process. The local eystomer who are involved in the ‘work hard to complete the improvement pro- Fully, Thus, the senior management must focus on ‘aking local Views of the customers, The assessment team must ke the ideas stiggestions of local people and evaluate it based on local conditions, They should recognize the ideas and must adjust them with open-mind, professionalism and positively. 5, Concentrate on Action software proce The main purpose of software assessment must be improvement of software process, Its main action must be to provide solutions to current problems and handle priority issues ‘and also to implement the recommendation procedures. Prior to software assessment the software team must try to explore the general problems, understand the issues and try to solve them. Since this is very tedious task, software process assessment i considered as an accurate procedure to improve the software process. In this, the concems and suggestions are discussed to and reported to site manager. Later, based on the approval of ‘manager the improvements are dot ‘Q19. Describe the assessment process. Answer t Assessment Process Assessinent process can be earried out ba steps, dentify an Assessment Team and the Org P, assessment team is formed based on the view= point of team manager, Initially, an assessment team manager ‘who have huge sollware experience is selected. The assessment manager must have posses the following eapabil @ wo, ‘They:mmust handle small groups and ‘They must have sufficient assessment experience. Scanned with CamScanner“After this, the assessnzent team member who is APO vies "nent sofware developer, have experience in modeling Mere owst he Ware process is see = 4 minicnum of six software professionals. The assessmen! (2 ust Be selected based on the below guidelines. (@_~ Am sessment team should include a sofware profes sional who have eight to ten years of software experiene®s Gi They mist Fave respect in organization. (ii) They must deal informal people eiciently (iv). They must be a team player. (v) They must attend th ssment training with team. 4 be selected from roup ‘An efficient assessment team group who are involved in assessment process rather th ‘ho are selected for review such team members ean also be selected from assurance or support group. However, the people who are involved in the process of reviewing, managing and supporting the assessed project must not be considered as an assessment team, Even the members involved in parallel proj- cet, local test, Software Quality Assurance (SQA) can also be ‘apartof assessment eam, Besides ths, atleasta singe software professional who belongs to the organization must participate full ime assessment team member. They must focus on (@ Planning process (i) Provide background knowledge about organization ii) _ Set up focal point to logical assessfient and follow up action plan, Step-2: Considering Self Assessment Self assessment isa process wherein the organization assess the software process by themselves. It is basically done in order to identify the potential problems that are present within the software process. This assessment initially carried out by assessment staff in most ofthe organizations. Inthis, temporary team of members usually gets involved in the assessment process and try to assess the software project before the site manager gets involved. Moreover, ifthe site managers wants to conduct the self assessment by themselves they can sign an agreement along with the line manager and must make a commitment to Support it. The considerations that must be made to perform sell assessment are as follows, (i) Assign work to people when needed. i) Attend the essential meetings. (iii) Develop an action plan to describe the recommendations. ‘Step-3: Defining Assessment Ground Rules ‘An organization must define set of assessment ground rules for assessed organization and assessment team imembers fo carry out the assessment process suecessfully. An extemal assessment is basically Carried out by site manager and it team leader. ‘To do this, they must si a round rules, These rules are tested assessment agreement including the below. WARNING: XrouPnotBeOR GANA ORRIN acoA HE ain ui EE [JNTU-HYDER, gr MANAGEMENT E ERA, —asment ent tea me eae ent cont aa ingandcosing F285 Mn, i ple: THe OPT ey team MEMES eo involve atlea aber must ZOvOIVE ATCT ule-3: The site ee regular member 10 hy fessional Pr ements aM EXME th woolen aane™ follow-up action plan. ie | 1 ment and implementation off), rule The ere pe dn By site mana action tent ecommendtions ment sl als be e-5: yal member of assessme ea ess ee er rating 2 ation ple. ternal assessment, the organization cane Peaed based on the above ground ni conduct in-house assessments 4: Train the Assessment Team ‘The assessment team must completely participate training period, onsite review as well as Wrap-up meetings team should attend each session by ste Keeping the unrelated calls on hold. Rescheduling the meetings and Rescheduling the commitments. Moreover, the role of team leader is to conduct at about the assessment process among the assessment 2 ‘This enables them to establish a cohesive work group. assessment training to new team can be conducted cither the senior management or by the member who are prev trained about the assessment process. This training pros catried out inorder to make the new team understand about, @, i) (iii). Participate equally in assessment process. How organization is assessed? How to contribute on assessment plan? The training program is conducted in the fol ‘manner, 4 Initially, outiine the s cc Inyo 1 schedule and object 2. Revie Review the assessment principles i Me process model which is consi assessment framework 3 , . ‘outline of organ at dy te line of organizations mission ms sessment team based on the manage! Stvctu an tisony tO" Me NS pe Pac the assessment guidlines with te team : ssk them to sign/authenticate the writen ag" Conducta team building exercise that helpsin esti 've and mutual supportive operation mode ‘an effect WIS LIABLE to face LEGAL proceedings: Scanned with CamScanneruniT-t_ Soteare Process Matty, Process Reference Modols assessment plan must ude the follow Topiss of all the sessions, Discuss about the leader assignments, BSeotify the errors and how to eliminate it When team conchusion must be reached and how. (9) How to prepare and present the report, when to prepare it and who will present it = Rebearse the portion of process until the team members es comnfortable with its role, Final rising task must includes the details of on site pesied planning. An on site planning is a process where size mesiher can make a note of key active projects. ‘They can also discuss the way in which the desired project can be assessed. This planning process also ‘oa identifying the different back-up projects iff certain projects becomes unavailable. To cover the entire projects review of three or six projects must be done. Based on project selection final details of on-site period sboald be fixed depending on which meeting can be sooducted. participants can be selected. maintain daily schedule and provide administrative support. ESET rere PCT [2A Discuss in detail about conducting assessment. Asswer : Assesment Conduct Assessment conduct is a method used for implementing ‘se conse project. This type of implementation focuses on eciving maswes to the following. @ The purpose of the developing project. @ The dewils of how the project works, GH) The various problems encountered. ‘) The desired result that can be obtained. ‘The mswers to above set of questions must be prepared ‘rire tae arual assessment period gets started. The project mugs is responsible for reviewing these questions and also ‘ix prviding the overview about status of the project and fur- ‘ter suggestions. Assessment is generally conducted to ensure ‘the the software process is developed on time with sufficient mac ‘The assessment are basically conducted by a meeting ‘is 2 soup of software professionals or representative who ‘use ara knowledge on the’below facts of software process. °) Software quality assurance and release. Software testing. Software integration. Sofware coding. Unit testing. "Designing and requirement gathering. fg SPECTRUM ALLIN-ONE JOURNAL FOR ENGINEERING STUDENTS 59. 11d is estions n,m icipate in this assessment Asses professionals to provide su The representatives Who pa possess the following capabilities (They must be a opinion leader ny key problems. Gi) They should work on project iit) “They should be téchnical professional instead of tang (iv). They should understand the assessment process with confidentiality To conduct assessment below steps must be followed. Step-1: Exploring the Questions Assessment cannot be conducted efficiently as it is It to get accurate information. The reason for such iency is sted below, ()Misunderstanding of questions by the respondent. A software is basically developed in an English language. Since English is an indefinite language even a small + question may some time leads to huge explanation. «i Different understanding of few common terms by the respondents ‘The respondents must have understanding on common terms like high-level language, review and reusability. Thus, assessment team must discuss on the required terms. Respondents are unaware of work going on in their organization Gi) Many software professionals narrowly focus on special areas of software process. However, they are some times uninformed/misinformed about the type of work going on in organization by the managers. This is done inorder to check their experience and to fitter the current knowledge of people. People cannot accept the truth The respondent will not willing to accept the truth about misused favorable terms, unusual events ete. As itis difficult to obtain the accurate information for above reasons the assessment team must examine and check ‘each phase of assessment. wv) Step-2: Assessment Conclusions Assessment conclusion is a method wher¢in an assessment team creates @ conclusion report on preliminary ‘outcomes. This report includes the following. (i) Detail description of site status and (ii) Summary about preliminary key arcas. Initially this report is reviewed by the project manager followed by the site or project managers. This review is done in order to identify the problems or topics that are overlooked, misrepresented and overemphasized. Bee Scanned with CamScanner‘based on initial outcomes are, 1es of the Projects (Review the major iss (i) * Identifying the key issues of next maturity level. (iii) Display the supported assessment. (iv) Action recommendations that are addressable. (%) Extensive generalization, Similarly, the guidelines to ereate assessment conclusion based on presentation are, (Agenda Gi) Scope of assessed project Conducting assessment based on schedule 0) Step-3: Assessment Report ‘Summary of composite status ete, Assessment report is a final written report and Fecommendations created by the assessment staff and site ‘manager. It includes recommendations of atleast four items which are of high priority. As organizations cannot handle ‘multiple tasks on time, the task that requires special attention ‘must be reduced to ten. Such recommendations must be explained clearly and must be implemented based on priority, The outline of report will be, . @ Summary and Conclusions It includes the detail summary of outcomes and | recommendations, (i) Assessment Background specifies detail description of assessment background and assessment process. (i) Site Status It describes summary of site manager, (iv) Key @utcomes I includes brief explanation about each outcome. “W) Recommendations It defines des priority Appendices ion of recommendations based on wi) It specifjes assessment agreement, ‘The guidelines that must be followed while creating assessment report or recommendation are as follows, @ © Wording and formatting must be done carefully Gi) Star the recommendations with a single or two sentences (Gii)__ State what is recommended, Gv) Specify the purpose of recommendation and (%) Specify the process of earring out the recommendations. An as because, ‘A written recommendation enable ‘understand what isto be re @ the ass minriended, Iteliminates ambigious records oF vn, Itactasa ideal 001 hat helps the sotvencpy to clearly deseribe about the actign | in implementations. ins Step-4: Action Plan An action plan isa follow up plan prepinsy local organizations under the supervision of kn, assessment team member. It specifies how the be carried out here, @ ‘The software professionals must prepare an ction for better result and acceptance. The key manager must be responsible for trac ‘outcome of the actions taken, ing ii) The site manager must periodically review the su and progress of project. Step-5: Reassessments Follow-up: assessments must be conducted organization after the development and approval of inital plans because, (@.__Ithelps in tacking the progress of the project, Gil) Itspecifies the future milestone that is needed to com, ‘an action prior to assessment, Gil) Tehelps in assigning new priorities for contin improvement, 21. Discuss in brief about various consideratk to implement assessments. Answer : Considerations to Implement Assessinent ‘The considerations that must software assessment must be intermng 1 Risks and 2. Staffing, be taken ‘to imple of, inti retary improvement. Hence, a catalyst ir a i required ler wher ig i enn ‘Sub goals are specified, Here, ee ae WARNING: Xecouphtseii oth bss CRMINAL Anji oid uty is LIABLE ofa LEGAL py for maint ‘anager is responsible and establishing the periodic issues, SP&*if¥ing the plans L Risks * The key risks and actions of sofa | He process (2) Sehedute Contticts aes oe Schedule conflicts is a process . | ¢ third of asses i EPS in condut- | We 10 discuss about the underlying jotP8 enables the | manager. PME Fu with the te | Scanned with CamScannerer nt sobre Pees Hy Pres orn A Faatequate SUM > » ee . (ii) Senior Management rast , evélop an operating, ed Se nager is responsible to develop 3” 0P% eaten v tone segue ise, Moreover Competent people, Ths increases the frustration amon mae anager ae responsi for managing sole as the management spa provide sucien orzo pi aes 3 (i) Software Manager fg. basket Fallow Through ag management chi evuntered then the site i plan. Sie meNABeT rand complete action plan, Wa Rep hen mprovewents cannot be done eit, He a eca be abhieve ifthe managers change ffs have ees improvement cabin proper improvement al 2, Staffing staffing is also an severd implementation problem. Itis assessment technique that generally include, fp A small group of poople/staff who works flltime jnonler to provide improved efforts software engi process group. {a Participation in part-time project within action plan ‘working group. {Gi) Implementation and review of project based on resulting actions, L.1.4 The Initial Process (022. What are the tasks involved in initial process? Answer # Model Papert, 2(a) ‘Task Involved in Initial Process Initial process level is also called as adhoe process level “Atthis level, the requirements of software process 1s defined, $anned, managed and developed. This phase does not deals with predicting cost, quality assurance and scheduling of project. In this phase, the software professionals focuses on identifying the unplanned priorities as well ay ihe unmanaged change. AS such identification cannot be identified easily. However; as the software progress the unplanned priorities and uninanaged thange can be easily identified. The members who belong {0 this group must plan about, Delivery of project on schedule time, Gi). Efforts that should be made by individual on a specific Project and i)" Strengths of the organization: ‘The staff that are included in this group are, © Welt Intentionéd and Competent People Such people do their job effectively on committed time, But, dueto lack of efficient planning and management, resources, por coordination they fail in performing the Tequired services. ible for managing the yy replace by new Software manager site reso! software, But, they are frequent manager as an when required. sthat must be performed at initial level are, The bas 1. Planning, 2. Costestimation 3, Project Scheduling 4, Perforniance tracking 5. Change control 6. Commitment management and 7. Quali Q23. Discuss the common problems of chaotic software behavior and general solutions for the Answer Problems Software manager most oftenly make guesses instead of plan. If the guess fils it leads to chaos (problems). Eventhough commitments are considered as accurate but ssome-times the project scale and functions are based on previous experience of guesser. When the creation of software gets rough, then people strongly believes in magic. At certain instances a “savor” can be encountered or new technology can work. This ‘occur due to improper planning. ‘To scale a software project following cycle must be fol- lowed (Approgram is written with multiple ines of code than expected. (ii) New technical and management issues occur as the programs become big. (iii) As this is.a completely new experience, it is a surpris (iv) If there is an increase in scale, then the cost in- creases. Higher maturity level is achieved by an organization (or) net management de to erred competition nd new technical challenges. The maturity basically in due to lack of training, — 3 SPECTRUM ALL-IN-ONE JOURNAL FOR ENGINEERING STUDENTS 9c). -SiiAtiAn Scanned with CamScannerGans fei proses cams management must be app and managing the process- L Jed by controlling ning, implementa The gefieral solu 1, Systematic project estinating lamin and 2. Change management must te inh changes gathering requirement, d tion and test. Software assura ‘etn proesinadeto este that activity are performed properly. ‘The! fed principles that must be followed by a software organization to contol the chaos are as follows, ‘Work must be planned. * Maintain the track of the plan. Partition the work into multiple independent tasks. Specify the requirements based on each part “Manage the relationship each par. Consider software development as a learning process, Fix the gap between the knowledge and tasks, Identify what is unknown, Work must be managed, audited and reviewed inorder ‘o.ensure that work i properly planned, ‘Complete the assigned work to meet the commitment. Define the plan to improve the knowledge, 2 THE REPEATABLE PROCESS Q24. Write short notes on commitment discipline. . ependent formed using independ ce musta singin 1 2 3. 4 5. 6. 1. 8 9, OR When the process is repeatabie? Why? Answer : ‘OctiNow-20(816), a6(6) Repeatable Process A software process said to be repeatable iit allows a st of actions to be performed for making the software efficient hile minimizing the variations in development and limiting Unwanted resouree utilization. For a successful and efficien, Software management, commitment discipline plays akey role Commitment Discipline Software project management isa technique that focuses ‘on managing the software. Is basic purpose isto ensure succes ‘completion ofa project. To ensure this, system considers commitment Reviews 1¢ must be properly conducted py embling enforce anion ‘the responsibility of senior mat per to perform the me are discussed helow, commited work (i) Define work among customers and develop 0) Produce a docu estimate, cont estin rent plan con se and sc! ing. resource ule Involve parties who a agreement ii) ree upon a written Develop a business and technical pre censure commitment irespective of risk. (iv) tion to (v)_ Enabling the participating group to make use the resources. as an when required. (vi) Conduct independent review to ensure that work. done in accordance to organization standards. jement system of commitments. Answer 5 Management System ‘The general objectives of management system 15 based on the following components. . 1 Defining a technical and business strategy inorder to achieve long-term goals based on growth rate and market position. 1. Develop ahigh quality product that helps in meeting the ‘customers requirement in an efficient and timely way. 3. Completing the assigned mission competitively and economically. 4, Improve the ability of organization by handling chal- lenges. “The above objectives are followed by most of the orga- izations to achieve the desired commitments, These objectives: ate common to all the software groups since they have equal tribution for defining resources, assigning priorities, gencrat- ing short term responses, idemtifying long term performance, itageoving productive capability and delivering of products, In management system, senior manayement is respon- sible for 1. Creating annual revenue report. 2. Identifying profits. 3. Measuring productivity 4 Producing quarterly and annul work report by corporation. jonven Models LAT The conflicts that effects the efficient ma tem are disesrssed below, Plans of Product and Period “Annual operating plans creates an operational framework fine and staff This plan includes the task that must be 1 as responsibilities to of resources to project in project planning bet perforn complete th and staff are consider ‘he various types of plans that are defined by manabe iment system 1, Operating Plan 1 issues of organi it is possible to develop Itdeals with business and tecbt tional and annual terms. Due to this, the following based on each organizational entity. (i) Capital requirement Gi) Expenses (iy Specifying product delivery (iv). Defining annual productivity ()__ Stating annual profitability and (vi) Specifying management strategies. 2. Project Plan Project plan describes objectives and responsibilities of each project. The issues pertaining to project plan are cost, schedule, function, quality, resources and checkpoints. Since teach project has their own set of resources, some of them are required for common purpose on periodic basis. Eventhough, the purpose of product and period are cleatly stated there are few distinctions between the two. That is, ‘a project act as a fundamental business view of an organization where as period specify the needed information, Besides this, it is impossible to measure project based on annual basis as it is Jifficult to collect annual data on cost, quality and productiv- ity. However, itis possible to measure data on periodic basic by translating the project data into periodic terms like annual budget, plans and reports, 3. Management Overview ‘Amanagement system makes use of review arid tion system inorder to resolve the conflicts that arises between product and period. It develops a balance between line and staff. As both organization line and staff enables preparation of annual reviews and plans of all the involved parties. If conflicts between produc ce prepare a consolidated project plan which can be i peep an be inc in later subsequent plans of next organizational level. tiene unique individual plan is created by each project prior to peoiecy initiation, periodic reviews and update. Prior to project __ SPECTRUM ALLAN-ONE JOURNAL FOR ENGINEERING STUDENTS pares RL Thico:ex SMA Scanned with CamScanner===”. SOFTWARE PROCESS AN GEMENT [JNTU-HYDER Ap, 1D PROJECT MANA o 1.18 ition. The bi ‘Contention Process tional re asi sion and rational crn easion ge best decision 10 solve it, The Maipts of contention system, expr support per eve ys 10 SUP et and sof the erstand the relevant iaswes : i in The following are the PP iscuse the possibilities contention ystems followe allowed yy contention system jx 1 ui ieee yee 8 all involved parties if ine best dec of apneement and ther (i) Review the major decision wit ‘of issues hefore proceedin ther to state view and take decisions: ate agreement if there exists Giy All the dissenting partion must any disagreement between the pi, Gil) The senior member sho Cicada, term used to assign responsibility for su, Contention ayatern does 1 missin 5, Quarterly Review 1 software process. Quarterly FeVieW is done ement system must focus on performing quarterly gs, .w is done to monitor assess; and goal review om th proup of people ta resolve product ee ee age operation like projects, technical support as ws ci ci an Magee (SM, Sots ag surance (SQA) and Software Engineering Process Group (SEPG).’ ia ee rina plc Fei vsof E ba scm lin and betes Bei i producing and veloping standardized soar proces improvised methods and eels ‘Q26. List and explain the project planning principle Answer: 4 Mode! Papers, ‘oF project and ong: In quarterly review, site manage 1 finance, The tectmical support of oF Project Planning Principles Project planing is technique that enables a user to estimate the desired project on time with sufficient resource. Ii framework for managing reviews and controls It is a process for analyzing the actual performance of the system. The bas ject planning principles areas follows, ih £1 equiements ar unclear and incomplete, then a quality program must be developed with accurate and corréct un. Sepang ofa. The project plan bezins by mapping the unclear and incomplete requirement to accurate and pre 2. Develop a conceptual design based is Develo cme a Oi on plans design is a initial structure that defines breakdowns of unit p framework plan and implement ees eltionships between units. This inital structure also acts an organiza i ae work, It's impossible o cover error from conceptual design. oe " he requirements, resource projection, size estimation and schedule. evelop a detailed design and implémentation strategy i ; ‘ tegy if require {Establish implementation details and document 6 Pj pan aetasa amen or amework for arranging the time and resoure sources throughout the ‘considerations and pl ba ne eveles that should be defined are discussed below, esides this, the various plannin Planning Considerations tare ang a ings awe of en cat 4 software on time, Besides penis ai sine “tgement team. ‘The tean considers pl as an initial Planning Cycle e sie also fe NeW product functions must be specified estimation and scheduling. Softw: ing is a criti An iterative planning eyele is as follows, mii requzements must be 1 there a the stating of The requirement sa femens must he understond to create tov create «plan, however commitinents cannot be made ‘ade without a plan WARNING: XeroxdPhatbcopying htt i CRMINAL ot yori ih uy is ABLE acs ue fac8 LEGAL proceedings. Scanned with CamScanner1.19 stware Process M )ywitt Sof laturity, Process Reference Models. Created estimate the size of product, lan by break i ‘ down Structure (WBS). i the work into multiple elements known as Work Bre: Gather the resources. create a schedule. -preplanning cycle is as shown below, Initial Requi 3 y Negotiating Commi Y Requirement No. Decomposition[*——] Foimating |_, [Estimating Project | Product Size Resources 7 | wae Developing | Schedule Etc 18 Schedule | — Met or Not : | progimmer |_——-s[Beyeoring |___- uste ‘Months and Software Delivery Machine Time Compass ‘Actuals }——| (Database) Figure: Planning Cycle of Software Development GZ, Discuss in detail about various elements of a software plan. . Answer : ‘The elements of project plan are as follows, 1, Goals and objectives 2. Work Breakdown Structure (WBS) : 3. Estimates of Product Size 4. Estimates of Resources 5. Scheduling projects 1. Goals and Objectives nt phase, 1 is a negotiation period existing amon The goals and objectives of project are developed during requir ‘oftware engineers and users on how, (0 Work is to be done 7) To measure success : (ii) Needed time and resources are obtained. SPECTRUM ALLIN-ONE JOURNAL FOR ENGINEERING STUDENTS f \ 4 hk Scanned with CamScannerSOFTWARE PROC wail Green changes wil ivarialy NET As usr requirement changes it wit Stel the work prog design and mplenenation eM Ay virem itware engineering. TE stable requirements ete. Change in req as one of the continuous problem of goals of project plan are, a 1. The product must be implemented in st ‘ ; te sleted inorder to sure sor to enhance requirements all increments Each singe increment mu next subsequent ineremen knowledge. ro $3. in the requirements at each inerement prior Aesigning. : art of implem 4. hangesin equiements oeeurasa part of impleme tation then perform those changes in next succeeding increments, : UE changes are not encountered, then stop working, Perform requirement modification, revise the plan an start the designing process. 2 Work Breakdown Structure (WBS) For answer refer UnitIll, Q23, 3. Estimates of Product Size > _Thepproduct size estimate is considered as an quantitative code assessment needed for product elements like subsystems, ‘components and modules. The concept of contingency is applied to these estimates depending onthe previous project experience, 4. Estimates of Resources ‘The required resource estimates for each WBS element ‘re specified based on prior experience or inknown productivity factors. 5. Project Schedule A schedule for key tasks and deliverable item can be specified depending on project staffing and resource. 028. Write short notes on LOC and function points. Ansvier : Lines of Code (LOC) LOCis one ofthe simplified metric present amongll the other metres to assess project size. It estimates the project size by taking into account number of source instructions present, ‘ut it will not consider the header lines and commer adopted a technique of divi the modules are divided int the leaf node module size. Total size estimation isn after gaining the estimation of lowest level moda Function Point Metric ing the problem into module, Again to submodules tll it figures out that ichieved only les In the year 1983, Albrecht developed Function Point Dyetric I overcomed several drawbacks of LOC met, te > point metric is that it compute Wwe of software directly from the problem specitonnes yleteas incase of LOC, the size can be estimated only af, the product has been completely developed WARNING: xerovPnotcopyn BARRA GRIN hware is aso =p re pro Software me shows the 1 Function poi software product terms of the weight Unadjusted Funetion Point (UFP) manner. Different Parameters @ a) ity cy ca) HAPS RO LAL tae LEAL ~ the mumbe Function point is cal n point metric Is that sing ea behind Hi istint functiONs oF fea, based on ”overal featutes WOuld bj oduct wr ction is invoked it ready 2. Wh suiput data. For instance, cons tinto®em, When this book feature by provides its location along wi ut an ds ns outPUL ber of input and output which supports the sys in estimating the size of i din function point j ize is presente' ; ita Jin om ofthe five problem charactersiy, feulated in two WAYS, f ion point is esti unadjusted function points esti ‘nical complexity factor is estimated, ml zrhus calculation of Bu int met Inthe first step, the the second step tec ‘Unadjusted function point is expressed in the following UFP=(ND)*4+(NO)*5+(Na) *4+(NF)*10+(NT)*10, ‘The different parameters of UFP are as follows, Number of Inputs (NI) Data item input is provided by each user data. It is i 4. Actual performance of the project is tracked as the projet progress. This is shown in the dotted line. As scheduling is applied to complete project, the overall status of the project is specified to users. Project tracking for Projects can be done based on the following key points, {. Each checkpoint must be measurable and specific. 2. Adetailed plan must be created that allows the checkpoints to (i) Complete 50% of the module design, conduct reviews make corrections (ii) Complete 25% of test eases without erors. (iii) Complete 15% of test program without error, * 3._The project plan helps in determining the percentage ofthat is complete, Q31. List and explain the basic configuration Management functions, Answer: Basic Configuration Management Functions {In basic configuration management system initially a baseline is developed, after the initi ili successive set of increase (of a baseline) a new baseline in developed. mh penton gr saber a ‘Each baseline is then maintained within a database, ‘Thus, it ean be suid that a baseline isthe official rep ‘A baseline includes the approved changes and the ‘A baseline act asa source that helps the program ‘The main SCM tasks are, (Configuration control Gi) Change management : (iil) Revisions (iv). Versions ira at one place with all the changes that produced it story ofthe product and it holds the most current version. tested code which is fully protected, imersto ensure thatbeir task is performed consistently. eeoe (¥) Deltas (Wi) Conditional code _ WARNING: Nero ASCABIRS EWS HS CRIMINAL BRAVA iy Is LIABLE 10 faée LEGAL 4 ‘ f f Scanned with CamScannerProcess Mati ; ya sonore falurily, Procens Reference Modols 1.23 os con Control, o Fconfiguration ean revolves ie wsk orconfiguraton ean rots Uirouphout an official eapy of code, " earest way to protect euch system revision into ke 4 Teese od p wystem revision is W keep a separate official copy at ever revision level atti baseline paetine on validation [7] ¥ Authorize design use >| change 7 ("| changes y Change implementation y Approve ‘Change change | . validation Figure (i Overview of Change Management. ‘This would take a let of storage space, one of the issue is with code division. When more than one group work on different copies of the same or similar versions of common code, sometimes different » changes are made to correct the same problems. The final cost ofthis can be understood by considering system drivers. 44 Exsimple, one programmer may requir a copy of the system contol program fo unit es 4+ Altough the contol program may ndt completed the functions tis programmers required may be unstable : 4 Henoe itis helpful to provide a control program copy with this funeton rather than write he developers time. Revisions 4 — Revisions is one of the significant task of configuration management © Imthis large systems, some program such as control system, provides essential function for all others. % Ifthe component's module have been combined into testable unit, then it can be tested with the latest control program level These previous tests can be re-run o find the problem source, if fuer problem are found. © 1¢an early diver is produced again, using the latest version! ‘of the control program modules, some of these module will likely be changed, so the previous tests are not exactly produced © One ofthe key feature isto keep track of ll the changes that have been made to module and test cases. [Always there is only one latest official version and all previous versions are identified and maintained, such that these copies can be used in tracing problem. + Continuous process of revision, integration and testis nothing but the development. Derivations One of the powerful software testing feature can be used to find what has chang Example: Ifa program works on day the and notin the next day, then the fist step is 0 find what ars the changes. {ALL-IN-ONE:JOURNAL FORIENGINEERING STUDENTS 301. 4 be] Scanned with CamScanner SPECTRUM MANEeens es 2 ==— --- — AGEMENT [JNTU. 1.24 SOFTWARE PROCESS AND PROJECT MA\ f NFR 3 Level 226 Test A Level 227 | Rerun test A . Figure (i: Derivations ‘S _ Desvation dat would show that testa was un on control program level 116 andthe rerun was attempted on lve i S _ Changes x and y can be identified, "Data then might be maintained in such derivation record is, 1. Revision level of every module. 2 Revision level of the tools used to assemble compile link, load and execute the program and tests. . 3. The test cases used and the test information employed. . 4 Thefiles used, * Software and hardware stem configuration along with peripherals, features, options, allocations, assignment and hardware change levels | & The operational steps. : : % _Arscord of jb steams being executed when there is no stand along test Versions won _ fam chones = en there can be other potential issues. More different tacks can be implerients by the same module Example ¥ ea ins figure shows thatthe standard memory management would be used be 7 mode switch would hold the larger ‘memory size, below $12 K and the ther ui ‘a % The different programs would have the differen t designation, management modules. Juke MEMS and MEML for the standard and large memory MEM >si2 on 208] [so Figure i: Versions 4 Deltas + Execution of deltas is another test of configuration management. (On one handy the versions solves the problem of different functional requiement forthe ce it hhand creates multiple copies of the same code. “odule but on the other % —Tocovercome this problem of multiple copies of same code use case deltas. WARNING: xeric oe CRIMINAL oc Ano oO ABLE ( ee aN Scanned with CamScanner Proceedings.1.25 MEM MEM Lange memory Standard memory Figure (vl: Deltas 2 The above figure illustrates that saving the base module like MEM, When the changes are requires on MEM then the changes can be made directly, with interface will the delta code. g_ Thechanges are only made to the MEML code and the MEM code islet unchanged. ceattional Code Conditional program construction is used to handle the small changes between modules. ‘¢ Consider an example, along with the changes required to make it into ME} Billing in NY cr P: Program a —— Billing Billing Billing program. Program program F | | ¥ NY cr ] PA | Newyork Connecticut Pennsylvania Figure (vl: Conditional Code Scenario ling program which include different functions depending on the requirement of a state |. The above example shows the | onsales tax. © The program includes different sales tan versions, but they would not be included i final system unless called for a system | installation. * This requirement of conditional code is fulfilled by using system generation options. % — Based on the conditional code, one of the many available optional modules is selected depending on the specific state ‘where the program was used. * One usage of conditions, case the code control as there is only one official copy ifevery module. * Another advantage of the conditional code is that providing one complete copy of the complete program, 5 All the code woitld be available, and users have to select the specific combination required for installation. Once conditional code is ready, this requires that all the program options and features be provided to the end users, but it ¥8 difficult to control unauthorized distribution and use. SPECTRUM ALLIN-ONE JOURNAL FOR ENGINEERING STUDENTS. 35\,0:55, OMA ba \ , Scanned with CamScannerse Q32. Explain in detail about SQA. Answer : ‘Software Quality Assurance (SQA) ve Quality is used to determine ifthe software mects phase, Software requirements that were specified during design sand nal assurance fused to monitor the sofware proses methods fr ensuring its quay. By using ais of Qt management system, SQM improves the sofivare qual SQA is very mach related to quality assurance in ode! manufcturing, There are some nticeabedfeences beweet software produet anda manfictued product Amanufictre product is something that is physical entity which can be seen, whereas software product is invisible and temporary. Because of this nature functions, benefits and costs of software are not ‘measured easily. When a manufactured produet is ready for shipping Its said tobe a complet, finished product, Whereas software produc sintangible and can never be finished, Testing the quality ofa software is expensive because it include cost of detecting and correcting bugs, cost of developing and executing test cases Software quality assurance is required because the computers fail to work as per users commands. Hence there is d need to develop a bug free code. This process is known as debugging where bugs are found and corrected. Some bugs can be easily found whereas other need special testing methods. Debugging provides tools that detect the errors and corrects them. Following are some types of errors that may be encountered during debugging, 1, Logie Error ‘This typeof err occurs when the eode, doesnot function acsordingly inspite of being syntactically corect. The code can execute without performing any itelevant peraton but produces inelevant result, This type of Teen dete by testing the code and analysing 1 Out come, Run-time Error its desired functionality For instance, accessing an object whieh has not been declared Syntax Error This type oferorarises ifthe 5 ses ifthe code i incor Heine noaedhowerdarmc ee es ETDS canbe detected easily ni ee 'Y-Without the need ot nated by perfor in wo 8PES Of Quality Seenariocbased assurance testing, There are t ‘esting error-based testing and then by per 2 cases: differ 13 a3. error @ WARNING: xerouPnatsesgnyra { prograi forms of ta interaction bugs. Onl However, it detects high Answer t Software Standard objectact and value. A software standard specifies the way a which software is developed and maintained. Software standais. "are defined based on languages, coding conventions, comments, people product and Supportive environment, enabling, int system testing, Reasons for Defining Software Standards follows, ny, \ i ting, error based TES iB pis hac, of earn inerest Then thes hin iment method oft comp er f hours have tobe tested ois, ete. The test mUSt cheek wy jes these values. Ifthe values aren yorted. HO hers, code hard i ern must be FP th can be used for integratn, technique Errore ee the objects that process mess, forming tes jnased Testing : sting is also known as usage base, brad acim by the user by identiyin, tasks, Then the tasks are performed and ks are tested. This type of testing may ay jot ly a single-form of test i8 performs tems. It does not detect all forms of subnet ly system interaction Scenario- THE DEFINED PROCESS st the reasons, benefits and examples g software standards. Model Papers, cay Astandard define rules to assess the size, content, quali Teporting etc, software standards are defined based ca tools. It is essential for developing commea tegration or performing (THe teasons for defining software standatds ares Tey enables large software organization to determining sighificn, °f Uniform procedures that provides seigamount of training and procedure th! Provide’ signifi fra development, 22 #MOunt of training and procedue ‘ommon codin, ‘conventions an ting "evie ee cotventons and commen "the project data “Hon Of desighing and coding oe wintain ability oF developed produ mming efficient Scanned with CamScanner\ i ss Maturit wet some Process Maturity, Process Reference Models 1.27 seasons (Priority needs with in an organization software standards enables a software manager to | (i) Projects status _Sagoessfil software product and process. It specifies ost 2 Myon which the desired software can be created. The SEE semble language of IBM ie. IBM's 08.360 allows ooiand ee development of 13 Taboratories and 6 counted, ee he use of standard high-level language like PSL see ec product development and support. Beside this, one no assist the software managers, To analyze the key problems and fin thet effective solutions depend on setae and procedures it also helps in analyzing the suec a ile ofa project. tvample of Some Most Commonly Used Standards ‘The software standards which are defined by IBM's sole ystem Division (FSD) are listed below, gpstematic Design Practices Logical Expression 1h describes a mathematical-based technique based on reasoning and expression. It can be applied in all phase of software development Program Expression Itspecifies data, program structure and control to record the program design. i 3. Program Design If describes the stepwise refinement process to record the structure of program design. 4. Program Design Verification It defines function theoretic technique to prove correctness of a structured program. System Design Practices Itdescribes the process depending on state machines. It allows creation of specification and documentation of software stem. Real-time Design It specifies stage-wise designing of asynchronous sofware process inorder to identify concurrent operations Besides this, various code management standards are excited by IBM FP inorder 1 cover programming AnewiEe ‘ofingctarlurd and conventions, software support hierarchic brogram control library and high order programming ts age Some of the standard and conventions of IBM are 08 Standard, oprgrng system sonar, program suppor OD 34, Discuss in detail about establishing sofwa standards. ' Answer : Establishing Software Standard avare standards an organization mas To establish sot consider the following. specrRuM ALLAN-ONE JOURNAL FOR ENGINEERING STUDENTS, 7. Gii) Standard enforcement mean. “The standards are established by examining the standards and procedural needs of the organization, Software are defined based on the following three categories, 1. Managing and planning procedures and standards. 4+ Management configuration 4 Costing and estimating 4 Software quality assurance. 2, Developing process standards and methods 4 Specifying requirements Design’ 4 Documentation & Coding 4 Testing and integration 4 _ Review, walkthrough and unspection. 3. Tools and Process Standard 4 Naming the-product 4 cost and size measures 4 Counting and recording defects 4 Editing and code entry tools 4 Documentation system . 4 Languages ‘Library system. Standard Development Process ‘The steps to develop a standard areas follows, (i) A standard strategy must be developed with priorities and prior work recognization. (ii) Review, distributed and maintain the standard strategy (iii) Top-priority standard can be created by choosing an individualsmall working group. (iv) The defined standard must be developed based on (a) Prior work that is available (b) Areas that are applicable (©) _ Defining introduction strategy and (@) Purpose of enforcement plane, (v) Distribute and review the drafts standards (vi) Revise the standards by incorporating the comments of | review and re-view it if changes are encountered (vii) _ Implement the standard based on test environment (vii) Review and revise the standards after the test (ix)_Implement the standard across specified area and enforce it (x) Standards are to be evaluated based on actual price, Scanned with CamScanner” ROJEGT MANAGEMENT [UNTU-Hy pe, 1 12s SOFTWARE PROCESS AND P! of toh Mt Mants are be established hy infil smal UP fechnical experts. New standards can be established by adopting it from, nee . another onganiz: S ofusers (or) by enforcing st As software standart Purpose. Itspecities formal review process that enables reviews © create a plan, design implementation approach and adopt enforcement provisions, 2 Maintaining Standards coo, Standands can be maintained by either individual oF group. The responsibilities of individual/group to maintain standards are as follows, () Standard implementation problem should not be considered (ii) Guidance and advises on standards must be considered (ii) Standard basetineand control change must be maintained (iv) Review the standards periodically inorder to ensure effoctiveness. Q35._ List the objectives and principles of inspection. Answer : Model Paper 238) Inspection . Inspection is a process of verifying the work/product / process technically and provides assessment of the product and" specify the desired improvements. It is basically done prior to higH level designing, implementation and test. Inspection Objectives ‘The inspection objectives are listed below, 1. It focuses on identifying error at early stage of development cycle. * Ttensures that the technical parties to agree of work on time. 3: It Verifies that checks whether the predefined criteria is met or not. 4, It focuses on completing the technical task on time. 5, It specifies the product data and inspection process. Besides this, it provides the below benefits, Itensures thatthe related working team are familiar with the product It allows development of effective technical team sists utilization of best talent in organization Gi) Ita Itenables the developing participants to becomea reviewer, ) Basic Inspection Principles “The basic inspection principles areas follows, Inspeetions are considered as a structured process thay includes system checklists and specified roles of. Tralee defines means t0 implement provess within an organiza, engineering is done to develop at gene Inspection i Senetic « standards based on each inspection type, Reeds. The generic checklist must inci, plan, preparation, conduct, 28 Well 2s 5 A. Inspections performed to preparea ist of. 3 TMjrance). So.as to identity the eoncems ap Frio begging of inspections. 4, inspection helps in determining the probes. rarmepections conduted with minimum ¢ inspection is basically handled by group os 5 + Feaple for people who does technical work. 7, to identify the technical problems. 6 Inspection process and its data is maintzingy database to monitor its effectiveness and to; quality of product. Software inspections are done 0 as to imp; quality of software process as well as its productivi type of review done by the software programmer ino. improve the software quality fixing the encountered er: to software development. . aia Q36. Write about various types of software tesin, strategi Answer = Model Paper oss ‘Testing Strategy Testing strategy is used to detect bugs in a prod system by considering all the constraints. There are many <=: strategies in object oriented approach. Following are t important strategies. 1. White Box Testing 2. Black Box Testing 3. Top-Down Testing 4, Bottom-up Testing. 1. White Box Testing White’ box testing deals with the internal losie «=! structure, of the program code. It is also known as glass structural or open-box testing. In glass-box testing, test 8S are derived based on the knowledge of software structure 28 implementation. The tester can analyze the code and ms of the knowledge abouit the structure to derive test dat. Wh box tests ean analyze data flow, conirol flow, information exception and errot handling techniques. These techniques, used to test the behavior of software. ___A tester should have explicit knowledge a0"! internal working of the system being tested. Branch (°° and path testing are the techniques used in white box tie, Ifthe implementation details are changed, the tests shoud? be modified. The different methods used to perform white testing are as follows, : ie participants. WARNING: xerouPnGiBEGAMFSr FR LAB SIOURSER TORE SYNE BUNGE By is LABLE 1 18S LEGAL proceedings Scanned with CamScanner ”rete econs May, unt Os patvatice me provi oek wht gt seen atute fenced a Tenet one. Nomen fine xox a1 (Oot arate ato avalle Ueer-provided parameters or provedire available uy Planet wserstetione te ayaa Detined ew coder ate available, w go _Brasetetston Covere ‘eats are performed ta chock whether enh taneh ofa devision is executed atleast once, Decisions require two {atuce in standant Rootean decision testing, Mut in ewve ‘afoompourt or nested deelsions, the numberof Hoolenn decision values can be greater than two, ay Condition Covernpe ‘ests are performed to check whether a acceptsall the nevessary outputs Italso checks whether the entry points to the procedure cof low is invoked at least once, tn ease of compound and nested loops, condition testing is provided with tnultiple test values. The other exceptional routines and crror handlers are also invoked! while testing the eniry pints. 2, Black Box Testing Black box testing is also known as Functional testing ceBehavioural testing. It is an effective and efficient approach tse fo concentrate on the inputs, outputs and principle af asoftware system module. In a block-box test fa software is based on system specifications rather than on code. This, the system is assumed fo be “black box’ whose tehavior an only be determined by studying its inputs, outputs and functional requirements of the software. The tests ean be chserved from the program codes or component specifications. Black box testing is helpful to software engineers in crdet to understand the set of input conditions, which d ven functional requirements ofa programm. Black-box (esting ‘suseful to identify errors such as, (Inaccurate functions wo (iii) Performance errors Interface errors (iv) Data structure errors (¥) Initialization and termination errors. Black Box testing is performed after studying the white ‘oxtestng that prints to the control of the system. The following are the questions that black box testing (What wil be the eapacity and the speed of system data? (iy What are the classes that results in good test enses? “rovenn Hoforonces Mitel SPECTRUM ALLIN-ONE JOURNAL FOR ENGINEERING STUDENTS. 1,29 eee mn Tiected by specie combination of dain? (Iv) How ate ayatem perfon il behavior tested? (9) How ate the Himitations of dats € ed? (v}) Whether all the input parameter are accessible by the ayaten’? Top-Down Testing {iyp- down texting isn method Is which the testing begins fom top or main control module of main pro low inthe contr hierarchy. assumes tha the prim ‘ofthe appliention oF object Interactions andl syst : early stages of y provluct beesuse and event-driven anotons thereby providing lve testing, H supports user interfis ier interface tests the interface fy the tuition through wereens, requirements, 1 hive on advantage tha see the look nnd feel of the application in the early stages of inplementation, tn addition to the above, top down testing is tlio uveli for testing subsystems and system integration. p Testing Up Testing isan alternative to top-down testing. 1 initially begins by considering the units at the J proceed upwards till the main unit is reached. ofsystemare tested integrated "This techni lowest level a In this testing, iu tested for Bottom-up (esting tests the class and methods that ‘all other methods, Then the classes and methods of the next upper level that call the lower level classes are tested. Then {tegration of two bottom layers are tested. This process iues until the complete program has been tested. G37. Explain the Booch Methodology Is detail. Answer ¢ Booch Methodology Booch methodology is used to design systems using. “object-oriented method. It uses the Analysis and Design phases of 00 method, It defines many symbols to describe the design decision, However, many symbols will be left unused. The class and object diagrams are used in the Analysis phase, ARer this, the code is generated by using design symbols, Booch Methodology contains many diagrams like class diagrams, object diagrams, state transition diagrams, module diagrams, Process diagrams and interaction diagrams. It describes two methouls-macro development process and micro development process. ‘Macro Development Process, This process manages the technological areas ina system. takes place trom weeks to months. It maintains the traditional Analysis and Design phases and acts as a framework for micro process for controlling its activities Macro development process, is carried out in the followin Scanned with CamScanner1.30 lization step, the major requirements for t forthe system are discovered. Then a prototype and goals to achieve the project is developed, 2 Analysis and Development of Model In this step, class and object diagrams are used. Class diagrams describe the behavior of objects by means of roles and responsibilities. Object diagrams deseribe the behavior of system by means of scenarios. It also uses interaction diagrams to describe the behavior of by means of scenarios, 3. Design the System Architecture In this step, class, object, module and process diagrams are used, Class diagrams are used to identify the class and their relationships. Object diagram is used to identify the methods that demonstrate the way of collaborating objects. Module diagram is used to locate‘the place of classes and objects. Process diagram is used to allocate Processes to processors. It also identifies the schedules for processes on similar processor. 4. Implementatioa In this step, the system is refined by performing many iterations. It generates software such that each software is an enhancement of the previous software. 5. Maintenance. In this step, changes must be done on location basis for ‘adding additional requirements and removing the bugs, Micro Development Process ‘This process manages all the micro processes involved in the development of a system. A’micro process gives the déscription of all the activitjes by means of an individual or group of developers. Every macro development process has its micro development processes. ‘The steps involved in carrying out a micro development process are as follows, 1, _- Finding the classes and objects. 2. Finding the semantics of class and object. Finding the relationships between classes and object. 3. 4, Finding the interfaces and implementation for classes and objec Gas. Discuss about the UA Proposed Repository. Answer! .ce where the previously defined data cepjeets, patterns, frameworks and user interfaces are sored Peseta comprises of the best practices of already Supt

You might also like

• 1651 - GCS200888 - Vo Nguyen Duy Nam - Assignment 2 PDF

  

  No ratings yet

  1651 - GCS200888 - Vo Nguyen Duy Nam - Assignment 2 PDF

  25 pages
• SPPM - Full Notes

  

  No ratings yet

  SPPM - Full Notes

  80 pages
• Wireless & Cellular Communication-18EC81: Prof - Priyanka L JCET Hubli ECE

  

  100% (1)

  Wireless & Cellular Communication-18EC81: Prof - Priyanka L JCET Hubli ECE

  49 pages
• Chapter 15 - Exercises - Reduced Instruction Set Computers

  

  No ratings yet

  Chapter 15 - Exercises - Reduced Instruction Set Computers

  6 pages
• Syllabus

  

  No ratings yet

  Syllabus

  136 pages
• Ad3311 - Ai Lab Manual

  

  No ratings yet

  Ad3311 - Ai Lab Manual

  37 pages
• Entity-Relationship (ER) Model - PPT (Compatibility Mode) (Repaired)

  

  No ratings yet

  Entity-Relationship (ER) Model - PPT (Compatibility Mode) (Repaired)

  55 pages
• Intern 122 Report

  

  No ratings yet

  Intern 122 Report

  73 pages
• 2021 Lecture08 FirstOrderLogic PDF

  

  No ratings yet

  2021 Lecture08 FirstOrderLogic PDF

  97 pages
• Atc Module 3 Notes

  

  No ratings yet

  Atc Module 3 Notes

  38 pages
• C21 - Me - Iv Sem

  

  No ratings yet

  C21 - Me - Iv Sem

  101 pages
• Electrical and Electronics Engineering S7 & S8

  

  No ratings yet

  Electrical and Electronics Engineering S7 & S8

  362 pages
• Start Here Guide: Release v2019.4

  

  No ratings yet

  Start Here Guide: Release v2019.4

  68 pages
• Ece - VR20 29082022 2

  

  No ratings yet

  Ece - VR20 29082022 2

  125 pages
• Semester-IV: Introduction To Software Engineering Course Code: 4340702

  

  0% (1)

  Semester-IV: Introduction To Software Engineering Course Code: 4340702

  9 pages
• JNTU Kakinada - M.Tech - EMBEDDED REAL TIME OPERATING SYSTEMS

  

  No ratings yet

  JNTU Kakinada - M.Tech - EMBEDDED REAL TIME OPERATING SYSTEMS

  7 pages
• CD Unit 5 PDF

  

  100% (1)

  CD Unit 5 PDF

  16 pages
• Chapter 4 Operators

  

  No ratings yet

  Chapter 4 Operators

  25 pages
• Programs, Files Data Structures

  

  100% (1)

  Programs, Files Data Structures

  13 pages
• DDM Lab Main - 1

  

  No ratings yet

  DDM Lab Main - 1

  74 pages
• Electrical Measurement Lab by SK Final

  

  No ratings yet

  Electrical Measurement Lab by SK Final

  40 pages
• R18 Ece Syllabus - Bec

  

  No ratings yet

  R18 Ece Syllabus - Bec

  211 pages
• Intermediate Code Generation-17-19

  

  No ratings yet

  Intermediate Code Generation-17-19

  90 pages
• Pervasive Web Application Architecture

  

  0% (1)

  Pervasive Web Application Architecture

  20 pages
• Final Year Report Submitted

  

  No ratings yet

  Final Year Report Submitted

  61 pages
• C Programming Language Sample Question Paper

  

  No ratings yet

  C Programming Language Sample Question Paper

  5 pages
• IV-I CSE SPPM Full Notes

  

  No ratings yet

  IV-I CSE SPPM Full Notes

  137 pages
• Module 3 Merged

  

  No ratings yet

  Module 3 Merged

  80 pages
• Network Management Mod2

  

  No ratings yet

  Network Management Mod2

  14 pages
• COA Notes

  

  No ratings yet

  COA Notes

  36 pages
• B e Cse PDF

  

  No ratings yet

  B e Cse PDF

  406 pages
• Cse CD QB R18

  

  No ratings yet

  Cse CD QB R18

  30 pages
• Cse 3-2 Cs & Syllabus - Ug - r20

  

  No ratings yet

  Cse 3-2 Cs & Syllabus - Ug - r20

  93 pages
• L3-Assembly Language Fundamentals

  

  No ratings yet

  L3-Assembly Language Fundamentals

  54 pages
• DWM Lab Manual 3yr 1

  

  No ratings yet

  DWM Lab Manual 3yr 1

  68 pages
• Unit 3 - Computer Graphics & Multimedia - WWW - Rgpvnotes.in

  

  No ratings yet

  Unit 3 - Computer Graphics & Multimedia - WWW - Rgpvnotes.in

  30 pages
• UNIT 7 - S - P Key Distribution

  

  No ratings yet

  UNIT 7 - S - P Key Distribution

  36 pages
• Embedded Systems Unit 2

  

  No ratings yet

  Embedded Systems Unit 2

  78 pages
• Security in Computing - Chapter 2 Notes

  

  100% (1)

  Security in Computing - Chapter 2 Notes

  14 pages
• Lab Manual Cs6461 - Object Oriented Programming Lab: Valliammai Engineering College SRM Nagar, Kattankulathur

  

  No ratings yet

  Lab Manual Cs6461 - Object Oriented Programming Lab: Valliammai Engineering College SRM Nagar, Kattankulathur

  30 pages
• Ppsuc Manual r20

  

  No ratings yet

  Ppsuc Manual r20

  98 pages
• Buratutosd 1123 BSIT

  

  100% (1)

  Buratutosd 1123 BSIT

  40 pages
• 16CS517-Formal Languages and Automata Theory

  

  No ratings yet

  16CS517-Formal Languages and Automata Theory

  8 pages
• TLRF 2m PDF

  

  No ratings yet

  TLRF 2m PDF

  25 pages
• Web Question Bank

  

  No ratings yet

  Web Question Bank

  6 pages
• GlobalLogic Sample Programming Placement Paper Level1

  

  No ratings yet

  GlobalLogic Sample Programming Placement Paper Level1

  20 pages
• Tybsc-It Sem5 Ai Apr19

  

  No ratings yet

  Tybsc-It Sem5 Ai Apr19

  2 pages
• Chapter 3 - Solving Problems by Searching Concise1

  

  No ratings yet

  Chapter 3 - Solving Problems by Searching Concise1

  64 pages
• CS3391 OOPS UNIT 5 NOTES EduEngg

  

  No ratings yet

  CS3391 OOPS UNIT 5 NOTES EduEngg

  34 pages
• Instruction Cycle in Computer System Architecture - CSE

  

  No ratings yet

  Instruction Cycle in Computer System Architecture - CSE

  4 pages
• Unix Network Programming and Simulation Lab File

  

  0% (1)

  Unix Network Programming and Simulation Lab File

  42 pages
• Chapter 11 - Mass Storage Management

  

  No ratings yet

  Chapter 11 - Mass Storage Management

  19 pages
• Material For CAT 1

  

  100% (1)

  Material For CAT 1

  22 pages
• Lecture 0 INT306

  

  No ratings yet

  Lecture 0 INT306

  38 pages
• MAD Report

  

  No ratings yet

  MAD Report

  19 pages
• Daa Notes Unit 4

  

  No ratings yet

  Daa Notes Unit 4

  14 pages
• Software Design and Architecture JUNE-2021 Sem - II SET-5 (T.Y.B.tech COMP)

  

  No ratings yet

  Software Design and Architecture JUNE-2021 Sem - II SET-5 (T.Y.B.tech COMP)

  6 pages
• Big Data Nit067

  

  No ratings yet

  Big Data Nit067

  1 page
• CodeCompass - An Open Software Comprehension Framework For Industrial Usage

  

  No ratings yet

  CodeCompass - An Open Software Comprehension Framework For Industrial Usage

  9 pages
• A Survey On Security Issues in Service Delivery Models of Cloud Computing

  

  No ratings yet

  A Survey On Security Issues in Service Delivery Models of Cloud Computing

  11 pages