What are five stages of developing program?

Answer 1

1.Review the input, processing, output, and storage requirements.

2.Develop the logic for the program

3.Write the program using a programming language.

4.Test and debug the program.

5.Complete the program documentation.

Answer 2

The Rational Unified Process® is a Software Engineering Process. It provides a disciplined approach to assigning tasks and responsibilities within a development organization. Its goal is to ensure the production of high-quality software that meets the needs of its end-users, within a predictable schedule and budget. The Rational Unified Process enhances team productivity, by providing every team member with easy access to a knowledge base with guidelines, templates and tool mentors for all critical development activities. The Rational Unified Process activities create and maintain models. Rather than focusing on the production of large amount of paper documents, the Unified Process emphasizes the development and maintenance of models-semantically rich representations of the software system under development. The Rational Unified Process is a guide for how to effectively use the Unified Modeling Language (UML). The UML is an industry-standard language that allows us to clearly communicate requirements, architectures and designs.

The Rational Unified Process divides one development cycle in four consecutive phases [10]

• Inception phase

• Elaboration phase

• Construction phase

• Transition phase

Each phase is concluded with a well-defined milestone-a point in time at which certain critical decisions must be made, and therefore key goals must have been achieved [2].

The phases and major milestones in the process.

Each phase has a specific purpose.

Inception Phase

During the inception phase, you establish the business case for the system and delimit the project scope. To accomplish this you must identify all external entities with which the system will interact (actors) and define the nature of this interaction at a high-level. This involves identifying all use cases and describing a few significant ones. The business case includes success criteria, risk assessment, and estimate of the resources needed, and a phase plan showing dates of major milestones.

Elaboration Phase

The purpose of the elaboration phase is to analyze the problem domain, establish a sound architectural foundation, develop the project plan, and eliminate the highest risk elements of the project. To accomplish these objectives, you must have the "mile wide and inch deep" view of the system. Architectural decisions have to be made with an understanding of the whole system: its scope, major functionality and nonfunctional requirements such as performance requirements. In the elaboration phase, an executable architecture prototype is built in one or more iterations, depending on the scope, size, risk, and novelty of the project. This effort should at least address the critical use cases identified in the inception phase, which typically expose the major technical risks of the project.

Construction Phase

During the construction phase, all remaining components and application features are developed and integrated into the product, and all features are thoroughly tested. The construction phase is, in one sense, a manufacturing process where emphasis is placed on managing resources and controlling operations to optimize costs, schedules, and quality. In this sense, the management mindset undergoes a transition from the development of intellectual property during inception and elaboration, to the development of deployable products during construction and transition.

Transition Phase

The purpose of the transition phase is to transition the software product to the user community. Once the product has been given to the end user, issues usually arise that require you to develop new releases, correct some problems, or finish the features that were postponed. The transition phase is entered when a baseline is mature enough to be deployed in the end-user domain. This typically requires that some usable subset of the system has been completed to an acceptable level of quality and that user documentation is available so that the transition to the user will provide positive results for all parties.

This includes:

• "beta testing" to validate the new system against user expectations

• Parallel operation with a legacy system that it is replacing

• Conversion of operational databases

• Training of users and maintainers

• roll-out the product to the marketing, distribution, and sales teams Rational Unified Process:

The transition phase focuses on the activities required to place the software into the hands of the users. Typically, this phase includes several iterations, including beta releases, general availability releases, as well as bug-fix and enhancement releases. Considerable effort is expended in developing user-oriented documentation, training users, supporting users in their initial product use, and reacting to user feedback. At this point in the lifecycle, however, user feedback should be confined primarily to product tuning, configuring, installation, and usability issues.

Answer 3

design, code, test and maintain

Design you will come up with how it will take shape

Code you will build it

Test you will find the bugs

Maintain you will make small adjustments and regular upkeep

Answer 4

1. Planning: Identify requirements, objectives, and constraints for the program.
2. Design: Create a high-level architectural design and detailed program specifications.
3. Implementation: Write, test, and debug the program according to the design specifications.
4. Testing: Verify that the program works as expected and troubleshoot any issues.
5. Maintenance: Address bugs, update features, and ensure the program continues to meet user needs.