1 / 33

Introduction to the Course Software Specification Lecture 1

Explore software and systems requirements engineering concepts, principles, and techniques. Topics cover requirements elicitation, validation, and formal software specification. Practice techniques through exercises and term project.

jgrey
Download Presentation

Introduction to the Course Software Specification Lecture 1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Introduction to the CourseSoftware SpecificationLecture 1 Prepared by Stephen M. Thebaut, Ph.D. University of Florida

  2. Contact Info • Instructor: Steve Thebaut, E330 • Office Hours: Tuesdays 3:00-4:00 or by appointment (brief matters: whenever present in office) • E-Mail: smt AT cise DOT ufl DOT edu • Phone: (352) 505-1564 • TA: TBD

  3. Course Description Software Specification, CEN 6075, is a graduate-level survey course on the concepts, principles, and techniques related to software and systems requirements engineering (RE).

  4. Course Description (cont) Topics include: • Requirements elicitation, analysis, validation, and documentation techniques (“without the academic methodology mumbo jumbo”) • The Volere requirements process framework • Formal software specification overview

  5. Course Description (cont) Students will practice the techniques presented in class via individual and/or group exercises and (possibly) a term RE project.

  6. Prerequisite • (1) Successful completion of an upper division (undergraduate) or graduate-level software engineering survey course (such as CEN 3031/ 5035), or permission of the instructor. (Students currently or recently employed as software engineering professionals automatically meet this requirement.) If you do NOT meet this requirement, you can instead register for CEN 5035, Software Engineering, which is also being offered this semester.

  7. Prerequisite (cont’d) • (2) Familiarity with programming using a high-level language (C, C++, JAVA, etc.); basic knowledge of algorithms, data structures, and discrete math.

  8. Class Meeting Times and Location (for on-campus students): • Tuesday 7th (1:55-2:45), Thursday 7th-8th (1:55-3:50) • Room: CSE 107 • All in-class lectures will be recorded by UF EDGE and posted on Canvas shortly thereafter for viewing by registered students.

  9. Course Website: www.cise.ufl.edu/class/cen6075/fa16.html • Syllabus • Lecture Notes • Practice Exams • Exam Schedule • Exercises • Reading assignments • Announcements • Contact Information Recorded lectures and the course grade book are available to registered students via UF's “e-Learning on Canvas” at https://lss.at.ufl.edu

  10. Getting Help • E-Learning access assistance – contact: E-Learning Support Services: learning-support At ufl DOT edu phone: 352-392-4357 option 3 • EDGE registration assistance – contact: UF EDGE, 352-392-9670

  11. Getting Help (cont’d) • course content–related help: Steve Thebaut: smt AT cise DOT ufl DOT edu phone: 352-505-1564

  12. Textbooks • (1)EXPLORING REQUIREMENTS: QUALITY BEFORE DESIGN, by David Gause and Gerald Weinberg, Dorset House; • (2)MASTERING THE REQUIREMENTS PROCESS: GETTING REQUIREMENTS RIGHT (3RD ED.), by Suzanne and James Robertson. Other readings/resources are available on-line or elsewhere.

  13. Outline of Topics • Course introduction and review of SE realities and RE basics • Volere overview: some fundamental truths and a requirements process framework outline • Human aspects of RE – working with people to explore requirements (Gause and Weinberg) • More Volere process nuts and bolts • An overview of formal specification (algebraic, model-based, functional)

  14. Class Format You should complete assigned readings / exercises before they are discussed in class, and should expect in-class discussions/activities to complement(as opposed to summarize or replace) the readings / exercises.

  15. Class Format (cont’d) Impromptu in-class role-playing and/or illustrative exercises will be the norm for some topics (e.g., parts of the Gause & Weinberg text), while a more traditional lecture format will be used for others (e.g., formal specification techniques). Local students will be asked to provide occasional status reports on their term project activities.

  16. Possible Term Project Assuming adequate TA support, local students will undertake a significant RE project spanning a multi-week period with an actual customer of their choosing. Off-campus EDGE students will have the option of participating in a similarly structured RE project if circumstances permit, or of undertaking a relevant independent study project. Additional information will be provided later.

  17. Examinations and Grades Your course grade will be based SOLELY on a term project (possibly) and two tests, all weighted equally – NO EXCEPTIONS! A histogram of numeric scores will be provided with solution notes for each test; your course letter grade will be determined at the end of the semester.

  18. Examinations and Grades (cont’d) Since tests vary in difficulty, the grading scale is not fixed in advance. Typical course grade distribution: • A: 10-20% • A-: 25-35% • B+: 25-35% • B: 10-20% • lower than a B: 5-15%.

  19. Exercises Exercises for some topics will be made available and discussed in class as appropriate, but will not be graded. Required Computer Facilities Access to e-mail and the WWW is required.

  20. Exam Schedule (tentative) • Test 1: October 13 (Non-Gainesville area EDGE students: October 13-14); • Test 2: December 1 (Non-Gainesville area EDGE students: December 1-2). Note: there is no (comprehensive) “final exam” for this course.

  21. Exam Procedures for EDGE Students • Proctors will be instructed to schedule a SINGLE Test TIME for all students at each off-campus site. If this is not possible for any reason, students must contact the instructor well in advance to discuss other possible arrangements. • Proctors should return electronic copies of completed tests directly to the instructor via e-mail after administration.

  22. Grading Errors • General test re-grade requests (AKA “fishing expeditions”) are NOT accepted. • Suspected grading errors should be brought to my attention (with explanation) ASAP, but no later than two weeks after graded tests are made available for review for appropriate consideration. • Your original, UNALTERED test must be returned to me (on-campus students) together with a correction request form (to be provided). • Note that partial credit policies are not subject to debate.

  23. Make-Up Exam Policy • Students are expected to be available at scheduled test times. Do NOT schedule conflicting elective activities (family gatherings, interview trips, weddings, divorces, vacations, etc.). • If missing a test is unavoidable (e.g., due to sickness, accident, or other reasons beyond your control), contact me as far in advance as possible.

  24. Make-Up Exam Policy (cont’d) • Make-up tests, when permitted, may be administered orally. • If it is not practical to administer a make-up test before the end of the term, a course grade of "I" (incomplete) may be assigned.

  25. Class Attendance Students are expected to view all recorded lectures and are responsible for any recorded announcements made in class or posted on the course website, but are NOT required to attend live lectures unless their project team has been asked in advance to provide an in-class status reports on their activities.

  26. Exercises • Optional, self-check exercises (together with solution notes) will be made available on the course website for some topics.

  27. Reading Assignments • Brooks, “No Silver Bullet – Essence and Accident in Software Engineering,” in The Mythical Man-Month (Anniversary Edition), chapter 16; also available on-line. • Optional RE review reading: Sommerville, “Requirements Engineering,” in Software Engineering (9th/10th Edition), Chapter 4. • Robertson & Robertson, Mastering the Requirements Process, Chapters 1 & 2.

  28. Reading Assignments (cont’d) • Gause & Weinberg, Exploring Requirements: Quality Before Design, entire book. • Robertson & Robertson, Mastering the Requirements Process, chapters TBD. • Sommerville, “Formal Specification,” Chapter 27, in Software Engineering, 2009, available on-line.

  29. Academic Integrity • You will be asked to sign the following state-ment on the tests in this course: On my honor, I have neither given nor received unauthorized aid on this exam and I pledge not to divulge information regarding its contents to those who have not yet taken it. • Note that a copy will be retained of all graded tests returned to students.

  30. Other Items For info regarding: • Accommodation for Students with Disabilities, • UF Counseling Services, • UF Software Use Policies, and • Instructor background, please see the course syllabus.

  31. Questions?

  32. Introduction to the CourseSoftware SpecificationLecture 1 Prepared by Stephen M. Thebaut, Ph.D. University of Florida

More Related