processes, in which progress is seen as flowing steadily downwards through the phases of conception, initiation, analysis, design, construction, testing, production/implementation and maintenance.

Requirements – analysis in systems and software engineering that encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements
Design – the process by which an agent creates a specification of a software artifact, intended to accomplish goals, using a set of primitive components and subject to constraints. Problem solving.
Development – the detailed creation of working meaningful software through a combination of coding, verification, unit testing, integration testing, and debugging
Testing/Debugging – an investigation conducted to provide stakeholders with information about the quality of the product or service under test.
Deployment – all of the activities that make a software system available for use.
Maintenance – the modification of a software product after delivery to correct faults, to improve performance or other attributes.

Enterprise Architect – work with stakeholders, both leadership and subject matter experts, to build a holistic view of the organization’s strategy, processes, information, and information technology assets. The role of the enterprise architect is to take this knowledge and ensure that the business and IT are in alignment.

Project Manager– the person responsible for leading a project from its inception to execution. This includes planning, execution and managing the people, resources and scope of the project.

Scrummaster – the facilitator for a product development team that uses scrum, a rugby analogy for a development methodology that allows a team to self-organize and make changes quickly.

SAFe Practitioner – an expert in a freely-revealed knowledge base of integrated patterns for enterprise-scale Lean-Agile development.

Business Analyst – someone who analyzes an organization or business domain (real or hypothetical) and documents its’ business or processes or systems, assessing the business model or its’ integration with technology.

Business Systems Analyst – a person who works directly with management and users to analyze, specify, and design business applications. Translates business requirements into technical requirements for the developers.

Product Owner – the member of the team responsible for defining stories and prioritizing the team backlog to streamline the execution of program priorities, while maintaining conceptual and technical integrity of the features or components the team is responsible for.
Product Manager – responsible for analyzing market conditions and defining features or functions of a product.

Developers – a person concerned with facets of the software development process, including the research, design, programming, and testing of computer software.

Rails (RoR) – an open source framework for Web development in Ruby, an object-oriented programming (OOP) language.
.NET– a software development framework from Microsoft. It provides a controlled programming environment where software can be developed, installed and executed on Windows-based operating systems.

Java – a general-purpose computer programming language that is concurrent, class-based, object-oriented, and specifically designed to have as few implementation dependencies as possible.