Project Management (April - 2017) [CBSGS - Paper Solution] {Mumbai University}

BOOK CODE: TYBSCIT-PM-007
APRIL – 2019
Mumbai University
B.Sc.IT (Information Technology)
CBSGS: Semester – VI
YEAR: APRIL – 2017
PROJECT
MANAGEMENT
By
Kamal Thakur

1
© Mumbai B.Sc.IT Study Kamal T.
Project Management
Paper Solution
 University: University of Mumbai
 Year: April – 2017
 Course: B.Sc.IT (Information Technology)
 Semester: VI
 Subject: Project Management
 Syllabus: CBSGS – 75:25 Pattern
BY
Kamal Thakur
B.Sc.IT (Mumbai University)
Web Designer | Blogger | YouTuber | E-Books Designer & Maker

2
Contact Me @
Email ID:
kamalthakurbscit@gmail.com
WhatsApp No.:
+91 – 8454975016
Social Network @
YouTube
http://bit.do/KamalT
Official Site
http://mumbaibscitstudy.com
Facebook
https://facebook.com/mumbaibscitstudy
Instagram
https://instagram.com/mumbaibscitstudy
Twitter
https://twitter.com/kamaltuniverse
Pinterest
https://in.pinterest.com/kamaltuniverse

3
PROJECT MANAGEMENT
(PAPER SOLUTION)
APRIL – 2017 | CBSGS – 75:25 PATTERN
BY
KAMAL THAKUR

4
Time: 2 ½ Hours Total Marks: 75
NOTES:
(1) All Question are Compulsory.
(2) Make Suitable Assumptions Wherever Necessary And State The Assumptions Made.
(3) Answer To The Same Question Must Be Written Together.
(4) Number To The Right Indicates Marks.
(5) Draw Neat Labeled Diagrams Wherever Necessary.
(6) Use of Non – Programmable Calculator is allowed.
Q.1. Attempt Any Two Questions: (10 Marks)
Q Explain the five basic Parameters of the Software Cost Model. .............................6
Q Explain the drawbacks of Waterfall Model..............................................................7
Q How software size can be reduced? Explain. ...........................................................7
Q How peer inspection helps in improving returns on investment? Explain. ............8
Q Summarize differences, in emphasis on different life cycle aspects, between the
two Life Cycle Stages. ................................................................................................9
Q Explain "Elaboration Phase" of the Life Cycle. .......................................................10
Q List all the five Artifact Sets. Explain Release Specification...................................10
Q Discuss Technical perspective of Software Architecture. ......................................12
Q Write a short note on Major Milestones................................................................13
Q Define WBS. Explain Evolutionary Work Break Down Structures. ........................14
Q Explain the Iteration Planning Process. ..................................................................14
Q Summarize the Life Cycle Emphasis associated with each Workflow. ..................15
Q Define Organizational Structure. What is a Line of Business Organization? Briefly
explain main features of default Line of Business Organization. ..........................17
Q Discuss various change categories defined on the basis of causes of change. .....18
Q Explain Mapping between Process Workflows and Software Development
Tools.........................................................................................................................18
Q How the Teams Gravity shifts over the Life Cycle? Explain. ..................................19

5
Q Define Metrics. Explain 7 Core Metrics. .................................................................20
Q Discuss the basic characteristics of Good Metrics..................................................21
Q Explain SPCP (Software Project Control Panel)......................................................22
Q What do you mean by "Tailoring the Process"? Explain the dimensions of
discriminating factors for tailoring the process. ....................................................23
Q How Modern Process Framework exploits several Critical Approaches for
resolving the five recurring issues of the Conventional Process. ..........................24
Q Discuss the Software Management Best Practices. ...............................................25
Q Discuss the two major improvements expected in the Next Generation Cost
Models. ....................................................................................................................25
Q Discuss the Culture Shifts necessary for the transition to Modern Software
Process.....................................................................................................................26
Q Discuss important trends in improving Software Economics. ...............................27
Q Give difference between Software Architecture and Design. ...............................28
Q Discuss issues related to Conventional WBS..........................................................29
Q Write a short note on SCO. .....................................................................................29
Q Explain EVS (Earned Value System). .......................................................................31
Q Summarize the balanced application of modern principles to achieve Economic
results.......................................................................................................................32

