At the dawn of the second Toyota project we are looking to strengthen our reporting side. For the second project, Jasper Reports will be integrated and we will present reports as pdf files.
Also we will use incremental prototyping. we will agree upon two-three weeks of screens on prototypes and move forward.
For big projects model driven development can be needed, but when a small project comes up it is probably better to keep paperwork minimum and delve into prototyping(assuming you have a framework to build upon). Generally a well studied use-case and activity diagrams of a few key scenarios and state diagram of a few key entities would suffice. Key to success is test driven development i believe. For me any project scope larger than 6 months is doomed to fail. Even a big project can be scheduled to give fruits in 6 months cycle.
For our next project at Toyota we will do storyboarding as the use-case diagrams are being fleshed out with all interested parties.
Two software is promising:
At Toyota, migrating to new system is fun and challenging.
You need to have excel skills as well as a good understanding of new java regexp package,
the other system i helped designed is deployed on a OS/390 websphere, no actually ibm couldnt manage it..
i hope they can install SunJCE to that machine when we ask them to. Cause we are informed that EAR file we have given is undergoing through an instruction code manipılation before it is deployed.
i also hope that reflection which is at the heart of any serious java framework these days wont be broken by the transformation. i am not asking too much am i?
they wouldnt call it java compatible would they ?
Atlassian - JIRA - Customer Testimonials: "(an internally developed and used Microsoft bug tracker.) I'd put JIRA second"
thank you my darling for your understanding.
sen olmasan ben ne yapardım:)
