Is this a normal project? 1

[Tschibo]

Hi there!
I'm working in an apartment of a big automotive company which is responsible for research on topics of software architecture.
Originally i was employed as a Java specialist with experiences in GUI design/programming.
But the project i'm in turned out to be quite different from what i expected. We're doing now research about existing tools for over 8 months. All i did till now was reading documents, getting to conferences where i was shown this-and-that tool, writing documents and meeting with our customer.
That's definitely not what i expected of "software architecture".

Do you think, that this is normal for a research department? Or is it this very project?
What are your experiences? How can i motivate myself getting on?

Thank you very much
Christoph

 

[CajunCenturion]

this is normal for a research department For a research department, yes. You're doing research in a department whose function is to research software engineering methodologies. This is basically an academic pursuit which has real world applicability. Software Architecture is design, not code development. A building architect designs a building, but doesn't actually build it - that task is turned over to a contractor, with the architect insuring that specs are being met with respect to functionality and tools - walls and doors in the right place, and the right grade of concrete and glass, and so forth.

This is no different with software. The Architect is the designer - the writing of code is the production staff, and the architect insures that software specs are being met and the proper tools are being used. Sometimes, you need to do a litter research on your own to know just what those tools are. That is software architecture.

Sounds like you'd rather be in software development, actually writing the code. If that's the case, and you're not happy in that department, then I suggest you inform your superiors of how much you've enjoyed your work here, how much you've learned, and how much you'd really like to put this new-found knowledge to work. That may be in the form of a transfer into a production department, or you might be able to sell your boss on the concept of benchmarking tools against each other. Actually write programs to test the various tools against each other, and gather real hard data over which tool is best. Good Luck
--------------
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[Tschibo]

CajunCenturion,
i know what software architecture/design is, but what i'm doing it's definitely not. To clarify my situation in the example of the real world architect: My job is actually like checking out the different machines and tell the architect which to use for building the house...
Analyzing/evaluating different tools for 8 months can't be it. This is rather the job for a consulting company but not for a research department. Nearly no IT knowledge is needed for that job.

Christoph

 

[CajunCenturion]

If you're analyzing and evaluating different tools to use for a job - how is that not research? What else could it be?

I don't mean to be argumentative. I guess I'm just not sure on what your definition of research is.

I'm working in an apartment of a big automotive company which is responsible for research on topics of software architecture. I can understand that its not what you want to do, but it does sound like your job is consistent with the mission of that department. Good Luck
--------------
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[Tschibo]

CajunCenturion,
thank you. You're not argumentative, that's what i wanted to know. To summarize it: The project fits the department's mission and i'm not really happy with it.
But i'm gaining experience, reputation and money for it

Thanx again
Christoph

 

[CajunCenturion]

Its certainly good to gain experience, reputation, and money doing it, but being happy is also important. You might want to keep your eyes and ears open about a position opening up in one of the other IT departments within your company, and if the situation is right - maybe you could transfer to it. Good Luck
--------------
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[Tschibo]

I'm already thinking about that, but i guess, i can't change (at least it's not for against my project leader) until the projects finished.
I've heard (from a good friend) about a very interesting department which would most likely meet my wishes