CS 615 Software Project Management. Final All quizzes and papers

Transcription

1 CS 615 Software Project Management Final All quizzes and papers Which of these is not an example of a project? P a g e 1 1. Buying clothes from the market on a special sale. 2. Planning for your friend s wedding. 3. Building a bridge across the Amazon river. 4. Cleaning the office building every day. Which relationship model is most commonly used in the Precedence diagrams? 1. start-to-start 2. start-to-finish 3. finish-to-start 4. finish-to-finish AOA activity diagrams are only represented using which representation? 1. start-to-start 2. start-to-finish 3. finish-to-start 4. finish-to-finish Which of the following is not true about the Delphi technique? 1. Individuals participating must know each other for Delphi technique to be successful. 2. Delphi technique is most commonly used to obtain expert opinion. 3. In Delphi technique participants are generally anonymous. Typically signing of project charter is the responsibility of 1. Project Sponsor 2. Senior Management 3. Project Manager 4. Project stake-holders

2 You are the project manager of ABC project. Mid-way through the project a key component was stolen. This was not planned for. The team met after the event and managed to make the product work without the stolen component. This is an example of 1. Risk mitigation 2. Transfer of risk 3. Work-around 4. Accepting the consequences passively. Most common cause of conflicts in a project is 1. Schedules 2. Technical opinions 3. Personal Issues 4. Project priorities The most long-lasting conflict resolution is caused by which of these techniques? 1. Smoothing 2. Confrontation 3. Compromising 4. Forcing You are the Project Manager of ABC project. The project is being executed in an earthquake-prone area. To take care of this you buy insurance for earthquakes. This is an example of 1. Risk mitigation 2. Transfer of risk 3. Risk contingency planning 4. Accepting the consequences passively. Which of these is correct with respect to a product developed or a service performed. 1. Bad quality is acceptable, but bad grade is not. 2. Bad grade is acceptable, but bad quality is not. 3. Neither bad grade nor quality is acceptable. 4. Grade and quality is the same thing. P a g e 2

3 Which of the following theory was suggested by Deming? 1. Apply continuous small improvements to reduce costs and ensure consistency. 2. Marginal Analysis 3. Expectancy theory - people expect to be rewarded for their efforts. 4. Plan-do-check-act to improve quality. Which of the following is not a tool for Perform Quality Control process. 1. Inspection 2. Benchmarking 3. Flow charting 4. Histogram You are the Project Manager for ABC project. You need to find out which issue has maximum impact on the project. Which tool should you use? 1. Pareto diagram 2. Control chart 3. Trend analysis 4. Fishbone diagram When analyzing quality for a project a Project Manager decides to use a tool. This tool provides a creative way to look at the causes or potential causes of a problem. Which tool is the Project Manager planning to use? 1. Pareto diagram 2. Control chart 3. Statistical sampling 4. Ishikawa diagram A Project Manager is using AOA to perform critical path analysis. The network diagram is represented as shown using below. Which of the following represents the path Activity Duration Dependent on A 3 None C 3 None P a g e 3

4 B 2 A D 5 C E 2 None F 4 E G 3 D,F H 1 D,F I 2 B,G R 0 H,I 1. ABIR 2. CDHR 3. CDGIR 4. EFGIR For the sequence diagram in ABOVE question 15, what is the float of activity B For the sequence diagram in question 15, what is the float of activity H Which of these is not a benefit measurement project selection method? 1. Integer Algorithm 2. Internal Rate of Return P a g e 4

5 3. Scoring model 4. Discounted cash flow Which of these is a constrained optimization project selection method? 1. Parallel algorithm 2. Number programming 3. Murder board 4. Dynamic Programming You are part of an expert committee deciding which project should be implemented by your company. Your committee asks tough questions from the project teams and helps decide which project your company should select. Which project selection technique are you using. 1. Scoring Model 2. Committee Selection 3. Murder Board 4. Selection By Quiz Which of these is a process in the Scope Management knowledge area 1. Identify Scope 2. Clarify Scope 3. Control Scope 4. Close Scope You have just been made the Project Manager of the ABC project. You are trying to read the WBS and are unable to understand some of the WBS components. Which should be your first step to understand this? 1. Refer to the WBS dictionary 2. Refer to the scope statement 3. Refer to the Project charter 4. Contact the previous Project Manager Who among the following is responsible for performing the scope verification? 1. Project Manager P a g e 5

6 2. Senior Management 3. The quality team 4. The customer You are planning to use PERT for planning of your project. A task has pessimistic estimate of 24 days, most likely estimate of 15 days and optimistic estimate of 12 days. What is the mean using the PERT technique? days days days days days Which of these is a process in the Project Procurement Management knowledge area? 1. Select Sellers 2. Administer Procurements 3. Administer Contracts 4. Plan Purchases and Acquisitions Oligopoly refers to which of these 1. There is only one qualified seller in the market. 2. There are no sellers in the market, so you have to build the product in-house. 3. There are few sellers and action of one seller will have impact on other sellers prizes. 4. Your company prefers to contract with only one seller. You are using straight line depreciation to compute the value of your computer after three years. If the current cost is $1000, what will be the value after three years assuming that the computer's life is five years. 1. $0 2. $ $ $600 Which of the following is not true about analogous estimating. P a g e 6

7 1. Estimate is based on past projects. 2. It is not very accurate. 3. It uses bottom-up approach 4. It is a form of an expert judgment You have been asked to make an estimate for a project. The project involves manufacturing 1000 toys. You expect that as the team manufactures some toys, the time to make them will reduce. Which estimation technique are you trying to use? 1. Analogous Estimation 2. Regression Analysis 3. Bottom up Estimating 4. Learning Curve John is an excellent engineer. The management assumes that since he is a good technical performer, he will be a good project manager too. Based upon this, John was promoted to Project Manager. This is an example of 1. Halo Effect 2. Expectancy Theory 3. McGregory Theory of X and Y 4. Herzberg Theory Which of these is an example of processes in the closing process group? 1. Project Closure 2. Scope Closure 3. Close Project or phase 4. Scope Verification The authority to approve or deny change request lies with 1. Project Manager 2. Customer 3. Project Sponsor 4. Configuration Control Board You are the Project Manager of the XYZ project. You want to find the planned expenses for next month. Which document do you need to refer to? P a g e 7

8 1. Cost Management Plan 2. Cost Baseline 3. Cost Control Plan 4. Cost Variance report Which of the following is not true about the WBS report? 1. WBS should focus in on the activities that must be performed in the project and should not focus on the deliverables. 2. The project team must be involved in developing the WBS. 3. As a rule of thumb, each activity of WBS should take less than 80 hours. 4. WBS is usually represented in a hierarchical fashion. Which of the following processes produces WBS as an output? 1. Plan Scope 2. Initiate Project 3. Define Activities 4. Create WBS Which process identifies the project manager? 1. Develop Project Management Plan 2. Develop Project Charter 3. Define Scope 4. Select Project Process You are the Project Manager assigned to build a next generation vehicle. You identify a dependency that the wheels must be designed and developed before the assembly of the vehicle can be performed. This is an example of which type of dependency? 1. External 2. Discretionary 3. Soft Logic 4. Mandatory P a g e 8

9 You are the Project Manager assigned to build a next generation vehicle. You identify a dependency that before the vehicle can be sold, it must be approved by the Government regulatory authority. This is an example of which type of dependency? 1. External 2. Discretionary 3. Soft Logic 4. Mandatory You are required to estimate the time to paint a large wall. You know it takes two hours to paint one square foot of wall. The wall has an area of 30 square foot. So you estimate that it will take 60 hours to paint the wall. Which estimation model are you using? 1. Bottom-up 2. Parametric modeling 3. Analogous 4. Expert judgment The level of accuracy for order of magnitude estimation is % to +75% % to +50% % to +25% % to +10% You are the project manager responsible for building a new web site. The project is running late. To bring the project on schedule, you decide to add additional resources to the critical path. This is an example of 1. Fast-tracking 2. Resource planning 3. Crashing 4. Schedule Management You are the project manager of ABC project. One of the risks that has been identifies is attrition of team members. Mid-way through the project you notice that the morale and motivation of the team members is going down. You think that this is a precursor to people leaving the organization. For this risk, low motivation is an example of P a g e 9

10 1. work-around 2. trigger 3. risk monitoring 4. risk planning You are working on the project of painting of your house. You identify a dependency that the painting of roof should begin only after two days of completion of painting of walls. This is an example of 1. Lag 2. Lead 3. Slack 4. Float What percentage of Project Manager's time is spent on communicating? You are the Project Manager for XYZ project. The scope of the project has been completed. You receive a request for a new module to be developed as part of this project. What should you do next? 1. You should approach the Project sponsor and ask her for a new module to be developed as part of this project. 2. You should approach the Senior Management and ask them for a new module to be developed as part of this project. 3. You should send the request to Change Control Board for approval. 4. Since the project scope is completed you should inform the customer that this change cannot be done as part of the project. Perform Quality Assurance process is part of which phase? 1. Planning 2. Execution 3. Control 4. Closure P a g e 11

11 You are managing the project of planning a party for your company employees. There is a risk that the employees will not come to the party. You decide to not take any action against this as the likely-hood of this is low. Which risk response strategy are you following? 1. Acceptance 2. Avoidance 3. Mitigation 4. Transference Ref: This is an example of Acceptance risk response strategy. The process of Conduct Procurements is part of which phase? 1. Planning 2. Execution (Conduct Procurements is part of execution phase) 3. Control 4. Closure You are the Project Manager of ABC project. There was a conflict between two key project members. The three of you meet and decide to use compromise as the conflict resolution technique. Compromise generally leads to 1. Win-win situation 2. Win-Loose situation 3. Loose-Loose situation 4. None of these The Procurement statements of work is an output of which of these processes? 1. Plan Procurements 2. Conduct Procurements 3. Administer Procurements 4. Close Procurements Which of these is a tool for Develop Project Charter process? 1. Project selection methods P a g e 11

12 2. Project management methodology 3. Expert Judgment 4. Earned Value Technique Which of the following best describes the purpose of a war room? 1. A war room is used for meetings between the Project Manager and the customer. 2. A war room is used for important meetings between the Project team and the senior management. 3. A war room is used for collocation 4. Whenever there is a resource conflict between different Project Managers, they meet in a war room. You are the Project Manager of a project involving building a computer. Your team members follow what you tell them because you have the authority to provide negative feedback in their performance appraisal. This is an example of which type of power? 1. Coercive 2. Referent 3. Formal 4. Reward Cost baseline is usually represented using which curve or line? 1. a Slanted line 2. an S-curve 3. a Z curve 4. a PQ curve You are in the process of Source Selection for a contract for your project. You are planning to use weighing process for source selection. There are four vendors being considered. There are two deciding factors price (weightage 40), quality (weightage 60). The scores of four vendors that your team has computed are displayed in the table below. Which vendor will among these four should be chosen? Vendor scores Vendor 1 Vendor 2 Vendor 3 Vendor 4 Price Quality P a g e 12

13 1. Vendor 1 2. Vendor 2 3. Vendor 3 4. Vendor 4 Which of the following indicate that the project is doing well? Select the best option. 1. A negative Cost Variance 2. An SPI of less than one 3. A negative schedule variance 4. A CPI of greater than one. You are performing Earned Value Reporting for your project. The project's CPI is 0.9 and the budget at completion is One thousand dollars. What is the estimated cost at completion? 1. Nine hundred dollars 2. One thousand one hundred and eleven dollars 3. One thousand dollars 4. One thousand and one hundred dollars Ref; EAC = (BAC/CPI). You are working on a project to build a bridge. You have reached the planned half way mark. The total planned cost at this stage is five hundred dollars. The actual physical work that has been completed at this stage is worth $400. You have already spent one thousand dollars on the project. What is the CPI? CPI = EV/AV. EV=400, AC = 1000, PV=500. You are working on a project to build a bridge. You have reached the planned half way mark. The total planned cost at this stage is five hundred dollars. The actual physical work that has been completed at this stage is worth $400. You have already spent one thousand dollars on the project. What is the Schedule Variance? P a g e 13

