Your SlideShare is downloading. ×
0
The software developmentlifecycleHow software is made
Success =on time +withinbudget +it works
Poor requirements are wildlyexpensive
Developersandcustomersmust agree onrequirementsthroughoutthe SDLC
Requirements Managementinvolves¡  Planning the SDLC ¡  Including how to gather requirements¡  Controlling requirements ...
¡  kjlThe Softwaredevelopmentlifecycle (SDLC) ismarked by a trail ofdocuments
These documents outlinethe SDLC¡  Project charter¡  Functional Requirements¡  Nonfunctional requirements¡  Use Case Di...
The project charter¡  The foundation
Functional requirements¡  One-sentence description¡  What the software should do
Nonfunctionalrequirements¡  One-sentence description¡  Parameters
The use case diagram¡  Big-picture layout of all functionality¡  How they relate to actors and to each other
Use cases¡  Text narrative¡  What the software    should do¡  Not how to do it
Activity diagrams¡  Visual representation of a use case¡  Industry-standard nomenclature
CRC cards ¡  A tool to                identify so    objects!                 ftware¡  Complete               ly optiona...
Sequence diagrams¡  A tool to expose how the objects relate to one    another¡  Emphasizes the order in which they relate
Collaboration diagrams¡  A tool to expose how the objects relate to one    another¡  Emphasizes the relationships, not t...
Class diagrams¡  Extremely low-level design of the software
Several of these artifacts arecreated using UML¡  The UML is the standard language for visualizing,    specifying, constr...
Conclusion¡  Requirements list everything that the software    must do¡  To get these wrong is to design bad software¡ ...
Upcoming SlideShare
Loading in...5
×

01 the SDLC

900

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
900
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "01 the SDLC"

  1. 1. The software developmentlifecycleHow software is made
  2. 2. Success =on time +withinbudget +it works
  3. 3. Poor requirements are wildlyexpensive
  4. 4. Developersandcustomersmust agree onrequirementsthroughoutthe SDLC
  5. 5. Requirements Managementinvolves¡  Planning the SDLC ¡  Including how to gather requirements¡  Controlling requirements changes ¡  including scope creep¡  Tracking progress¡  Negotiating requirements issues¡  Periodic, formal reviews
  6. 6. ¡  kjlThe Softwaredevelopmentlifecycle (SDLC) ismarked by a trail ofdocuments
  7. 7. These documents outlinethe SDLC¡  Project charter¡  Functional Requirements¡  Nonfunctional requirements¡  Use Case Diagram¡  Use Cases¡  Activity Diagrams¡  CRC Cards¡  Sequence Diagrams¡  Collaboration Diagrams¡  State Diagrams¡  Class Diagrams
  8. 8. The project charter¡  The foundation
  9. 9. Functional requirements¡  One-sentence description¡  What the software should do
  10. 10. Nonfunctionalrequirements¡  One-sentence description¡  Parameters
  11. 11. The use case diagram¡  Big-picture layout of all functionality¡  How they relate to actors and to each other
  12. 12. Use cases¡  Text narrative¡  What the software should do¡  Not how to do it
  13. 13. Activity diagrams¡  Visual representation of a use case¡  Industry-standard nomenclature
  14. 14. CRC cards ¡  A tool to identify so objects! ftware¡  Complete ly optional !
  15. 15. Sequence diagrams¡  A tool to expose how the objects relate to one another¡  Emphasizes the order in which they relate
  16. 16. Collaboration diagrams¡  A tool to expose how the objects relate to one another¡  Emphasizes the relationships, not the order
  17. 17. Class diagrams¡  Extremely low-level design of the software
  18. 18. Several of these artifacts arecreated using UML¡  The UML is the standard language for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system
  19. 19. Conclusion¡  Requirements list everything that the software must do¡  To get these wrong is to design bad software¡  It is ridiculously expensive to discover bad requirements late in the lifecycle¡  The artifacts guide the SDLC and document its history
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×