Software developer
In the US, software developer is a job classification.
(TO DO: expand, organize, cross-reference, illustrate.)
Contents
Description
Software developer jobs classified into one of three titles (all under the 15-0000 Computer and Mathematical Occupations Major Group):
- 15-1131 Computer Programmers<ref name="15-1131 Computer Programmers">
- 15-1132 Software Developers, Applications
- 15-1133 Software Developers, Systems Software
A person who develops stand-alone software (that is more than just a simple program) and gets involved with all phases of the development (design and code) is a software developer.
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,Template:Dubious 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.
See also Debate over who is a software engineer.
Aspects
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
Scale
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.
