DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

B. Tech-IV Year I Semester-II Mid-Term Examinations

LONG ANSWER QUESTIONS

Devise the Line-of- business organizations and the evolution of organizations in project organizations.

Articulate through brief note on software project quality indicators? Explain them in detail of each indicator.

Illustrate the Project Organization, Project Control and process instrumentation through necessary diagrams.

Defend the seven-core metrics significance in project organizations? How pragmatic software metrics helps to grow
their business lines.

Rephrase about next generation software economics and modern process transitions

Describe & Discuss about the common subsystem view of CCPDS-R and Explain test progress of CCPDS-R

Explain the Next-Generation software Economics and also How Modern Process Transitions help in the
agile process in modern software project management.
Examine the CCPDS-R Case Study and write a detailed notes on

Future Software Project Management Practices

OBJECTIVE BITS

1) Project teams are motivated by the cost, Schedule &quality of specific deliverables
2) Software Engineering Process Authority (SEPA), facilities the exchange of information
& process guidance both to & from project practitioners
3) Software Engineering Environment Authority (SEEA), is responsible for automating the
organization’s process, maintaining the organization’s standard environment, Training
projects to use the Environment &maintaining organization-wide reusable assets
4) Software errors can be categorized into two types
5) GUI support for a software project manager role and flexibility to support other roles.
6) Pragmatic Software Metrics demonstrates quantifiable correlation between process
perturbations (problems) and business performance.
7) There are three fundamental sets of management metrics: technical progress, financial
status, and staffing progress
8) The project management team is an active participant, responsible for producing as well
as managing.
9) The architecture team is responsible for real artifacts and for the integration of
components, not just for staff functions.
10) The development team owns the component construction and maintenance activities.
11) Develop an iterative life-cycle process that identifies the risks at an early stage
12) Develop a configuration process that should be economically scalable
13) The next generation software cost models should be designed in a way that, they can
assess larger architectures with economy of scale.
14) The lower-level managers and the middle level managers should participate in the
 project development
15) The performance of the project can be determined earlier in the life cycle.
16) The software project manager should ensure that quality assurance is integrated in
every aspect of project that is it should be integrated into every individual’s role, every
artifact, and every activity performed etc.
17) Boehm proposed three levels of the model: basic, intermediate and detailed. COCOMO
focuses mainly upon the intermediate model.
18) COCOMO is transparent. It can be seen how it works.
19) The activities of the process are organized in to seven major workflows
20) In most of the cases a process is a sequence of activities why because of easy to
understand, represent, plans and conduct.
21)An iteration represents the state of the overall architecture and the complete deliverable system.
22) An increment represents the current work in progress that will be combined with the
preceding iteration to form the next iteration.
23) Check pointing is a technique to add fault tolerance into computing systems. It basically
consists of saving a snapshot of the application's state, so that it can restart from that point in
case of failure.
24) Work breakdown structure is the “architecture” of the project plan and also an architecture
for financial plan.
25) A WBS is simply a hierarchy of elements that decomposes the project plan into discrete work
tasks.
26) Pragmatic planning is more dynamic in an iterative process
27) Organizational role may be fulfilled by a single individual or several different teams
28) SEPA Stands for Software Engineering Process Authority.
29) SEEA Stands for Software Engineering Environment Authority
30) The SEEA is responsible for automating the organization’s process, maintaining the
organization’s standard environment, Training projects to use the Environment &maintaining
organization-wide reusable assets.
31) The PRA – Project Review Authority is the single individual responsible for ensuring that a
software project
32) Quality is everyone’s into all activities and checkpoints
33) The environment must be the first-class artifact of the process.
34) Most managers know their resource expenditures in terms of costs and schedule. The problem
is to assess how much technical progress has been made.
35) Tracking actual versus planned staffing is a necessary is well-understood management metric
36) Breakage is defined as the average extent of change, which is the amount of software that
needs rework.
37) To analyze the data, software project control panel (SPCP) that maintains an on-line version
of the status of s/w provides the key advantage
38) In the project development lifecycle, the engineering phase concentrates on identification and
elimination of the risks associated with the resource commitments just before the production
stage.
39) Improve change freedom with the help of automated tools that support round-trip
engineering.
40) The next generation cost model developed on the basis of architecture-first approach