enow.com Web Search

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. For example: [2]

3. Responsibility-driven design - Wikipedia

   en.wikipedia.org/wiki/Responsibility-driven_design

   Responsibility-driven design is a design technique in object-oriented programming, which improves encapsulation by using the client–server model. It focuses on the contract by considering the actions that the object is responsible for and the information that the object shares. It was proposed by Rebecca Wirfs-Brock and Brian Wilkerson.

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

5. Software design - Wikipedia

   en.wikipedia.org/wiki/Software_design

   Software design usually is directed by goals for the resulting system and involves problem-solving and planning – including both high-level software architecture and low-level component and algorithm design. In terms of the waterfall development process, software design is the activity of following requirements specification and before coding ...

6. GRASP (object-oriented design) - Wikipedia

   en.wikipedia.org/wiki/GRASP_(object-oriented_design)

   General Responsibility Assignment Software Patterns (or Principles), abbreviated GRASP, is a set of "nine fundamental principles in object design and responsibility assignment" [1]: 6 first published by Craig Larman in his 1997 [citation needed] book Applying UML and Patterns.

7. Software architecture - Wikipedia

   en.wikipedia.org/wiki/Software_architecture

   Software architecture patterns operate at a higher level of abstraction than software design patterns, solving broader system-level challenges. While these patterns typically affect system-level concerns, the distinction between architectural patterns and architectural styles can sometimes be blurry. Examples include Circuit Breaker. [13] [14] [15]

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

9. 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 ...