Question

There are activities that take place simultaneously throughout the software life cycle. List the activities and briefly discuss each.

Answer 1

There are activities that take place simultaneously throughout the software life cycle. List the activities and briefly discuss each.

Ans:-

List of activities that take place through the software life cycle:-

1. Requirement Analysis

2. Design

3. Implementation

4. Testing

5. Deployment and Maintenance

Requirement Analysis:-

The Software Development Life Cycle begins with requirement analysis phase, where the stakeholders discuss the wants of the software that must be developed to realize a goal. The aim of the need analysis phase is to capture the detail of every requirement and to form sure everyone understands the scope of the work and the way each requirement is going to be fulfilled.
It is a traditional practice to also discuss how each requirement are going to be tested then testers can add great value in participating in requirement analysis meetings.
Depending on which software development methodology is employed , different approaches are taken in moving from one phase to a different . For example, within the waterfall or V model, the need analysis phase are saved during a SRS (Software Requirement Specification) document and wishes to be finalized before subsequent phase can take place.

Design:-

The next stage of SDLC is that the Design phase. During the planning phase, developers and technical architects start the high Level design of the software and system to be ready to deliver each requirement.

The technical details of the planning is discussed with the stakeholders and various parameters like risks, technologies to be used, capability of the team, project constraints, time and budget are reviewed then the simplest design approach is chosen for the merchandise .

There is selected architectural design, defines all the components that must be developed, communications with third party services, and user flows and database communications also as front-end representations and behavior of every components. the planning is typically kept within the Design Specification Document (DSD)

Implementation:-

After the wants and style activity is completed, subsequent phase of the SDLC is that the implementation or development of the software. during this phase, developers start coding consistent with the wants and therefore the design discussed in previous phases.

Database admins create the required data within the database, front-end developers create the required interfaces and GUI to interact with the back-end all supported guidelines and procedures defined by the corporate .

Developers also write unit tests for every component to check the new code that they need written, review each other’s code, create builds and deploy software to an environment. This cycle of development is repeated until the wants are met.

Testing:-

Testing is that the last phase of the software development life cycle before the software is delivered to customers. During testing, experienced testers start to check the system against the wants .

The testers aim to seek out defects within the system also as verifying whether the appliance behaves needless to say and consistent with what was documented within the requirements analysis phase.

Testers can either use a test script to execute test and verify the results, or use exploratory testing which is more experience based approach.

It is possible that defects are identified within the testing phase. Once a defect is found, testers inform the developers about the small print of the difficulty and if it's a legitimate defect, developers will fix and make a replacement version of the software which must be verified again.

This cycle is repeated until all requirements are tested and every one the defects are fixed and therefore the software is prepared to be shipped.

Deployment and Maintenance:-

Once the software has been fully tested and no high priority issues remain within the software, it's time to deploy to production where customers can use the system.

Once a version of the software is released to production, there's usually a maintenance team that take care of any post-production issues.

If a problem is encountered within the production the event team is informed and counting on how severe the difficulty is, it'd either require a hot-fix which is made and shipped during a short period of your time or if not very severe, it can wait until subsequent version of the software.