6
Q.1.Attempt Any Two Questions: (10 Marks)
Q.1. (A) Explain the five basic Parameters of the Software Cost Model.
SOLUTION
Parameters of the Software Cost Model:
Five basic Parameters of the Software Cost Model are listed below:
1) Size
2) Process
3) Personnel
4) Environment
5) Required Quality
Size:
The size of the end product, which is typically quantified in terms of the number of
source instructions or the number of function points required to develop the required
functionality.
Process:
The process used to produce the end product, in particular the ability of the process
to avoid non-value-adding activities.

7
Personnel:
The capabilities of software engineering personnel, and particularly their experience
with the computer science issues and the application domain issues of the project.
Environment:
The environment, which is made up of the tools and techniques available to support
efficient software development and to automate the process.
Required Quality:
The required quality of the product, including its features, performance, reliability, and
adaptability.
Q.1. (B) Explain the drawbacks of Waterfall Model.
SOLUTION
Drawbacks of Waterfall Model:
 Real products rarely follow this sequential flow.
 Because of iteration, changes can cause confusion as the project team proceeds.
 It is very difficult for customer to state all the requirements in One Time.
 Many projects face this uncertainty at beginning only, so it is very difficult to
design next phases.
 Time span required for each phase could not be specified.
 Naturally project requires more time.
 Project becomes lengthy also.
 Customer should have patience.
Q.1. (C) How software size can be reduced? Explain.
SOLUTION
Reducing Software Product Size:
Languages: UFP (Universal Function Points):
 These points are language independent.
 The basic units of the UFP are external user inputs, external outputs, internal
logical data groups, external data interfaces, and external inquiries.
Object-Oriented Methods and Visual Modelling:
 OO (Object-Oriented) Technology reduces the size of the program.
 An Object-Oriented methodology improves the team work and interpersonal
communications by improving the understanding between the end users and
developers of the system.

8
 Prevent change in one part of system to affect another.
 Early Risk Resolution.
Reusability:
 The "Reusability" is mostly implemented with stored functions and subprograms.
 The main reason for reuse is "lack" of money.
 Reuse is implemented across many projects if they are similar.
 Costs needed to build reusable and configure reusable components.
Commercial Components:
 Main advantage of using Commercial Components is that it saves custom
development efforts.
 Commercial Components usually need tailoring.
 Commercial Components have an impact on quality, cost, supportability, and the
architecture.
Packages:
 Various elements of analysis model are categorized into packages that are given
a representative name.
 Packages is a model element that can contain other model elements.
 The components help to model the physical aspect of an Object-Oriented
Software system representing the relationship between various components.
Q.1. (D)
How peer inspection helps in improving returns on investment?
Explain.
SOLUTION
 Inspections are also a good vehicle for holding authors accountable for quality
products.
 Inspections is more tangibly focused on integrated and executable aspects of the
overall system.
 Inspections allow gross blunders to be caught and feedback can be appropriately
channeled.
 These inspections ensure professional development of a team.

9
Q.2. (A)
Summarize differences, in emphasis on different life cycle
aspects, between the two Life Cycle Stages.
SOLUTION
Life-Cycle
Aspect
Engineering Stage
Emphasis
Production Stage
Emphasis
Risk Reduction Schedule, Technical
Feasibility
Cost
Products Architecture Baseline Product Release Baselines
Activities Analysis, Design, Planning Implementation, Testing
Assessment Demonstration, Inspection,
Analysis
Testing
Economics Resolving Diseconomies of
scale
Exploiting Economies of Scale
Management Planning Operations

10
Q.2. (B) Explain "Elaboration Phase" of the Life Cycle.
SOLUTION
Elaboration Phase of the Life Cycle:
Primary Objectives:
 Baselining the Architecture as rapidly as practical.
 Baselining the vision.
 Baselining a high-fidelity plan for the construction phase.
 Demonstrating that the baseline architecture will support the vision at a
reasonable cost in a reasonable time.
Essential Activities:
 Elaborating the vision.
 Elaborating the process and infrastructure.
 Elaborating the architecture and selecting components.
Primary Evaluation Criteria:
 Is the vision stable?
 Is the architecture stable?
 Does the executable demonstration show that the major risk elements have been
