(Object-Oriented Software Engineering) (Fall 2004)
- Section 3 -

Project Final Phase (Due Jan 3rd, 2005)  (Group Work) (Updated: Dec 30,2004@18:25)

a. A 10-15 minute presentation of the project work (Architectural Model, Deployment Diagram, Component/Package Diagram, Use Case Diagram, Class Diagrams, Selected Dynamic and Behavioral UML diagrams)  

b. A 10-15 minute demonstration and application of selective test cases (acceptance testing) and showing of metric results.

c. Revised reports: domain analysis report, requirements analysis reports (including use cases and use case diagrams, domain model), software design report (all other types of UML diagrams and UI snapshots).

d. The Software Test Plan (test environment and all applicable test cases) and test results (Ticking next to the test cases to state that your software has passed all test cases successfully is sufficient).

e. Traceability Matrix (requirements/use cases - design items - UI items - test cases)

f. Results of software code  metrics. (These will be obtained using Together. The metrics to be observed are  given in the Notes. Justify your metrics if they are beyond the limits.

Important Notes

1. The last handout contains some nice examples on deployment, component, and package diagrams. Use the ideas there in your reports!

2. Your presentations may be done by showing the diagrams on Together as far as they are understandable. You don't have to prepare separate powerpoint slides.

3. Demonstrations will be held on Monday Jan 3rd, 2005 starting at 13:30. Before the demostration you should turn in your printed reports. Come and listen to other people's solutions and join the public juri!

4. Each student will also be asked to do a peer evaluation of the project group members on Monday.

5.You are expected to bring your own laptop or computer for the demonstration.

6. Sample Traceability Matrix (in MS Word or Excel)

7. Metrics to be observed are Basic (LOC, NOA, NOC, NOO), Cohesion (LOCOM3), Complexity (CC), Coupling (CBO), Encapsulation (AHF, MHF), Depth of Inheritance, Maximum (MNOL, MNOP, MSOO),  Polymorphism (NOAM, NOOM), Ratio (CR). 

8. We will run your own test cases but  with my data inputs.  No input verification is required. But use combo boxes, radio buttons, etc. where possible to eliminate wrong entries.

9. You are expected to use the OCSF framework and use the server to keep/serve the data. 

10. Do you really need to use a database or store all data persistently in the database? NO!  As one of you have already noticed, initializing all objects from the main() when the program is run and keeping all relevant information in memory for the entire lifetime of the program may be a better way to exploit the object-oriented technology better. As I said earlier using a database is not mandatory. 

Project Phase 3  (Due Dec 13th, 2004)  (Group Work)

a. Revise what you have done in Phase I (P4.4) as necessary.

b. Revise what you have done in Phase II (~P5.1) (~P7.5) (~P7.6) as necessary.

c. Do (P8.3)

d. Draw package, component and deployment diagrams for your system.

Project Phase 2  (Due Nov 22nd, 2004)  (Group Work)

(~P5.1) Create a class diagram of the 'Small Hotel Reservation System'. Base your analysis on the requirements you developed in the first project phase. Your diagram should have any necessary classes, associations, generalizations and attributes. Submit the hard copy of your work.

(Determine the responsibilities and operations as much as possible based on your current knowledge.) 

(~P7.5) Develop a complete set of use cases for the Small Hotel Reservation System. (Note that you do not have to draw the Use Case Diagrams yet! Just represent your use cases verbally as we have seen in Section 4.6) Submit the hard copy of your work.

(~P.7.6) Develop a prototype user interface (UI) for the  Small Hotel Reservation System, as follows. If possible, involve users from the hotel industry.

Step 1.  Do some parallel design of paper prototypes (see Section 4.6). Then pick the best features of each paper prototype to create a final version. 

Step 2. Use a rapid prototyping tool (e.g., Together's or JBuilder's GUI designer) to create a partially functional prototype (just the UI) based on your paper prototype. This prototype will not actually manipulate any data, so it will not make use of the object model you have developed.

Step 3. Have people use your prototype. Observe the difficulties they have. Change the prototypes as necessary. 

You need to submit only the final screenshots of your prototype.

Project Phase 1  (Due Nov 8th, 2004)  (Group Work)

P4.3 Perform a domain analysis about hotel reservations. This will help you to resolve certain ambiguities that might be present in the above statement of requirements. (You may choose to use internet search intensively instead of interviewing with the stakeholders)

P4.4 Develop a full requirements definition for the above problem. Among the techniques you should consider employing are the following: 

- interview some people who run hotels, and take a look at existing front-desk systems (You may choose to use internet search intensively instead of interviews); 

- use brainstorming techniques to refine the requirements; 

- perform use-case analysis to determine who the actors are and what tasks they must perform.

As you do the above, narrow the problem statement, excluding features that will noit be needed in the first release. Before you complete your requirements definition, make sure you hold a formal review.

Submit the hard and soft copies of your work.

Final Exam grades posted.

Final  project  phase's grades posted.

Final Exam Solutions posted.

Letter grades will be determined after they are normalized with other CS-319 sections' grades.

Final note: You have only seen part of the OO world. You should really work hard to reach the required expertise level in the commercial world.