AseerZa3beel said:
Please I want an expert in java to help me solving a portfolio, because Im go to a trip outside the country and I should handle the project before the 9 10 2006
Hi, AseerZa3beel. What do you mean by portfolio?
Develop a small application for a Business. Your application must include the following:
1) The business scenario and the business Logic
2) UML design (classes, attributes and methods)
3) Class Relationship diagram
What business? Is this something that you can make up? How you approach this depends on whether you are required to adhere to a specific development methodology such as RUP (Rational Unified Process).
In most cases, you would be in contact with people at the business to discover what their objectives and develop use cases and possibly other models from these communications. At the casual/agile end, this might be a collection of notes for what they are trying to accomplish each week. At the more formal/predicitive end, this could result in a SRS (Software Requirement Specification) spanning hundreds of pages which could under go several revisions before any code is even written.
One use of UML is to model the user's view of the software and use case diagrams are often helpful in doing this (see
http://en.wikipedia.org/wiki/Use_case_diagram for a simple introduction). UML is more often thought of as a way to describe types and relationships within an application or network of applications. Some development shops deeply take this approach and use highly methodical, tools-driven techniques in designing and, notably, maintaining their software, automatically producing program source from UML diagrams.
For the project you seem to be describing (which I'm guessing is some kind of school related assignment), I think you would want a short document describing the business rules and use cases accompanied by a use case diagram, along with one relatively simple class relationship diagram. For this level of complexity,
ArgoUML would be a good free program to use.
4) Java Code (soft copy saved in M drive and hard copy)
At lease one Interface
Inheritance
At least one super class
At least two sub classes (i.e. 2 levels of inheritances)
Validation: Any data entered by the user must be validated
Necessary methods: Calculation method, printing method, etc.
Conventions: Must follow proper conventions.
You can find Sun's Java coding conventions here:
http://java.sun.com/docs/codeconv/
It is an unsuprising evolution of modern C style with CamelCase notation.
It is important to find out if 'printing' is print to screen or using a printer. Printing (with paper) in Java is much easier with a solid understanding of how Graphics are handled through AWT/Swing and there are a few different basic approaches with varying level of complexity/flexibility.
Validation should carefully handle exceptions in a reasonable, transactional way. It could be encapsulated in an InputVerifier or put in a reusable controller.
To be honest, many business applications only occasionally need three levels of subclasses and over use of inheritance can reduce the clarity of a program. The truth about Java is that it is not a pure object-oriented language, though it is more OO-focused than C++. In any case, you can often create deep inheritance trees by carefully considering the elements of the business work. E.g., a package could be more specifically a UPS package and then a 2-day UPS package, etc.
Oh, and never, never save anything to drive M.
