How to reset Aparchi Server with Eclips in java

In the eclips IDE , go to Window.
Click on Preferenece.
click on Server
click on Runtime Environment
If any server version have currupt or any prople of apparch server, from here You just remove all versions.
After add the required Aparchi version .
click on OK ...
Restart IDE and have fun with Eclips..

Requirements Gathering With OOA&D

Let the customer talk--find what the system needs to Do...(later can think how the system will do)
U need to imagin and relised how the system actually work to get better requirements..
Ask the questions to identify actually what they need..,.........
want to imagin by listing the steps for each tasks one by one.......

1. List out the steps for a task(for one task may be 7 steps to complete the task)
2. Write down the ALTERNATE PATHS for each steps which may be affect for that task
3.

Use cases
Use case is what the system does to accomplish agoal...
List of steps that the system has to do work correctly...
usecase is for specially accomplishing one perticular goal...
For each goal required seperate use cases..

We can easily realise soround stuffs of task by creating use cases(Ex-door want to close automatically)...therwise never can it properly..
We can use use cases for explain the system to customer or Boss...
want to maintain as simple with everyday language..


Use cases
1. Every use case must have a clear value to the system(mean usecase help to the achive the goals)
2. Every use case must have definite starting and ending point..
3. Every use case have a external initiator...it may be out side the system.


Ex-
1. clear value - Todd at the bed, dog out side the .....no warries...
2. External Initiator-dog barks for to be let out
3. stoping point -The door shut automatically

AFTER WANT TO CHECK REQUIREMENT LIST AND USE CASES TO CHECK WHETHER ALL THE REQUIRMENTS HAS COVERED OR NOR...
Compare the requirements to apply foe each use case steps....

With Requiremnts and Use cases and after comparing and finalising it , can start the coding.................

First implement main uce cases and second vertion do for the alternate paths...

Also checking on use cases we can identify correct requirements..............

Make sure ur requirements cover all the steps in the use cases for ur system..

Use use cases to find out about things ur customer forget to tell u......

Use cases will reveal any incomplete or missing requirements that might have to add to ur system....

page 139 hv definitions in a box...............

use cases hv two paths....
1. main path(this is the process hapening most of the time)
2. Alternate paths(some time may be happen)

Senario is a complete path through a use case , from the first step to the last.

Any time u change the use case , want to recheck the requirement list against to the new use cases..
Most use cases hv several different senarios..
But thye always share the same user goal..

How to do Object Oriented Analysis and Design-01

Good OOA&D give folowing reuslts...

1. satisfy customer and software must do what the customer wants it to do.----getting good requirements with some analysing
2. Apply OO pronciples to add flexibility
3. Strive for a maintainable, resusable and well design.

if the system meet above requirements, that system hv good OOA&D....

---------------REPEAT THIS STEPS------------------------------

System must work ----------------getting proper reqs and make correct functions to meet customer needs
Keep working for every day-------no crashes when using system unusual way = robust,
must be able to esily upgrade----using encapsulation, composition, delegation can make app maintainable and extentionable
must be able to esily Reused-----by avoiding all sort of nasty dependencies and associations that really dont need. for this can use OCP and SRP.
System must be flexible----------by refactoring and turn it in to nice framwork, so then it can use for different purpose.

encapsulation is breaking app into logical parts.
delegation is giving another object the responsiblity of handling a perticular task.
Always remind what the customer need.....
Once got the basic funcctionalities of app in place, work on refining the design so its flexible...
with good functional and flexible design ..U think for proper design pattern for improve design further and to easiar to reuse...
FIND THE PARTS OF UR APPLICATION THAT CHANGE OFTEN, AND seperate them from the parts DON'T CHANGE.....

OOA&D satisfy customer and also proframer.....//////////////////////////////////////////////////


well designed,well coded, easy to maintain, reuse, extend.

Good OOD is less problems for customer and less maintainging for developer
its automatically robust code
Ex-Using enums.........

From our first function we want to implement good design techniqs

Analyse a method..
based on user input data
based on function processing path
based on how generating results
based on what user getting results


1.Objects should do what their names indicate.
2.Each object should represent a single concept.
3.Unused properties are dead give away
3.Anywahere u see duplicate code , look for a place to encapsulate


must apply with better user satisfaction
oo design
no duplicate coding
best reusability
loosly copling
no modification, only extention
Delegation is when an object needs to perform certain events, and instead of doing that task directly , it ask to another ogbect to handle the task.
Delegation is good and it make code resusable
Delegation helps to make loosly coupled apps
Loosly coupled objects can use in another objects easily

Loosly coupled means objects in application each have specific job to do and only hv that job.
So the functionalty of app is spread out over lots of well-defined aojects, which each do a single task is really well