Requirements Managementinvolves¡ Planning the SDLC ¡ Including how to gather requirements¡ Controlling requirements changes ¡ including scope creep¡ Tracking progress¡ Negotiating requirements issues¡ Periodic, formal reviews
¡ kjlThe Softwaredevelopmentlifecycle (SDLC) ismarked by a trail ofdocuments
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
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 optional !
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 the order
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, constructing, and documenting the artifacts of a software-intensive system
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
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.