addressed and credibly resolved?
 Is the construction phase plan of sufficient fidelity, and is it backed up with a
credible basis of estimate?
 Are actual resource expenditures versus planned expenditures acceptable?
Q.2. (C) List all the five Artifact Sets. Explain Release Specification.
SOLUTION
Artifact Sets:
There are five types of Artifact Sets as listed below:
1) Requirements Set
2) Design Set
3) Implementation Set
4) Deployment Set
5) Management Set
Requirements Set:
 Vision Document
 Requirements Model(s)

11
Design Set:
 Design Model(s)
 Test Model
 Software Architecture Description
Implementation Set:
 Source Code Baselines
 Associated Compile-Time Files
 Component Executables
Deployment Set:
 Integrated Product Executable Baselines
 Associated Run-Time Files
 User Manual
Management Set:
a) Planning Artifacts:
 Work Breakdown Structure
 Business Case
 Release Specifications
 Software Development Plan
b) Operational Artifacts:
 Release Descriptions
 Status Assessments
 Software Change Order Database
 Deployment Documents
 Environment
Release Specification:
 Release Specification Artifacts and their inherent evaluation criteria are more
concerned early on with ensuring that the highest risk issues are resolved.
 Evaluation Criteria are transient snapshots of objectives for a given intermediate
Life-Cycle milestone.
 Evaluation Criteria are defined as Management Artifacts.

12
Q.2. (D) Discuss Technical perspective of Software Architecture.
SOLUTION
Architecture: A Technical Perspective:
 An Architecture Framework is defined in terms of views that are abstractions of
the UML Models in the Design Set.
 The Design Model includes the full breadth and depth of information.
 An Architecture View is an Abstraction of the design model; it contains only the
architecturally significant information.
 Most real-world systems require four views: Design, Process, Component, and
Deployment.
 The purpose of these views are as follows:
1) Design: Describes architecturally significant structures and functions of the
Design Model.
2) Process: Describes concurrency and control thread relationships among the
Design, Component, and Deployment Views.
3) Component: Describes the structure of the implementation set.
4) Deployment: Describes the structure of the deployment set.

13
Q.3. (A) Write a short note on Major Milestones.
SOLUTION
Major Milestones:
 Major Milestones are system wide events that are held at the end of each
development phase.
 They provide visibility to system wide issues, synchronize the management and
engineering perspectives and verify that the aims of the phase have been
achieved.
 Major milestones at the end of each phase, use formal, stakeholder approved
evaluation criteria & release descriptions.
Types of Major Milestones:
There are four types of Major Milestones as follows:
(1) Life-Cycle Objectives Milestone
(2) Life-Cycle Architecture Milestone
(3) Initial Operational Capability Milestone
(4) Product Release Milestone

14
Q.3. (B) Define WBS. Explain Evolutionary Work Break Down Structures.
SOLUTION
Work Break Down Structures (WBS):
 A Work Breakdown Structures (WBS) is simply a hierarchy of elements
that decomposes the project plan into the discrete work tasks.
 A WBS provides the following information structure:
 A Delineation of all significant work.
 A Clear task decomposition for assignment of responsibilities.
 A Framework for Scheduling, Budgeting and Expenditure Tracking.
Evolutionary Work Break Down Structures:
 First-Level WBS Elements are the workflows (Management, Environment,
Requirements, Design, Implementation, Assessment, and Deployment). These
elements are usually allocated to a single team and constitute the anatomy of a
project for the purposes of planning and comparison with other projects.
 Second-Level Elements are defined for each phase of the life cycle (Inception,
Elaboration, Construction, and Transition). These elements allow the fidelity of
the plan to evolve more naturally with the level of understanding of the
requirements and architecture, and the risks therein.
 Third-Level Elements are defined for the focus of activities that produce the
artifacts of each phase. These elements may be the lowest level in the hierarchy
that collects the cost of a discrete artifacts for a given phase, or they may be
decomposed further into several lower level activities that, taken together,
produce a single artifact.
Q.3. (C) Explain the Iteration Planning Process.
SOLUTION
Iteration Planning Process:
Inception Iterations:
 Normally only one iteration included.
 Large Scale Custom Developments may require two iterations.
Elaboration Iterations:
 Result in an Architecture.
 Fees critical use cases demonstrable at the end.
 Normally two iterations included.

