1. Chapter 2: The Software Development Process. By : Anisah A
Azizan
2. Overview The large and growing body of software development
organizations implement process methodologies.
3. Software Deployment Activities. There are three types of
software Deployment activities: I. Planning. II. Implementation,
testing and documenting. I. Deployment and maintenance.
4. Planning. I. Customers typically have an abstract idea of
what they want as an end result, but not what software should do.
Skilled and experienced software engineers recognize incomplete,
ambiguous, or even contradictory requirements at this point.
5. Implementation, testing and documenting I. Implementation is
the part of the process where software engineers actually program
the code for the project. II. Software testing is an integral and
important phase of the software development process. This part of
the process ensures that defects are recognized as soon as
possible. III. Documenting the internal design of software for the
purpose of future maintenance and enhancement is done throughout
development. This may also include the writing of an API, be it
external or internal. The software engineering process chosen by
the developing team will determine how much internal documentation
(if any) is necessary. Plan-driven models (e.g., Waterfall)
generally produce more documentation than Agile models.
6. Deployment and maintenance I. Deployment starts after the
code is appropriately tested, approved for release, and sold or
otherwise distributed into a production environment. This may
involve installation, customization (such as by setting parameters
to the customer's values), testing, and possibly an extended period
of evaluation. II. Software training and support is important, as
software is only effective if it is used correctly. III.
Maintaining and enhancing software to cope with newly discovered
faults or requirements can take substantial time and effort, as
missed requirements may force redesign of the software.
7. Software development models. Waterfall model 1.Requirements
specification (Requirements analysis) 2.Software design
3.Implementation and Integration 4.Testing (or Validation)
5.Deployment (or Installation) 6.Maintenance
8. Waterfall Process.
9. Waterfall Software Development Process.
10. Spiral ModelI. formulate plans to: identify software
targets, selected to implement the program, clarify the project
development restrictions; II. Risk analysis: an analytical
assessment of selected programs, to consider how to identify and
eliminate risk; III. the implementation of the project: the
implementation of software development and verification; IV.
Risk-driven spiral model, emphasizing the conditions of options and
constraints in order to support software reuse, software quality
can help as a special goal of integration into the product
development. However, the spiral model has some restrictive
conditions, as follows: V. The spiral model emphasizes risk
analysis, and thus requires customers to accept this analysis and
act on it. This requires both trust in the developer as well as the
willingness to spend more to fix the issues, which is the reason
why this model is often used for large-scale internal software
development. VI. If the implementation of risk analysis will
greatly affect the profits of the project, the spiral model should
not be used. VII. Software developers have to actively look for
possible risks, and analyze it accurately for the spiral model to
work
11. Good Cooperation make a good software development.
12. All these stuffs help to avoid this situation..=)
