B.Sc.(I.T.) Sem VI Software Project Management Solution Set, April 2017

Size: px
Start display at page:

Download "B.Sc.(I.T.) Sem VI Software Project Management Solution Set, April 2017"

Transcription

1 B.Sc.(I.T.) Sem VI Software Project Management Solution Set, April 2017 Q1 (a) Explain the five basic parameters of the software cost model Q1(b) Explain briefly the drawbacks of Waterfall Model. Q1(c) How software size can be reduced? Explain. 1. Object Oriented methods and visual modeling 2. Reuse 3. Commercial Components Q1(d) How peer inspection helps in improving returns on investment? Explain. Peer Inspection : In software development, peer review is a type of software review in which a work product (document, code, or other) is examined by its author and one or more colleagues, in order

2 to evaluate its technical content and quality. Peer Inspection finds the problems very early in the project life cycle, hence improves the ROI. It provides a significant return. One value of inspections in the professional development of a team. It is generally useful to have the products of junior team members reviewed by senior mentors. Putting the products of amateurs into the hands of experts and vice versa is a good mechanism for accelerating the acquisition of knowledge and skill in new personnel. Gross blunders can be caught and feedback can be appropriately channeled, so that bad practices are not perpetuated. This is one of the best ways for junior software wngineer to learn. Q2(a) Summarize differences, in emphasis on different life cycle aspects, between the two life cycle stages.

3 Q2(b) Explain Elaboration Phase of the life cycle.

4 Q2(c) List all the five artifact set. Explain Release Specification. Release Specification :- (NOTE : give marks if students are writing explanation of Release specification instead of the outline given above) Q2(d) Discuss technical perspective of software architecture.

5 Q3(a) Write a short note on Major Milestones. Definition of Milestones Definition of Major Milestones 4 types of major milestones (brief explanation)

6 Q3(b). Define WBS. Explain Evolutionary Work Break Down Structures. Evolutionary Work Break Down Structures Q3(c) Explain the Iteration planning process.

7

8

9 Q3(d). Summarize the life cycle emphasis associated with each workflow.

10 Q4(a). Define Organizational structure. What is a Line of Business organization? Briefly explain main features of default Line of business organization. Organizational Structures form the architecture of the teams. Organizational Structure refers to the lines of authority that have the ability to control and take the decisions and the distribution of type of work performed is based on the core purpose and strategic purpose of the organization. Line of business refers to an internal corporate business unit. It is a set of one or more highly related projects. AA brief explanation of the following : 1. SEPA (software engineering process authority) 2. SEEA (software engineering environment authority) 3. PRA (project review authority) 4. Infrastructure Q4(b). Discuss various change categories defined on the basis of causes of change. Allocate the appropriate change category to the following changes: 1 Port to new platform 2 Loss of user data 3 Use of colours to differentiate updates from the previous version 4 Browser expands but doesn t collapse displayed entries 5 Upgradation to improve query performance

11 Q4(c). Explain mapping between process workflows and software development tools.

12 (Not necessary to make the diagram given above. Explanation should be on the same lines as in the diagram.) Q4(d). How the teams gravity shifts over the life cycle? Explain.

13 Q5(a). Define Metrics. Briefly explain 7 core metrics.

14 Q5(b) Discuss the basic characteristics of good metrics. Q5(c). Explain SPCP (software project control panel). SPCP is Software Project Control Panel. SPCP automates the project control activities of a software. It maintains an on-line version of the status of evolving artifacts. The panel can support standard features such as warning lights, thresholds, variable scales. digital formats and analog formats to present an overview of the current situation. This automation support can improve management insight into progress and quality trends and improve the acceptance of metrics by the engineering team.

15 Q5(d). What do you mean by Tailoring the process? Explain the dimensions of discriminating factors for tailoring the process. The process framework must be configured to the specific characteristics of the project. It is known as Tailoring the process. In tailoring the management process to a specific domain or project, there are two dimensions of discriminating factors:- 1. Technical Complexity 2. Management Complexity

16 Q6(a). How modern process framework exploits several critical approaches for resolving the five

17 recurring issues of the conventional process. Q6(b). Discuss the software management best practices.

18

19 Q6(c). Discuss the two major improvements expected in the next generation cost models Q6(d). Discuss the culture shifts necessary for the transition to modern software process. 1. Lower level & mid level managers are performers. 2. Requirements and designs are fluid and tangible. 3. Ambitious demonstrations are encouraged. 4. Good & bad project performance is much more obvious earlier in the life. 5. Early increments will be immature. 6. Artifacts are less important early, more important later. 7. Real issues are surfaced and resolved systematically. 8. Quality assurance is everyone s job, not a separate discipline. 9. Performance issues arise early in the life cycle. 10. Investments in automation are necessary. 11. Good software organizations should be more profitable.

20 Q7(a) Discuss important trends in improving software economics. Q7(b) Give difference between Software architecture and design. Software design is about designing the individual modules or components, what are the responsibilities, functions of modules, what it can do and what it can not do. Software Architecture is skeleton of a system. Its the highest level of abstraction of a system. What kind of data storage is present, how do modules interact with each other. What recovery systems are in place. So, software architecture is more about the design of the entire system while software design emphasizes on module or component. Q7(c). Discuss issues related to conventional WBS. (brief explanation of each point)

21 Q7(d). Write a short note on SCO.

22 Q7(e). Explain EVS (earned value system). One common approach to financial performance measurement is use of an Earned Value System, which provides highly detailed cost and schedule insight. EVS has proved to be effective for the production stage, where there is high - fidelity tracking of actuals versus plans and predictable results.

23

24 Q7(f). Summarize the balanced application of modern principles to achieve economic results.