Scribd
Upload
25 views5 pages

Statistics

Uploaded by

malegaon vv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
25 views5 pages

Statistics

Uploaded by

malegaon vv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Q2 a) Write the Risk Management Process by considering any project you came across with.

Mention Risk Identification, Risk Analysis, and Risk Mitigation.


Answer:

1. Risk Identification:
o Identify risks that might affect the project (e.g., budget overruns, technical
challenges, resource unavailability).
o Tools: Brainstorming, checklists, and expert judgment.
2. Risk Analysis:
o Assess the likelihood and impact of each identified risk.
o Use qualitative and quantitative techniques to rank risks.
3. Risk Mitigation:
o Develop strategies to reduce or eliminate risks.
o Examples: Allocating contingency reserves, improving team training, or
employing alternate solutions.

Q2 b) Explain the use of MS Project to track agile project progress.


Answer:
Microsoft Project is a powerful tool for managing agile projects. Its uses include:

1. Sprint Planning: Create and manage tasks in sprints.


2. Progress Tracking: Use Gantt charts to visualize project progress.
3. Resource Allocation: Assign resources effectively and monitor workloads.
4. Integration: Link tasks and dependencies for smooth workflow.
5. Custom Reporting: Generate real-time reports on velocity, burndown charts, etc.

Q2 a (alternative): Compute the functional point for the project.


Answer:
Functional Point (FP) Calculation:
Using the formula:
FP = Σ (Count × Weighting Factor)
Given factors:

 Number of User Inputs: 15 × 4 = 60


 Number of User Outputs: 21 × 5 = 105
 Number of User Enquiries: 11 × 4 = 44
 Number of User Files: 12 × 10 = 120
 Number of External Interfaces: 19 × 7 = 133

Total FP (unadjusted): 462


Adjusting for complexity factors (Data communication, performance, etc.):
Add complexity adjustment value (CAV) as required.

Q2 b) Explain the benefits of agile project management.


Answer:

1. Flexibility: Quick adjustments to project scope and requirements.


2. Customer Satisfaction: Continuous delivery of working solutions ensures
satisfaction.
3. Risk Mitigation: Frequent releases reduce risks of failures.
4. Team Collaboration: Agile promotes close interaction among stakeholders.
5. Quality Improvement: Regular testing ensures better quality outcomes.

Q3 a) A new project with estimated 325 KLOC system has to be developed. For the
development of the project following things also required. i) Volatility of the virtual machine
environment is low (0.87) ii) Product Complexity is High (1.15) iii) Virtual machine
experience is high (1.07) iv) Complexity of the product is Extra High (0.90) v) Use of
software tools is very high (0.83) vi) Remaining all drivers are treated as Nominal.
Calculate ; 1) Effort 2) Development time 3) Average staff size 4) Productivity of the product
Answer:
To calculate Effort, Development Time, Average Staff Size, and Productivity, we can use
the COCOMO (Constructive Cost Model) formulas.

Formulas:

1. Effort (E):

E=a×(KLOC)b×∏Effort MultipliersE = a \times (KLOC)^b \times \prod \text{Effort


Multipliers}E=a×(KLOC)b×∏Effort Multipliers

oKLOC=325KLOC = 325KLOC=325
oa,ba, ba,b: Scale factors (from the basic COCOMO model; assume typical
values for Embedded systems a=3.0,b=1.12a = 3.0, b = 1.12a=3.0,b=1.12)
o Effort Multipliers are the given factors like volatility, complexity, etc.
2. Development Time (Tdev):

Tdev=c×(E)dTdev = c \times (E)^dTdev=c×(E)d

o c,dc, dc,d: Time factors (assume c=2.5,d=0.35c = 2.5, d = 0.35c=2.5,d=0.35).


3. Average Staff Size (Staff):

Staff=ETdev\text{Staff} = \frac{E}{Tdev}Staff=TdevE

4. Productivity:

Productivity=KLOCE\text{Productivity} = \frac{KLOC}{E}Productivity=EKLOC

Step-by-Step Calculation:

1. Effort Multipliers (EM):

Given values:

 Volatility of the virtual machine: 0.870.870.87


 Product Complexity: 1.151.151.15
 Virtual Machine Experience: 1.071.071.07
 Complexity of Product: 0.900.900.90
 Use of Software Tools: 0.830.830.83
 Remaining Drivers: Nominal (1.01.01.0)

EM=0.87×1.15×1.07×0.90×0.83=0.849EM = 0.87 \times 1.15 \times 1.07 \times 0.90 \times


0.83 = 0.849EM=0.87×1.15×1.07×0.90×0.83=0.849
2. Effort (E):

E=a×(KLOC)b×EME = a \times (KLOC)^b \times EME=a×(KLOC)b×EM


E=3.0×(325)1.12×0.849E = 3.0 \times (325)^{1.12} \times 0.849E=3.0×(325)1.12×0.849
First, calculate 3251.12325^{1.12}3251.12:

3251.12≈436.52325^{1.12} \approx 436.523251.12≈436.52


Then:

E=3.0×436.52×0.849≈1111.09 Person-Months (PM)E = 3.0 \times 436.52 \times 0.849 \


approx 1111.09 \, \text{Person-Months (PM)}E=3.0×436.52×0.849≈1111.09Person-
Months (PM)
3. Development Time (Tdev):

Tdev=c×(E)dTdev = c \times (E)^dTdev=c×(E)d Tdev=2.5×(1111.09)0.35Tdev = 2.5 \times


(1111.09)^{0.35}Tdev=2.5×(1111.09)0.35
First, calculate 1111.090.351111.09^{0.35}1111.090.35:

1111.090.35≈6.561111.09^{0.35} \approx 6.561111.090.35≈6.56


Then:

Tdev=2.5×6.56≈16.4 MonthsTdev = 2.5 \times 6.56 \approx 16.4 \, \


text{Months}Tdev=2.5×6.56≈16.4Months
4. Average Staff Size:

Staff=ETdev\text{Staff} = \frac{E}{Tdev}Staff=TdevE Staff=1111.0916.4≈67.76 Persons\


text{Staff} = \frac{1111.09}{16.4} \approx 67.76 \, \text{Persons}Staff=16.41111.09
≈67.76Persons
5. Productivity:

Productivity=KLOCE\text{Productivity} = \frac{KLOC}{E}Productivity=EKLOC
Productivity=3251111.09≈0.292 KLOC/Person-Month\text{Productivity} = \frac{325}
{1111.09} \approx 0.292 \, \text{KLOC/Person-Month}Productivity=1111.09325
≈0.292KLOC/Person-Month

Final Results:

1. Effort: 1111.09 Person-Months1111.09 \, \text{Person-Months}1111.09Person-


Months
2. Development Time: 16.4 Months16.4 \, \text{Months}16.4Months
3. Average Staff Size: 67.76 Persons67.76 \, \text{Persons}67.76Persons
4. Productivity: 0.292 KLOC/Person-Month0.292 \, \text{KLOC/Person-
Month}0.292KLOC/Person-Month
Q3 b) Explain the Agile Manifesto in detail.
Answer:
The Agile Manifesto in Detail

The Agile Manifesto, introduced in 2001 by a group of software development professionals,


outlines a set of principles and values that prioritize flexibility, collaboration, and customer
satisfaction in software development. It is the foundation of Agile methodologies like Scrum,
Kanban, and XP (Extreme Programming).

Core Values of the Agile Manifesto:

1. Individuals and Interactions Over Processes and Tools


o Explanation: Focus on collaboration and communication within teams, rather
than rigidly adhering to processes or relying heavily on tools.
o Why It Matters: Strong teamwork and effective communication lead to better
results than depending solely on predefined systems.
2. Working Software Over Comprehensive Documentation
o Explanation: Deliver functional software frequently, rather than spending
excessive time on detailed documentation that may become outdated.
o Why It Matters: Customers value usable products more than lengthy
documentation. Documentation should be sufficient but not overwhelming.
3. Customer Collaboration Over Contract Negotiation
o Explanation: Involve customers in every phase of development to ensure the
product meets their needs. Focus on building trust and maintaining open
communication.
o Why It Matters: Frequent feedback ensures the final product aligns with
customer expectations, reducing risks of misalignment.
4. Responding to Change Over Following a Plan
o Explanation: Be flexible and open to changes in requirements, even late in
development. Plans should guide the process but not limit adaptation.
o Why It Matters: Businesses and priorities evolve, and Agile allows teams to
pivot quickly to accommodate new needs.

12 Principles of Agile Software Development:

1. Customer Satisfaction Through Early and Continuous Delivery


o Deliver valuable software frequently to ensure customers see progress and
value early.
2. Welcome Changing Requirements, Even Late in Development
o Agile embraces change as a way to ensure the product remains relevant and
valuable.
3. Deliver Working Software Frequently
o Deliver software in smaller, incremental updates (e.g., every 2-4 weeks) for
consistent progress.
4. Close Collaboration Between Business People and Developers
o Maintain constant communication between stakeholders to align development
with business goals.

You might also like