Computer Science Homework Help

Part 1: Software Requirements Specification

One of the first tasks in the development of a software application is to gather and document the requirements. The requirements will be used in all other phases of the project so they are vitally important. For this assignment, you will be creating the Software Requirements Specification (SRS) for your Software Development Plan you started in Module 1 (you will create the SRS as a separate document for this assignment).

Part 2: Prepare a design for the application

Once the requirements have been completed for your Software Development Plan, the next step is to prepare a design for the application. The design process will vary based on the project you have selected, but there will be some common steps. You should always select a proper architecture, and you will usually have a user interface of some kind that will require design. There is often some type of business logic involved, and you may also have a database. Ultimately, you need a good set of design artifacts for your application that will allow the software engineers to do their job of implementation. For this assignment, you will be adding design documents to your Software Development Plan that you have been working on in the first two modules of the course.

SLP Assignment Expectations

The following topics should be covered:

• Requirements Elicitation
• Summarization of the process used to gather requirements for your software project.
• Software Architecture
  • Select an appropriate architecture for your application.
  • Describe the architecture and justify your selection based on the strengths of the architecture and suitability to the type of application you are developing.
• Software Design
  • Identify the major functional areas of your application (i.e., user interface, business logic, database, etc.). Note that your functional areas should address the functional requirements in this module
  • For each functional area, prepare appropriate software design documentation sufficient to allow software engineers to implement the required code. Design documentation should include descriptions and appropriate diagrams to support the design definition (i.e., UML diagrams such as class diagrams, sequence diagrams, etc.).