15
Construction Iterations:
 Normally two major iteration require alpha release and beta release.
 Alpha release has 70% of total product breadth.
 Beta release has 95% total product breadth.
Transition Iterations:
 Normally One iteration included.
 Transitions beta release into final product.
Q.3. (D)
Summarize the Life Cycle Emphasis associated with each
Workflow.
SOLUTION
Workflow-wise Life Cycle & Emphasis:
Management Workflow:
 Inception – Prepare Business Case and Vision
 Elaboration – Plan Development
 Construction – Monitor and Control Development
 Transition – Monitor and Control Development
Environment Workflow:
 Inception – Define Development Environment and Change Management
Infrastructure.
 Elaboration – Install Development Environment and Change Management
Database.
 Construction – Maintain Development Environment and Software Change
order Database.
 Transition – Transition Maintenance Environment and Change Order Database.
Requirements Workflow:
 Inception – Define Operational Concept
 Elaboration – Define Architecture Objectives
 Construction – Define Iteration Objectives
 Transition – Define Release Objectives
Design Workflow:
 Inception – Formulate Architecture Concept
 Elaboration – Achieve Architecture Baseline
 Construction – Design Components
 Transition – Define Architecture and Components

16
Implementation Workflow:
 Inception – Support Architecture Prototypes
 Elaboration – Produce Architecture Baseline
 Construction – Produce Complete Componentry
 Transition – Maintain Components
Assessment Workflow:
 Inception – Assess Plans, Vision, Prototypes
 Elaboration – Assess Architecture
 Construction – Assess Interim Releases
 Transition – Assess Product Releases
Deployment Workflow:
 Inception – Analyze User Community
 Elaboration – Define User Manual
 Construction – Prepare Transition Materials
 Transition – Transition Product To User

17
Q.4. (A)
Define Organizational Structure. What is a Line of Business
Organization? Briefly explain main features of default Line of
Business Organization.
SOLUTION
Organizational Structure:
Organizational Structures form the architecture of the teams.
Line of Business Organization:
Software Line of Business Organizations are motivated by ROI, new Business
Discriminators, and Market Diversification & Profitability.
Features Of Default Organization:
The main features of Default Organization are as follows:
 Responsibility for process definition and maintenance is specific to a cohesive line
of business, where process commonality makes sense.
 Responsibility for process automation is an organizational role and is equal in
importance to the process definition role.
 Organizational roles may be fulfilled by a single individual or several different
teams, depending on the scale of the organization.

18
Q.4. (B)
Discuss various change categories defined on the basis of causes
of change.
Allocate the appropriate change category to the following changes:
(i) Port to New Platform
(ii) Loss of User Data
(iii) Use of colours to differentiate updates from the previous version
(iv) Browser expands but doesn’t collapse displayed entries
(v) Upgradation to improve Query Performance
SOLUTION
Change Categories:
Type 0: Critical Failures
Type 1: Bug or Defect that does not inspire the usefulness of the system.
Type 2: Enhancement
Type 3: Updating
Type 4: Other Changes
Allocate appropriate Change Category to the following changes:
i) Post to new platform – Type 4
ii) Loss of Uses Data – Type 0
iii) Use of colours to differentiate updates from the previous version – Type 2
iv) Browser Expands but doesn't Collapse displayed entries – Type 1
v) Upgradation to improve Query Performance – Type 3
Q.4. (C)
Explain Mapping between Process Workflows and Software
Development Tools.
SOLUTION
Mapping between Process Workflows and Software Development Tools:
1) Management Workflow: Controlling the process and ensuring win conditions of
for all stakeholders
2) Environment Workflow: Automating the process and evolving the maintenance
environment.
3) Requirements Workflow: Analyzing the problem space and evolving the
requirements artifacts.
4) Design Workflow: Modelling the solution and evolving the architecture and
design artifacts.
5) Implementation Workflow: Programming the components and evolving the
implementation and deployment artifacts.
6) Assessment Workflow: Assessing the trends in process and product quality.
7) Deployment Workflow: Transitioning the end products to the user.

19
Q.4. (D) How the Teams Gravity shifts over the Life Cycle? Explain.
SOLUTION
Teams Gravity shifts over the Life Cycle:
 Iterative Development should start with a Small Team.
 Maintenance Team will be smaller than Development Team.
 For Commercial Production Development, Size of Maintenance & Development