14 a. SV=EV-PV. 400 minus 500 is John needs to visit many countries as part of his job. He has learned that he needs to avoid being ethno-centric. What does ethnocentrism mean? 1. Not being friendly to strangers 2. Unable to get adjusted to the food of a new place 3. Belief that ones culture is superior to others. 4. Initial shock of landing in a new country. You are planning to use screening system for source selection process to select a vendor for supplying food for your company? Which of these is a good example of screening system? 1. You interview all the vendors and decide based upon the interviews. 2. You negotiate with all the vendors and select the one that provides the best price. 3. You only consider those vendors who have revenue of ten million dollars in the last financial year. 4. You select the vendor who responds first to your advertisement. Which of the following is not an input to the Conduct Procurements process? 1. Source selection criteria 2. Make-or-buy decisions 3. Organizational process assets 4. WBS You are using control charts to perform quality control. Which of these situations does not indicate that the process is out of control and an assignable cause needs to be assigned. Assume that the control limits have been set to three sigma. 1. One of the point is more than the mean + (3*sigma) 2. Two points together are more than mean +(2*sigma), but less than mean + (3*sigma) P a g e 14

15 3. Seven points together are on one side of the mean. You are the Project Manager of a car manufacturing company. As part of Quality Control you decide to check only 5% of the cars generated for environmental check. Which technique are you using? 1. Pareto Diagram 2. Control Charts 3. Statistical Sampling 4. Sample Selection Which of the following is true statement about risks? 1. If a risk is identified in a risk response plan, then that means that risk has already happened. 2. Once a risk has happened, you refer to the risk management plan to determine what action needs to be taken. 3. A risk that was not planned but has happened is called a trigger. 4. Risk identification happens in all the phases of the project. Which of the following is not true about the Close Project or Phase process? 1. Contract closeout must be performed after the Administrative Closeout. 2. The risk is the lowest at this stage of the project. 3. The probability of completion is the highest at this stage of the project. 4. Stakeholders have least amount of influence at this stage. Which of the following is an output of the Identify Risks process. 1. Lessons Learned 2. Checklists 3. Risk Register 4. SWOT Analysis In which process of Project Risk Management knowledge area are numeric values assigned to probabilities and impact of risks 1. Perform Qualitative Risk Analysis 2. Perform Quantitative Risk Analysis 3. Perform Numeric Risk Analysis P a g e 15

16 4. Plan Risk Response A node on a network schedule is that point in time at which an activity Begins 2. Begins or Ends (pg 297) 3. Ends 4. None of given A node on a network schedule is that point in time at which an activity either begins or nds. A is defined as "the work breakdown that covers the acquisition of a specific defense material item and is related to contractual effort." 1. Program WBS 2. Contract WBS 3. Contract Program WBS 4. None of given A Program WBS is defined as "the work breakdown that covers the acquisition of a specific defense materiel item and is related to contractual effort." Using PERT and CPM, , helps you complete a project on time. By using these techniques, you can determine the latest time by when an activity should start to be completed on time. 1. Individually 2. Combination 3. Individual and Combine 4. None of given Using PERT and CPM, individually or in combination, helps you complete a project on time. By using these techniques, you can determine the latest time by when an activity should start to be completed on time. Predecessor activities need to before the next can begin. After a predecessor activity is completed, the successor activity becomes the predecessor for another activity. 1. Both start and end P a g e 16

17 2. End 3. Start 4. None of given Predecessor activities need to end before the next can begin. After a predecessor activity is completed, the successor activity becomes the predecessor for another activity. A extends the Program WBS to a lower level in order to provide management and cost information to the Government 1. Program WBS 2. Contract WBS 3. Contract Program WBS 4. None of given A Contract WBS extends the Program WBS to a lower level in order to provide management and cost information to the Government. Which of the following tools and techniques shows the impacts of one decision over another as well as the probability and cost of each risk along a logical path? 1. Simulation 2. Decision tree 3. Probability / impact risk matrix 4. Sensitivity analysis To risks from occurring, the project team prepares the risk plan before the commencement of the project. 1. Avoid 2. Deal 3. None of given 4. Manage To avoid risks from occurring, the project team prepares the risk plan before the commencement of the project.. theory when the deliverables of a project are more important than its phases. This normally happens when the deliverables are decided before the project begins. P a g e 17

18 1. Project life-cycle-based 2. Scheduled 3. None of given 4. Deliverable-based You use the deliverable-based theory when the deliverables of a project are more important than its phases. This normally happens when the deliverables are decided before the project begins. Risk analysis and management are a series of steps that help a software team to understand and manage Uncertainty 2. Crises 3. None of given 4. Problem Risk analysis and management are a series of steps that help a software team to understand and manage uncertainty. There are types of Work Breakdown Structures. 1. None of given 2. Two 3. Three 4. Four The two types of Work Breakdown Structures. Which of the following Network scheduling techniques use network schedules to trace the completion of predetermined activities? 1. Gantt chart 2. PERT 3. CPM 4. Both PERT and CPM Which of the following is displayed as an S-curve? P a g e 18

19 1. Gantt 2. Cost baseline 3. Critical path 4. PERT The cost baseline is graphically displayed as an S-curve. Over the course of the project, a comparison of the due date and the date delivered provides a metric for how well deliverable dates are. by the project team. 1. Met 2. Scheduled 3. None of given 4. Changed Over the course of the project, a comparison of the due date and the date delivered provides a metric for how well deliverable dates are met by the project team. Each. can be subdivided into sub tasks. 1. None of given 2. Program 3. Task 4. Project Each task can be subdivided into sub tasks. To aid planning, scheduling, and monitoring a project, you can use tools 1. PERT and CPM Timeline 2. charts and Gantt charts 3. Both of given 4. None of given To aid planning, scheduling, and monitoring a project, you can use tools such as: Program Evaluation and Review Techniques (PERT) Critical Path Method (CPM) Timeline charts P a g e 19

20 Gantt charts CSOM stands for 1. Computer system operator's manual 2. Computer system offered manual 3. Computer software operator's manual 4. Computer system obvious manual Computer system operator's manual CSOM The DIDs (Data Item Description) includes a section called 1. Formal Documentation 2. Preparation Instruction 3. Associated Documentation 4. Effective Resolution The DID s include a section called preparation instructions that provides a large degree of freedom by permitting tailoring of the document format and the use of alternate presentation styles. is identifying the specific activities that must be performed to produce the various project deliverables 1. Scope Planning Scope 2. Definition Activity 3. Duration Estimating 4. Activity Definition Activity Definition identifying the specific activities that must be performed to produce the various project deliverables. The decomposition of a software project is one of the first task of 1. software engineer 2. software project manager 3. software analyst 4. software tester P a g e 21

21 identifying and documenting interactivity dependencies 1. Activity Definition Activity 2. Sequencing Activity 3. Duration Estimating 4. Resource Planning Activity Sequencing identifying and documenting interactivity Dependencies. To expand or contract project scope, to modify cost, or schedule estimates are examples of 1. Work results 2. Change request 3. Change schedule 4. Change scope Change requests. Change requests (e.g., to expand or contract project scope, to modify cost [budgets], or schedule estimates [dates, etc.]) are often identified while the work of the project is being done. is based on soft skills and relies more on human factors, such as collecting information during group discussions 1. Source lines of Code (SLOC) 2. Function Point (FP) Constructive 3. Cost Model (COCOMO) 4. Delphi technique Delphi Technique: This technique is based on soft skills and relies more on human factors, such as collecting information during group discussions. The Data Item Descriptions define the formal documentation standards for all required documents generated during the development of software according to standard P a g e 21

22 The Data Item Descriptions define the formal documentation standards for all required documents generated during the development of software according to standard There are Planning Process Tasks 1. Ten 2. Thirteen 3. Fifteen 4. Seventeen Lessons learned are important to document because an organization can use them to improve future projects and the Project Management process. Therefore, in project closing procedures, it is helpful to review the 1. Checklists for risk identification 2. WBS 3. Original contract 4. All of given technique used to integrate the project s scope, schedule, and resources and to measure and report project performance from initiation to closeout 1. PMIS 2. EVM 3. Stakeholder skills and knowledge 4. PV Earned value management (EVM). A technique used to integrate the project s scope, schedule, and resources and to measure and report project performance from initiation to closeout. A change in the arrangement of tasks can occur on the basis of theories of WBS. 1. Two 2. Three P a g e 22

23 3. Four 4. Single In the planner develops estimates of the information domain. 1. Function point sizing 2. Standard component sizing 3. Change sizing 4. All of given Function point sizing: The planner develops estimates of the information domain. Its characteristics will be discussed later in the session. Which of the following is not true? 1. It is important to select the best people for jobs and then instruct them in the best methods 2. The team leader need not assess the training needs of his team members.? 3. It is good to improve productivity by encouraging reuse of existing software components.? 4. It would be good if the employees consider work as natural as rest or play and they like it. is one of the most important management activities and is an ongoing effort throughout the life of the project. Software project management begins with a set of 1. planning 2. analysis 3. organizing 4. leading P a g e 23

24 In problem evaluation area of effort, once problems have been identified, the determines what information is to be produced by the new system and what data will be provided to the system. 1. Analyst 2. Designer 3. Coder 4. Manager 1. spiral model is an evolutionary life cycle model that combines the linear nature of the Waterfall model and the iterative nature of the Prototyping model. 2. Use functional structures when the organization is small, geographically centralized, and provides few goods and services. 3. Project interfaces generally fall into categories i.e. Organizational interfaces, Technical interfaces, Interpersonal interfaces, all of the given 1. Network scheduling techniques are Pert and CPM. 2. Despite the different approaches followed by PERT and CPM, both techniques have some common components. These include: 1. Activities 2. Nodes & Network 3. Critical path 4. All of the given two types of risks are. product_related, development process related there are steps of risk management. (3, risk identification, risk analysis, risk mitigation) SQA is an umbrella activity that ensures conformance to standards and procedures throughout the SDLC of a software product. P a g e 24

25 In Microsoft Project, you can specify four types of dependencies: Finish-to-Start (FS) Start-to-Start (SS) Finish-to-Finish (FF) Start-to-Finish (SF) There are eight schedule-related constraints are available in Microsoft Project. As soon as possible (ASAP) As late as possible (ALAP) Start no later than (SNLT) Finish on later than (FNLT) Start no earlier than (SNET) Finish no earlier than (FNET) Must start on (MSO) Must finish on (MFO) Using Microsoft Project 2000, you can create Two types types of standard reports: Standard resource report, Standard task report there are four types of maintenance activities: Corrective Adaptive Perfective Preventive The nature of software applications can be characterized by their information 1. complexity 2. content 3. Determinacy 4. content and determinacy P a g e 25

26 CS 615 Software Project Management Mid All quizzes and papers is the technical kernel of software engineering. Design Implementation Requirements analysis Testing These all are outputs of Initiating Process except Project Manager Assignments Constraints Selection Criteria Assumptions Project management processes can be organized into groups Four Five Six Seven Product quality depends on its conformance to Software requirements Development standards Implicit requirements All of given Finally, the specification includes a Bibliography Appendix Both Bibliography and Appendix Reference Cognitive model describes a system as perceived by its User community Developer Top level management Manager P a g e 26

27 Project management is a of constant communication and negotiation. Process Concept Practice None of given is a software engineering task that bridges the gap between system level requirements engineering and software design. Cost Analysis Design analysis Risk analysis Requirements analysis The VP of marketing approaches you and requests that you change the visitor logon screen on the company's website to include a username with at least six characters. This is considered: 1. Project initiation 2. Ongoing operations 3. A project 4. Project execution Your company manufactures small kitchen appliances. They are introducing a new product line of appliances in designer colors with distinctive features for kitchens in small spaces. These new products will be offered indefinitely starting with the spring catalog release. Which of the following is true? 1. This is a project because this new product line has never been manufactured and sold by this company before. 2. This is an ongoing operation because the company is in the business of manufacturing kitchen appliances. Introducing designer colors and features is simply a new twist on an existing process. 3. This is an ongoing operation because the new product line will be sold indefinitely. It's not temporary. 4. This is not a project or an ongoing operation. This is a new product introduction not affecting ongoing operations. Your company manufactures small kitchen appliances. They are introducing a new product line of appliances in designer colors with distinctive features for kitchens in small spaces. These new products will be offered indefinitely starting with the spring catalog release. In order to determine the characteristics and features of the new product line, you will have to perform which of the following? 1. Fast tracking P a g e 27

