Software developer - Computer Science

A software developer is a person concerned with facets of the software development process. Their work includes researching, designing, implementing, and testing software.^[1] A software developer may take part in design, computer programming, or software project management. They may contribute to the overview of the project on the application level rather than component-level or individual programming tasks. Software developers are often still guided by lead programmers but the description also encompasses freelance software developers.

In the US, a software developer is classified into one of 3 titles (all under the 15-0000 Computer and Mathematical Occupations Major Group):^[2]

15-1131 Computer Programmers^[3]
15-1132 Software Developers, Applications^[4]
15-1133 Software Developers, Systems Software^[5]

A person who develops stand-alone software (that is more than just a simple program) and got involved with all phases of the development (design and code) is a software developer.^{[citation needed]} Some of the notable software people include Peter Norton (developer of Norton Utilities), Richard Garriott (Ultima-series creator), and Philippe Kahn (Borland key founder), all of whom started as entrepreneurial individual or small-team software developers.

Other names which are often used in the same close context are programmer, software analyst, and software engineer.

According to developer Eric Sink, the differences between system design, software development and programming are more apparent. Already in the current market place there can be found a segregation between programmers and developers,^{[dubious – discuss]} being that one who implements is not the same as the one who designs the class structure or hierarchy. Even more so that developers become systems architects, those who design the multi-leveled architecture or component interactions of a large software system.^[6] (see also Debate over who is a software engineer)

Aspects of developer's job may include:

Software design
Actual core implementation (programming which is often the most important portion of software development)
Other required implementations (e.g. installation, configuration, customization, integration, data migration)
Participation in software product definition, including business case or gap analysis
Specification
Requirements analysis
Development and refinement of throw-away simulations or prototypes to confirm requirements
Feasibility and cost–benefit analysis, including the choice of application architecture and framework, leading to the budget and schedule for the project
Authoring of documentation needed by users and implementation partners etc.
Testing, including defining/supporting acceptance testing and gathering feedback from pre-release testers
Participation in software release and post-release activities, including support for product launch evangelism (e.g. developing demonstrations and/or samples) and competitive analysis for subsequent product build/release cycles
Maintenance

In a large company, there may be employees whose sole responsibility may consist of only one of the phases above. In smaller development environments, a few, or even a single individual might handle the complete process.

Separation of concerns

In more mature engineering disciplines such as mechanical, civil and electrical engineering, the designers are separate from the implementers. That is, the engineers who generate design documents are not the same individuals who actually build things (such as mechanical parts, circuits, or roads, for instance). In software engineering, it is more common to have the architecture, design, implementation, and test functions performed by a single individual. In particular, the design and implementation of source code is commonly integrated.^{[citation needed]}

This resembles the early phases of industrialization in which individuals would both design and build things. More mature organizations have separate test groups, but the architecture, design, implementation, and unit test functions are often performed by the same highly trained individuals.^{[citation needed]}

References

^ "O*NET Code Connector - Software Developers, Systems Software - 15-1133.00". Onetcodeconnector.org. http://www.onetcodeconnector.org/ccre port/15-1133.00. Retrieved 2013-01-13.
^ "15-0000 Computer and Mathematical Occupations (Major Group)". US Bureau of Labor Statistics. http://www.bls.gov/oes/current/oes150 000.htm.
^ "15-1131 Computer Programmers". US Bureau of Labor Statistics. http://www.bls.gov/oes/current/oes151 131.htm.
^ "15-1132 Software Developers, Applications". US Bureau of Labor Statistics. http://www.bls.gov/oes/current/oes151 132.htm.
^ "15-1133 Software Developers, Systems Software". US Bureau of Labor Statistics. http://www.bls.gov/oes/current/oes151 133.htm.
^ Eric Sink. "Small ISVs: You need Developers, not Programmers". sourcegear. http://software.ericsink.com/No_Progr ammers.html. Retrieved 2008-06-06. "A programmer is someone who does nothing but code new features and (if you're lucky) fix bugs. They don't write specs. They don't write automated test cases. They don't help keep the automated build system up to date. They don't help customers work out tough problems. They don't help write documentation. They don't help with testing. They don't even read code. All they do is write new code."