Previous Similar  Assignments

H1   Small Java Program
        The program should read text input, accept a button click to process the input / generate some output message.
        Ex:  "Bill"  input  could generate the message  "Hello Bill,  have a nice day"
                                 or  " 'Bill' is not one of the common names I know, try again?"
        Specific requiremens:  disk with label (printed name, cis501, Sp03),
                                          root directory should have H1_Run.bat file and a folder for program  files,
                                          the folder should have "src"  and "class" folders,
                                          the program should be in a single package.

H2    First version of program to display (and add) quotes, with selection by author.
         the program must  meet  (some) "common program requirements" (as defined in class).

H3    Common quotations program, with selection by author.  The quoteCollection should implement this interface.
          The program should meet all of the related common program requirements.

H4    UseCase model for the POS system  (hardcopy of diagram and narrative)

H6: Writing Assignment:
       Two copies of paper ( one with name &  right 4 digits of ssn, one with only  4-digit id ) , and e-copy:
(a)  Obtain approval of topic:
      Email the full reference  (author, title, journal/publisher, date, pages, url )  and a brief description.
      Be sure to include your name in your email.
(b) Write a summary/review of the item you selected.
      Your paper must be readable by other students in CIS501.
      It should have an appropriate title;
      It must be  typed, spell-checked;
      it must include some references (at least of your source) in the correct form;
      it must include both a summary of the concept that you read about
         and an evaluation of the paper you read (was it readable, well presented, was the topic useful, etc.).
      The length must be 2-5 pages of text (you may include additional pages of diagrams, references) .
(c)  Later you will receive a paper from some other student.
      You are to check the paper.  Mark  comments and corrections using red ink.
      Give two evaluation scores:  (0-5) for grammar, structure, and readability
                                                 (0-5) for technical content and clarity, for both summary and evaluation

Project: New project or Extension of  previsous class project
You may work in pairs, but that is not required.
You do not have to implement all of the features that are included in your design.
Construct a typed cover page with a list of the required milestones and room for inspector's signature and date of inspection.
For inspections, diagrams may be hand drawn; for final submission, the diagrams should be drawn using a UML tool.
Mile stones are:
    [1] Use case diagram, concise  statement, and  description of  features.
    [2] Active GUI model  (sketch or screen snap shots) and associated state model
    [3] Domain model.
    [4] Scenario(s) of some major operations
    [5] Statement of plan for testing.
    [6] Notice that "some" coding completed.
    [7] Demonstration to class and/or to instructor. (optional)
    [8] Submit disk /CD  of the project with bat file, source, class files, and , copies of the diagrams.
         Submit hard copy of the milestone items, diagrams,  and list of the source file names and sizes.
         Put disk and papers in 8.5 x 11 size  envelope (which is slightly larger than 8.5 x 11).
         Attach the sign off sheet as the cover page for the envelop.
    [9] If you are working in a group, include a signed statement of "who did what" for the project.
 The program should have the usual system features as in previous homework.
Evaluation criteria:
    The work will be judged equally on
    (a) the documentation
    (b) usability of the program and structure of the code.

    (evaluation items to be posted) 
 
 
 
 
 
 
 
 
 
 
 

        ========================================
Assignments from other semesters:

H2.  Use JBuilder.
Due:
          Build a simple program with some GUI components,...
          It should conform to the common requirements (posted elsewhere).

H2.    Message RMI Program:
          Use the remote  interface in .....
          Include appropriate RMI calls  in the message wrapper from your H1.
          (See the sample Client class  and the Message interface.)
          Run your modified program.
          Add a new message (parameters are your name and the text message)  to the RMI Message service.
          Submit hardcopy of your new message wrapper.<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

H3.    UML Diagrams for......
          Use Together (or equivalent UML tool).
          Develop the class model for ...... (no GUI or data storage classes).
          Develop the sequence diagrams for ......
          Notes:   Together Guide  )

H4:  Writing Assignment:
          Two copies of paper, 1 4-digit id (no name), and e-copy:
(a)  Obtain approval of topic:
      Email the full reference  (author, title, journal/publisher, date, pages, url )  and a brief description.
      Be sure to include your name in your email.
(b) Write a summary/review of the item you selected.
      Your paper must be readable by other students in CIS501.
      It should have an appropriate title;
      It must be  typed, spell-checked;
      it must include some references (at least of your source) in the correct form;
      it must include both a summary of the concept that you read about
         and an evaluation of the paper you read (was it readable, well presented, was the topic useful, etc.).
      The length must be 2-5 pages .
(c)  Later you will receive a paper from some other student.
      You are to check the paper.  Mark  comments and corrections using red ink.
      Give two evaluation scores:  (0-5) for grammar, structure, and readability
                                                 (0-5) for technical content and clarity, for both summary and evaluation

H5 Project:  Extension of  Java Text Memorization Helper Tool  (as described in class)
You may work in pairs, but that is not required.
You do not have to implement all of the features that are included in your design.
Construct a typed cover page with a list of the required milestones and room for inspector's signature and date of inspection.
For inspections, diagrams may be hand drawn; for final submission, the diagrams should be drawn using a UML tool.
Mile stones are:
    [1] Use case diagram, concise  statement, and  list of likely new  features.
    [2] GUI model  (sketch or screen snap shots)   + state model of GUI behavior.
    [3] Test data and list of test cases.
    [4] Domain model.
    [5] Scenario(s) of some major operation (as assigning questions, checking memorization, and displaying questions).
    [6] Notice that "some" coding completed.
    [7] Have some other student use and evaluate your program.
         Include a statement of evaluation by the other student.
    [8] Demonstration to class and/or to instructor.
    [8] Submit disk /CD  of the project with bat file, source, class files, and , copies of the diagrams.
         Submit hard copy of the milestone items and list of the source file names and sizes.
         Put disk and papers in 8.5 x 11 size  envelope (which is slightly larger than 8.5 x 11).
         Attach the sign off sheet as the cover page for the envelop.
    [9] If you are working in a group, include a signed statement of "who did what" for the project.
Check off items may be submitted to either Hankley or TA, but at least some items should be submitted to Hankley.
The program should have the usual system features as in previous homework.
Evaluation criteria:
    The work will be judged equally on
    (a) the documentation
    (b) usability of the program and structure of the code.

Homework 6.  Small, non-GUI C++ program.
Build a C++ (or C#) version of  the message generator program.
A simple text I/0, command line interface is sufficient,
 but you may use a GUI interface.
The key point is that the program must use a well-formed object-oriented structure.
Submit at least disk with source code and an executable file ( H7.exe or "aout" )
Submit hardcopy of the source and a log of sample execution.