LPU

ASSIGNMENT
NO2 OF
PRINCIPLES OF
SOFTWARE
ENGINEERING
SUBMITTED TO- SUBMITTED BY-
MR.AMANDEEP VARUN
KATOCH
E3801B53
 BCA-MCA
Q1. Implement the concept of function point in your
software project.
Ans 1
FPA is a method to break systems into smaller
components, so they can be better understood and
analyzed. It also provides a structured technique for
problem solving. Function Point Analysis is a structured
method to perform functional decomposition of a
software application. Function points are a unit
measure for software much like an hour is to measuring
time, miles are to measuring distance or Celsius is to
measuring temperature. Function Points are interval
measures much like other measures such as
kilometres , Fahrenheit, hours , so on and so forth.
Function Points measure software by quantifying its
functionality provided to the user based primarily on
the logical design.

Q2. Write down the advantages of using different

architecture styles.

Ans 2 Benefits of Architectural Styles

1.Architectural styles provide several benefits.

1. The most important of these benefits is that they

provide a common language.
2. Another benefit is that they provide a way to have
a conversation that is technology-agnostic.
3. This allows you to facilitate a higher level of
conversation that is inclusive of patterns and
principles, without getting into the specifics. For
example, by using architecture styles, you can talk
about client-server versus N-Tier.
4. Styles
5. Common language
 6. It is also technology-agnostic
7. Defined constraints
8. Exhibits well-known Quality Attributes
9. Enables forecasting architecture impact
10. Enables architecture analysis
11. Promotes design reuse
12. Promotes artifact reuse

Q3. Create process planning document for any software

project.
Ans 3 Process Planning

Products and their components are designed to perform

certain specific functions. Every product has some
design specifications which ensure its functionality
aspects. The task of manufacturing is to produce
components such that they meet design specifications.
Process planning acts as a bridge between design and
manufacturing by translating design specifications into
manufacturing process details. It refers to a set of
instructions that are used to make a component or a
part so that the design specifications are met, therefore
it is major determinant of manufacturing cost and
profitability of products. Process planning answers the
questions regarding required information and activities
involved in transforming raw materials into a finished
product. The process starts with the selection of raw
material and ends with the completion of part. The
development of process plans involves mainly a set of
following activities;
 • Analysis of part requirements
• Selection of raw workpiece
• Selection of manufacturing operations and their
sequences
• Selection of machine tools
• Selection of tools, tool holding devices, work
holding devices and inspection equipments
• Selection of manufacturing conditions i.e. cutting
speed, feed and depth of cut.

• Determination of manufacturing times

Q4. How will you implement the concept of COCOMO

model? Take the example of any live project you are
working on.
Ans4
1. Embedded software system on microcomputer
hardware.
2. Basic COCOMO predicts a 45 person-month
effort requirement
3. Attributes = RELY (1.15), STOR (1.21), TIME
(1.10), TOOL (1.10)
4. Intermediate COCOMO predicts
a. 45*1.15*1.21.1.10*1.10 = 76 person-months.
5. Total cost = 76*$7000 = $532,000
6. Algorithmic cost models provide a basis for
project planning as they allow alternative
strategies to be compared.
7. Alternative 1: Use more powerful hardware to
reduce TIME and STOR attribute multipliers.
 8. Alternative 2: Invest in support environment.

Q5. As a project manager perform project scheduling

and staffing functions in your
organization when your company is starting number of
new ventures.

Ans 5 In providing project management training to non-

profits and other smaller organizations, I am often
asked to recommend software for project management
scheduling and resource planning. I recommend
Microsoft Project, for someone who has $600 to spend
on software and another for training. For those whose
scheduling needs or resources are more modest,
however, I've looked around to find freeware on the
Web, and haven't so far found anything to recommend.
(Aha, but that is changing, see the downloads below
from other sources!)

Over the years I've seen low-budget projects use

Microsoft EXCEL spreadsheets for scheduling and
resource management, with columns to track planned
and actual start and finish dates. While this approach
is derided by the pros, it is sometimes the practical
solution for a small project in a small organization. To
advance the state of the art, I've experimented here
with a Gantt chart type schedule using the EXCEL
spreadsheet format. This attempts to provide some
features of the fancy project management scheduling
programs within the constraints of the spreadsheet
format and normal EXCEL user.

Using EXCEL for this purpose has two limitations. First,

it clearly can't do all the things that dedicated PM
software programs can do, especially in terms of
graphics displays and database flexibility. Second, it
pushes the complexity of the EXCEL spreadsheet logic
beyond what some beginning EXCEL users might be
comfortable with. (Helpful users have certainly pushed
some versions beyond my skill level, too.) That said, it
is way better than nothing, it may help you learn more
about EXCEL, and certainly more about project
scheduling, and it's FREE! So you can't beat the price.

(BTW, my personal experience has been that it is often

easier to make my own EXCEL spreadsheet than to
master someone else's, so bear that in mind. I've tried
to keep it simple and have not used any macros or VB,
so it should be pretty straightforward. Good luck!)

At this point, I'm sorry to say that these are no longer

supported. I lost track of the subsequent updates
made by others and haven't had the time or EXCEL
knowledge to get into them

Q6. Create risk planning document for any software

project.
Ans 6 Developing an effective Risk Management Plan is
an important part of any project. Unfortunately, this
step is often avoided with the "deal with it later"
attitude. If everything goes smoothly and without
incident, that approach does no harm. But normally,
issues do arise and without a well developed plan, even
small issues can become emergencies.

There are different types of Risk Management and

different uses that include calculating credit-
worthiness, planning for adverse events (i.e. disasters),
determining how long the warranty on a product should
last, calculating insurance rates, and many more. In
this document we will look at Risk Management from
the standpoint of planning for adverse events.