What defines an "analyst programmer"?

I'm trying to suss out a few things at my work with regards to my role, etc........

To me, they're higher on the food chain than programmers: they do analysis tasks like requirements gathering and documentation, define architectures, design whole systems, and tend to be more senior people. They might do some programming, but less than a dedicated programmer, and less than they used to earlier in their career.

NOTCHOOOOOO!!!

I disagree commando.

A/P's can exist in at all levels on the food chain.

To me an Analyst Programmer is a label for a Software Engineer who participates in the Requirements Gathering, Systems Analysis and Design and Implementation phases.

That doesn't sound unreasonable, but i've found that requirements gathering/analysis and design/architecture are typically done by the more senior people.

So someone who does everything from helping the client write the brief to testing the final product would be an Analyst Programmer of sorts?

Does it change things much if the programming is done in ASP (with a MS SQL Server database)?




TheChad - get over yourself.

Someone who does the whole lot - i'd call them a software developer, not an analyst programmer. Actually I wouldn't call anyone an analyst programmer, it's an outdated title, IMHO. What you said is probably true though, no matter what language and tools you use.

Analyst Programmer really does mean to me that the person is quite senior, in charge of others usually. Remember all this is my opinion, not fact.

PFunk: Head Nail Hit, the key bit being that they are involved with the analysis of the problem domain and proposed solution.
The term is technonogly neutral

And yes commando I do prefer the term software developer for a role that has full lifecycle involvement.

hmmm this is interesting just out of curioisity what size software companies / development are you guys working on ?

In my experience an analyst prgrammer wouldn't be involved in writing the brief or the testing of the end product thats what your BA / QA / TA's are for.

however i would say an analyst programmer was involved in the architectural decisions (the high level design) as well as the solution to meet these decisions (low level design) and the actual programming of said solution (code monkeying )

To me an AP is someone who role is both similar to a BA and a Software Engineers.

Meaning the write the specs.

Mmm.. I wouldn't say that seniority and AP's go hand and hand as it depends upon the project.

Typically AP's are used for small projects where as the roles are seperated to BA / Engineers for larger projects.

My first job description was AP, then I became Senior AP, not I'm simply an Engineer.

PD - I just emailed you @dancenet

OK I've just recently gotten a new job as a "Graduate Analyst Programmer".

Here is an abbridged copy of my job description:

Designing, developing and maintaining software solutions for XXX customers.

Assisting Business Analysts and other stratgeic staff to define the customer's business needs, identify their requirements, scope, specify and design solutions.

Participation in the strategic planning, development and implementaion od IT solutions, ensuring delivery within time and budget of systems that meet the customer's real needs.

Participating in process improvment activites.

Supporting the sales and marketing staff to assist in identifing commercial opportunities, securing contracts and contributing to the on going development of XXX.


Hopfully you find this useful PFunk.

Cheers RoqueOne - that's pretty much what I do