28 2. Consulting with the stakeholders 3. Planning the project life cycle 4. Progressive elaboration Progressive elaboration is the process of determining the characteristics and features of the product of the project. Progressive elaboration is carried out in steps in detailed fashion. A project is considered successful when: 1. The product of the project has been manufactured. 2. The project sponsor announces the completion of the project. 3. The product of the project is turned over to the operations area to handle the ongoing aspects of the project. 4. The project meets or exceeds the expectations of the stakeholders. A project is considered successful when stakeholder needs and expectations are met or exceeded. 6. The VP of customer service has expressed concern over a project you're involved in. His specific concern is that if the project is implemented as planned, he'll have to purchase additional equipment to staff his customer service center. The cost is substantial and was not taken into consideration in the project budget. The project sponsor insists that the project must go forward as originally planned or the customer will suffer. Which of the following is true? 1. The VP of customer service is correct. Since the cost was not taken into account at the beginning of the project, the project should not go forward as planned. Project initiation should be revisited to examine the project plan and determine how changes can be made to accommodate customer service. 2. The conflict should be resolved in favor of the customer. 3. The conflict should be resolved in favor of the project sponsor. 4. The conflict should be resolved in favor of the VP of customer 5. service. Conflicts between stakeholders should always be resolved in favor of the customer. This question emphasizes the importance of identifying your stakeholders and their needs as early as possible in the project. 7. Which of the following brings together a set of tools and techniques used to describe, organize, and monitor the work of project activities? 1. Project managers 2. Guide to the PMBOK P a g e 28

29 3. Project management 4. Stakeholders Project management brings together a set of tools and techniques to organize project activities. Project managers are the ones responsible for managing the project processes. 8. What are the triple constraints? 1. Time, schedules, and quality 2. Time, availability, and quality 3. Time, money, and schedules 4. Time, money, and quality The triple constraints that drive all projects are time, money, and quality. 9. You are the project manager for a large construction project. The project objective is to construct a set of outbuildings to house the Olympic support team that will be arriving in your city 18 months from the project start date. You've been given a budget of $12 million to complete this project. Resources are easily attained. Which of the triple constraints is the primary constraint for this project? 1. Time, because the date cannot be moved 2. Money, because the budget is set at $12 million 3. Resources, because they're not fixed 4. Quality, because the buildings have to be functional and safe The primary constraint on this project is time because the date absolutely cannot move. The Olympics are scheduled to begin on a certain date, and this can't be changed. The budget is also a constraint because it's set at $12 million, but in this example, it would be a secondary constraint. It's important that the project manager understands the priority of the constraints and manages to them. You are the project manager for a large construction project. The project objective is to construct a set of outbuildings to house the Olympic support team that will be arriving in your city 18 months from the project start date. Resources are not readily available as they are currently assigned to other projects. Jack, an expert crane operator, is needed for this project two months from today. Which of the following skills will you use to get Jack assigned to your project? A. Negotiation and influencing skills B. Communication and organizational skills P a g e 29

30 C. Communication skills D. Problem-solving skills Negotiation and influencing skills are needed to convince Jack's boss and come to agreement concerning his assignment. You are a project manager with technical expertise in the pharmaceutical industry. You've decided to try your hand at project management in the entertainment industry. Which of the following is true? 1. You will likely be successful because communication skills are your strong suit. You anticipate having technical experts on your project team to address industry specifics that you're not familiar with. 2. You will likely be successful because your organizational skills are excellent. You anticipate having technical experts on your project team to address industry specifics that you're not familiar with. 3. You will probably be successful because you have a friend in the entertainment industry that has briefed you on all the important aspects of this project that you'll need to know. You anticipate having technical experts on your project team to address industry specifics that you're not familiar with. 4. You will probably not be successful because you have little knowledge of the entertainment industry even though you anticipate having technical experts on your project team to address industry specifics that you're not familiar with. Project management processes span industries. A project manager can take these skills across industries and apply them successfully. Technical experience in the industry doesn't hurt, but it's not required. The most important skill any project manager can have is communication skills. Poor communication skills might lead to an unsuccessful conclusion no matter how strong the project manager's other skills are. You are managing a project to install a new postage software system that will automatically print labels and administer postage for certified mailings, overnight packages, and other special mailing needs. You've attempted to gain the cooperation of the business analyst working on this project and need some answers. She is elusive and tells you that this project is not her top priority. To avoid situations like this in the future, you should: 1. Establish the business analyst's duties well ahead of due dates and tell her you'll be reporting on her performance to her functional manager. P a g e 31

31 2. Establish the business analyst's duties well ahead of due dates and tell her you are expecting her to meet these expectations because the customer is counting on the project meeting due dates to save significant costs on their annual mailings. 3. Negotiate with the business analyst's functional manager during the planning process to establish expectations and request to participate in the business analyst's annual performance review. 4. Negotiate with the business analyst's functional manager during the planning process to establish expectations and inform the functional manager of the requirements of the project. Agreement from the functional manager will assure the cooperation of the business analyst. Negotiate with the functional manager to participate in the business analyst's annual performance review. The amount of authority a project manager possesses can be related to: 1. The project manager's communication skills 2. The organizational structure 3. The amount of authority the manager of the project managerpossesses 4. The project manager's influencing skills The level of authority the project manager has is determined by the organizational structure. For instance, in a functional organization, the project manager has little to no authority, but in a projectized structure, the project manager has full authority. What is one of the advantages of a functional structure? 1. All employees report to one manager and have a clear chain of command. 2. All employees report to two or more managers, but project team members show loyalty to functional managers. 3. The organization is focused on projects and project work. 4. Teams are collocated. An advantage for employees in a functional organization is that they have only one supervisor and a clear chain of command exists. You have been assigned to a project in which the objectives are to direct customer calls to an Interactive Voice Response system before being connected to a live agent. You are in charge of the media communications for this project. You report to the project manager in charge of this project and the VP of marketing, who share responsibility for this project. Which organizational structure do you work in? P a g e 31

32 1. Functional organization 2. Weak matrix organization 3. Projectized organization 4. Balanced matrix organization Employees in a balanced matrix often report to two or more managers. Functional managers and project managers share authority and responsibility for projects. There is a balance of power between the functional managers and project managers. You have been assigned to a project in which the objectives are to expand three miles of the north-south highway through your city by two lanes in each direction. You are in charge of the demolition phase of this project, and you report to the project manager in charge of this project. You have been hired on contract and will be released at the completion of the demolition phase. What type of organizational structure does this represent? 1. Functional organization 2. Weak matrix organization 3. Projectized organization 4. Balanced matrix organization Projectized organizations are focused on the project itself. One issue with this type of structure is determining what to do with project team members when they are not actively involved on the project. One alternative is to release them when they are no longer needed. What are the five project management process groups, in order? 1. Initiation, Executing, Planning, Controlling, and Closing 2. Initiation, Controlling, Planning, Executing, and Closing 3. Initiation, Planning, Controlling, Executing, and Closing 4. Initiation, Planning, Executing, Controlling, and Closing Remember the acronym that sounds like syrup of ipecac: IPECC. You have been assigned to a project in which the objectives are to expand three miles of the north-south highway through your city by two lanes in each direction. You are interested in implementing a new project process called design-build in order to speed up the project schedule. The idea is that the construction team will work on the first mile of the highway reconstruction at the same time the design team is coming up with plans for the third mile of the reconstruction rather than completing all design before any construction begins. This is an example of: 1. Managing the projects as a program 2. Fast tracking 3. Progressive elaboration P a g e 32

33 4. Collocation Fast tracking is starting a new phase before the phase you're working on is completed. This compresses the project schedule, and the project is completed sooner as a result. During which project management process are risk and stakeholder's ability to influence project outcomes the highest at the beginning of the process? 1. Planning 2. Executing 3. Initiation 4. Controlling The Initiation process is where stakeholders have the greatest ability to influence outcomes of the project. Risk is highest during this stage because of the high degree of unknown factors. You are a project manager working on gathering requirements and establishing estimates for the project. Which process group are you in? 1. Planning 2. Executing 3. Initiation 4. Controlling The Planning process is where requirements are fleshed out, stakeholders are identified, and estimates on project costs and time are made. Basit is the project manager working on the Resource Planning process. He should consider all of the following when developing the resource requirements output except: 1. WBS 2. Supply purchase policies 3. Resource rates 4. Special knowledge and talents All of the following are true regarding the tools and techniques of activity sequencing except: 1. GERT uses analogous methods 2. GERT allows for loops 3. GERT is a conditional diagramming method 4. GERT allows for conditional branches P a g e 33

34 Pervaiz Elahi is a project manager for Changing Tides Video games. He has produced a project network diagram and has updated the activity list. Which process have he just finished? 1. The Activity Sequencing process, which identifies all the specific activities of the project 2. The Activity Sequencing process, which identifies all the activities dependences 3. The activity duration Estimating process, which diagram project network time estimates 4. The activity duration Estimating process, which identifies all the dependent activities of the project 4. Pervaiz Elahi is a project manager for Changing Tides Video games. He has gathered the inputs of for the Activity Duration Estimation process. He will employ which tools and techniques to produce the outputs for this process? 1. Activity list, analogous estimating, quality based durations, and alternatives identification 2. Activity list, analogous estimating, expert judgment, and quality based durations 3. Expert judgment, analogous estimating, quality based durations, and reserve time 4. Expert judgment, alternative identification, quality based durations, and reserve time 5. As a project manager, you know that all of the following are true concerning analogous estimating techniques except: 1. It s a qualitatively based estimating technique 2. It s a Top-down estimating technique 3. It s a tool and technique of Activity Duration Estimating and Cost Estimating 4. It s a form of expert judgment. 6. All of the following are true regarding parametric modeling except: 1. It s a form of Top-down estimating 2. It s a mathematical model 3. It s a tool used to estimate project costs 4. It s a tool used to estimate project time 7. Which logical relationship does the PDM use most often? 1. Start to finish 2. Start to start 3. Finish to finish 4. Finish to start P a g e 34

35 8. One of the most powerful leadership tools a project manager is has his/her 1. Own knowledge 2. Own experience 3. Own behavior 4. Own reference 9. The organization structure that provides the project manager with the most authority over the project team is: 1. Functional 2. Balanced matrix 3. Strong matrix 4. Projectized 10. Using an EFFORT RATIO for each type of change in 1. Fuzzy logic sizing 2. Function point sizing 3. Changing sizing 4. Standard component sizing 11. What is one of the problems with project management software? 1. The project manager manages the software instead of the project 2. Project duration calculations are sometimes approximate 3. You cannot override the project management software decisions regarding schedule 4. It s expensive and difficult to use 13. If you know expected value is 500 and the standard deviation is 12, you can ay with approximately a 95 percent confidence rating which of the following? 1. The activity will take between 488 and 512 days 2. The activity will take between 464 and 536 days 3. The activity will take between 494 and 506 days 4. The activity will take between 476 and 524 days 14. If your expected value is 110 and the standard deviation is 12, which of the following is true? 1. There is approximately a 99 percent chance of completing this activity between 86 and 134 days P a g e 35

36 2. There is approximately a 68 percent chance of completing this activity between 98 and 122 days 3. There is approximately a 95 percent chance of completing this activity between 98 and 122 days 4. There is approximately a 75 percent chance of completing this activity between 86 and 134 days 16. All of the following strategies are tools and techniques of Risk Response Planning used to reduce or control risk except? 1. Mitigation 2. Simulation 3. Avoidance 4. Acceptance 17. Object points are measurable code sections in an object-oriented programming language, such as 1. C++ 2. Ada 3. Java 4. All of the given 18. involves determining what qualities are to be used to perform project activities. 1. Resource planning 2. Cost estimating 3. Cost budgeting 4. Cost control 19. The resources assigned to them will significantly influences the duration of most activities. 1. True 2. False 20. Using the intermediate COCOMO technique effort is calculated in 1. Two-step process 2. Three-step process 3. Four-step process 4. Five-step Process P a g e 36

37 1. Which of the following is true regarding NPV? 1. NPV assumes reinvestment at the cost of capital 2. NPV decisions should be made based on the highest value for all of the selections 3. NPV assumes reinvestment at the prevailing rate 4. NPV assumes reinvestment at the NPV rate 2. Hasnain is a project manager for VU International. Since he doesn t sleep much, he get a lot of project work done. He is considering recommending a project that cost s Rs , and expected inflows are Rs per quarter for the first 2 years, then Rs per quarter thereafter. What is the pay back period? months months months months 3. Mathematical models using linear, dynamic, integer, or algorithm models are considered: 1. Project selection criteria 2. A form of expert judgment 3. Project selection methods 4. A form of historical information 4. WBS Is Not: 1. The WBS should contains 100% of the work defined by the scope or contract 2. Development of WBS should involve the entire project team 3. A listing of tasks or activities 4. Should captures all deliverables (Internal, External, Interim) in terms of work to be completed. 5. COMSAT project selection committee used a weighted scoring model and found that project BAT, with a score of 54, should be chosen over the other competing projects. Which of the following is true? 1. Weighted scoring models are a benefit measurement method, which is tool and technique in the Initiation process 2. Weighted scoring models are constraint optimization method, which is output of the Initiation process 3. Weighted scoring models are constraint optimization method, which is tool and technique in the Initiation process P a g e 37

