When.com Web Search

  1. Ads

    related to: software architect role and responsibility in project management

Search results

  1. Results From The WOW.Com Content Network
  2. 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.

  3. Responsibility assignment matrix - Wikipedia

    en.wikipedia.org/wiki/Responsibility_assignment...

    In business and project management, a responsibility assignment matrix [1] (RAM), also known as RACI matrix [2] (/ ˈ r eɪ s i /; responsible, accountable, consulted, and informed) [3] [4] or linear responsibility chart [5] (LRC), is a model that describes the participation by various roles in completing tasks or deliverables [4] for a project or business process.

  4. 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]

  5. Software project management - Wikipedia

    en.wikipedia.org/wiki/Software_project_management

    Software project management is the process of planning and leading software projects. [1] It is a sub-discipline of project management in which software projects are planned, implemented, monitored and controlled.

  6. Software architecture - Wikipedia

    en.wikipedia.org/wiki/Software_architecture

    Software architecture is the set of structures needed to reason about a software system and the discipline of creating such structures and systems. Each structure comprises software elements, relations among them, and properties of both elements and relations.

  7. Architectural decision - Wikipedia

    en.wikipedia.org/wiki/Architectural_decision

    Often, no single optimal solution for any given set of architecture design problems exists. Architectural decision making is a core responsibility of software architects; [5] additional motivation for/of the importance of architectural decisions as a first-class concept in software architecture can be found online. [6]