Intended Audiences

This website is intended for anyone interested in:

• The development, operation, and retirement of software-intensive systems.
• The impacts such applications can have on businesses.

Primary Audiences

This website is primarily intended for use by the following audiences, who must understand their roles, responsibilities, and the tasks they will perform:

• Analysts:
  • Metrics Analyst, which is the role that is played when a person produces metrics for an endeavor.
  • Security Analyst, which is the role that is played when a person engineers an application's security requirements.
  • User Analyst (a.k.a., user researcher), which is the role that is played when a person analyzes users and user organizations to determine the users' desires and needs.
• Architects:
  • Business Architect, which is the role that is played when a person develops the business strategy for a customer’s business.
  • Database Architect, which is the role a person plays when developing the database aspects of the system and software architecture.
  • Hardware Architect, which is the role that is played by a person who produces the hardware architecture of the application.
  • Information Architect, which is the role that is played by a person who produces that information architecture of the application.
  • Security Architect, which is the role that is played when a person architects the security mechanisms of an application.
  • Software Architect, which is the role that is played when a person produces the software architecture.
  • System Architect, which is the role that is played when a person produces the system architecture.
• Content Workers:
  • Content Creator, which is the role that is played when a person creates or obtains new content for one or more applications:
    • Audio Artist, which is the role that is played when a person creates or obtains new audio content for one or more applications.
    • Content Author, which is the role that is played when a person creates or obtains new textual content for one or more applications.
    • Graphic Artist, which is the role that is played when a person creates or obtains new graphic content for one or more applications.
    • Video Artist, which is the role that is played when a person creates or obtains new video content for one or more applications.
  • Content Designer, which is the role that is played when a person designs content and produces the associated templates and transformation software.
  • Content Director, which is the role that is played when a person orders the production of new content.
  • Content Entry Clerk, which is the role that is played when a person enters content for one or more applications into a content management system.
  • Content Translator, which is the role that is played when a person internationalizes content, primarily by translating the textual content of one or more applications:
    • Foreign language content into native language.
    • Native language content into one or more foreign languages.
  • Content Editor, which is the role that is played when a person copy edits textual content prior to approval.
  • Content Approver, which is the role that is played when a person approves content for incorporation into an application and release to the users.
  • Content Publisher, which is the the role that is played when a person publishes approved content to an application (e.g., a website).
  • Content Usage Analyst, which is the role that is played when a person analyzes content usage.
• Designers:
  • GUI Designer (a.k.a., visual designer, information architect), which is the role that is played when a person designs GUIs.
  • Software Designer, which the role that is played when a person designs the software components of an application.
• Domain Expert (a.k.a., subject matter expert), which is the role played when a person provides authoritative information about a given domain (i.e., subject matter area).
• Engineers:
  • Database Engineer, which is the role a person plays when designing, implementing, and installing an application’s databases.
  • Hardware Engineer, which is the role that is played when a person produces the hardware components of an application.
  • Integration Engineer (a.k.a., build master), which is the role that is played when a person integrates the application components.
  • Process Engineer (a.k.a., methodologist), which is the role that is played when a person promotes process engineering at the endeavor and organizational levels.
  • Programmer, which is the role that is played when a person produces the source code for new software components.
  • Quality Engineer, which is the role that is played when a person independently performs quality assurance and control tasks on the endeaver.
  • Requirements Engineer, which is the role that is played when a person performs requirements engineering.
  • Reuse Engineer, which is the role that is played when a person engineers work products to be reusable.
  • Security Engineer, which is the role that is played when a person engineers components, applications, and data centers to meet their security requirements.
  • Test Engineer (a.k.a., tester), which is the role that is played when a person performs testing tasks:
    • Test Monitor, which is the role that is played when a person monitors a test participant during a usability test.
  • Toolsmith, which is the role that is played when a person develops and updates software tools on a project.
  • Usability Engineer, which is the role that is played by a person who implements the human interfaces.
• Managers:
  • Configuration Manager, which is the role that is played when a person manages the configuration management activity on an endeavor.
  • Program Manager, which is the role that is played when a person provides administrative management to a program of related projects.
  • Project Manager, which is the role that is played when a person provides administrative management to a single project.
  • Reuse Librarian, which is the role that is played when a person manages the reuse repository.
  • Scheduler, which is the role that is played when a person maintains the schedule of an endeavor.
  • Technical Leader, which is the role that is played when a person provides techical leadership on an endeavor.
• Operations:
  • Computer Operator, which is the role that is played when a person operates one or more computers and associated perepheral equipment.
  • Database Administrator, which is the role that is played when a person adminsisters one or more databases in the production environment.
  • Network Administrator, which is the role that is played when a person administers one or more networks in the production environment.
  • Systems Administrator, which is the role that is played when a person administers a data center and its associated production environments.
• Strategists:
  • Business Strategist, which is the role that is played when a person develops the business strategy for a customer’s business.
  • Digital Brand Strategist, which is the role that is played when a person develops the digital brand strategy for a customer’s business.
  • Technology Strategist, which is the role that is played when a person develops the technology strategy for a customer’s business.
• Trainer, which is the role that is played when a person trains members of the project team and other project stakeholders.
• Technical Writer, which is the role that is played when a person produces technical documents by incorporating input from other roles.

Secondary Audiences

This website is also intended for use by the following secondary audiences, who may use it to improve their work:

• Academics and Trainers, who can use the content of this website when developing engineering curricula and competency-based training programs.
• Consultants, who can use the content of this website (1) when providing consulting to development or customer organizations and (2) when independently assessing their technical maturity or competency.
• Customer Representatives, who can use the content of this website to better understand the work of members of the development organization.
• Methodologists, who can use the content of this website when iterating and enhancing their methodologies.
• Tool Vendors, who can use the content of this website when developing process support tools or skill assessment tools.