enow.com Web Search

Search results

1. Results from the WOW.Com Content Network

2. Lead programmer - Wikipedia

   en.wikipedia.org/wiki/Lead_programmer

   A lead programmer has responsibilities which may vary from company to company, but in general is responsible for overseeing the work, in a technical sense, of a team of software developers working on a project, ensuring work meets the technical requirements, such as coding conventions, set by the software architect responsible for the underlying architecture. [1]

3. Software engineering - Wikipedia

   en.wikipedia.org/wiki/Software_engineering

   Software engineering is a field within computer science focused on designing, developing, testing, and maintaining of software applications. It involves applying engineering principles and computer programming expertise to develop software systems that meet user needs.

4. Technical director - Wikipedia

   en.wikipedia.org/wiki/Technical_director

   In software development, a technical director is typically responsible for the successful creation and delivery of the company's product to the marketplace by managing technical risks and opportunities; making key software design and implementation decisions with the development teams, scheduling of tasks including tracking dependencies, managing change requests, and guaranteeing quality of ...

5. Programmer - Wikipedia

   en.wikipedia.org/wiki/Programmer

   A software engineer usually is responsible for the same tasks as a developer plus broader responsibilities of software engineering including architecting and designing new features and applications, targeting new platforms, managing the software development lifecycle (design, implementation, testing, and deployment), leading a team of ...

6. Software architect - Wikipedia

   en.wikipedia.org/wiki/Software_architect

   A software architect is a software engineer responsible for high-level design choices related to overall system structure and behavior. [1] It's software architect's responsibility to match architectural characteristics (aka non-functional requirements) with business requirements. For example: [2]

7. Systems architect - Wikipedia

   en.wikipedia.org/wiki/Systems_architect

   In general, the role of the architect is to act as a mediator between the users and the engineers, reconciling the users' needs and requirements with what the engineers have determined to be doable within the given (engineering) constraints. In systems design, the architects (and engineers) are responsible for: