Академический Документы
Профессиональный Документы
Культура Документы
PART B (3 x 16 = 48 marks)
1.
a Explain about the evolutionary process model (16)
Evolutionary models are iterative. They are characterized in a manner that enables you to develop increasingly more
complete versions of the software
Prototyping
The customer sees a "working version" of the software, wants to stop all development
and then buy the prototype after a "few fixes" are made
In most circumstances, plan to discard the prototype and engineer the actual production software with a goal
toward quality
Spiral Model
(or)
b. Explain the iterative waterfall and the incremental model for software life cycle
and various activities in each phase (16)
Work flow is in a linear (i.e., sequential) fashion within an increment and is staggered between
increments
Iterative in nature; focuses on an operational product with each increment
Provides a needed set of functionality sooner while delivering optional components later
Useful also when staffing is too short for a full-scale development
Tracking can be accomplished in a
number of different ways:
Conducting periodic project status
meetings in which each team
member reports progress and
problems
Evaluating the results of all reviews conducted throughout the software engineering process
Determining whether formal project milestones have been accomplished by the scheduled date
Comparing the actual start date to the planned start date for each project task listed in the resource
table
Meeting informally with practitioners to obtain their subjective assessment of progress to date and
problems on the horizon
Using earned value analysis to assess progress
quantitatively
The time-boxing strategy recognizes that the
complete product may not be deliverable by the
predefined deadline. The tasks associated with
each increment are then time-boxed.
WebApp project scheduling distributes estimated effort across the planned time line (duration) for building each
WebApp increment.
seven increments. Each framework action can be adapted in one of four ways
(1) a task is applied as is,
(2) a task is eliminated because it is not necessary for the increment,
(3) a new (custom) task is added, and
(4) a task is refined (elaborated) into a number of named subtasks that each becomes part of the schedule.
(or)
b Brief about calculating Earned Value Measures.(16)
3. a. Describe LOC and function point estimation with neat example (16)
(or)
What are the categories of software risks? Give an overview about risk management.
b.
(16)
two characteristics
Uncertainty
the risk may or may not happen; that is, there are no 100 percent probable risks
Loss
if the risk becomes a reality, unwanted consequences or losses will occur
When risks are analyzed, it is important to quantify the level of uncertainty and the degree of loss
associated with each risk.
Project risks threaten the project plan.
the project schedule will slip and that costs will increase
identify potential budgetary, schedule, personnel, resource, stakeholder, and requirements
problems and their impact on a software project
Technical risks threaten the quality and timeliness of the software to be produced.
implementation may become difficult or impossible