· Case Study 1: Software Requirement Specification

case_study_1_software_requirement_specification.docx

Home >Information Systems homework help >· Case Study 1: Software Requirement Specification

· Case Study 1: Software Requirement Specification

Due Week 4 and worth 100 points

Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook.

Write a three to five (3-5) page paper in which you:

1. Create a Software Requirement Specification (SRS) that includes the following:

1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided.

2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided.

3. A detailed requirement specification written in structured natural language.

2. Structure and present the requirements in a logical and consistent manner.

3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length.

Your assignment must follow these formatting requirements:

. Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions.

. Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length.

. Include charts or diagrams created in Visio or an equivalent such as Dia. The completed diagrams / charts must be imported into the Word document before the paper is submitted.

The specific course learning outcomes associated with this assignment are:

. Analyze and describe functional and nonfunctional requirements in software engineering.

. Describe the key components in requirements elicitation and analysis.

. Use technology and information resources to research issues in software engineering.

. Write clearly and concisely about software engineering using proper writing mechanics and technical style conventions.

Grading for this assignment will be based on answer quality, logic / organization of the paper, and language and writing skills, using the following rubric.

Points: 100	Case Study 1: Software Requirement Specification
Criteria	Unacceptable Below 60% F	Meets Minimum Expectations 60-69% D	Fair 70-79% C	Proficient 80-89% B	Exemplary 90-100% A
1a. Create a Software Requirement Specification (SRS) that includes a detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. Weight: 15%	Did not submit or incompletely created a Software Requirement Specification (SRS) that includes a detailed description of both user and system requirements. Did not submit or incompletely provided at least four (4) user requirements and four (4) system requirements should be provided.	Insufficiently created a Software Requirement Specification (SRS) that includes a detailed description of both user and system requirements. Insufficiently provided at least four (4) user requirements and four (4) system requirements should be provided.	Partially created a Software Requirement Specification (SRS) that includes a detailed description of both user and system requirements. Partially provided at least four (4) user requirements and four (4) system requirements should be provided.	Satisfactorily created a Software Requirement Specification (SRS) that includes a detailed description of both user and system requirements. Satisfactorily provided at least four (4) user requirements and four (4) system requirements should be provided.	Thoroughly created a Software Requirement Specification (SRS) that includes a detailed description of both user and system requirements. Thoroughly provided at least four (4) user requirements and four (4) system requirements should be provided.
1b. Create a Software Requirement Specification (SRS) that includes a detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. Weight: 15%	Did not submit or incompletely created a Software Requirement Specification (SRS) that includes a detailed description of both functional and nonfunctional requirements. Did not submit or incompletely provided at least four (4) functional requirements and four (4) nonfunctional requirements.	Insufficiently created a Software Requirement Specification (SRS) that includes a detailed description of both functional and nonfunctional requirements. Insufficiently provided at least four (4) functional requirements and four (4) nonfunctional requirements.	Partially created a Software Requirement Specification (SRS) that includes a detailed description of both functional and nonfunctional requirements. Partially provided at least four (4) functional requirements and four (4) nonfunctional requirements.	Satisfactorily created a Software Requirement Specification (SRS) that includes a detailed description of both functional and nonfunctional requirements. Satisfactorily provided at least four (4) functional requirements and four (4) nonfunctional requirements.	Thoroughly created a Software Requirement Specification (SRS) that includes a detailed description of both functional and nonfunctional requirements. Thoroughly provided at least four (4) functional requirements and four (4) nonfunctional requirements.
1c. Create a Software Requirement Specification (SRS) that includes a detailed requirement specification written in structured natural language. Weight: 15%	Did not submit or incompletely created a Software Requirement Specification (SRS) that includes a detailed requirement specification written in structured natural language.	Insufficiently created a Software Requirement Specification (SRS) that includes a detailed requirement specification written in structured natural language.	Partially created a Software Requirement Specification (SRS) that includes a detailed requirement specification written in structured natural language.	Satisfactorily created a Software Requirement Specification (SRS) that includes a detailed requirement specification written in structured natural language.	Thoroughly created a Software Requirement Specification (SRS) that includes a detailed requirement specification written in structured natural language.
2. Structure and present the requirements in a logical and consistent manner. Weight: 20%	Did not submit or incompletely structured and presented the requirements in a logical and consistent manner.	Insufficiently structured and presented the requirements in a logical and consistent manner.	Partially structured and presented the requirements in a logical and consistent manner.	Satisfactorily structured and presented the requirements in a logical and consistent manner.	Thoroughly structured and presented the requirements in a logical and consistent manner.
3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Weight: 25%	Did not submit or incompletely developed a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia.	Insufficiently developed a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia.	Partially developed a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia.	Satisfactorily developed a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia.	Thoroughly developed a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia.
4. Clarity, writing mechanics, and formatting requirements Weight: 10%	More than 8 errors present	7-8 errors present	5-6 errors present	3-4 errors present	0-2 errors present