Computer Science Homework Help

Computer Science Homework Help. Requirements Specification

For this assignment you will specify the requirements for a software system. Software systems are assigned during in-class interviews, and your information about your application to specify will come from in-class client interviews. In these interviews, you will ask your “client” (other students) about the application you are expected to specify.

The purpose of this assignment is to learn how to write a fairly complete and precise requirements specification, which is a critical step in developing a large software system. You will utilize all of the methods discussed to elicit requirements, including from the client directly. Client interviews will be held during lecture.

The deliverable is a single electronic document that contains your software requirement specification. There is no explicit requirements for the format, but as a minimum we have provided a Feel free to expand, improve, or find examples elsewhere (like the IEEE guidelines


SRS Rubric

SRS Rubric

Criteria Ratings Pts

This criterion is linked to a Learning OutcomeClarity and WritingCovers the logical construction of the document, as well as the writing itself (grammar, spelling, formatting).

3 to >2.0 pts

Full Marks

The writing is clear and correct — sentences are constructed appropriately, easy to read, and few to no spelling or grammatical errors. The logical flow of the document is intuitive and easy to follow.

2 to >1.0 pts

Clean writing, can improve organization

The content is appropriately written, but the logical flow of the document could be improved to make the content easier to follow.

1 to >0 pts

Content and flow need work

The writing and flow make the document difficult to follow and appear unfinished.

3 pts

This criterion is linked to a Learning OutcomeIntroduction and OverviewCovers the introduction and overview of both the document itself as well as the application specified.

5 to >4.0 pts

Full Marks

The application is introduced briefly and non-technically in terms of the client’s goal, why the system is needed, the major features, who (users) is effected, and the contents of the document itself and its organization are laid out.

4 to >2.0 pts

Improve level of Abstraction

The appropriate information is present, but is too detailed or too technical.

2 to >1.0 pts

Can improve organization

Introduction requires more information about the application or purpose of the specification document to give a complete picture to the reader.

1 to >0 pts

Missing

Information summarizing the application and document are not present.

5 pts

This criterion is linked to a Learning OutcomeUser RequirementsDescribes application context and environmental constraints. Information about the use (from user perspective) of the application and the targeted platform(s), and any assumptions or constraints on hardware, software, or design (UI).

3 to >2.0 pts

Full Marks

Information present and clearly presented.

2 to >1.0 pts

Can improve

Requires more information, or improved clarity.

1 to >0 pts

Missing

Information not present.

3 pts

This criterion is linked to a Learning OutcomeFunctional RequirementsClearly describes the proposed software product, including its capabilities and attributes. Describes the functional requirements of the system in precise detail. When possible, identify the entities (components, sections, areas of functionality) that make up the system. Characterize the properties, states, functions, and interrelationships of each entity.

10 to >9.0 pts

Full Marks

Comprehensive use-case diagram present, with text descriptions of different use-cases organized in a clearly understandable manner.

9 to >5.0 pts

Can improve

Use case diagram present but requires more use-cases, or missing text description.

5 to >1.0 pts

Requires use case diagram

Functional properties described, but only in text.

1 to >0 pts

Missing

Information not present.

10 pts

This criterion is linked to a Learning OutcomeNon-functional Requirements

5 to >4.0 pts

Full Marks

Information present and clearly presented.

4 to >1.0 pts

Can improve

Requires more information, or improved clarity.

1 to >0 pts

Missing

Information not present.

5 pts

This criterion is linked to a Learning OutcomeOtherUp to 5 extra points on additional information, for example: expected changes or additions of features after software release, a glossary of terms from the document, potential risks, timeline, or others. Get creative!

5 to >1.0 pts

Extra Information

Additional information present and clearly presented. Information is appropriate, and does not contradict the client’s requirements.

1 to >0 pts

Missing

Information not present.

5 pts

Total Points: 31

PreviousNext

Computer Science Homework Help

 
"Our Prices Start at $11.99. As Our First Client, Use Coupon Code GET15 to claim 15% Discount This Month!!"