38 4. Weighted scoring models are a benefit measurement method, which is output of the Initiation process. Obtaining forma project plan approval and sign-off is important for all of the following reason except: 1. Stakeholders are aware of the specific details regarding project schedule, budgets, and risk 2. Stakeholders will be more likely to cooperate 3. Stakeholders are aware of the project details, which makes them more likely to participate in future project decisions 4. Stakeholders are able to recommend a project planning methodology to follow throughout the remaining process group All of the following are true regarding the project plan except: 1. Some of its input and outputs from other planning processes 2. It s used to guide the project Executing and Controlling processes and it is the baseline used to measure project performance 3. It consists of one document that should be formally approved and signed by stakeholder 4. It contains things like the WBS, project schedule, and resource assignment An activities list is typically shown in this ways. 1. It can be shown as an outline 2. It can be shown as an outline or it can be graphically presented 3. It can be graphically presented 4. None of the given Always remember that projects are in dynamic working environments, so try to maintain flexibility in the work breakdown structure. 1. Always true 2. Always false 3. Sometimes true sometimes false 4. Depends on condition To create a schedule, you can use project management tools; 1. Gantt charts 2. Network-scheduling techniques 3. PERT 4. All of given P a g e 38

39 Usman is project manager for a new website for a local zoo. He needs to perform Quantitative Risk Analysis. He will use all of the following tools and techniques to accomplish this except: 1. Overall risk ranking for the project 2. List of prioritized risk 3. Inputs to other processes 4. List of risks for additional analysis and management 12. Which of the following describes the cost of quality associated with scrapping, rework, and downtime? 1. Internal failure 2. External failure 3. Prevention cost 4. Appraisal cost 13. Choudhary & Brothers hardware vendor left you voic saying that a snowstorm in the Midwest will prevent your equipment from arriving on time. You identified a risk response for this risk and have arranged for a local company to lease you the needed equipment until yours arrives. This is an example of which risk response strategy? 1. Transference 2. Acceptance 3. Mitigation 4. Avoidance 14. What document outlines the action steps to be taken if an identified risk event should occur? 1. Project plan 2. Corrective action Plan 3. Contingency Plan 4. Risk response plan 15. Tools and techniques for risk identification include all but: 1. Checklist 2. Risk assessment 3. Interviewing P a g e 39

40 4. Assumption analysis 16. Tools and techniques for Performance reporting are: 1. Performance review 2. Variance analysis 3. Trend analysis 4. All of the given 17. Analogous estimating is a form of 1. Expert Judgment 2. Bottom up estimating 3. Delphi method 4. Computerized estimating 18. is another term for top down estimating. 1. Life cycle costing 2. Parametric modeling 3. Analogous estimating 4. Work package 19. Assumptions generally involve: 1. A degree of risk 2. Financial control 3. Historical information 4. Lesson learned 20. Receivers in the communications model filter their information through all of the following except: 1. Culture 2. Knowledge of subject 3. Conflict 4. Language 1- The presence of which of the given factors is mandatory in a quality assured software 1. Change adaptive P a g e 41

41 2. Faulty 3. Correctness 4. Both Change adaptive and Correctness 2- Which of the following testing technique is followed to ensure that the software user requirements are being met? 1. White box 2. Gray box 3. Blue box 4. Black box 3- Which of the following testing techniques is usually used during implementation of individual modules? 1. White Box 2. Black Box 3. Integration testing 4. None of given How do the dynamic testers confirm that the executions of a program (other than the expected execution of a program) are running accurately? 1. Some important program input are selected from the set of all and executed 2. It is hard to confirm that 3. The execution of the program other that the intended execution is useless to test 4. None of given The execution of a program is tested by a model based approach in-case of 1. Formal testing 2. Dynamic testing 3. Static testing 4. Un What is the difference between formal methods and testing? 1. Formal methods aim at verification and proving correctness, while testing can only show the presence of errors. 2. Testing is done only in the third phase of SDLC whereas Formal methods are done in all the phases of SDLC except Testing phase 3. There is no big difference between the both P a g e 41

42 4. Testing can only be done after the requirements gathering phase of SDLC whereas Formal methods can be applied before that. The schedule provides in Project management process answers to two basic planning questions, these are. 1. What, When 2. How, When 3. What, How 4. Why, When SDP Stands for. 1. Software Development Plan 2. Software Design Plan 3. Software Demanding Plan 4. Software Defining Phase Application of techniques helps the software designer to achieve high quality specification. 1. Quality Management 2. Software engineering 3. Formal Technical Reviews 4. None of the given The main idea behind symbolic execution is to use symbolic values, instead of actual data, as input values, and to represent the values of program variables as symbolic expressions. 1. True 2. False 8- The purpose of mutation testing is 1. to help the tester develop effective tests or 2. to locate weaknesses in the test data used for the program never accessed during execution 3. to locate weaknesses in the test data used in sections of the code that are seldom accessed during execution 4. All of given 9- Which of the following is the example of mutation operators? P a g e 42

43 1. Replace each boolean sub expression with true and false. 2. Replace each arithmetic operation with another one, e.g. + with *, - and /. 3. Replace each boolean relation with another one, e.g. > with >=, == and <=. 4. All of given 10- Which of the following testing approach is used to test the software functionality that previously worked as desired, stops working or no longer works in the same way that was previously planned? 1. Integration testing 2. Unit testing 3. Regression testing 4. Dynamic testing 11- Which of the following can be a type of regression? 1. Local - changes introduce new bugs. 2. Unmasked - changes unmask previously existing bugs. 3. New feature regression 4. All of given 12- Which of the following testing is required when it needs to test the software after combining the modules into a group? 1. Unit 2. Regression 3. White box 4. Integration 13- SQA encompasses the entire software development process 1. True 2. False 14- The process of software quality assurance (SQA) is designed to prevent software defects and inefficiencies 1. True 2. False 15- There is no difference between software quality assurance and software testing 1. True 2. False managing the relationship with the seller. P a g e 43

44 1. Source Selection 2. None of the given 3. Contract Closeout 4. Contract Administration is the ability to encourage by "push or pull" technical people to produce to their best ability. 1. Evaluating 2. Motivation 3. None of the given 4. Monitoring Motivation: The ability to encourage (by "push or pull") technical people to produce to their best ability. Unproductive work environment is a 1. Technology-related problems 2. Process-related problems 3. People-related problems 4. Product-related problems Unproductive work environment: The work environment is a major factor that affects the productivity of the development team. For example, a noisy or cramped workspace decreases the motivation levels of the employees. Similarly, unfriendly organizational policies also lower the motivation of the team members. As the project manager, you need to ensure that the team is protected from harmful external make the workspace friendly to work in. People-related problems are Low motivation Problem employees Unproductive work environment Inefficient project management style: Lack of stakeholder interest Ineffective project sponsorship by management Most software project manager s practice a lot of management techniques that are of doubtful authenticity are called P a g e 44

45 1. Project management tools 2. Project management myths 3. Project management thumb rules 4. Project management fundamentals Project Management Myths In most cases, you learn the skills required to manage a software project while on the job. As a result, most software project managers practice a lot of management techniques that are of doubtful authenticity. Many software project managers learn about the so-called management skills and concepts that are actually myths. We can classify the problems that affect software projects into categories You can classify the problems that affect software projects into the following four categories: People-related problems Process-related problems Product-related problems Technology-related problems Technology-related problems include 1. Overestimated savings from reusable components and new tools and methods 2. Switching tools in mid way 3. Integrating different software products in cross-platform implementation 4. All of given McCall (MCC77) and his colleagues proposed some software quality factors based on most important aspects of a software product: 1. Product operation 2. Product revision and 3. Product transition 4. All of the given P a g e 45

46 Synchronization control helps to ensure that parallel changes performed by two different people do. 1. Not overwrite one another 2. Overwrite one another 3. May overwrite one another 4. None of given The code generation step performs the task 1. Translated specification into a machine-readable form 2. Translated design into a machine-readable form 3. Translated requirements into a machine-readable form 4. Translated user data into a machine-readable form Before requirements can be analyzed, modeled, or specified they must be gathered through a/an 1. Elicitation process 2. Interviewing 3. Meeting 4. None of given The quality of software is said to be high if it meets the 1. Standards, defined for the product 2. Procedures, defined for the product 3. Standards and procedures, defined for the product 4. Design defined for product The British Standards Institution (1986) has stated the quality as 1. The ability of a software product to satisfy its specified requirements 2. "An inherent or distinguishing characteristic or a property" 3. Quality is in the eye of the beholder, a matter, of the client's judgment. 4. All of the given The distinguishing characteristics of a software product are the cyclomatic complexity, cohesion, function points, and lines of code. These characteristics of a software product define the quality of the product. P a g e 46

47 The US DOD (1988) defines software quality rather simply as: The ability of a software product to satisfy its specified requirements. The British Standards Institution (1986) has stated that: Quality is in the eye of the beholder, a matter, of the client's judgment. A baseline version 1. Have a short life 2. Can be assigned version numbers Tested and certified version of a system 4. Survive only during bug fixing You can use the Item Traceability Matrix to identify at the end of each phase 1. SCIs 2. SCM 3. Design 4. Construction You can use the Item Traceability Matrix to identify SCIs at the end of each phase Software requirements engineering is a process of all except 1. Discovery 2. Refinement 3. Design 4. Specification Software requirements engineering is a process of discovery, refinement, modeling and specification. The Introduction of the software requirements specification states the 1. Goals 2. Objective 3. Design 4. Goals and objectives of the software Efficiency with which a program runs on different platforms or operating systems is Reusability 1. True P a g e 47

