Review of Software Requirements Specifications
computer science
Description
This Case Assignment consists of two parts:
Part 1: Review of Software Requirements Specifications
A Software Requirements Specification (SRS) is a key document that is used to support all other phases
of a software development project. A good SRS must include key information for the project and should
be prepared using industry-recognized best practices for SRS documents. For this case study, you will
locate, review, and evaluate an example SRS document. There are many appropriate SRS documents
available on the Web that you may use for this case study, and your evaluation should address the
following points:
- How well does the SRS conform to best practices for the preparation of requirements
specifications?
- What are the strengths of the SRS?
- What are the weaknesses of the SRS?
- What would you add or remove from the SRS? Be sure to justify your response to this question.
Part 2: Software Architecture and Design Review
The architecture and overall design of a software application can make the difference between success
and failure. A poor architecture might prohibit an application from ever meeting the requirements
established during the requirements phase, and poor overall design will cause poor quality and failure
of development goals. For this case study, you will review and evaluate the architecture and design of an
open-source software program.
Your review will examine DotNetNuke, a popular open-source content management system. The
complete source code and other resources for the latest version can be found
at http://dotnetnuke.codeplex.com/releases. In addition, you can find more information about this
application at www.dotnetnuke.com.
Your evaluation should address the following points:
- What is the architecture used in this application?
- How well does the architecture match the type of application?
- What are the major functional areas of the application?
- What is the general design of each of the functional areas?
- Summarize your overall opinion of the design and architecture of the application.
Assignment Expectations
- Thorough, well-organized topic coverage
- Written at a college level
- 4 – 8 pages (not including title page or bibliography), double-spaced Microsoft Word document
- APA Format
- At least 2 good research references (no wikis)
