CST438 - Week 7

This week we learned all about the System Requirements Specification (SRS) Documents. SRS documents vary slightly across organizations but contain important information about the system environment, use cases, and logical data structure, to name a few of the key components. In a Plan and Document/Waterfall process, this document outlines all of the requirements for all stakeholders of the project before the development process begins. We were instructed to write an abbreviated SRS document for the service we developed in this class, the registration or gradebook service. These are the figures that I included in my SRS document:

Figure 1: System Environment

Figure 2: Logical Structure of Gradebook Data

Agile VS. Plan and Document (Waterfall)

Agile and Plan and Document are two processes that stakeholders choose between when beginning a project. Whereas Agile takes an iterative approach, the Waterfall process aims to define the requirements and project specifications before development. Both of these methods aim to deliver a high-quality product with which the client will be satisfied. They both have the same goal but achieve it in very different ways. In the Waterfall process, the aim to please is based on clearly laying out everything right at the start so the client knows exactly what they will receive. The Agile process aims to please the client by constantly being in contact with them each step of the way to make sure each iteration brings the product closer to a final product that the client will approve.