Vous êtes sur la page 1sur 4

1.

Software danger

 Capability and capacity of machines increased.


 People became more aware about the use of computers.
 The cost of Hardware became low.
 Computer system improved fast with the help of more powerful machines and
availability of user friendly operating system.

Software requirements increased because the use of computer and its applications
increased. For the development of software system the attention shifted from the simple
programming. For the development of software systems, the techniques for simple
writing program could not be upgraded. Thus the software find in computer world
always in the middle of software danger. Software danger can be described as a group
of errors and troubles which grows during the period of development of software. These
software dangers spread very quickly.

Importance of software danger in concerned to software Engineering

To resolution of software danger with computerized techniques is used as a term of


software Engineering. Software Engineering term may be used or defined as a set of
those programs and thoughts that helps in solutions of computer problems or software
danger. Development of software and regular maintenance of it is the main part of
software Engineering. Resolution of problems which creates by soft danger is the
discipline which is concerned to software Engineering.

2. The importance of software engineering


Software engineering is important because specific software is needed in almost every
industry, in every business, and for every function. It becomes more important as time
goes on – if something breaks within your application portfolio, a quick, efficient, and
effective fix needs to happen as soon as possible.

Generally, software development cycle presupposes following steps:

 Planning
 Feasibility analysis
 Product design
 Coding
 Implementation and Integration
 Software Testing
 Installation and Maintenance

3. The principles which play a major role in development of software.

Principles of software development


A set of rules which is made on the basis a number of observations done by user is
called the principles of software development. We have described the software
development principles which are given below:
 Quality on preference - Quality is the first objective of software development
process. Because a low level of quality not accepted by the user or client. We
have a lot of definitions about the quality product.

 Possibility of high quality software - Scope of higher quality is always there.


For getting the high quality many techniques, design inspections on time and
hired the best employee for this can be adopted.

 Be on time delivery - The better way is to send the sample to the customer so
that he can use that software and give feedback. On the basis of feedback
developer can take charge and developed the software according to the need of
customer.

 Fix the problem - Before getting any solution of problem fix the problem which
cause is customer needs. After getting the problem we are trying to use alternate
solution of that problem basis on time, cost and risk factor.

 Valuation of alternate design - When we know the need of customer then we


observed much kind of algorithms and architectural so that with the help of them
we can build the software. We select that alternate who have the quality of safety,
alteration and more functional.

 Selection of appropriate process model - Software development process


model have a large area of choice just like waterfall, prototype and spiral module
are the suitable examples for this. But there is a fact that every process is not
suitable or in favor every time.

 Minimum gap between client and developer - According to famous Dijkestra


intellectual gap may be describe, is the distance between the real world problem
and the computerized solution to the problem. If the maintenance of the software
is easy then the gap will be low. With the help of the object oriented design and
jack system of development method we can find that the structure of software
which will be near real world structure.

 Design for change - The techniques or method which is used in development


process of software should have capacity of change.

 Reduce tricks - We should try to reduce of those programs and code who
makes compaction in that process.

 Management - In the comparisons of good technology, good management is the


best option because it helps the employees to motivate them for doing their
duties in the proper way. Management planning cannot be done for a long period
because its base is time and situation which can change any time.
 Right person is the base of success - For the success of any planning we
need to experts, experienced and skilled person. An expert can provide the best
output with those sources who are not enough in normal condition.

 Use carefully - For getting the best output it is necessary to use different method
and techniques with carefully otherwise they provide the wrong output.

 Keep updated - In the present time, this world is more progressive and
competitive so to survive in the present time it is necessary to stay updated every
time for new technology and their risk factors.

4. Principles of Software Design

Some of the commonly followed design principles are as following.

 Software design should correspond to the analysis model: Often a design


element corresponds to many requirements, therefore, we must know how the
design model satisfies all the requirements represented by the analysis model.

 Choose the right programming paradigm: A programming paradigm describes


the structure of the software system. Depending on the nature and type of
application, different programming paradigms such as procedure oriented,
object-oriented, and prototyping paradigms can be used. The paradigm should
be chosen keeping constraints in mind such as time, availability of resources and
nature of user's requirements.

 Software design should be uniform and integrated: Software design is


considered uniform and integrated, if the interfaces are properly defined among
the design components. For this, rules, format, and styles are established before
the design team starts designing the software.

 Software design should be flexible: Software design should be flexible enough


to adapt changes easily. To achieve the flexibility, the basic design concepts
such as abstraction, refinement, and modularity should be applied effectively.

 Software design should ensure minimal conceptual (semantic) errors: The


design team must ensure that major conceptual errors of design such as
ambiguousness and inconsistency are addressed in advance before dealing with
the syntactical errors present in the design model.

 Software design should be structured to degrade gently: Software should be


designed to handle unusual changes and circumstances, and if the need arises
for termination, it must do so in a proper manner so that functionality of the
software is not affected.
 Software design should represent correspondence between the software
and real-world problem: The software design should be structured in such
away that it always relates with the real-world problem.

 Software reuse: Software engineers believe on the phrase: 'do not reinvent the
wheel'. Therefore, software components should be designed in such a way that
they can be effectively reused to increase the productivity.

 Designing for testability: A common practice that has been followed is to keep
the testing phase separate from the design and implementation phases. That is,
first the software is developed (designed and implemented) and then handed
over to the testers who subsequently determine whether the software is fit for
distribution and subsequent use by the customer.

 Prototyping: Prototyping should be used when the requirements are not


completely defined in the beginning. The user interacts with the developer to
expand and refine the requirements as the development proceeds. Using
prototyping, a quick 'mock-up' of the system can be developed.

JENIFER S. CUARESMA

Vous aimerez peut-être aussi