Teams may be same.

20
Q.5. (A) Define Metrics. Explain 7 Core Metrics.
SOLUTION
Metrics:
Software Metrics instrument the activities and products of the software
development/integration process.
The Seven Core Metrics:
Work and Progress:
 Purpose: Iteration Planning, Plan Vs. Actuals, Management Indicator
 Perspectives: SLOC, Function Points, Object Points, Scenarios, Test Cases, SCOs
Budgeted Cost and Expenditures:
 Purpose: Financial Insight, Plan Vs. Actuals Management Indicator
 Perspectives: Cost Per Month, Full-Time Staff Per Month, Percentage of Budget
Expended
Staffing and Team Dynamics:
 Purpose: Resource Plan Vs. Actuals, Hiring Rate, Attrition Rate
 Perspectives: People Per Month Added, People Per Month Leaving

21
Change Traffic and Stability:
 Purpose: Iteration Planning, Management Indicator of Schedule Convergence
 Perspectives: SCOs Opened Vs. SCOs Closed, By Type (0, 1, 2, 3, 4), By
Release/Component/Subsystem
Breakage and Modularity:
 Purpose: Convergence, Software Scrap, Quality Indicator
 Perspectives: Reworked SLOC Per Change, By Type (0, 1, 2, 3, 4), By
Rework and Adaptability:
 Purpose: Convergence, Software Rework, Quality Indicator
 Perspectives: Average Hours Per Change, By Type (0, 1, 2, 3, 4), By
MTBF and Maturity:
 Purpose: Test Coverage/Adequacy, Robustness For Use, Quality Indicator
 Perspectives: Failure Counts, Test Hours Until Failure, By
Q.5. (B) Discuss the basic characteristics of Good Metrics.
SOLUTION
Basic Characteristics of Good Metrics:
 It is considered meaningful by the customer, manager and performer
 It demonstrates quantifiable correlation between process perturbations and
business performance.
 It is objective and unambiguously defined.
 It display trends.
 It is a natural by-product of the process.

22
Q.5. (C) Explain SPCP (Software Project Control Panel).
SOLUTION
Software Project Control Panel (SPCP):
The Software Project Control Panel (SPCP) is an example of metrics automation
approach that collects, organizes & reports values and trends extracted directly from
the evolving engineering artifacts.
Start the SPCP:
The SPCP starts and shows the most current information that was saved when the user
last used the SPCP.
Select a Panel Preference:
The user selects from a list of previously defined default panel preferences. The SPCP
displays the preference selected.
Select a Value or Graph Metric:
The user selects whether the metric should be displayed for a given point in time or in
a graph, as a trend. The default for values is the most recent measurement available.
The default for trends is monthly.
Select to Superimpose Controls:
The user points to a Graphical Object and requests that the control values for that
metric and point in the time be displayed. In the case of trends, the controls are shown
superimposed with the metric.
Drill down to trend:
The user points to a Graphical Object displaying a point in the time and drills down to
view the trend for the metric.
Drill down to Point In Time:
The user points to a Graphical Object displaying a trend and drills down to view the
values for the metric.
Drill down to lower levels of information:
The users points to a Graphical Object displaying a point in time and drills down to view
the next level of information.
Drill down to Lower Level of Indicators:
The user points to a Graphical Object displaying an indicator and drills down to view
the breakdown of the next level of indicators.

23
Q.5. (D)
What do you mean by "Tailoring the Process"? Explain the
dimensions of discriminating factors for tailoring the process.
SOLUTION
Tailoring The Process:
Software Management efforts span a broad range of domains. While there are
some universal themes and techniques, it is always necessary to tailor the
process to the specific needs of the project at hand.
Dimensions of Discriminating Factors for tailoring the Process:
In tailoring the management process to a specific domain or project, there are
two dimensions of discriminating factors: Technical Complexity and
Management Complexity.
Figure 1: The Two Primary Dimensions Of Process Variability

