1 / 13

SOFTWARE LIFE-CYCLES

SOFTWARE LIFE-CYCLES. Elements and Definitions. Life Cycle ANSI / IEEE Std 729-1983. A life-cycle is a period of time that starts when a software product is conceived and ends when the product is no longer available for use. ==> Organised in phases. Phases of a Life-Cycle. Requirements

tcisneros
Download Presentation

SOFTWARE LIFE-CYCLES

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SOFTWARE LIFE-CYCLES Elements and Definitions

  2. Life CycleANSI / IEEE Std 729-1983 • A life-cycle is • a period of time that • starts when a software product is conceived and • ends when the product is no longer available for use. ==> Organised in phases

  3. Phases of a Life-Cycle • Requirements • System Design • Detailed Design • Implementation • Testing & Installation • Operations & Maintenance • Retirement

  4. A phase is a • period of time within a life-cycle • that has a defined goal and • is based on result(s) of earlier phases.

  5. Phases are activities • that transform inputs into outputs and • interact so that the transformation goes • from abstract needs to • correct source-code. ==> results (= inputs & outputs): documents ==> verify transformations at milestones

  6. Documentation • internal technical documentation • external technical documentation • end-user documentation • for each version and release ==> supported by standards

  7. internal technical documentation: • the results of each phase • the rationale and assumptions behind the decisions made in each phase • layouts and results of tests • error & fixes log

  8. external technical documentation: • system structure • required environment • instructions for installation • maintenance & operation • guidelines for trouble shooting

  9. end-user documentation: • user handbook • quick reference • guided tour • standard set-up

  10. Milestone • A scheduled event • for which some project member or manager is accountable and • that is used to measure progress.

  11. A milestone includes typically • - a formal review, • - the issuance of documents and • - the delivery of an (intermediate) product. ==> supported by standards

  12. Standards • Project independent • rules and procedures • embedded in a common system of terms • and quality criteria • that ensure inter-project adaptability • and compatibility of solutions. • Important organisations: ANSI, IEEE

  13. End of Section 1b coming up: alternatives to the waterfall model

More Related