1 / 17

Software Life Cycle

Software Life Cycle. Software development. « include ». « include ». « include ». Problem definition. System development. System operation. Client. Project manager. Developer. Administrator. End user. Simple life cycle for software development. System. development. activity.

chantale-perry
Télécharger la présentation

Software Life Cycle

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 Cycle

  2. Software development «include» «include» «include» Problem definition System development System operation Client Project manager Developer Administrator End user Simple life cycle for software development

  3. System development activity System upgrade activity Market creation activity Problem System System definition development operation activity activity activity Another simple life cycle.

  4. Lessons learned Market survey document document System specification Executable system document Entity-centered view of software development. Software Development

  5. Activity Work product Market survey consumes document Problem definition activity produces Specification document consumes System development activity produces Executable system consumes System operation activity produces Lessons learned document Activities and products of the simple life cycle of Figure 15-2.

  6. Software Life Cycle Money * Process Group Time Participant * Process * Resource * Work Unit consumed by * * Activity Task Work Product produces Model of the software life cycle

  7. Development processes Management processes Integral processes Concept Exploration Process System Allocation Process RequirementsProcess ProjectInitiation Process ConfigurationManagement Process DesignProcess ImplementationProcess ProjectMonitoring&Ctrl Process DocumentationDevelopmentProcess InstallationProcess Operation& SupportProcess S/W QualityManagement Process TrainingProcess MaintenanceProcess Verification& Validation Process RetirementProcess Process interrelationships in the IEEE 1074 standard.

  8. Project Initiation Process Concept Exploration Process System Allocation Process Requirements Process Design Process Implementation Process Verification & Validation Process Installation Process Operation & Support Process The waterfall model of software development is an activity-centered view of the software life cycle.

  9. System Requirements Operation Analysis Software Client Requirements Acceptance Elicitation System Requirements Integration Analysis & Test Component Preliminary Integration Design & Test Detailed Unit Design Test Implementation V-Model of software development.

  10. Boehm’s spiral model (Adapted from [Boehm, 1987]).

  11. Management Unified Process Software Life Cycle Environment Requirements Design Inception Implementation Elaboration Assessment Construction Deployment Transition Workflows in the unified software life cycle used by Royce. releases Product * Workflow Cycle * 4 Phase * * Artifact Iteration

  12. States of a Software System called phases in the Unified Process. Inception Elaboration Transition Construction

  13. The seven workflows in the Unified Process.

  14. Entity-centered life cycle view of the models of the Unified Process. Use case model specified by realized by Analysis model distributed by Design model implemented by Deployment model verified by Implementation model Test model

  15. i1:Issue status={Closed} i5:Issue status = {Open} i2:Issue status = {Open} i7:Issue status={Closed} i3:Issue status = {Open} i6:Issue status = {Open} Snapshot of a project issue base. Issues i1 and i5 have been resolved, whereas all other issues are still open. Dependencies among issues indicate that the resolution of an issue can constraint the alternatives for dependent issues.

  16. Req. Elicitation Analysis i1:Issue i5:Issue status={Closed} status={Closed} i2:Issue i7:Issue status={Closed} status={Closed} i3:Issue System Design status={Closed} i6:Issue status = {Open} The waterfall model as a special case of the issue-based life cycle model. All issues that belong to the same issue category are contained in the same UML package. In the project status shown in the figure, all the requirements elicitation and analysis issues have been closed; that is, the requirements elicitation and analysis activities have been completed.

  17. Req. Elicitation Analysis i1:Issue i5:Issue status={Open} status={Open} i2:Issue i7:Issue status={Closed} status={Closed} i3:Issue System Design status={Closed} i6:Issue status = {Open} In a complex project state, all activities can still have some open issues, which means that all activities need to be managed concurrently.

More Related