1. Computer ScienceSoftware Engineering Slide 1 Today l As3 grading Clarity, completeness, inconsistencies Comments l CVS guru name l Project assignment l Architecture l Next: Design, review, code, test, review, integrate, test

2. Computer ScienceSoftware Engineering Slide 2 Today’s laws l Boyle's Laws: The deficiency will never show itself during the dry runs. Clearly stated instructions will consistently produce multiple interpretations. l Brooks's Law: Adding manpower to a late software project makes it later. l Cheops's Law: Nothing ever gets built on schedule or within budget.

3. Computer ScienceSoftware Engineering Slide 3 Groups Paul Simmerlink Andrew Rodgers Daniel Coming Ogechi Ugwulebo William Nelson Jigna J. Bhatt Casey J. Powell Jonathan Ward Michael Vidal Howard C. Wu Stephen Herbert Don Miller James Frye David Brewer Olja Mihic Casey Mees Maggie Lu Reid Webber Taisuke Nagayama Stan Sexton Matasaka Sako Brett Harrison Shana Rheault RichardD.VanHorn Rodel Mangoba Steve Luong Jason Dodd Beifang Yi Dorothy P. Cheung James King Will Woolsey James Cohen, Judy Rowley, Rajashekhar Yakkali, Kazuhito Mori, Jeff Payne

4. Computer ScienceSoftware Engineering Slide 4 Architecture l Interfaces and skeletons

5. Computer ScienceSoftware Engineering Slide 5 LMS Class Skeleton public class Patron { // Class Semantics and roles // Library Patrons function in two primary // roles, as researchers who use index, // reference and database materials, and as // borrowers of loanable resources. // Information maintenance // Creation: new patrons are introduced // into the system by library staff when // presented with a library membership // application or from information // retrieved from a web-based application

6. Computer ScienceSoftware Engineering Slide 6 LMS Class Skeleton public class Patron { // Class Semantics and roles // Library Patrons function in two primary // roles, as researchers who use index, // reference and database materials, and as // borrowers of loanable resources. // Information maintenance // Creation: new patrons are introduced // into the system by library staff when // presented with a library membership // application or from information // retrieved from a web-based application

7. Computer ScienceSoftware Engineering Slide 7 More LMS Class Skeleton // Information maintenance continued // Deletion: patrons are removed from the // library database 3 years after their // membership expires // // Instance variables private String name; // Patron name in // last, first, middle initial format private long PatronID; // Patron library ID // number. Automatically generated...( See deliverable 5.1 for other instance variables )

8. Computer ScienceSoftware Engineering Slide 8 More LMS Class Skeleton // Class variables private static long nextPatronID; // Keeps // track of next patronID to be assigned // Constructors public Patron(String n, long home, Date m, Date e, String street, String city, String state, long zip) { // Parameters: n = name, home = homephone // PatronID = getnextPatronID() // street,city, state, and zip are used // to create an address object for // homeAddress

9. Computer ScienceSoftware Engineering Slide 9 More LMS Class Skeleton // Constructors continued // Precondition: for constructor: // Library database can accept an // additional entry and memory allocation // succeeds // Postcondition: Library database will // contain an additional Patron and Address // entry } // Static methods public static long getnextPatronID() { return nextPatronID; nextPatronID++;}

10. Computer ScienceSoftware Engineering Slide 10 More LMS Class Skeleton // Non-static methods public boolean validatePatron(Date e) { // ensure membership is not expired // Precondition: expireDate != null // if expireDate <= Today return false // else return true }...( See deliverable 5.1 for other non-static methods ) } // end class Patron