Question

Please answer them in brief. Don't plagiarize. Please use your own words. Thank u

1. What are the fundamental activities that are common to all software processes? explain in brief
2. List 3 generic process models that are used in software engineering? explain in brief
3. What are the development stages in integration and configuration? explain the brief points
4. What are the principal requirements engineering activities? explain brief
5. What are the two different approaches to process improvement and change that have been proposed? explain brief
6. What are the identified levels in the SEI’s Capability Maturity Model. explain brief

Answer 1

i)

There are some fundamental activities that are common to all software process:

Software specification - In this activity the usefulness of the software and limitations on its activity must be characterized.

Software design and implementation - The software that meets the detail is created.

Software validation - Software must be approved to guarantee that it has all the functionalities what the client needs.

Software evolution - The product must develop to meet changing client needs.

ii)

The waterfall model - In this model of software process the fundamental process exercises of detail, improvement, approval and advancement are spoken to as successive cycle stages, for example, requirements specification, software design, implementation, testing, etc.

Evolutionary development. - This methodology interleaves the exercises of specification, development and validation. An initial system is quickly evolved from unique details. At that point the initial system is refined by client contributions to deliver a system that fulfills the client's needs.

Component-based software engineering - The process models that utilization this methodology depend on the presence of countless reusable parts. The system development process centers around incorporating these segments into a system instead of creating them.

iii)

There are four phases in an integration and configuration model:

• Component Analysis
• Requirements Modification
• System design with reuse
• Development and integration

Component Analysis: Once the requirement specification or gathering stage is finished, an investigation of existing parts is performed to comprehend which segments are in arrangement with the necessities. The segments that are gainful to the new system are recognized.

Requirements Modification: The Requirements are currently refined, and changes are recommended to the existed modules to arrive at the ideal item. The requirement are adjusted as per the new system, to advance reusable parts. On the off chance that changes are unrealistic, elective methodologies are examined.

System design with reuse: The plan of the System is characterized to adjust and rebuild the current parts to the new requirements.

Development and integration: The modules are then evolved from the current modules. New modules dependent on the requirements are additionally made. These are then incorporated to build up the required software.

iv)

Requirements Elicitation: Obtain the prerequisites from the stakeholders

Requirements Analysis: Ensure that all stakeholders and their needs have been recognized and that a wide range of prerequisites (functional, performance, quality) and design constraints have been caught.

Requirements Specification: Capture the necessities in the fitting organize and get duties from stakeholders

Requirements Validation: Ensure that the prerequisites, as documented, are cohesive, consistent, atomic, traceable to their source, unambiguous, and verifiable

Requirements Management: Manage changes to the prerequisites of the system through the design, development, and maintenance activities

v)

The Process Maturity Approach
The Agile Approach

vi)

• Initial
• Repeatable
• Defined
• Managed
• Optimizing

Initial- Few processes characterized, and achievement relies more upon singular brave endeavors than on following a processes and utilizing a synergistic collaboration.

Repeatable- Basic venture the executives measures are built up to follow cost, timetable, and usefulness. Arranging and overseeing new items depends on involvement in comparative ventures.

Defined- Processes for the executives and designing are archived, normalized, and incorporated into a standard software measure for the association. All ventures utilize an endorsed, custom-made adaptation of the association's standard software measure for creating software.

Managed- Detailed software cycle and item quality measurements set up the quantitative assessment establishment. Significant varieties in measure execution can be recognized from arbitrary clamor, and patterns in cycle and item characteristics can be anticipated.

Optimized- The association has quantitative input system set up to recognize measure shortcomings and fortify them supportive of effectively. Venture groups investigations deformities to decide their causes; software measures are assessed and refreshed to keep known kinds of imperfections from repeating