Inf 43: Introduction to Software Engineering – Homework 1

Hello, if you have any need, please feel free to consult us, this is my wechat: wx91due

Inf 43: Introduction to Software Engineering – Homework 1

Requirements Homework

For Homework 1 you will elicit, analyze, and specify the requirements for SubDo, a computer system that supports the management and scheduling of substitute teachers. Elicitation will be done via interviews with your customer during the class lecture period on Thursday, April 7 and Tuesday, April 12.

The Homework 1 deliverables are draft and final versions of the specifications, uploaded to the EEE Dropbox “Inf 43 – Hw 1 draft” and “Inf 43 – Hw 1 final”. The draft is due by Monday, April 11, at 11:55pm (using EEE’s clock). The draft will not be scored, but it must contain a reasonable first draft of the “Introduction” and “Description of the Problem” sections. No drafts will be accepted after 9:30am on Tuesday, April 12. Your draft will not be commented on or returned. The final version is due on Monday, April 18, at 11:55pm, and must be in .docx, .doc, .rtf, or .txt format (no PDF files, no compressed files).

The structure of your requirements specification will closely follow “Example 4: Essential SRS—Narrative Approach” in Appendix B of the textbook, with the addition of a “Use Cases” section. Use Homework1-template.docx at http://frost.ics.uci.edu/inf43/Homework1- template.docx as a starting point for your homework, and maintain its spacing, typeface, and overall structure.

Your document will be scored as follows:

10 points: Draft was turned in on time and represented a reasonable start.

20 points: Document is carefully proofread and is written in clear, grammatical, business-like English. Using the present tense is a good choice. Bullet items are permitted if used sparingly: do not nest one list or set of bullet items within another; avoid sentence fragments (except with Use Cases). Appendix B, Example 4’s B.i.a-d might well have some points taken off.

10 points: Introduction section meets the criteria given in Appendix B, and includes all relevant information provided during the interviews.

10 points: Description of the problem section meets the criteria given in Appendix B, and includes all relevant information provided during the interviews.

5 points: The Use Cases section specifies several important use cases for SubDo in the format described in discussions.

45 points: The Description of software solution section meets the criteria given in part C and includes all relevant information provided during the interviews. Do not use a table to organize  features and functional capabilities (see the template for an explanation).

Many Informatics 43 requirements specifications are 3 to 6 pages long, but the length of the document is not a scoring criterion.

Fidelity to the customer’s desires is paramount. This is not a creative writing exercise. Do not add or omit requirements without the customer’s approval.

The four sections of your document will certainly have some overlap, but they have distinct purposes. Points will be lost if material is in the wrong section.

发表评论

电子邮件地址不会被公开。 必填项已用*标注