48 2. False Portability Efficiency with which a program runs on different platforms or operating systems Reusability Extent to which the program can be used in more than one program or system (P# 121 ) Efficiency with which a program runs on different platforms or operating systems is called Configurability 2. Reusability 3. Interoperability 4. portability Which of the items listed below is not one of the software engineering layers? 1. Process 2. Manufacturing 3. Methods 4. Tools Software engineering layers, Process, A quality focus, Method, Tools Discrete portions of the project that can be charged to a single organization are called Work packages 2. Deliverables 3. Tasks 4. Activities Work packages are: Discrete portions of the project that can be charged to a single organization The first step in project planning is to Determine the budget 2. Select a team organizational model 3. Determine the project constraints P a g e 48

49 4. Establish the objectives and scope The software quality assurance activity which is performed to check errors in logic, function, or implementation for any representation of the software is called : 1. Inspection 2. Formal technical review(s) 3. Walkthrough 4. Auditing Formal Technical Reviews One of the most common, yet important, software quality assurance activity performed is FTR. This activity is performed to check errors in logic, function, or implementation for any representation of the software. (P# 126) All of the following are types of project closures or endings except: 1. Addition 2. Integration 3. Verification 4. Extiction 4 Formal types of project ending: - Addition - Starvation - Integration - Extinction Ineffective project sponsorship by management is a 1. Technology-related problems 2. Process-related problems 3. People-related problems 4. Product-related problems People-related problems are Low motivation Problem employees Unproductive work environment Inefficient project management style: Lack of stakeholder interest Ineffective project sponsorship by management During the Implementation phase the software modules are coded and initial unit tests are performed. P a g e 49

50 1. True.? 2. False Which one the following components are purchased from a third party, are ready for use on the current project and have been fully validated? 1. Software 2. Off the shelf 3. Hardware 4. Microsoft Off-the-shelf components: Existing software that can be acquired from a third party or that has been developed internally for a past project. COTS (commercial off-the-shelf) components are purchased from a third party, are ready for use on the current project, and have been fully validated refers to the quantifiable outcome of the software project. 1. Schedule 2. Effort 3. Size 4. Resource Function Points are language dependent approach to estimating software development effort. 1. True 2. False Adding more people to a project that is already behind schedule is a good way to catch up. 1. True 2. False The decomposition of a software project is a division of the system into its operational components as they are seen by the user. P a g e 51

51 1. Design 2. Functional 3. Project 4. planning Ease with which a program is tested is called Flexibility 2. Testability 3. Maintainability 4. Reusability Cost, effort, risks, and resources are the factors included in Estimation 2. Testing 3. Development 4. Maintenance The software quality assurance activity which is performed to check errors in logic, function, or implementation for any representation of the software is called : 1. Inspection 2. Formal technical review(s) 3. Walkthrough 4. Auditing Extent to which the program can be used in more than one program or system is called Portability 2. Reusability 3. Interoperability 4. Configurability P a g e 51

52 The requirements phase precedes the design phase 1. True 2. False Software engineers do not need to consider hardware when designing a computerbased system 1. True 2. False The model serves as the basis for the creation of for the Software. 1. Design 2. Maintenance 3. Testing 4. Specifications Throughout evaluation and solution synthesis, the analyst's primary focus is on 1. "What, not "how." 2. Model 3. Evaluation and Synthesis 4. Specification A software project that meets all the stated objectives is a success of 1. Project quality 2. Project fundamental purpose 3. Project management myth.??? 4. Project requirement Mode of specification has a great impact on quality of solution. Forcing SWE to work with incomplete, inconsistence, or misleading specifications result in frustration and confusion affecting: Quality Timeliness and Completeness of SW product All of given P a g e 52

53 Mode of specification has a great impact on quality of solution. Forcing SWE to work with incomplete, inconsistence, or misleading specifications result in frustration and confusion affecting: Quality Timeliness and Completeness of SW product The overall role of Software in a larger system is identified during 1. Requirements engineering 2. Process engineering 3. System engineering 4. All of given Upon evaluating current problems and desired information (input and output), the analyst begins to 1. Synthesize solutions 2. Model 3. Specification 4. All of given A facilitator controls the meeting can be 1. Customer 2. A developer 3. An outsider 4. All of given Version control combines to manage different versions of configuration objects that are created during software product development. 1. Procedure 2. Tools 3. Procedure and Tools 4. None of given P a g e 53

54 Once the review is complete, the Software Requirements Specification is "signed-off by 1. Developer 2. Customer 3. Top level Management 4. Both Customer and Developer. REF:: Once the review is complete, the Software Requirements Specification is "signed- off by both the customer and the developer. Controlling Versions is activity of 1. Construction 2. Testing 3. SCM..software configuration management 4. Design ensures that the standards laid down for a project are followed. 1. Quality assurance 2. Quality control 3. Product evaluation 4. Process control ensures that appropriate steps to follow the product development procedures are carried out 1. Quality Management 2. Design 3. Process monitoring 4. Quality Control During project, you identify the resources required and allocate them to the software project. 1. Development 2. Initiation 3. Scope P a g e 54

55 4. planning Which of the following task is not part of product Implementation activities. 1. Implementation plan creation 2. Scope determination 3. Support Plan Creation 4. User Acceptance Plan Like all engineering disciplines, requirements engineering is not conducted in a 1. Sporadic random 2. Otherwise haphazard fashion 3. But instead is the systematic use of proven approaches? 4. All of given defines the duration of implementation and the hard and software perquisites for implementing the software product. 1. Training plan creation 2. User acceptance plan 3. Implementation plan creation 4. Support plan creation Implementation of software quality often associated with 1. Project Manager 2. Software developer 3. Customer 4. User Research-oriented software development is a 1. Technology-related problems 2. Process-related problems 3. People-related problems 4. Product-related problems P a g e 55

56 Defined scope is a 1. Technology-related problems 2. Product-related problems 3. Process-related problems 4. People-related problems The primary focus of is to ensure that the final software product offers all the functionality and performance that the customer wanted. 1. Training test 2. User acceptance test 3. Implementation test 4. Support test The primary focus of user acceptance test is to ensure that the final software product offers all the functionality and performance that the customer wanted. Therefore, the customer tests the software product for issues such as aesthetics, user friendless, and scalability. These all are process-related problems in a software project except 1. Insufficient identification 2. Unsuitable life cycle model selection 3. Abandoning quality under pressure of deadlines 4. Structured and hurried software development Software design is actually a multi step process that focuses on distinct attributes of a program When you build a product or system, it's important to go through a series of predictable steps a road map that helps you create a timely, high-quality result, The road map that you follow is called a 1. Software design 2. Software Process 3. Software schedule 4. Framework P a g e 56

57 PMIS Stands for. 1. Process Management Inter System 2. Project Management Information System 3. Program Maintenance Interior System 4. Personal Matters Information System These all are Product Revision Factors except 1. Usability 2. Maintainability 3. Flexibility 4. Testability To control versions, you can use 1. Version Control File 2. Version Control Register 3. Version Control authority 4. All of given is an umbrella activity that ensures conformance to standards and procedures throughout the SDLC of a software product. 1. SQA 2. Design 3. Testing 4. All of given The design decomposition of a software system is a division of the system that coincide with the actual software components of the system. 1. Operational components 2. High level components 3. Low level components 4. High level components and Low level components P a g e 57

58 All of the following are benefits of meeting quality requirements except 1. An increase in stakeholder satisfaction 2. Less rework 3. Low turnover 4. Higher productivity The Preliminary Users Manual presents the software as a black box: That is, heavy emphasis is placed on 1. User input 2. User output 3. User input and the resultant output 4. None of given The in project management process focuses on Change associated with error correction, adaptations required as the software's enviornment evolves, and changes due to enhancements which brought about by changing customer requirements. 1. Analysis Phase 2. Definition Phase 3. Support Phase 4. Development Phase An output from the quality planning process is 1. Process adjustment 2. Acceptance decision 3. Quality improvements 4. Quality management plan Which of the following might require re-baselining of the cost baseline? 1. Corrective action 2. Revised cost estimates 3. Updates to the cost management plan 4. Budget updates identify which quality standards are relevant to the project and determines how to satisfy them P a g e 58

59 1. Quality planning 2. Quality assurance 3. Quality control 4. Process control Many software projects digress from the original scope because of the nature of the software product or technology used, it s happen in 1. Product scope changed toward the end of the project life cycle 2. Research-oriented software development 3. Defined scope 4. Fuzzy users Reviews conducted at each of this phase/s 1. Analysis 2. Design 3. Coding 4. All of givenwww.vuzs.net Describe where the work must be performed. Specify the location of hardware and software and where the people must perform the work is called 1. Scope of work 2. Location of Work 3. Period of Performance 4. Deliverables Schedule Location of Work: Describe where the work must be performed. Specify the location of hardware and software and where the people must perform the work. Effective project managers 1. Lead by example 2. Are visionary 3. Are good motivators, communicators, supports team members and stand up to 4. upper management where necessary? 5. All of given The distinguishing characteristics of a software product are. 1. Cyclomatic complexity and cohesion 2. Function points and lines of code P a g e 59

60 3. all of the given 4. None of given The distinguishing characteristics of a software product are the cyclomatic complexity, cohesion, function points, and lines of Insufficient identification is a 1. Technology-related problems 2. Process-related problems 3. People-related problems 4. Product-related problems Insufficient identification: Unidentified, partially identified, and unplanned risks pose a threat to the success of a software project. You need to intensively identify risks and evolve a risk management plan such that the project is completed successfully, on time. of the system is an effort to better understand data and control flow, functional processing, operational behavior, and information content 1. Specifications 2. Design 3. Model 4. Evaluation and Synthesis During the evaluation and solution synthesis activity, the analyst creates models of the system in an effort to better understand data and control flow, functional processing, operational behavior, and information content. The model serves as a foundation for software design and as the basis for the creation of specifications for the Software. The customer may be unsure of precisely what is required. These all are Product Transition Factors except 1. Interoperability 2. Configurability 3. Expandability 4. Testability Inefficient project management style is a 1. Product-related problems 2. Technology-related problems 3. Process-related problems 4. People-related problems P a g e 61

61 Inefficient project management style: the project manager needs to lead by example. The team members absorb the work culture, work ethic, and attitude of the project manager and implement it in their work style. If you display a lack of leadership qualities and weak ideals, the motivation levels decrease across software team. Software design is actually a multi step process that focuses on distinct attributes of a program, these are 1. Data structure, and Software architecture 2. Interface representations, and procedural detail 3. Both of given 4. None of given Software design is actually a multi step process that focuses on four Distinct attributes of a program: Data structure, Software architecture, Interface representations, and procedural (algorithmic) detail. Software requirements analysis may be divided into areas of effort Software requirements analysis may be divided into five areas of effort: (1) Problem recognition, (2) Evaluation and synthesis, (3) Modeling (4) Specification, and (5) Review McCall (MCC77) and his colleagues proposed some software quality factors based on most important aspects of a software product: P a g e 61

62 There are a number of factors that determine the quality of a software product. These factors can be measured either directly or indirectly. McCall (MCC77) and his colleagues proposed some software quality factors based on three most important aspects of a software product: 1. Product operation 2. Product revision and 3. Product transition contains an analysis of what went wrong, what went right, and what you could have done better in the software project. 1. Prepare closedown report 2. Identify learning 3. Identify reusable software components 4. Create reference material: Prepare closedown report: The project closedown report contains the results of the causal analysis that you do for the project. This contains an analysis of what went wrong, what went right, and what you could have done better in the software project. contains an analysis of what went wrong, what went right, and what Project Quality Management includes the required to ensure that the project will satisfy the needs for which it was undertaken 1. Time 2. Cost 3. Processes 4. None of the given Project Quality Management includes the processes required to ensure that the project will satisfy the needs for which it was undertaken. It includes all activities of the overall management function that determine the quality policy, objectives, and responsibilities and implements them by means such as quality planning, quality assurance, quality control, and quality improvement, within the quality system. The check-in and checkout facilities provide 1. Best control 2. Best control 3. SCI control 4. Synchronization control P a g e 62

63 The check-in and checkout facilities provide synchronization control. Synchronization control helps to ensure that parallel changes Configuration control tools include 1. Automatic version control 2. Change control tools 3. Monitoring, auditing and registration support utilities 4. All of given correct The of project organization is based on the four cornerstones of management: delegation, authority, responsibility and supervision. 1. Strict structure 2. None of the given 3. Hierarchical structure 4. Network structure Unstructured and hurried software development is a 1. Technology-related problems 2. Product-related problems 3. Process-related problems correct 4. People-related problems Auditing is activity of 1. Construction 2. Design 3. SCM 4. Testing Strong leadership motivation may sound an obvious trait for a Leader 2. Manager 3. Specialist 4. None of the given P a g e 63

64 Strong leadership motivation may sound an obvious trait for a leader. After all, only those who want the weighty responsibilities and grueling pressures of leadership are likely to strive for it. identifying which quality standards are relevant to the project and determining how to satisfy them. 1. Quality Planning 2. Communications Planning 3. Organization Planning 4. Staff Acquisition All of the following describe the activity list except: It s an extension of the WBS It include all activities of the project.??? It describe the WBS update It include a description of project activities is path finding, is path following Leadership, Management Leader, Leadership Management, Leadership Manager, Management Leadership is path finding Management is path following Management is about doing things right Leadership is about doing the right things Software project is an activity that distributes estimated effort across the planned project duration by allocating the effort to specific software engineering tasks. 1. Scheduling 2. Cost estimation 3. Risk management 4. Both middle and later stage P a g e 64

65 A macroscopic schedule is developed at.. 1. Early stage 2. Middle stage 3. Later stage 4. Both middle and later stage A review of the Software Requirements Specification is conducted by Software developer Customer Both the software developer and the customer Top level management which of the following delays software projects, 1. Incorrect initial estimates 2. Technical difficulties 3. Human difficulties 4. Incorrect initial estimates, technical, human difficulties A meeting is conducted at a and attended by both software engineers and customers. Software engineer site Neutral site Customer site Company site In problem evaluation area of effort, once problems have been identified, the determines what information is to be produced by the new system and what data will be provided to the system. Analyst Designer Coder Manager Requirements are refined and analyzed to assess their clarity, completeness, and Correctness P a g e 65

66 Consistency Concurrency None of given Software project are carried out sequentially and that each phase is completed before the next is taken up. The Prototyping Model The Incremental Model The Waterfall model The Spiral model These all are design phase activities except Output Design Input Design The software test plan Software Selection The first activity in risk analysis is risk management. True False Both the software engineer and customer take an active role in software requirements engineering-a set of activities that is often referred to as Requirement Managing Recognition Analysis Modeling During the Implementation phase the software modules are coded and initial unit tests are performed. 1. True 2. False The final activity for a project manager is Project closedown Project implementation Project execution P a g e 66

67 Project Quality We can classify the problems that affect software projects into categories All given below are the problems that affect software projects except: Product-related problems Technology-related problems Procedure-related problems People-related problems completion and settlement of the contract, including resolution of any open items. Contract Administration Source Selection None of the given Contract Closeout Decisions also have a element to them the right decision may not be the best decision if it is made too early or too late. 1. Cost 2. Quality 3. Time 4. None of the given During the period of, you will find that software that was produced was generally over budgeted, under scheduled, and of poor quality. 1. Software crises 2. Software Development 3. Tracking 4. Quality Assurance of production volume usually comes from of the producers %, 20% 2. 20%, 80% 3. 40%, 60% 4. 60%, 40% P a g e 67

68 interact with the software, once it is released for production use. 1. Customer 2. Team Leads 3. End user 4. Project manager Scheduling for software engineering projects can be viewed from Two_. rather different perspectives. ================ subjective questions December 9, 2012 at 8:57pm Quality Function Deployment (5) A quality management technique that translates needs of customers into technical requirements of software. 1. Normal Requirement: meeting objectives & goals stated for a product or system during meeting 2. Expected Requirement: Implicit to products / system and may be so fundamental that customer does not explicitly state them 3. Exciting Requirement: Features beyond customer s expectation and prove to be very satisfying when present. 2. Formal Technical Review (5) Formal technical review (FTR) in conducted to assess the quality and design of the prototype. It is a meeting with the technical staff to discuss the quality requirements of a software product and its design quality. FTRs help in detecting errors at an early phase of development. This prevents errors from percolating down to the latter phases and resulting in rework. 4. Attributes of Software Design (2) Software design is actually a multi step process that focuses on four P a g e 68

69 Distinct attributes of a program: Data structure, Software architecture, Interface representations, and procedural (algorithmic) detail. 1.Explain the concept of Preliminary User Manual? (2marks) the Software Requirements Specification may be accompanied by an executable prototype (which in some cases may replace the specification), a paper prototype or a Preliminary User's Manual. The Preliminary Users Manual presents the software as a black box: That is, heavy emphasis is placed on user input and the resultant output. The manual can serve as a valuable tool for uncovering problems at the human/machine interface. List names of major design styles? (2marks) Major design styles 1. Object, 2. structured, 3. data-structured design What software development life cycle model has characteristics of waterfall model and prototype model? (2marks) Ans: Incremental and spiral models. Both combines the linear nature of the Waterfall model and the iterative nature of the Prototyping model. Define software processes and explain it. (3marks) When you build a product or system, it's important to go through a series of Predictable steps a road map that helps you create a timely, high-quality result, The road map that you follow is called a 'software process'. It provides stability, control, and organization to an activity that can, if left uncontrolled, become quite chaotic. Suppose you are working as a project manager in a software company. You are going to develop a software Examination system of VU. Mention methods for requirement elicitation you will use for software. (3marks) P a g e 69

70 6.What is meant by SMARTER? Explain in detail. (5marks) SMARTER is an acronym, that is, a word composed by joining letters from different words in a phrase or set of words. In this case, a SMARTER goal or objective is: Specific: For example, it's difficult to know what someone should be doing if they are to pursue the goal to "work harder". It's easier to recognize "Write a paper". Measurable: It's difficult to know what the scope of "Writing a paper" really is. It's easier to appreciate that effort if the goal is "Write a 30-page paper". Acceptable: If I'm to take responsibility for pursuit of a goal, the goal should be acceptable to me. For example, I'm not likely to follow the directions of someone telling me to write a 30-page paper when I also have to five other papers to write. Realistic: Even if I do accept responsibility to pursue a goal that is specific and measurable, the goal won't be useful to me or others if, for example, the goal is to "Write a 30-page paper in the next 10 seconds". Time frame: It may mean more to others if I commit to a realistic goal to "Write a 30-page paper in one week". However, it'll mean more to others (particularly if they are planning to help me or guide me to reach the goal) if I specify that I will write one page a day for 30 days, rather than including the possibility that I will write all 30 pages in last day of the 30-day period. Extending: The goal should stretch the performer's capabilities. For example, I might be more interested in writing a 30-page paper if the topic of the paper or the way that I write it will extend my capabilities. Rewarding: I'm more inclined to write the paper if the paper will contribute to an effort in such a way that I might be rewarded for my effort. The context free questions are mostly not related to requirements of the software P a g e 71

71 project and may be used for understanding process. How do content free questions elicitation help in basic understanding of the problem. (5marks) What are SCM activities; give example of SCI? (5) SCM is used to establish and maintain integrity of software items and ensure that they can be traced easily. Using SCM, you can define a library structure for storage and retrieval of software items. SCM needs to be performed at all phases in the SDLC of a software project. The various SCM activities are: 1. Identifying Objects 2. Controlling Versions 3. Controlling Changes 4. Auditing 5. Communicating Changes SCI(identifying software configurable) is an aggregation of software that is designated for configuration management. It is treated as a single entity in the configuration management process. For example: 1. design documents, 2. program code, 3. test case, and 4. custom requirement document are configurable items. List the inputs of initiation process? Inputs Product Description Strategic Plan Selection Criteria Initiating Process P a g e 71

72 Historical Information Outputs Project Charter Project Manager assignments Constraints Assumptions Tools and Techniques Project selection methods Expert judgment Software requirements analysis a bridge between system engineering and software design, show it by diagram. A bridge between system engineering and software design System engineering SW requirements and analysis SW design Question No: 23 ( Marks: 5 ) Write down the software process player s names and their roles in projects. The Players P a g e 72

73 The software process (and every software project) is populated by players who can be categorized into one of five constituencies: 1. Senior managers who define the business issues that often have significant influence on the project. 2. Project (technical) managers who must plan, motivate, organize, and control the practitioners who do software work. 3. Practitioners who deliver the technical skills that are necessary to engineer a product or application. 4. Customers who specify the requirements for the software to be engineered and other stakeholders who have a peripheral interest in the outcome. 5. End-users Elaborate the problem in project money fuzzy users which is product related (2) Fuzzy users: it is product related problem You also need to clarify the background characteristics of the users of the final software product at the beginning of the software project. If the description of the users is fuzzy, then the software analysis, design, and development stages may reflect the ambiguity with regard to the functions and performance of the final software product. 2) list the inputs of initiating process (2) Initiating Process Inputs Product Description Strategic Plan Selection Criteria Historical Information list the features of WBS? (2) Ans :First, it gives the management an idea about the size and complexity of the P a g e 73

74 project. Second, it helps in planning, scheduling, and monitoring a project realistically. This is possible because all the tasks in the project can be preformed measurable targets for each task. Difference between reactive & proactive risk management (5) Ans: A reactive strategy monitors the project for likely risks. Resources are set aside to deal with them, should they become actual problems. More commonly, the software team does nothing about risks until something goes wrong. Then, the team flies into action in an attempt to correct the problem rapidly. This is often called a fire fighting mode. When this fails, Crisis Management takes over, and the project is in real danger. A proactive strategy A considerably more intelligent strategy for risk management. It begins long before technical work is initiated. Potential risks are identified, their probability and impact are assessed and they are ranked by importance. Then, the software team establishes a plan for managing risk. The primary objective is to avoid risk, but because not all risks can be avoided, the team works to develop a contingency plan that will enable it to respond in a controlled and effective manner. Prepare simple risk analysis table?(5) Risk description Probability of occurrence (0-1) Impact on project (1-10) Risk factor (probability * impact) Spring may 2012 P a g e 74

75 Difference between scope planning and scope definition (2marks) P a g e 75 Scope Planning is developing a written scope statement as the basis for future project decisions while Scope Definition is subdividing the major project deliverables into smaller, more manageable components. Difference between baseline and interim version (5 marks) SCM differentiates between baselines and interim versions. A baseline is a tested and certified version of a system. Baselines can be assigned version numbers such as 1.0, 2.0, 3.0, and so on. A baseline usually undergoes intensive testing. Baselines are more visible with the marketing team and the vendors than the interim versions. Interim versions, It has version numbers, such as 1.1 or 1.2. The interim version is a temporary version. Interim versions have a short life and survive only during bug fixing, testing, or debugging. interim versions also have a unique version number or name. However, as part of SCM, all versions of changes are saved, clearly labeled, and archived. Archiving is the process of maintaining controlled copies of prior versions. Archiving helps in re-creating earlier versions in the event of data loss or data corruption. Who much group of project management process and list down the name (3marks) Project management processes can be organized into five groups of one or more processes each: 1. Initiating processes authorizing the project or phase 2. Planning processes defining and refining objectives and selecting the best of the alternative courses of action to attain the objectives that the project was undertaken to address

76 P a g e Executing processes coordinating people and other resources to carry out the plan 4. Controlling processes ensuring that project objectives are met by monitoring and measuring progress regularly to identify variances from plan so that corrective action can be taken when necessary 5. Closing processes formalizing acceptance of the project or phase and bringing it to an orderly end. Why we need item traceability matrix (2marks) We need the Item Traceability Matrix to identify SCIs at the end of each phase. To identify SCls, we need to first breakdown the project deliverable to the SCI level. As Each phase in the project has its own deliverables. So to trace the deliverables, to map the SCls to the phases in which they are delivered. Briefly discuss the review concept 1. Software review is an effective way of filtering errors in a software product. 2. Software review is used as a filter at various points of software development. 3. Reviews conducted at each of these phases, analysis, design, coding, and testing reveal areas of improvement in the product. 4. Reviews also indicate those areas that do not need any improvement. 5. You can use software reviews to achieve consistency and uniformity across products. Reviews also make the task of product creation more manageable. Some of the most common software review techniques, practiced across software organizations include: a) Inspection b) Walkthrough c) Formal technical reviews =========== MAKE THE FACILITY SOFTWARE MANAGEMENT SOFTWARE GRAPHICALLY 5 marks Situations ( as a software system manger how can you proceed and initiate the project life cycle 5 marks

77 A project has five phases. Here's a brief summary of each: Initiation Articulate your vision for the project, establish goals, assemble your team, and define expectations and the scope of your project. Planning Refine the scope, identify specific tasks and activities to be completed, and develop a schedule and budget. Executing Accomplish your goals by leading your team, solving problems, and building your project. Controlling Monitor changes to the project make corrections, adjust your schedule to respond to problems, or adjust your expectations and goals. Closing Deliver your project to your audience, acknowledge results, and assess its success. Take the time to compose a written evaluation of the project and the development effort. ============ Project Life Cycle includes the following Phases and activities: A. Concept Phase 1. User Need 2. Initial Investigation P a g e 77

78 3. User Review 4. System Performance Design 5. Candidate Review 6. Study Phase Report B. Requirements Phase 1. The software requirements specification document 2. The project development plan 3. The software test plan C. Design Phase 1. General System Review 2. Processing Requirements Identification 3. Data Base Design 4. Control Requirements 5. Output Design 6. Input Design 7. Software Selection 8. Equipment Selection/Acquisition 9. People 10. Reference Manual Identification 11. Plans 12. Design Specifications Preparation P a g e 78

79 13. Design Phase Report Preparation D. Development Phase 1. Implementation Planning 2. Computer Program Design 3. User Review 4. Equipment Acquisition and Installation 5. Coding and Debugging 6. Computer Program Testing 7. System Testing 8. Reference Manual Preparation 9. Personnel Training 10. Changeover Plan Preparation 11. Development Phase Report Preparation 12. User Acceptance Review E. Operation Phase 1. System Changeover 2. Routine Operation 3. System Performance Evaluation 4. System Changes/Enhancements Processes during closing of the software cycle? Closing processes is the formalizing acceptance of the project or phase and bringing it to an orderly end. P a g e 79

80 Each process is described by: Inputs Tools & Techniques Outputs Explain ESTIMATION? 2 Marks This helps in plan for resources and schedule the project. In a software project, unless you are sure that your estimation is accurate, you cannot make much progress. Estimation of factors is crucial such as 1. cost, 2. effort, 3. risks, and 4. resources. It gives you a fair idea of the size of the project. You can use the information about size to estimate the cost, effort, and duration of the project. Explain WBS? 2 Marks Work breakdown structure (WBS) is a technique to decompose the project for the purpose of management and control. It provides the framework for organizing and managing the work. It gives the management an idea about the size and complexity of the project. It helps in planning, scheduling, and monitoring a project realistically. Explain Quality Control 2 Marks Quality control involves the series of inspections, reviews, and tests used throughout the software process to ensure each work product meets the requirements placed upon it. Quality control includes a feedback loop to the process that created the work product. Quality control activities may be fully automated, entirely manual, or a combination of automated tools and human interaction. Risk management 2 Marks Project Risk management is the systematic process of identifying, analyzing, and responding to project risk. It includes maximizing the probability and P a g e 81

81 consequences of positive events and minimizing the probability and consequences of adverse events to project objectives. 1. Risk Management Planning deciding how to approach and plan the risk management activities for a project. 2. Risk Identification determining which risks might affect the project and documenting their characteristics. 3. Qualitative Risk Analysis performing a qualitative analysis of risks and conditions to prioritize their effects on project objectives. 4. Quantitative Risk Analysis measuring the probability and consequences of risks and estimating their implications for project objectives. 5. Risk Response Planning developing procedures and techniques to enhance opportunities and reduce threats to the project s objectives. 6. Risk Monitoring and Control monitoring residual risks, identifying new risks, executing risk reduction plans, and evaluating their effectiveness throughout the project life cycle. What is COCOMO? 3 Marks The COCOMO technique is popular estimation technique. Dr: Barry propounded this technique in COCOMO uses cost driver attributes to calculate the effort and duration of a project. The COCOMO technique has three levels of implementation. With each level, the complexity of the model increases. The levels of the COCOMO technique are: 1. Basic: estimates the effort and cost of a software project by using only the lines of code. 2. Intermediate: involves an additional step of calculating the effort adjustment factor (EAF). 3. Advanced: uses the steps of the intermediate COCOMO technique. In addition, it uses costs driver attributes assigned to each phase of the SDLC such as analysis and design. P a g e 81

82 Explain SLOC?3 Marks The SLOC technique is an objective method of estimating the size because there are no multiple ways of calculating the lines of code. Therefore, the effort estimate is close to being accurate. The SLOC technique is also used to directly calculate the effort to be spent on a project. It is defined as the source lines of code that are delivered as part of the product. The effort spent on creating the source lines of code is expressed in relation to thousand lines of code (KLOC). Define the disadvantages of the SLOC?...3 marks Disadvantages of SLOC: Despite being accurate in providing figures to calculate the effort required for a project, the SLOC technique has a drawback. The SLOC technique is language-dependent. The effort required to calculate source lines of code may not be the same for all languages. For example, to conceive and write 8 lines of code that accomplish a task in the assembly language may require 15 minutes. However, you may need only five minutes to complete the same lines of code if it is written in Visual Basic. Explain Project Scheduling? 3 Marks Software project scheduling is an activity that distributes estimated effort across the planned project duration by allocating the effort to specific software engineering tasks. Software project have a tendency to get out of control because of the multiple activities that need to be monitored, tracked, and controlled. What is Quality Assurance explain 5Marks SQA is the process of evaluating the quality of a product and enforcing adherence to software product standards and procedures. It is an umbrella activity that ensures conformance to standards and procedures throughout the SDLC of a software product. There are a large number of tasks involved in SQA activities. These include: P a g e 82

83 1. Formulating a quality management plan 2. Applying software engineering techniques 3. Conducting formal technical reviews 4. Applying a multi-tiered testing strategy 5. Enforcing process adherence 6. Controlling change 7. Measuring impact of change Performing SQA audits ix. Keeping records and reporting What is RISK PROJECTION 5Marks Risk projection, also called risk estimation, attempts to rate each risk in two ways-the likelihood or probability that the risk is real and the consequences of the problems associated with the risk, should it occur. The project planner, along with other managers and technical staff, performs four risk projection activities: (1) Establish a scale that reflects the perceived likelihood of a risk, (2) delineate the consequences of the risk, (3) Estimate the impact of the risk on the project and the product, and (4) Note the overall accuracy of the risk projection so that there will be no misunderstandings. WBS, what it contains?2marks It maps all contractual obligations (SOW) regarding deliverables 1. Details project objectives 2. Detailed enough to meet performance (measurable) objectives Contains built-in WBS and Project Plan review and update List down the tasks of Initializing process (2) 1. Requirement gathering: 2. Scope determination: 3. Resource allocation 4. Creating an initial project plan What is prototype (2) P a g e 83

84 Analysis should be conducted regardless of the SW engineering paradigm. It is possible to apply operational analysis principles and derive a model of SW from which a design can be developed. Requirement Elicitation (FAST, QFD etc) is conducted and a model is built, called Prototype. Name any six planning process tasks (3) Planning Process Tasks 1. Scope Planning 2. Scope Definition 3. Activity Definition 4. Activity Sequencing 5. Activity Duration Estimating 6. Resource Planning 7. Cost Estimating 8. Cost Budgeting Risk Planning 9. Schedule Development 10. Quality Planning 11. Communications Planning 12. Organization Planning 13. Staff Acquisition 14. Procurement Planning 15. Project Plan Development Discuss technology related problems in a software project (5) Overestimated savings from reusable components and new tools and methods: You can reuse software components in a software project to save time, effort, and cost of creating the component again. It is important that you assess the savings that the use of such a software component provides to a software project. This expectation of both the customer and the management might not be met, if you overestimate the savings from reusing software components. Switching tools in mid way: The current technology environment offers new tools and technologies for software development at a fast rate. All these tools and technologies offer the benefits of a shorter development cycle, lower costs, and under better functionality than earlier tools. You should identify and commit to the tool and technology for the software project before the project commences. Switching the tool or technology used during the software development stage causes the developers to relearn a new tool. In addition, there is a chance that it might not be possible to integrate the software already developed with the new tool. P a g e 84

85 Integrating different software products in cross-platform implementation: The modem software environment requires that all software should integrate with each other. However, many software projects do not plan for integration with existing software in the same or different domain. This limits the applicationofsu9h software and reduces the shelf life drastically. They key to the success of a software product is interoperability. The software project manager needs to determine the scope for the software product such that is can be integrated easily with existing software. 3) what are the people related problem on software project management Low motivation Problem employees Unproductive work environment Inefficient project management style Lack of stakeholder interest Ineffective project sponsorship by management Differentiate between the bibliography and appendix (5) The bibliography contains references to all documents that relate to the software. These include other software engineering documentation, technical references, vendor literature, and; standards. The appendix contains information that supplements the specifications. Tabular data, detailed description of algorithms, charts, graphs and other material, are presented as appendixes. Elaborate the concept of product operation factors and explain all product operation factors? (5) 1. Product Operation Factors The product operation factors determine the quality of software when a program is executed. Good quality software is not only correct and reliable but also delivers correct performance in all circumstances. Some of the factors of product operation are correctness, reliability, efficiency, integrity, and usability. Correctness Accuracy of the program and the extent to which it fulfills design specifications Reliability Extent to which the program is secure and its ability to recover quickly from failure. Efficiency Performance of the program and its ability to perform tasks within a time frame P a g e 85

