07-11-2011, 10:14 PM
what are the tasks that you perform in project closedown ? (2)
. state any three benefits of weekly status report (2)
list the features of WBS? (2)
what are the advantage of function point (2)
.what are the types of risk (2)
how can material resource rate is calculated? (2)
.define software process & explain it (3)
.write down concept of “time and effort allocation” for project scheduling ? (3)
.when risk is considered in the context of software engineering what conceptual underpinning are always in evidence (3)
what is process line? How many ways a progress line can be displayed? (3)
.list the project planning key tasks used in planning physics (3)
.what are the output that comes from staff acquisition (3)
.why we use WBS?(5)
difference between reactive & proactive risk management (5)
. prepare simple risk analysis table?(5)
================================
Q 31. what are the tasks that you perform in project closedown ? (2)
Ans: Prepare closedown report
Identify Learning
Identify reusable software components
Create reference material
32. state any three benefits of weekly status report (2)
Ans: Activities during the period
Activities plaaned for next week
Problems.
33. list the features of WBS? (2)
Ans :First, it gives the management an idea about the size and complexity of the
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.
34. what are the advantage of function point (2)
Function points are language-and technology-independent. Therefore, you can use
them to estimate any kind of project. 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.
In addition, 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.
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.
35.what are the types of risk (2)
Ans: A software project encounters two types of risks, development process risks and
product- related risks. Some of the development process risks are developer
errors, natural disasters, disgruntled employees, and poor management objectives.
Some project related risks are incomplete requirements, unclear project
deliverables and objectives, and complexity of the product.
36.how can material resource rate is calculated? (2)
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.
38.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
39.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"?
40.what is progess 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,
41.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
11. Assign resources
12. Schedule work
42.what are 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.
43.why we use WBS?(5)
Ans: Using a WBS provides a number of benefits to the management and to the
development teams.
First, it gives the management an idea about the size and complexity of the
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.
44.difference between reactive & proactive risk management (5)
Ans: Reactive strategies have been laughingly called the “Indiana Jones School of risk
management” [THO92]. In the movies that carried his name, Indiana Jones, when
faced with overwhelming difficulty, would invariably say, “Don’t worry, I’ll
think of something!” Never worrying about problems until they happened, Indy
would react in some heroic way.
Sadly, the average software project manager is not Indiana Jones and the
members of the software project team are not his trusty sidekicks. Yet, the
majority of software teams rely solely on reactive risk strategies. At best, 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” [CHA92] takes
over, and the project is in real jeopardy.
A considerably more intelligent strategy for risk management is to be proactive. A
proactive strategy 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.
45. prepare simple risk analysis table?(5)
. state any three benefits of weekly status report (2)
list the features of WBS? (2)
what are the advantage of function point (2)
.what are the types of risk (2)
how can material resource rate is calculated? (2)
.define software process & explain it (3)
.write down concept of “time and effort allocation” for project scheduling ? (3)
.when risk is considered in the context of software engineering what conceptual underpinning are always in evidence (3)
what is process line? How many ways a progress line can be displayed? (3)
.list the project planning key tasks used in planning physics (3)
.what are the output that comes from staff acquisition (3)
.why we use WBS?(5)
difference between reactive & proactive risk management (5)
. prepare simple risk analysis table?(5)
================================
Q 31. what are the tasks that you perform in project closedown ? (2)
Ans: Prepare closedown report
Identify Learning
Identify reusable software components
Create reference material
32. state any three benefits of weekly status report (2)
Ans: Activities during the period
Activities plaaned for next week
Problems.
33. list the features of WBS? (2)
Ans :First, it gives the management an idea about the size and complexity of the
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.
34. what are the advantage of function point (2)
Function points are language-and technology-independent. Therefore, you can use
them to estimate any kind of project. 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.
In addition, 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.
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.
35.what are the types of risk (2)
Ans: A software project encounters two types of risks, development process risks and
product- related risks. Some of the development process risks are developer
errors, natural disasters, disgruntled employees, and poor management objectives.
Some project related risks are incomplete requirements, unclear project
deliverables and objectives, and complexity of the product.
36.how can material resource rate is calculated? (2)
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.
38.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
39.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"?
40.what is progess 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,
41.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
11. Assign resources
12. Schedule work
42.what are 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.
43.why we use WBS?(5)
Ans: Using a WBS provides a number of benefits to the management and to the
development teams.
First, it gives the management an idea about the size and complexity of the
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.
44.difference between reactive & proactive risk management (5)
Ans: Reactive strategies have been laughingly called the “Indiana Jones School of risk
management” [THO92]. In the movies that carried his name, Indiana Jones, when
faced with overwhelming difficulty, would invariably say, “Don’t worry, I’ll
think of something!” Never worrying about problems until they happened, Indy
would react in some heroic way.
Sadly, the average software project manager is not Indiana Jones and the
members of the software project team are not his trusty sidekicks. Yet, the
majority of software teams rely solely on reactive risk strategies. At best, 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” [CHA92] takes
over, and the project is in real jeopardy.
A considerably more intelligent strategy for risk management is to be proactive. A
proactive strategy 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.
45. prepare simple risk analysis table?(5)
0300-9520262
Get solution in 24 hour |cpmputer & internet
mileys81:[SIZE="4"][SIZE="3"]....[/SIZE][/SIZE]
