CS 3321 Software Engineering Project Assignment 1 - Requirements Submission: Submit your document as a single .pdf file through Blackboard.

As the first step of your project, you will prepare a requirements document. The requirements document should include introduction, functional requirements, non-functional requirements, user interface requirements, and use case diagrams. Note that this document will be a part of your final report. You should revise and update this document as needed throughout the semester.

Style Guidelines: You can use Arial, Times New Roman, or Calibri fonts with font size 11/12pt. Line spacing should be at most 1.5. Paper size should be 8.5"x11" (Letter) and you should use Normal MS Word margins (1" top, bottom, right, and left margins.).

Your report must contain the sections listed below. You can add subsections under these sections if you need.

1. Introduction

This section should contain the description of the project in at least 2 pages. You can provide background information and motivation, describe the problem, and define the scope of the project. You can also briefly describe the features of the planned software.

After providing introduction, you should also list important terms and their definitions in a glossary. You can see an example glossary of the MSG Foundation case study in the textbook and lecture slides.

2. Functional Requirements

List the functional requirements of the project. Functional requirements define services that the system should provide. These requirements should be consistent with the use cases provided in Section 5. You should list at least 10 functional requirements.

3. Non-functional Requirements

Non-functional requirements define system properties and constraints. Figure 1 shows some types of non-functional requirements. You should list at least 10 non-functional requirements under at least 5 categories. You will not be required to meet the non-functional requirements in the final product. An example requirements document containing functional and non-functional requirements can be found at http://web.cse.ohio- state.edu/~bair.41/616/Project/Example_Document/Req_Doc_Example.html

Figure 1. Types of non-functional requirements

4. User Interface Requirements

Describe the user interface requirements, but also include a graphic illustrating each requirement. You may find images on the Web or make hand-drawn sketches on paper, then scan them and insert as images into your report. Do not spend time polishing these graphics. You will also not be required to have a fancy graphical user interface in the final product. You should include at least 5 requirements. For instance, if you list a requirement to have a page/window for searching flights for a trip by a system user, you should include an image showing that page/window as given in Figure 2. An example GUI requirements document can be found at https://www.fhwa.dot.gov/cadiv/segb/files/i15/i15guireq.htm

Figure 2. An example page to search a flight.

5. Use Cases

List the use cases one by one and provide the description of each use case as shown in the MSG Foundation case study in the textbook and lecture slides. Present all of your use cases in a single diagram as shown in Figure 3. You should have at least 7 use cases and at least 3 actors. For the use case descriptions, you can also check the website given for functional and non- functional requirements.

Figure 3. An example use case diagram.