24
Q.6. (A)
How Modern Process Framework exploits several Critical
Approaches for resolving the five recurring issues of the
Conventional Process.
SOLUTION
Five Recurring Issues of Conventional Projects:
1) Protracted Integration and Late Design Breakage are resolved by forcing
integration into the engineering stage. This is achieved through
continuous integration of an architecture baseline supported by
executable demonstrations of primary scenarios.
2) Late Risk Resolution is resolved by emphasizing an architecture-first
approach, in which the high-leverage elements of the system are
elaborated early in the life cycle.
3) The analysis paralysis of a Requirements-Driven Functional Decomposition
is avoided by organizing lower level specifications along the content of
releases rather than along the product decomposition (by subsystem, by
component, etc.).
4) Adversarial Stakeholder Relationships are avoided by providing much
more tangible and objective results throughout the Life Cycle.

25
5) The conventional Focus on Documents and Review Meetings is replaced
by a focus on demonstrable results and well-defined sets of artifacts, with
more-rigorous notations and extensive automation supporting a
paperless environment.
Q.6. (B) Discuss the Software Management Best Practices.
SOLUTION
Software Management Best Practices:
 Formal Risk Management.
 Agreement on Interfaces.
 Formal Inspections.
 Metric-Based Scheduling and Management.
 Binary Quality Gates at the inch-pebble level.
 Program Wide Visibility of Progress versus Plan.
 Defect Tracking Against Quality Targets.
 Configuration Management.
 People-Aware Management Accountability.
Q.6. (C)
Discuss the two major improvements expected in the Next
Generation Cost Models.
SOLUTION
Two major improvements expected in the Next Generation Cost Models:
1) Separation of the engineering stage from the production stage will force
estimators to difference between architectural scale and implementation
size. This will permit greater accuracy and more-honest precision in life-
cycle estimates.
2) Rigorous Design Notations such as UML will offer an opportunity to define
units of measure for scale that are standardized and therefore can be
automated and tracked. These measures can also be traced more straight-
forwardly into the costs of production.

26
Q.6. (D)
Discuss the Culture Shifts necessary for the transition to Modern
Software Process.
SOLUTION
Culture Shifts for the Transition to Modern Software Process:
Culture Shifts necessary for the transition to Modern Software Process as follows
below:
 Lower Level and Mid-Level Managers are performers.
 Requirements and Designs are fluid and tangible.
 Ambitious Demonstrations are encouraged.
 Good and Bad Project Performance is much more obvious earlier in the Life Cycle.
 Early Increments will be immature.
 Artifacts are less important early, more important later.
 Real issues are surfaced and resolved systematically.
 Quality Assurance is everyone's job, not a separate discipline.
 Performance issues arise early in the Life Cycle.
 Investments in Automation are necessary.
 Good Software Organizations should be more profitable.

27
Q.7.Attempt Any Three Questions: (15 Marks)
Q.7. (A) Discuss important trends in improving Software Economics.
SOLUTION
Improving Software Economics:
The Software Economics can be improved by using a "balanced" approach as the key.
The five key parameters that can be help in improving the software economics are:
1. Reducing the Product Size (Number of Lines of Code) and Complexity of the
Software.
2. Improving the Software Development Process.
3. Using more-skilled personnel i.e. improving the team effectiveness.
4. Creating better environment by improving the automation with more
appropriate tools and technologies.
5. Achieving required quality by peer inspections.
Trends on which the Five Key Parameters depend:
Size: (describes Abstraction and Component Based
Development Technologies)
 High Level Programming Languages (C++, Java, VB)

28
 Object-Oriented Methods and Visual Modelling (Analysis, Design &
Programming)
 Reusability
 Commercial Exponents
 Packages
Process: (involves Methods and Techniques)
 Iterative Development
 Process maturity models such as CMM
 Architecture-first development
Personnel: (describes the Effectiveness of the
Development Team)
 Training to develop the personnel skills
 Team Work
 Win-Win Culture
Environment: (involves Automated Tools and Technologies)
 Integrated tools such as Complier, Editors and Debuggers
 Hardware Performance
 Automated Coding, Documentation, Testing and Analyses.
Quality: (describes the Performance, Reliability,
Accuracy issues)
 Hardware Platform Performance
 Peer Inspections
 Statistical Quality Control
Q.7. (B) Give difference between Software Architecture and Design.
SOLUTION
Software Design Vs. Software Architecture:
Software Architecture:
 Software Architecture is a plan that gives enough detail to produce a software