86 Integrity Ability of the program to take care of security and the extent to which it can prevent unauthorized. Usability Ease with which a user can learn, operates, and uses the program. Question No: 24 ( Marks: 10 ) Explain the following terms regarding project characteristics and project dimensions. Temporary, Unique, Aims, People, Process Temporary Temporary means that every project has a definite beginning and a definite end. The end is reached when the project s objectives have been achieved, or it becomes clear that the project objectives will not or cannot be met, or the need for the project no longer exists and the project is terminated. Temporary does not necessarily mean short in duration; many projects last for several years. In every case, however, the duration of a project is finite; projects are not ongoing efforts unique: Operations and projects differ primarily in that operations are ongoing and repetitive while projects are temporary and unique. A project can thus be defined in terms of its distinctive characteristics a project is a temporary endeavor undertaken to create a unique product or service. Temporary means that every project has a definite beginning and a definite end. Unique means that the product or service is different in some distinguishing way from all other products or services. For many organizations, projects are a means to respond to those requests that Aims/Tasks/Purpose The projects are designed to achieve specific targets defined in terms of aims, tasks or a purpose. The nature and size of the project depends upon complexity of the task, realization of the aims and scope of the purpose any organization wants to achieve. In short project has to be aimed for achieving certain tasks in a given time frame. Process: A software process provides the framework from which a comprehensive plan for software development can be established. Give the name of configuration control tools? P a g e 86

