Download Course Project II - Software Engineering | CS 3773 and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity! CS3773 Course Project II For this project, you will create a Software Architecture Design for the UTSA Book Club software system. Deliverables You will produce a design document for the UTSA Book Club. Your design should provide a solution for the UTSA Book Club requirements that have been identified and documented in your SRS as the first project. Write clearly and organize your report so it is easy to find things within your submission. Your design document will include the sections as below. • Abstract: presenting an overview of the key points in your report, targeted to a manager or a developer. • Introduction and Overview: giving a summary of your report, its organization, and its salient conclusions. A person should be able to read the abstract and introduction and have a good idea of the contents of the remainder of your report. • Architecture: depicting and picturing the overall structure of the system that you are proposing to implement, with description of each major component and of the interactions among them. These components are to be primarily subsystems and modules, but also include processes, files, and databases. In your descriptions, concentrate on goals, requirements, feasibility, maintainability, etc., rather than on lower level concepts such as variables and data structures. You should clarify global control flow, such as units of concurrency and method of passing control from one component to another. Your system's architecture should be easy to understand, with simple interfaces, and modest interactions among subsystems and modules. Clarify what style of architecture (in the sense of Garlan and Shaw) that you are proposing. You should use diagrams that clearly illustrate the structure of your system. You may use DFDs (Data Flow Diagrams), ERDs (Entity-Relation Diagrams), or class diagrams. • External Interfaces: List information transmitted to/from the system together with the format, such as by Graphical User Interfaces, files, databases, messages or networks. • Data Dictionary: Include a glossary that briefly defines all the key terms used in your architecture. • Maintainability: Discuss how your architecture is designed to support future UTSA book club features. • References: List any documents that your reader may wish to or need to read in conjunction with your report.
