software_life_cycle

software_life_cycle - Software Life Cycle Processes...

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
Abdelghani Bellaachia Page: 1 Software Life Cycle Processes ª Objective: Establish a work plan to coordinate effectively a set of tasks. Improves software quality. Allows us to manage projects more easily. Status of projects is more easily tracked. Provides a baseline for improvement and measurement. ª Build-and-Fix Model: Build a product without specs or any attempt at design Rework the product to satisfy the client It is not practical for product of reasonable size. Approach: Build first version Modify until customer is satisfied Maintenance
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Abdelghani Bellaachia Page: 2 ª Definition: “A life cycle is the course of development changes through which a project passes from its inception as a project request to the mature state as characterized by a stable production environment.” ª According to IEEE Std 12207 (ISO/IEC 12207), Standard for Information Technology -- Software life cycle processes: Establishes a common framework for software life cycle processes that can be referenced by the software industry. Lists processes that can be applied during the acquisition, supply, development, operation and maintenance of software and systems containing software. ª Development Process Note that development often accounts for less than a third of the total project! Once a system has been built, the time spent on maintenance will be greater than the time spent on all other phases Maintenance takes around 60% of total cost. But note that for a very successful system (say, Unix, or Microsoft Word), maintenance can continue for a very long time. In fact, some describe developing software as the process of maintaining a blank sheet of paper!
Background image of page 2
Abdelghani Bellaachia Page: 3 ª Different Processes: z Problem identification : someone identifies a problem, which needs addressing and might be susceptible to a computerized solution. z Requirements analysis : z It is much harder than people think. z Required features that should be included in a computerized solution to provide a cost-effective solution to the problem. z Capture what the customer wants. z Develop test plan : Develop test procedures to determine if a completed product correctly provides all of required features. z Develop software design : z Analyze the required features to identify existing software that can be reused in this product. z Changes needed in reused Components. z Create high level design for new components z For each component in high level design, develop detailed design. z Also develop unit test plan for each component.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Abdelghani Bellaachia Page: 4 z Built and Document : z Develop code for each module. z
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 09/03/2010.

Page1 / 17

software_life_cycle - Software Life Cycle Processes...

This preview shows document pages 1 - 5. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online