Process impact

9

Click here to load reader

Transcript of Process impact

Page 1: Process impact

Process impactSoftware requirements

Alexandra – Ionela DONOSAAn IV, CTI

Page 2: Process impact

What is a software development process ?

A software development process, also known as a software development life-cycle (SDLC), is a structure imposed on the development of a software product.

Similar terms include software life cycle and software process. It is often considered a subset of systems development life cycle.

There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process.

Page 3: Process impact

Which are the phases of a software development process ?

1. Requirements specification (Requirements analysis)2. Software design3. Implementation and Integration4. Testing (or Validation)5. Deployment (or Installation)6. Maintenance

Page 4: Process impact
Page 5: Process impact

What software requirements are ?

Software Requirements is a field within Software Engineering that deals with establishing the needs of stakeholders that are to be solved by software.

Page 6: Process impact

The IEEE Standard Glossary of Software Engineering Technology defines a software requirement as:

1. A condition or capability needed by a user to solve a problem or achieve an objective.

2. A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document.

3. A documented representation of a condition or capability as in 1 or 2.

Page 7: Process impact

Classification : Software Requirements can broadly be broken up into :

1. Elicitation

2. Analysis

3. Specification

4. Management

Page 8: Process impact

1. Elicitation is the gathering and discovery of requirements from stakeholders and other sources

2. Analysis involves reaching a richer and more precise understanding of each requirement and representing sets of requirements in multiple, complementary ways.

3. Specification involves representing and storing the collected requirements knowledge in a persistent and well-organized fashion that facilitates effective communication and change management.

4. Validation involves techniques to confirm that the correct set of requirements has been specified to build a solution that satisfies the project's business objectives.

Page 9: Process impact

Bibliography:

1.http://en.wikipedia.org/wiki/Software_requirements

2.http://www.processimpact.com/SR3E/Software%20Requirements%20Third%20Edition%20Sample%20Chapters.pdf