Scribd Logo
Upload

Welcome to Scribd!

  • SPPM

    Uploaded by

    Kalyan Reddy
    19 views180 pages

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document

    Copyright:

    © All Rights Reserved
    Download as PDF or read online from Scribd
    Flag for inappropriate content
    Download as pdf
    19 views180 pages

    SPPM

    Uploaded by

    Kalyan Reddy

    Copyright:

    © All Rights Reserved
    Download as PDF or read online from Scribd
    Flag for inappropriate content
    Download as pdf
    of 180
    SHORT QUESTIONS Qt. What ls a Process Group? Answer t For answer refer Unit-1, Q2 7 a. Sy four esi nepecton ps Answer . For answer refer Unit, Q4. ; EA a. cna cbc ID Answer = : ‘moor a, For answer refer Unit-1, Q7. aL Wat are the erent situations of oftware requirements developmentin terms of aks. of participants? “te Answer = : For answer refer Unit-1, QU. : ot ESSAY QUESTIONS Oe. Describe the principles of software process change and TSP. Answer : (Cetion- 2416), A Des-t99 F| For answer refer Unit-I, Q15. Q6. Discuss in brief about various considerations to implement assessments. Answer { For answer refer Unit, Q21. *Q7. List and explain the basic configuration management functions. Answer : Impo For answer refer Unit-I, Q31. dus (8; What is data gathering and analysis? List the principles and objectives of data gathering, Import ung Answer : pra an For answer refer Unit-l, Q43. Q8. Write about Defect Prevention. Discuss the principles of software defect prevention. Answer : Important Que For answer refer Unit-I, Q48. Q10. Explain the Capability Maturity Models in detail. ‘Answer : (Important Question | Oct.Nov. 20 For answer refer Unit-I, Q53. Q11. Discuss about software process assessment. And also discuss about CMM. Answer : * (important Question | Dec-19(R1. For answer refer Unit-I, Q56. Ana SPECTRUM ALL-IN-ONE JOURNAL FOR ENGINEERING STUDENTS ais q ¥2 SOFTWARE PROCESS AND PROJECT MANAGEMENT [JNTU-HYDERABAD] ieee ‘UNIT - IT : Software Project Management Renaissance, Life-Cycle Phases and Process Artifacts SHORT QUESTIONS Q1, What the phases of the life-cycle process? Explain. Answer : (NowJDec.-17(R13), Q1(e) | Nov/Dec.-17(R13), Cf) | March-17(R13), Ci(e) | Nov/Dec.-16(R13), C(e}) For answer refer Unit-Il, Q9. Q2. What is meant by late risk resolution? Answer For answer refer Unit-U, QI. Q3. What are the major components of software cost? Why? = (NovsDec.-17(R13), C1(a) | March-17(R13), 1(s)) os (March-17(R13), C4) | NowsDee. AGRA), 2H) For answer refer UnitIl, Q4. Q4. Define late design breakage. a (umportant Question | Nov/Dec AG(R13}, Qa) For answer refer Unit-ll, Q3. Q5. What are the top five principles of a modem process? , ate (important Question | March-17(R13), Q1(qd)) For answer refer Unit-I1, Q8. ESSAY QUESTIONS 6, Briefly discuss about engineering stages. Answer! (Dec. 19716), O5 | NowdDee. 71819), 06 | March-¢7(R3), C7) | NowtDee-1{13), C8 For answer refer Unit-II, Q48. : = : ; Q7. Describe transitioning to an iterative process. are (OctiMov.-24(R16), G2 | March-17(R13}, O5(0)) For answer refer Unit-II, Q47. Q8. What are the principles of modem software management? ee (NovdDec.-17(R13), 05 | March-17(R13), QA) For answer refer Unit-II, Q45. foe 80 8 Q9: Explain the principles of conventional software engineering. Auswer : (ec.-19(R16), O52) | Now/Dec.-16(R13), O5()) For answer refer Unit-II, Q44. aidebiers Qo. Oe ees penetens Gat hopes eras software quality? Explain them: Answer : (Norton ATR} 4 | NowDec-83, 8) [2] Foi answer refer Unit-Il, Q42. BUT WARNING: xerauphoticopyiig ofthis book & GRWANAL‘al” Ril tbr Gul i LIABLE to fate LEGAL proceedings. WH) FAQ's and [Q's Q11._ Explain about improving software process and improving term effectiveness._-——~ 4 Answer: (Bec -A9(RI8}, 26 | Maren-17¢R5, ~ Y SA4a) For answer refer Unit-II, Q38. Q12. What are the three levels of software process and thelr attributes? Explain. Amewer : For answer refer Unit-I1, Q33. my Q13. Explain in detail about test artifacts. ~ Anewer! portant Guteton |, For answer refer Unit-II, Q57- “Her, Q14. Explain pragmatic artifacts of software project management. Answer 1 For answer refer Unit-Il, Q62. ‘mPoran Oo, UNIT - Il : Workflows and Checkpoints of Process, SHORT QUESTIONS Q1. Witte brief notes on major milestones in software process. Answer + (Doc--49(R16), AN | Novidee.-A71R13), 4H) For answer refer Unit-IIl, Q6. Q2. Define product release milestone. Aaa _ important Question | Marche For answer refer Unit-Ill, Q3. ha Q3. Who are stakeholders? List them. a (Gmportant Question | March.7¢9), For answer refer Unit-IIl, Q4. i] Q4. What is WBS? Answer : (important Question | Now Dec.-16t yy For answer refer Unit-IIl, Q7. Q5. Discuss about initial operational capability milestone. Answer : (important Question | NovDec.-17(Rt3), 044) For answer refer Unit-IIl, Q10. ESSAY.QUESTIONS Q6. Discuss life cycle planning balance. Anewer : (Cetmov.20(R16), a8(e)| March-¢7i3), a0 fel 2 mes For answer refer Unit-III, Q29. SPECTRUM ALLIH-ONE JOURNAL FOR ENGINEERING STUDENTS e Fe SOFTWARE PROCESS AND PROJECT MANAGEMENT [JNTU-HYDERABAD] SS Q7,_ Describe the conventional WBS Issues and planning guidelines. Anker ir (Dec.-19(R16), 26 | Nov/Dec.-16(R13), 29(a)) For answer refer Unitelll, Q27, “An evolutionary work breakdown structure should organize the planning elements around the process framework rather than product framework”. Substantiate this statement. Auewer = {OctuNov.20(R16), Q3| Nov/Dec.-16{R13), 28(a)) 2 For answer refer Unit-lll, Q25, Q9. What are default agendas for the life-cycle architecture milestone? Answer : © (important Question | March-17(R13), Q8(a)) For answer refer Unit-Ill, Q19, 10. Explain the conventional WBS issues and evolution of planning fidelity in the WBS over the life cycle. Answer: (important Question | Nov/Dec.-17(R13), Q8) For answer refer Unit, Q6.| '” “Qit. Atypical project would have six-iteration profiles. Discuss them. i Answer t 2 (important Question | Oct/Nov.-20(R16), Q8(b)), For answer refer Unit-IIl, Q30. 12, Summarize the differences in emphasis between engineering and production stages. Answer : (important Question | Oct/Nov.-20(R16), Q7) For answer refer Unit-IIl, Q31. 13, Explain about the iteration planning process.and pragmatic planning. Auewera (Important Question | Dec.19(R16), 7) For answer refer Unit-I, Q32! ( UNIT - IV : Project Organization, Project Control and Process Instrumentation ) SHORT QUESTIONS 1. Write brief notes on metrics automation. 1. ‘auewitx (0ee.49(R16), a(t) | Now/Ove-17R19), 0) | For answer refer Unit 1V, 08. : = Q2. What is roundtrip engineering? Answer : (Nov.Dee.17(R13), Q1(4) | March-17(R13), Q4(c)) 2 For answer refer Unit-IV, Q6. WARNING: Xerox/Photocopying of this book is a CRIMINAL act, Anyone found guily is LIABLE to face LEGAL proceedings. ? 93a viper Write olution of of Answer t (important For answer refer Unit-lV, Q2. Q4, What are the basic parameters of an earned value system? a Answer t (important Queston | Ney, Dae ; My For answer refer Unit-IV, Q4- ‘ Q5. Define rework and adaptability. ey Im a he Answer t . {Important Question Mech For answer refer Unit-IV, Q10. tray, ESSAY QUESTIONS be ‘ % Q6. What are the seven core metrics? Explain. ‘Answer + (GetiNow-24(R6), G4) | NviDes-A7R43}, G10 | Marh-47ER49), 10() | NovIDee-A6RRI, at 5 hati) For answer refer Unit-1V, Q29. 7. What are the four component teams in a default project organization and their responsibility? Answer : (NovsDee-6(3), OH) | March-171R9), an For answer refer Unit-IV, QU ae ‘Answer : Important oue | For answer refer Unit-IV, Q14. : Q9, What are the software project quality indicators? Explain them. : | Amsyers {important Question | De. ty ‘ For answer refer Unit-IV, Q32. 8 Q10. What is a seven core metrics? Discuss about pragmatic software metrics. | rr e {important Queston Dec. : % For answer refer Unit-IV, Q36. Qi1. Explain the significance of Software Project ControtPanel (SPCP) in metrics automation, Answer: : Important na | For answer refer Unit-1V, Q40. | (unin -v: copps-R Case Study and Future Software Project Management Pract) | SHORT QUESTIONS Q1. Write a brief note on 80 : 20 principles. Answer + Important Quin For answer refer Unit-V, QI ri Q2. Whatis meant by early risk resolution? Answer : (Important Question | Dec.-19(R16) atl For answer refer Unit-V, Q3. ‘SPECTRUM ALL-IN-ONE JOURNAL FOR ENGINEERING STUDENTS: or9X * F6T SOFTWARE PROCESS AND PROJECT MANAGEMENT [JNTU-HYDERABAD} eS ees Q3. Explain about. evolutionary requirements. Answer! (important Question | Dec.-19(R16), 01()) ~For answer refer Unit-V, Q4, ’ ——ooOoO eee Q4, , List CSCI. Answer t ‘ Important Question For answer refer Unit-V, Q6, ESSAY QUESTIONS Q5. How was the project organized in CCPDS-R project? : Answer Important Question For answer refer Unit-V, Q10. Q6. Elaborate on CCPDS-R process along with macro process, milestones and schedule. Answer i+ {important Question | Oct/Nov.-20(R'16), Q5) For answer refer Unit-V, Q13, Q7. ‘There are two approaches to manage People In CCPDS-R’. Discuss them briefly. Answer ¢ 7 Important Question For answer refer Unit-V, Q20. 8, What are the software management best practices? Explain them. Answer (important Question | Dec.-19(R16), Q10) For answer refer Unit-V, Q25. 7 a 9. Discuss about next generation software economics. Answer = (important Question | Dec.-19(R16), Qt) For answer refer Unit-V, Q26. + 10. Explain culture shifts for modern process transitions. ‘Answer + (important Question | NoviDée.-16(R13), Q10(b)) For answer refer Unit-V, Q28. WARNING: Xerox/Photocopying of this book is a CRIMINAL act. Anyone found guilty is LIABLE to face LEGAL proceedings. UNIT-1. Sofware Process Maturity, Process Reference Models (PART-B) ESSAY QUESTIONS WITH SOLUTIONS || SOFTWARE PROCESS MATURITY [.1.| Software Maturity Framework ai2. Define software proce: improvement. Answer t software Process * :OHIMHAW @) 1.10 to discover the systems problems very late. (iv) _ It does not follow any stable physical princi (7) It does not involve software management discipline. (vi) It is a system element that provides software functionalities to end users by hiding the implementation and design details, This leads to change in requirements based on view point of customers. ) Iintegrates various system elements together. s considered as a black-art by most of the non- software practitioners. This is because, it does not allow software managers to solve any problem on their own. Describe @ strategy for impleménting software process. ¢ (viii) ai7. Answer Strategy for Implementing Software Process To implement software process change, two forms. 1. Software professionals initially considers the changes fas immutable, incapable and technically insoluble. However to salve such problems they include detail procedures, standards, rules etc. ‘The management does not unders' problems. However, an effective change in software process em- ploys the following three phases. 1. Unfreezing’ 2. Moving and 3. _ Freezing. In software process, unfrcezing is consideged as the best effort to understand the software problems. The implementation St software change can be done based on the following, 1. Champions, Agents and Sponsors @) software takes stand the real software ‘Champion * ‘Champions are senior manag: the change in software process. They are res} the following, (@ __ Draw attention of manager to a particular s (ii) Take the blessings of sponsors. (iii) Launches the change program. (iv) Maintains focus on achieving the desired goals. Champions have less chance for success. cement persons who initialise ponsible for subject. Agents ‘Agents are group of people who are responsible for carrying out changes in planning and implementation phase. They are responsible for, (i) __ Specifying the resources. (ii) Assigning the task. i SOFTWARE PROCESS AND PROJECT MANAGEMENT [JNTU-HYD) ERABA, Agents should be selected bi considerations. 'd on the belo, y a ‘They must be responsible for carrying out ch d process. ange They must be capable of u k nders technical and political software problema E the ‘They must respect the people with whom they ‘They must gain the confidence of management must assure that they will act with cooperation acceptance. mand Sponsors Sponsoring is @ process where senior managem recognize the value of work and sponsor it. The fies bf sponsoring is done with the help of resources a cmfisial backing mechanisms. After sporing, the task “ Champions are done based on which the change process can be initiated. Change of Elements In software engineering pl communication are considered as Change. Planning phase focuses on including knowledgeable representative from each group that is affected. These’ fepresentative are responsible for developing @ competen plan and ensuring its acceptance. After this, the sav of vaplementation phase can be discussed. Here, some inital wi efforts must be applied to minimize the risk at the earlier stage At the end, proper communication must be'carried out inorder to maintain the project progress. 3. © 2 lanning, implementation ang key elements of effective Refreezing Refréezing is a process tl practitioners to acquire the require hat enables the software .d capability using general | practice. (i) Maintain a management team that can start the change. (i) Alter the procedures of organization. Build the measurement and incentives. Establish dedicated staff's0.as to monitor the performance and support it. ing and education program. (iii) (iv) 1.1.3 Software Process Assessment > of software professionals 18. Whatis software process assessment? Discuss the five assessment principles. Answer + Software Process Assessment Software process assessment is a typical review per- formed by software organization. This review is done by team who has high training and assess- jucted inorder to guide the software fessional and management about the process of improving | ‘overall software operations. Besides this, local and outide | complete sofiware process. ment experience. It is condi the reviewers can examine the (iii) Making calls to senior management etc. WARNING: Xerox/Photocopying ‘of this book is a CRIMINAL act. Anyone found guilty i is LIABLE to face LEGAL proceedings. UNI Software process assessments main purpose is 10 deter- mine the high priority area for improvement and also specifies dance to perform those improvements. The basic principle of assessment enables a local software manager and professionals to improve theit operations by providing guidance to them on avhat and how improvements must be done, assessment Prinelples ‘The basic assessment Principles enables competent ‘team, sound leadership.28 well as the cooperative organization to review te software process. The Various software assessment preps are discussed below. 1, Identify the process mode! needed for performing as- sessment. Recognize the requirement with strict confidentiality. 3, Involve highly experienced senior manager. 4, 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 onthe vision specified by the users. This enables a user to com- assessment 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 because, assessment pro- cess gets easily degenerated into loosely directed exploration. ‘Asithe 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 to explore the software process. In addition to this, it also act as a ‘framework to setup problem priorities using which the complete assessment team can work in collaboration with each other and can address on the key issues and recommendations. 2, Recognize the Requirement with Strict Confidentiality This assessment principle suggest that, assessment must be done’ inorder to improve the software process based on organizations viewpoint. This type of review must be done by. | hiding the problems from higher management. Even though it is very difficult to maintain strict confidentiality particular if the higher executive wants to see the results but also assessment team must try to maintain strict confidentiality. This is because, (Confidentiality allows assessors to discuss the levels of organization. (ii) Confidentiality is needed at organizational level so as to specify the professionals that their comments would not be attributed. i ‘ ‘Software Process Maturity, Process Reference Models 1.11 3. Involve Highly Experience Senior Manager Senior manager must be involved in assessment process as they are capable of assigning priorities to the organization. In process assessment, local manager ar¢ responsible for provid- ing approvals to software commitments. Besides this, they are also tesponsible for acknowledging the corporate management. Where as, the responsibility of senior manager is to handle mul- tiple projects from different locations, This belps in eliminating project disruption, simplify assessment arrangements and to promote consecutive action plan and implement them. Here, the senior manager is referred to as site manager. The site manager is responsible for performing assessments based on the follow- up action plans. This plan includes the work that must be done with priority, Moreover; the site manager must participate in (Performing reviews periodically (i) Assigning qualified people for work (iii) Analyze the progréss of the action plans 4, Respect the Views of People Working in Organization with Open Mind Software assessment is process carried out by group of remote experts, That is, in large and complex organization it is considered as a review that is done to improve the overall software ptocess. The local customer who are involved in the software process work hard to complete the improvement pro- cess successfully. Thus, the senior management must focus on taking local views of the customers. The assessment tedm must take the ideas suggestions 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 ‘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 is considered as an accurate procedure to improve the software process. In this, the concerns and suggestions are discussed to and reported to site manager. Later, based on the approval of manager the improvements are done. Q19. Describe the assessment process. Answer : Assessment Process ‘Assessment process can be carried out based on the fol- lowing steps, Step-1: Identify an Assessment Team and the Organization Inthis step, assessment team is formed based on the view- point of team manager. Initially, an assessment team manager ‘who have huge software experience is selected. The assessment manager must have posses the following capabilities, (© They must handle sthall groups and (i) They must have sufficient assessment experience. SPECTRUM ALL-IN-ONE JOURNAL FOR ENGINEERING STUDENTS SOFTWARE PROCESS AND ‘After this, he assessment team member who isa prom ling the soft- nent software developer, have experience in modk ware process is selected, An. ‘assessment team must have atleast vwninimum of six software professionals. The assessment (eam must be selected based on the below guidelines. should include a software profes” sfhware experiene ‘An assessment team sional who have eight to ten years of so “They must have respect in organization. @ di) (ii) They must deal informal people efficiently. (iv) » They must be a team player. aoe (v) They must attend the assessment trainin " ana be select An efficient assessment La fee sane ethan grOUP gfoup who are involved in assess eho are selected fr review such team ected frm assurance oF SUPPOM ‘who are involved in the proce », supporting the assessed project ization must a part ofassessmen ey must focus on professional who beloni 1 full time assessment team mi () Planning process (ii) Provide background knowledge about ‘organization (ii) Setup focal point to logical assessment and follow up gs to the organi ember. Th action plan. ‘Step-2: Considering Self Assessment Self assessment is a process where in the organization assess the software process by themselves, It is basically done inorder to identify the potential problems that are present within the software process. This assessment initially carried out by assessment stafTin most of the organizations. In this, a 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 o 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 self assessment are as follows, () Assign work to people when needed. (ii) 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 rrules for assessed organization and assessment team members to carry out the assessment process successfully. An extemal assessment is basically carried out by site manager and assessment team leader. To do this, they must sign a written eet including the ground rules. These rules are tested PROJECT MANAGEMENT [JNTU-HyDe, “he assessment team members mus of assessment confide Rule-! keep ae rea ye opening and cl The : Rule? conducted by team members, ule 3: The site member must involve atleast two Nog ay professionals besides regular member Bosessment arrangements and execute statdle follow-up action plan. the Wor -the development and implementati " ‘action plan must be done by site man, OF folloy, the assessment recommendations, bay? Rule-4? ‘A local member of assessment must fesponsible for creating a action plan, also be a . lk Rule-5: Besides external assessment, the organiza sondetinout assestmensbasd ofthe shove rot, nd ry}, ly ‘Train the Assessment Team- step-4: ‘The assessment team must completely par tring period, onsite review as wells wrap-up meets tram should attend each session by ene (Keeping the unrelated calls on hold. Gi) Gi) escheduling the meetings and escheduling the commitments. Moreover, te role of team leader isto conduct ee day raining program describe he processofaseqet to enitire software team This program creates a famijin™ to cipe asexsment process among the assessmen is arty enables them to establish a cohesive work hd assessment training to new team can be conducted ch the senior management or by the member who are prey by te sed about the assessment process. This training progn seat out inorder to make the new team understand abo” How organization is assessed? @ How to contribute on assessment plan? di) (iii). Participate equally in assessment process, ‘The training program is conducted: in th eee 1 following 1.. Initially, outline the sch jecti sei 8 edule and objectives gf t 2, Review, the assessment principles in accordance to | software process model which is considered as a | assessment ffamework. 3. Abrief outline of organizations mission must be created by the assessment team based on the management structure and its history. Discuss the assessment guidelines with the team member and ask them to sign/authenticate the written agreement 5. Conducta team building exercise that helps in establishing an effective and mutual supportive operational mode. WARNING: Xerox/Phot it ¥ toeopying A AnisinesEais a CRIMINAL act: ANYON fodi#Gl Guilty is LIABLE to face LEGAL proceedings. UNIT-1. Software Process Maturity, Process Reference Models « GA detailed assessment plan must include the following (i) Topics ofall the sessions, (i) Discuss about the leader assignments, Identify the errors and how to eliminate it, When team conclusion must be reached and how. ii) (iv) (v) How to prepare and present the report, when to prepare it and who will present it, * Rehearse the portion of process until the t. 1 gets comfortable with its role, ee 3, Final training task must includes the details of on site " periodiplanning. An onsite planning is a process where a team member can make a note of key active projects, They can i discuss a way in which the desired project can be assessed. This plannin, focus on identifying the different back-up project certain projects becomes unavailable. To cover the entire projects, a review of three or six projects must be done Based on project selection final details of on-site period should be fixed depending on which meeting can be conducted, participants can be selected, maintain daily schedule and provide administrative support, (20. Discuss in detail about conducting assessihent. ‘Answer ¢ ‘Assessment Conduct Assessment conduct isa method used for implementing the complete project. This type of implementation focuses on specifying answers tothe following. () The purpose of the developing project. (i The details of how the project works. (ji) The various problems encountered. (jv), The desired result that can be obtained. | The answers to above set of questions must be prepared before the actual assessment period gets started. The project manager is responsible for reviewing these questions and also for providing the overview about status of the project and fur- ther suggestions, Assessment is generally conducted to ensure thatthe software process is developed on time with sufficient materials. The assessment are basically conducted by a meeting | with a group of software professionals or representative who | have detailed knowledge on the below facts of software process: () Software quality assurance and release. (i) Software testing. (iv) Software coding, | (vi) Designing and requirement gathering. | (ii) Software integration. Unit testing. 3 Assessment conduct is a free discussion done by professionals to provide suggestions oni many key problems. The representatives who participate in this assessment must possess the following capabilities, (i) They must be a opinion leader in a desired area. (ii) They should work on project instead of staff, (ii) ‘They should be technical professional instead of manager. ‘They shbuld 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 difficult to get accurate information. The reason for such inefficiency is listed 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. 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 ieam must discuss on the required terms. (iv) Gi) (iii) Respondents are unaware of work going on in their organization 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 expetienceand to fitter the current knowledge of people. (iv) People cannot accept the truth The respondent will not willing to accept the truth about misused favorable terms, unusual events ete. As it is difficult to obtain the accurate information for above reasons the assessment team must examine and check each phase of assessment. Step-2: Assessment Conclusions Assessment conclusion is a method wherein an assessment team creates a conclusion report on preliminary outcomes. This report includes the following, @ ___ Detail description of site status and (i) Summary about preliminary key areas, 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. ‘SPECTRUM ALL-IN-ONE JOURNAL FOR ENGINEERING STUDENTS feta 1.14 “The guidelines to creaie assessment conclusion report based on initial outcomes are, (Review the major issues of the projects (i) Wentifying the key issues of next maturity level. (iii) Display,the supported assessment, + (iv) Action recommendations that are addressable. (v) Extensive generalization. Similarly, the guidelines to create assessinent c based on presentation are, (i) Agenda # (ii) Scope of assessed project (Gi) Conducting assessment based on sehedle . onclusion (iv) Summary of composite status et Step-3: Assessment Report ‘Assessment report is 4 final aut ‘and site recommendations created by the S58@55701 0. four items ‘manager, It includes reco 1 ‘cannot handle which are of high priority. AS Ot uires special attention report and i task mi is on dations must be . Such recommen ust | aa Oe fel at be implemented based on priority. exp vand m ‘The outline of report will be, oO ‘Summary and Conclusions ; It includes the detail summary of outcomes an recommendations. (i) Assessment Background . It specifies detail description “of assessment background and assessment process, (iiiy Site Status It describes summary of site manager. (iv) Key Outcomes 4 h outcome. It includes brief explanation about eac! (v) Recommendations 1k defines description of recommendations based on priority. (vi) Appendices It specifies assessment agreement. The guidelines that must be followed while creating assessment report or recommendation are as follows, (@ Wording and formatting must be done carefully. (ii). Start the recommendations with a single or two sentences. (iii) ‘State what is recommended. (iv) _ Specify the purpose of recotmmendation and (v) Specify the process of carring out the recommendations. WARNING: ‘Xerox/Phototopylag 6f iH bbok'H & CRIMINAL act! Anyone foultid guilty is LIABLE to face LEGAL proceedings. SOFTWARE PROCESS AND PROJECT MANAGEMENT [YNTU-HYDeR, y Tan assessment report must only be in wn po because, . fome | reais eriten cecommendation enable th w@ understand ‘what is to be recommended, Men Go tteliminales ambigious records of wha ig iii) ttactasa ideal too! that helps the software p nM Gi) (clearly describe about the action pst, implementations. . Plan ay step-4 Action Plan action plan is a follow up plan repareg » _" eal organizations under the supervision of knoyje,’Y te Jos team member. Itspecifies how the assesses ‘hou assessm jent fe carried out here, 3 software professionals must prepare (Tee Ser result and acceptance, Dy ‘The key manager must be responsible for traekin, he Gi) jutcome of the actions taken. ‘The site manager must periodically review the Gi) and progress of project. Stalling Step-5: Reassessments Follow-up assessments must be conducteg 4 y ization, after the development and approval Of initial atin plans because, Ithelps in tracking the progress of the project, @ i) rtspecifes the future milestone thats needed to comp an action prior to assessment. lee (iy Ithelps in assigning new priorities for coninugy 21, Discuss in brief about various consideration, to implement assessments. Answer ? Considerations to Implement Assessment ‘The considerations that must be taken to impledx software assessment must be interms of, 1. ~ Risks and 2. Staffing, Inthis, assessment of risk will not provide any signficat improvement. Hence, a catalyst is required to inorder to keep tack of improvement priority like management reviews and goals, Here, long term goals are completly established ar sub goals are specified. Here, the senior manager isresponsie for maintaining high level check point, specifying the pas and establishing the periodic issues. 1. Risks “The key risks.and actions of software process are, (a) Schedule Conflicts ; Schedule conflicts is a process that helps in conéut | ing‘one third of assessment. Iti an approach that enables executive to discuss about the underlying issues with te sie manager. \ \ sf atl ‘Software Process Matutity, Process Reference Models et jadequate Support 7 ® 3 Inadequate management support ig asses anime 10 MADEENEH eye Senior executive snag tno subse ia Moreover, nel manage ae responsible for managing softwere g : bat 7 provide sufficient organization priority. i Lack of Follow Through if management changes and high priority i qoute the the site manager must oss on rede a couman. Site manager can even create a final assessment per complete action plan. If action priorities is oe ined then improvements cannot be done efficiently. Here, sige pe achieved the manager can change efors tone s improvement capability and proper improvement goal. L Staffing ' staffing is also an severe implementation i sessment fechnique that generally include, iepiem. Wie ‘Asmall group of people/staff who i : p of works full-t id , inorder to provide improved efforts, software engineering process gTOUP. Participation in parttime project within action plan ‘working group. Implementation and review of project based on resulting actions. @ Gi) 1.1.4 The Initial Process 22. What are the tasks involved in intial process? Model Paper, 22(a) Answer = task Involved in Initial Process Initial process level is also called as adhoc process level. urs level, the requirements of sofware process is defined, pinned, managedand developed. Tis phase doesnot deals with sedng cost, quality assurance and scheduling Of projet. In the software professionals focuses on identifying (i) Senlor Management Senior manager is responsible to develop an operating plan if the commitments are not fulfilled by the competent people. This increases the frustration among the management. (ii) Software Manager Software manager are responsible for managing the software. But, they are frequently replace by new ‘manager as an when required. ‘The basic tasks that must be performed at 1. Planning Cost éstimation Project Scheduling Performance tracking, I level are, Change control Commitment management and a4 een Quality assurance. 3 23, Discuss the common problems of chaotic software behavior and general solutions for the initial process chaos. Answer : Problems 1. Software manager most oftenly make guesses instead * of plan. If the guess fails, 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. 2, 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. this phase, theunplaned priorities as well asthe unmanaged change. As ‘unh identification cannot bé identified easily. However, as | 3. To scale a software project following cycle must be fol- the software progress the unplanned priorities and unmanaged lowed ily i ified. jh lk to i a 5 a : oe eae aay eee The members who belong (i) ‘program is written with multiple lines of code group must P than expected. y le time. 6), Delivery of projest on schedule ime: (ii) New technical and management issues occur as (i) Efforts that should be made by individual ona specific the programs become big. project and i ‘ : ‘ : (iii) As this is a completely new experience, it is a (ii) ‘Strengths of the organization. surprise. ‘The staff that are included in this group are, (iv) If there is an increase in scale, then the cost in- Well Intentioned and Coinpetent People creases. ‘ Such people do their job effectively on committedtime. | 4. Higher maturity level is; achieved by an organization (or) Buit, due to lack of efficient planning and management, new: ‘management due to increased competition andnew resources, poor coordination they fail in performing the technical challenges. The maturity basically increased, required services. due to lack of training. + «SPECTROM ALLIN-ONE: JOURNAL FOR ENGINEERING STURENTS OMA The general solutions for the initial process chaos are, Systematic project management miust be applied by estimating, planning and managing the process. ‘Change management must be included by controlling changes gathering requirement, designing. implementa- tion and test. 7 3. Software assurance must be performed using independent technical process inorder to ensure that essential project activity are performed properly. “The basic principles that must be followed by asoftware organization to control 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 part. Consider software development as a Jearing Prooess- Fix the gap between the knowledge and tasks- ify what is unknown. ar ef managed, audited and reviewed inorder tocensure that work is properly planned. Complete the assigned work to meet the commitments: Define the plan to improve the knowledge. k 2 3. 4. 5. 6. 7. 8. x i u 1.2. THE REPEATABLE PROCESS Q24, Write short notes on commitment discipline. OR When the process Is repeatable? Why? ‘OctiNov.-20(R16), Q6(b) ‘Answer = Repeatable Process “Asoftware process is said to be repeatable if it allows a ~ setof actions to be performed for making the software efficient ‘while minimizing the variations in development and limiting Unwanted resource utilization, For a successful and efficient Software management, commitment discipline plays a key role. ‘Commitment Discipline Software project management is a technique that focuses ‘on managing the software, Its basic purpose is to ensure successfl ‘completion of project. To ensure this, system considers commitment disciplines its basic foundation. Commitment discipline is a method that enables planning, estimating, reviewing and system tracking, ‘This method ensures that the organization meets its specified ‘commitments. Commitment discipline is achieved by, 1. Make commitnient 2. Commitment hierarchy and 3. Software commitment process. L Make Commitment . Commitment is a type of agreement done by single person to perform a task on time. It mostly specifies, (i). Plan of completion date (ii) Considerations that are to be made and ii) Payment, SOFTWARE PROCESS AND PROJECT MANAGEMENT (NTU-HYDER ny I J ‘Commitment is defined by Salancik as follow, a primary foundation to perform sfmutipe professionals work with voordinat hee commitments are essential required. For example ity ers work on a single project then in Nt anges work must be partitioned among the team. Th "aa ‘neludes the following distributions. ition @ di) Gi) dv) ) (wi) (vii) Program version and Mor, Function distribution Common interfaces Standard formats Naming conventions Test plans Data design (viii) Test cases. ‘The programmers can work effectively, if they in mutual coordination with each other and can achieve commitment process. In large software projects, coopera efforts of individual is required. This is because, large me fnvolve many people and detailed coordination of both cffective commitment can be achieved based on follow elements. ing @. ‘The person who do commitment must willingly the committed task. " Gi) The commitment discipline must include work, resources and schedule. (iii) Prepare an agreement specifying what work should be done, who will perform it and when it should be'done. (iv) State the commitments openly and publicly. w) (vi) Meet the commitment as an when needed. Prepare a advance notice of new commitment date the committed date is not reached. 2, Commitment Hierarchy Commitment hierarchy is a technique opted by management team inorder to make commitments and meetthen | on time. It specifies the process based on which work should | be done to complete the desired commitment on time. Since commitments are visible to users, strong management suppor | is needed including the change in requirements by customers This helps in developing and meeting the desired estimations | and plans. Besides this, the other management commitmentare, () Supporting the required facilities (ii) Conducting meetings and (ii) Scheduling the meetings. WARNING: xerowPhotocopying ofthis book is 6 CRIMINAL act. Anyone found guilty Is LIABLE to face LEGAL proceedings uit Software Process Maturity, Process Reference Model Fortware Commitment Proces 3 commitment process isa management principle jue oped bP Bazin soas 0 achieve the following, ‘The senior executive of the organization should make > commitments for software delivery, Commitments must be done after the formal review and + concurrence process is completed successfully : Reviews and concurrence must be Properly conducted by enabling enforcement mechanism, ‘The responsibility of senior manager to perform the amid workon time are discussed below, () Define work among customers and developers. (ji) Produce,a document plan cohtaining resource estimate, cost estimate and schedule. Involve parties who agree upon a written agreement, (iv) Develop a business and technical, preparation to ensure commitment irrespective of risk. (0) Enabling the participating group to make use the resources as an when required, Conduct independent review to ensure that work is done in accordance to organization standards. Gi) wi @s. Describe the management system of commitments. Answer + Management System The general objectives of management system is based on the following components. |. Defining a technical and business strategy inorder to achieve long-term goals based on growth rate and market position. 2. . 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- nizations to achieve the desired commitments. These objectives are common to all the software groups since they have equal contribution for defining resources, assigning priorities, generat- ing short term responses, identifying, long term performance, improving productive capability and delivering of products, In management system, senior management is respon- sible for Creating annual revenue report. Identifying profits. Measuring productivity Producing quarterly and annual work report by corporation, ’ Mi 1.17 ‘The conflicts that effects the efficient management sys- tem are discussed below, . Plans of Product and Period i onal framework Annual operating plans creates an operational between line and staff. This plan includes the task that must be performed, assigning of resources as well as responsibilities to ‘complete the project. Here, allocation of resources to project and staff are considered as an initial step in project planning. ‘The various types of plans that are defined by manage- ment system are, . 1. Operating Plan i ical issues of organiza It deals with business and technical issues of tional and annual terms.’ Due to this, it is possible to develop the following based on each organizational entity. (Capital requirement Gi)’ Expenses ii) Specifying product delivery iv), Defining annual productivity — (v), Stating annual profitability and (vi) 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 each project has their own set of resources, some of them are required for common purpose on periodic basis. Specifying management strategies. Eventhough, the purpose of product and period are clearly stated there are few distinctions between thetwo. Thats, 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 difficult to collect annual data on cost, quality and productiv- ity. However, it is possible to measure data on periodi¢ basic by translating the project data into periodic tems like annual budget, plans and reports, : 3. Management Overview Amanagement system makes use of review and conten- 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 the conflicts between product and period then it is possible to prepare a consolidated project plan which can be incorporated in later subsequent plans of next organizational level. Here, a ‘unique individual plan is created by each project prior to project initiation, periodic reviews and update, f _ SPECTRUM ALLAN-ONE JOURNAL FOR ENGINEERING ‘STUDEI BEER eRe scm MMAR X SOFTWARE PROCESS AND PROJECT MANAGEMENT UINTUSYDERAR 1.18 4. Contention Process , ‘Acontention system is followed ina followed by contention system is to understand the relevant be said that contention system helps in finding best decision. partes in advances sacinand rational resolution. The Basic py Ope pd tae best decision 10 solve it Thee Me ie P — “ne principles of contention system, * Htea jes of agreement and the reso), hi review system to support issues of the ‘The following discuss the possibiit Review the major decision with all involved of issues before proceeding. a (ii). All the dfssenting parties must gather to state view and take decisions snp ese Bia ‘The senior member should identify knowledgeable agreement iT ma jg term used to assign responsibilty for sub sq, 7 more preparation is required. “Delegation es not ensure disagreement, Here, ‘Delegati @). (iii) Contention system do‘ mission. jew on the 80! 5. Quarterly Review oS anery revi Management system must focus 00 performing ai monitor their Progress: group of people to resolve product and Largeuern plan and goal , ‘ Of project and organization performance" i tive to manage operation like projects, technical support as lor exec eC fanagement (SCM), Software Quay 6 e ftware process. Quarterly review is dong ‘This review is done to monitor asses, by Sey ‘ - - seni ion Mi review, site manager act as 1 ‘Software Configuration M22 c ical support of 07 inca EPC). ‘This review is done inorder to verify ee status ofthe prj frware Engineering Prost ing quarterly review progress of eA focuses On organizay, Besides 1 aig and developing standardize software process, prove? ent Tn quarterly as finance. The techn surance (SQA) and Softwar based on its plan and objectives. jmprovement. This deal with anagem impfovised methods and technologies. — 26. List and explain the project planning principles: oe ct on time with sufficient resource, 1 a Answer: | performance of the system. The basi ing Principles eal i jred proje’ Project planning is a techniqu to pepe a pant os a framework for managing reviews and contol ss for analyzing the actual project planning prineples areas follows, : If requirements are unclear and incomplete then & quality program must be developed with oe and correct unde, certng of uses. The project plan begins bY MAPPIN i oe ear and iicomplete fequifement to accurate ana preg requirement. Project Plannil 1¢ that enables a user Is. It is a proces 1 structure that defines breakdowns of unit prog. Develop a conceptual design based on planning. This design is a initial structure H n ve allocation of functional units, as well as relationships between tinits. This initial structure also acts an organization] framework to plan and implement the work. It js.impossible to cover error from conceptual design. fine the requirements, resource projection, size estimation and schedule. ts are clear and include them in project plan. & 4. Develop a detailed design and implementation strategy if requiremen 5, Establish implementation details and document it later after future refinement. 6 Project ian acts as a framework for arranging the time and resources throughout the cycle. + ides this, the various planning considerations and planning cycles that should be defined are discussed below, Planning Considerations d scheduling resources: Similarly, new product functions must be specified Software planning is a way of estimating an develop a software on time. Besides this, software manager must also focuses on resource estimation and scheduling. Software remit must alo specify the duration of project, ensure quality of product. Software planning isa eriticl tet of software mn deement team. The team considers plan as an initial point to reduce schedule or cos. | Planning Cyele | ‘An iterative planning cycle is as follows, Initial requirements must be gathered as the starting of cycle. The requirements must b i ¢ understood to create a plan, however commitments cannot be made without a plan. WARNING: Xerox/Phatocopying ofthis Bdok's | 0 ocopying of tis 836K & CRIMINAL act. Anyone fotrid guilty is LIABLE to face LEGAL proceedings. software engineers and users on how, 0 i i) Process wt sober Maturity, Process Reference Models ud Jan by breakit Greate a plan by ing the work into multiple elements known as Work Breakdown Structure (WBS). timate the sizeof product, 4 ater the resourees, 5 Create a schedule. 6 ‘the planning cycle is as shown below, Initial Requirement ¥ Negotiating Commitment x Requirement No Decomposition [* @77. Discuss in detail about various elements of a software plan. Fotimating |__, [Estimating Project Product Size Resources ‘ k wes |__| Developing Schedule sLoc IS Schedule Met or Not Programmer | Developing > Product Months and Software Delivery Machine Time ‘Compass Actuals | ——| atabase) Figure: Planning Cyele of Software Development ‘Answer = The elements of project plan are as follows, 1. Goals and objectives : Work Breakdown Structure (WBS) 2. 3, Estimates of Product Size { 4. Estimates of Resources 5. Scheduling projects. Goals and Objectives ‘The goals anid objectives of project are developed during requirement phase. It is a negotiation period existing among Work is to be done ‘To measure success (iii) Needed time and resources are obtained. " SPECTROM ALLIN-ONE JOURNAL FOR ENGINEERING STUDENTS | 1.20 the work progress, design and implementation e! stable requirements ete. Change in require 4s one of the continuous probl goals of project plan are, SOFTWARE PROCESS AND PRO. invariably changes ffort, defining ments are considered fem of software engineering. The ‘As user requirement chunges i ‘The product must bé implemented in small incremed!s- must be selected inorder '0 support Each single increment ° 7 next subsequent increments OF to enhance requiremen! knowledge. i 10 3, Maintain the requirements at each increment pro designing. ae 4, Ifchanges in requirements — i sy a voding tation then perform those dl aise working, 5, If changes are not encountered then oP ig . hanes irement modification: ¥ > oI start the designing Process: 2, Work Breakdown Structure (WBS) For answer refer Unit-ll, 23. 3. Estimates of Product ‘Size at “The product size estimate is considered a an quantita code assessment needed for product elements like subsystems <0 nand modules. The concept of contingency isapp to these estimates depending on the previous project experience 4. Estimates of Resources * “The required resouree estimates foreach WBS element are specified based on prior experience or unknown productivity factors. 5," Project Schedule ‘A schedule for key tasks and deliverable item can be specified depending on project staffing and reSOUrTe estimates. ‘@28. Write short notes on LOC and function points. Answer = Lines of Code (LOC) other metrics to assess project size. It esti LOC is one of the simplified metric present among all the mates the project size by taking into account number of source instructions present But it will not consider the header lines and commenting code ines during the process of counting. It is di fficult to determine LOC count at the beginning of a project, while quite an easier job to count LOC atthe end of a project. Thus project manager ‘adopted a technique of dividing the problem into module. Again the modules are divided into submodules till it figures out that the leaf node module size. Total size estimation is achieved only after gaining the estimation of lowest level modules. Function Point Metric ‘ In the year 1983, Albrecht developed Function Point Metric. It overcomed several drawbacks of LOC metric. The biggest advantage of function point metric is that it computes the size of a software directly from the problem specification. Whereas incase of LOC, the size can be estimated only after the product has been completely developed.- software Is a bool invoked, the number shows the m Function poin! software terms of Function while in th Unadjuste wt smalle input data and Jk feature ‘ tha ct funet tee gt | Hct which possess several features eet : re Pro the product which possess less features, Of V size, When the function is invoked it not converts it into output data. For instance, ads the ‘of library system. When this book le Me iy with treads as input and provides its location ety frcopies available as output, ‘ong. ‘Thus calculation of number of input and ow ratamber of function Which supports the yt tT metric also helps in estimating the «jo: rset The size i8 presented in fineton mat’ the weighted sum of the five problem characterin ir point is calculated in two ways, the first step, the unadjusted function points ex second step technical complexity factor is, estimagt Itput ¢, in se In} ‘ed Function Point (UFP) Unadjusted funtion point is expressed in the follow ng manner. (uy *4+(NO)*5+(Na)*4+(NF)* 10+ QT)», UFP: Different Parameters @ Gi) ii) dy) w) ‘The different parameters of UFP are as follows, Number of Inputs (NI) pata item input is provided by each user data 1 different from user inquiries. Programmers do not coum errual data items but only consider set of relay ‘asingle input. For instance, entering the deals Stanemployee in pay roll software such as Name, Phone numbers, Address, Sex is considered as ead related single input. ol Number of Outputs (NO) Outputs denotes the Screen outputs, error messages | juced, reports printed. When number of outputs are calculated only set of related data items is counted by, | individual data items present within the report are no, considered. Number of Files (NF) Files refers to logical file and physical file. Logical file denotes a sét of logically related data. Therefore they can also be physical files or data structures. Number of Inquiries (NQ) ‘Number of inquiries refers to the distinctive interactive | queries which are inquired by user. These are nothing but the user commands which needs action to be performed. indi inputs as Interfaces refers to things used for exchanging details with other systems, For example, data files, tapes, disks. WARNING: xeroePhoszoig fag MMOL SFL ENS PURPA. MELE far LEGA: Proceed, u Number of Interfaces (NT) | | | - T-1_ Sofware Provese Maturty, Process Reference Models
      ) Estimating Blas It is a type of error that occurs at stage when estimates ‘are made, If the estimate is done early, there are less chances of inaccuracy, The greater the chance there are more chances of inaccuracy. (il) Estimating Contingencies Contingency is a technique wherein the programmer ‘can estimate the desired code inorder to implement a function. It deals with resource estimate scheduling and increased cost. ‘To.estimate contingency prior knowledge of programmer about new product must be made and its range should be selected. Each software size should include the concept of estimating contingencies with product code. Q30, Explain about scheduling and project tracking. Answer: Model Paper-t, Q2(b) Scheduling Project scheduling is determined based on the resources that are encountered over planned product development phase. This estimation is done by analyzing the data depending on the historical experience organization. If such data is not available then factors like resource and time that are publicity available are used for determination. The conditions that should be consider. for scheduling are, 1. Various project phase definitions Various resource categories included Different software methods used ‘Various product types being developed ‘Various levels of programmes skills a rns Degrees of project. The conditions can vary among organization and projects. As the.organization must focus on gathering the resource distribution data. After this, the overall project schedule is followed. This is as follows, 1, Develop asstaffing plan. “2, Establish/create a preliminary schedule by performing comparison among cumulative resource needs and expected needs, 3. _ Review the preliminary plan sos to ensure that there is a consistent assignments of staffing based on schedule and resource profile. The process of scheduling is done based on work breakdown structure which is dependent on the current project phase as well as previous experience. Project Tracking Project tracking is a projéct ptocess that focuses on schedule and checkpoints. This process is referred to as earned- value project scheduling that focuses on following, ‘SPECTRUM ALLIN-ONE JOURNAL FOR ENGINEERING STUDENTS t 1.22 SOFTWARE PROCESS AND PROJECT MANAGEMENT [JNTU-HYDER Ay 3. Determine checkpoints for each project phase to perform tasks like, ; (Creation of module based on specification that are completed and approved Gi) Creation of module that has complete design, inspected and corrected (iii) Creation of unit plan module that is complete, reviewed and approved (iv) Creation of module that is complete and clean (¥) Creation of code module that is inspected completely and corrected (i) Creation of module that is unit tested, delivered to SCM with baseline integration. Determine the resources that are needed to complete each checkpoint based on total project. Plot the plan as shown below, ; 90 Complete percentage Were hown in the dotted line. ‘Actual performance ofthe project is tracked as the project progress. This is s As ee is applied Sealed project, the overall status ofthe project is. specified to users. Project tracking fay i projects can be done based on the following key points, : i Each checkpoint must be measurable and specific. 2 A detailed plan must be created that allows the checkpaints to (i) Complete 50% of the module design, conduct reviews make corrections (i) Complete 25% of test cases without errors. - (iii) Complete: 15% of test program without error. 3, The project plan helps in determining the percentage of that is complete. Q31, List and explain the basic configuration management functions. 4. Answer : Basic Configuration Management Functions In basic configuration management system initially a baseline is developed, after the initial product gets stabilized on eas successive set of increase (of a baseline) a new baseline in developed. Each baseline is then maintained within a database, at one place with all the changes that produced it. Thus, it can be said that a baseline is the official repository of the product and it holds the most current version, A baseline includes the approved changes and the tested code which is fully protected, ‘A baseline act as a soutce that helps the programmers to ensure that/their task is performeid consistently, ‘The main SCM tasks are, (Configuration control (ii) Change management : (iii). Revisions : : (iv) Versions, (v) Deltas (vi) Conditional code. oe ee WARNING: Xerox/Phot6vopiying ofthis bdciieé WIORIMINAL act. ‘Anjbrie fdtitid-qlitty.isLIABLE to face LEGAL. proceedings. é - ynitt Software Process Maturity, Process Reference’ Mod ration Cont 1.23 ‘The task of configuration can revolves throughout an official copy of code. ‘The eariest way to protect each system revision is to Keep a separate official copy at ever revision level. ° r Initial Establishing [Baseline development baseline update validation Authorize change : Change implementation ‘Approve Change change validation Figure (ik: Overview of Change Management g 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 ofthe same or similar versions of common code, sometimes different unl ciges areiiede to cocrect Gi see problems, {} Thefinal cost ofthis can be understood by considering system drivers. Example, one programmer may require a copyiof the ‘system control program for unit test. Although the control program may not completed, the functions this programmers required may be unstable. * Hence, its helpful to provide a control program copy with this function rather than write the developers time. Revisions . Revisions is one of the significant task of configuration management. Inthis large systems, some prograim such as control system, provides essential function for all others. + Ifthe component's module have been combined into a testable unit, then it can be tested with the latest control program level. % These previous tests can be re-run to find the problem source, if further problem are found. + % Ian early driver is produced again, using the latest versions of the control program modules, some of these module will likely be changed, so the previous tests are not exactly produced. One of the key feature is to keep track of all 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. 3 a: — Cofttinuous process of revision, integration and test is nothing but the development. Derivations One of the powerful software testing feature can be used to find what has changed. Example: Ifa program works on day the and not in the next day, then the first step isto find what are the changes. vessvoy, ns SPECTRUM ALLAN-ONE JOURNAL FOR ENGINEERING STUDENTS 0 erty SOFTWARE PROCESS AND PROJECT MANAGEMENT [JNTU-HYDE| 201 Level 226 Module TestA 201 Level 227 : Ml Rerun test A Jule Fase Dont .d the rerun was attempted : \e rerun was 4 Dereon data would sh thea was un ont ogame 16 : onlevel ny, Changes x and y can be identified. } Data then might be maintained in such derivation record is, 1. Revision level of every module. ! and tests. 2, Revision level of the tools used to assemble compile link, Joad and exeeute the program 3. Tie test cases used and the test information employed. 4, Thefiles used. siogasons, nla 5, Software ahd hardware system configuration along with peripherals, features, options and hardvang change levels 6. The operational steps. : 7. record of job streams being executed when there is no stand along test. Versions : fa module changes then there canbe other potential issues. Mi ‘with few small coding differences. Example q ‘The folowing figure shows tha, the standard memory mode switch would hold the larger memory siz. i “The dierent programs would have the different designation, like MEMS and MEML forthe standard and lage memory ore different tasks can be implements by the same modal, nanagement would be wed blow S12K andthe other sng ey . management modules. Lage Standard, ; memory memory Figure (i): Versions Deltas % Execution of deltas is another test of configuration management. ‘+ On one hand, the versions solves the problem of different functional requirement for the same module but on the other hand creates multiple copies of the same code. * — Toovercome this problem of multiple copies of same code use case deltas. WARNING: Xerox/Photocopying-ofthig Bobs & CRIMINAL ‘act: Anyone fouiid guity is LIABLE to face LEGAL proceedings. g ra -1, Sofware Process Maturity, Process Reference Models 1.25 : MEM | MEM Large memory Standard memory Figure (iv): Dottas ample: The above igure illustrates that saving the base medule like MEM, along with the changes required o makeitinto MEML., When the changes are required on MEM then the changes canbe made diretl, with interface will the delta code, » The changes are only made to the MEML code and the MEM code is left unchanged. -pnditional Code * ° soe Conditional program construction is used to han dle the small changes between modules, Consider an example, . Billing Billing Billing Program program program NY cr PA Newyork Connecticut Pennsylvania Figure (vi: Conditional Code Scenario The above example shows the billing program which include different functions depending on the,requirement of a state ‘on sales tax. ‘The program includes different sales tan versions, but they would not be included in 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, i One usage of conditions, case the code control as there is only one official copy if every module. Another advantage of the conditional code is that providing one complete copy of the complete program. All the code would 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 is dificult to control unauthorized distribution and use. ‘i 4 soibesoe SPECTRUM ALLINGONE JOURNAL FOR ENGINEERING STUDENTS, «3 :cnuen \ , 1.26 Q32, Explain in detail about SQA. Answer: Software Quality Assurance (SQA) Quality is used to determine ifthe software meets all the requirements that were specified during design phase, Software quality assurance is used to monitor the: software processes and methods for ensuring its quality, By using audits of quality management system, SQA improves the software quality: SQA is very much related to quality assurance in product manufacturing. There are some noticeable differences between a software product and a manufactured ‘Amanulactured product is something that is physica entity which can be ee?» ‘Whereas software product is invisible and temporary: roe cof this nature functions, benefits and costs sat pear i ‘measured easily. When # manu shipping. It vendo bea complete, Finished Prod bsnl software products intangible and can Pe" : aware i expensive : ws 1 es gacato develoring and executing test cases. tree ta because the ee wor as per users commands, lence Here

      You might also like