87 1. Automatic version control and 2. Change control tools 3. Monitoring, auditing and registration support utilities 4. Storage facilities; a safe repository for all approved configuration items,including: On-site storage for the day to day development process Off-site storage for catastrophe recovery Giving reasons for your answer based on the type of system being developed, suggest the most appropriate software process model which might be used as a basis for managing the development of the following system: (9) i. Certified Carriers is a courier company that has decided to automate its billing, customer service, and inventory systems due to an increase in their sales volume and customer strength. The company has no experience in automation because this is for the first time that they are planning for automating their basic services. The client too has no idea about the size, cost, and the duration of the project. They have assigned the automation project to Technology Systems. Technology Systems needs to analyze the systems of Certified Carriers and present a prospective: working model of the software product. Only after the working model is approved and signed-off by Certified Carrier, will the team draw up a specific project plan and create a development team. However, an analysis team is formed to create the working model, arrange meetings with the client, accept feedback, and implement all practicable feedback to the working model. The team at Technology Systems intends to reuse the technology and the working model to further develop and complete the creation of the software product. High level WBS goals 2marks Software development 1. Requirements analysis 2. Prototype development 3. Prototype specification 4. Prototype design 5. Prototype implementation Design 1. Top level design P a g e 87

88 2. Detailed design Implementation 1. Coding 2. Unit test Integration 1. Software integration 2. Hardware/software integration Testing 1. Alpha testing 2. Beta testing 3. Acceptance Installation / Maintenance 1. Error correction 2. Software enhancement Management 1. Planning 2. Staffing 3. Administration and services 4. Budget administration 5. Personnel management 6. Quality assurance 7. Configuration management Training / Procurement 1. Acquisition of development tools 2. Acquisition of system components (off the shell) 3. Equipment selection 4. Vendor selection P a g e 88

89 5. Ordering procedure 6. Inventory control Documentation Technical writing Project publishing activities Development documentation Non-deliverable development documentation Deliverable development documentation Maintenance documentation / User documentation A 'Work Breakdown Structure' (WBS) is identified for each project, which includes a hierarchical set of phases, activities and tasks to be undertaken on the project. What is progress line.2marks To track a project plan, you first view the progress of a project. You can view the progress of a project by applying progress lines to the tasks in the project. You can display progress lines in three ways, 1. at the current status of a project, 2. on selected dates of a project plan and 3. at regular intervals such as daily, weekly, or monthly. What is software process.2marks When you build a product or system, it s important to go through a series of predictable steps a road map that helps you create a timely, high-quality result, The road map that you follow is called a software process. Types of risk 3Marks There are two types of risks: 1. development process risks and 2. Product- related risks. P a g e 89

90 Development Process Risks The risks encountered during product development are categorized as development process risks. These comprise developer errors, natural disasters, disgruntled employees, and poor management objectives. Product Risks Product risks crop up in the form of changing requirements during product development. Incomplete and unclear requirements are a risk to the product during development. Similarly, problems in meeting design specifications can also be categorized as risk to product development. What is meant by project uniqueness? 3Marks Projects are always unique; there are never 2 projects that are exactly the same. Uniqueness can be defined in the following terms: - Start Date and End Date - Objectives - Goals Again, there are never 2 projects that are exactly the same, otherwise, Project Management can be something done by anyone. When a software engineer is provided incorrect, incomplete requirements, which areas are affected most (3) Solution; Budgeting, costing, team management (graphics is missing) What are the tasks that you perform in project closedown? (5) The final activity for a project manager is project closedown. For most software projects, the project closedown activities take place in the post-implementation phase. However, in some software projects, the customer requests support activities for a longer duration. In such cases, the software project is considered closed immediately after implementation. The tasks that you perform in project closedown are mentioned below: Prepare closedown report: The project closedown report contains the results of the causal analysis that you do for the project. This contains an analysis of what went wrong, what went right, and what you could have done better in the software project. P a g e 91

91 Identify learning: You also need to assess the entire software project and the results of the causal analysis to identify the key learning points from the software project. This helps you identify areas of improvement for future projects. The learning points can also be used by the organization as considerations while planning and executing the next software project. Identify reusable software components: Reusing software components enables you to lower the cost, time, and effort required to complete the software project successfully. After project closedown, you identify the software components that can be reused in future projects of similar nature. The software components prepared for a software project may be complete, partially complete, or in the design stage. These components or their designs can be assessed for usability in future projects. Create reference material: After the project is complete, you can create white papers and reference documents. This can be a significant contribution to the organization and the application area of the software by creating an authoritative knowledge base. Q 31. What are the tasks that you perform in project closedown? (2) Ans: 1. Prepare closedown report 2. Identify Learning 3. Identify reusable software components 4. Create reference material State any three benefits of weekly status report (2) Ans: 1. Activities during the period 2. Activities planed for next week 3. Problems. 37. Define software process & explain it (3) Ans: When you build a product or system, it s important to go through a series of predictable steps a road map that helps you create a timely, high-quality result, The road map that you follow is called a software process A software process provides the framework from which a comprehensive plan for software development can be established. Describe Formal change process in detail (5) Change control combines human procedures and automated tools to provide a mechanism for controlling change. The purpose of change control is to monitor and control changes in order to baseline SCIs. In Formal Change Control Process a request for change triggers that change control procedure. Then request is logged in the change request register. Next, the change request number is recorded in the change request evaluation plan. The request is evaluated and P a g e 91

