c

cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc

ccccccccccccccc


ccc
 c
c  c

 c
cccccccccccccccccccccccccccccccccccccccccccccccccccc c  c

ccccccccccccccccccccccccccccccccccccccccccccccccccc c
c

cccccccccccccccccccccccccccccccccccccccccccccccccc
c
cc

c +c (
"

c $*
,$c'

c
+c * -)c' )c
In this tem paper I have talked about the
design issue of a large software.In this I '
c   
c
have covered the difference model used for +#c .c/c
making a software and after that I have c ' c& 
cc
cc  cc
specified which model is used for making a 
 c
large software or we can say developing a c & c0c
large software.I have also talked about main #c
c0c
features of a large software.
1c


cc,
* c  c
 !c 
 c)
$
c
c 
"
c 2c 
 c

cc
#c c$

c c %)c% c  c
#c% c& c'
c (
 $
c
c3  c
##c(

)*c'
c i.c 


c
c 
#+c "$ c")"c /c 
"

cc
$
c cc"
cc
#c* c'
c
c
 c c

c 
"
c c

hen we try to design a software either c

large or small we have to keep certain things
4(c
in mind and they are how reliable a software
is,is the functioning of software is same as
that we wanted or there is a bug we have to
sort out.The programmer has to keep
different crisis and risk in mind which may
come while developing the software.There
are different model for developing a
software for a large software we use a
specific model because all other model have
problems in creating the software so we use c
a particular model to develop a software.
& cc c c$
c

#c cc'
c c c5$
c
e have four different model or more used
In this we try to gather requirement i.e the
for developing a software they are as
needs require to built our software.After all
follows
our requirement is fulfilled we move to next
#cc% c c$
c step.

The water fall model is also know as the top c c
 c
down model. It is highly structured physical
ÿere we talk about the designing part.the
environments in which after-the-fact
design is divided into three parts Top level,
changes are prohibitively costly, if not
Detailed, Built from requirements.
impossible. The main problem in water fall
model is that if we want to make any change iii.c $*$ 

in our model we have to check it from the
top though we want to make any change in ÿere we try to put our code to function our
middle but we have to start from the software the way we want it to function.
begning.
iv.c c
 c"

cccc
This is done first by the developer and than
c by the analyst who are behind the project i.e
people who are working for the project.This
c is done to check whether any error has
ocuured or not.
 v.c ,)
The software is delivered to specific
customer.

##ccc(

)*cc'
˜-
In this model we make a constant change in
our software until the customer is satisfied
with the project we make the constant
changes the way the customer requires.
c
cc
cc

  c
c

cc

In this model the Software Requirements are

well defined, but realization may be delayed
c and The basic software functionality are
required early.
& c#c*

)*c$
c

The model start from requirement gathering #c* c$

˜-
and it move s ahead goes on for the
The most important of all because it is used
development of software as per the customer
to develop the large software.It is the most
satisfaction.The main falut in this model is
reliable model for developing large
high costing and some time the quality of
software. The main advantage of this model
software goes down.
is that it combine advantages of top-down
#+ccc "$ c")"c$
˜
and bottom-up concepts. Also known as the
spiral lifecycle model.
In this model we goes on updating our
software from the basic level and move The main structure of this model˜
forward doing the same.
 This is usually a scaled-down system, and
represents an approximation of the
characteristics of the final product.

A second prototype is evolved by a fourfold

procedure˜

1.c Vvaluating the first prototype in

terms of its strengths, weaknesses,
and risks.

2.c Defining the requirements of the

second prototype.
c
3.c Planning and designing the second
& ccc
* c$
c prototype.

4.c Constructing and testing the second

4(
prototype.
The system requirements are defined in as
SO spiral model is most important of all the
much detail as possible. This usually
model because it is like a circle and we
involves interviewing a number of users
check the project after every circle is
representing all the external or internal users
completed so the chances of error is less so
and other aspects of the existing system.
that¶s why we use this model for large
A preliminary design is created for the new program.
system. This phase is the most important
c
part of "Spiral Model". In this phase all
possible alternatives, which can help in +c (
"

c $*
,$c
developing a cost effective project are
'

c
analyzed and strategies to use them are
decided. This phase has been added +c c c  * -)c ' )c '
c
specially in order to identify and resolve all
  
c
the possible risks in the project
development. If risks indicate any kind of
uncertainty in requirements, prototyping
may be used to proceed with the available
data and find out possible solution in order
to deal with the potential changes in the
requirements.

A first prototype of the new system is

constructed from the preliminary design.
 c
& c2c .c/c$
c

ISO 9000 describes standards for a formally

c organized process to manufacture a product
& c1c'' c$
c and the methods of managing and
monitoring progress. Although the standard
The Capability Maturity Model Integration was originally created for the manufacturing
(CMMI) is one of the leading models and sector, ISO 9000 standards have been
based on best practice. Independent applied to software development as well.
assessments grade organizations on how Like CMMI, certification with ISO 9000
well they follow their defined processes, not does not guarantee the quality of the end
on the quality of those processes or the result, only that formalized business
software produced. CMMI has replaced processes have been followed.
CMM.
c ' 6c &474c .&c


84c.&%4c


&
c0c


in which all work on adding new features is

suspended, shifting the effort towards
fixing bugs and improving the user
#cc .c/c
experience. The addition of new features
may have a disruptive effect on other parts
of the program, due both to the introduction
of new, untested source code or resources
and to interactions with other features; thus,
a feature freeze helps improve the program's
stability.
#
c0c 7.c hat happens if we need to add a new
A "
c 0, in which no changes
whatsoever are permitted to a portion or the

c

c
entirety of the program's source code.
Particularly in large software systems, any
change to the source code may
have unintended consequences, potentially
introducing new bugs; thus, a code freeze
helps ensure that a portion of the program
that is known to work correctly will
continue to do so. Code freezes are often
employed in the final stages of development,
when a particular release or iteration is
being tested, but may also be used to prevent
changes to one portion of a program while
another is undergoing development.
1c


cc,
5.c A team of programmers have to write
different parts of the code that will
work together
6.c ÿow do we make sure that the software
does what it is supposed to do?
feature to the software?c
2c 
c
Large Software Systems Often˜ Do not
provide the desired functionality, Take too
long to build, Cost too much to build,
Require too much time, space, or other
resources to run, cannot evolve to meet
changing needs.
Software¶s Chronic Crisis˜
c
Three-decades later (1994) an article in
Scientific American by . ayt Gibbs was
Titled˜ ³Software¶s Chronic Crisis¶¶
1.c For every 6 large software projects
* c
 c that become operational, 2 of them
are cancelled


c)
$
c 2.c On the average software
development projects overshoot their
1.c The team members have to schedule by half
communicateand interact with each 3.c 3 quarters of the large systems do not
other A single software developer may provide required functionality
not be able to do the job in the required Vxamples˜
amount of time, developers have to
work as a team. 1.c Because of software related
problems in its automated baggage-
2.c The team member has to communicate
handling system, opening of
and interact with each other. Denver¶s big, state-of-the art,
3.c Specification of a large software international airport was delayed
product is more complicated than just almost a year in 1993
saying write a program that sorts a set
of integers. 2.c NASA¶s Mars Climate Orbiter was
lost in 1999 ,Cause˜ failed translation
4.c For a large software project one has to
of Vnglish units to metric units
carefully think about the design of the
software before starting to write code. 3.c NASA¶s Mars Sojourner software
deadlocked. Cause˜ Priority
 inversion. Priority inversion occurs d.c Poor quality of software
when a process that has higher e.c Poor maintainability
priority is waiting for a process for a f.c Ad hoc software
lower priority to release a lock. development results in
ÿowever, since the process holding such problems
the lock has lower priority it does not
get scheduled and the system a)c No planning of development
deadlocks. work (e.g. no milestones
defined)
c %)c % c 
 c b)c Deliverables to user not
(

$
c
c3
 c identified
c
1.c Customer¶s needs are hard to c)c Poor understanding of user
discover and record requirements
2.c Customer¶s needs change
d)c No control or review
with time
3.c The larger the system the e)c Technical incompetence of
more potential interactions developers
among components
4.c Several people must f)c Poor understanding of cost
cooperate communication and effort by both developer
complexity among people and userc
can grow.
Challenge in large projects˜ /c 
"

c
It is generally felt in our community, that
1.c Developing large/complex with each generation large detector, software
software application is very is becoming a bigger and bigger problem. If
challenging we extrapolate this trend to the SSC era,
software would be a very big problem
(i)c Vffort intensive indeed. Many people are inventing or using
(ii)c ÿigh cost new tools to attack the software problem,
(iii)c Long development time but some of these tools are like aspirins,
(iv)c Changing needs for users they alleviate some pain but don¶t cure the
(v)c ÿigh risk of failure, user acceptance, disease. e need to understand the real
performance, maintainability causes of our current problems, before we
can find the real solutions.
2.c Quite different from one-time The intent of this paper is to discuss the
programs where author and user implications that the process of developing
are same! very large software or very large
information systems (VLIS) has on the
approach to the software engineering
i.c c



c
c
 problem. Although the same SV problems
a.c Schedule slippage are found in many domains, they take on a
b.c Cost over-runs unique set of constraints when considered in
c.c Does not solve user¶s the context of developing VLIS. It is our
problem position that possibilities for enhancing the
software development process are functions
of the domain in which one participates.

c4&464c

Link˜-
1.c http˜//en.wikipedia.org/wiki/aterfall_
model

2.c http˜//en.wikipedia.org/wiki/aterfall_
model

3.c http˜//www.softdevteam.com/Increment
al-lifecycle.asp

4.c http˜//en.wikipedia.org/wiki/Spiral_mod
el

5.c http˜//en.wikipedia.org/wiki/Project_ma
nagement_softwarec

Book˜-

1.c Pressman , software engineering A

practitioner¶s approach
2.c An integrated approach to software
engineering , 3rd edition by Pankaj
Jalote