design.
 Architecture constrains designs to achieve an organization's business and
technology strategy.
 Software architecture places big-picture constraints on the design to ensure that
it aligns with the business and technology strategy of an organization.

29
 This includes considerations such as compliance, technology standards and
operational efficiency.
 Architecture is intended to prevent designs from repeating known mistakes or
being inconsistent with the rest of the organization.
 It could be said that architecture is global optimization of software and design is
local optimization.
 Architecture is analogous to the structure of a building that provides constraints
and basic services that are used by the interior designs on each floor.
Software Design:
 Software Design is a plan that gives enough detail to implement software.
 Designs constrain implementation to achieve objectives such as consistency,
reliability and security.
 Software design provides everything that software developers need to know to
produce consistent software that implements the required functionality.
 This includes specifications of services, components, integrations, data models
and algorithms.
Q.7. (C) Discuss issues related to Conventional WBS.
SOLUTION
Conventional Work Breakdown Structures (WBS):
There are three fundamental issues with Conventional WBS as follows:
 They are prematurely structured around the product design.
 They are prematurely decomposed, planned, and budgeted in either too much
or too little detail.
 They are Project-Specific, and Cross-Project Comparisons are usually difficult or
impossible.
Q.7. (D) Write a short note on SCO.
SOLUTION
Software Change Order (SCO):
 The atomic unit of software work that is authorized to create, modify, or
obsolesce components within a configuration baseline is called a Software
Change Order (SCO).
 Software Change Orders (SCO) are a key mechanism for partitioning, allocating,
and scheduling software works against an established software baseline and for
assessing progress and quality.
 The example of SCO as shown in figure below is a good starting point for
describing a set of change primitives.

30
Figure 2: The Primitive Components of a Software Change Order
Title:
 Title is composed by the user of the software who is an external person and tells
about his major problem regarding the software.
 Afterwards, this title is compiled by the originator and finalized by the
configuration control board (CCB).

31
Description:
 Description is composed of originators name, date is mentioned. When CCB
finalized title, then addition to that CCB also assigned SCO identifier and version.
These two fields are also mentioned in the description.
 The written description is in brief formats including all the details such as
problem codes, view snapshots, error and alert message and few other relevant
data by which change is stated in simple words.
Metrics:
 This is one of the important entities of the SCO.
 It is used for planning, scheduling and making improvement.
Resolution:
 This filed contains the analyst that means the person who is perform change,
implement on that component which should be change, metrics and related
description.
Assessment:
 This field contains the assessment methods such as Inspection, Analysis,
Demonstrate and Testing etc.
Disposition:
 This field contains the state which is approved by the Configuration Control
Board (CCB).
Q.7. (E) Explain EVS (Earned Value System).
SOLUTION
Basic Parameters of Earned Value System (EVS) are:
 Expenditure Plan: Planned Spending Profile for a Project.
 Actual Progress: Technical Accomplishment Relative to Planned Progress.
 Actual Cost: Actual Spending Profile for a Project.
 Earned Value: Value that represents the Planned Cost of Actual Progress.
 Cost Valiance: Different between the Actual Cost and Earned Value.
 Schedule Valiance: Difference between Planned Cost & Earned Value.

32
Q.7. (F)
Summarize the balanced application of modern principles to
achieve Economic results.
SOLUTION
Modern Iterative Development Process Framework is characterized by –
 Continuous Round-Trip Engineering from requirements to test at evolving levels
of abstraction.
 Achieving High-Fidelity Understanding of the drivers (20%) as early as practical.
 Evolving the artifacts in Breadth & Depth Based on Risk Management Priorities.
 Postponing Completeness and Consistency Analyses until later in the Life Cycle.
☮☮☮

Project Management (April - 2017) [CBSGS - Paper Solution] {Mumbai University}

Recommended

Recommended

More Related Content

Similar to Project Management (April - 2017) [CBSGS - Paper Solution] {Mumbai University}

Similar to Project Management (April - 2017) [CBSGS - Paper Solution] {Mumbai University} (20)

More from Mumbai B.Sc.IT Study

More from Mumbai B.Sc.IT Study (20)

Recently uploaded

Recently uploaded (20)

Project Management (April - 2017) [CBSGS - Paper Solution] {Mumbai University}