92 analyzed to check if the change is valid. Change request is also evaluated in terms of the number of items affected and the effort involved in effecting the change. Finally, the possible outcome of the change request is communicated. The request for change is rejected, deferred, or approved. If the request for change is rejected, the requestor needs to log a fresh request. A deferred change request is evaluated at a later date while the change request that is approved is implemented. Synchronization control helps to ensure that parallel changes performed by two different people do not overwrite one another. Star Change request is made Change request is logged Change request is evaluated Outcome is notified Is the Request YES Rejected? Is the Request NO YES Deferred? NO Change request is implemented P a g e 92 STOP

93 Integrating different software products in cross-platform implementation: The modern software environment requires that all software should integrate with each other. However, many software projects do not plan for integration with existing software in the same or different domain. This limits the application software and reduces the shelf life drastically. They key to the success of a software product is interoperability. The software project manager needs to determine the scope for the software product such that is can be integrated easily with existing software. Explain the process of controlling versions (3) Controlling Versions Version control combines procedures and tools to manage different versions of configuration objects that are created during software product development. To control versions, you can use Version Control Register. In Version Control Register, you enter the details of components, such as component identification numbers, their versions, and dates of validity. It is advisable to release a baseline after a version is released. Baseline is a specification or a product that is formally reviewed and agreed upon. This serves as the basis for further development. Baseline can be changed only through formal change control procedures. A baseline consists of a set of SCIs that are logically related to each other. Baselines are established when subsequent changes to the SCIs need to be controlled. Version control is essential so that everybody uses only the latest version. Any kind of version mismatch might result in rework. In your opinion what are the essential Project Manager skills to execute a Software project timely and in cost-effective way meeting the specifications and quality standards. Briefly discuss two of them. (5) Ans: P a g e 93

94 Following are the essential Project Manager skills to execute a Software project timely and in cost-effective way meeting the specifications and quality standards. The role of the Leader in project management is one of great responsibility. It's the project manager's job to direct and supervise the project from beginning to end. Here are some other roles: (a) Leadership (b) Communications (c) Problem Solving (d) Negotiating (e) Influencing the Organization (f) Mentoring (g) Process and technical expertise Problem Solving There are three steps involved in this important leadership role; 1. identifying problem; 2. analyzing its cause; and 3. solving the problem. Problem solving involves a combination of problem definition and decision-making. Problem definition requires distinguishing between causes and symptoms. Problems may be: Internal (a key employee is reassigned to another project) External (a permit required to begin work is delayed). Technical (differences of opinion about the best way to design a product) Managerial (a functional group is not producing according to plan) or Interpersonal (personality or style clashes). P a g e 94

95 Decision-making 1. Decision-making includes analyzing the problem to identify viable solutions, and then making a choice from among them. 2. Decisions can be made or obtained (from the customer, from the team, or from a functional manager). 3. Once made, decisions must be implemented. 4. Decisions also have a time element to them the right decision may not be the best decision if it is made too early or too late. Four dimensions of a software project. (5) Four Project Dimensions Software project management is an umbrella activity within software engineering. It begins before any technical activity is initiated and continues throughout the definition, development, and support of computer software. Four P's have a substantial influence on software project management- people, product, process, and project. People must be organized into effective teams, motivated to do high-quality software work, and coordinated to achieve effective communication. The product requirements must be communicated from customer to developer, partitioned (decomposed) into their constituent parts, and positioned for work by the software team. The process must be adapted to the people and the problem. A common process framework is selected, an appropriate software engineering paradigm is applied, and a set of work tasks is chosen to get the job done. The project must be organized in a manner that enables the software team to succeed. Effective software project management focuses on the four P s: people, product, process, and project. The order is not arbitrary. The manager who forgets that P a g e 95

96 software engineering work is an intensely human endeavor will never have Success in project management. A manager who fails to encourage comprehensive customer communication early in the evolution of a project risks building an elegant solution for the wrong problem. The manager who pays little attention to the process runs the risk of inserting competent technical methods and tools into a vacuum. The manager who embarks without a solid project plan jeopardizes the success of the product. What is the most important contributor to a successful software project? People In a study published by the IEEE, the engineering vice presidents of three major technology companies were asked the most important contributor to a successful software project. They answered in the following way: VP 1: I guess if you had to pick one thing out that is most important in our environment. I d say it s not the tools that we use, it s the people. VP 2: The most important ingredient that was successful on this project was having smart people very little else matters in my opinion...the most important thing you do for a project is selecting the staff...the success of the software development organization is very, very much associated with the ability to recruit good people. VP 3: The only rule I have in management is to ensure I have good people real good people-and that I grow good people and that I provide an environment in which good people can produce. Indeed, this is a compelling testimonial on the importance of people in the P a g e 96

97 software engineering process. And yet, all of us, from senior engineering vice presidents to the lowliest practitioner, often take people for granted. Managers argue (as the preceding group had) that people are primary, but their actions sometimes belie their words. In this section we examine the players who participate in the software process and the manner in which they are organized to perform effective software engineering. 1. The Players The software process (and every software project) is populated by players who can be categorized into one of five constituencies: 1. Senior managers who define the business issues that often have significant influence on the project. 2. Project (technical) managers who must plan, motivate, organize, and control the practitioners who do software work. 3. Practitioners who deliver the technical skills that are necessary to engineer a product or application. 4. Customers who specify the requirements for the software to be engineered and other stakeholders who have a peripheral interest in the outcome. What is the advantage of function point (2) Advantages of Using Function Points 1. Function points are language-and technology-independent. Therefore, you can use them to estimate any kind of project. 2. They can also be used to estimate the effort, cost, and schedules of projects that use the Prototyping and Spiral models because such projects have uncertain user and project requirements. P a g e 97

98 3. you can use function points as a project estimation technique when you anticipate changes in the middle of a project. These changes may disturb the estimates if, you had used SLOC to estimate the effort, cost, or size of a project. 4. The FP estimation uses a subjective and holistic approach for project estimation. Consequently, the estimates calculated by using the FP are unlikely to be incorrect. Write down concept of time and effort allocation for project scheduling? (3) Ans: Each activity in a software project needs a certain amount of time and effort for completion. To manage the project, you assign start and end dates to each activity. You also need to allocate appropriate effort to each activity. Most software projects operate with time and effort constraints. Therefore, managing within the available resources is very important for a software project manager. When risk is considered in the context of software engineering what conceptual underpinning are always in evidence (3) Ans: The future is our concern what risks might cause the software project to go awry? Change is our concern -how will changes in customer requirements, development technologies, target computers, and all other entities connected to the project affect timeliness and overall success? Last, we must grapple with choices - what methods and tools should we use, how many people should be involved, how much emphasis on quality is "enough"? What is progress line? How many ways a progress line can be displayed? (3) To track a project plan, you first view the progress of a project. You can view the progress of a project by applying progress lines to the tasks in the project. You can display progress lines in three ways, You can choose to display progress lines always at the current status of a project. To do this, you need to select the Always display current progress lines check box in the Progress Lines dialog box. Selecting this option displays progress lines every time based on the current status of a project. P a g e 98

99 The second way to display project lines is to display them on selected dates of a project plan. For example, you use this option when you need to know the progress status of a project on the jay development is completed. In this case, you select the Display selected progress lines check box to display progress lines on that day. Similarly, you can use this option to display progress lines on the day when testing is completed or the project-end date. Finally, you can display progress lines at regular intervals such as daily, weekly, or monthly.1f you choose daily, you can further define its preciseness by choosing everyday, every second, or every third day, and so on. Alternatively, if you choose monthly, you can refine your choice by selecting the month and day when a progress line is displayed. List the project planning key tasks used in planning physics (3) Ans: 1. Set goal and scope 2. Select lifecycle 3. Set organization team form 4. Start team selection 5. Determine risks 6. Create WBS 7. Identify tasks 8. Estimate size 9. Estimate effort 10. Identify task dependencies P a g e 99

100 11. Assign resources 12. Schedule work What is the output that comes from staff acquisition (3) Ans: i. Project staff assigned. The project is staffed when appropriate people have been reliably assigned to work on it. Staff may be assigned full time, part time, or variably, based on the needs of the project. ii. Project team directory. A project team directory lists all the project team members and other stakeholders. The directory may be formal or informal, highly detailed or broadly framed, based on the needs of the project. Benefits/advantages WBS? Ans: Using a WBS provides a number of benefits to the management and to the development teams. 1. First, it gives the management an idea about the size and complexity of the project. 2. Second, it helps in planning, scheduling, and monitoring a project realistically. 3. This is possible because all the tasks in the project can be performed measurable targets for each task. Why we use WBS?(5) Ans Defines 100% of the scope and can communicate the scope of the project without the presence of the scope statement or document. 4. Communicates effectively to all stakeholders 5. Defines and clarifies 6. Boundaries (Life cycle of the project, not the product) 7. Deliverables 8. Refines Scope Spring 2013 mid paper. Explain the quality standard and procedure in detail. P a g e 111

101 Quality Standards and Procedures : The quality of software is said to be high if it meets the standards and procedures, defined for the product. Standards are criteria to which the products are compared. For example, there may be standards that govern the quality review process. There are are the three types of standards that software projects usually follow. 1. Documentation standard 2. design standard and 3. code standard Documentation standard specifies the form and content for planning, control, and product documentation. Design standards provide rules and methods for translating the software requirements into software design. The design standards are specified in the form and content of the product design. Code standard defines the language in which code should be written. The standard clearly mentions the structures, style conventions, and rules for data structures and interfaces that will be implemented in the project. Procedures are criteria to which the development and control processes are compared. Procedures are explicit steps followed in a process. Procedures need to be properly documented because they are needed for configuration management, nonconformance reporting, corrective action, testing, and formal inspections. Proper documentation of procedures is necessary because SQA activities rely on them for project compliance. Organizations normally enforce quality standards with the help of checklists, common error lists, and standards and guidelines. Configuration controls cannot be effective the necessary tool and facility. Which tool should be used for configuration control? Configuration control tools, including: P a g e 111

102 1. Automatic version control and 2. Change control tools 3. Monitoring, auditing and registration support utilities 4. Storage facilities; a safe repository for all approved configuration items, including: On-site storage for the day to day development process Off-site storage for catastrophe recovery Suppose a project manager switches either tool or technology during development phase of a project, u have to identified the issue raised due to this change. Switching the tool or technology used during the software development stage causes the developers to relearn a new tool. In addition, there is a chance that it might not be possible to integrate the software already developed with the new tool. The prototype is normally used for requirement gathering. Analysis should be conducted regardless of the SW engineering paradigm. It is possible to apply operational analysis principles and derive a model of SW from which a design can be developed. Requirement Elicitation (FAST, QFD etc) is conducted and a model is built, called Prototype. Switching tool (adopting a new tool) in the mid of project is problematic for the development team. Why do you need switching tools? The current technology environment offers new tools and technologies for software development at a fast rate. All these tools and technologies offer the benefits of a shorter development cycle, lower costs, and under better functionality than earlier tools. You should identify and commit to the tool and technology for the software project before the Project commences. Switching the tool or technology used during the software development stage causes the developers to relearn a new tool. In addition, there is a chance that it might not be possible to integrate the software already developed with the new tool. Define the SAFETY RISKS AND HAZARDS? 5 Marks ANS : P a g e 112

103 Risk is not limited to the software project itself. Risks can occur after the software has been successfully developed and delivered to the customer. These risks are typically associated with the consequences of software failure in the field. Software safety and hazard analysis [LEV95] are software quality assurance activities that focus on the identification and assessment of potential hazards that may affect software negatively and cause an entire system to fail. If hazards can be identified early in the software engineering process, software design features can be specified that will either eliminate or control potential hazards. Define the SQA Concept? ANS : SQA is the process of evaluating the quality of a product and enforcing adherence to software product standards and procedures. It is an umbrella activity that ensures conformance to standards and procedures throughout the SDLC of a software product. Define the importance Human resource management in the terms of the Software Management? ANS : Project Human Resource Management includes the processes required to make the most effective use of the people involved with the project. It includes all 1. The project stakeholders 2. sponsors, 3. customers, 4. partners, and 5. Individual contributors. Following are some major processes: Organizational Planning identifying, documenting, and assigning project roles, responsibilities, and reporting relationships. P a g e 113

104 Staff Acquisition getting the human resources needed assigned to and working on the project. Team Development developing individual and group competencies to enhance project performance. These processes interact with each other and with the processes in the other knowledge areas as well. Each process may involve effort from one or more individuals or groups of individuals, based on the needs of the project. Draw the Product Orientation table According to the WBS? ANS: Define the Product risk? 5 makrks ANS: Product risks crop up in the form of changing requirements during product development. Incomplete and unclear requirements are a risk to the product during development. Similarly, problems in meeting design specifications can also be categorized as risk to product development. Risks could arise if 1. the project deliverables or objectives are not clearly defined or P a g e 114