Editing Software company (section)

== Common roles in a software company ==

Organizing a [[software]] company is a very specialized type of management skill, where experienced persons can turn the organizational problem into a unique benefit. For example, having sub-teams spread in different [[time zones]] may allow a 24-hour company working day,  if the teams, systems, and procedures are well established. A good example is the test team in a time zone 8 hours ahead or behind the development team, who fix [[software bug]]s found by the testers.

A professional software company normally consists of at least three dedicated sub-teams :
*[[Business analyst]]s who define the business needs of the market
*[[Software developer]]s who create the [[Specification (technical standard)|technical specification]] and write the software
*[[Software tester]]s who are responsible for the whole process of [[quality management]]

In bigger software companies, greater specialization is employed, and quite often there are also:

*[[Technical writer]]s who write all the [[Software documentation|documentation]] such as [[user guide]]s
*Release specialists who are responsible for building the whole product and [[software versioning]]
*[[User experience design]]ers, who are creating the design architecture based on business requirements, user research and expertise in [[usability]]
*[[Graphic designer]]s who are normally responsible for the design of the [[graphical user interface]].
*Maintenance engineers who are behind two, three or more lines of support
*Consultants are responsible for making the solution operational, especially if some specialist knowledge is necessary. Examples of this include: building [[Multidimensional scaling|multidimensional cubes]] in [[business intelligence software]], integrating with existing solutions, and implementing business scenarios in [[Business Process Management]] software.